Implemented protocols in UNIGATE® CX
Deutschmann Automation GmbH & Co. KG
42
UNIGATE
®
CX V. 1.4
2.10.19
7.10.1.2 UNIGATE
®
CX:
•
FE or ModTCP side: Ethernet TCP/IP (Modbus TCP) Transport protocol: Modbus TCP client
encapsulation
•
FE or ModTCP side: Application protocol: Modbus RTU Slave (set Modbus RTU Slave ID via
rotary coding switches S4+S5)
•
2. Fieldbus: Application protocol: Universal Modbus RTU Master (up to24 Modbus Requests
configurable)
Description:
The Modbus requests are configured in the "Universal Modbus RTU Master" application protocol.
These are then passed on internally via the application protocol "Modbus RTU Slave" to the field-
bus 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 Mod-
bus TCP server is then transferred in reverse order to the "Universal Modbus RTU Master" appli-
cation protocol. Depending on the function code (for example, FC3), the data is then written to
the relevant fieldbus or read by the fieldbus.
Note:
A valid Modbus RTU ID (1 ... 247) must be set via the two rotary coding switches S4 and
S5. The ID must match the one in the configured 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...
