Working with WFS
Hunter flow-capable controllers are designed to measure and record actual flow, shut off irrigation when a high flow condition occurs, and identify which stations caused the condition.
The controller’s learn mode samples each station individually, and learns a typical flow for each station in the system. During actual irrigation, the flow can be observed at the controller. Actual flows are recorded and stored in the controller facepack. The ACC or I-Core controller will also compare actual flows to the estimated total of all active stations to see if there is an unacceptable difference, indicating a leak or break.
Consult the controller documentation closely for setup and operation of flow monitoring. It is vital to set the correct pipe size, so that the controller interprets the flow data correctly. It is also important to set adequate overage amounts (minimum is 15% over normal) and delays (default is one minute) to prevent false alarms.
Mainline Pressure Fluctuation
Some water sources may have varying pressure depending upon the demand for water upstream of the point of connection. During times of heavy demand, system pressure through the mainline may drop.
This is why the flow limit percentage and delay periods (set in the controller) are important, as false alarms lead to a lack of confidence in the system.
Additionally, excess air in irrigation piping causes the WFS impeller to spin freely during station startup, which may cause temporarily high readings. This problem may be reduced by installing check valves in the system, and by setting the alarm delay values to prevent premature alarms.
Still need help? We're here.
Tell us what you need support with and we'll find the best solution for you.