Ethernet/Ip Tag/File To Modbus Diagnostics Page - Comtrol DeviceMaster EtherNet/IP-Modbus EIP-MOD User Manual

EtherNet/IP Tag/File to Modbus Diagnostics Page

8.11. EtherNet/IP Tag/File to Modbus Diagnostics Page

Access the EtherNet/IP Tag/File to Modbus Diagnostics page by clicking Diagnostics | Data Mapping
Diagnostics | Tag/File to Modbus.
Line
PLC Type
IP Address
Tag/File
Tx Messages
Rx Messages
Error Responses
Device ID
Function code
Address (base 1)
Tx Messages
Rx Messages
No Path
Error Responses
Unexpected
Responses
DeviceMaster EIP-MOD User Guide: 2000664 Rev. A
EtherNet/IP Tag/File to Modbus Diagnostics Page
Displays the configuration line number.
Displays the EtherNet/IP PLC type that is being read from.
Displays the IP address of the EtherNet/IP PLC in xxx.xxx.xxx.xxx format.
Displays the EtherNet/IP PLC tag or file name.
Displays the number of read messages transmitted to the EtherNet/IP PLC.
Displays the number of valid read responses received from the EtherNet/IP PLC.
Displays the number of read response errors received from the EtherNet/IP PLC.
Displays the Modbus Device ID that is being written to. This may be the device ID
of either the Shared Memory or a Modbus slave device.
Displays the function being used to perform the write operation.
Displays the Modbus address in Base 1 format.
Displays the number of write messages transmitted to the Shared Memory or
Modbus device.
Displays the number of valid write responses received from the Shared Memory or
Modbus device.
Displays the number of no path conditions. No path conditions occur when any of
the following occur:
• There is no valid destination to send the Modbus message.
- There are no serial ports configured as slave ports.
- There is no remote Modbus configuration for the device ID.
• If there is a remote Modbus configuration, the gateway is unable to connect to
the Modbus/TCP IP address.
Displays the number of write response errors received from the Shared Memory or
Modbus device.
Displays the number of unexpected write responses received from the Shared
Memory or Modbus device. These occur when an incorrect function code is received
in the response, or a response message is received when it is not expected.
Chapter 8. Diagnostic Menus - 115