Instruction Manual Universal Fieldbus-Gateway Unigate Ic - Profibus

Instruction Manual
Universal Fieldbus-Gateway
UNIGATE® IC - PROFIBUS
Deutschmann Automation GmbH & Co. KG

www.deutschmann.com | wiki.deutschmann.de
1 General introduction . . . . . . . . . . . . . . . . . . . . . . . . 9
2 The UNIGATE® IC . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 Technical introduction . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4 The serial standard interface . . . . . . . . . . . . . . . . . . . . . . 10
2.5 The synchronous interface . . . . . . . . . . . . . . . . . . . . . . . 10
2.6 The Debug-interface . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.7 UNIGATE® IC hardware survey . . . . . . . . . . . . . . . . . . . . 11
3 Hardware design. . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.1 -Boot enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.2 Load out (SPI-Master: SS0-) . . . . . . . . . . . . . . . . . . . . . 13
3.2.3 Data out (SPI-Master: SS1-) . . . . . . . . . . . . . . . . . . . . . . 13
3.2.4 Data In (SPI: MISO) . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.5 Load In (SPI: MOSI) . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.6 Clock (SPI: SCK) . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.7 -Reset In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.8 LED-PB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.9 -Config Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.10 DbgTX, DbgRx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.11 TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.12 TX, RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.4 Basic line of proceeding . . . . . . . . . . . . . . . . . . . . . . . . 14
3.5 Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.6 Layout examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.7 Operation with external PROFIBUS-driver . . . . . . . . . . . . . . . 21
3.8 Termination (PROFIBUS) . . . . . . . . . . . . . . . . . . . . . . . 21
3.9 Handling (mounting the UNIGATE® IC on the carrier board) . . . . . . 21
3.10 Differences between the various versions . . . . . . . . . . . . . . . 22
3.10.1 Standard version. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.10.2 Version "without 485 (PROFIBUS)-driver". . . . . . . . . . . . . . . 22
3.10.3 Version "LWL" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4 The serial interface . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2 Initialization of the serial interface . . . . . . . . . . . . . . . . . . . 23
4.3 Use of the serial interface . . . . . . . . . . . . . . . . . . . . . . . 23
4.4 Further operation modes . . . . . . . . . . . . . . . . . . . . . . . . 23
16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 3

5 Synchronous serial interface . . . . . . . . . . . . . . . . . . . 24

5.1 Shift register operation . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.1.1 Example-Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2 SPI mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.1 Example-Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6 The Debug-interface . . . . . . . . . . . . . . . . . . . . . . . . 26
6.1 Overview of the Debug-interface . . . . . . . . . . . . . . . . . . . . 26
6.2 Starting in the Debug-mode . . . . . . . . . . . . . . . . . . . . . . 26
6.3 Communication parameter for the Debug-interface . . . . . . . . . . 26
6.4 Possibilities with the Debug-interface . . . . . . . . . . . . . . . . . 26
6.5 Commands of the Debug-interface . . . . . . . . . . . . . . . . . . 26
7 Script and configuration . . . . . . . . . . . . . . . . . . . . . 27
7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2 The configuration mode . . . . . . . . . . . . . . . . . . . . . . . . 27
7.3 Update the script . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.4 Configuration of the UNIGATE® IC . . . . . . . . . . . . . . . . . . . 29
7.4.1 PROFIBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.4.2 RS232/RS485/RS422 . . . . . . . . . . . . . . . . . . . . . . . . . 30
8 Generating a script . . . . . . . . . . . . . . . . . . . . . . . . 31
8.1 What is a script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.2 Memory efficiency of the programs . . . . . . . . . . . . . . . . . . 31
8.3 What can you do with a script device? . . . . . . . . . . . . . . . . . 31
8.4 Independence of buses . . . . . . . . . . . . . . . . . . . . . . . . 31
8.5 Further settings at the Gateway . . . . . . . . . . . . . . . . . . . . 31
8.6 The use of the Protocol Developer . . . . . . . . . . . . . . . . . . . 32
8.7 Accuracies of the baud rates at UNIGATE® IC . . . . . . . . . . . . 32
8.8 Script processing times . . . . . . . . . . . . . . . . . . . . . . . . 33
9 PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.1 Description of the DPV1- / DPV2-functions . . . . . . . . . . . . . . 34
9.1.1 DPV1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.1.2 DPV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2 Setting the PROFIBUS-address . . . . . . . . . . . . . . . . . . . . 35
10 Error handling at UNIGATE® IC . . . . . . . . . . . . . . . . . . 37
11 Firmware-update . . . . . . . . . . . . . . . . . . . . . . . . . . 38
11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
11.2 Adjusting the firmware-update-mode . . . . . . . . . . . . . . . . . 38
11.2.1 Adjustment by hardware . . . . . . . . . . . . . . . . . . . . . . . . 38
11.2.2 Adjustment by software . . . . . . . . . . . . . . . . . . . . . . . . 38
11.3 Execution of the firmware-update . . . . . . . . . . . . . . . . . . . 38
11.4 Note on safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

11.5 Operation mode of the IC . . . . . . . . . . . . . . . . . . . . . . . . 38

12 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
12.1 Mechanics of the UNIGATE® IC . . . . . . . . . . . . . . . . . . . . 39
12.1.1 General dimensions of UNIGATE® IC . . . . . . . . . . . . . . . . . 39
12.1.2 Dimensions UNIGATE® IC (PROFIBUS DP only) . . . . . . . . . . 39
12.2 Technical data UNIGATE® IC-PROFIBUS . . . . . . . . . . . . . . . 40
12.2.1 Features of the different versions . . . . . . . . . . . . . . . . . . . 40
13 Accessory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
13.1 Adapter RS232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
13.2 Adapter RS485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
13.3 FirmwareDownloadTool (FDT) . . . . . . . . . . . . . . . . . . . . . 41
13.4 Protocol Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
13.5 Developerkit UNIGATE® IC-AB IC . . . . . . . . . . . . . . . . . . . 41
13.5.1 Developerboard UNIGATE® IC-AB . . . . . . . . . . . . . . . . . . 41
13.5.2 Quick start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
14 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
14.1 Explanations of the abbreviations . . . . . . . . . . . . . . . . . . . 43
14.2 Basis board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
14.2.1 Overview basis board PROFIBUS DP . . . . . . . . . . . . . . . . . 44
14.2.2 Connectors of the basis board . . . . . . . . . . . . . . . . . . . . . 48
14.2.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . 48
14.2.2.2 PROFIBUS DP connector . . . . . . . . . . . . . . . . . . . . . . . . . . 49
14.2.2.3 Power supply of the basis board . . . . . . . . . . . . . . . . . . . . . . . 49
14.2.2.4 Shield terminal lead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
14.2.2.5 Rotary coding switches . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
14.2.2.6 Slide switch (RS485/RS232 interface) . . . . . . . . . . . . . . . . . . . . 49
14.2.2.7 Slide switch (RS485 termination) . . . . . . . . . . . . . . . . . . . . . . 49
14.2.3 Wiring diagram UNIGATE® IC-basis board PROFIBUS DP . . . . . . 50
15 Representation of the data in PROFIBUS DP . . . . . . . . . . 53
15.1 Configuration telegram . . . . . . . . . . . . . . . . . . . . . . . . . 53
15.2 Configuration telegram . . . . . . . . . . . . . . . . . . . . . . . . . 54
15.3 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
15.3.1 Diagnosis in DPV1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
15.4 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
16 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
16.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
16.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . 59


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 – 2018. 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.


Deutschmann Automation GmbH & Co. KG General introduction
1 General introduction
In the past the integration of a fieldbus connection required an enormous effort from the progress
engineers. On account of the large variety of communication systems it is not enough to compile
the right combination of communication hardware; due to their standards and fundamentals dif-
ferent busses also require the corresponding skills of the engineers.
This does not apply in case of the UNIGATE® IC by Deutschmann Automation any more. All dig-
ital functions, software, stack and driver as well as optocoupler are integrated on a UNIGATE® IC
in correspondence with the standard. In addition to the reduction of the required size, also differ-
ent fieldbusses can easily be integrated.
Through the flexible firmware of UNIGATE® IC no software-changes are required on the

