DEUTSCHMANN AUTOMATION UNIGATE CL ProfibusDP User manual

Instruction manual
Universal Fieldbus-Gateway
UNIGATE® CL - ProfibusDP
Art.-Nr.: V3572E
Deutschmann Automation GmbH & Co. KG Carl-Zeiss-Str. 8 D-65520 Bad Camberg
Tel:[phone] Hotline: [phone] Fax: [phone]
Internet: http://www.deutschmann.de

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 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 CL software flow-chart . . . . . . . . . . . . . . . . . . . . . 11
3.2 UNIGATE block diagram . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3 UNIGATE 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5 RS-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1 RS-interfaces at the UNIGATE CL . . . . . . . . . . . . . . . . . . . . 14
5.2 Buffer sizes at the UNIGATE CL . . . . . . . . . . . . . . . . . . . . . 14
5.3 Framing Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 SSI-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 Initiation of the SSI-interface . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Hardware-wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7 The Debug-interface . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1 Overview of the Debug-interface . . . . . . . . . . . . . . . . . . . . . 17
7.2 Starting in the Debug-mode . . . . . . . . . . . . . . . . . . . . . . . . 17
7.3 Communication parameter for the Debug-interface . . . . . . . . . . . . 17
7.4 Possibilities with the Debug-interface . . . . . . . . . . . . . . . . . . . 17
7.5 Commands of the Debug-interface . . . . . . . . . . . . . . . . . . . . 17
8 Mode of operation of the system . . . . . . . . . . . . . . . . . . . 18
8.1 General explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.3 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.4 Possible data lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.5 Startup phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
9 Generating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.1 What is a Script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.2 Memory efficiency of the programs . . . . . . . . . . . . . . . . . . . . 19
9.3 What can you do with a Script device? . . . . . . . . . . . . . . . . . . 19
9.4 Independence of buses . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.5 Further settings at the Gateway . . . . . . . . . . . . . . . . . . . . . . 19
9.6 The use of the Protocol Developer . . . . . . . . . . . . . . . . . . . . 20
9.7 Accuracies of the baud rates . . . . . . . . . . . . . . . . . . . . . . . 20
9.8 Script processing times . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Deutschmann Automation GmbH & Co. KG
4 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
10 Implemented protocols in UNIGATE CL with Universal Script . . . . 22
10.1 Protokoll: Transparent . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.1.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
10.2 Protocol: Universal 232 . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.2.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
10.2.2 Fieldbus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.2.3 RS232 parameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2.3.1 Start character (232 Start character) . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2.3.2 Length 232 (232 Length) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2.3.3 End character (232 End character) . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2.4 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
10.3 Protocol: 3964(R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.3.1 Data structure 3964R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
10.3.2 Protocol definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.3.3 Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
10.3.3.1 Initiation of data communication by the low-priority user . . . . . . . . . . . . . . . 24
10.3.3.2 Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.3.3.3 Timeout times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.3.3.4 Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.3.3.5 Initiation of data communication by the high-priority user . . . . . . . . . . . . . . . 24
10.3.4 Protocol type 3964 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
10.4 Protocol: MODBUS-RTU . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.4.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
10.4.2 UNIGATE as MODBUS-Master . . . . . . . . . . . . . . . . . . . . . . . . .25
10.4.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.4.2.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4.2.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4.3 UNIGATE as MODBUS-Slave . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4.3.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4.3.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4.4 UNIGATE as Modbus-ASCII Master . . . . . . . . . . . . . . . . . . . . . . .27
10.5 The trigger byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
10.6 The length byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11 Hardware ports, switches and LEDs . . . . . . . . . . . . . . . . . . 28
11.1 Device labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
11.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
11.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . . .28
11.2.2 Connector supply voltage and DEBUG-interface . . . . . . . . . . . . . . . .29
11.2.3 ProfibusDP-connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11.2.4 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
11.3 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
11.3.1 LED "(Bus) Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
11.3.2 LED "Bus" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
11.3.3 LED "(Bus) State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
11.3.4 LED "Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
11.3.5 LED "State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 5
Deutschmann Automation GmbH & Co. KG
11.3.6 LEDs 1 / 2 / 4 / 8 (Error No. / Select ID) . . . . . . . . . . . . . . . . . . . . 30
11.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
11.4.1 Termination Rx 422 + Tx 422 (serial interface) . . . . . . . . . . . . . . . . . 31
11.4.2 Rotary coding switches S4 + S5 (serial interface) . . . . . . . . . . . . . . . 31
11.4.3 Termination (Profibus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
11.4.4 Rotary coding switches High + Low (Profibus-ID) . . . . . . . . . . . . . . . 31
11.5 The Debug cable for UNIGATE SC . . . . . . . . . . . . . . . . . . . . 31
12 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
12.1 Error handling at UNIGATE CL . . . . . . . . . . . . . . . . . . . . . . 32
13 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.2.1.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
13.2.1.2 Equipotential bonding connection. . . . . . . . . . . . . . . . . . . . . . . . . . . 34
13.2.2 ProfibusDP communication interface . . . . . . . . . . . . . . . . . . . . . . 34
13.2.2.1 Bus line with copper cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
13.2.3 Line routing, shield and measures to combat interference voltage . . . . . . . 34
13.2.4 General information on line routing . . . . . . . . . . . . . . . . . . . . . . . 34
13.2.4.1 Shielding of lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
14 ProfbusDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14.1 Description of the DPV1-/DPV2-functions . . . . . . . . . . . . . . . . 36
14.1.1 DPV1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14.1.2 DPV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14.2 Representation of the data in ProfibusDP . . . . . . . . . . . . . . . . . 36
14.2.1 Configuration telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
14.2.2 Configuration telegram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
14.2.3 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
14.2.3.1 Diagnosis in DPV1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
14.2.4 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
15 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
15.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
15.1.1 Interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
16 Commissioning guide . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.4 Dimensional drawing UNIGATE CL - ProfibusDP . . . . . . . . . . . . . 43
16.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
16.6 Setting the Profibus address . . . . . . . . . . . . . . . . . . . . . . . 43
16.7 Profibus connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.8 Connection to the process device . . . . . . . . . . . . . . . . . . . . . 45
16.9 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 45
16.10 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Deutschmann Automation GmbH & Co. KG
6 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
16.11 Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
16.12 Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
17 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
17.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
17.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . . 46
18 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
18.1 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
19 Declaration of conformity . . . . . . . . . . . . . . . . . . . . . . . . 48
19.1 EC declaration of conformity . . . . . . . . . . . . . . . . . . . . . . . 48

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 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 – 2010. 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.
Art.-No.: V3572E

Information on CE marking of the module Deutschmann Automation GmbH & Co. KG
8 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
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 availableat 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 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.

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 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 CL - ProfibusDP V. 2.3 17.6.10
3 Introduction
The UNIGATE CL-ProfibusDP module serves to adapt a serial port to the ProfibusDP to EN 50
170. In this application, it functions as a Gateway and operates as the ProfibusDP Slave. It can
be operated by any standard-compliant Master.
The module CL-ProfibusDP essentially consists of the following hardware components:
•Electrically isolated RS485 interface to the ProfibusDP
•Profibus ASIC
•Microprocessor 89C51RD2
•RAM and EPROM
•Optionally electrically isolated
•Serial interface (RS232, RS485 and RS422) to the device connected externally

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 11
Deutschmann Automation GmbH & Co. KG Introduction
3.1 UNIGATE CL software flow-chart

Introduction Deutschmann Automation GmbH & Co. KG
12 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
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.

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 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
•Configuring the Gateway
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-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x00FF Script(16k)="Universalscript
Deutschmann" Author="G/S" Version="V 0.1t CL-DP_COV4_FE_DN_RS" Date=25.05.2007
SN=47110001 ID=0“.
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.3 Data exchange mode
The Gateway has to be in the data exchange mode, so that a data exchange between the
RS-side of the Gateway and the fieldbus is possible. As long as the Gateway is not in the config-
uration mode or the test mode, the data exchange mode is active. In the data exchange mode
the Gateway will execute the downloaded Script.

RS-interface Deutschmann Automation GmbH & Co. KG
14 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
5 RS-interface
5.1 RS-interfaces at the UNIGATE CL
The UNIGATE CL - ProfibusDP has the interfaces RS232, RS422 and RS485 available. The
hardware always features a DEBUG-interface, see chapter 7.
5.2 Buffer sizes at the UNIGATE CL
UNIGATE CL 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 Pro-
tocol Developer). The presetting for the "Stop Bit Framing Check" is "enabled".

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 15
Deutschmann Automation GmbH & Co. KG SSI-interface
6 SSI-interface
The UNIGATE also supports the connection of applications or products, that communicate via
SSI.
6.1 Initiation of the SSI-interface
The required Script (example_SSI), the firmware- (Cust0023) and Protocol Developer-extension
(Cust_ssi.xml) are available free of charge from our website at www.deutschmann.de, as well as
the softwaretool Protocol Developer and the configuration software WINGATE.
•In the Protocol Developer (see chapter 7, The Debug-interface) the ConfigFile "Cust_ssi.xml"
has to be added. At Options -> Settings -> ConfigFiles.
•Load the Script "example_SSI.dss" into the Protocol Developer.
•The encoder type has to be defined in the Script itself under "Set number of bits" and "Set
typ" (default = 12-Bit-Single-Turn-Gray):
// Set number of bits (1..16 = Single Turn, 17..32 = Multi Turn)
moveconst (bAnzBit, 12); // i.e. 12 Bit single turn
// Set typ
// Values of bTyp:
// 0 = Reserved
// 1 = Output-value without change (i.e. binary encoder)
// 2 = Output-value changed from Gray to Binary (i.e. Gray encoder)
// >2 = Reserved
moveconst ( wTyp, 2); // i.e. 12 Bit Gray
•Load the Script into the device. Open WINGATE and activate the device in the configuation
mode (see chapter 4.1, Configuration mode (config mode)) - an actuation message appears,
that looks in line with the following (example CL-PB):
Special Firmware (23) not loaded
RS-PBV1-CL (232/422/485) V7.31[30] (c)dA Switch=0x02FF Script(8k)="SSI" Aut-
hor="Deutschmann Automation" Version="V 1.0" Date=20.03.2008 SN=47110002 ID=2
Konfigmode...
The note "Special Firmware (23) not loaded" means that the firmware-extension is not yet
loaded. The extension is loaded through Extras -> Firmware Script Extension. Select the file
"Cust0023 (Cmd 23 + 24 for SSI).hex" and choose "write extension".
•Re-start the device -> now only the device’s actual actuation message appears and not the
note any more.
•Bring the device into the data exchange mode (see chapter 4.3, Data exchange mode) ->
DONE!
6.2 Hardware-wiring
The clock wires of the SSI-interface are placed onto the Tx-wires of the RS422-interface and the
data wires onto the Rx-wires at the UNIGATE CL.

SSI-interface Deutschmann Automation GmbH & Co. KG
16 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
X1 (3pin + 4pin screw-plug-connector):
Pin no. Name Function at SSI
1Rx 232 n. c.
2Tx 232 n. c.
3AP-GND n. c.
4Rx 422+ SSI DAT+
5Rx 422- SSI DAT-
6Tx 422+ SSI CLK+
7Tx 422- SSI CLK-

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17
Deutschmann Automation GmbH & Co. KG The Debug-interface
7 The Debug-interface
7.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.
7.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.
7.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.
7.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’.
7.5 Commands of the Debug-interface
The commands for the use of the Debug-interface are described in the instruction manual Proto-
col Developer.

Mode of operation of the system Deutschmann Automation GmbH & Co. KG
18 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
8 Mode of operation of the system
8.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 8.3.
8.2 Interfaces
The Gateway features the RS232-, RS422- and RS485-interfaces.
8.3 Data exchange
All data is transferred by the Gateway in dependence of the downloaded Script.
8.4 Possible data lengths
The table below shows the maximum transferable data:
Input data max. 244 bytes Variable: maximum value in this case
Output data max. 244 bytes Variable: maximum value in this case
Parameters 8 bytes No user parameters *
Configuration data max. 16 bytes Dependent on configuration *
Diagnosis max. 8 bytes 1 user diagnostic bit = error code *
*) Contrary to this default setting these parameters can be altered through special Script com-
mands.
The commands can be found in the Protocol under “Bus specific“-“Profibus“:
Set Profibus Config Data
Set Profibus Parameter InBuf
Set Profibus Diagnose
Further information can be found in the Protocol Developer’s online help.
8.5 Startup phase
The Gateway is parameterized and configured by the Master during the startup phase. Only after
a correct termination of the startup phase the data exchage with external devices will take place.

