Dorkbot DC March Meeting

Tuesday, 25 March 2008
7 PM – 9 PM (ET)
Smith Hall of Art, Room 114
George Washington University
801 22nd St NW
Washington, DC 20037

Tom Lee : Cheaper Arduino Wifi

Lady Ada's XPort-based Arduino shield.Bringing ethernet connectivity to the Arduino for around fifty dollars, Lady Ada’s XPort Shield has gotten people understandably excited. But with a little elbow grease and a custom firmware, you can do even better: a $10 component can bring Ethernet, wifi and a full Linux environment to your microcontroller project. Not bad, right? Tom Lee will explain how, and show a simple Arduino-based ambient display that uses the approach to show Metro schedule information.

Tom Lee is a DC web developer and technologist who contributes to DCist, Techdirt and whatever other blogs will have him.

Gareth Branwyn : Jack Parsons: The Original Burning Man

Photo of Jack Parsons with a solid-fuel engine prototype.

Gareth will present a “Maker Profile” on under- appreciated American rocketry pioneer Jack Parsons, based on “Darkside Rocketeer,” his piece on Parsons running in MAKE Volume 13.

Jack Parsons is one of the most important figures in the history of American rocketry and space development. He invented the JATO (jet-assisted take-off) motor– America’s first rocket program, co-founded the Jet Propulsion Laborartory and Aerotech Corporation, and created the formulations for solid rocket motors still in use today. Unfortunately, Parsons’ controversial private life — as a practitioner of ceremonial magick, a follower of infamous British occultist Aleister Crowley, and as a devout hedonist — has caused many of his technical achievements to be shoved into the closet of history. Parsons’ untimely death in a mysterious home lab explosion, has only added to the sordid nature of his story.

Gareth will talk not only of Parsons, but the group of fellow amateurs and CalTech students he worked with, known as The Suicide Squad, and the amazing intellectual backdrop of Pasadena and CalTech in the 1920s and ’30s.

Gareth Branwyn is a writer on technology and fringe culture. He is a contributing editor to MAKE, writes for the Make: Blog, and is an editor for O’Reilly’s Make: Books imprint.

Welcome to Dorkbot DC!

Rules for Roboticists

In honor of Robot Day on Make: Blog, I’ve posted my “Rules for Roboticists” from my 2004 book Absolute Beginner’s Guide to Building. It’s a playful list of operating principles, rules of thumb, and words o’ wisdom about bot building. The piece is accompanied by robot scientist “trading cards” illustrated by Mark Frauenfelder for the book.


The Rules for Roboticists

[This piece originally appeared in The Absolute Beginner’s Guide to Building Robots]

Remember The Rules, that icky book written by those two insufferable women who nobody would want to date regardless of what relationship principles were or were not being applied? Well, I decided to dream up some rules of my own. No, they’re not things like “Never call a robot after the final assembly. Make it call you.” Or: “The way to a robot’s stomach is through its rear access panel.”  These “rules” represent the collective working wisdom of builders who’ve been bolting together bots for decades. The cyberneticist Gregory Bateson used to say: “Always tie your ideas with slipknots.” So these are not hard and fast rules, more like rules of thumb. Just a few things to consider as you build robots.

1. A roboticist is a generalist, a systems thinker.
One of the things that attracts a lot of people (me, for one) to robotics is that it involves the orchestration of many different disciplines. There are, obviously, specialists in the field — those who work only on AI control architectures, or robot locomotion, or whatever — but even they must keep the entire machine in mind. Most people who work in the field, and certainly all amateurs, have to have at least basic skills in numerous disciplines. As you get more into robotics, you’ll also find yourself spending a lot of time looking at humans and animals trying to figure out how they work. Oddly, trying to construct machine “creatures” gives one an even greater appreciation for the heavenly designs of nature, which brings us to…

2. A roboticist is a “deconstructionist”
As a robot builder, you’ll find yourself obsessively looking at the natural and built worlds and going: “Ah-ha! So that’s how it’s done.” Nothing will be safe as you take apart toys and machines that don’t work anymore (and some that still do), and find yourself playing with your food in a manner unsettling to others (“Cool, there’s the ligament attachments!”). But, for the love of all that’s civilized, leave the family pets alone!

Rumor has it that BEAM (and Wow Wee Toys) robot inventor Mark Tilden has been known to put all manner of bio-matter (chicken and other animal bones and bits) into his dishwasher so that he can clean them thoroughly for study of their mechanics, and one might even assume, incorporation into disturbing SRL-esque bio-mechs.