side of the customer!
Since 1997 Deutschmann Automation has experience in the field of fieldbus gateways; this
enormous experience results in the UNIGATE® IC as a consistent sequel of this successful
product line.
Terminology
In the entire document and in all parts of the software that is to be used, the terms Input and Out-
put are used. Input and Output are ambiguous, always depending on the viewpoint. We see the
fieldbus as central interface and as integral component of your device; therefore in all places it is
always referred to data from the viewpoint of the Slave, that is Input data, as data from the Mas-
ter to the Slave - regardless of the used bus.
Representation of numbers
Numbers in decimal format are always represented without prefix and without suffix as well.
hexadecimal numbers are always marked with the prefix 0x.

The UNIGATE® IC Deutschmann Automation GmbH & Co. KG
2 The UNIGATE® IC
2.1 Technical introduction
The UNIGATE® IC by Deutschmann Automation contains all components that are required for
the communication in a fieldbus in one single module. Therefore a developer does not have to
take care for that detail any more, only a hardware redesign is necessary in order to integrate the
UNIGATE® IC and the required plug connectors.
2.2 Availability
The module is available as PROFIBUS DP. Further fieldbusses are either planned or being
worked on. They will only differ in the connections of the busses. The meaning of the general
pins 1 - 9 as well as 24 and 26 - 32 will remain unchanged also for further fieldbus implementa-
tions.
You can find an up-to-date list for all UNIGATE® ICs under:
http://www.deutschmann.com.
2.3 Firmware
UNIGATE® IC is programmed via scripts. On principle any script, that has been developed for a
UNIGATE® SC, can also be operated on the UNIGATE® IC.
2.4 The serial standard interface

Intelligent devices, that already feature a micro controller or a microprocessor, are generally sup-
plied with a serial asynchronous interface with a TTL-level. It is directly connected with the TTL-
interface of the UNIGATE® IC. For more information on this serial interface see chapter 4 on
page 22.
2.5 The synchronous interface

In addition to the standard interface there is also the possibility of the synchronous input and out-
put. That way for instance digital IOs can be connected through shift register components or also
analog IOs can be connected through a DA-converter with serial in-/output. For synchronous IOs
256 signals at the most can be used (256 bit). Wiring examples can be found in chapter 3.5 on
page 14 and for software examples see chapter 5. This interface can also be used to connect
modules or devices with SPI-interface. It is also possible to build, for instance digital or analo-
gous I/O-modules, with the customer’s device not being equipped with an own controller. The
fieldbus IC is also operable autonomously without that controller.
2.6 The Debug-interface

The UNIGATE® IC features a Debug-interface, which allows to process a script step by step and
also to monitor or manipulate data. This is indispensable for the development of a script. Usually
a script is developed with the software Protocol Developer. For more details take a look at the
instruction manual Protocol Developer.
All interfaces can independently be used at the same time.

Deutschmann Automation GmbH & Co. KG The UNIGATE® IC
2.7 UNIGATE® IC hardware survey

The hardware of the UNIGATE® IC consists of some few standard components. The picture
below shows the functional structure of the IC.
LOAD DATA DATA LOAD
CLOCK OUT OUT IN IN
T T R T R
E X X X X
N
UART 1 UART 2 SYN.SERIAL
Flash-ROM
Microcontroller RAM
EEROM
Isolation
DC Opto Coupler
DC
Fieldbus-Interface

Hardware design Deutschmann Automation GmbH & Co. KG
3 Hardware design
This chapter gives basic advise, that is required in order to load UNIGATE® IC into your own
hardware designs. In the following all ports of UNIGATE® IC are described in detail.
3.1 Ports
UNIGATE® IC features 32 pins in its layout as a DIL 32 component. Pin 10 -12 and 21 - 23 as
well are not wired due to the electrical isolation. The exact mechanical dimensions can taken
from chapter 12 on page 38.
In the layout boreholes for ALL 32 pins have to be planned.
3.2 Pinout
Pin Technical Name Description Remark
specifications
1 5V ± 5% < Typ 170mA Vcc + 5 V voltage supply see chapter 12.2.1 on page 39
3.3V ± 5% < Typ 170mA + 3.3V voltage supply (optionally
at PBL)
2 INLogic -BE boot enable
3 OUTDriver Load out strobe signal for synchronous,
(SS0-) serial interface
4 OUTDriver Data out output data for synchronous,
(SS1-) serial interface
5 INLogic Data in input data of the synchronous, internally pulled up with 10 k
(MISO) serial interface
6 OUTLogic Load in input data of the synchronous,
(MOSI) serial interface; alternatively
strobe signal of the output data
7 OUTDriver Clock clock pulse signal for synchro-
nous, serial interface
8 INReset -Reset in reset-input of the IC internally pulled up with 100 k
9 connected to pin 1 Vcc + 5 V voltage supply
10-12 nc nc no pin available
13* according to norm PB-A PROFIBUS-signal according to galvanically isolated 
TxPB1) standard insulation voltage 1000 Vrms
14* according to norm PB-B PROFIBUS-signal according to galvanically isolated 
RxPB1) standard insulation voltage 1000 Vrms
15* according to norm PB-RTS PROFIBUS-signal according to galvanically isolated 
standard insulation voltage 1000 Vrms
16-18 according to norm nc not connected
19* according to norm PB-GND PROFIBUS-signal according to galvanically isolated 
20* according to norm PB-5V PROFIBUS-signal according to galvanically isolated 
21-23 nc nc no pin
24 connected to pin 32 GND ground supply voltage of the IC
25 OUTTristate LED-PB bus error LED of the PROFIBUS 8 mA, internal series resistor 
5V = 1.5 kVR
26 INLogic -Config Mode signal to start the configuration internally pulled up with 10 k
mode
27 OUTLogic DbgTX serial Debug TX
28 INLogic DbgRX serial Debug RX internally pulled up with 10 k
29 INLogic RX serial data RX internally pulled up with 10 k
30 OUTLogic TX serial data TX

Deutschmann Automation GmbH & Co. KG Hardware design
31 OUTLogic TE transmit enable

32 GND GND ground supply voltage of the IC

The PROFIBUS signals are galvanically isolated. The insulation voltage is 1000 Vrms.
1)
Version without 485 (ROFIBUS) - driver (see chapter 3.7 and chapter 3.10.2).
*) The version “LWL“ (without galvanic isolation on the PROFIBUS-side) has the TTL-signals directly avai-
lable at the pins 13, 14 and 15. The pins 19 and 20 are not connected, since for the LWL-version no galva-
nic separated PROFIBUS-voltage is required or it is generated by itself (see chapter 3.10.3).
5V ± 5%, < 250mA VIL VIH

INReset < 0.3V / 5mA >1.95V / 10µA
INLogic < 0.8V / 0,5mA >1.95V / 10µA
VOL VOH
OUTLogic < 0.6V / 1mA >3.8V / 0.1mA
OUTDriver < 0.33V / 4mA >3.8V / 4mA
3.3V ± 5%, < 250mA VIL VIH
INReset < 0.2V / 4mA >1.5V / 10µA
INLogic < 0.5V / 0.4mA >1.5V / 10µA
VOL VOH
OUTLogic < 0.6V / 1mA >2.3V / 0,1mA
OUTDriver < 0.5V / 4mA >2.5V / 4mA
3.2.1 -Boot enable

The IC is started in the firmware update mode with the level GND during the power up process.
See also chapter 11 on page 37.
3.2.2 Load out (SPI-Master: SS0-)

Strobe signal for the synchronous serial interface. With the positive edge at this output data is
taken from the connected shift registers to the physical outputs.
In SPI mode this Pin serves as a low-active Slave-Select-Signal.
3.2.3 Data out (SPI-Master: SS1-)

On this line data is output on the synchronous serial interface. The most significant bit of the data
is output first.
In SPI mode this Pin serves as a low-active Slave-Select-Signal.
3.2.4 Data In (SPI: MISO)

Data is read in on the synchronous serial interface via this signal. The most significant bit of the
data is expected first.
In SPI mode this Pin serves as data transfer from Slave to Master.
3.2.5 Load In (SPI: MOSI)

This pin is the strobe signal for the input data of the synchronous serial interface.
In SPI mode this Pin serves as data transfer Master to Slave.
3.2.6 Clock (SPI: SCK)

This signal is the clock line for the synchronous serial interface. That signal is equally valid for
data input and data output.
3.2.7 -Reset In
• A reset generator (Max 809) is on board; with it in the normal case the reset input is not
required. In this case the reset input has to be connected with VCC, in order to avoid interfer-
ences (see chapter 3.6).

