DEUTSCHMANN AUTOMATION UNIGATE CL-LONWorks Series User manual

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

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.4 3
Deutschmann Automation GmbH & Co. KG
1Information 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
2Information for the machine manufacturers. . . . . . . . . . . . . . . 9
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 EU Machinery Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1 Difference in the hardware version . . . . . . . . . . . . . . . . . . . . 10
3.2 UNIGATE CL software flow-chart . . . . . . . . . . . . . . . . . . . . . 11
3.3 UNIGATE block diagram . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.4 UNIGATE application diagram . . . . . . . . . . . . . . . . . . . . . . 12
4Operation modes of the Gateway. . . . . . . . . . . . . . . . . . . . 13
4.1 Configuration mode (config mode) . . . . . . . . . . . . . . . . . . . . 13
4.2 Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3 Data exchange mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5RS-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 RS-interfaces at the UNIGATE CL . . . . . . . . . . . . . . . . . . . . 15
5.2 Buffer sizes at the UNIGATE CL . . . . . . . . . . . . . . . . . . . . . 15
5.3 Framing Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6SSI-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1 Initiation of the SSI-interface . . . . . . . . . . . . . . . . . . . . . . . 16
6.2 Hardware-wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7The Debug-interface. . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.1 Overview of the Debug-interface . . . . . . . . . . . . . . . . . . . . . 18
7.2 Starting in the Debug-mode . . . . . . . . . . . . . . . . . . . . . . . . 18
7.3 Communication parameter for the Debug-interface . . . . . . . . . . . . 18
7.4 Possibilities with the Debug-interface . . . . . . . . . . . . . . . . . . . 18
7.5 Commands of the Debug-interface . . . . . . . . . . . . . . . . . . . . 18
8Mode of operation of the system . . . . . . . . . . . . . . . . . . . . 19
8.1 General explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.3 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.4 Possible network variables and their data lengths . . . . . . . . . . . . 19
8.5 Run-up phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9Generating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.1 What is a Script? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.2 Memory efficiency of the programs . . . . . . . . . . . . . . . . . . . . 20
9.3 What can you do with a Script device? . . . . . . . . . . . . . . . . . . 20
9.4 Independence of buses . . . . . . . . . . . . . . . . . . . . . . . . . . 20
9.5 Further settings at the Gateway . . . . . . . . . . . . . . . . . . . . . . 20
9.6 The use of the Protocol Developer . . . . . . . . . . . . . . . . . . . . 21
9.7 Accuracies of the baud rates . . . . . . . . . . . . . . . . . . . . . . . 21

Deutschmann Automation GmbH & Co. KG
4 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.4 14.7.10
9.8 Script processing times . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10 Hardware ports, switches and LEDs . . . . . . . . . . . . . . . . . . 23
10.1 Device labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . . .23
10.2.2 Connector supply voltage and DEBUG-interface. . . . . . . . . . . . . . . . .24
10.2.3 LONWorks-connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
10.2.4 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
10.3 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.3.1 LED "Service". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
10.3.2 LED "Rx" (at LONWorks 62 only). . . . . . . . . . . . . . . . . . . . . . . . .25
10.3.3 LED "Tx" (at LONWorks 62 only). . . . . . . . . . . . . . . . . . . . . . . . .25
10.3.4 LED “(Bus) State“. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
10.3.5 LED "Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
10.3.6 LED "State". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
10.3.7 LEDs 1 / 2 / 4 / 8 (Error No. / Select ID) . . . . . . . . . . . . . . . . . . . . .25
10.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.4.1 Termination Rx 422 + Tx 422 (serial interface). . . . . . . . . . . . . . . . . .25
10.4.2 Rotary coding switches S4 + S5 (serial interface) . . . . . . . . . . . . . . . .26
10.4.3 Pushbutton "Service" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
10.5 The Debug cable for UNIGATE CL . . . . . . . . . . . . . . . . . . . . 26
11 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.1 Error handling at UNIGATE CL . . . . . . . . . . . . . . . . . . . . . . 27
12 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
12.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
12.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
12.2.1.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.2.1.2 Equipotential bonding connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
12.2.2 LONWorks communication interface . . . . . . . . . . . . . . . . . . . . . . .29
12.2.2.1 Bus line with copper cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.2.3 Line routing, shield and measures to combat interference voltage. . . . . . . .29
12.2.4 General information on line routing. . . . . . . . . . . . . . . . . . . . . . . .29
12.2.4.1 Shielding of lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
13 LONWorks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.1 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.2 Network variables (NVTs) . . . . . . . . . . . . . . . . . . . . . . . . . 31
13.2.1 Implementing the network variables into the UNIGATE-LONWorks . . . . . . .32
13.2.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
13.2.3 Technical data (characteristics) for LONWorks. . . . . . . . . . . . . . . . . .32
13.3 Script examples for the initialization of LONWorks . . . . . . . . . . . . 33
13.4 LON-specific parameters . . . . . . . . . . . . . . . . . . . . . . . . . 34
13.5 Darstellung der Daten in LONWorks . . . . . . . . . . . . . . . . . . . 34
13.5.1 Network variables (NVTs) . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.4 5
Deutschmann Automation GmbH & Co. KG
13.5.2 Determination of a LON-Gateway’s update time . . . . . . . . . . . . . . . . 35
14 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
14.1.1 Interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
15 Commissioning guide. . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.4 Dimensional drawing UNIGATE CL - LONWorks . . . . . . . . . . . . . 38
15.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.6 LONWorks connection . . . . . . . . . . . . . . . . . . . . . . . . . . 38
15.7 Connection to the process device . . . . . . . . . . . . . . . . . . . . . 39
15.8 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 39
15.9 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
15.10 Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
15.11 Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
16 Servicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
16.1 Returning a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
16.2 Downloading PC software . . . . . . . . . . . . . . . . . . . . . . . . . 40
17 Annex. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
17.1 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
18 Declaration of conformity. . . . . . . . . . . . . . . . . . . . . . . . 42
18.1 EC declaration of conformity . . . . . . . . . . . . . . . . . . . . . . . 42

