Check remote irrigation commands and feedback

Remote control is useful only when the team can tell what happened after a command. Pair a valve command with an appropriate feedback signal and operator confirmation. Review the signal against the hydraulic system and local safety procedure before planning the next action.

Precision agriculture with Sensorius

Begin with the irrigation task

Start by naming the valve or other asset, the zone it serves, the intended operating window, and the conditions that could make the action unsuitable. A command to one part of a network can affect pressure and flow elsewhere. Pump capacity, filtration, water availability, pipe condition, crop stage, weather, and local procedures all matter to the decision.

Use field measurements, weather context, crop timelines, and the irrigation record to review where attention may be needed. Use these sources as context. A sensor threshold alone is not an irrigation prescription. The farmer or agronomy team remains responsible for the decision.

A command is not confirmation

At the site, the device can use a reversible 12 V output to drive a compatible external actuator. Compatibility depends on the specific actuator’s electrical demand, wiring, travel behavior, control timing, and installation conditions; a matching voltage alone is not enough.

IN1 and IN2 collect supported pulse or state signals from connected equipment. Depending on the installation, a signal may represent a switch state, actuator feedback, or flow-meter pulses. The wiring and configuration define what the signal means. A requested movement, a reported state, and water moving through the intended zone are different facts and should be recorded as such.

The device connects over LTE-M or NB-IoT. Supported events and measurements can be buffered during a connectivity interruption, then sent after the connection returns. That means a newly received event may describe an earlier time. Operators need to check the event time and follow the agreed procedure for out-of-date or delayed information before treating it as current confirmation.

Decide how operators will confirm each action

For each remote action, define who can authorize it, what evidence should follow, how long to wait, and who responds if that evidence is missing or contradictory. Depending on the equipment, confirmation may use an actuator limit switch, a flow pulse, a local controller signal, an on-site inspection, or more than one source.

A flow pulse can indicate measured flow at its sensor, but does not by itself prove that pressure, distribution, water quality, or the rest of the hydraulic system is safe. A position signal can indicate actuator position without proving that the intended zone receives water. Keep the meaning and limits of every signal visible to operators.

Before using remote control, decide what should happen if power or communication fails, the actuator does not complete its travel, an unexpected input arrives, a timeout occurs, or someone overrides the system manually. Remote commands must not bypass local interlocks, equipment protections, emergency procedures, or manufacturer instructions. Unattended operation requires separate site approval and a tested fail-safe design; it is not assumed by the device capability described here.

Fit the workflow to field operations

Irrigation plans change with crop development and field conditions. Teams can review available soil measurements, weather and forecast context, crop timing, previous irrigation events, and connected equipment feedback together. Missing or delayed information should remain visible so the operator can decide whether to wait, check locally, or use the farm’s established procedure.

Where the deployment includes compatible valves or meters, SENS-FLOW-CTRL-V1 can add remote actuation and input telemetry to that review. SENS-SOIL-BASIC-V1 provides direct soil-condition measurements. These capabilities help your team record commands and check their results. They do not guarantee water savings, crop response, or the suitability of an irrigation schedule.

Deployment checks

  • Identify the exact actuator and verify voltage, current, reversible-polarity behavior, wiring, travel time, and environmental requirements.
  • Review hydraulic effects, including pump dependencies, pressure and flow ranges, zone interactions, and the safe sequence of operations.
  • Document what each digital input represents, its signal characteristics, and how invalid, missing, or delayed readings will be handled.
  • Set command authorization, timeout, confirmation, retry, cancellation, escalation, and manual override procedures.
  • Confirm mounting, power, LTE-M or NB-IoT coverage, local access, and protection appropriate to the site.
  • Test the complete command and feedback path locally under controlled conditions before enabling remote use.
  • Train operators to distinguish a sent command, a device event, actuator feedback, flow measurement, and verified irrigation outcome.

Continue with the irrigation solution

Back to Irrigation · Discuss an irrigation workflow

Contact Us

Remote valve control can help an irrigation team coordinate planned actions across fields, blocks, greenhouses, or storage points. SENS-FLOW-CTRL-V1 provides a 12 V reversible-polarity output for a compatible external actuator and two digital inputs for supported pulse or state telemetry. LTE-M or NB-IoT carries supported device events and measurements to the Sensorius Platform. The installation plan must specify what the device can control, what each input reports, and how an operator will confirm the result.

Discuss an irrigation workflow

Begin with the irrigation task

Start by naming the valve or other asset, the zone it serves, the intended operating window, and the conditions that could make the action unsuitable. A command to one part of a network can affect pressure and flow elsewhere. Pump capacity, filtration, water availability, pipe condition, crop stage, weather, and local procedures all matter to the decision.

Use field measurements, weather context, crop timelines, and the irrigation record to review where attention may be needed. Use these sources as context. A sensor threshold alone is not an irrigation prescription. The farmer or agronomy team remains responsible for the decision.

A command is not confirmation

At the site, the device can use a reversible 12 V output to drive a compatible external actuator. Compatibility depends on the specific actuator’s electrical demand, wiring, travel behavior, control timing, and installation conditions; a matching voltage alone is not enough.