• If the customer’s application has to initiate a reset of the UNIGATE® IC, then the reset input can
also be connected with a reset output of the customer’s application instead of connecting it with
VCC. Here all specifications of the reset signal, mentioned in chapter 3.2 have to be kept. The
reset-impulse is supposed to last at least 10 ms.
3.2.8 LED-PB
A red LED can be connected to this line. It is controlled by the PROFIBUS ASIC and goes out in
the state „Data Exchange“. (see chapter 3.6)
3.2.9 -Config Mode

If the pin has the level GND, then the IC starts in the configuration mode.
3.2.10 DbgTX, DbgRx

They are transmission line and receive line as well of the IC’s Debug-interface. For the function
description of the Debug-interface see chapter 6.
3.2.11 TE
The Transmit Enable Signal allows the connection of RS485 drivers to the IC’s serial interface.
The signal is set to High whenever the IC sends via the line TX.
3.2.12 TX, RX
Transmission and receive line of the serial interface. This interface is programmable in accor-
dance with the description in chapter 4.
3.3 Software
The software executes script-commands, which in turn control the IC’s hardware and they pro-
cess their complete protocol by software. The script itself can be generated by the company
Deutschmann Automation or with the software Protocol Developer by yourself. For a detailed
description of the script.commands of the Protocol Developer see the instruction manual Proto-
col Developer and the online documentation concerning script-commands.
3.4 Basic line of proceeding

In theory it is enough to replace the RS232-driver that is included in your application by the UNI-
GATE® IC.
Max 232
Customer
Processor .
. .
. .
. .
U
A
. .
R
T
9-pol DSUB
RS232

Your device, which on the whole is supposed to be assembled as shown above, will now be mod-
ified in a way that the PROFIBUS is available at the 9-pol. socket. However, a hardware redesign
is necessary in order to keep the assignment in standard form.
UNIGATE®-IC
Customer
Processor
.
. .
. .
U U . .
A A
R R
. .
T T
9-pol-DSUB
Profibus
After the RS232-driver has been replaced by the UNIGATE® IC, the PROFIBUS is available at
the 9-pol. D-sub-socket.
Deutschmann Automation is also offering an appropriate adapter board. With it existing devices
can be adapted without re-design; see chapter 13.
3.5 Connection examples

Here you will find some advise that offers help for a re-design. In the following several versions
are listed, that should make it easier for you to decide.
Version 1: Use as a pure link module for the bus
M icrocontroller U N IG A T E
IC
Profibus
D -Sub
U
A
UART
R .
T . .
1
. .
Profibu s
. .
U
N ot used A . .
R
T
2
S
N ot used Y
N
S
E
R
The UNIGATE® IC independently processes the communication with the customer’s device via
the TTL-interface.

Version 2: Use of UNIGATE® IC for digital or analog I/O-modules
Out N-M Out 1-8
8 8
UNIGATE
IC

SR SR Profibus
D-Sub
U
Not used A
R .
T . .
1
. .
. .
U
Not used A . .
R
T
2
S
Y
SR 
SR N
S
E
R
8 8
IN N-M IN 1-8
Here only the synchronous serial interface is used, the asynchronous serial interface is basically
of no account. If you want to program the script in your completed application, then the use of a
connector for the asynchronous interface is recommended. With it you can carry out the ISP-pro-
gramming.
For this operating mode no additional controller is required on your application!

The following circuit diagram is an example for how shift register components can be connected
to the IC.
Version 3: Example for digital I/Os

The serial synchronous and the asynchronous interface as well can be operated by UNIGATE®
IC at the same time. Here the possibility results that an existing application can be extended by
additional digital or analog I/Os.
In chapter 5.2 you find an example for a script, that operates these I/Os.

Valid for all versions: A planed plug connection of the serial interface in the application offers the
possibility of an update of the firmware or the software via an external connection.
D-Sub
customer U UNIGATE
processor UART
A IC .
R
T Profibus . .
1
. .
connector
. .
U
A . .
R
T
connector 2
S
IN Y
N
S
Out E
R
3.6 Layout examples
The connection of the two PROFIBUS-lines (PB+ and PB-) are to be

implemented as short as possible, in order to avoid reflections and with
it disturbances on the PROFIBUS line!
If these stub-lines (PB+ and PB-)are too long, communication problems
may arisewhen operating at higher bus speeds (> 1.5 Mbaud). According
to the PROFIBUS Test Specification, the max. allowed total length of all
stub-lines on a bus segment is 80mm at 12 Mbaud. Over a full bu sseg-
ment of 32 nodes this equals 25mm.

The 74HCT595 used in this example has an undefined on-position, but

therefor can set the outputs to the tri-state condition via the OutEnable-
Pin 13. If it is more important to have a defined on-position in an applica-
tion, and the OutEnable-pin is not necessary, the 74HCT594 can be used
here.


3.7 Operation with external PROFIBUS-driver
Note: Only in connection with IC-version “without 485 (PROFIBUS) - driver“.
3.8 Termination (PROFIBUS)

Generally it is recommended to use a PROFIBUS connector with integrated bus termination. If
this is not possible a switchable terminating resistor (220 R) can be integrated on the carrier
board. In this case furthermore a Pull-Down-resistor (390 R) to PB-GND and a Pull-Up-resistor
(390 R) to PB-5V has to be intergrated.
3.9 Handling (mounting the UNIGATE® IC on the carrier board)

Depending on the application and the expected shock- and vibration-conditions you can choose
from the following possibilities for the UNIGATE® IC’s installation on the carrier board:
• Mounting on a socket in the carrier board. If necessary solder the UNIGATE® IC to 2 or 4 pins
in the socket. Normally the IC can easily be pulled out after the soldering points have been re-
moved.
• Make arrangements for two holes next to the socket in the layout. After the UNIGATE® IC was
plugged in the socket pull an isolated wire over the IC and solder it on the carrier board at the
specified holes.
• Fasten the UNIGATE® IC With a wire or a tie wrap on the socket.
• Manual soldering directly on the carrier board.
• Automatic soldering directly on the carrier board, whereas „selective“ soldering is essential (no
wave soldering)

The advantage of the socketed variant is the easy download of Script- and Firmware-updates, if
the carrier board is not designed for it. Besides, that way the Fieldbus can be changed easily by
changing the UNIGATE® IC if the corresponding plug connectors are provided on the carrier
board. Another advantage is, that - normally - only a reflow soldering of the carrier board is ne-
cessary.
The advantage of the soldered variant is, that the installation height is lower and a higher shock-
and vibration-safety is provided.
3.10 Differences between the various versions

3.10.1 Standard version
(e. g. V3473 UNIGATE® IC-PBDPL-5V)
In the regular version, that is usually used, the IC is ”fully assembled”, which means that you only
have to provide for the D-Sub and you are all set! (take a look at the layout example "UNIGATE®
IC PROFIBUS DP variant1” in chapter 3.6)
3.10.2 Version "without 485 (PROFIBUS)-driver"

(e. g. V3626 UNIGATE® IC-PBDPL-5V-without RS485-driver)
The solution ”without driver” should be used for applications, where the UNIGATE® IC cannot be
arranged within close proximity to the PROFIBUS-connector. The technical background is as fol-
lows: Up to 32 participants can be operated in one segment of the PROFIBUS. The higher the
used baud rate the more critical the stub lines on the PROFIBUS line. Here you have to watch
out since each connection from the PROFIBUS connector to the driver is to be considered as
stub line. In practice you can proceed on the assumption that lines with a maximum length of
25mm will not be a problem, even in case of the highest baud rate (12 MBaud), that means, if the
line between UNIGATE® IC and PROFIBUS-connector is shorter than 25mm, then you can use
the standard UNIGATE® IC. In case of a longer distance you should use the version "without 485
(PROFIBUS)-driver" (see chapter 3.7).
3.10.3 Version "LWL"

(e. g. V3743 UNIGATE® IC-LWL-PBDPL-5V)
Apart from the driver (see above) the LWL-version is also missing the complete galvanic isolation
(optocoupler and DC/DC-converter).
This version can - as its name implies - be used for an LWL-connection.
They also find use at customers, where our 1kV galvanic isolation is not sufficient. These cus-
tomers are then in the position to provide for a ”better” galvanic isolation in their design exter-
nally.
If our customers hava a problem with the height of the UNIGATE® IC (DPL and DPX), then this
version can also be used. Here the DC/DC-converter, that determines the height in this case, can
be mounted on the customer‘s circuit board.

Deutschmann Automation GmbH & Co. KG The serial interface
4 The serial interface

