“How can I help you, today?” Super nice (and I imagine super cute) nurse lady who helps people without health insurance.
“I have some pretty severe pain in my stomach. I’m pretty sure my colon has been inflamed for about a week now but I wasn’t sure if it was…
View original post 525 more words
[Frank Zhao]—an awesome guy, an inadvertent Hackaday contributor, and an Adafrut fellow—has come up with a device to use a keyboard and mouse with Playstation 4 games. He calls it the UsbXlater, and even if [Frank] can’t get it working with his PS4, it’s still going to be an awesome tool.
On the board are two USB ports and an STM32F2 microcontroller. The micro provides a USB host interface and a USB device interface, enabling it to translate mouse movements and keystrokes into something a PS4 can understand. While this project was originally designed to use a keyboard and mouse on [Frank]’s shiny new PS4, it’s not quite working just yet. He’s looking for a few gamer/dev folks to help him suss out the communication between a keyboard/mouse, the UsbXlater, and a PS4.
Of course, even if this device is never used for what it’s designed for, it’s still…
View original post 105 more words
Can you spot the serial port in the pic above? You can probably see the potential pads, but how do you figure out which ones to connect to? [Craig] over at devttys0 put together an excellent tutorial on how to find serial ports. Using some extreme close-ups, [Craig] guides us through his thought process as he examines a board. He discusses some of the basics every hobbyist should know, such as how to make an educated guess about which ports are ground and VCC. He also explains the process to guessing the transmit/receive pins, although that is less straightforward.
Once you’ve identified the pins, you need to actually communicate with the device. Although there’s no easy way to guess the data, parity, and stop bits except for using the standard 8N1 and hoping for the best, [Craig] simplifies the process a bit with some software that helps to quickly…
View original post 25 more words
The current marketplace allows hobbyists to easily find inexpensive, well-documented displays, but what if you wanted to interface with something more complicated, such as the screen on an iPod Nano 6? [Mike] has given us a detailed and insightful video showing his process for reverse engineering a device with little-to-no documentation. Here he covers the initial investigation, where one scours the web in search of any available information. In [Mike’s] example, the display uses an MIPI D-PHY interface, which he has never worked with. He learns that the MIPI Alliance will provide design specs in exchange for a signed NDA (Non-Disclosure Agreement) and a modest $8000 fee. Nice.
[Mike] shows off some serious hardware hackery, tackling some extremely difficult soldering in order to set up a proper test platform. He then demonstrates how to use a rather awesome oscilloscope to better understand the display protocol. We found it fascinating to see…
View original post 48 more words
[Fran] has been working on tearing down and reverse engineering the Saturn V Launch Vehicle Digital Computer (LVDC). In her finale, she’s succeeded in depotting the legacy components while keeping them intact.
She accomplished this by carefully removing the silicone compound using a gum brush. This was a laborious process, but it allowed her to see the device’s innards. With this knowledge, she could recreate the logic modules on a breadboard.
[Fran]’s work on the LVDC has been very interesting. It began with a look at the PCB, followed by an x-ray analysis. Next up was a threepartseries of the teardown. With each part is a detailed video on the progress.
While this is the end of [Fran]’s work on the project, she will be handing off the LVDC hardware to another engineer to continue the analysis. We’re looking forward to seeing what comes out of this…
View original post 2 more words
[Kurt] likes to know what’s going on with his network. He already uses bandwidth checking software on his DD-WRT capable router, but he wanted a second opinion. So he built his own network monitor. [Kurt] started by building a passive Ethernet tap. He then needed a network interface chip that would serve his purposes. The common Wiznet chips used with Arduinos didn’t allow enough manipulation of raw packet data, so he switched to a Microchip ENC624J600 (PDF). The Microchip controller allowed him to count the bytes in the raw Ethernet packets.
With the Ethernet interface complete, [Kurt] turned his attention to a microcontroller to run the show. He started with an Arduino, but the lack of debugging quickly sent him to an Atmega128 in Atmel Studio. After getting the basic circuit working, [Kurt] switched over to a PIC24F chip. With data finally coming out of the circuit, he was able to tell that…
View original post 54 more words