Pepperl+Fuchs ICDM-RX/MOD Manual page 53

ICDM-RX/MOD User Manual
Diagnostics Menu
Modbus/TCP and Serial Modbus Master Statistics Page (Continued)
Remote Modbus/TCP
Device Timeouts
Unexpected Responses
From Modbus/TCP
Slaves
Error Responses from
Modbus/TCP Slave(s)
Unexpected Response
Function Codes From
Modbus/TCP Slave(s)
Invalid Response
Protocol Types From
Modbus/TCP Slave(s)
Failed Modbus/TCP
Connection Attempts to
Modbus/TCP Slave(s)
Modbus/TCP
Connection Problems
Unexpected Dropped
Connections
Displays the number of messages to remote devices that were determined to have
timed out by this gateway.
Displays the number of responses received when no response was expected.
Displays the number of responses received from Modbus/TCP slaves with errors
indicated. This may be caused by such things as:
• Device timeouts detected by slave Modbus/TCP device, such a gateway.
• Invalid device address.
• Invalid device ID.
• Invalid message data.
Displays the number of unexpected response function codes from Modbus/TCP
slaves. This occurs when a response was received with a different function code
than what was sent.
Displays the number of responses with invalid protocol errors. This occurs when a
response is returned with a protocol other than the Modbus/TCP protocol value of
zero.
Displays the number of failed Modbus/TCP connection attempts to the specified
PLC IP address.
Displays the number of Modbus/TCP connection attempt problems. This occurs
when the device responds and the connection is made, but there are problems
setting up the connection options.
The possible option problems include:
• Setting the TCP connection to TCP_NODELAY.
• Setting the socket connection to SO_OOBINLINE.
• Setting the socket connection to SO_KEEPALIVE.
Displays the number of Modbus/TCP connections that were unexpectedly
dropped.
53