3. A roboticist knows how to K.I.S.S. it.
Actually not every robot builder knows this, but they should. K.I.S.S. stands for “Keep It  Simple, Stupid” and it’s a maxim recited (but frequently unheeded) in many design disciplines. Heed it in your robot building. Take time to plan your projects. Don’t just throw technology at a problem ‘cause you can. Use prototyping tech such as LEGO MINDSTORMS, VEX, and breadboarding to test out designs. Then try and figure out what you might not need and toss it. The simpler and more elegant your designs, the more likely your robot is to be stable and robust.

4. A roboticist must learn to think “outside the bot.”
Innovation comes from thinking differently, heading down the road less traveled. Don’t be afraid to take chances, to go in radical directions. Apply what I call Rodney Brooks’ Research Heuristic. Here’s how this works: In his book Flesh and Machines, Brooks reveals how he came upon many of his radical ideas regarding robots and AI: He would figure out what was so obvious to all of the other researchers that it wasn’t even on their radar, and then he’d put it on his. Essentially, Brooks would look at how everyone else was tackling a given problem, and what assumptions were so implicit to them that these assumptions were no longer being questioned. And he would question them. Don’t listen when people tell you that you can’t do something. Ignore your critics.

This is completely unrelated to robots, but it neatly illustrates our fourth rule. Many years ago, a friend of mine, a fabric artist, entered a beginner’s fabric weaving contest. She rented a small loom, learned how to weave, and decided to weave a seersucker blouse. Because she was new to weaving, she didn’t know that you “couldn’t” hand-weave seersucker (which is comprised of alternating puckered and smooth stripes). She had a devil of a time doing it, but she thought it was just because she was new to weaving. The judges were stunned. Needless to say, she won the contest, and the grand prize, a gorgeous room-sized Swedish loom that was the size of a small sailing vessel.

5. A roboticist is as much an artist as a scientist.
Find someone who’s done anything truly cutting-edge in science and technology, and chances are, he or she has a bit of an artist’s/poet’s soul. Independent engineer and self-proclaimed “high-tech nomad” Steven Roberts is often quoted as saying, “Art without engineering is dreaming. Engineering without art is calculating.”

6. A roboticist must be methodical and patient (like any scientist).

The pressure that many robot developers are under to deliver creations that live up to sci-fi-like expectations leads too many to attempt too much, too soon. Scientific development is measured, by its nature. Don’t be afraid to get one thing right rather than a bunch of things “sorta okay.” (Notice how we just contradicted rule number 4. What can we say? Rules are … well for those two ladies who wrote that book.)

7. A roboticist knows that neatness counts.

After you’ve built a few robots, you’ll quickly learn that the mechanics and (especially) the electronics can quickly become complicated, even in simple machines. There are usually wires sprouting everywhere, and trying to fit all of the parts inside your robot body, or on your robot platform, can become quite a challenge. You’ll learn that keeping everything neat and tidy will make a huge difference in the end. Use quick connectors when you can (for plugging and unplugging wires), use cable ties to bundle related wires together, and carefully plan (or revise) your design to maximize order and quick deconstruction/reconstruction of subsystems for easier troubleshooting. Color-code.

8. A roboticist must be a master of many trades.
As stated in rule number 1, a roboticist must be able to look at the big picture and know at least a little about a lot. He or she must have a working knowledge of materials sciences, structural and mechanical engineering, electrical engineering, and computer sciences. This may all sound intimidating to an absolute beginner, but knowing something about all of these areas of technology and science can actually be fun and exciting. And don’t let the big words trip you up. In plain English, these boil down to: building stuff (and knowing the right stuff to use), doing basic electronics, and knowing the ins and outs of microcontrollers and their software.

9. A roboticist should know his or her tools, materials, and processes.
You can have all the fancy “book learnin’” in the world, but if you don’t have a good working knowledge of robot building tools, building materials, and real-world construction techniques, you’re not going to be seeing robots scooting around your den anytime soon. The more you tinker, experiment, the more mad skills you’ll acquire — which leads us to…

10. A roboticist knows that you need to build early and build often.
Modern robot building technologies such as LEGO MINDSTORMS, VEX, iRobot’s iCreate, open source microcontrollers, prototyping boards, and other similar innovations (not to mention computer designing, simulation, and programming software) allow robot builders a tremendous amount of freedom to experiment and build on demand. Think of pre-PC writing tech (pens and paper, typewriters) versus a word processor (complete with spell- and grammar-checking, a built-in dictionary, Thesaurus, and so forth) and that gives you some idea of today’s robot tools versus those of a decade ago, even five years ago. Now you can have an idea for a new drive or sensor system, whatever, and have it built and tested within a few hours. If it doesn’t work, you can quickly disassemble and assemble something else. From this rapid prototyping can come truly innovative robot designs.

11. A roboticist should know when to come back later (A.K.A. “The Kenny Rogers Rule”)

