DEUTSCHMANN AUTOMATION UNIGATE EL-DeviceNet User manual

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

Manual Art.-No.: V4149E

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™ V. 1.0 4
Deutschmann Automation GmbH & Co. KG
1 Information on CE marking of the module . . . . . . . . . . . . . . . . 9
1.1 EU Directive EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Scope of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Note installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 Installation of the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Working on switch cabinets . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Information for the machine manufacturers . . . . . . . . . . . . . . 10
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 EU Machinery Directive . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
3.1 UNIGATE®EL software flow-chart . . . . . . . . . . . . . . . . . . . . 12
3.2 UNIGATE®block diagram . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3 UNIGATE®application diagram . . . . . . . . . . . . . . . . . . . . . . 13
4 Operation modes of the Gateway. . . . . . . . . . . . . . . . . . . . 14
4.1 Configuration mode (config mode) . . . . . . . . . . . . . . . . . . . . 14
4.1.1 Data structure on the Ethernet-Side in configuration mode . . . . . . . . . . . 14
4.2 Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Data exchange mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5 RS-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1 RS-interfaces at the UNIGATE®EL . . . . . . . . . . . . . . . . . . . . 16
5.2 Buffer sizes at the UNIGATE®EL . . . . . . . . . . . . . . . . . . . . . 16
5.3 Framing Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6 The Debug-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1 Overview of the Debug-interface . . . . . . . . . . . . . . . . . . . . . 17
6.2 Starting in the Debug-mode . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3 Communication parameter for the Debug-interface . . . . . . . . . . . . 17
6.4 Possibilities with the Debug-interface . . . . . . . . . . . . . . . . . . . 17
6.5 Commands of the Debug-interface . . . . . . . . . . . . . . . . . . . . 17
7 Mode of operation of the system . . . . . . . . . . . . . . . . . . . . 19
7.1 General explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.3 Data exchange DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . 19
7.3.1 Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.4 Possible data lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8 Generating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1 What is a Script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2 Memory efficiency of the programs . . . . . . . . . . . . . . . . . . . . 20
8.3 What can you do with a Script device? . . . . . . . . . . . . . . . . . . 20
8.4 Independence of buses . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.5 Further settings at the Gateway . . . . . . . . . . . . . . . . . . . . . . 20
8.6 The use of the PROTOCOL DEVELOPER . . . . . . . . . . . . . . . . 21
8.7 Accuracies of the baud rates . . . . . . . . . . . . . . . . . . . . . . . 21
8.8 Script processing times . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9 Hardware ports, switches and LEDs . . . . . . . . . . . . . . . . . . 23
9.1 Device labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Deutschmann Automation GmbH & Co. KG
5 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet V. 1.0 22.6.17
9.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . . .23
9.2.2 Connector supply voltage and DEBUG-interface. . . . . . . . . . . . . . . . .24
9.2.3 Ethernet interface connector . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
9.2.4 DeviceNet-connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
9.2.5 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
9.3 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.3.1 LED "Link/Act." . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.3.2 LED "Power/State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.3.3 LEDs 1 / 2 / 4 / 8 (Error No. / Select ID) . . . . . . . . . . . . . . . . . . . . .25
9.3.4 LED "State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
9.3.5 LED "Bus Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
9.3.6 LED "Bus State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
9.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9.4.1 Termination Rx 422 + Tx 422 (serial interface). . . . . . . . . . . . . . . . . .26
9.4.2 Rotary coding switches S4 + S5 (serial interface) . . . . . . . . . . . . . . . . 26
9.4.3 Termination (DeviceNet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
9.4.4 DIP-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
10 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
10.1 Error handling at UNIGATE®EL . . . . . . . . . . . . . . . . . . . . . 28
10.1.1 Error on the extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
11 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 31
11.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 31
11.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
11.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
11.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
11.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
11.2.2 DeviceNet communication interface . . . . . . . . . . . . . . . . . . . . . . . 32
11.2.3 Line routing, shield and measures to combat interference voltage. . . . . . . . 32
11.2.4 General information on line routing . . . . . . . . . . . . . . . . . . . . . . . . 32
12 Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
13 DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.1 The Product Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.2 EDS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.2.1 Sample EDS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.3 DeviceNet™ information . . . . . . . . . . . . . . . . . . . . . . . . . 37
14 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
14.1 Network-addresses, network-connections . . . . . . . . . . . . . . . . 38
14.2 TCP-connection setup . . . . . . . . . . . . . . . . . . . . . . . . . . 38
14.3 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
14.3.1 TCP or UDP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
14.4 Data exchange mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
14.5 UNIGATE®-SCAN-function . . . . . . . . . . . . . . . . . . . . . . . . 39
15 Implemented protocols in UNIGATE®EL . . . . . . . . . . . . . . . . 40
15.1 Implemented protocols (Transport protocols at the EL interface) . . . . . 40
15.2 Configuration options for the individual transport protocols . . . . . . . . 41

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™ V. 1.0 6
Deutschmann Automation GmbH & Co. KG
15.2.1 Parameter TCP response time (0 off 1..65 sec). . . . . . . . . . . . . . . . . 41
15.3 Operation of individual transport protocols . . . . . . . . . . . . . . . . 42
15.3.1 TCP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
15.3.2 UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
15.3.3 TCP (server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
15.3.4 TCP (client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
15.3.5 Modbus TCP (server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
15.3.6 Modbus TCP (client). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
15.3.7 Universal Modbus TCP Server . . . . . . . . . . . . . . . . . . . . . . . . . 48
15.3.8 Universal Modbus TCP (client) . . . . . . . . . . . . . . . . . . . . . . . . . 50
15.4 Delivery status (factory setting) . . . . . . . . . . . . . . . . . . . . . . 52
15.4.1 Erstinbetriebnahme (Quick Start) . . . . . . . . . . . . . . . . . . . . . . . . 52
15.5 Trigger Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
15.6 Length Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
15.7 Swap word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
16 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
16.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
16.1.1 Interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
17 Commissioning guide . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17.4 Dimensional drawing UNIGATE®EL - DeviceNet™ . . . . . . . . . . . 56
17.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
17.6 Setting the DeviceNet™ address and baud rate . . . . . . . . . . . . . 57
17.7 DeviceNet™ connection . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.8 Ethernet connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.9 Connection to the process device . . . . . . . . . . . . . . . . . . . . . 57
17.10 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 57
17.11 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
17.12 Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
18 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
18.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
18.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . . . 58
19 Annex. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
19.1 Explanations of the abbreviations . . . . . . . . . . . . . . . . . . . . . 59
19.2 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Deutschmann Automation GmbH & Co. KG
7 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet V. 1.0 22.6.17

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 8
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 – 2016. 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
9 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 22.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
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 oper-
ating 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.
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)

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 10
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
11 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 22.6.17
3 Introduction
The UNIGATE®EL-DeviceNet module serves to connect an Ethernet port to DeviceNet. In this
application, it functions as a Gateway. The DeviceNet interface in accordance with "DeviceNet
Specification Release 2.0" operates as DeviceNet "Group 2 Only Slave". It can be operated by
any standard-compliant Master.
The module EL-DeviceNet essentially consists of the following hardware components:
•Electrically isolated interface to DeviceNet
•CAN-controller SJA 1000
•Microprocessor 89C51RE2
•RAM and EPROM
•Serial interface (RS232, RS485 and RS422) to the device connected externally
•10/100 Base-T Ethernet LAN (RJ-45 connector)
Conceptual
•In the further course of this manual, the term "Fieldbus" is frequently
used. In these cases this applies to the DeviceNet interface.

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 12
Deutschmann Automation GmbH & Co. KG Introduction
3.1 UNIGATE®EL software flow-chart

Introduction Deutschmann Automation GmbH & Co. KG
13 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 22.6.17
3.2 UNIGATE®block diagram
The following picture shows a typical UNIGATE®-module design.
3.3 UNIGATE®application diagram
The following graph shows a typical connection scheme.

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 14
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.82 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-DN-CL[Cfg=256] (RS+Ext.Board) V6.6[42] (c)dA[40MHz] Switch=0x41FF
Script(C:11781/16128,V:13022/16384)="Universalscript Deutschmann EL" Author="G/S"
Version="V1.6.0" Date=30.09.2016 SN=47110001
Ext-Board: EL-IO-DICNET[193] V1.51 (c)dA 47110211
FE: IP=0.0.0.0 MAC=00-14-11-15-1A-53 Data-Flash=1MB“.
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.1.1 Data structure on the Ethernet-Side in configuration mode
10/100 Base-T: 1. + 2. Byte Echo of the received Ethernet data
3. Byte Zero
4. Byte Echo of the received Ethernet data
5. Byte FF
6. - 8. Byte Version of the Ext. Card e.g. 13
Connection setting for 10/100 Base-T (RJ45 connector)

This connector has four channels (sockets) with the following transport protocols:
Channel Transport 
protocol
Config mode Test mode data exchange mode
Channel 1 TCP server
(TCP/IP server)
port 23
 default
Channel 2 Web server  
Channel 3 FTP (Control)  
Channel 4a FTP (Data)  
After FTP connec-
tion UDP connec-
tion is erased
Channel 4b UDP
(UNIGATE®
Scan)
 

Operation modes of the Gateway Deutschmann Automation GmbH & Co. KG
15 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 22.6.17
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.
8 Bytes are output on the Ethernet interface:
The first 6 Byte are an echo of the received Ethernet data, the 7. Byte is incremented every sec-
ond 0-255 and then again from 0. The 8. Byte is also incremented every second, but always
cyclically from 0-9.
In test mode the Gateway always operates with TCP/IP (server) port 23.
4.3 Data exchange mode
The Gateway has to be in the data exchange mode, so that a data exchange between the Ether-
net-side of the Gateway and the DeviceNet is possible. As long as the Gateway is not in the con-
figuration-, 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_EL.dcs(ScriptName „Universalscript Deutschmann EL“).

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 16
Deutschmann Automation GmbH & Co. KG RS-interface
5 RS-interface
5.1 RS-interfaces at the UNIGATE®EL
The UNIGATE®EL - DeviceNet 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®EL
UNIGATE®EL 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
17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 22.6.17
6 The Debug-interface
6.1 Overview of the Debug-interface
The UNIGATE®IC 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 processing 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-development 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.

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 18
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
19 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 22.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 to 6 are blank, and
Layer 7 is converted in accordance with chapter 7.3.
7.2 Interfaces
The Gateway features the RS232-, RS422- and RS485-interfaces as well as 10/100 Base-T LAN
(RJ-45).
7.3 Data exchange DeviceNet
All data is transferred by the Gateway in dependence of the downloaded Script.
In the DeviceNet the gateway acts as a "Group 2 Only Slave". The access method "Polling", is
supported, which is described below.
7.3.1 Polling
In the event of Polling the DeviceNet-master sends a telegram according to the configured length
to the gateway. The gateway sends out these data via the RS-interface according to the selected
protocol. As an answer the DeviceNet-master receives the latest data received by the RS-inter-
face.
The maximum amount of input- out output data to be configured is 255 Byte.
7.4 Possible data lengths
The table below shows the maximum transferable data in DeviceNet:.
DeviceNet Input data (Consumed) max. 255 bytes Variable: maximum value in this case
Output data (Produced) max. 255 bytes Variable: maximum value in this case
EL Input- and output data max. 1536 bytes dynamic

22.6.17 UNIGATE®fieldbus gateway UNIGATE®EL - DeviceNet™V. 1.0 20
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. However,
there are also exceptions to it. 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