4.1 Overview
The serial interface is the most important connection between the UNIGATE® IC and the micro
controller of your application. The interface is designed in a way so that your application at least
does not have to be changed on the software-side. The wide range of services of the UNIGATE®
IC’s serial interface constitutes the basis for it. The UNIGATE® IC allows to connect controllers
with a baudrate of 110 bit to 625 kbit. The baudrate for the communication itself is permanently
stored in the module. The maximum size for the IO-data kann be taken from the table in chapter
12.2.1, line „RS-buffer size“. Furthermore the maximum size for IO-data can be read-out with the
Script command “Get RSOutBufFree16“.
Depending on the read-in script of the UNIGATE® IC, the module carries out actions indepen-
dently, in order to identify data from the connected device. For customers who already have a
software-adaptation at he company Deutschmann Automation, this protocol as well or a Script
after an adaptation can be processed by the IC.
Anyway, the IC will take over the communication with the fieldbus independently.
4.2 Initialization of the serial interface

The initialization of the interface is carried out by script-commands, such as “Set baudrate“,
“Set databits“, “Set parity“. For a detailed description of these commands see the online
documentation for the Protocol Developer or the instruction manual for the Protocol Developer.
4.3 Use of the serial interface

The serial interface can freely be programmed by the user. Efficient script-commands for sending
and receiving data are available; just to mention some possibilities: such as waiting with timeout
for a character, waiting for a fixed number of characters or also sending and receiving data in the
Modbus RTU. A reference to these commands is offered in the online documentation for the Pro-
tocol Developer as well as in the instruction manual for the Protocol Developer.
4.4 Further operation modes

In the modes configuration mode and firmware-update mode the serial interface also serves to
configure the standard software or to carry out a firmware-update. More details can be found in
chapter 11.5.

Synchronous serial interface Deutschmann Automation GmbH & Co. KG
5 Synchronous serial interface

The synchronous serial interface of the UNIGATE® IC is used to connect clocked shift registers
or components that have a Serial Peripheral Interface (SPI).

It allows
• the expansion of the IC for digital inputs and outputs (for example for driving LEDS or for
reading switch positions)
• communicate with microcontrollers or
• the control of DA and AD converters.
Connection examples are give in chapter 3.
By using the synchronous serial interface can realize products that can work without another
microcontroller (stand-alone mode). Examples are sensor products or digital IO modules
5.1 Shift register operation

Before the interface can be used, it has to be initialized by setting various Script parameters.
(see chapter 5.1.1)
The parameters „ShiftRegisterInputType“ and „ShiftRegisterOutputType“ allow the
use of different shift register types, which differ in the polarity of the shift register signals. To use
the shift register types 74595 and 74165, for example, the values „RiseClk_RiseLoad“ and
„RiseClk_LowLoad“ can be set.

The shift register width is set by the parameter „ShiftRegisterInputBitLength“ and
„ShiftRegisterOutputBitLength“ The maximum width is 256 bits.

The data exchange with the connected shift registers ensues with the commands „Write-
ShiftRegister“, „ReadShiftRegister“ or bidirectional with the command „ShiftRegis-
terDataExchange“. The clock rate is between 280 kHz and 320 kHz.

Further information on the commands and parameter values can be found in the Help section of
the Protocol Developer Software. On request, the Deutschmann Script language can be comple-
mented by additional parameter values in order to support other types of shift registers.
5.1.1 Example-Script
Note: The script example refers to the circuit example in chapter 3.5.
var InBuffer: Buffer[2];

