Books You Should Read: Instruments Of Amplification

July 21, 2016 by Steven Dufresne 33 Comments

Psst… Wanna make a canning jar diode? A tennis ball triode? How about a semiconductor transistor? Or do you just enjoy sitting back and following along an interesting narrative of something being made, while picking up a wealth of background, tips and sparking all sorts of ideas? In my case I wanted to make a cuprous oxide semiconductor diode and that lead me to H.P. Friedrichs’ wonderful book Instruments of Amplification. It includes such a huge collection of amplifier knowledge and is a delight to read thanks to a narrative style and frequent hands-on experiments.

My well worn copy of Instruments of Amplifications

DIY point-contact semiconductor transistor

Friedrichs first authored another very popular book, The Voice of the Crystal, about making crystal radios, and wanted to write a second one. For those not familiar with crystal radios, they’re fun to make radios that are powered solely by the incoming radio waves; there are no batteries. But that also means the volume is low.

Readers of that book suggested a good follow-up would be one about amplifier circuits, to amplify the crystal radio’s volume. However, there were already an abundance of such books. Friedrichs realized the best follow-up would be one on how to make the amplifying components from scratch, the “instruments of amplification”. It would be unique and in the made-from-scratch spirit of crystal radios. The book, Instruments of Amplification was born.

The Experiments

Microphonic relays, via H.P. Friedrichs Homepage

The book includes just the right amount of a history, giving background on what an amplifier is and how they first came in the electrical world. Telegraph operators wanted to send signals over greater and greater distances and the solution was to use the mix of electronics and mechanics found in the telegraph relay. This is the springboard for his first project and narrative: the microphonic relay.

The microphonic relay example shown on the right places a speaker facing a microphone; the speaker is the input with the microphone amplifying the output. He uses a carbon microphone salvaged from an old telephone headset, housing everything in an enclosure of copper pipe caps, steel bar stock, nuts and bolts mounted on an elegant looking wood base. All the projects are made with simple parts, with care, and they end up looking great.

Continue reading “Books You Should Read: Instruments Of Amplification” →

MicroPython On The ESP8266: Kicking The Tires

July 21, 2016 by Elliot Williams 32 Comments

Scripting languages are for large computers, right? “Real” embedded device work is a hellish, never-ending cycle of code, compile, and re-flash. Well, I used to think so too, but with the proliferation of scripting and other interactive languages to microcontrollers over the last few years, the hurdle to interactive development on the small chips has gotten a lot lower.

On the ESP8266 platform, I’ve tried out NodeMCU’s Lua and ESP8266 BASIC. (For the last half-year, I’ve been using the awesome Mecrisp-Stellaris almost exclusively on the STM32F1xx and F4xx chips, but haven’t dipped into ESP8266 Forth yet.)

NodeMCU is great because it’s got everything you could want built in, and through cloud services it’s easy to get a tailored build made that maximizes free flash memory for your projects. I just don’t dig the asynchronous Lua thing (you might, try it!). ESP BASIC has a different set of libraries, and is missing MQTT for my purposes. Still it’s pretty slick, and worth a look.

So when the MicroPython folks announced that they were releasing the binary builds for the ESP, I thought it was time to give it a spin. I’ve used Python for nearly twelve years now, so it’s like a comfortable shoe for me. Would MicroPython be the same on the ESP8266? The short answer is yes and no.

Continue reading “MicroPython On The ESP8266: Kicking The Tires” →

Retrotechtacular: The Incredibly Difficult Task Of Copying A Document

July 20, 2016 by Al Williams 57 Comments

It seems hard to imagine, but in the early part of the 20th century, there weren’t a lot of great options for creating copies of documents. The most common method was to use carbon paper to create multiple copies at once from a typewriter or a line printer. All that changed with a company called Haloid. Never heard of them? They later became the Xerox company.

The underlying technology dates back to 1938 (invented by a physicist who was also a lawyer). In 1944, they produced a practical copier and shortly thereafter sold the rights to Haloid. The Haloid company originally made photographic copy machines that used wet chemistry.

