DEUTSCHMANN AUTOMATION UNIGATE CM - PROFINET 2Port User manual

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

Manual Art.-No.: V4013E

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 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 manufacturers . . . . . . . . . . . . . . 9
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 EU Machinery Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1 UNIGATE®CM software flow-chart . . . . . . . . . . . . . . . . . . . . 11
3.2 UNIGATE®block diagram . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 UNIGATE®CM application diagram . . . . . . . . . . . . . . . . . . . 12
4 Operation modes of the Gateway . . . . . . . . . . . . . . . . . . . 13
4.1 Configuration mode (config mode) . . . . . . . . . . . . . . . . . . . . 13
4.2 Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Data exchange mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 RS-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 RS-interfaces at the UNIGATE®CM . . . . . . . . . . . . . . . . . . . 15
5.2 Buffer sizes at the UNIGATE®CM . . . . . . . . . . . . . . . . . . . . 15
5.3 Framing Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6 The Debug-interface . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1 Overview of the Debug-interface . . . . . . . . . . . . . . . . . . . . . 16
6.2 Starting in the Debug-mode . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3 Communication parameter for the Debug-interface . . . . . . . . . . . . 16
6.4 Possibilities with the Debug-interface . . . . . . . . . . . . . . . . . . . 16
6.5 Commands of the Debug-interface . . . . . . . . . . . . . . . . . . . . 16
7 Mode of operation of the system . . . . . . . . . . . . . . . . . . . 18
7.1 General explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.3 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.4 Possible data lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.5 Startup phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8 Generating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1 What is a Script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2 Memory efficiency of the programs . . . . . . . . . . . . . . . . . . . . 19
8.3 What can you do with a Script device? . . . . . . . . . . . . . . . . . . 19
8.4 Independence of buses . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.5 Further settings at the Gateway . . . . . . . . . . . . . . . . . . . . . . 19
8.6 The use of the Protocol Developer . . . . . . . . . . . . . . . . . . . . 20
9 FTP-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.1 Script-update via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.2 System configuration update via FTP . . . . . . . . . . . . . . . . . . . 21
10 WEB-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.1 Server Side Includes (SSI) . . . . . . . . . . . . . . . . . . . . . . . . 22

