Connection status codes you may see include:
5 = Connection attempt timed out, unable to establish connection (usually means
remote device not connected or not reachable)
104 = Connection reset by peer
111 = Connection refused
113 = Connection aborted
114 = Network is unreachable
115 = Network interface not configured
116 = Connection timed out
118 = Host is unreachable
125 = Address not available
6.3 Reviewing the Packet Log
To further aid in diagnostics, a packet log is provided where you can see the last 200
or so raw messages. The message's unit or slave address, function code, and data are
displayed. RTU checksum and TCP header are omitted from the display to aid in clarity.
The most recent message is always displayed at the top, and elapsed time gives a
relative indication of when the message was sent. The Source/Dest column indicates
the "from" and "to". Content is the actual message sent.
Indicator
->
Request from master to
slave
<-
Response from slave
The example packet log below shows what the packet log can look like when accessing
RTU devices from TCP. The RTU slave address is indicated as "RTU x". There is no TCP
number in this case because the TCP Device Map is not used in this mode.
6. Error Counts and Packet Log
file:///C:/AAA_CSI/Literature/2021 User Guides/BB3-6101-MX-61 Use...
3 of 6
5/4/2021, 9:56 AM
