We all know that the little black globs on electronics has a semiconductor of some sort hiding beneath, but the process is one that’s not really explored much in the home shop. The basic story being that, for various reasons , there is no cheaper way to get a chip on a board than to use the aptly named chip-on-board or COB process. Without the expense of encapsulating the raw chunk of etched and plated silicon, the semiconductor retailer can sell the chip for pennies. It’s also a great way to accept delivery of custom silicon or place a grouping of chips closely together while maintaining a cheap, reliable, and low-profile package.
As SparkFun reveals, the story begins with a tray of silicon wafers. A person epoxies the wafer with some conductive glue to its place on the board. Surprisingly, alignment isn’t critical. The epoxy dries and then the circuit board is taken to a, “semi-automatic thermosonic wire bonding machine,” and slotted into a fixture at its base. The awesomely named machine needs the operator to find the center of the first two pads to be bonded with wire. Using this information it quickly bonds the pads on the silicon wafer to the board — a process you’ll find satisfying in the clip below.
The final step is to place the familiar black blob of epoxy over the assembly and bake the board at the temperature the recipe in the datasheet demands. It’s a common manufacturing process that saves more money than coloring a multimeter anything other than yellow.
In the show Full Metal Alchemist, there’s a city called Rush Valley whose main and only business are the high performance prostheses called Automail. Engineers roam the street in Rush Valley; the best have their own shop like that of the high-end clothiers in Saville Row. Of course; it’s all fantasy set in a slightly ridiculous Japanese cartoon, but while walking through this year’s Maker Faire I began to wonder if is a future that may come to be.
The problem with prosthetics is the sheer variety of injuries, body types, and solutions needed. If an injury is an inch higher or an inch lower it can have a big effect on how a prosthetic will interact with the limb. If the skin is damaged or the nerves no longer function a different type of prosthesis will be needed. Some prostheses are to replace a lost limb, others are to assist an ailing body in order to return it to normal function. More than a few are simply temporary aides to help the body along in its healing efforts. Unfortunately, this means that it’s often the case that larger companies only sell the prostheses people are most likely to need; the rarer cases are often left without a solution.
However, we see hackers stepping up and not just working on the problems, but solving them. One of our semifinalists last year, openbionics, inspired one of the projects we’ll be talking about later. There are robotic legs. We met a guy at MRRF who has been 3D printing hands for his son from the E-nable project.
Along these lines, we saw two really cool projects at Maker Faire this year: The first is the Motor-Assistive Glove, or MAG. MAG is designed to help people with Peripheral Neropathy regain some use of their hands while they go through the lengthy road to recovery. Perhipheral Neuropathy is a disease, usually resulting from diabetes, toxin exposure, or infection, where the nerves are damaged in such a way that typically the hands and feet are no longer mobile or feel sensation in a useful way. Once the disease is in full swing, a previously able person will find themselves unable to do simple things like hold a can of soda or grasp a doorknob firmly enough to open it.
We had a chance to interview one of the members of the MAG team, [Victor Ardulov], which you can see in the following video. [Victor] and his group started a research project at the University of Santa Cruz to develop the Motor-Assistive Glove. The concept behind it is simple. People with Peripheral Neuropathy typically have some movement in their hands, but no strength. The MAG has some pressure sensors at the tips of the fingers. When the user puts pressure on the pad; the glove closes that finger. When the pressure is off; the glove opens. The concept is simple, but the path to something usable is a long one.
My heyday in programming was about five years ago, and I’ve really let my skills fade. I started finding myself making excuses for my lack of ability. I’d tackle harder ways to work around problems just so I wouldn’t have to code. Worst of all, I’d find myself shelving projects because I no longer enjoyed coding enough to do that portion. So I decided to put in the time and get back up to speed.
Normally, I’d get back into programming out of necessity. I’d go on a coding binge, read a lot of documentation, and cut and paste a lot of code. It works, but I’d end up with a really mixed understanding of what I did to get the working code. This time I wanted to structure my learning so I’d end up with a more, well, structured understanding.
However, there’s a problem. Programming books are universally boring. I own a really big pile of them, and that’s after I gave a bunch away. It’s not really the fault of the writer; it’s an awkward subject to teach. It usually starts off by torturing the reader with a chapter or two of painfully basic concepts with just enough arcana sprinkled in to massage a migraine into existence. Typically they also like to mention that the arcana will be demystified in another chapter. The next step is to make you play typist and transcribe a big block of code with new and interesting bits into an editor and run it. Presumably, the act of typing along leaves the reader with such a burning curiosity that the next seventeen pages of dry monologue about the thirteen lines of code are transformed into riveting prose within the reader’s mind. Maybe a structured understanding just isn’t worth it.
I wanted to find a new way to study programming. One where I could interact with the example code as I typed it. I wanted to end up with a full understanding before I pressed that run button for the first time, not after.
When I first read about literate programming, my very first instinct said: “nope, not doing that.” Donald Knuth, who is no small name in computing, proposes a new way of doing things in his Literate Programming. Rather than writing the code in the order the compiler likes to see it, write the code in the order you’d like to think about it along with a constant narrative about your thoughts while you’re developing it. The method by which he’d like people to achieve this feat is with the extensive use of macros. So, for example, a literate program would start with a section like this:
KiCAD has been making leaps and bounds recently, especially since CERN is using it almost exclusively. However, while many things are the same, just enough of them are different from our regular CAD packages that it’s hard to get started in the new suite.
[Chris Gammell] runs Contextual Electronics, an online apprenticeship program which goes from concept to assembled electronics covering everything in between. To take the course you pay a nominal fee, but [Chris] posted a very excellent ten-part video series made during the last run of classes which you can watch without charge. The videos go through the basics of KiCAD while hitting the major points to consider when designing and manufacturing your electronics.
The project [Chris] chose is a simple circuit that blinks an LED with a 555. The first videos cover navigating KiCAD’s component schematic editor and library system. Next comes creating circuit schematics and component footprint creation. [Chris] covers PCB layout, the generation of Gerber files, and finally ordering the design from OSH Park — the purveyors of purple boards we’ve come to know and love. The series finishes up with simulating the circuit in LTSpice, ordering the parts, and finally soldering and debugging of the board. If all goes correctly you should now have a single blinking LED.
If the bright summer sun is burning your delicate skin, and you’d rather be locked inside with solder fumes, add this to your watch list now!
[This Old Tony] teaches us how to make springs on a lathein this video done in the style of How It’s Made. Mixed in with snark, in his usual style, is a lot of useful information.
The Machinery’s Handbook certainly has all the information one would need to design the basic spring shapes, but it’s not always necessary. [Tony] points out that cheating is entirely acceptable. For example, if you need a spring that’s close to the dimensions of a standard spring, simply copy over the values from the standard spring. He explains all the terminology needed to decrypt the pages in your engineering tome of choice.
He shows the basics of winding a spring on a mandrel (or that round metal thing, if you want to use the industry term). First wind the inactive coils, then set your lathe to the desired spring pitch. Engage it as if threading, then disengage and wind the final inactive coils. A quick trip to the sander squares the ends of a standard coil spring. However, the tools can also be used to make torsion springs, or even exotic combination springs.
For a good… educational laugh, watch the whole video after the break.
This robot may have the fastest hand we’ve ever seen. It’s only a hand at the moment, but it’s certainly good with it.
The hand comes from a research project out of the University of Washington. The researchers didn’t just want to program the robot to do tricks, they wanted it to learn. Some tasks are just by nature too complex and tedious to program all the details for. Look at all those tendon activators. You want to program that?
The current focus of the robot is twirling a stick. While they’re probably a ways away from a robot cheerleading squad or robot drum major, the task itself is extremely difficult. This can be proven by just how many YouTube videos there are on the art of pencil twirling.
While the video didn’t show the robot dramatically twirling the stick at high speed, it did show the robot rotating it a little bit without dropping it. And this is a behavior that it has learned. For anyone who has ever had a run-in with robotics, or the art of convincing a robot not to discard all the data it collects in order to not run directly into a wall, this is a pretty big achievement. Video after the break.
A class in Brazil was given the assignment to make a board game. [Marcelo], presumably, heard his son lamenting how lame it was going to be if the board was just cardboard with some drawings on, and came to the rescue.
Working with the class, they came up with the rules of the game. We’re not certain what those are, but it involves a regular game board, a flashing light circle with numbers, and a fusion between Operation and one of those disease transmitters commonly found at the doctor’s office. You can try to puzzle them out from the video after the break.
The brains of the board is an Arduino with an external EEPROM for all the sound effects and other data needed for this construction. Everything is laid out on a beautifully done home etched PCB. It’s too bad the other side of the board isn’t visible.
We’re sure the kids learned a lot working with [Marcelo]. It would have been nice if a traveling wizard came to some of our earlier classes in school and showed us just how much cool stuff you can do if you know electronics.