Besmoke – Fluid Dynamics

[vimeo= 2963541]

Besmoke is a fluid dynamics engine. It is compatible with any multitouch system, as well as the accelerometer in an iPhone. It also accepts audio input. The audio input can turn it into a fancy music visualizer that would even work with live or acoustic music. Different frequencies cause fluid to be injected from different “emitters”. There’s great info on his page, including the papers that he based this off of. We’ve covered [Eric]’s work before with his election party light system.

Autofocus Assist Light

afassist

[Aki]’s Nikon D2H did not come with an autofocus assist light.  His other cameras have them, and he likes the feature, so he decided to hack one into his D2H. He wired into the AF system, so that his LED gets voltage when the shutter release is pressed half way. The circuit needs refinement though, he found that the light was staying on during shutter release and affecting his light metering. You can see the hack in action after the break.
Continue reading “Autofocus Assist Light” →

Parts: AT Keyboard

atkeyboard

Last week we introduced a new version of the Bus Pirate universal serial interface tool. The last firmware update included an AT keyboard decoder library for both hardware versions.

There’s a ton of old AT keyboards making their way to the landfill. We’ll show you how to recycle one as an input device for your next project.

Continue reading “Parts: AT Keyboard” →

Forknife, Android G1 Controlled Robot

g1bot

When we first saw [Jeffrey Nelson]’s G1 based robot we immediately wondered what the transport for the controls was. The G1‘s hardware supports USB On-The-Go, but it’s not implemented in Android yet. It turns out he’s actually sending commands by using DTMF tones through the headphone adapter. The audio jack is connected to a DTMF decoder that sends signals to the bot’s Arduino. He wrote client/server code in Java to issue commands to the robot. You can find that code plus a simple schematic on his site. A video of the bot is embedded below.

Continue reading “Forknife, Android G1 Controlled Robot” →

TEMPEST: A Signal Problem

TEMPEST is the covername used by the NSA and other agencies to talk about emissions from computing machinery that can divulge what the equipment is processing. We’ve covered a few projects in the past that specifically intercept EM radiation. TEMPEST for Eliza can transmit via AM using a CRT monitor, and just last Fall a group showed how to monitor USB keyboards remotely. Through the Freedom of Information Act, an interesting article from 1972 has been released. TEMPEST: A Signal Problem (PDF link dead, try Internet Archive version) covers the early history of how this phenomenon was discovered. Uncovered by Bell Labs in WWII, it affected a piece of encryption gear they were supplying to the military. The plaintext could be read over that air and also by monitoring spikes on the powerlines. Their new, heavily shielded and line filtered version of the device was rejected by the military who simply told commanders to monitor a 100 feet around their post to prevent eavesdropping. It’s an interesting read and also covers acoustic monitoring. This is just the US history of TEMPEST though, but from the anecdotes it sounds like their enemies were not just keeping pace but were also better informed.

[via Schneier]

Sound Effects Box

vs

At first glance, this may look like a retro styled monome, but it is actually quite different. Merging a Project64 key pad and a Voice Shield for Arduino, [Spikenzie] has made a sound effects box. Each button triggers a unique sound that is stored in the Voice Shield. Of coarse, it will be like a game of memory trying to remember what sound is where. You can see a demo video here.

Wattcher, Twittering Kill A Watt Plans Posted

kill-a-watt

You probably saw [Phillip Torrone] and [Limor Fried]’s twittering Kill A Watt earlier this week. It was an entry in the Core77/Greener Gadgets Design Competition. We saw a little bit about how it was assembled, but now they’ve posted a full guide to assembling the hardware. Each Kill A Watt gets an XBee radio that transmits back to a receiver that logs the power usage. The difficult part when putting this design together was the XBee required 50mA when transmitting. This is well above the Kill A Watt’s internal power supply. They remedied this by adding a 10,000uF supercap to act as a rechargeable battery. The daily twittering is just a side-effect of the project. The Kill A Watts transmit every 2 seconds, so you’ll get a very accurate report of your power usage. This is a great project for renters who can’t permanently modify their power infrastructure. Each Kill A Watt can support quite a few appliances since they’re rated for 15A, ~1800W.