Lawn Mower Overclocking

The most exciting phrase to hear in science, the one that heralds new discoveries, is not “Eureka” but “That’s funny…”
—Isaac Asimov (1920–1992)

Perhaps twenty-five years ago, my parents owned an Ariens riding lawnmower. This was a basic, no-frills model, but it ran reliably and got the job done. Being the teenage son, reasonably mechanically-inclined, underpaid, and somewhat expendable, I got lawn-mowing duty. (Actually, my Dad volunteered to do the trim work with the push mower, so even back then, I recognized I got the better end of that deal.)

The Ariens did a good job nearly all of the time — but at 5HP, it was quite a bit underpowered for what it was asked to do. When cutting through thick grass or climbing the steep hill in back of the house, it would sometimes stall out. The canonical workaround for the thick-grass problem was to raise the cutting deck, and drive over the grass very slowly at full power; the workaround for the climbing-the-hill problem was to dismount and walk alongside the mower up the hill while reaching over to steer it. This was fun, but you always ran the risk of the mower either getting away or running over your toes. (At least I had the sense to shut off the blades.)

One day, while backing up to turn around near some pine trees, the mower’s engine revved up dramatically. Not knowing what was happening, I quickly shut it off and rolled it back away from the trees. When I started it up again, everything was fine. I took a look around the engine, and noticed a spring-loaded lever on the right side, near the back of the mower. Pressing gently on this lever caused the engine to speed up a bit.

Playing around with the lever mechanism a bit more, I figured out what it was — a governor for the engine, tied to a set of vanes that pulled the lever forwards when the engine speed increased. By applying some pressure to the lever, the engine could be made to speed up. Since car engines often speed up when more power is needed, I decided to see if this could be used to give the mower a bit more power.

I found some twine, tied it through a hole in the lever, and tied it to one of the seat supports. By pulling gently on the line, I could apply pressure to the lever, and cause the engine to rev up a bit past its normal set point. Instant “turbo mode!”

The mower worked great after that. Whenever I saw a steep hill or tall grass ahead, I would simply pull on the “extra power” cord, and power through the grass or up the hill with no problem at all. Rumors that I would occasionally put the mower into fourth gear and use this effect for extra speed while racing back to the garage are merely conjecture based on stereotypical generalizations of teenage guys. (That’s my story, and I’m sticking to it.)

A year or two later, while doing spring cleaning in the garage, my Dad noticed the line and asked me about it. I told him what it was for and why; to his credit, he just rolled his eyes and mumbled something about pretending not to have seen it. (I guess he did a quick calculation of the risk of a blown engine vs. the unsafe practice of me walking alongside the mower when going up the hill, and decided it was worth it.)

We eventually got a larger mower, and sold the Ariens (still running like the day we bought it, but minus the hack) at a yard sale. The newer mower had a 10HP two-cylinder Briggs and Stratton, electric start, and headlights. It climbed the hill easily and went through the worst summer grass like it was nothing. It was also fast enough in top gear that even as a reckless teenager, I usually didn’t run it flat out because of the risk of hitting a tree. (It cornered like a dump truck.) Still, sometimes I missed the Ariens. There’s just something about a good, fun hack.

 

Posted in Hacks, Nostalgia | 1 Comment

Breadboard oscilloscope

Miniaturization has made a lot of cool electronic toys tools possible. Often, when the size and cost of a device is greatly reduced, it opens up many new possibilities. In-the-field tests that would be impossible with a rackmount or desktop tool and awkward with a handheld one suddenly become easy when the tool can be almost built in to a project under development.

One great example of this is the Gabotronics XProtoLab. It’s a miniature, breadboardable dual-trace digital oscilloscope! While it doesn’t have all of the functionality of a desktop ‘scope (notably, its 2MSPS sampling rate limits it to low frequency signals), the ability to stick it on a breadboard or dev board and view signals in the field can be very helpful.

The Gabotronics XProtoLab breadboardable oscilloscope. (Click for larger.)