IN1 and IN2 collect supported pulse or state signals from connected equipment. Depending on the installation, a signal may represent a switch state, actuator feedback, or flow-meter pulses. The wiring and configuration define what the signal means. A requested movement, a reported state, and water moving through the intended zone are different facts and should be recorded as such.

The device connects over LTE-M or NB-IoT. Supported events and measurements can be buffered during a connectivity interruption, then sent after the connection returns. That means a newly received event may describe an earlier time. Operators need to check the event time and follow the agreed procedure for out-of-date or delayed information before treating it as current confirmation.

Decide how operators will confirm each action

For each remote action, define who can authorize it, what evidence should follow, how long to wait, and who responds if that evidence is missing or contradictory. Depending on the equipment, confirmation may use an actuator limit switch, a flow pulse, a local controller signal, an on-site inspection, or more than one source.

A flow pulse can indicate measured flow at its sensor, but does not by itself prove that pressure, distribution, water quality, or the rest of the hydraulic system is safe. A position signal can indicate actuator position without proving that the intended zone receives water. Keep the meaning and limits of every signal visible to operators.

Before using remote control, decide what should happen if power or communication fails, the actuator does not complete its travel, an unexpected input arrives, a timeout occurs, or someone overrides the system manually. Remote commands must not bypass local interlocks, equipment protections, emergency procedures, or manufacturer instructions. Unattended operation requires separate site approval and a tested fail-safe design; it is not assumed by the device capability described here.

Fit the workflow to field operations

Irrigation plans change with crop development and field conditions. Teams can review available soil measurements, weather and forecast context, crop timing, previous irrigation events, and connected equipment feedback together. Missing or delayed information should remain visible so the operator can decide whether to wait, check locally, or use the farm’s established procedure.

Where the deployment includes compatible valves or meters, SENS-FLOW-CTRL-V1 can add remote actuation and input telemetry to that review. SENS-SOIL-BASIC-V1 provides direct soil-condition measurements. These capabilities help your team record commands and check their results. They do not guarantee water savings, crop response, or the suitability of an irrigation schedule.

Deployment checks

  • Identify the exact actuator and verify voltage, current, reversible-polarity behavior, wiring, travel time, and environmental requirements.
  • Review hydraulic effects, including pump dependencies, pressure and flow ranges, zone interactions, and the safe sequence of operations.
  • Document what each digital input represents, its signal characteristics, and how invalid, missing, or delayed readings will be handled.
  • Set command authorization, timeout, confirmation, retry, cancellation, escalation, and manual override procedures.
  • Confirm mounting, power, LTE-M or NB-IoT coverage, local access, and protection appropriate to the site.
  • Test the complete command and feedback path locally under controlled conditions before enabling remote use.
  • Train operators to distinguish a sent command, a device event, actuator feedback, flow measurement, and verified irrigation outcome.

Common questions

Can SENS-FLOW-CTRL-V1 operate any irrigation valve?

No. It supports a 12 V reversible-polarity output for compatible external actuators. The specific actuator, current demand, travel behavior, wiring, timing, and site conditions must be checked before compatibility is confirmed.

Does a successful command mean that water is flowing?

No. A command requests an action. Input feedback may provide evidence defined by the installation, but valve position and measured flow do not establish every hydraulic condition. Confirmation must match the asset and operating risk.

Does Sensorius decide when to irrigate or irrigate automatically?

No. Sensorius helps teams review field and operational information. Farm operators and agronomy teams decide when to act. Any unattended control requires separate deployment approval, a defined fail-safe, and commissioning under local procedures.

What happens if cellular connectivity is interrupted?

Supported events and measurements can be buffered and sent after reconnection. Delivery may be delayed, so operators should consider timestamps and follow the site procedure when current confirmation is unavailable.

Continue with the irrigation solution

Back to Irrigation · Discuss an irrigation workflow

Common questions

Can SENS-FLOW-CTRL-V1 operate any irrigation valve?

No. It supports a 12 V reversible-polarity output for compatible external actuators. The specific actuator, current demand, travel behavior, wiring, timing, and site conditions must be checked before compatibility is confirmed.

Does a successful command mean that water is flowing?

No. A command requests an action. Input feedback may provide evidence defined by the installation, but valve position and measured flow do not establish every hydraulic condition. Confirmation must match the asset and operating risk.

Does Sensorius decide when to irrigate or irrigate automatically?

No. Sensorius helps teams review field and operational information. Farm operators and agronomy teams decide when to act. Any unattended control requires separate deployment approval, a defined fail-safe, and commissioning under local procedures.

What happens if cellular connectivity is interrupted?

Supported events and measurements can be buffered and sent after reconnection. Delivery may be delayed, so operators should consider timestamps and follow the site procedure when current confirmation is unavailable.

Continue with the irrigation solution

Back to Irrigation · Discuss an irrigation workflow

Contact Us

Continue with the irrigation solution

Back to Irrigation

Discuss an irrigation workflow

Discuss an irrigation workflow

Discuss an irrigation workflow

Back to Irrigation · Discuss an irrigation workflow

Discuss an irrigation workflow

Define the first decision loop

Choose one repeated, timing-sensitive workflow and agree how usefulness and outcomes will be reviewed.

Discuss an irrigation workflow