In 1959, the Xerox 914 (so called because it could copy a 9″ x 14″ document) came on the scene (that’s it, below). The 650 pound copier could make seven copies per minute and came with a fire extinguisher because it had a tendency to burst into flames. If you didn’t want to spend the $27,500 price tag, you could rent for only $25/month (keep in mind that in 1959, $25 would buy about 25 pounds of T-bone steaks). You can see a commercial for the 914 in the video below.

In the commercial, you’ll see them make a big deal out of the fact that the print was dry. That’s because a lot of previous machines used actual photographic processes with wet chemistry. Obviously, that also took special paper.

Even Further Back

If the copier didn’t exist until recently, how did people make copies before? Turns out there were lots of ways to make copies of varying degrees of bad quality or extreme trouble. In some sense, the best copies were made by scribes just writing down a second copy of things. There were a variety of machines that would capture what you wrote and make a copy by mechanical or other means. A polygraph (not the lie detecting kind) allowed Thomas Jefferson to write letters and make a copy. The machine moved a pen to match the movements of the author’s pen, thus making a near perfect copy. With a few adjustments, this became the pantograph which not only does the same job, but also can shrink or enlarge the copy. Carbon paper was widely used to make multiple copies of handwritten and typewritten documents.

Continue reading “Retrotechtacular: The Incredibly Difficult Task Of Copying A Document” →

What Could Go Wrong? I2C Edition

July 19, 2016 by Elliot Williams 53 Comments

I should really like I2C more than I do. In principle, it’s a brilliant protocol, and in comparison to asynchronous serial and SPI, it’s very well defined and clearly standardized. On paper, up to 127 devices can be connected together using just two wires (and ground). There’s an allowance for multiple clock-masters on the same bus, and a way for slaves to signal that the master needs to wait. It sounds perfect.

In reality, the tradeoff for using only two wires is a significantly complicated signalling and addressing system that brings both pitfalls and opportunities for debugging. Although I2C does reduce the number of signal wires you need, it gets dangerous when you have more than a handful of devices on the same pair of wires, and you’re lucky when they all conform to the same standard. I’ve never seen twenty devices on a bus, much less 127.

But still, I2C has its place. I2C was designed to connect up a bunch of slower, cheaper devices without using a lot of copper real estate compared to its closest rival protocol: SPI. If you need to connect a few cheap temperature sensors to a microcontroller (and their bus addresses don’t clash) I2C is a great choice. So here’s a guide to making it work when it’s not working.

Continue reading “What Could Go Wrong? I2C Edition” →

Hackerspaces Are Hard: Insurance

July 19, 2016 by Kristina Panos 48 Comments

Do you dream of opening a hackerspace, makerspace, or co-working space? Maybe it’s in the works and you’re already scoping out locations, intoxicated by visions of all the projects that will emerge from it. Here’s a sobering thought: makerspaces are a great big pile of risk. If the doors of your ‘space are already open, perhaps you’ve come to realize that the initial insurance policy you signed doesn’t really fit the needs of your particular creative paradise. Even if it does, the protection you need will change as you acquire new toys.

So why should you even get insurance? For one thing, your landlord will probably require it. If you own the building, you should insure it to protect yourself and anyone who uses the space. Do it for the same reason you’d insure a car, your house, or your collection of vintage pinball machines: to mitigate risk. It takes a lot of hard work to open a makerspace, perform the day-to-day operations, and keep it growing and getting better. Whenever the unthinkable happens, insurance will protect your investment as well as the people who make it a great place to be.

In researching this article, I contacted several well-established makerspaces in the United States as well as most of the major insurance providers to get both sides of the story. My intent was not to make a how-to guide, but to simply explore the topic and provide a view of the process and the struggle.

Continue reading “Hackerspaces Are Hard: Insurance” →

Sonic 3D Printer Auto Bed Leveling Makes A Swoosh

July 18, 2016 by Moritz Walter 49 Comments

3D Printering: the final frontier. These are the voyages of another 3D printer hack. Its mission: to explore strange new ways of leveling a print bed.

So far, we’ve had servo probes, Allen key probes, Z-sled probes, inductive and capacitive contactless switches, just to name a few. All of them allow a 3D printer to probe its print bed, calculate a correction plane or mesh, and compensate for its own inherent, time variant, inaccuracies.

Continue reading “Sonic 3D Printer Auto Bed Leveling Makes A Swoosh” →