Modbus Tcp - ABB ScreenMaster RVG200 Operating Instructions Manual

ScreenMaster RVG200
Paperless recorder

7.10.6 MODBUS TCP

MODBUS TCP enables MODBUS TCP devices to communicate via an ethernet network transferring
MODBUS messages via TCP / IP. Communication with standard, serially connected, MODBUS RTU
devices is also possible through a MODBUS TCP Gateway.
The recorder can be configured to act as either a MODBUS TCP Slave or a MODBUS TCP Master device
on a MODBUS TCP network.
If configured as a Slave, the recorder responds to MODBUS queries transferred via the MODBUS TCP
protocol for the registers described in Appendix B, page 149. The recorder can be configured for
unrestricted access or access can be restricted to a maximum of 6 MODBUS TCP Masters, from defined IP
addresses.
If configured as a Master, the recorder collects data from MODBUS TCP Slaves into its 24 Comms Analog
and 24 Comms Digital Channels. Each analog and digital input can be configured individually to any register
within any slave device. The configuration allows for receipt of data in most commonly used data formats
MODBUS TCP
Implementation
Note. The following parameters are displayed only if Implementation is set to Slave or Master.
MODBUS TCP Port
Note. The following parameter is displayed only if Implementation is set to Slave.
Reverse IEEE Data
OI/RVG200-EN
Select the required MODBUS TCP configuration.
Slave – recorder acts as a MODBUS Slave.
Master – recorder acts as a MODBUS Master.
Disabled – MODBUS TCP disabled.
Set the TCP / IP port-through used by the MODBUS TCP network –
normally port 502.
All analog data is read from the recorder in IEEE format contained in
adjacent registers representing the data in high word, low word order.
Select Yes to reverse the IEEE data, otherwise select No.
7 Configuration
121