navigator subscribe what is this? virtual console latest news home contact search
navigator1 boutique sponsors public speaking press room resources technomads microship adventure
navigator2 winnebiko volunteers sponsor behemoth winnebiko2
icon navigation final tour office album camping recumbent security packaging why communication computer power beginnings

The R&D Lab

Speaking of serviceability, what, exactly, do I service this with? The standard suite of bicycle tools is on board, of course, but that hardly takes care of eprom programming, glitch chasing, interface hacking, logic probing, analog calibrating, and embedded system debugging.

Nestled among the packs of clothing and camping gear in the trailer is the R&D Pack, a collection of tools and parts that should handle most field-development and maintenance tasks. This includes a Createc 10 MHz handheld dual-trace oscilloscope with LCD screen and flexible user interface. Naturally, I also have a small logic probe, digital multimeter, and frequency counter -- as well as a good selection of precision hand tools.

For wiring, there is an Ultratorch butane soldering iron (also does heat shrink), as well as an insulation-displacement tool for the Robinson-Nugent prototyping panels. And a healthy inventory of chips, discretes, packaging hardware, special spares, and wire rounds out the R&D Pack.

But there are a number of other tools required for a system as complex as this. For example, digital panel meters with thumbwheel switches are mounted on the console and in the commbay (trailer) to allow quick hardware checks of all major system voltages. And a 6X8 array of LEDs on the front panel is driven by a dedicated multiplexer that allows display of 144 individual bit conditions, including key buses and power-control lines. This is normally off to conserve power, of course, but when things aren't working it provides an instant window into BEHEMOTH's internal organs.

And then there are the development environments -- FORTH for the controllers and HyperTalk for the Macintosh. We can also transmit bit images or JEDEC files to a BP device programmer as required.

Finally, the documentation of the entire system is handled by an OrCAD hierarchical file structure. This allows me to home in quickly on a needed schematic file, edit it, add notes, generate printed circuit artwork for emailing or faxing to a fab house, or whatever -- all from the console. Of course, I also generate an occasional hardcopy of the whole system for easy reference, and transmit backups to the base office for security in case of a disk crash!

next