In the days before semiconductor diodes, transistors, or even vacuum tubes, mechanical means were used for doing many of the same things. But there’s still plenty of fun to be had in using those mechanical means today, as [Manuel] did recently with his relay computer. This post is a walk through some circuits that used those mechanical solutions before the invention of the more electronic and less mechanical means came along.
We aren’t sure this technically qualifies as music synthesis, but what else do you call a computer playing music? In this case, the computer is a Teensy, and the music comes from a common classroom instrument: a plastic recorder. The mistaken “flute” label comes from the original project. The contraption uses solenoids to operate 3D printed “fingers” and an air pump — this is much easier with a recorder since (unlike a flute) it just needs reasonable air pressure to generate sound.
A Teensy 3.2 programmed using the Teensyduino IDE drives the solenoids. The board reads MIDI command sent over USB from a PC and translates them into the commands for this excellent driver board. It connects TIP31C transistors, along with flyback diodes, to the solenoids via a terminal strip.
On the PC, a program called Ableton sends the MIDI messages to the Teensy. MIDI message have three parts: one sets the message type and channel, another sets the velocity, and one sets the pitch. The code here only looks at the pitch.
This is one of those projects that would be a lot harder without a 3D printer. There are other ways to actuate the finger holes, but being able to make an exact-fitting bracket is very useful. Alas, we couldn’t find a video demo. If you know of one, please drop the link in the comments below.
Electromechanical solenoids are pretty cool devices. Move some current through an electromagnet and you can push a load around or pull it. If you’re MIT student [Lining Yao], you can use them to dance. [Lining] built TapBot, a re-configurable set of tap-dancing robots that are both modular and modern. She even rolled her own solenoids.
The one with the eye stalk is the bridge, and it’s connected to a computer over FTDI. The other nodes attach to the bridge and each other with small magnets that are designed to flip around freely to make the connections. These links are just physical, though. The nodes must also be connected with ribbon cables.
Each of the nodes is controlled by an ATtiny45 and has a MOSFET to drive the solenoid at 8-12 V. [Lining] snapped a small coin magnet to the end of each solenoid slug to provide a bigger surface area that acts like a tap shoe. TapBot can be programmed with one of several pre-built tap patterns, and these can be combined to make new sequences. The curtain goes up after the break.
There are other ways to make things dance, like muscle wire. Check out this whiteboard pen that uses nitinol to dance to Duke Nukem.
Simple, elegant, and well executed. This solenoid engine build is everything we’ve come to love about [Matthias Wandel]’s work. If you don’t recognize his name you probably remember the name of his site: Wood Gears.
In what feels like an afternoon project he put together a solenoid engine. It translates the linear motion of a small solenoid into the circular motion of a flywheel. The only specialized part in this hack is the solenoid. It has a pretty long throw and includes a hinge pin at the end.
The rest is crafted mostly of wood — it is admirable how he uses that table saw like a surgeon uses a scalpel. The wooden components include a base, flywheel, very interesting bearing blocks, and a few mounting brackets to hold everything in just the right place. Add to this a coat hanger for the cam shaft, the internals of a terminal strip for the cam, some heavy gauge wire, and you’re in business. The latter two make up a clever electrical switch that synchronizes the drive of the solenoid with the flywheel.
It’s amusing to hear [Matthias] mention that this engine isn’t very practical. We still think the project has merit — it’s great for learning about how simple an engine can be, and for developing an intuitive appreciation for how great commercially available motors and engines actually are. Plus, if you can mimic these fabrication techniques you can build anything. Great work on this one [Matthias], another thing of beauty!
If you ever want to pique a kid’s interest in technology, it is best to bring out something simple, yet cool. There was a time that showing a kid how a crystal radio could pull in a radio station from all the way across town fit the bill. Now, that’s a yawner as the kid probably carries a high-tech cell phone with a formidable radio already. Your latest FPGA project is probably too complicated to grasp, and your Arduino capacitance meter is–no offense–too boring to meet the cool factor criterion.
There’s an old school project usually called an “electromagnetic train” that works well (Ohio State has a good write up about it as a PDF file). You coil some bare copper wire around a tubular form to make a tunnel. Then a AAA battery with some magnets make the train. When you put the train in the tunnel, the magnetic forces propel the train through the tunnel. Well, either that or it shoots it out. If that happens, turn the train around and try again. There’s a few of these in Internet videos and you can see one of them (from [BeardedScienceGuy]) below.
[Ken Rumer] bought a new house. It came with a troublingly complex pool system. It had solar heating. It had gas heating. Electricity was involved somehow. It had timers and gadgets. Sand could be fed into one end and clean water came out the other. There was even a spa thrown into the mix.
Needless to say, within the first few months of owning their very own chemical plant they ran into some near meltdowns. They managed to heat the pool with 250 dollars of gas in a day. They managed to drain the spa entirely into the pool, but thankfully never managed the reverse. [Ken] knew something had to change. It didn’t hurt that it seemed like a fun challenge.
The first step was to tear out as much of the old control system as could be spared. An old synchronous motor timer’s chlorine rusted guts were ripped out. The solar controler was next to be sent to its final resting place. The manual valves were all replaced with fancy new ones.
Rather than risk his fallible human state draining the pool into the downstairs toilet, he’d add a robot’s cold logical gatekeeping in order to protect house and home. It was a simple matter of involving the usual suspects. Raspberry Pi and Arduino Man collaborated on the controls. Import relay boards danced to their commands. A small suite of sensors lent their aid.
Now as the soon-to-be autumn sun sets, the pool begins to cool and the spa begins to heat automatically. The children are put to bed, tired from a fun day at the pool, and [Ken] gets to lounge in his spa; watching the distant twinkling of lights on his backyard industrial complex.
This Raspberry Pi 2 with computer vision and two solenoid “fingers” was getting absurdly high scores on a mobile game as of late 2015, but only recently has [Kristian] finished fleshing the project out with detailed documentation.
Developed for a course in image analysis and computer vision, this project wasn’t really about cheating at a mobile game. It wasn’t even about a robotic interface to a smartphone screen; it was a platform for developing and demonstrating the image analysis theory he was learning, and the computer vision portion is no hack job. OpenCV was used as a foundation for accessing the camera, but none of the built-in filters are used. All of the image analysis is implemented from scratch.
The game is a simple. Humans and zombies move downward in two columns. Zombies (green) should get a screen tap but not humans. The Raspberry Pi camera takes pictures of the smartphone’s screen, to which a HSV filter is applied to filter out everything except green objects (zombies). That alone would be enough to get you some basic results, but not nearly good enough to be truly reliable and repeatable. Therefore, after picking out the green objects comes a whole chain of additional filtering. The details of that are covered on [Kristian]’s blog post, but the final report for the project (PDF) is where the real detail is.
If you’re interested mainly in seeing a machine pound out flawless victories, the video below shows everything running smoothly. The pounding sounds make it seem like the screen is taking a lot of abuse, but [Kristian] mentions that’s actually noise from the solenoids and not a product of them battling the touchscreen. This setup can be easily adapted to test out apps on different models of phones — something that has historically cost quite a bit of dough.
If you’re interested in the nitty-gritty details of the reasons and methods used for the computer vision portions, be sure to go through [Kristian]’s github repository where everything about the project lives (including the aforementioned final report.)