var OutBuffer: Buffer[2];
MoveConst( OutBuffer[0], #0x58#0x21 );
Set( ShiftRegisterInputType, RiseClock_FallLoad );

Set( ShiftRegisterOutputType, RiseClock_RiseLoad );

Deutschmann Automation GmbH & Co. KG Synchronous serial interface
Set( ShiftRegisterInputBitLength, 16 );

Set( ShiftRegisterOutputBitLength, 16 );
WriteShiftRegister( OutBuffer[0] );

ReadShiftRegister( InBuffer[0] );
// Input data is now in the INBuffer

// 0x58 is applied to the outputs of the analog converter
// 0x21 at the shift register‘s outputs
5.2 SPI mode

Before the interface can be used in SPI mode, this must be initialized. The command InitSPI
sets the operating type, the mode (signal polarity and phase) and the clock frequency.
The data exchange ensues with the command ExchangeSPI. The maximum clock frequency is
between 1 and 5 MHz, depending on the hardware. For details please see the IC-Pinout list in
the download area of our website.
Please also refer to the script commands documentation in the online help of the Protocol Devel-
oper.
5.2.1 Example-Script
var L_Freq : long;
var b_Channel : byte;
var w_Len : word;
var a_BufOut : buffer[100];
var a_BufIn : buffer[100];
moveconst( L_Freq, 1000000); // 1 MHz

InitSPI( 1 , 0 , L_Freq );
moveconst( b_Chanel, 0 );

moveconst( w_Len, 11 );
moveconst( a_BufOut[0], "Hello World" ); 
ExchangeSPI( b_Channel , w_Len , a_BufOut[0] , a_BufIn[0] );

The Debug-interface Deutschmann Automation GmbH & Co. KG
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® IC (power up) the firmware will output the binary
character 0 (0x00) after a self-test was carried out on this interface. If the IC 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.
6.5 Commands of the Debug-interface

The commands for the use of the Debug-interface are described in the instruction manual Proto-
col Developer.

Deutschmann Automation GmbH & Co. KG Script and configuration
7 Script and configuration

7.1 Overview
The script stored in the UNIGATE® IC, as well as the configuration, can be replaced or updated
via the serial interface (application) in the configuration mode.
7.2 The configuration mode

If the pin „ConfigMode“ pulled to GND during the PowerUp or Reset, then the UNIGATE® IC
starts in the configuration mode. In this mode it is possible to communicate with the IC without
processing the regular software. In this mode it is possible to change the UNIGATE® IC’s settings
of the standard software or to write a new script in the UNIGATE® IC. It shows its start in the con-
figuration mode by issuing a status message, which might look as follows:
IC-PB-SC V5.9A[25] (c)dA Script(2k)="Leer" Author="Deutschmann Automation GmbH"
Version="1.0" Date=21.08.2001 SN=47110001 ID=1
The configuration of a UNIGATE® IC is restricted to setting the PROFIBUS-address (see also
chapter 9.2 ’Setting the PROFIBUS-address’).
7.3 Update the script

• The preferred option is to insert the UNIGATE® IC into the base board from Deutschmann
(Developer Board UNIGATE® IC-AB) and use the Deutschmann tools (software WINGATE with
„Write Script“ under „File“ or with the software ScriptProgramTool).
• Your host can also automatically replace the script in your application. In the following flow
chart the handshake is shown.

Script and configuration Deutschmann Automation GmbH & Co. KG

Deutschmann Automation GmbH & Co. KG Script and configuration
The operational sequence is as follows:
The Gateway has to be in the config-mode.

The script-download is initiated with "Ctrl-P (=0x10)".
After that the data follows byte by byte as ASCII-hex-characters.
The download is terminated with a "LF (=0x0A)".
Afterwards the word-checksum follows as ASCII-hex-characters.
The Gateway responds with a clear text reply to that download and carries out a warm start.
Example:
The following 4-bytes script is supposed to be downloaded: 0x01 0x12 0x5A 0x23
The sum of the bytes is 0x0090 as checksum.
Then the following sequence is to be sent:
1. 0x10 Ctrl-P
2. 0x30 '0'
3. 0x31 '1'
4. 0x31 '1'
5. 0x32 '2'
6. 0x35 '5'
7. 0x41 'A'
8. 0x32 '2'
9. 0x33 '3'
10. 0x0A LF
11. 0x30 '0'
12. 0x30 '0'
13. 0x39 '9'
14. 0x30 '0'
Gateway’s reply: "Download ok"
7.4 Configuration of the UNIGATE® IC

UNIGATE® IC is delivered with an empty script.
The configuration of the UNIGATE® IC - PROFIBUS DP is restricted to the setting of the fieldbus
address, that can be changed with the software WINGATE®.
7.4.1 PROFIBUS
• Configuration data: In accordance with GSD file (DAGW2079 or UGIC3218)
• Diagnostic data : Max. 8 bytes (see chapter Error handling)
• Baud rate: Automatic detection up to 12 MBaud
• Sync: Supported
• Freeze: Supported
• Ident. No.: 0x2079 or 0x3218

Script and configuration Deutschmann Automation GmbH & Co. KG
7.4.2 RS232/RS485/RS422
• RS type: RS232
• Start bit: 1
• Data bits: 8
• Stop bit: 1
• Parity: None
• Baud rate: 9600 Baud
Default setting This configuration can be changed via the Script.

Deutschmann Automation GmbH & Co. KG Generating a script
8 Generating a script
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
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
8.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.
8.7 Accuracies of the baud rates at UNIGATE® IC

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!

Deutschmann Automation GmbH & Co. KG Generating a script
In the following please find a listing of baud rates at a 40 MHz-crystal frequency with the corre-
sponding errors:
4800 baud: 0.16%
9600 baud: 0.16%
19200 baud: 0.16%
38400 baud: 1.35%
57600 baud: 1.35%
62500 baud: 0%
115200 baud: 1.35%
312500 baud: 0%
625000 baud: 0%
8.8 Script processing times

The Script is translated by the Protocol Developer and the consequently generated code is
loaded into the Gateway. Now the processor in the Gateway interprets this code. In this case,
there are commands that can be processed very fast (e. g. "Set Parameter"). There are also
commands, however, that take longer (e. g. copying 1000 bytes). Consequently, for one thing the
processing time differs due to the kind of Sript command. But the processing time of the Script
commands is considerably more determined by the processor time that is available for this pro-
cess. Since the processor has to carry out several tasks simultaneously (multitasking system)
only a part of the processor's capacity is available for the Script processing. The following tasks -
in the order of priority - are executed on the processor:
• Sending and receiving data at the Debug-interface (provided that the Protocol Developer has
been started on the PC)
• Sending and receiving data at the RS-interface
• Sending and receiving data at the Fieldbus-interface
• Tasks controlled via internal clock (1 ms) (e. g. flashing of an LED)
• Processing of the Script
From experience approximately 0.5 ms can be calculated for each Script line. This value con-
firmed itself again and again in many projects as a standard value. He is always quite right if the
processor has enough time available for the Script processing.
By means of the tasks mentioned above, the following recommendation can be formulated in
order to receive a rather fast Script processing:
• Deactivate the Debug-interface (it is the normal case in the serial use)
• Keep the data length at the RS-interface as small as possible. The baud rate is not the problem
here, but the amount of characters which are transferred per second.
• Do not unnecessarily extend the data length at the Fieldbus side. Especially at acyclical bus
data, if possible do only send them when changes were made. The data length at buses that
are configured to a fixed length (e. g. PROFIBUS) should not be longer than absolutely neces-
sary.
If the processing time should be too large in spite of these measures, there is the possibility to
generate a customized Script command, that executes several tasks in one Script command.
Please contact our support department for this purpose.

PROFIBUS DP Deutschmann Automation GmbH & Co. KG
9 PROFIBUS DP
At present UNIGATE® IC PROFIBUS DP supports PROFIBUS DP as version DPV0 - DPV2. Any
imaginable combination of input- and output-quantities is possible. In case a desired combination
is not included in the GSD files (DAGW2079.GSD, UGIC3218.GSD) it can be described by stat-
ing configuration octets (see chapter 15).
The UNIGATE® IC automatically supports the PROFIBUS functions Sync and Freeze.
From V. 7.0 (IC-PB-DPL) on user parameters are supported.
9.1 Description of the DPV1- / DPV2-functions

9.1.1 DPV1
The DPV1-enlargement consists of the following functions:
1. Acyclic data exchange with Class1-Master (e. g.: PLC)
This function is optional for a DPV1-Slave. Our gateways support this function as a default. By
means of this function the Class1-Master can read and write data from the slave acyclically. This
data is processed by the script in the gateway. The channel for the acyclic data exchange is set
up firmly during the parameterization.
2. Acyclic data exchange with Class2-Master (e. g.: control unit)
This option is optional for a DPV1-Slave as well. Our gateways support this function as a default.
By means of this function the Class2-Master can read and write data from the slave acyclically.
This data is processed by the script in the gateway. The channel for the acyclic data exchange is
set up prior to every data exchange and closed again afterwards.
3. Alarm handling
Also the alarms are optional. If they are activated, they replace the device-specific diagnosis. At
present our gateway does not support alarms.
Every DPV1-Slave must support the extended parameterization since it is determined in Octet 8
of the parameterization telegram whether it is a DPV0- or a DPV1-Slave.
A DPV1-Slave can also be operated at a DPV0-Master if the DPV1-functions remain turned off.
9.1.2 DPV2
The DPV2-enlargement consists of the following functions:
1. Isochron Mode (IsoM)
It means the clock-synchronous behavior of a bus system. This function is optional for a DPV2-
Slave and is activated via the GSD-file. At present our gateway does not support this mode.
2. Data Exchange Broadcast (DxB)
It means the communication between Slaves (inter-communication). This function is optional for
a DPV2-Slave and is activated via the GSD-file. At present our gateway only supports the func-
tion of the „Publisher“ (sending data to other Slaves). The function „Subscriber“ (receiving data
from other Slaves) is not supported at present.
3. Up- And Download
This function is also optional for a DPV2-Slave and at present it is not supported by our gateway.
4. Time-synchronization (Time stamp)
5. Redundancy concept

Deutschmann Automation GmbH & Co. KG PROFIBUS DP
9.2 Setting the PROFIBUS-address

There are different possibilities to set the IC’s PROFIBUS-address.
1. Setting the address through the configuration

The UNIGATE® IC has to be in the configuration mode (see also chapter 7.2 ’The configura-
tion mode’). With WINGATE it is now possible to set the address. This address is preserved
until it will be changed again.
2. Setting the address through the Script

The address can be stored in the Script as well. This proceeding, however, is likely to be of
interest for a few applications only, since it is necessary to change the Script in order to also
adjust the PROFIBUS-address (see also the following Script example).
3. Setting the address through the serial interface

The address can also be transmitted to the IC through the serial interface. Then the address
can be set with the Script command "SetByVar". This possibility should be used in case
your device has a control front available and the menu of the front can be extended by the
setting "PROFIBUS-address". The adjustment of the PROFIBUS-address through the serial
interface is the most convenient possibility for those applications.
4. Setting the address through the bus itself

Address 126 is reserved for devices that do not feature the hardware which is required to set
the bus address (such devices with protection class IP 65). Address 126 has to be config-
ured through WINGATE (see point 1.).
.
5. Connecting the rotary switches to the shift registers
Rotary switches can be connected to a shift register as well as to our basis board. Now it is
possible for the Script to read those switches and to set them as fieldbus-address. Basically
the following Script can be used for it.

PROFIBUS DP Deutschmann Automation GmbH & Co. KG
Script example for the initialization of the PROFIBUS

var InSize: word;
var OutSize: word;
Set (FieldbusID, 4) ;
// this parameter can also be set by the command SetByVar.
// var PBAddress: long;
// MoveConst( PBAddress, 4) ;
// or from the shift registers
// SetByVar();
BusStart;
// the Profibus ASIC is ready now.
// from now on the Master CAN configure the participant.
// However, that does not mean that the configuration of the
// participant has already been carried out by the Master.
wait (Bus_Active);
// the Profibus is now in the state of Data Exchange
// This command might take a very long time and is
// not interruptible!
// Now it is also known to the Script with which configuration
// the Slave was put into operation by the Master.
Get ( BusInputSize, InSize);

Get ( BusOutputSize, OutSize);
// Insize and OutSize ar from the IC's point of view!
// It is possible to read out data from the bus

// all available bytes should be read.
var InBuffer: Buffer[100];
Readbus ( InBuffer[0], InSize) ;
// It is now possible to write data.

// You must not write more bytes than available.
var OutBuffer: Buffer[100];
WriteBus ( OutBuffer[0], OutSize );

Deutschmann Automation GmbH & Co. KG Error handling at UNIGATE® IC
10 Error handling at UNIGATE® IC

A distinction can be made between two categories of system-errors:
Serious errors (1-4): In this case, the Gateway must be switched off and switched back on again.
If the error occurs again, the Gateway must be exchanged and returned for repair.
Warnings (6-15): These warnings are displayed for one minute simply for information purposes
and are then automatically reset. If such warnings occur frequently, please inform After-Sales
Service.
The system-error can be read-out via the Script.
In the configuration mode these displays are not valid and only meant for internal use.
Error no. Error description
0 Reserved
1 Hardware fault
2 EEROM error
3 Internal memory error
4 Fieldbus hardware error or wrong Fieldbus ID
5 Script error
6 Reserved
7 RS-transmit buffer overflow
8 RS-receive buffer overflow
9 RS timeout
10 General fieldbus error
11 Parity-or frame-check-error
12 Reserved
13 Fieldbus configuration error
14 Fieldbus data buffer overflow
15 Reserved
Table 1: Error handling at UNIGATE® IC

Firmware-update Deutschmann Automation GmbH & Co. KG
11 Firmware-update
11.1 Overview
UNIGATE® IC has a 64 kbyte flash memory for the firmware. In the firmware-update-mode the
firmware can be replaced via the UNIGATE® IC’s serial interface.
11.2 Adjusting the firmware-update-mode

11.2.1 Adjustment by hardware
UNIGATE® IC can be brought to the firmware-update-mode by the hardware. For it the signal BE
(boot enable) has to be pulled to the potential GND during the Power-up-process.
11.2.2 Adjustment by software

If the UNIGATE® IC is in the configuration mode (see chapter 7.2) it can be brought to the firm-
ware-update-mode interactively through the command CTRL-F (0x06). After sending the com-
mand a security query follows, that has to be answered with J or N (J = Yes, N = No). After a
positive confirmation the IC is re-started in the firmware-update-mode.
11.3 Execution of the firmware-update

The safest way for the firmware-update is the use of the basic board combined with the software
“FDT.EXE“ (firmware-download-tool). These tools are available from Deutschmann Automation
(see chapter 13 on page 40).
It is also possible to use the description and the tools of the manufacturer of the controller
(TEMIC, 89C51RD2) as well.
11.4 Note on safety

The firmware-update should only be carried out when there is no other possibility left. A firm-
ware-update-process that has already been started CANNOT be undone. With it the previously
used firmware is permanently unusable.
11.5 Operation mode of the IC

Standard-operation mode
This mode is required for the regular use of the IC. In this mode the IC will process all script-com-
mands and normally exchange the corresponding user data. The bus as well is operated in this
mode through the IC.
Configuration mode
In the configuration mode the UNIGATE® IC will carry out a self-test after the start (or after a
reset). After a successful self-test it will wait for further commands. Here it is possible to load a
translated script into the unit or to initialize the firmware-download-mode.

Deutschmann Automation GmbH & Co. KG Technical data
12 Technical data
In this chapter you will find all necessary technical data on UNIGATE® IC.
All measurements in mm.
12.1 Mechanics of the UNIGATE® IC

12.1.1 General dimensions of UNIGATE® IC
12.1.2 Dimensions UNIGATE® IC (PROFIBUS DP only)
*) depending on the version (see chapter 12.2.1)
The pins of UNIGATE® IC - PROFIBUS DP are arranged with a grid spacing of 2.54 mm.
DIP-Spacing Code 6
In case you intend to use other fieldbus ICs, the maximum overall height of  20 mm (including
pins) has to be taken into consideration.

