DEUTSCHMANN AUTOMATION UNIGATE MB - MPI User manual

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

Manual Art.-No.: V4046E

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 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®MB 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 RS-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 RS-interfaces at the UNIGATE®MB . . . . . . . . . . . . . . . . . . . 15
5.2 Buffer sizes at the UNIGATE®MB . . . . . . . . . . . . . . . . . . . . 15
5.3 Framing Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6 SSI-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1 Initiation of the SSI-interface . . . . . . . . . . . . . . . . . . . . . . . 16
6.1.1 Parameter sample frequency (Clock stretch) . . . . . . . . . . . . . . . . . . 16
6.1.2 Parameter Encoder monitoring (Check Encoder) . . . . . . . . . . . . . . . . 16
6.2 Hardware-wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7 Mode of operation of the system . . . . . . . . . . . . . . . . . . . 18
7.1 General explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.3 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.4 Possible data lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.5 Startup phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8 Implemented protocols in UNIGATE®MB . . . . . . . . . . . . . . . 19
8.1 Protocol: Transparent . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2 Protocol: Universal 232 . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.2 Fieldbus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.3 RS232 parameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.3.1 Start character (232 Start character) . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.3.2 Length 232 (232 Length) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.3.3 Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.3.4 End character (232 End character) . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2.4 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.3 Protocol: 3964(R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Deutschmann Automation GmbH & Co. KG
4 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
8.3.1 Data structure 3964R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.3.2 Protocol definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.3.3 Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.3.3.1 Initiation of data communication by the low-priority user . . . . . . . . . . . . . . . 21
8.3.3.2 Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.3.3.3 Timeout times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.3.3.4 Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.3.3.5 Initiation of data communication by the high-priority user . . . . . . . . . . . . . . . 22
8.3.4 Protocol type 3964 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.4 Protocol: MODBUS-RTU . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.4.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
8.4.2 UNIGATE®as MODBUS-Master . . . . . . . . . . . . . . . . . . . . . . . . 22
8.4.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.4.2.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4.2.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4.3 UNIGATE®as MODBUS-Slave . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4.3.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.4.3.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.4.4 UNIGATE®as Modbus-ASCII Master . . . . . . . . . . . . . . . . . . . . . . 24
8.5 Protocol SSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.6 The trigger byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.7 The length byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.8 Protocol „Universal Modbus RTU Slave“ . . . . . . . . . . . . . . . . . 25
8.8.1 Data structure on the fieldbus side e.g.: PROFIBUS . . . . . . . . . . . . . .26
8.8.1.1 Example: FC1 + FC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.8.1.2 Example: FC3 (Read Holding Register) + FC4 (Read Input Register) . . . . . . . . 27
8.8.1.3 Example: Write Single Coil FC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.8.1.4 Example: Write Single Register FC6 . . . . . . . . . . . . . . . . . . . . . . . . . 29
8.8.1.5 Example: Force multiple coils FC 15 . . . . . . . . . . . . . . . . . . . . . . . . . 30
8.8.1.6 Example: Preset multiple register FC16 . . . . . . . . . . . . . . . . . . . . . . . . 30
8.9 Protocol „Universal Modbus RTU Master“ . . . . . . . . . . . . . . . . 31
8.9.1 Data structure Fieldbus side (e.g. PROFIBUS): . . . . . . . . . . . . . . . . . 31
8.9.2 Data structure Application side: . . . . . . . . . . . . . . . . . . . . . . . . .31
8.9.3 Configuration: via Wingate since wcf Datei Version 396 . . . . . . . . . . . . .32
8.9.3.1 Example: Read coil status FC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8.9.3.2 Example: Read input status FC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.9.3.3 Example: Read multiple register FC3 . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.9.3.4 Example: Read input registers FC4 . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.9.3.5 Example: Force single coil FC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.9.3.6 Example: Preset single register FC6 . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.9.3.7 Example: Force multiple coils FC15 . . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.9.3.8 Example: Preset multiple register FC16 . . . . . . . . . . . . . . . . . . . . . . . . 38
8.10 Protocol „Universal Modbus ASCII Master/Slave“ . . . . . . . . . . . . 39
8.10.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.10.1.1 Example Configuration 1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.10.1.2 Swap Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.10.1.3 Example with Fast Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 5
Deutschmann Automation GmbH & Co. KG
9 Hardware ports, switches and LEDs . . . . . . . . . . . . . . . . . . 45
9.1 Device labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . . 45
9.2.2 Connector supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.2.3 MPI-bus-connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.2.4 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.3 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.3.1 LED "(Bus) Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.3.2 LED "Bus" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.3.3 LED "(Bus) State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.3.4 LED "Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.3.5 LED "State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.3.6 LEDs 1 / 2 / 4 / 8 (Error No. / Select ID) . . . . . . . . . . . . . . . . . . . . 47
9.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.4.1 Termination Rx 422 + Tx 422 (serial interface) . . . . . . . . . . . . . . . . . 47
9.4.2 Rotary coding switches S4 + S5 (serial interface) . . . . . . . . . . . . . . . 48
9.4.3 Termination (MPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.4.4 Rotary coding switches High + Low (MPI-bus-ID) . . . . . . . . . . . . . . . 48
10 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
10.1 Error handling at UNIGATE®MB . . . . . . . . . . . . . . . . . . . . . 49
11 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.1.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.2.1.2 Equipotential bonding connection. . . . . . . . . . . . . . . . . . . . . . . . . . . 52
11.2.2 MPI-bus communication interface . . . . . . . . . . . . . . . . . . . . . . . 52
11.2.2.1 Bus line with copper cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
11.2.3 Line routing, shield and measures to combat interference voltage . . . . . . . 52
11.2.4 General information on line routing . . . . . . . . . . . . . . . . . . . . . . . 52
11.2.4.1 Shielding of lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
12 Representation of the data in a S7 . . . . . . . . . . . . . . . . . . . 54
12.1 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
13 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
13.1.1 Interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
14 Commissioning guide . . . . . . . . . . . . . . . . . . . . . . . . . 57
14.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
14.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
14.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
14.4 Dimensional drawing UNIGATE®MB - MPI . . . . . . . . . . . . . . . . 57
14.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
14.6 Setting the MPI-address . . . . . . . . . . . . . . . . . . . . . . . . . 58

Deutschmann Automation GmbH & Co. KG
6 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
14.7 MPI-bus-connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
14.8 Connection to the process device . . . . . . . . . . . . . . . . . . . . . 58
14.9 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 58
14.10 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
14.11 Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
15 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
15.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
15.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . . 59
16 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
16.1 Explanations of the abbreviations . . . . . . . . . . . . . . . . . . . . . 60
16.2 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 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 – 2021. All rights reserved.
This document may not be passed on nor duplicated, nor may its contents be used or disclosed
unless expressly permitted. Violations of this clause will necessarily lead to compensation in
damages. All rights reserved, in particular rights of granting of patents or registration of
utility-model patents.

Information on CE marking of the module Deutschmann Automation GmbH & Co. KG
8 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
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 therequirements 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.

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 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®MB - MPI V. 1.9 27.10.21
3 Introduction
The module UNIGATE®MB-MPI serves to adapt a serial port to the Siemens MPI-bus. In this
application, it functions as a Gateway and operates as MPI master or slave, optionally adjustable
via Script. It is in the position to communicate with any MPI-device (e. g. S7-300).
The module MB-MPI essentially consists of the following hardware components:
•Electrically isolated RS485 interface to the MPI-bus
•ASIC "MPI 12x"
•Microprocessor 89C51RD2
•RAM and EPROM
•Serial interface (RS232, RS485 and RS422) to the device connected externally

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 11
Deutschmann Automation GmbH & Co. KG Introduction
3.1 UNIGATE®MB software flow-chart

Introduction Deutschmann Automation GmbH & Co. KG
12 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
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.

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 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-MPI-CL-MB (232/422/485) PV3.2[40] (c)dA[40MHz] Switch=0x01FF
Script(C:11634/16128,V:8142/8192)="Universalscript Deutschmann" Author="G/S" 
Version="V 1.3" Date=06.08.2014 SN=47110001“.
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.
In the test mode the following default is valid on the Fieldbus side:
MPI Partner Addr = 2
MPI Write Type = 0x44; // DB
MPI Write Type-No = 1; // DB 1
MPI Write Address = 0; // DW 0
MPI Read Type = 0x44; // DB
MPI Read Type-No = 1; // DB 1
MPI Read Address = 0; // DW 0
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.

Operation modes of the Gateway Deutschmann Automation GmbH & Co. KG
14 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
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.

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 15
Deutschmann Automation GmbH & Co. KG RS-interface
5 RS-interface
5.1 RS-interfaces at the UNIGATE®MB
The UNIGATE®MB - MPI has the interfaces RS232, RS422 and RS485 available.
5.2 Buffer sizes at the UNIGATE®MB
UNIGATE®MB features at the serial side a buffer with the size of 1024 bytes for input data and
output data each.
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 fixed setting for the "Stop Bit Framing Check" is "enabled".

SSI-interface Deutschmann Automation GmbH & Co. KG
16 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
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 configuration of the SSI-interface is executed in the config mode with the WINGATE soft-
ware, Protocol SSI. The encoder type and the sampling frequency are defined via the parameter
"Resolution" (1 bit..15 bit, 24 bit...25 bit), "SSI Encoder Type" (Binary or Gray code) and "Clock
stretch".
6.1.1 Parameter sample frequency (Clock stretch)
You can change the sampling frequency. For this purpose a "Stretch value" is passed that inserts
a waiting period after each clock edge.
If a 0 is passed, there is no waiting time.
Thus the following SSI sample frequencies may vary slightly:

Waiting time = 0 →SSI-Clock ~ 333kHz (No Stretch)
Waiting time = 1 →SSI-Clock ~ 185kHz
Waiting time = 2 →SSI-Clock ~ 150kHz
Waiting time = 3 →SSI-Clock ~ 125kHz
Waiting time = 4 →SSI-Clock ~ 110kHz
Waiting time = 5 →SSI-Clock ~ 100kHz
Waiting time = 6 →SSI-Clock ~ 88kHz
Waiting time = 7 →SSI-Clock ~ 80kHz
Waiting time = 8 →SSI-Clock ~ 72kHz
Waiting time = 9 →SSI-Clock ~ 67kHz
Waiting time = A →SSI-Clock ~ 62kHz
Waiting time = B →SSI-Clock ~ 58kHz
Waiting time = C →SSI-Clock ~ 54kHz
Waiting time = D →SSI-Clock ~ 50kHz
Waiting time = E →SSI-Clock ~ 48kHz
Waiting time = F →SSI-Clock ~ 45kHz
The bit time from which these frequencies were derived, calculate as follows:
t = 3μs + (2* (+ 0.6µs (n* 0.6µs))), where n corresponds to the "Stretch value" (1.. F).
Without clock extension (n = 0) remains at 3μs →333kHz!
The max. Bit length of 32 bits and the slowest clock this results in a total readout time of
32 * = 22μs ~ 700μs.
6.1.2 Parameter Encoder monitoring (Check Encoder)
An encoder monitoring can be activated via the parameter "Check encoder", as long as the used
SSI-encoder supports this function. After the last read encoder bit it is verified if the data line is
still at Low for at least one bit. If the UNIGATE®does NOT detect this bit on Low, error 12 is
issued. For example it can detect a cable break or a not connected encoder. However, it can also
be a misconfigured bit length, or a too slow read out clock.

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 17
Deutschmann Automation GmbH & Co. KG SSI-interface
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®MB.
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-

Mode of operation of the system Deutschmann Automation GmbH & Co. KG
18 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
7 Mode of operation of the system
7.1 General explanation
Communication can be split into seven layers, Layer 1 to Layer 7, in accordance with the
ISO/OSI model.
The Deutschmann Automation Gateways convert Layers 1 and 2 of the customized bus system
(RS485 / RS232 / RS422) to the corresponding Fieldbus system. Layers 3 to 6 are blank, and
Layer 7 is converted in accordance with chapter 7.3.
The Gateway can be configured via the software WINGATE.
7.2 Interfaces
The Gateway features the RS232-, RS422- and RS485-interfaces. The switching of the inter-
faces is done via the configuration (Parameter 232 Interface).
7.3 Data exchange
All data is transferred by the Gateway in dependence of the configuration.
7.4 Possible data lengths
The table below shows the maximum transferable Fieldbus data:
Reading 255 bytes Maximum data length
Writing 255 bytes Maximum data length
Supported are:
Reading- and writing-accesses on DB, markers, inputs and outputs as well as passive accesses
on markers and DB.
7.5 Startup phase
In the run-up phase the Gateway programs and configures itself with the partner station at the
bus. Data exchange with the external device does not occur until after the run-up phase has
been completed with no errors.

27.10.21 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 19
Deutschmann Automation GmbH & Co. KG Implemented protocols in UNIGATE® MB
8 Implemented protocols in UNIGATE®MB
UNIGATE®MB is supplied with the Script “Universal Script Deutschmann“. The configuration of
the protocols is carried out in the configuration mode (see Chapter 4.1) with the software WING-
ATE. See "Instructions UNIGATE®CL - Configuration with WINGATE". The PDF can also be
found on our website under Support/Downloads/Manuals.
Attention: If a Reset Device is carried out it is possible (depending on the
firmware version of the UNIGATE) that the "Universal Script" will get lost
and must be played in again.
If you no longer have the compiled script, a corresponding request must
be sent to Deutschmann Support.
https://www.deutschmann.de/en/support/enquiry/
8.1 Protocol: Transparent
The data is transferred bidirectional from the UNIGATE®.
8.1.1 Data structure
On the RS-entry side the timeout time of 2 ms is firmly set. If no more data is received within the
timeout period, then the data that has been received so far is transferred to the bus.
If less data is received through Rx then configured by the device description file (I/O-length), then
the rest is complemented with ZERO.
Too much data received will be cut off.
Depending on the fieldbus, the required length of the input and output data (I / O length) can be
set via the device configuration of the UNIGATE or via the device description file in the hig-
her-level controller.
8.2 Protocol: Universal 232
The protocol designation "Universal 232" and the relation to the
"RS232-interface" in the description have eveloped over the years. The
protocol also works with RS422 and RS485 though!

Implemented protocols in UNIGATE® MB Deutschmann Automation GmbH & Co. KG
20 UNIGATE®fieldbus gateway UNIGATE®MB - MPI V. 1.9 27.10.21
8.2.1 Data structure
8.2.2 Fieldbus parameters
Trigger byte: See „The trigger byte“, chapter 8.6
Length byte: See „The length byte“, chapter 8.7
8.2.3 RS232 parameter table
8.2.3.1 Start character (232 Start character)
If this character is defined, the gateway evaluates only the data at the RS232 interface following
this start character. Each transmission from the gateway via the RS232 interface is initiated with
the start character in this case.
8.2.3.2 Length 232 (232 Length)
If this byte is activated, the gateway, at the receive end, awaits as many bytes of useful data as
specified in this byte by the RS232 transmitter. At the transmission end, the gateway then sets
this byte to the number of useful data items transmitted by it. If byte "Length232" is not defined,
the gateway, on reception at the RS232 interface, waits for the end criterion if this is defined. If no
end criterion is defined either, as many characters as can be transferred in the fieldbus transmit
buffer are read in via the RS232 interface.
As a special case for this parameter also a length byte with additional Timeout monitoring can be
set in WINGATE. In that case the received characters will be discarded at a Timeout.
Attention:
If "Timeout“ is selected as end character, then this byte has no significance.
8.2.3.3 Timeout
If the end character is set to "FF", the value that was set in the RX_Timeout parameter is acti-
vated and the time entered there is waited for with serial reception, or triggered for new charac-
ters. If the set time is exceeded without an event, the end criterion is reached and the characters
are copied onto the bus.
8.2.3.4 End character (232 End character)
If this character is defined, the gateway receives data from the RS232 interface up to this charac-
ter. The "Timeout" criterion can be defined as a special case. In this case, the gateway continues
to receive characters until a defined pause occurs. In the special case "Timeout" the "Length
232-byte" has no significance. At the transmit end, the gateway inserts the end character, if
defined, as the last character of a transmission.