Deutschmann Automation GmbH & Co. KG
6 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.4 14.7.10

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 7
Deutschmann Automation GmbH & Co. KG
Disclaimer of liability
We have checked the contents of the document for conformity with the hardware and software
described. Nevertheless, we are unable to preclude the possibility of deviations so that we are
unable to assume warranty for full compliance. The information given in the publication is,
however, reviewed regularly. Necessary amendments are incorporated in the following editions.
We would be pleased to receive any improvement proposals which you may have.
Copyright
Copyright (C) Deutschmann Automation GmbH & Co. KG 1997 – 2010. All rights reserved.
This document may not be passed on nor duplicated, nor may its contents be used or disclosed
unless expressly permitted. Violations of this clause will necessarily lead to compensation in
damages. All rights reserved, in particular rights of granting of patents or registration of
utility-model patents.
Art.-No.: V3652E

Information on CE marking of the module Deutschmann Automation GmbH & Co. KG
8 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 14.7.10
1 Information on CE marking of the module
1.1 EU Directive EMC
The following applies to the module described in this User Manual:
Products which bear the CE mark comply with the requirements of EU Directive „Electromagnetic
Compatibility“ and the harmonized European Standards (EN) listed therein.
The EU Declarations of Conformity are available at the following location for perusal by the
responsible authorities in accordance with the EU Directive, Article 10:
Deutschmann Automation GmbH & Co. KG, Carl-Zeiss-Straße 8, 65520 Bad Camberg, Ger-
many.
1.2 Scope of application
1.3 Note installation guidelines
The module complies with the requirements if you
1. comply with the installation guidelines described in the User Manual when installing and oper-
ating the module.
2. also follow the rules below on installation of the equipment and on working on switch cabinets.
1.4 Installation of the unit
Modules must be installed in electrical equipment rooms/areas or in enclosed housings (e.g.
switch boxes made of metal or plastic). Moreover, you must earth the unit and the switch box
(metal box) or at least the top-hat rail (plastic box) onto which the module has been snapped.
1.5 Working on switch cabinets
In order to protect the modules against static electrical discharge, the personnel must discharge
themselves electrostatically before opening switch cabinets or switch boxes.
The modules are designed for use in the industrial sector and comply with the following
requirements.
Scope of application Requirement applicable to
Emitted interference Interference immunity
Industry EN 55011, cl. A (2007) EN 61000-6-2 (2005)

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 9
Deutschmann Automation GmbH & Co. KG Information for the machine manufacturers
2 Information for the machine manufacturers
2.1 Introduction
The UNIGATE module does not constitute a machine as defined by the EU "Machinery“
Directive. Consequently, the module does not have a Declaration of Conformity in relation to the
EU Machinery Directive.
2.2 EU Machinery Directive
The EU Machinery Directive stipulates the requirements applicable to a machine. The term
"machine" is taken to mean a totality of connected parts or fixtures (see also EN 292-1, Para-
graph 3.1)
The module is a part of the electrical equipment of the machine and must thus be included by the
machine manufacturer in the Declaration of Conformity process.

