
2.10.19
UNIGATE
®
CX V. 1.4
41
Deutschmann Automation GmbH & Co. KG
Implemented protocols in UNIGATE® CX
7.10 Protocol Modbus TCP client encapsulation
The "Modbus TCP client encapsulation" fieldbus transport protocol can only be used in conjunc-
tion with the "Modbus RTU Slave" application transport protocol.
7.10.1 Function
7.10.1.1 UNIGATE
®
CL:
•
Ethernet TCP/IP (Modbus TCP) transport protocol: Modbus TCP client encapsulation
•
Application protocol: Modbus RTU Slave (Modbus RTU Slave ID adjusted via rotary coding
switch S4+S5)
Description:
The Modbus requests of the Modbus RTU Master connected to the application side are forwar-
ded device internally via the application protocol "Modbus RTU Slave" to the fieldbus transport
protocol "Modbus TCP client encapsulation". So that the Modbus requests are transmitted to the
Modbus TCP server (Target IP address). The Modbus Response of the Modbus TCP server is
then transferred to the Modbus RTU Master in reverse order.
Note:
A valid Modbus RTU slave ID (1 .. 247) must be set via the two rotary coding switches S4
and S5. The ID must match the one in the Modbus requests.
Example:
UNIGATE CL-FE or ModTCP S4 + S5 = 01. Then "1" has to be displayed in the record
in Modbus Request parameter "Req. ... Slave ID".
Summary of Contents for UNIGATE CX Series
Page 2: ...Manual Art No V3792E...