Deutschmann Automation GmbH & Co. KG
4 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
10.2 HTML-Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
11 File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
12 Hardware ports, switches and LEDs . . . . . . . . . . . . . . . . . . 25
12.1 Device labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . . . 25
12.2.2 Connector supply voltage and DEBUG-interface . . . . . . . . . . . . . . . .26
12.2.3 CANopen interface connector . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.2.4 PROFINET-connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.2.5 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
12.3 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
12.3.1 LED "Power/State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
12.3.2 LEDs 1 / 2 / 4 / 8 (Error No. / Select ID) . . . . . . . . . . . . . . . . . . . . .28
12.3.3 LED "State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.3.4 LED "Bus State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.3.5 LED "Bus Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.3.6 LED "Link / Act. P1" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.3.7 LED "Link / Act. P2" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.4.1 Termination Rx 422 + Tx 422 (serial interface) . . . . . . . . . . . . . . . . .29
12.4.2 Rotary coding switches S4 + S5 (serial interface) . . . . . . . . . . . . . . . . 30
12.4.3 CANopen termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
13 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.1 Error handling at UNIGATE®CM . . . . . . . . . . . . . . . . . . . . . 31
13.1.1 Error on the extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
14 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
14.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
14.2.1.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.2.1.2 Equipotential bonding connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14.2.2 PROFINET-IO communication interface . . . . . . . . . . . . . . . . . . . . .34
14.2.3 Line routing, shield and measures to combat interference voltage . . . . . . .34
14.2.4 General information on line routing . . . . . . . . . . . . . . . . . . . . . . . 34
14.2.4.1 Shielding of lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
15 Firmware update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
16 Implemented protocols in UNIGATE®CM . . . . . . . . . . . . . . . 37
16.1 Implemented protocols (Transport protocols at the CM interface) . . . . 37
16.2 Configuration options for the individual transport protocol . . . . . . . . 38
16.2.1 Possibilities on the CANopen side . . . . . . . . . . . . . . . . . . . . . . . .38
16.2.2 Possibilities on the fieldbus side . . . . . . . . . . . . . . . . . . . . . . . . .38
16.3 Operation of the transport protocols . . . . . . . . . . . . . . . . . . . 39
16.3.1 CANopen Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 5
Deutschmann Automation GmbH & Co. KG
16.3.1.1 Configuration of the mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
16.3.1.2 Node guarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
16.3.1.3 Displaying the node guarding states . . . . . . . . . . . . . . . . . . . . . . . . . 41
16.3.1.4 Emergency Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.3.1.5 Gateway control byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16.3.1.6 Bit 7 (MSB): EMCY toggle bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.3.1.7 Bit 6: set operational toggle bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.3.1.8 Bit 5: RTR - Request to response . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.3.1.9 Gateway error byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.3.1.10 SDO Obj Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.3.1.11 Slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.3.1.12 CAN Baud rate and address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.3.1.13 Starting phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.3.1.14 Data cycle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.3.2 Layer 2 11Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
16.3.3 Universal (L2 11Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
16.3.4 Universal (L2 11Bit) with COB-ID used . . . . . . . . . . . . . . . . . . . . . 47
16.3.5 Universal (L2 11/29Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
16.3.6 Universal (L2 11/29Bit) with COB-ID used . . . . . . . . . . . . . . . . . . . 49
16.3.7 L2 11Bit (Tgl+FBlen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
16.4 Delivery status (factory setting) . . . . . . . . . . . . . . . . . . . . . . 49
16.5 Trigger byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
16.6 Length Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
16.7 Swap word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
17 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
17.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
17.1.1 Interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
18 Commissioning guide . . . . . . . . . . . . . . . . . . . . . . . . . 52
18.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
18.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
18.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
18.4 Dimensional drawing UNIGATE®CM - PROFINET-IO . . . . . . . . . . 52
18.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
18.6 PROFINET address-assignment . . . . . . . . . . . . . . . . . . . . . 53
18.7 PROFINET device name . . . . . . . . . . . . . . . . . . . . . . . . . 53
18.8 PROFINET connection . . . . . . . . . . . . . . . . . . . . . . . . . . 53
18.9 Setting the CANopen address and baudrate . . . . . . . . . . . . . . . 53
18.10 CANopen connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
18.11 Connection to the process device . . . . . . . . . . . . . . . . . . . . . 53
18.12 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
18.13 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 53
18.14 Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
18.15 Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
19 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
19.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
19.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . . . 55

Deutschmann Automation GmbH & Co. KG
6 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
20 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
20.1 Explanations of the abbreviations . . . . . . . . . . . . . . . . . . . . . 56
20.2 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 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 – 2017. 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
8 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
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 harmonized 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-Straße 8, 65520 Bad Camberg, Ger-
many.
1.2 Scope of application
The modules are designed for use in the industrial sector and comply with the following
requirements.
Scope of application Requirement applicable to
Emitted interference Interference immunity
Industry EN 55011, cl. A (2007) EN 61000-6-2 (2005)
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
operating 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.

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 9
Deutschmann Automation GmbH & Co. KG Information for the machine manufacturers
2 Information for the machine manufacturers
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®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
3 Introduction
The UNIGATE®CM-PROFINET 2Port module serves to adapt a interface to PROFINET net-
works. The device features 2 PROFINET ports - one port can for instance be used as an outgo-
ing PROFINET port.Talking of PROFINET is automatically connected with the 100 Mb/s-version,
full-duplex and switched Ethernet. The terminal unit’s protocol is converted in the UNIGATE®via
a Script.
The module CM-PROFINET essentially consists of the following hardware components:
•Electrically isolated PROFINET-interface
•Processor
•RAM and FLASH
•Serial interface (RS232, RS485 and RS422)
•Electrically isolated interface to CANopen
Conceptual
In the further course of this manual, the term "Fieldbus" is frequently used. In
these cases this applies to the PROFINET interface.

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 11
Deutschmann Automation GmbH & Co. KG Introduction
3.1 UNIGATE®CM software flow-chart

Introduction Deutschmann Automation GmbH & Co. KG
12 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
3.2 UNIGATE®block diagram
The following picture shows a typical UNIGATE®-module design.
3.3 UNIGATE®CM application diagram
The following graph shows a typical connection scheme.

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 13
Deutschmann Automation GmbH & Co. KG Operation modes of the Gateway
4 Operation modes of the Gateway
4.1 Configuration mode (config mode)
The configuration mode serves to configure the Gateway. The following adjustments are possible
in this mode.
•Loading a Script
•Updating the firmware (only CL-basis)
•Configuring the Gateway (via WINGATE Version V2.85 or higher)
The Gateway will be starting in this mode in case both switches S4 as well as S5 are set on posi-
tion "F" when switching on the Gateway. Right after switching on the Gateway in the configura-
tion mode it will be sending its starting message, that looks analog with the following message:
RS-PN-CL (RS+Ext.Board) V2.4.8[41] (c)dA[66,666MHz] Switch=0xFF
Script(C:5719/32512,V:4687/16384)="Universalscript Deutschmann CM" Author="G/S"
Version="V1.0.3" Date=18.01.2016 SN=47110211 IP=10.10.10.10 MAC=00-14-11-15-1A-53
Name=""
Ext-Board: (CM-IO-DICNET) V1.4 (c)dA 47110002
CAN[MapOff]: ID(11/29)=1 Baud=500000 LSS-ID=1, LSS-BaudIdx=2
In the configuration mode the Gateway always operates with the settings 9600 Bauds, no Parity,
8 Databits and 1 Stopbit, the RS-State LED will always be flashing red, the "Error No/Select ID"
LEDs are of no account for the user. All software revisions contain the configuration mode.
4.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, for instance
to test the parameters of the RS-interfaces.
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 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.
4 Bytes are output on the CANopen interface:
1 byte: Echo of the first received byte via CAN
2 byte: Read back byte IO8 ! Option
3. byte: value only for internal purposes
4. byte: Output to IO8 ! Option

Operation modes of the Gateway Deutschmann Automation GmbH & Co. KG
14 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
4.3 Data exchange mode
The Gateway has to be in the data exchange mode, so that a data exchange between the
CANopen-side of the Gateway and the fieldbus is possible. As long as the Gateway is not in the
configuration-, test-, firmware update or debug mode, the data exchange mode is active. In the
data exchange mode the Gateway will execute the downloaded Script UniversalScript_CM
(ScriptName „Universalscript Deutschmann CM“).

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 15
Deutschmann Automation GmbH & Co. KG RS-interface
5 RS-interface
5.1 RS-interfaces at the UNIGATE®CM
The UNIGATE®CM - PROFINET-IO has the interfaces RS232, RS422 and RS485 available.
The hardware always features a DEBUG-interface, see chapter 6.
5.2 Buffer sizes at the UNIGATE®CM
UNIGATE®CM features at the serial side a buffer with the size of 1024 bytes for input data and
output data each.
The FIFO of the application interface (RS-interface) can be changed in any Gateway form Script
revision 26 on, that is capable for Script. For it please check in the Protocol Developer under
"Device Control" - "Hardware".
5.3 Framing Check
The length of the stop bit received by the Gateway is checked through the function "Framing
Check". Here the stop bit generated by the Gateway is always long enough, so that connected
participants can evaluate the stop bit.
Please be aware that the function "Framing Check" becomes effective only in case of 8 data bit
and the setting "No parity".
An error is detected and indicated by the Error LEDs in case the stop bit does not show the
length 1 bit during the activated check.
The possible setting for this parameter can be controlled by the Script (see online help from
Protocol Developer). The presetting for the "Stop Bit Framing Check" is "enabled".

The Debug-interface Deutschmann Automation GmbH & Co. KG
16 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
6 The Debug-interface
6.1 Overview of the Debug-interface
The UNIGATE®CM features a Debug-interface, that allows a step-by-step processing of a
Script. Normally this interface is only required for the development of a Script.
6.2 Starting in the Debug-mode
When applying power to the UNIGATE®(power up) the firmware will output the binary character
0 (0x00) after a self-test was carried out on this interface. If the UNIGATE®receives an
acknowledgement via this interface within 500 ms, it is in the Debug-mode. The
acknowledgement is the ASCII-character O (0x4F).
With the start in the Debug-mode the further execution of Script commands will be put to a stop.
6.3 Communication parameter for the Debug-interface
The Debug-interface is always operating with 9600 baud, no parity, 8 data bit, 1 stop bit. It is not
possible to change this parameter in the Protocol Developer. Please consider the fact that these
settings have to be in accordance with those of the PC-COM-interface and that the flow control
(protocol) has to be set on „none“ there.
6.4 Possibilities with the Debug-interface
Usually the Protocol Developer is connected to the Debug-interface. With it a step-by-step pro-
cessing of a Script, monitoring jumps and decisions and looking at memory areas is possible.
Moreover breakpoints can be set. It basically possesses all characteristics a software-develop-
ment tool is typically supposed to have. However, it is also possible to carry out a Scrip-update
via this interface.
From Script version [27] on you can also output data with the Script command
"SerialOutputToDebugInterface". Please also pay attention to the remark in the manual
’Protocol Developer’.
6.5 Commands of the Debug-interface
The commands for the use of the Debug-interface are described in the instruction manual
Protocol Developer.
Restriction:
•Script commands that make a data exchange with the Ext. Card are not supported in Debug
mode.
•The command „SerialOutputToDebugInterface“, referred to in chapter 6.4, as well as
the command „SerialInDebugInterface“, is not supported.
•Redirection of the Debug interface to the Application interface (X1).
With the script command „ScriptStartBehaviour(DbgOverApl);“ debugging to con-
nector X1 of the application is possible again, so that the commands for the Ext. Cards are
supported.
Note: The script command „ScriptStartBehaviour(DbgOverApl);“ must be placed
directly after the script info.
First, the script must be loaded, because only after a reboot it is possible to debug via the appli-
cation interface. If the command is taken out, the script has to be started once before you can
debug on the Debug interface.

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 17
Deutschmann Automation GmbH & Co. KG The Debug-interface
If debugging is redirected to the application, no script or command that wants to carry out com-
munication via the application interface is supported.
These are e.g.: SendRS and ReceiveSomeCharRS.

Mode of operation of the system Deutschmann Automation GmbH & Co. KG
18 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
7 Mode of operation of the system
7.1 General explanation
Communication can be split into seven layers, Layer 1 to Layer 7, in accordance with the
ISO/OSI model.
The Deutschmann Automation Gateways convert Layers 1 and 2 of the customized bus system
(RS485 / RS232 / RS422) to the corresponding Fieldbus system. Layers 3 and 4 are being cov-
ered by the UDP/IP-protocol, TCP/IP-protocol. The Layers 5 and 6 are blank. Layer 7 is con-
verted in accordance with chapter 7.3.
7.2 Interfaces
The Gateway features a CANopen and fieldbus interface as well as the serial interfaces RS232-,
RS422- and RS485.
7.3 Data exchange
All data is transferred by the Gateway in dependence of the downloaded Script.
7.4 Possible data lengths
The table below shows the maximum transferable data:
PROFINET Input data max. 1440 bytes variable: here maximum value
Output data max. 1440 bytes variable: here maximum value
CM
With Universal script CM the data length on the CANopen-side is dependant on the protocol
CANopen Mapping
Layer 2 11Bit
Universal (L2 11Bit)
Universal (L2 11Bit) with
COB-ID used
L2 11Bit (Tgl+Fblen
Universal (L2 11/29Bit)
Universal (L2 11/29Bit) with COB-ID
used
In- and Output data maximum 10 Byte, of which a
maximum of 8 Byte is payload
maximum 12 Byte, of which a maximum
of 8 Byte is payload
7.5 Startup phase
The Gateway is parameterized and configured by the PROFINET-IO-controller during the startup
phase. Only after a correct termination of the startup phase the data exchange with external
devices will take place.

23.6.17 UNIGATE®fieldbus gateway UNIGATE®CM PROFINET 2Port V. 1.6 19
Deutschmann Automation GmbH & Co. KG Generating a Script
8 Generating a Script
Note: All commands relating to the extension do not work in the debug
mode! See chapter 6.5.
8.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.
8.2 Memory efficiency of the programs
A Script command can carry out e. g. a complex checksum like a CRC-16 calculation via data.
For the coding of this command only 9 byte are required as memory space (for the command
itself). This is only possible when these complex commands are contained in a library.
A further advantage of this library is, that the underlying functions have been in practical use for
a couple of years and therefore can be described as ’void of errors’. As these commands are
also present in the native code for the controller, at this point also the runtime performance of the
Script is favorable.
8.3 What can you do with a Script device?
Our Script devices are in the position to process a lot of commands. In this case a command is
always a small firmly outlined task. All commands can be put into classes or groups. A group of
commands deals with the communication in general. This group’s commands enable the Gate-
way to send and receive data on the serial side as well as on the bus-side.
8.4 Independence of buses
Basically the Scripts do not depend on the bus, they are supposed to operate on. It means that a
Script which was developed on a PROFIBUS Gateway can also be operated on an Interbus with-
out changes, since the functioning of these buses is very similar. In order to also process this
Script on an Ethernet Gateway, perhaps further adjustments have to be made in the Script, so
that the Script can be executed reasonably.
There are no fixed rules how which Scripts have to operate properly. When writing a Script you
should take into account on which target hardware the Script is to be executed, so the necessary
settings for the respective buses can be made.
8.5 Further settings at the Gateway
Most devices require no further adjustments, except for those made in the Script itself. These
settings are made by means of the software WINGATE. If
you know our UNIGATE®-series, you are already familiar with the proceeding with it. An example
is the adjustment of the IP-address and the net-mask of an Ethernet-Gateway. These values
have to be known as fixed values and are not available for the runtime. Another reason for the

Generating a Script Deutschmann Automation GmbH & Co. KG
20 UNIGATE®fieldbus gateway UNIGATE®CM - PROFINET 2Port V. 1.6 23.6.17
configuration of the values in WINGATE is the following: After an update of the Script these val-
ues remain untouched, i. e. the settings that were made once are still available after a change of
the Script.
Only this way it is also possible that the same Script operates on different Ethernet-Gateways,
that feature different IP-addresses.
8.6 The use of the Protocol Developer
The software tool Protocol Developer can be downloaded from our website
http://www.deutschmann.de
It is a tool for an easy generation of a Script for our Script Gateways. Its operation is exactly
aimed at this use. After starting the program the Script that was loaded the last time is loaded
again, provided that it is not the first start.
Typical for Windows Script commands can be added by means of the mouse or the keyboard. As
far as defined and required for the corresponding command, the dialog to the corresponding
command is displayed, and after entering the values the right text is automatically added to the
Script. The insertion of new commands by the Protocol Developer is carried out in a way that
existing commands will not be overwritten. Generally a new command is inserted in front of the
one where the cursor is positioned. Of course the commands can also be written by means of the
keyboard or already written commands can also be modified.