Technical data Deutschmann Automation GmbH & Co. KG
12.2 Technical data UNIGATE® IC-PROFIBUS

Characteristics Explanation
Supply voltage 3.3 V / 5 V + 5 %, 170 mA (typ.), 200 mA (max.)
Interface 2 UART interfaces, 1 synchronous serial interface
Physical separation
-fieldbus-side Standard
Fieldbus-ID Adjustable via script
Fieldbus-baud rate Up to 12 MBaud (autodetect)
UART-baud rate Up to 625 Kbaud (adjustable via script)
Fieldbus data format Up to 96 or up to 244 byte I/O (depending on the version)
Technology ASIC
Others Sync, Freeze, e. g. digital I/Os, analogous signals, shift registers, LEDs,
switches and so on can be connected externally
Dimensions 45 x 25 x 9 mm or 45 x 25 x 12 mm (W x D x H)
Installation 32 DIL
Weight Approx. 9 g
Operating temperature -40°C ..+85°C
Storage / transport temperature -40°C..+100°C
Built-in position Any
12.2.1 Features of the different versions

Version
UNIGATE IC UNIGATE IC
Performance UNIGATE IC UNIGATE IC
PROFIBUS PROFIBUS DPX
characteristics PROFIBUS DPL PROFIBUS DP
DPV1 PROFIBUS DPY
Support DPV1 / DPV2 DPV0 DPV1 / DPV2 DPV1 / DPV2
PB-data length 244 byte I/O 96 byte I/O 244 byte I/O 244 byte I/O
RS-buffer size 256 byte 100 byte 1K 1K
Overall height in mm 12 9 9 12
Voltage supply in Volt 5V / 3.3V 5V 5V 5V / 3.3V
Certified Yes Yes Yes Yes
GSD-file ugic3218.gsd dagw2079.gsd ugic3218.gsd ugic3218.gsd

Deutschmann Automation GmbH & Co. KG Accessory
13 Accessory
The following tools are available from Deutschmann Automation.
13.1 Adapter RS232

In an application the adapter RS232 offers the possibility to replace an existing driver MAX 232
(only in DIL-16-housing) by this adapter. This board allows the use of the IC according to chapter
3.4 on page 13. Please note that with it the PROFIBUS does not offer a connection conforming to
the standards. With a plug adapter, however, at least the operation of PROFIBUS is possible.
The hardware is only meant for development purposes. It offers the possibility to make an
existing application capable for bus connection in no time and to test the IC’s utilizability and
functionality.
13.2 Adapter RS485

From the functionality’s point of view the RS485 adapter is the same as the RS232 adapter. It
offers the possibility to replace a module LS 176 (only in DIL-8-housing) by the IC.
There are the same restrictions as for the RS232 adapter.
13.3 FirmwareDownloadTool (FDT)

The FirmwareDownloadTool is available for download from our homepage: it is required for an
update of the firmware. Condition for it is, that a PC can be connected to the serial of the IC. The
software describes the procedure of an update itself.
13.4 Protocol Developer

The Protocol Developer is the development environment for scripts, that also contain the Debug-
ger. This software package also contains the documentation to all script-commands. This soft-
ware is available for download from our homepage at http://www.deutschmann.com. The
instruction manual for the Protocol Developer, which is available in pdf-format, gives further
advise on how to use the software.
13.5 Developerkit UNIGATE® IC-AB IC

The Devloperkit IC contains
• a Developerboard UNIGATE® IC (see chapter 13.5.1)
• a plug-in power pack to supply the Developerboard
• connection cables for appl. RS232, Debug RS232 and appl. RS422/485
• USB-cable
• Software and documentation to complete the packet.
13.5.1 Developerboard UNIGATE® IC-AB

The Developer Board was developed so that the fast implementation of the Deutschmann All-in-
one bus node UNIGATE® IC into your electronic system can be guaranteed. The board is suit-
able for all Fieldbuses and Industrial Ethernet Buses supported by Deutschmann Automation.

Accessory Deutschmann Automation GmbH & Co. KG
The required UNIGATE® IC / ICs are ordered separately. The required voltage (5V or 3.3V,
depending on the version) can be adjusted. An RS232-interface or a USB-connection is avail-
able for the connection to the PC (Debug-interface).
The application can be connected either through the USB, RS232, RS485 or the RS422.
The bus-connections according to standard or market standard are available to test the respec-
tive bus-side. Optionally Deutschmann Add-on packages (bus-master simulation) are available.
The board contains 32 bit input and 16 bit output, provided with one LED each. Different connec-
tors allow an easy coupling to your processor. A hole matrix field with the most important signals
(voltage, IOs) allows a customized hardware extension (e. g. to connect a D/A converter).
13.5.2 Quick start
For a transparent data exchange you can load the file

File -> New -> „Profibus_IC_BasisBoard.dss“
that is stored in the Protocol Developer.

