DEUTSCHMANN AUTOMATION UNIGATE CX Series User manual

Instruction Manual
Universal Fieldbus-Gateway
UNIGATE® CX
Deutschmann Automation GmbH & Co. KG
www.deutschmann.com | wiki.deutschmann.de

Manual Art.-No.: V3792E

2.10.19 UNIGATE® CX V. 1.4 3
Deutschmann Automation GmbH & Co. KG
1 Information on CE marking of the module . . . . . . . . . . . . . . . 8
1.1 EU Directive EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Scope of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Note installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Installation of the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 Working on switch cabinets . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Information for the machine manufacturer . . . . . . . . . . . . . . . 9
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 EU Machinery Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4 Hardware-design . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
4.1 Available types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Hardware structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3 UNIGATE® CX block diagram . . . . . . . . . . . . . . . . . . . . . . . 13
4.4 UNIGATE® CX design . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.5 Operation modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.1 RUN-operation (data exchange mode) . . . . . . . . . . . . . . . . . . . . . 16
4.5.2 Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5 Script-Programming . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1 What is a script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1.1 Function of the scripts in UNIGATE® CL . . . . . . . . . . . . . . . . . . . . 18
6 Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1 Overview of configurable buses . . . . . . . . . . . . . . . . . . . . . . 19
6.2 Configuration options of the available protocols . . . . . . . . . . . . . 20
6.2.1 Configuration over view without Ethernet resp. ModbusTCP interface . . . . . 20
6.2.2 Configuration overview with Ethernet resp. Modbus TCP interface . . . . . . 21
6.2.3 Configuration overview with two Ethernet resp. Modbus TCP interfaces . . . . 22
7 Implemented protocols in UNIGATE® CX . . . . . . . . . . . . . . . 23
7.1 Protocol: Transparent . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.1.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2 Protocol: Universal 232 . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.2.2 Fieldbus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.3 RS232 parameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.3.1 Start character (232 Start character) . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.3.2 Length 232 (232 Length) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.3.3 Data area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.3.4 Checksum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.3.5 End character (232 End character) . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.2.4 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.3 Protocol "CX (Pseudo)" . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.4 Protocol: 3964(R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.4.1 Data structure 3964R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.4.2 Protocol definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.4.3 Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4.3.1 Initiation of data communication by the low-priority user . . . . . . . . . . . . . . . 26

Deutschmann Automation GmbH & Co. KG
4UNIGATE
® CX V. 1.4 2.10.19
7.4.3.2 Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4.3.3 Timeout times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4.3.4 Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.4.3.5 Initiation of data communication by the high-priority user . . . . . . . . . . . . . . . 26
7.4.4 Protocol type 3964 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5 Protocol: MODBUS-RTU . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
7.5.2 UNIGATE® as MODBUS-Master . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.2.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.5.2.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.5.3 UNIGATE® as MODBUS-Slave . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.5.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.5.3.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.5.3.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.6 Protocol Modbus ASCII Master/Slave . . . . . . . . . . . . . . . . . . 28
7.7 Protocol „Universal Modbus RTU Slave“ . . . . . . . . . . . . . . . . . 28
7.7.1 Data structure on the fieldbus side e.g.: PROFIBUS . . . . . . . . . . . . . . 29
7.7.1.1 Example: FC1 + FC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.7.1.2 Example: FC3 (Read Holding Register) + FC4 (Read Input Register) . . . . . . . . 30
7.7.1.3 Example: Write Single Coil FC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.7.1.4 Example: Write Single Register FC6 . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.7.1.5 Example: Force multiple coils FC 15 . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.7.1.6 Example: Preset multiple register FC16 . . . . . . . . . . . . . . . . . . . . . . . . 33
7.8 Protocol „Universal Modbus RTU Master“ . . . . . . . . . . . . . . . . 34
7.8.1 Data structure Fieldbus side (e.g. PROFIBUS): . . . . . . . . . . . . . . . . . 34
7.8.2 Data structure Application side: . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.8.3 Configuration: via Wingate since wcf Datei Version 396 . . . . . . . . . . . . . 35
7.8.3.1 Example: Read coil status FC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.8.3.2 Example: Read input status FC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.8.3.3 Example: Read multiple register FC3 . . . . . . . . . . . . . . . . . . . . . . . . . 38
7.8.3.4 Example: Read input registers FC4 . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.8.3.5 Example: Force single coil FC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7.8.3.6 Example: Preset single register FC6 . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.8.3.7 Example: Force multiple coils FC15 . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.8.3.8 Example: Preset multiple register FC16 . . . . . . . . . . . . . . . . . . . . . . . . 41
7.9 Protocol „Universal Modbus ASCII Master/Slave“ . . . . . . . . . . . . 42
7.10 Protocol Modbus TCP client encapsulation . . . . . . . . . . . . . . . . 43
7.10.1 Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.10.1.1 UNIGATE® CL: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.10.1.2 UNIGATE® CX: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
8 Optional bus parameter . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.1 The trigger byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.2 The length byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.3 Swap word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2.10.19 UNIGATE® CX V. 1.4 5
Deutschmann Automation GmbH & Co. KG
9 Fieldbus parameters / Ethernet parameters . . . . . . . . . . . . . . 46
10 Hardware connections, switches and LEDs . . . . . . . . . . . . . 47
10.1 Device label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
10.2.1 Connector supply voltage and DEBUG-interface 1 . . . . . . . . . . . . . . . 47
10.2.2 Connector output voltage and DEBUG-interface 2 . . . . . . . . . . . . . . . 48
10.3 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
10.4 LEDs, switches, bus connection . . . . . . . . . . . . . . . . . . . . . 48
10.5 UNIGATE® CX connection cable . . . . . . . . . . . . . . . . . . . . . 48
11 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.2.1.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.2.1.2 Equipotential bonding connection. . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.2.2 Communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.2.2.1 CANopen Slave, CANopen Master / CAN Layer 2 . . . . . . . . . . . . . . . . . . 50
11.2.2.2 DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.2.2.3 EtherCAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.2.2.4 EtherNet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.2.2.5 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.2.2.6 LONWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.2.7 MPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.2.8 PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.2.9 PROFINET-IO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.3 Line routing, shield and measures to combat interference voltage . . . . . . . 51
11.2.4 General information on line routing . . . . . . . . . . . . . . . . . . . . . . . 52
11.2.4.1 Shielding of lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
12 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
12.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
13 Commissioning guide . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.4 Dimensional drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.4.1 UNIGATE® CX (all versions without CANopen Slave, CANopen Master,
CAN Layer 2, MPI or PROFIBUS DP) . . . . . . . . . . . . . . . . . . . . . 55
13.4.2 UNIGATE® CX (all versions with CANopen Slave, CANopen Master,
CAN Layer 2, MPI or PROFIBUS DP) . . . . . . . . . . . . . . . . . . . . . 56
13.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
13.6 Fieldbus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
13.7 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 56
13.8 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Deutschmann Automation GmbH & Co. KG
6UNIGATE
® CX V. 1.4 2.10.19
14 Service Interface (RS232) . . . . . . . . . . . . . . . . . . . . . . . . 57
14.1 Service interface (RS232) - Connection . . . . . . . . . . . . . . . . . 57
14.2 Service interface (RS232) – Access . . . . . . . . . . . . . . . . . . . 58
15 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
15.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
15.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . . 61
16 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
16.1 Explanations of the abbreviations . . . . . . . . . . . . . . . . . . . . . 62
16.2 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2.10.19 UNIGATE® CX V. 1.4 7
Deutschmann Automation GmbH & Co. KG
Disclaimer of liability
We have checked the contents of the document for conformity with the hardware and software
described. Nevertheless, we are unable to preclude the possibility of deviations so that we are
unable to assume warranty for full compliance. The information given in the publication is,
however, reviewed regularly. Necessary amendments are incorporated in the following editions.
We would be pleased to receive any improvement proposals which you may have.
Copyright
Copyright (C) Deutschmann Automation GmbH & Co. KG 1997 - 2019. All rights reserved.
This document may not be passed on nor duplicated, nor may its contents be used or disclosed
unless expressly permitted. Violations of this clause will necessarily lead to compensation in
damages. All rights reserved, in particular rights of granting of patents or registration of
utility-model patents.

Information on CE marking of the module Deutschmann Automation GmbH & Co. KG
8UNIGATE
® CX V. 1.4 2.10.19
1 Information on CE marking of the module
1.1 EU Directive EMC
The following applies to the module described in this User Manual:
Products which bear the CE mark comply with the requirements of EU Directive „Electromagnetic
Compatibility“ and the harmonised European Standards (EN) listed therein.
The EU Declarations of Conformity are available at the following location for perusal by the
responsible authorities in accordance with the EU Directive, Article 10:
Deutschmann Automation GmbH & Co. KG, Carl-Zeiss-Str. 8, 65520 Bad Camberg, Germany
1.2 Scope of application
The modules are designed for use in the industrial sector and comply with the following
requirements
1.3 Note installation guidelines
The module complies with the requirements if you
1. comply with the installation guidelines described in the User Manual when installing and ope-
rating the module.
2. also follow the rules below on installation of the equipment and on working on switch cabinets.
1.4 Installation of the unit
Modules must be installed in electrical equipment rooms/areas or in enclosed housings (e.g.
switch boxes made of metal or plastic). Moreover, you must earth the unit and the switch box
(metal box) or at least the top-hat rail (plastic box) onto which the module has been snapped.
1.5 Working on switch cabinets
In order to protect the modules against static electrical discharge, the personnel must discharge
themselves electrostatically before opening switch cabinets or switch boxes.
Scope of application Requirement applicable to
Emitted interference Interference immunity
Industry EN 55011, cl. A (2007) EN 61000-6-2 (2005)

2.10.19 UNIGATE® CX V. 1.4 9
Deutschmann Automation GmbH & Co. KG Information for the machine manufacturer
2 Information for the machine manufacturer
2.1 Introduction
The UNIGATE® module does not constitute a machine as defined by the EU "Machinery“
Directive. Consequently, the module does not have a Declaration of Conformity in relation to the
EU Machinery Directive.
2.2 EU Machinery Directive
The EU Machinery Directive stipulates the requirements applicable to a machine. The term
"machine" is taken to mean a totality of connected parts or fixtures (see also EN 292-1, Para-
graph 3.1).
The module is a part of the electrical equipment of the machine and must thus be included by the
machine manufacturer in the Declaration of Conformity process.

Introduction Deutschmann Automation GmbH & Co. KG
10 UNIGATE® CX V. 1.4 2.10.19
3 Introduction
In the field of automatic control many different Fieldbuses and Industrial Ethernet became estab-
lished worldwide. Again and again the ask of interconnecting these incompatible networks
comes up. The NIGATE® CX-series was created exactly for that task. The series contains Field-
bus-Slave as well as Industrial Ethernet versions.
The UNIGATE® CX is designed as DIN-rail module and contains the selected Fieldbuses or
Ethernet in the mechanical variant carried out in the respective standard. Internally the product is
realized by using two UNIGATE® CL-modules. By this modular structure all Fieldbus- and Ether-
net-versions can be supplied, provided that the respective CL-modules are available. The num-
ber of available versions is growing steadily by the continuous development of new CL-modules
e. g. in the Industrial Ethernet field.
With the UNIGATE® CX series, the data exchange can be realized via the configuration of the
implemented protocols or via the programming of a script. Another possibility is the combination
of implemented protocol and a script. The implemented protocols can be configured with the con-
figuration software WINGATE.
Scripts can be programmed with the software Protocol Developer.

2.10.19 UNIGATE® CX V. 1.4 11
Deutschmann Automation GmbH & Co. KG Hardware-design
4 Hardware-design
The UNIGATE® CX acts as gateway between two bus- respectively Ethernet systems. Both bus
connections are usually realized as slave. Excluded are CANopen (master) as well as Ethernet
or ModbusTCP (client). Each bus can be operated by a standard-compliant master.
4.1 Available types
UNIGATE® CX has a modular structure which makes any desired combination of fieldbuses pos-
sible. The following devive types can be realized:

Hardware-design Deutschmann Automation GmbH & Co. KG
12 UNIGATE® CX V. 1.4 2.10.19
From the above table you can see that all types can be combined, such as DeviceNet to 
DeviceNet in order to interconnect two autonomous DeviceNet-networks.
4.2 Hardware structure
In order to have the possibility to interconnect different fieldbuses UNIGATE® CX consists of sin-
gle components that can be combined with each other. These components are in detail:
•UNIGATE® CL 1 for fieldbus side A
•UNIGATE® CL 2 for fieldbus side B
The exact internal structure is not relevant to the order since only the buses that are to be inter-
connected have to be mentioned and you will receive a complete device.
Fieldbus/Ethernet B
Fieldbus/Ethernet A
CANopen
(Slave),
CANopen
(Master),
CAN Layer
2
DeviceNet EtherCAT Ethernet EtherNet/IP LONWorks Modbus
TCP MPI Profibus Profinet

CANopen
(Slave),
CANopen
(Master),
CAN Layer 2

DeviceNet 
EtherCAT 
Ethernet 
EtherNet/IP 
LONWorks 
Modbus
TCP 
MPI 
Profibus 
Profinet 

2.10.19 UNIGATE® CX V. 1.4 13
Deutschmann Automation GmbH & Co. KG Hardware-design
4.3 UNIGATE® CX block diagram

Hardware-design Deutschmann Automation GmbH & Co. KG
14 UNIGATE® CX V. 1.4 2.10.19
4.4 UNIGATE® CX design
4.5 Operation modes
4.5.1 RUN-operation (data exchange mode)
In the ex-works condition the device is set to RUN-operation.
In RUN-operation it is possible to use the Debug-interfaces of the UNIGATE® CLs.
With these interfaces it is possible to execute a Script step-by-step and in a normal case they are
only necessary for developing a Script. Furthermore the device can be configured through these
interfaces. To do so, the software WINGATE is used ("Extras" -> "Upload_Config_Debug" or
"Download_Config_Debug")
The Debug-interfaces are connected with X1 pin 3 + 4 or X2 pin 3 + 4.
Further information on how to use the Debug-interface can be found in the instruction manual
UNIGATE® CL for the respective Fieldbus.
4.5.2 Test mode
Setting of the test mode
The test mode is set by bringing the switches S4 and S5 in position "E". All other switches will not
be taken into consideration for the setting of the test mode. Now the Gateway has to be restarted
with these settings (by a short disconnection from the power supply).
In the test mode the Gateway always operates with the settings 9600 baud, no parity, 8 databits
and 1 stopbit.
The test mode may be helpful to integrate the Gateway in the relevant environment.

2.10.19 UNIGATE® CX V. 1.4 15
Deutschmann Automation GmbH & Co. KG Hardware-design
Mode of operation of the test mode
After the restart in the test mode the Gateway will be sending the values 0-15 in hexadecimal
representation ("0".."F") in ASCII-coding on the serial side (Debug-interface) every second.
Simultaneously the same values are issued binary on the fieldbus-interface.
In this mode the State-LED on the RS-side will be flashing red, the "Error No/Select ID" LEDs will
be displaying the value in a binary way, that is issued that moment. Additionally each character
that is received at one of the interfaces will also be output at the same interface as a local echo.
On the fieldbus-side only the first byte will be used for the local echo, that means on receiving as
well as on transmitting only the first byte of the bus data is looked at, the other bus data do not
change compared to the last data.

Script-Programming Deutschmann Automation GmbH & Co. KG
16 UNIGATE® CX V. 1.4 2.10.19
5 Script-Programming
5.1 What is a script?
A script is a sequence of commands, that are executed in that exact order. Because of the fact
that also mechanisms are given that control the program flow in the script it is also possible to
assemble more complex processes from these simple commands.
The script is memory-oriented. It means that all variables always refer to one memory area.
While developing a script you do not have to take care of the memory management though. The
Protocol Developer takes on this responsibility for you.
5.1.1 Function of the scripts in UNIGATE® CL
The scripts handle the data exchange between the two UNIGATE® CLs. Here the data of fieldbus
1 is edited in the CL 1 and transmitted to the CL 2 via an RS-connection. On account of the field-
buses’ complexity and the multitude of resulting versions we are not going into details at this
point. For further questions concerning scripts, please contact us directly.

2.10.19 UNIGATE® CX V. 1.4 17
Deutschmann Automation GmbH & Co. KG Protocol Configuration
6 Protocol Configuration
The UNIGATE® CX is delivered with the script "Universalscript Deutschmann". The delivery state
is with transparent data exchange, so only the fieldbus-specific parameters must be configured.
The fieldbus-specific parameters include, for example, data exchange ( byte), Fieldbus length
byte (Chapter 7.11, The length byte), Swap word (Chapter 7.12, Swap word) and the settings for
the IP address for the fieldbus variants.
The configuration takes place in the data exchange mode with the software WINGATE (Tools ->
"Upload_Config_Debug" or "Download_Config_Debug").
Further configuration options can be found in the following tables.
6.1 Overview of configurable buses
Configuration Programming (Script)
CANopen (Slave) 
CANopen (Master) 
CAN Layer 2 
DeviceNet 
EtherCAT 
Ethernet 
EtherNet/IP 
LONWorks 
ModbusTCP 
MPI 
PROFIBUS 
PROFINET 

Protocol Configuration Deutschmann Automation GmbH & Co. KG
18 UNIGATE® CX V. 1.4 2.10.19
6.2 Configuration options of the available protocols
The configuration options of the protocols are highlighted with green checkmarks in the
tables. For each application example, you will find a diagram for graphical illustration.
6.2.1 Configuration over view without Ethernet resp. ModbusTCP interface
UNIGATE CX
CX (Pseudo)
data fieldbus
data fieldbus
Modbus
RTU slave
4=0; S5=1
Modbus RTU Slave ID=1
data fieldbus
data filedbus
Fieldbus
Master
UNIGATE Side A
/
UNIGATE Side B
CX (Pseudo)
S4=0; S5=0
Fieldbus
Master
S4=0; S5=0

2.10.19 UNIGATE® CX V. 1.4 19
Deutschmann Automation GmbH & Co. KG Protocol Configuration
6.2.2 Configuration overview with Ethernet resp. Modbus TCP interface
UNIGATE CX
Modbus TCP
client
encapsulation
Modbus TCP response
Modbus TCP request
Modbus
RTU slave
S4=0; S5=1 Modbus RTU Slave ID=1
data fieldbus
data filedbus
Fieldbus
Master
Modbus
TCP Server
Modbus RTU
Slave
Ethernet (ModbusTCP) / UNIGATE Seite B
Universal
Modbus
RTU Master
Modbus RTU response
Modbus RTU request
S4=0; S5=0
S4=0; S5=1
Modbus RTU Slave ID=1 (example)

Protocol Configuration Deutschmann Automation GmbH & Co. KG
20 UNIGATE® CX V. 1.4 2.10.19
6.2.3 Configuration overview with two Ethernet resp. Modbus TCP 
interfaces
UNIGATE CX
TCP Server
TCP Client
S4=0; S5=1 Modbus RTU Slave ID=1
data fieldbus
Universal
232
data filedbus
TCP Client
Ethernet (ModbusTCP) A
/
Ethernet (ModbusTCP) B
data fieldbus
data fieldbus
S4=0; S5=0 Universal
232
TCP Server
S4=0; S5=0