Setup and use is very straightforward: provide 5VDC and ground, and connect the signals to be monitored. The four control buttons operate various menu options, allowing the time and voltage scales to be set, as well as other functions (triggering type and level, persistence, etc) to be controlled.

The cost is actually another plus — at $49US, it’s cost-effective to have one or two of these on hand for measurement of signals in the field. GPS-enabled projects, for example, don’t do well indoors, and debugging often involves monitoring system functionality while moving. In an industry where a blinking LED is a time-honored diagnostic tool, the advent of low-cost, affordable tools like this is very welcome.

 

Posted in Analog, Digital, Electronics, Tools, Toys | Tagged , , , , , , , | Leave a comment

RIP, Dennis Ritchie

I recently learned that Dennis Ritchie (of “Kernighan and Ritchie” fame) passed away a few days ago. He will be very much missed by the technical community. How many people can say that they were the principal designer of (and co-wrote THE book on) C — the single most influential computer language ever written?

If you Google “C programming language,” the top result is the Wikipedia description of the language itself. Just under that is the Wikipedia article on the book of the same title. Those of us in the industry refer to it as “Kernighan and Ritchie,” “The Book,” “K&R,” “The Bible,” and “The Book of C.” It’s a small, unassuming book — but very well-written. It provides a solid yet approachable introduction to programming in C. (It’s also responsible for the “Hello, World!” programming meme, started in a Bell company memo by Ritchie’s co-author Brian Kernighan.) If I had to cut my library down to only the books I could fit in my backpack, my copy of K&R would be included, no question about it.

C is almost literally everywhere. Microcontrollers with firmware written in C run our cars, make our coffee, and guide us to our destinations. More powerful CPUs running programs written in C are used in our computers and smartphones. The Linux kernel is written largely in C, and Windows and Mac OS also no doubt contain at least significant amounts of C code. Android programs may be written in (C-based) Java, but the underlying OS is written in C. The computer I’m using to type these words is running a browser (Chrome) no doubt written in a C-like language. The webserver which hosts this site runs the “LAMP stack“: Linux (written in C); the Apache webserver (written in C); MySQL (written in C and C++); and PHP (written in C). The routers shepherding the packets containing this text use firmware that is almost certainly written in C.

Although C was written between 1969 and 1973 as an operating-system language, it is still very much in widespread use today, and has inspired and influenced many other languages. Programs written in C++, C#, Java, Perl, PHP, Go, and others all owe their basic syntax and structure to C.

C is still widely used after so many years because it manages to be most things to most people. It is a very fast, efficient compiled language (nearly as fast as hand-written assembly code, in most cases), yet is far easier to learn and use than assembly. It can be used to write complex, multithreaded operating systems, create virtual 3D game worlds, or to write simple programs to make 40-cent microcontrollers blink an LED or run a toaster.

RIP, Mr. Ritchie. Thanks for giving the world one of the solid cornerstones of the Information Age.

 

Posted in C, Coding, Current Events, Digital, Digital Citizenship | Tagged , , , , , | Leave a comment

Unintentional Destructive Testing

Note to self: Current handled by circuits on solderless breadboards should be limited to no more than 1A or so. Otherwise, things start to get smokier than normal, as demonstrated by what a prototype control board did to itself during a test run…

High current = high temperatures = bad. (Click for larger.)

This kind of failure, though, demonstrates a valid diagnostic technique (albeit one taken to destructive extremes in this case): All else being equal, a conductor will become warmer when carrying more current. For example, it’s evident from the above picture what the high-current path was — through the first and fourth relays, which make up one half of an H-bridge setup. For some reason, the final part of the path — the short green wire at the upper left — didn’t get cooked, although it was carrying just as much current as the rest of the circuit. A different formulation of plastic, perhaps…?

Given an IR thermometer, this resistive heating effect (hopefully with less extreme temperatures) can be used to determine which chips are dissipating more power than others in a circuit. It can also sometimes be used to determine which device is causing a short — without risking burning your fingertips. Simple IR thermometers are available for around $20US; I picked one up a while back and keep finding new uses for it.

 

Posted in Drexel, Electronics, Power | Tagged , , , , | 2 Comments