Scope This purpose of this document is to provide an introduction to the MicroVision Controller and its Modbus TCP/IP capabilities. The intent is to provide a Modbus developer with the information needed to interface the controller with a typical Supervisory Control and Data Acquisition (SCADA) system. 2.
3. Connections and Installation Modbus Interface Type: Slave / Server Modbus Protocol Type: Modbus TCP Modbus Address: Connection Port: Data Encryption: none Endianness: big-endian Number of simultaneous connections: Timeout: 1 Sec. Function Codes Supported 4 (Read Input Registers) Notes: MicroVision supports both Dynamic and Static IP addresses.
4. Modbus memory map The availability and content of the registers listed in the following sections is model dependent. The MicroVision Modbus interface is designed to provide a Modbus Master / Client with controller configuration and status information via Modbus function code 4 (Read Input Registers).
Relay 3 Status Depending on the model this relay may be ORP or a Timer – See appendix A. Refer to Relay 1 table for field details. Modbus Name Start Data Details Address Address Type Relay 3 Run Time 30033 30034 UINT32 Relay 3 HOA Run...
Relay 4 30054 30055 FLOAT Measurement Value Relay 4 Relay 30056 30056 UINT16 State Bit Field Relay 5 Status On all models this relay is a Timer– See appendix A. Refer to Relay 1 table for field details. Modbus Name Start Data Details...
Relay 6 Status On all models this relay is a Timer– See appendix A. Refer to Relay 1 table for field details. Modbus Name Start Data Details Address Address Type Relay 6 Run Time 30069 30070 UINT32 Relay 6 HOA Run 30071 30071 UINT32...
Measurement Value Relay 7 Relay 30092 30092 UINT16 State Bit Field Relay 8 Status On all models this relay is a Timer– See appendix A. Refer to Relay 1 table for field details. Modbus Name Start Data Details Address Address Type Relay 8 Run Time 30093...
Alarms Alarms are presented to the Modbus master /client as input registers in the form of bit fields. Alarm indicators are binary, meaning they have two states. A “0” indicates the alarm is inactive while a “1” indicates the alarm is active. The following registers are accessible on all models.
Bit 8 = T3 Low Alarm Bit 9 = T4 Limit Alarm Bit 10 = T5 Limit Alarm Bit 11 = T6 Limit Alarm Bit 12 = PULSAlink Alarm Water Meters Water meter count data is presented to the Modbus master / client as floating point values.
Conductivity Probe Temperature The MicroVision Toroidal Conductivity Probe contains a built sensor to measure the cooling tower’s fluid temperature. The temperature measurement is reported in both Fahrenheit and Celsius. The following registers are available on all models. Modbus Name Start Data Details Address...
Page 14
4-20mA The content of the following registers is model dependent and will have no valid meaning unless the associated hardware is present and configured correctly. The following registers are available on all models. Modbus Name Start Data Details Address Address Type 4-20mA Input 1 30001...
Relay States Relay states are presented to the Modbus master /client as input registers in the form of bit fields. Relay state indicators are binary, meaning they have two states. A “0” indicates the relay is inactive while a “1” indicates the relay is active. The following registers are accessible on all models.
Digital Input States The states of the digital inputs are presented to the Modbus master /client as input registers in the form of bit fields. Digital input state indicators are binary, meaning they have two states. A “0” indicates the input is inactive while a “1” indicates the input is active.
Configuration Parameters The following registers are accessible on all models. However, the content of these registers is model dependent. The user must interpret the content of these registers within the context of the model and the associated installed hardware. Modbus Name Start Data Details...
Page 19
Setpt. Type T2 SetptMode float Setpt. 30217 30218 Sensor Type dependent T2 SetptMode float Dffrntl. 30219 30220 Sensor Type dependent T2 SetptMode float High Alrm Setpt. 30221 30222 Sensor Type dependent T2 SetptMode Low float Alrm Setpt. 30223 30224 Sensor Type dependent T2 SetptMode Lmt uint32_t 30225...
Page 20
8 = Temp. C 9 = Temp. F 10 = PPB 11 = PPM 12 = PSI 13 = % 4-20mA In 2 String 8 registers, 2 ASCII Name 30296 30303 Characters per Modbus reg. 4-20mA In 2 Type 30304 30304 uint16_t See 4-20mA In 1 Type...
Page 21
Time active in HOA On Mode Relay 8 Name String 8 registers, 2 ASCII 30371 30378 Characters per Modbus reg. Relay 8 Cnfg 30379 30379 uint16_t See Relay 2 Cnfg Relay 8 HOA Run uint32_t Number of seconds relay is Time 30380 30381...
5. Appendix A: MVEX Model Features Model / CXXE C5XE CPXX COXX CPOX Control Conductivity Conductivity Conductivity Conductivity Conductivity Parameters only only & PH & ORP & PH & ORP Relay 1 Conductivity Conductivity Conductivity Conductivity Conductivity Probe Probe Probe Probe Probe Relay 2...
Page 23
6. Appendix B: Uploading ModBus Software to Existing MVEX Controller Download existing datalog from the controller. Data stored on the controller will be lost when the software is updated. Data which has been uploaded from the controller to PULSAlink.net will NOT be lost and will remain on the PULSAlink server.
Page 24
Warranty Pulsafeeder, Inc. warrants control systems of its manufacture to be free of defects in material or workmanship. Liability under this policy extends for 24 months from date of shipment including the toroidal sensor. Electrodes/probes other than the toroidal conductivity sensor are considered maintenance items and as such are warranted for six (6) months from the date of shipment of the controller.
Need help?
Do you have a question about the MicroVision EX and is the answer not in the manual?
Questions and answers