Deutschmann Automation GmbH & Co. KG Appendix
14 Appendix
14.1 Explanations of the abbreviations
General
CL = Product group CL (Compact Line)
CM = Product group CM (CANopen Line)
CX = Product group CX
EL = Product group EL (Ethernet Line)
FC = Product group FC (Fast Connect)
GT = Galvanic separation RS-side
GY = Housing color gray
MB = Product group MB
RS = Product group RS
SC = Product group SC (Script)
232/485 = Interface RS232 and RS485 switchable
232/422 = Interface RS232 and RS422 switchable
DB = Additional RS232 DEBUG-interface
D9 = Connection of the RS through 9-pin D-SUB instead of 5-pin screw-plug connector
PL = Board only without DIN-rail module and without housing cover
PD = Board only without DIN-rail module and with housing cover
AG = Gateway installed in a die-cast aluminum housing
EG = Gateway installed in a stainless steel housing
IC = Product group IC (IC-design DIL32)
IO8 = Option I/O8
16 = Script memory expanded to 16KB
5V = Operating voltage 5V
3,.3V = Operating voltage 3.3V
Fieldbus
ASI = AS-Interface (AS-i)
BI = BACnet/IP
BMS = BACnet MSTB
CO = CANopen
C4 = CANopen V4
C4X = CANopen V4-version X (see comparison table UNIGATE® IC for the respective
product)
DN = DeviceNet
EC = EtherCAT
EI = Ethernet/IP
FE = Ethernet 10/100 MBit
FEX = Ethernet 10/100 MBit-version X (see comparison table UNIGATE® IC for the
respective product)
IB = Interbus
IBL = Interbus
LN62 = LONWorks62
LN512 = LONWorks512
ModTCP = ModbusTCP
MPI = Siemens MPI®
PL = Powerlink

Appendix Deutschmann Automation GmbH & Co. KG
PN = PROFINET-IO
PBDP = PROFIBUS DP
PBDPL = PROFIBUS DP-version L (see comparison table UNIGATE® IC for the respective
product)
PBDPX = PROFIBUS DP-version X (see comparison table UNIGATE® IC for the respective
product)
PBDPY = PROFIBUS DP-version Y (see comparison table UNIGATE® IC for the respective
product)
PBDPV0 = PROFIBUS DPV0
PBDPV1 = PROFIBUS DPV1
RS = Serial RS232/485/422
14.2 Basis board
The basis board that is descibed in this chapter was supplied until the
end of 2008.
A new board is available since the beginning of 2009 (see chapter
13.5.1).
14.2.1 Overview basis board PROFIBUS DP

Slot X 1 (ZIF-socket)
PIN 1 of the IC is located up at the lever of the ZIF-socket.
Never place the IC into the socket back to front!
P2
Pin Signal
Pin 1 24 V DC
Pin 2 Ground
The basis board is supplied with voltage through this plug connector.
P4
Earth terminal 6.3 mm for basis board.
P7
This plug is the basis board’s serial connection to the customer’s device and the connection to
the PC (Debug-interface).
For the pin assignment see chapter 14.2.2.1.
P8
The illustration shows the arrangement of the pins. On this connector strip the signals of the
serial connection between IC and RS-drivers are wired. For an initial development you will prob-
ably also use an existing driver in your application. In order to exchange it later on, you can also
directly take the signals of the serial interface here.
P 10
PROFIBUS plug connector, for the assignment of the connector see chapter 14.2.2.2.
P 11

Force Boot. By setting this bridge the Pin BE is dragged to Ground. For the function see chapter
11.2.1.
P 13
Status signal of the IC

Plug connector P 13
Pin Signal
1 Vcc
2 Gnd
3 -RESET
4 RX of the IC (TTL-level)
5 TX of the IC (TTL-level)
6 TE Pin IC (TTL-level)
7 TX Debug of the IC (TTL-level)
8 RX Debug of the IC (TTL-level)
P 14, SW5H, SW5L

Input shift register
For a detailed assignment and for information on which pin is assigned to which bits, see also
chapter 5.
Connection Pin Meaning

P 14 1 Input 9
..... .....
8 Input 16
SW5H 1 Input 25
..... .....
4 Input 28
SW5L 1 Input 29
..... .....
4 Input 32

P 15, SW1H, SW1L

Input shift register
Basically the same applies as for P 14, with the exception that different input bits of the shift reg-
isters are wire.
Connection Pin Meaning

P 12 1 Input 1
..... .....
8 Input 8
SW1H 1 Input 17
..... .....
4 Input 20
SW1L 1 Input 21
..... .....
4 Input 24
P 16
All digital outputs of the shift registers are available here. Additionally the LEDs D9, D15..D18,
D20 are connected to the shift registers.
P 17
With P17 the UNIGATE® IC can be brought into the configmode. If the jumper is plugged and if
the UNIGATE® IC is restarted (by power off and power on or by reset), then the UNIGATE® IC
will start in the configmode. In order to use the configmode with Deutschmann software tools the
interface of the board has to be in RS232-position and the PC has to be connected with the „nor-
mal“ interface, where otherwise your application is connected to.
See also chapter 7.2.
SW1H, SW1L, SW5H, SW5L
The rotary switches SW1H, SW1L, SW5H, SW5L are plugged into the base boards and can be
removed if required. As a default the rotary switches are plugged in and can be read in through
the basis board’s shift registers base boards (see also chapter 5 for it).

SW3, SW4
These switches are required for the setting of the serial interface. The switch SW3 is used to
switch between interface RS232 and RS485. This is the interface, the customer’s device is con-
nected to. The Debug-interface always has RS232-level.
The switch SW4 is of importance only, when it is an RS485-interface. Then this switch can be
used to connect the termination of the RS485-bus.
Each switch position can be taken from the illustration.
D12
Power LED
This LED is always supposed to be shining statically green when the board is supplied with volt-
age.
D9, D15..D18, D20
LEDs that are connected to the shift register components. (see also chapter 14.2.3 ’Wiring dia-
gram UNIGATE® IC-basis board PROFIBUS DP’).
D12
Bus Error LED (red)
This LED goes out in the state ’Data exchange’.
14.2.2 Connectors of the basis board

14.2.2.1 Connector to the external device (RS-interface)
The connection cable to the external device must be plugged in at the connector accessible on
the underside of the device.
Pin assignment P7 (9-pin Sub-D, plug)
Pin No. Name Function
1 Not connected Not connected
2 Rx/RS485- / RS422- (Tx) Receive signal customer’s device
3 Tx/RS485+ / RS422+ (Tx) Transmit signal customer’s device
4 Tx / Diag Transmit signal Debug interface
5 GND RS Ground connection, reference for PIN 2+3+6+7
6 RS422- (Rx)
7 RS422+ (Rx)
8 Not connected Not connected
9 Rx / Diag Receive signal Debug interface
Attention:
In case the RS-interface is NOT potentially divided, "GND" and "supply
0V" are connected internally.

Pin assignment P2 (2-pin screw-type/plug connector)

1 10.8...30 V / DC 10.8...30 V supply voltage
2 0 V / DC 0 V supply voltage
14.2.2.2 PROFIBUS DP connector

The connector for connection to PROFIBUS is located on the upper side of the device.
Pin assignment P10 (9-pin Sub-D, socket)

1 Shield
2
3 B Non-inverting input/output signal from PROFIBUS
4 CNTR-P Control signal
5 M5 DGND – data reference potential
6 P5 5 V supply voltage
7
8 A Inverting input/output signal from PROFIBUS
9
14.2.2.3 Power supply of the basis board

The device must be powered with 10.8-30 VDC.
Please note that the devices of the series UNIGATE® with 9-pin D-SUB connector, the power
supply is routed via the separate 2-pin screw-type/plug connector.
Please pay attention to the fact that devices of the series UNIGATE® cannot be operated with AC
voltage.
14.2.2.4 Shield terminal lead
The shield signal for the electronic circuitry is connected to the top-hat rail via the connector pro-
vided. The shield signal for the PROFIBUS cable shield is not electrically connected to the shield
signal of the electronic circuitry for reasons relating to interference immunity.
14.2.2.5 Rotary coding switches
The rotary coding switches are socketed and can be taken off, in order to alternatively use the
pins of the shift register.
14.2.2.6 Slide switch (RS485/RS232 interface)
This slide switch is used to select whether an RS485 interface or an RS232 interface is con-
nected at the connector to the external device.
14.2.2.7 Slide switch (RS485 termination)
If the Gateway is operated as the first or last physical device in the RS485 bus, there must be a
bus termination at this Gateway. In order to do this, either a bus terminating resistor in the con-
nector or the resistor (150) integrated in the gateway must be activated. In order to do this,
slide the slide switch to position ON. In all other cases, the slide switch must remain in position
OFF. Please refer to the general RS485 literature for further information on the subject of bus ter-
minations.
If the integrated resistor is used, please allow for the fact that this also activates a pull-down
resistor (390 ) to ground and a pull-up resistor (390) to VCC.
At the RS422-interface the transmission line is terminated. The receive line is always firmly
terminated.

14.2.3 Wiring diagram UNIGATE® IC-basis board PROFIBUS DP



