Then I chose a few specifics: at TIP120 transistor, a 1000uF capacitor, a 1N4004 diode, and a 5V solenoid from Sparkfun. …and did 19 iterations of the circuit; one per chime in the glockenspiel.
I’ve done a quick Fritzing circuit diagram, which I plan to upload to GitHub.
My main concern was whether the solenoids could be powered only by the VIn pin on the Arduino when powered via a 9V 650mA wall power supply. Turns out the answer seems to be “Yes”: the 1000uF capacitor prevents the solenoid from drawing down the main power enough to reset the Arduino, and the power consumption of the solenoids (see below) is easily supported by the power supply.
To avoid burning out the solenoids each one is powered only a few milliseconds at a time. This causes the solenoid to hit the chime with just enough power to ring nicely, but not too loudly. The math’s pretty straightforward: the data sheet provides the maximum average wattage that the solenoid can dissipate and the minimum resistance of the solenoid. The power supply puts out about 9V. Working out the numbers, it looks like for quickly-paced music, a 6ms-per-strike is about the maximum the solenoid should support (conservatively). Playing most music, this shouldn’t be anywhere near the maximum power the solenoid can support.
When I described my robotic glockenspiel project, a co-worker pointed me to the musical performances of Pat Metheny, which led me to LEMUR (League of Electronic Musical Robots), which made his instruments.
Check out the videos on LEMUR’s site (scroll down to the thumbnails). Some of them remind me of early 20th-century experimental music (especially the one with the siren). Love it!
This is my second try at making the frame for the chimes. You can read about the Epic Fail first attempt in my earlier post. The trick was figuring out how to make a wooden frame precisely-aligned enough that the chimes fit.
Here’s my tale of this second, successful attempt, phrased as “How to build a glockenspiel frame”
Suppose your glockenspiel will have 19 chimes (like mine) spaced 1″ apart, with a 1″ space at the top and bottom, then a 1.5″ piece of wood at the top and bottom, giving a total height of 24″.
Start by screwing together a 24″ square frame from overlapping pieces, where the sides are just for lining up marks; the top and bottom pieces will remain. Add a small triangle at each corner, to keep the frame square. Add a center piece of wood whose side (not center) marks the center of the frame. Later you will use this piece to line up the center marks of all the chimes.
Next, mark evenly-spaced 1″ marks that – when transferred to the angled parts of the frame – will show where each pipe goes. (I later found I should have marked 1/2″ spaces as well.)
Next you’ll add the angled parts of the frame:
on the longest pipe and the shortest pipe, measure the distance from the pipe center to the pipe node (one of the holes)
Mark the longest pipe distance on the top piece of the frame, and the shortest pipe distance on the bottom piece. It’s a little more complex than that, but you get the idea: place the pieces so that all the pegs will fit on them.
Mark the centerline of two 1.5″ wide pieces of wood.
Line up the centers of the two pieces of wood with the marks on the top and bottom pieces. Mark where the two pieces of wood extend past the top and bottom parts.
Cut off the extended parts of those pieces of wood, then replace them on their marks.
Glue and clamp the two pieces of wood to the top and bottom parts of the frame, making sure they are still aligned with their marks.
While the glue is drying, use the 1″-spaced marks on the side pieces to mark 1″-spaced marks on the two pieces that you’re gluing. Then similarly mark 1/2″ marks (ok, I should have originally marked 1/2″ marks on the side pieces). These 1/2″ marks will line up with the holes in each chime.
The result should look a lot like the photo below:
Once the glue is dry, unscrew the outer parts of the original frame, and cut the over-long remaining pieces, leaving you with what will be the final frame, with an extra piece running down the middle.
Next comes the tricky part: drilling the holes for the pegs that will hold each chime. The pegs need to fit precisely into the holes of the chimes so that the chimes will wiggle. Since the chime holes are 3/16″ and the pegs are 1/8″, there isn’t a lot of room for error. This is the point I messed up in the first attempt at a frame.
To make sure the pegs are lined up, here’s how to add the peg holes for one chime:
place the chime so that its holes are aligned with the 1/2″ centerline on the frame, and so that the lengthwise center of the chime is aligned with the long center piece running down the middle of the frame.
Hold the chime tightly in place while you use a drill with a 3/16″ bit to drill a shallow pilot hole for the left peg of the chime. Don’t drill the right side hole yet. Instead of drilling, you could use a very thin pencil to mark where the left hole will go.
Using a drill press (I have something like a Microlux micro drill press) with a 1/8″ bit, drill the left peg hole.
Cut a 1.5″ piece of 1/8″ dowel; this is one peg. Insert this peg into the hole (but not all the way yet – you want to be able to pull the peg out soon).
Place the chime on the left peg, and line up the right hole of the chime with the 1/2″ line. Center the left hole on the left peg, so there’s wiggle room.
Mark the right hole in the same way you did the left (with a hand drill or pencil).
Drill the right peg hole and insert a second peg.
Place the chime on the left and right pegs. Double check that it is still a little loose. If not, you have to putty up the right hole and try again (luckily I didn’t have to do this).
Remove the pegs and chime, and go on to the next chime.
Now unscrew and remove that center piece. You don’t need it now that you’ve drilled all the peg holes.
Meanwhile, it’s time to cut the felt pads that will surround each peg. These pads keep the chimes from rattling on the wood.
I recently made a rash Tweet saying that if you don’t have SSL (Secure Sockets Layer; what HTTPS uses) your WordPress site will be hacked. That’s an overstatement. I’ve known people who’ve run WP sites without SSL with no problems.
So here’s a little web SSL orientation for people who have better things to do than learn the details of computer security.
First, some people think that you need SSL on your web site/service only if you’re doing things you want to hide, or if you’re doing financial transactions.
My opinion is that your web needs SSL for anything that involves posting or login. As plenty of people have pointed out, if you as a web client don’t use SSL when you post or login to a site, an attacker – an eavesdropper – can easily post or login to that site as you. So if you don’t have SSL, you can’t trust that the poster or login isn’t somebody whose life goal is to sell counterfeit shoes, inflate the Google ratings of their bogus web site, or worse.
Another benefit of SSL is that it gives your web clients better assurance that when they go you your site, say “https://needhamia.com”, they are talking to the real site and not some imposter site (who wants to sell shoes, etc.)
SSL can involve a bit of sticker-shock on the scale of buying web hosting in the first place, so think about the costs to you and your users of your site getting hacked or their accounts or data being stolen. If your site and data need to be safe, you’ll probably choose to bite the bullet and pay the money necessary to make your site secure. (I know, I know, it sounds like a racket doesn’t it?)
SSL also involves a lot of lingo. Thankfully, you don’t have to understand the details of the meaning of the words or how SSL/HTTPS works to use it.
So here’s my recommended sequence of things you need to do to support SSL. I’ve left off the details because I just want to give you an orientation rather than a tutorial.
Get a web host that supports SSL. Most do, but a surprising number don’t. If you’re building your own web host from scratch, I expect you’ll be able to setup SSL.
Buy a domain name. For example, my domain name is Needhamia.com. It will cost you a small amount per year. This name is necessary for SSL registration. Some web hosts support only domain names that they sell, vs. domain names sold by other domain name registration services.
Once you have your domain name, connect it to your web site. If you bought your domain name from your web hosting service, they can help you do this. It’s not complex.
Once you have connected your domain name to your site, order an SSL certificate. It can cost you a surprisingly large amount per year – but think about the costs to you of not having it: suppose somebody hacks your site or impersonates a user. There are several kinds of cerfiticates. Again, some web hosts support only SSL certificates that they sell vs. certificates sold by others or ‘signed’ by yourself. Filling out the paperwork can seem daunting, but it’s not so bad for the simpler types of certificates.
“self-signed”. These certificates are the simplest/cheapest because you can make one yourself. It gives your web clients the security they need to keep from being eavesdropped. It doesn’t give them any assurance that your site is real – but that’s ok in some applications.
“standard” certificates. These are often the least expensive certificates a web host will sell. They’re probably fine if your site doesn’t deal with money directly. This is the level certificate I’m using on Needhamia.com.
Fancy certificates. These are more about what kind of logos various browsers will show for your site, and how much assurance the certificate gives web clients that your site is who it says and you are who you say you are. Useful if you’re selling stuff.
Once you have your SSL certificate, install it on your web site. Your web hosting company can make this easy for you, especially if you bought the certificate from them.
Ta Da! Now https://yourdomainname uses SSL!
To make your browser-based clients safer, it’s a good idea to make your web site “redirect” http to https. That is, if they type “http://yourdomainname” their browser automatically goes to “https://yourdomainname” instead. I found it hard to find the instructions I needed for this step, but a little searching turned it up.
To sum up: you need to, in this order, get a site, get a domain name for it, get an SSL certificate for that domain, install the SSL certificate on your site, and (optionally) redirect http to https.
In an earlier post I tuned the chimes. In this post, I find one way not to make a frame for those chimes.
I created the frame for the glockenspiel, with a square frame on the outside so that I could mark the inner part of the frame with 1″ lines, one per chime.
I then aligned each chime in turn with the lines and with the centerline of the frame – the place where the solenoid will strike the chime.
I then drilled a pair of shallow marker holes for each aligned pipe. I could have instead marked the holes by slipping a thin pencil through the chime holes – but I didn’t have such a pencil, so the handy hand drill sufficed.
I then drilled smaller holes centered in the marker holes, and glued a short dowel in each hole.
Then I made the big mistake: I unscrewed the frame so that I could glue it back together – replacing the screws with glue.
Although I was careful to glue the frame pieces along marker lines I’d made when it had been screwed together, the long sides of the frame slipped enough that the dowels no longer aligned with the holes in the chimes.
You can see in the photo below that, for example, the “D” chime hole is nearly 1/4″ away from the peg above it, that it should have been able to rest on. This offset is true for almost all the chimes, indicating that the long parts of the frame shifted between the time I drilled the dowel holes and the time I tried to drop the chimes onto the dowels in those holes.
So, my plan now is to make another frame, and to glue the frame together before I mark and drill the dowel holes (duh) that the chimes will fit over. If at first you don’t succeed, find the root cause of the problem and correct it :-)
My next post has the details of the working frame for the chimes.
Imagine my surprise, after working on my robotic glockenspiel for weeks, when I opened the Signals Catalog, and page two revealed Chimes of the Seasons Music Box, $90. The product has since been discontinued, but it was fun to see it in the catalog.
I knew the project was far from unique, but hadn’t seen such a thing in stores for years – cool that returned to the zeitgeist.
After a few weeks of experimentation, I think I can now write sensible notes on how to cut and tune the chimes for a glockenspiel (metal xylophone) out of metal conduit. This is the first step of my Robotic Glockenspiel project, which I hope to end with a network-connected, Arduino-controlled set of chimes that can play Christmas carols.
I’ve successfully assembled my second soldering kit: The Velleman MK130 ‘3D’ Christmas Tree. It’s a set of blinking LEDs that sit atop a 9V battery… or you can add some long wires and hang it as a Christmas ornament.
At any rate, it was good practice for soldering, and the result is kinda cute. See my YouTube Video of the Kit for the whole experience.
Since I’ve been doing Arduino work, I’ve accumulated a few board and Shield kits that I need to put together. I haven’t soldered since college, so I decided to brush up on my rusty skills by buying one of those little electronics project kits: a Velleman MK102 Flashing LEDs kit.
The front of the board doesn’t look too bad; only a few parts pulled away from the board a bit:
The back is the real giveaway that I’m a newbie: most of the soldering looks pretty good, but I see a couple cold solder joints, a couple dirty solders, and one pair of soldered points that are a bit too close for comfort – fortunately they didn’t short out.
Not bad for a first effort, and on par with the handiwork on many cheap electronic gizmos you might buy. Next I’m planning to solder one of those little Flashing LED Christmas Trees, which has many more components. Then I think I’ll be ready to have a go at one of the Arduino board kits!
Comment Spam is the bane of blogs: fake comments that are nothing more than links to sites offering high-fashion shoes, purses, and porn (curious set, no?)
I’d love to accept real comments from anyone who is not anonymous, but unfortunately Spam Comment robots happily provide fake identities. So I’ve had to restrict comments to people who have created an account on my site.
…but even that doesn’t take care of the problem. As this WordPress FAQ explains, the WordPress comment settings affect only future posts; existing posts are still targets for spam.
So now I’ve set up comments to work only for people who have accounts on this site, and have turned off comments for all my old posts.
Hopefully my new posts will welcome your comments, as long as you create an account with me. Sorry for the trouble; blame the Comment Spammers.
Et proiectus est talpa – "and the mole was cast out"