This driver is design to connect a Monnit Gateway via Modbus. The Monnit gateway supports multiple wireless devices. Additional eze System drivers are needed for the individual wireless devices.

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default “Field” name (if added to “Fields”)

Active Check box - Check this box and “Save changes” to run the driver. The driver program can be suspended by unchecking the box and clicking on “Save changes”.

User Notes - This space can be used to store information specific to the device and your application, such as: location, wiring, scaling, etc.

eze System Notes - In this space we provide: wiring instructions, product image, product details.

Modbus address - Enter Device I.D. (Modbus address). Default address is 95. This address must be unique on the bus.

Driver info - Typically this is the name from the program file

Driver updated/version - Date loaded or updated and the version of the driver

Battery & Signal - Signal indicates the progress through the script. If driver fails to operate, signal number indicates progress

Driver status - Color and text of status bubbles give a quick visual reference of Communication, Operation, and Application

Communication - Com count indicates number of successful and unsuccessful data packets received

1. Gateway serial - Unique serial number
2. Devices (Active) - Number of registered sensors active
3. Devices (Configured) - Number of registered sensors configured to operate through the gateway
4. Operating channel - Wireless channel in use (0-25).
5. Uptime - Number of seconds the gateway has been active
6. Active -
7. Full reset -
8. Network reset -