Introduction Deutschmann Automation GmbH & Co. KG
10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 14.7.10
3 Introduction
The module UNIGATE CL-LONWorks 62 or CL-LONWorks 512 serves to adapt a serial port to
the LON-bus. In this application, it functions as Gateway. It can be operated at any LON-bus with
FTT-10A.
The module CL-LONWorks essentially consists of the following hardware components:
•FTT-10A interface
•LONWorks ECHOLON ASIC
•Microprocessor T89 C51RD2
•RAM and EPROM
•Optionally electrically isolated RS-interface
•Serial interface (RS232, RS485 and RS422) to the device connected externally
3.1 Difference in the hardware version
LONworks 512 up to 256 input SNVTs and 256 output SNVTs
LONWorks 62 up to 62 SNVTs, input and output distributed in a variable way

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 11
Deutschmann Automation GmbH & Co. KG Introduction
3.2 UNIGATE CL software flow-chart

Introduction Deutschmann Automation GmbH & Co. KG
12 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 14.7.10
3.3 UNIGATE block diagram
The following picture shows a typical UNIGATE-module design.
3.4 UNIGATE application diagram
The following graph shows a typical connection scheme.

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 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
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-LN(62)-CL (232/422/485) V2.0 [30] (c)dA Switch=0xFF Script(8k)="Leer" Author="Deutsch-
mann Automation GmbH" Version="1.0" Date=21.08.2001 SN=47110001 Neuron-ID=04 36 EB
13 02 00“.
In the configuration mode the Gateway always operates with the settings 9600 Bauds, no Parity,
8 databits and 1 stopbit, the RS-State LED will always be flashing red, the "Error No/Select ID"
LEDs are of no account for the user. All software revisions contain the configuration mode.
4.2 Test mode
Setting of the test mode
The test mode is set by bringing the switches S4 and S5 in position "E". All other switches will not
be taken into consideration for the setting of the test mode. Now the Gateway has to be restarted
with these settings (by a short disconnection from the power supply).
In the test mode the Gateway always operates with the settings 9600 baud, no parity, 8 databits
and 1 stopbit.
The test mode may be helpful to integrate the Gateway in the relevant environment, for instance
to test the parameters of the RS-interfaces.
Mode of operation of the test mode
After the restart in the test mode the Gateway will be sending the values 0-15 in hexadecimal
representation ("0".."F") in ASCII-coding on the serial side every second. Simultaneously the
same values are issued binary on the fieldbus-interface.
In this mode the State-LED on the RS-side will be flashing red, the "Error No/Select ID" LEDs will
be displaying the value in a binary way, that is issued that moment. Additionally each character
that is received at one of the interfaces will also be output at the same interface as a local echo.
On the fieldbus-side only the first byte will be used for the local echo, that means on receiving as
well as on transmitting only the first byte of the bus data is looked at, the other bus data do not
change compared to the last data.
Attention:
In the testmode the Gateway UNIGATE-LONWorks 62 automatically generates a
variable In and Out of the type SNVT_count. The Out-variable is incremented by
one every second.
The program ID is changed to “TM004711“.
„Testmode“ stands in the selfdocstring.
Existing bindings are deleted!

Operation modes of the Gateway Deutschmann Automation GmbH & Co. KG
14 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 14.7.10
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.

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

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

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

The Debug-interface Deutschmann Automation GmbH & Co. KG
18 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 14.7.10
7 The Debug-interface
7.1 Overview of the Debug-interface
The UNIGATE® IC features a Debug-interface, that allows a step-by-step processing of a Script.
Normally this interface is only required for the development of a Script.
7.2 Starting in the Debug-mode
When applying power to the UNIGATE® (power up) the firmware will output the binary character
0 (0x00) after a self-test was carried out on this interface. If the UNIGATE® receives an
acknowledgement via this interface within 500 ms, it is in the Debug-mode. The
acknowledgement is the ASCII-character O (0x4F).
With the start in the Debug-mode the further execution of Script commands will be put to a stop.
7.3 Communication parameter for the Debug-interface
The Debug-interface is always operating with 9600 baud, no parity, 8 data bit, 1 stop bit. It is not
possible to change this parameter in the Protocol Developer. Please consider the fact that these
settings have to be in accordance with those of the PC-COM-interface and that the flow control
(protocol) has to be set on „none“ there.
7.4 Possibilities with the Debug-interface
Usually the Protocol Developer is connected to the Debug-interface. With it a step-by-step pro-
cessing of a Script, monitoring jumps and decisions and looking at memory areas is possible.
Moreover breakpoints can be set. It basically possesses all characteristics a software-develop-
ment tool is typically supposed to have. However, it is also possible to carry out a Scrip-update
via this interface.
From Script version [27] on you can also output data with the Script command
"SerialOutputToDebugInterface". Please also pay attention to the remark in the manual ’Protocol
Developer’.
7.5 Commands of the Debug-interface
The commands for the use of the Debug-interface are described in the instruction manual Proto-
col Developer.

