Four independent valve outputs
Separate two-wire connections drive four DC latching valves with polarity-reversing pulses. Sequential zone control coordinates the watering sequence.
DESIGN CASE · CONNECTED AGRICULTURE
Published engineering candidate. Prototype validation and production release are pending. A four-zone irrigation control design that brings valve drive, field power, wireless communication and sensor interfaces into one system.

01
Separate two-wire connections drive four DC latching valves with polarity-reversing pulses. Sequential zone control coordinates the watering sequence.
A protected LiFePO4 battery supplies the controller. A dedicated solar charger connects the panel to the battery, with power monitoring included in the board design.
The field controller communicates through a LoRa gateway. EU868 and US915 configurations address different deployment regions.
A wired rain switch and an optional pulse-output flow meter connect environmental feedback and water-use measurement to the control system.
02
Plan the water supply and zones together. Electronics coordinate valve commands; pipes, filtration and operating pressure belong to the irrigation design.
Connect independent valves to beds with different watering times. A supply-line meter records water use; indoor areas can use schedules without an outdoor rain interlock.
Assign a valve to each branch and command zones sequentially. Match cable length and coil voltage to manifold location; set the meter’s volume per pulse.
Combine lawn and planting zones with a wired rain contact for an interlock option. Battery power supports locations without a nearby controller power cable.
Place nodes near existing water connections and share a regional LoRaWAN gateway. Separate valve wiring from communication; plan gateway placement and backhaul around the site.
03
The controller is one part of the irrigation system. The design coordinates the power path, four valve connections, sensor inputs and wireless link.
04
A protected 2S LiFePO4 pack supplies separate 3.3 V logic and boosted valve-pulse rails. The solar panel connects through a dedicated charger, not directly to the battery connector.
RAK3172-T combines MCU and LoRa. Four DRV8876 H-bridges reverse coil polarity through independent pairs. Battery, pulse-bus and current monitoring inform power decisions and record electrical execution.
EU868 and US915 require matching module, antenna, gateway and software settings. Class A downlinks follow uplinks, linking reporting cadence to command latency.
05
The control strategy commands one watering zone at a time and distinguishes command acceptance, electrical pulse completion and hydraulic feedback.
Queue startup close pulses before opening requests; do not automatically restore a previous open state.
Validate ID, expiry, zone and maximum duration. Identical repeated IDs retain the original result and deadline.
Permit opening only with energy for opening, subsequent closing pulses and the configured margin.
Disable all outputs before reversing polarity, then apply a bounded pulse to one channel and record current.
Network loss does not extend watering. Skip expired schedules rather than grouping them for catch-up.
Prioritize closing at the deadline or low energy. Separate electrical faults from verified water-flow results.
06
These values describe the design interfaces and reference components. Valve choice, cable loss and environmental conditions determine the project configuration.
| Interface | Design basis | Configuration detail |
|---|---|---|
| Battery · J1 | Protected 2S LiFePO4 · 5.6–7.4 V interface basis | Battery positive / ground; no raw solar input |
| Valve outputs · J6–J9 | Four independent two-wire H-bridge outputs | One valve pair per channel; opening and closing polarity mapped to the coil |
| Reference coil | Hunter 458200 · 6–9 V · 4.8 Ω nominal · 250 ms | Manufacturer’s coil data; voltage applies at the coil |
| Rain · J4 | Ground + dry-contact input | Wired normally closed rain switch; define the inhibit rule |
| Flow · J5 | Ground + dry-contact pulse input | Reed output; set volume per pulse; no sensor-power pin |
| Service · J2/J3 | SWD and 3.3 V UART | Programming and diagnostics; cross UART TX/RX |
| Wireless | EU868 or US915 configuration | Match node, gateway and network-server settings |
Independent valve pairs do not mean galvanic isolation. J4/J5 do not accept an external 12 V or 24 V signal.
07
Latching valves use switching pulses without continuous coil holding power. Size pulse supplies for peaks; add sleep, radio, sensing and charging losses to the daily budget.
For a resistive sizing estimate, E ≈ V²t/R. At 8.7 V, 250 ms and 4.8 Ω, this gives about 3.9 J per pulse. Converter, bridge and cable losses require additional input energy; this is a calculation, not a measured consumption figure.
Size battery and panel for watering frequency, site sunlight and poor-weather reserve. Charge voltage, current and temperature inhibition follow the selected pack’s instructions.
08
Valve outputs, power conversion, the radio controller and sensor connections are arranged on one board.

The accessory plan covers valve bodies and DC latching solenoids, a battery and solar panel, a dedicated charger, the antenna and gateway, a rain switch, an optional flow meter, and the enclosure with its cable glands and harnesses.
| Four DC latching valves | Four independent two-wire outputs |
|---|---|
| Battery and solar panel | Dedicated charger → battery → controller |
| Rain switch | Wired dry-contact input |
| Optional flow meter | Pulse-output interface |
| Antenna and gateway | EU868 or US915 LoRa configuration |
| Enclosure and harnesses | Cable glands and separate valve wire pairs |
Valve thread type, regional radio configuration, charging parameters, sensor signal type and cable length are coordinated with the installation requirements. Each valve uses its own wire pair; the solar panel connects through the charger.
09
10
Product options include valve parameters, charging integration, battery size, antenna mounting, connectors, enclosure, reporting intervals and gateway/server integration. Additional sensors or pump controls need their own interface scope.
Board cost depends on area, layers, copper, radio module, four drive channels, sampling, protection and assembly. Programming, test fixtures and system checks also affect unit cost; component price alone is incomplete.
11
Share the coil model, drive voltage and pulse requirements. DC latching and continuously powered AC valves require different power stages.
The strategy keeps accepted local deadlines active. Class A remote commands depend on receive windows; urgent shutoff should not rely only on a downlink.
A latching valve retains its position. Complete-power-loss closing requires dedicated energy storage or a suitable hydraulic safeguard.
No. Electrical execution and physical water state are different. Confirming closure requires suitable flow or position feedback attributable to the valve.
A common supply meter supports consumption records during sequential commands. Other branches, leaks and mechanical faults affect attribution.
Calculate from the complete daily load and usable reserve. Module sleep current or nominal battery amp-hours alone cannot establish system autonomy.
12
The published PCB requires power-layout and manufacturing review before a pulse-power build. These resources support design review and prototype planning. Review diagrams, interfaces and engineering sources at your own pace. Downloads require neither registration nor an inquiry form.
All published resources and the file index.
ZIP · 3.05 MBPower, radio, sensing, pulse control and valve drives.
PDF · 451 KBEditable schematic, PCB and project libraries.
ZIP · 262 KBComponent references, quantities, values and footprints in CSV format.
CSV · 13 KBInterfaces, accessory selection and wiring diagrams.
ZIP · 492 KBCommands, deadlines, closing priorities and fault behavior.
ZIP · 25 KBCost drivers, manufacturing review and functional tests.
ZIP · 1.06 MBFind files through the package index. Include changed valve, battery or installation requirements in the inquiry.
Share what differs at your installation. Requirements and downloaded material help define electronics, accessories and integration.
Mention this irrigation design so the discussion covers its interfaces and accessories. Start with available information.