When you’re building anything, especially something as complicated as a robot, the build can sometimes get ugly. If you try to force your way through, you can often dig yourself into an even deeper hole. So here’s what you do: “Put the soldering iron down. Step away from the steaming robot entrails!” You’ll be amazed at what an hour away, vegging in front of the TV, rolling around on the floor with the cat, or sleeping on your problem will do. It almost never fails. Here’s a corollary: The extent to which you don’t want to drop what you’re doing and take a break (“I know I can fix this, damn it!”), is inversely proportional to the extent to which you need a break. Why is it the Kenny Rogers Rule? Cause “you got to know when to hold, know when to fold ’em, know when to walk away…”

[“Heroes of the Robolution” trading card illos by Mark Frauenfelder, from Absolute Beginner’s Guide to Building Robots]

Other Robot Projects on Street Tech

Dorkbot DC Tommorow Night! (2/26/08)

Next Meeting:
Tuesday 26 February 2008
7 PM – 9 PM (ET)

Smith Hall of Art, Room 114
George Washington University
801 22nd St NW
Washington, DC 20037

Exploded view of the MESSENGER spacecraft.Katie Bechtold : The MESSENGER Project
Katie, a spacecraft flight software developer and controller, will discuss MESSENGER, the first mission to visit Mercury in over 30 years. Now on its way to orbit Mercury starting in 2011, it flew close by the planet last month, offering some tantalizing images. Along with the scientific goals of the mission and an overview of the probe’s onboard sensors, Katie will present a few of the engineering challenges in exploring the innermost planet of our solar system.

Photo of Justin Sabe showing an onlooker his hacked toy accordion. Justin Sabe : MIDI Control — How to make expressive digital instruments
Justin broke all his toys as a kid and has spent the rest of his life putting them back together in new and interesting ways. He has toured playing keytar with the goth industrial rock band Ego Likeness taking him around the United States, Germany and to Shiney Z’s, the finest fetish club in Luxembourg. He also plays accordion and has performed at the Kennedy Center in an all tuba christmas concert. Last year he got a Technician class amateur radio license but has yet to key up because he can just call his ham friends on a cell phone any time he wants. He produces a podcast of cats purring.

Justin uses low-cost components to create fun MIDI controllers. He’ll have a show and tell and expand a bit about how to use MIDI for control and how to make expressive digital instruments.

Photo of Remembrancer installation showing the three panels and robotic painters. Alberto Gaitán : Remembrancer — (Part 2 of 2: The Software)
Alberto is a composer/ programmer/ artist who creates a wide range of new media work. His net-aware piece, Remembrancer, deals with transformation, memory, and the spacial, temporal and cultural resonance of events through automated robotic painters responding in real-time to RSS data flowing in over the Internet.

Alberto will be talking a bit about the applications he integrated to create Remembrancer including Max/MSP, Yahoo! Pipes, and RS485 commands.

Welcome to Dorkbot DC! – Link

DIY mercury testing (or NOT) and new Home Chemistry book

At Make: Books, we’ve been working on an awesome new title, Illustrated Guide to Home Chemistry Experiments, that we’re all really psyched about. Make: Books editor Brian Jepson offers details, by way of an exchange between MAKE publisher Dale Dougherty and the book’s author Robert Bruce Thompson, about the possibility of home-testing for mercury levels:


Robert Bruce Thompson, author of books on everything from PC Hardware to Astronomy, is working on a new book for Make: the Illustrated Guide to Home Chemistry Experiments. So, we’ve got chemistry on our mind here, which led Dale Dougherty, the Publisher of Make, to ask Robert:

I read a story last week about the alarmingly high levels of mercury found in fish in the top sushi places in Manhattan. Ever since, I’ve been wondering is it possible/feasible/reasonable to test for mercury in fish — a DIY mercury test kit. I doubt you could do this in restaurant so let’s presume that this is a test kit for store-bought fish.

The answer for mercury is a bit complex:

The problems are that mercury is toxic at unbelievably low levels and that it is a cumulative poison, which is to say it isn’t excreted. Accordingly, the allowable levels are set so low that there’s no chance they could be detected by any wet chemistry test with a sample of any reasonable size. I was pretty sure of my facts, but just to be certain I ran them past organic chemist Dr. Paul Jones. His response was, “Maybe you could use a wet chemistry test if you had an entire 500-pound tuna for your sample, but otherwise you’d have to use instrumental tests.” Organic chemist Dr. Mary Chervenak points out the Reinsch Test for mercury (which also produces a positive for several other heavy metals). You dissolve the sample in dilute HCl and put a copper strip in the solution. Any mercury present plates out on the copper as a silvery mirror. The trouble is, if enough mercury is present to produce a visible mirror with the Reinsch test, that sample has enough mercury in it to poison everyone in a radius of several blocks.

