Irrigation Automation Interlocks: Stop the Pump When No Valve Is Open

In a pump-fed irrigation network dedicated to valve-controlled zones, a pump should not continue running when there is no authorized water path. Irrigation automation interlocks connect the operating request to evidence from the field: available source water, a permitted valve sequence, valid flow and pressure signals, and the pump's own protection system. Sending an “open” command to a valve is not proof that water can pass through it. This guide develops a control sequence and acceptance worksheet for that distinction.

Pump control cabinets with meters, drive controls and operating indicators. Photo: IrriNex.

Define the irrigation system that the interlock protects

The example concerns a centrifugal pump supplying irrigation zones directly. A pump filling a storage tank, maintaining an independent pressure network, serving other users or circulating through an engineered minimum-flow route has different operating permissions. “No irrigation valve open” is not a universal shutdown rule for all those arrangements. Mark every legitimate destination for pumped water before writing the control logic.

Obtain the pump's allowable operating envelope at the intended speed and head. The U.S. Department of Energy pumping sourcebook explains why operation below a centrifugal pump's specified minimum flow can cause damage. A variable-speed drive does not remove the need to check that envelope. The irrigation pump flow and head calculation establishes the hydraulic duty that the control sequence must respect.

Treat this worksheet as a functional design brief for the irrigation designer and controls installer. It does not specify motor wiring, a universal shutdown delay or a substitute for independent equipment protection. A dashboard alarm, a software interlock and a protective device at the pump perform different roles. Record which part actually removes the run permission and how its operation will be verified.

Separate a request, an output and physical evidence

A schedule creates demand for a named sector. The controller then energizes an output or sends a message. A field device may acknowledge receiving that message. None of those events necessarily proves that the valve moved, the pilot operated or the downstream pipe accepted water. Keep separate names for “zone requested,” “valve commanded” and “flow established” in the operator display and event log.

Likewise, a pump-start output is a command to an appropriate interface. An auxiliary contact, drive status or other feedback can indicate the equipment's running state, but running feedback alone does not prove delivery to the crop. An intact discharge path still needs suitable hydraulic evidence. The controller and pump-interface selection guide covers the hardware boundary; this article defines the operating sequence across it.

For each signal, record its source, meaning, normal range, update interval and response to a missing or invalid value. A flow reading of zero, a disconnected sensor and a stale positive reading are different observations. The controller should not preserve a pumping permission indefinitely because the last received value looked normal. Specify the maximum acceptable signal age from the local control design and test that behavior.

Build permissions from the source to the active zone

Start with the source-water and equipment permissions: the intake or well can supply the duty, the pump is ready, required protection is healthy, and no maintenance lockout or latched fault is active. Next confirm that the requested zone combination is allowed by the hydraulic design. The NRCS irrigation pumping handbook, pages 8–91 and 8–92, describes low-water, flow and pressure switches as pump-protection inputs.

Place sensors where their readings answer the intended question. A flow meter upstream of a bypass may show pump circulation while every field zone is closed. A pressure sensor before a control valve may remain pressurized when the lateral receives no water. Distinguish protection of minimum pump flow from confirmation of field delivery. If both functions matter, the design must provide evidence for both.

A valve position switch can provide useful feedback when it is actually fitted and appropriate to that valve. Many irrigation diaphragm valves have no such switch, and some need hydraulic pressure to open. Do not require a nonexistent “fully open” signal or demand normal irrigation flow before the pump can start. Instead, document an approved starting path and a bounded transition in which pressure and flow must become established. Independent protective limits remain active throughout that transition.

Use explicit operating states for starting and stopping

The following sequence is an original design worksheet. It describes intended outcomes rather than executable code. The installer must adapt it to the actual valves, pump, source, pipeline and protective devices. Timers and thresholds require equipment data and commissioning measurements; the table deliberately supplies no universal number of seconds.

During startup, a limited allowance for developing normal flow is not permission to run a pump against a closed system. The approved starting arrangement must address valve behavior and pump protection while the network fills. A pressure-dependent valve may require a different arrangement from a motorized valve with position feedback. If the design cannot establish a protected transition, resolve the hydraulic arrangement before enabling automatic starts.

