Susan, an automated irrigation system
Reads soil moisture at several depths across a field and opens the water valve only when the field needs it. A button lets the farmer overrule the machine.
Design problem
Farms across northern Bangladesh pump groundwater for irrigation, and much of it goes onto fields that don't need it. The first version of Susan used one moisture sensor and one threshold, and it watered whenever the surface read dry. In the field, a farmer showed me that a "dry" plot was still wet underneath, because water from higher ground had collected below the surface where the sensor couldn't see it. The system was pumping water the crop didn't need.
“No need for water today.”
The farmer, checking the soil by handProcess
- Built v1 on the workbench: a moisture probe, a twelve-volt motor-driven valve, Python control logic, and live readings on my phone.
- Field-tested it, and found the subsurface-water failure when the farmer checked the soil by hand.
- Spent two weeks following farmers with a notebook, mapping where water pools after rain, which corners dry first, and why the plot near the canal never needs water.
- Deleted the single moisture threshold. Redesigned the system with probes at several depths, spread across the field.
- Added a manual override button on the enclosure, and logged every override as a design input for the next revision.
- Actuator
- 12 V motor valve
- Sensing
- 3 probe depths
- Control
- Python
- Override
- Manual · logged
Parts · click one for the design decision
Version 2 holds water when the soil is wet below the surface, and judges a field from many points instead of one patch of dirt. Every farmer override goes into a notebook titled “Things Susan Got Wrong,” and that notebook now drives the design more than the sensor data does.