Deutschmann Automation GmbH & Co. KG Representation of the data in PROFIBUS DP
15 Representation of the data in PROFIBUS DP

Any standard-compliant PROFIBUS DP Master can exchange data with the gateway. It is also
possible to use very "simple" Master connections owing to the data structure.
15.1 Configuration telegram

After programming, the Master must send a configuration telegram to the corresponding Slave.
The configuration telegram provides the Slave with information on the length of the input/output
data. If the user has set the ’Length byte’ flag, this means the maximum data lengths. Otherwise,
it means the actual lengths.
The user normally also configures the configuration telegram in the project planning tool where
he may also, if necessary, enter the address range in which the useful data is stored.
You can write up to 16 bytes or words in one octet of the DataUnit (DU). Inputs and outputs hav-
ing the same format can be combined in one octet. Otherwise, you must use as many octets as
the number of different bytes/words you wish to use and which cannot be combined in one octet.
If the module detects, during the check, that the maximum permitted input/output data lengths
have been exceeded, it signals incorrect configuration to the Master during a subsequent diag-
nostic scan. It is then not ready for useful data communication.

Representation of the data in PROFIBUS DP Deutschmann Automation GmbH & Co. KG
15.2 Configuration telegram

Octet 1 0
Configuration byte 1
Octet 2 0
Configuration byte x
Structure of an octet in the configuration telegram:
Length of the data

00 = 1 byte / word
15 = 16 bytes / words
Input/output
00 = specific ID format
01 = input
10 = output
11 = input-output
0 = byte, 1 = word
0 = consistent over byte / word

1 = consistency total length

15.3 Diagnosis
Diagnostic data is high-priority data. The gateway runs an external diagnostic if it detects an
internal error.
Representation of the information in the external diagnostic byte:
The diagnostic information of a DP Slave consists of standard diagnostic information items

(6 bytes) and a user-specific diagnostic information item. (Error number)
Telegram for diagnostic request:

Octet 1 0
Diag.station does not exist (sets Master)
Diag.station not_ready: Slave is not ready for

data exchange
Diag.cfg_Fault
Configuration data does not correspond
Diag.ext_diag
Slave has external diagnostic data
Diag.not supported: Requested function is not

supported in the Slave
Diag.invalid_slave_response (sets Slave

permanently to 0).
Diag.prm_fault
Incorrect programming (identification number etc.)
Diag.master_lock (sets Master)

Slave has been programmed by another Master

Octet 2 0
Diag.Prm_req
Slave must be reprogrammed
Diag.Stat_diag
Static diagnostic (byte Diag-Bits)
Permanently set to 1
Diag.WD_ON
Response monitoring active
Diag.freeze_mode
Freeze command received
Sync_mode
Sync command received
reserved
Diag.deactivated (sets Master)
Octet 3 0
reserved
Diag.ext_overflow
Octet 4 0
Diag master_add: Master address after

programming (FF without programming)
Octet 5 0
Ident. number high byte

Octet 6 0
Ident. number low byte
Octet 7 0
External diagnosis: header, length entry
Octet 8 0
UNIGATE® error number
15.3.1 Diagnosis in DPV1

The "external diagnosis" of DPV0 (old PB) is used differently at DPV1. At DPV1 the alarms and
the status messages are transferred there. Since the gateway’s error numbers have been trans-
ferred in the external diagnosis it became necessary then to carry out an adaptation at DPV1.
Now the 3 bytes "0x81, 0x00, 0x00" have been inserted in front of the actual error message in
order to be compatible with DPV1-masters. With it a DPV1-master identifies our gateway’s error
as status message now.
This results in a different representation of our gateway error in PROFIBUS. At DPV0 the error
number is transmitted in unmodified form as 1 byte external diagnosis. In case DPV1 has been
activated in the gateway through the GSD-file, the error number occurs as 1 byte status mes-
sage.
Supposing the DPV1 is activated and a master (which does not support the alarms and status
messages) is connected, then our gateway error number is presented as "external diagnosis"
with 4 bytes (see above), at which point the 4th byte contains the error number and the preceding
3 bytes (0x81, 0x00, 0x00) can be ignored.

15.4 Data exchange

After the Master, in the diagnostic, detects that the Slave is ready for data exchange, it sends
data exchange telegrams. Either the Master stores the data in the input/output direction in the
address area specified during project planning or the control program must fetch or retrieve the
data using specific function blocks.

Deutschmann Automation GmbH & Co. KG Servicing
16 Servicing
Should questions arise that are not covered in this manual you can find further information in our
• FAQ/Wiki area on our homepage www.deutschmann.com or directly in our Wiki on

www.wiki.deutschmann.de
If your questions are still unanswered please contact us directly.
Please note down the following information before calling:

• Device designation
• Serial number (S/N)
• Article number
• Error number and error description
Your request will be recorded in the Support center and will be processed by our Support Team
as quickly as possible (Usually in 1 working day, rarely more than 3 working days.). 

Technical Support hours are as follows:
Monday to Thursday from 8 am to midday and from 1 pm to 4 pm, Friday from 8 am to midday
(CET).

Carl-Zeiss-Straße 8
D-65520 Bad-Camberg
Germany
Central office and sales department +49 6434 9433-0

Technical Support +49 6434 9433-33
Fax sales department +49 6434 9433-40

Fax Technical Support +49 6434 9433-44
E-mail Technical Support support@deutschmann.de
16.1 Returning a device

If you return a device, we require as comprehensive a fault/error description as possible. We
require the following information in particular:
• What error number was displayed?

• What is the supply voltage (±0.5 V) with Gateway connected?
• What were you last doing or what last happened on the device (programming, error on power-
up, ...)?
The more precise information a fault/error description you provide, the more exactly we will be
able to pinpoint the possible causes.
16.2 Downloading PC software

You can download current information and software free of charge from our Internet server.
http://www.deutschmann.com

Servicing Deutschmann Automation GmbH & Co. KG



Servicing Deutschmann Automation GmbH & Co. KG

Instruction Manual Universal Fieldbus-Gateway Unigate Ic - Profibus

Uploaded by

Document Informationclick to expand document informationIC

Document Informationclick to expand document information

Copyright:

Available Formats

Instruction Manual Universal Fieldbus-Gateway Unigate Ic - Profibus

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Instruction Manual Universal Fieldbus-Gateway Unigate Ic - Profibus

Uploaded by

Copyright:

Available Formats

Instruction Manual

Deutschmann Automation GmbH & Co. KG

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 3

5 Synchronous serial interface . . . . . . . . . . . . . . . . . . . 24

4 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

11.5 Operation mode of the IC . . . . . . . . . . . . . . . . . . . . . . . . 38

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 5

6 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 6

7 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

Through the flexible firmware of UNIGATE® IC no software-changes are required on the

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 8

2.4 The serial standard interface

2.5 The synchronous interface

2.6 The Debug-interface

9 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

2.7 UNIGATE® IC hardware survey

UART 1 UART 2 SYN.SERIAL

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 10

In the layout boreholes for ALL 32 pins have to be planned.

11 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

31 OUTLogic TE transmit enable

5V ± 5%, < 250mA VIL VIH

3.2.1 -Boot enable

3.2.2 Load out (SPI-Master: SS0-)

3.2.3 Data out (SPI-Master: SS1-)

3.2.4 Data In (SPI: MISO)

3.2.5 Load In (SPI: MOSI)

3.2.6 Clock (SPI: SCK)

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 12

3.2.9 -Config Mode

3.2.10 DbgTX, DbgRx

3.4 Basic line of proceeding

13 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

3.5 Connection examples

Version 1: Use as a pure link module for the bus

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 14

Version 2: Use of UNIGATE® IC for digital or analog I/O-modules

Out N-M Out 1-8

15 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

Version 3: Example for digital I/Os

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16

3.6 Layout examples

The connection of the two PROFIBUS-lines (PB+ and PB-) are to be

17 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

The 74HCT595 used in this example has an undefined on-position, but

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 18

19 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18

3.7 Operation with external PROFIBUS-driver

Note: Only in connection with IC-version “without 485 (PROFIBUS) - driver“.

3.8 Termination (PROFIBUS)

3.9 Handling (mounting the UNIGATE® IC on the carrier board)

16.5.18 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 20

3.10 Differences between the various versions

3.10.2 Version "without 485 (PROFIBUS)-driver"

3.10.3 Version "LWL"

21 Instruction manual UNIGATE® IC - PROFIBUS DP V. 5.1 16.5.18