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.

[Kc7fys] came up with a this simple battery level indicator. It uses a single LED to display a battery’s voltage; if the voltage exceeds 12V, it glows green. If it is below 11V, the LED glows red. Anything in between generates an orange glow. The meter is built around an LM358 chip per this schematic, but his actual build looks pretty sloppy because of the dead-bug assembly (check out NASA’s pretty version). Nonetheless, it works, so clean it up and build one if you want to put it (or your batteries) to the test.