All Field Notes
Tutorials··4 min read

Reading an Irrigation Controller for the First Time

Stations, programs, run times, and the difference between a conventional and a two-wire controller. If you can read one panel, you can read most of them.

Every controller is the same three ideas

The first time you open a strange controller, it looks like a cockpit. Rain Bird, Hunter, Toro, Weathermatic, some no-name box a previous contractor left behind. Different buttons, different menus, different dials. It feels like you need to learn each one from scratch.

You do not. Underneath the branding, almost every controller is the same three ideas: stations, programs, and run times. Learn those once and you can walk up to a panel you have never seen and have it figured out in a few minutes.

Stations

A station is one output. One wire (or one decoder address on a two-wire system) that opens one valve, which runs one zone. Station 1 is zone 1. Station 8 is zone 8. When a tech says "bump station 4," they mean manually fire the fourth output so you can go watch that zone run.

The number of stations is the ceiling on how many zones the controller can drive. A 6-station controller runs 6 zones. Need a 7th zone, you need a bigger controller or a second one.

Programs

A program is a schedule: which stations run, on which days, starting at what time. Most controllers give you a few programs, usually labeled A, B, and C.

Why more than one? Because not everything on a property should water on the same schedule. Turf wants frequent, short cycles. Shrub beds want deep, infrequent soaks. Drip wants something different again. So you put the turf zones on Program A running Monday, Wednesday, Friday at 5am, and the beds on Program B running Sunday at 4am, and they never step on each other.

This is the single most common thing new techs get wrong: they throw every zone onto one program and wonder why the beds are drowning or the turf is dry.

Run times

The run time is how long each station stays open. Set per station, per program. Zone 1 runs 10 minutes, zone 2 runs 15, zone 3 (that drip line) runs 45.

Here is the part that trips people up. On a single controller, the stations in a program run one after another, not all at once. The controller opens station 1 for its run time, closes it, opens station 2, and so on down the line. It physically cannot run two stations at the same time on the same program. That sequencing matters, and we wrote a whole separate note about why it fools most scheduling software.

Conventional vs two-wire

Two wiring types, and you can usually tell which you are looking at fast.

Conventional. One wire per station, plus a shared common. Open the controller and you see a row of terminals, one per zone, with a wire landed on each. Simple, and what you find on most residential and small commercial jobs. If you have a bad zone, you are chasing that zone's individual wire.

Two-wire (also called decoder systems). A single pair of wires runs the whole property, and every valve has a decoder with its own address. The controller talks to decoder number 14 down that shared pair, and only valve 14 opens. You find this on large commercial sites, golf, big HOAs, anywhere running two wires to every valve box would be a nightmare.

Two-wire is not harder to read, it is just addressed differently. Instead of "which terminal is this wire on," you are asking "what is this decoder's address." When a two-wire zone goes bad, you are troubleshooting the decoder and the shared path, not a dedicated home run.

The five-minute walkthrough

Open a controller you have never seen and do this in order:

  1. Find the station count. Look at the terminals or the display. Now you know the ceiling.
  2. Find the programs. Cycle through A, B, C and see which stations are assigned where.
  3. Read the run times per station. This tells you what the previous contractor intended.
  4. Note the wiring type. Row of individual terminals is conventional. A single pair with decoders is two-wire.
  5. Check the start times and days. This is the actual schedule the property is running on right now.

That is the whole panel. Brand and menu layout change, those five things do not.

If you keep controller, program, and zone data in your head or a binder, that is fine on one property. Across a few hundred, it is the first thing that falls apart, which is a big part of why we built FlowSync to hold it for you. But the reading skill is yours to keep either way. Learn the three ideas and the boxes stop being intimidating.

FlowSync