For a routine stop, avoid closing the last available route while the pump is still driving flow unless the engineered sequence explicitly accommodates it. Pump deceleration, valve travel, check-valve behavior and pipeline transients belong in the same review. A fault or emergency stop can require a different response from routine completion. Do not postpone a required protective shutdown merely to finish a scheduled irrigation or flushing duration.

Check sector overlap against the pump's permitted flow

Consider a hypothetical design with zone A requiring 30 m³/h and zone B requiring 20 m³/h at their intended operating pressures. Assume the selected pumping arrangement is approved for 18–40 m³/h under the relevant conditions. These numbers are teaching inputs, not IrriNex equipment ratings. They let the designer test the proposed sequence before programming it.

Each zone alone falls within that assumed flow interval, but their combined target is 30 + 20 = 50 m³/h. Opening B before closing A therefore requests a duty above the assumed 40 m³/h limit. This arithmetic does not predict that the actual pump will deliver 50 m³/h; its operating point depends on the network. It shows that the proposed overlap has not been justified by the design inputs.

A third zone requiring only 8 m³/h would fall below the assumed 18 m³/h minimum if operated alone without another approved water path. A timer change cannot fix that hydraulic mismatch. Review zone grouping, pump selection or an engineered minimum-flow arrangement, and verify the actual pressures and flows. A sector-change command should select only a transition that the completed hydraulic design supports.

Set flow and pressure logic that can detect real faults

Define the expected operating band for each allowed sector combination, with justified allowance for normal variation and instrument uncertainty. Establish what happens when flow is too low, too high, absent, implausible or unavailable. The response may need a bounded confirmation period for ordinary fluctuations, but protective thresholds must not be defeated by an unrestricted delay. Document the reason for each timer and which protections remain independent of it.

Pressure and flow together provide more useful evidence than either alone. Low delivery flow with substantial upstream pressure points to a different investigation from low pressure with excessive delivery flow. Neither observation identifies a single cause automatically. Sensor placement, bypass flow, pump status and valve configuration must be considered before labeling the event as a blockage, leak or dry source.

Check the flow meter's reporting behavior at the smallest authorized duty. Pulse resolution and reporting intervals affect how soon the controller can distinguish a low flow from a failed signal. Use the irrigation flow-meter installation guide to review measurement location and installation conditions. A threshold based on unreliable measurements gives unreliable operating permission.

Keep injection and local protection tied to actual water delivery

Fertilizer injection adds another dependency. Its permission should require the defined irrigation delivery conditions, and it must be removed when those conditions fail. The University of Minnesota chemigation guidance explains the role of injection interlocks and shutdown protection in its regulatory context. Use the applicable local requirements and product labels for the actual installation, including prevention of continued chemical flow after shutdown.

Do not assume that switching off an injection motor prevents every possible gravity or siphon path. The functional brief should identify how the injection system is isolated, how backflow protection is provided and how those functions are checked. Water-only commissioning is different from authorizing chemical application. A successful software demonstration does not replace inspection of the required physical devices.

Specify which decisions remain local when an internet or radio link fails. A remote alarm may help an operator respond, but it must not be the only means of stopping an unsafe local condition. The guide to irrigation with unreliable internet distinguishes communication failures from power and field-device failures. For this interlock, state whether loss of each required local signal removes permission immediately or through a specifically justified bounded response.

Commission failure responses with a recorded test plan

Test the approved logic with the installer using suitable simulation or controlled water-only procedures. Do not deliberately dry-run or deadhead a pump to prove that an alarm exists. Record the stimulus, input values, expected action, actual command, physical response and reset behavior. A successful screen message is incomplete evidence if the pump continues running.

Complete the record with power-return behavior, manual-mode permissions, sector-change tests and recovery after a trip. Acknowledging an alarm should not silently reapply an old run request. Retain the approved settings, software configuration version and the person's signoff for the functional tests. For an IrriNex controls review, provide the route diagram, pump operating envelope, valve behavior, signal list and completed acceptance record.