[Quinn Dunki] is looking to augment the tools she has available at her electronics bench and built the HEX Out as a mock-logic sniffer. The device reads 8 or 16-bit inputs, showing the current state of those connections on a 7-segment display. This requires that you’re comfortable reading Hex codes, but if you’re not it’s almost like studying flash cards; before long you’ll be able to read them without thinking about it.

She’s blogging about the design and build process in three parts. The link above is the first installment where she shares the development process for the top layer which hosts the display hardware. The other two parts should be up for your enjoyment in the next couple of weeks.

You’ll notice her design on this portion of the project still requires a lot of point-to-point soldering, even though she etched her own circuit boards. We didn’t look too closely, but it seems this would be worth going to the trouble of etching a double-sided board if you can.

UPDATE: Part Two is now available

Quad copters have been pretty popular for the last few years, but this one is new to us. Take the same basic layout, but bump it to 6 rotors. Then you’ll have the hexacopter (google translated). With 6 rotors, built in GPS and stabilization and a camera mounted on the bottom, this thing is pretty well equipped. You can see how agile and stable it is in the video above. We know it isn’t necessarily new, but it is new to us. Of course, you don’t have to stop at 6 rotors. You could always just continue on to 8.

[Incudie] tipped us off about a method to fix a borked HDD in your Xbox 360. Many of the one million consoles banned earlier in the month also had the hard disks scrambled making off-line gaming impossible as well. It turns out that this is caused by having a ban flag in the NAND chip on the motherboard. It has been discovered that because of wear levelling, the NAND will have two copies of the “secdata.bin” file which stores the ban flag. Please note, this will NOT allow the console to use Xbox Live, it just re-enables the HDD.

The quick and dirty of the fix is as follows: First the NAND is dumped from your Xbox 360 to a computer. After verifying the file, it can be opened in a HEX editor and the two copies of “secdata.bin” located. Once identified by date, the older version is injected on top of the newer to overwrite the ban flag.

Looks like this is not for the faint of heart, but if you got banned for modding in the first place this should be easy to pull off.

Update: Looks like xbox-scene now has a collection of apps to help you with this process. [Thanks CollinstheClown]

As a followup to last week’s post on automated protocol analysis, [Tod Beardsley] has written up how to start analyzing a protocol manually. He walks through several examples to show how to pull out the interesting bits in binary protocols. His first step was sending 10 identical select statements and capturing the outbound packets. He used the Ruby library PacketFu to help with the identification. It compared the ten packets and highlighted one byte that was incrementing by four with each packet, probably a counter. Looking at the response indicated a few other bytes that were also incrementing at the same rate, but at different values. Running the same query on two different days turned up what could be a timestamp. Using two different queries helped identify which byte was responsible for the statement length. While you may not find yourself buried in HEX on a daily basis, the post provides good coverage of how to think critically about it.