From field data to controlled irrigation.
Irrigation control built around the last valid local schedule during communication loss and controlled resynchronisation afterwards.
How it works
Transfer the schedule to device memory and verify it by reading back. Do not expect immediate remote commands while disconnected. Include expiry and duplicate-prevention behaviour in acceptance so stale commands are not executed after reconnection.
Data used
Last approved schedule; local clock; battery state; outage duration; queued commands; executed-watering records.
Design and commissioning
Define scope by evaluating site topology, planting and soil, selected devices, sensors and software version together. For retrofit projects, establish valve/coil compatibility, measurement points, communication coverage and operational responsibilities during the survey.
Test schedule behaviour under power/battery and communication interruptions for the selected model. Compare clock, schedule version and executed actions after reconnection.
The next step
Progressive outage profiles, safe standby and automated event reconciliation.
This section describes development and project-specific integration objectives. It is not a claim of standard product availability or guaranteed performance; implemented functions are defined in the quotation and acceptance criteria.
Applications
Municipal parks, public gardens, university campuses, industrial-zone landscapes, residential estates, hotels, sports facilities and road medians. As zone and site counts grow, standard asset records, traceable actions and measured management become essential.
Plan your landscape irrigation project with us.
Share the site area, valve count, existing connectivity and project objectives. We can define device selection, coverage survey, integration and pilot requirements together.
Request a project quotationContact our technical team