14.7.10 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 19
Deutschmann Automation GmbH & Co. KG Mode of operation of the system
8 Mode of operation of the system
8.1 General explanation
Communication can be split into seven layers, layer 1 to layer 7, in accordance with the
ISO/OSI-model.
The DEUTSCHMANN AUTOMATION LONWorks-Gateways convert all layers in accordance
with the LONTalk-protocol. Layer 7 is realized according to chapter 8.3.
8.2 Interfaces
The Gateway features the interfaces RS232, RS485 and RS422.
8.3 Data exchange
The UNIGATE has to be connected to the LON-bus through a projecting tool. In the Gateway the
data received from the bus is transferred to the externall device depending on the loaded Script.
The external device responds in accordance with the protocol conventions.
The data received from the external device is written by the Gateway into the internal RAM to the
fixed network variable.
All data is transferred consistently by the Gateway in both directions. The maximum data length
of consistent data must be considered in the case of data exchange between the participants.
8.4 Possible network variables and their data lengths
At present the UNIGATE supports all network variables from the SNVT master list of May
2002.
Aliases
8.5 Run-up phase
The Gateway is programmed and configured in the run-up phase. Data exchange with the exter-
nal device does not occur until after the run-up phase has been completed with no errors.
UNIGATE Maximum amount of SNVTs Total byte Input Output Input Output
LONWorks 512 256 256 512 512
LONWorks 62 62 altogether 512 512
UNIGATE Amount of alias table entries
LONWorks 512 62
LONWorks 62 62

Generating a Script Deutschmann Automation GmbH & Co. KG
20 UNIGATE fieldbus gateway UNIGATE CL - LONWorks V. 1.5 14.7.10
9 Generating a Script
9.1 What is a Script?
A Script is a sequence of commands, that are executed in that exact order. Because of the fact
that also mechanisms are given that control the program flow in the Script it is also possible to
assemble more complex processes from these simple commands.
The Script is memory-oriented. It means that all variables always refer to one memory area.
While developing a Script you do not have to take care of the memory management though. The
Protocol Developer takes on this responsibility for you.
9.2 Memory efficiency of the programs
A Script command can carry out e. g. a complex checksum like a CRC-16 calculation via data.
For the coding of this command only 9 byte are required as memory space (for the command
itself). This is only possible when these complex commands are contained in a library.
A further advantage of this library is, that the underlying functions have been in practical use for a
couple of years and therefore can be described as ’void of errors’. As these commands are also
present in the native code for the controller, at this point also the runtime performance of the
Script is favorable.
9.3 What can you do with a Script device?
Our Script devices are in the position to process a lot of commands. In this case a command is
always a small firmly outlined task. All commands can be put into classes or groups. A group of
commands deals with the communication in general. This group’s commands enable the Gate-
way to send and receive data on the serial side as well as on the bus-side.
9.4 Independence of buses
Basically the Scripts do not depend on the bus, they are supposed to operate on. It means that a
Script which was developed on a Profibus Gateway can also be operated on an Interbus without
changes, since the functioning of these buses is very similar. In order to also process this Script
on an Ethernet Gateway, perhaps further adjustments have to be made in the Script, so that the
Script can be executed reasonably.
There are no fixed rules how which Scripts have to operate properly. When writing a Script you
should take into account on which target hardware the Script is to be executed, so the necessary
settings for the respective buses can be made.
9.5 Further settings at the Gateway
Most devices require no further adjustments, except for those made in the Script itself. However,
there are also exceptions to it. These settings are made by means of the software WINGATE. If
you know our UNIGATE-series, you are already familiar with the proceeding with it. An example
is the adjustment of the IP-address and the net-mask of an Ethernet-Gateway. These values
have to be known as fixed values and are not available for the runtime. Another reason for the
configuration of the values in WINGATE is the following: After an update of the Script these val-
ues remain untouched, i. e. the settings that were made once are still available after a change of
the Script.
Only this way it is also possible that the same Script operates on different Ethernet-Gateways,
that feature different IP-addresses.