Modbus slave and raw-data device settings – Comtrol Modbus TCP User Guide User Manual
Page 38
38 - Chapter 3. Embedded Configuration Pages
DeviceMaster UP Modbus/TCP User Guide: 2000447 Rev. I
Modbus Slave and Raw-Data Device Settings
3.3.4. Modbus Slave and Raw-Data Device Settings
Use the Modbus Slave and Raw-Data Device Settings area of the Edit Port Configuration page to set the
response timeout (ms) for Modbus slave and raw-data devices.
Modbus Slave and Raw-Data Device Settings
Response Timeout (ms)
Modbus Slave and Raw-Data Command/Response mode timeout
setting. The DeviceMaster UP will wait for the response(s) until this
time has elapsed before transmitting another message. The default is
250 ms.
Modbus Slaves Only
Lost Device Search Enable
(2- and 4-port, only)
If this is set, lost devices that were on this Modbus to-slave port will be
searched for on other Modbus to-slave ports that also have this option
set. For a discussion of this setting, see
Raw-Data Only
Raw-Data Message
Transfer Mode
If you select Data-Stream (default), the serial port will operate in Data-
Stream mode, see
If you select Command/Response, the serial port will operate in
Command/Response mode, see s
2.2.4.2. Command/Response Mode
Cmd/Resp Age Time,
Discard Responses After
(seconds)
The Age Time, or elapsed time, when responses destined for Modbus
interface(s) are discarded. This typically occurs when a Modbus
controller stops communicating and leaves a response in the response
queues.
The default is 10 seconds.
Cmd/Resp Expected
Responses Per Command
The number of responses expected for each transmitted command. The
default is 1.
Cmd/Resp Mode Response
To Modbus/TCP Based On
Method or returning responses to Modbus/TCP interfaces.
•
If you select IP-Address (default), all responses will be returned to
the IP-Address of the original command was received from. This
may the same or different TCP connection.
•
If you select TCP-Connection, all responses will be returned to the
same TCP connection the original command was received from.
Note: TCP-Connection is typically required when multiple controllers
are communicating from the same PLC or computer.
This image shows the
Lost Device Search Enable
option, which is only available on the 2- and 4-port models.