As a little series of stuff, I’m going to write retrospectives on several projects I’ve done at Berkeley. I’m going to start with the recent stuff while I still remember it.
In Fall 2012 I took Björn Hartmann’s inaugural class on Interactive Device Design, co-taught with a member of the Mechanical Engineering faculty, (Paul Wright)[http://www.me.berkeley.edu/faculty/wright/] in the spanking new CITRIS Invention Lab. The goal of the class was to educate the software-inclined in physical manufacture and the physical-inclined in software. Students turned out from a few different places, with the makeup showing grads and undergrads from EECS, Mechanical Engineering, Information, and Biomedical Engineering. We worked through several homework assignments involving implementing games and basic controls in software and hardware, as well as performing basic modeling tasks in SolidWorks.
Ultimately we split into groups for our final course projects. I had the pleasure of working with Shiry Ginosar from EECS and Mark Fuge from ME. We had a series of discussions about projects that interested us, and the theme we ended up hitting on was physical devices that had some kind of “smart” configuration aspect, for example a pair of shoes with dynamically inflatable inserts that can adjust to the user’s stance, adapt when he changes from walking to running, etc., to reduce pressure on particular areas of the foot. These types of self-configuring products are becoming more feasible as internet connectivity becomes more ubiquitous and cloud processing cheaper, just think of the Nest Thermostat.
The project we finally decided to pursue was a water-conserving gardening tool, which we call H2O IQ. Inspired by water shortages in both California and Shiry’s home country, Israel, we set out to investigate what it would take to build a device that can be planted in the garden, attached to a drip irrigation system, and forgotten about.
It turns out, not that much. It also turns out that’s not what people want. As a part of the project milestones we were required to do preliminary user interviews. As it happens, gardeners enjoy the time they spend in the garden, and none of them liked the idea of a computer taking over. So much for our machine-learning self-adapting dreams.
Instead, we headed in the direction of a notification system. Our garden device would share soil with a plant and alert its owner when the moisture was too high or too low, prompting action on their part. It could also, of course, serve as a backup watering device in the case the owner is on vacation or otherwise unable to water.
We ended up with H2O IQ, which looks like this:
And works like this:
The 3D printed piece has a solar panel on top for power, a servo for controlling water flow through the irrigation system (connected at the nubs), an XBee for communicating with the Pi upstream, four buttons for changing the watering schedule in-garden, and a moisture sensor built from cast plaster.
The Raspberry Pi functions as a webserver, and can communicate with the device via XBee radio. It serves a website that allows the user to see a graph of the watering history of the plant, as well as perform a one-time automatic watering or set a schedule of future watering.
We didn’t actually have time to test the product in the course, but we made a final presentation at the end which you can see on Google docs. All of our code, SolidWorks models, and Eagle files for circuitboards (as well as a teensy bit of documentation…) can be found on Github.
It was an interesting course project that led into some territory I’d not explored before, but which I suspect I’ll need as I delve deeper into the world of hardware.