IMPORTANT: If you observe timeouts (no-response errors) at your Modbus RTU master
or Modbus TCP client, but do not see no-response errors tabulated here, then the
timeout setting in your master or client may be too short. If the device on the other
side of this gateway fails to respond, it will be logged as a no-response error here, and
your master/client should receive an exception 11 report. You should never see just a
timeout on the master/client side of this gateway. Refer to section 4 or 5 as applicable
for additional notes about timeout settings.
6.2 Reviewing TCP Device Status
When accessing TCP devices from RTU, an additional diagnostic is available on
the TCP Device Map page. If a TCP device has failed to connect or failed to respond, its
status in the Status column will be some number other than zero (0=no error
detected). Status codes will normally clear on their own, but you can also force them
to clear by clicking the Reset button. If the condition still exists, the status code will
return to its non-zero value upon the next attempt to connect.
6. Error Counts and Packet Log
file:///C:/AAA_CSI/Literature/2021 User Guides/BB3-6101-MX-61 Use...
2 of 6
5/4/2021, 9:56 AM