Robert’s got more details over at his daynotes journal, and a couple of other tests have come to our attention since Dale’s original question. Dale sent a link to a Heavy Metals Test (Robert posted his thoughts on this test in his journal as well), and Popular Science just posted a link to a portable blood test for heavy metals. Have any of you come across some interesting tests for poisons in your body, food, or environment? What results have you had?

From The Maker Store: Illustrated Guide to Home Chemistry Experiments by Robert Bruce Thompson Price: $34.99 Pre-order/Buy: Maker store – Link. For students, DIY hobbyists, and science buffs, who can no longer get real chemistry sets, this one-of-a-kind guide explains how to set up and use a home chemistry lab, with step-by-step instructions for conducting experiments in basic chemistry. Learn how to smelt copper, purify alcohol, synthesize rayon, test for drugs and poisons, and much more. The book includes lessons on how to equip your home chemistry lab, master laboratory skills, and work safely in your lab, along with 17 hands-on chapters that include multiple laboratory sessions.

First Dorkbot DC/Make: DC Joint Project Event

On January 16, 2008, the first joint event of Dorkbot DC and the newly formed Make: DC was held at the Marian Koshland Science Museum. The evening was a smashing success, with some 65 people showing up! We built Arduino-controlled LED Cubes, inspired by the Make: Weekend Projects Podcast on building a “Pocket LED Cube.”

One bit of added excitement to our evening was the ever-present fear that we might set off the fire alarm system which would have killed power to the *entire* building. We were told about the room’s overly-sensitive alarm system — blinking its status-light taunts right above our heads and over one of our work tables — just as dozens of adorable Dorks were pouring into the place, 600-degree firesticks in hand. We nervously moved some tables and scrounged up a bladed fan to push fumes around. As probably 20 irons fired up and that heady, fluxy aroma of solder filled the air, we held our collective breath. I (only half-jokingly) told folks with cameras to have them at the ready so that, when the power went out, as the building filed out into the cold, dark streets, we could at least blog the whole sordid business (“DC Dorks Darken City Block”). Miraculously, no buildings were harmed in the making of our little LED cubes and a great time was had by all (at least as far as I could smell… er tell).

Dorkbot DC has been holding meetings in the Metro area since June 2006. Make: DC is one of a growing number of groups sprouting up in various US cities, started by fans of MAKE who want to get together to build projects inspired by the magazine. So far, there are Make: City groups in Philly, NYC, SF, and now DC. These groups are unofficial, but Maker Media has been kindly supportive of their efforts. For this first Make: DC meeting, The Maker Store generously helped subsidize the cost of the Arduino microcontrollers. A million thanks to Dan, Rob, Sherry, and everybody at Maker Media and at the store.

The next meeting of Dorkbot DC will be Feb 26, at GWU. Check our website for details as they happen. The next Make: DC is not scheduled yet. Adam Koeppel and Nick Farr, co-creators of Make: DC, have put up a website (still being constructed) and will announce the next meeting date and details there.

[Few more pics of the evening after the jump…]


Dorkbot DC/Make: DC Project Night, This Wednesday!

This Wednesday (7 PM – 9 PM ET) is the January meeting of Dorkbot DC and the inaugural meeting of Make: DC, a new project building group inspired by MAKE magazine. We will likely be holding several joint Dorkbot DC and Make: DC events throughout the coming year.

During this first joint meeting, we’ll be building LED cubes based on on the Make: Weekend Projects podcast. See the Dorkbot DC website for details on what tools and hardware to bring. If you don’t have the require components, you can still come and help out. There’s *a lot* of soldering to do.

We’ll be meeting at the lovely Marian Koshland Science Museum of the National Academy of Sciences, 6th & E Streets, NW, Washington, DC 20001, (202) 334-1201.

This event is co-sponsored by The Maker Store.


In last year’s Holiday Gadget Guide, I reviewed the wonderful then-new LEGO MINDSTORMS NXT system. It’s a year later and my admiration for this product has only grown. It has been enthusiastically embraced by robot hobbyists and professionals, educators, kids of all ages, R&D departments looking for quick n’ dirty prototyping components — 1,001 uses. It’s also been embraced by publishers, who’ve followed the product with a felled forest worth of books. Three of may favorites are from No Starch Press (disclosure: O’Reilly, the publisher I work for, distributes No Starch titles).

[Read on…]


I want an Arduino-powered Christmas, baby!

My Make: Books co-conspirator Brian Jepson has posted a quick n’ dirty way of building a 64-node LED matrix (green and red, natch) of holiday lights, driven by a Max 7219 chip and controlled by an Arduino cloneboard. Not too shabby. The resulting LED “net” will only cover a small tree. For a larger tree, you’d have to do a much more ambitious build and cascade Max chips, but it seems to be time-consuming than anything else. Being the geek that he is, Brian also got the thing talking to his mobile phone over Bluetooth, which he promises more info on soon.