Skip to main content
Skip table of contents

i500 Irrigation Flow Meter MODBUS Inputs

Note: These features can only be accessed by Client Admin users. Your Wildeye devices may be managed by a third party as a service.

Overview

Wildeye devices with RS485 or RS232 can interface with the I500 Flow Meter through the use of MODBUS Inputs. You can read about the article about product codes and required accessories to support I500 meters here.

MODBUS Inputs

All MODBUS registers in the I500 can be logged by your Wildeye. These are set up in the Input Settings page.

Due to the way MODBUS works, it is necessary to use Calculated Inputs to extract some information from some registers, for example to extract bits for status of faults.

Some examples of MODBUS settings and Calculated Inputs are described below. Wildeye devices can be delivered with standard Input settings already configured if requested when ordered.

Battery Level

Battery_Level_Parent.png
Battery_Level_Child.png

Current Flow

current_Flow_Parent.png
Current_Flow_Child.png

F & Z Factors

F___Z_Factors_Parent.png
F_Factor_Child.png
Z_Factor_Child.png

 

Logic Status

Logic_Status_Parent.png
Logic_Status_of_Self_Test_Functions_Child.png
Logic_Status_of_System_Faults_Child.png

Calculated Inputs

Some examples of using calculated Inputs to extract necessary information from MODBUS registers using bit shifting.

AD Converter Check

CODE
Return System.Convert.ToUInt16(Inputs.Logic status of Self Test function.Value) >> 0 And 1

Coil Current Check

CODE
Return System.Convert.ToUInt16(Inputs.Logic status of Self Test function.Value) >> 6 And 1

Coil Resistance High

CODE
Return System.Convert.ToUInt16(Inputs.Logic status of System Faults.Value) >> 3 And 1

Signal Noise Fault

CODE
Return System.Convert.ToUInt16(Inputs.Logic status of System Faults.Value) >> 7 And 1
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.