For this mode, you should also enter the number of server connections to support.
This will default to one. If more than one Modbus TCP client will be polling RTU devices
at the same time through this gateway, then increase this number in order to allow
more connections. If your TCP client opens and closes a different connection for each
request (considered bad behavior by Modbus protocol but some devices do it anyway)
then you may need to increase this number to sustain reliable connections. The
gateway must be restarted after changing the number of server connections. (Note
that setting the connection count substantially higher than what is actually in use will
result in increased latency due to the gateway taking time to check for traffic on all of
the unused connections).
IMPORTANT: Set timeout to something long enough for the device. If too short, the
gateway will not wait long enough for a response from the Modbus slave device, and
the result will be a lot of "no response" errors from the device even though the device
is perfectly functional.
IMPORTANT: The timeout you set in your Modbus TCP client must be longer than the
timeout set on this page. If the RTU slave queried times out, it will be tabulated as a
no-response error here in the gateway, but the gateway will return an exception 11 to
the TCP client telling it that the RTU slave timed out. If your TCP client timeout is
shorter than the timeout set above, then your client will not receive that exception
report.
You do not need to do anything on the TCP Device Map page for this mode.
4.2 How It Works
When the gateway receives a request from the TCP device, the gateway will remove
the TCP header, add an RTU checksum, and transmit the request on the RTU network.
The gateway will then wait for a response from the RTU slave.
If the slave does not respond, the gateway will return exception code 11 to the
TCP client (master). Exception code 11 is defined by Modbus protocol to mean
"Gateway target device failed to respond". This is how a gateway reports a timeout or
no-response error back to the requesting TCP device.
4. Accessing RTU Devices from TCP
file:///C:/AAA_CSI/Literature/2021 User Guides/BB3-6101-MX-61 Use...
2 of 3
5/4/2021, 9:56 AM