17.6.10 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 19
Deutschmann Automation GmbH & Co. KG Generating a Script
9 Generating a Script
9.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.
9.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.
9.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.
9.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 without
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.
9.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
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.

Generating a Script Deutschmann Automation GmbH & Co. KG
20 UNIGATE fieldbus gateway UNIGATE CL - ProfibusDP V. 2.3 17.6.10
9.6 The use of the Protocol Developer
The Protocol Developer 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.
9.7 Accuracies of the baud rates
The baud rate of the serial interface is derived from the processor’s crystal frequency.
Meanwhile all Script-Gateways are working with a crystal frequency of 40 MHz.
You can enter any desired integer baud rate into the Script. After that the firmware adjusts the
baud rate, that can be derived the most precisely from the crystal frequency.
The baud rate the Gateway is actually working with (BaudIst) can be determined as follows:
BaudIst= (F32 / K)
F32 = Crystal frequency [Hz] / 32
K = Round (F32 / BaudSoll);
Round () is a commercial roundoff
Example:
The actual baud rate is to be calculated, when 9600 baud are pre-set, where the Gateway is
operated with 40 MHz:
F32 = 40000000 / 32 = 1250000
K = Round(1250000 / 9600) = Round(130.208) = 130
BaudIst= 1250000 / 130 = 9615.38
I. e.: The baud rate actually adjusted by the Gateway is 9615.38 baud
The resulting error in per cent can be calculated as follows:
Error[%] = (abs(BaudIst - BaudSoll) / BaudSoll) * 100
In our example the following error results:
Error = (abs(9615.38 - 9600) / 9600) * 100 = 0.16%
In practise errors below 2% can be tolerated!
In the following please find a listing of baud rates at a 40 MHz-crystal frequency with the corre-
sponding errors: