Process Gateway

© 2010 Ing. Punzenberger COPA-DATA GmbH
All rights reserved.
Distribution and/or reproduction of this document or parts thereof in any form are permitted solely with
the written permission of the company COPA-DATA. The technical data contained herein has been
provided solely for informational purposes and is not legally binding. Subject to change, technical or
otherwise.
1. Welcome to COPA-DATA help ...................................................................................................... 1
2. Process Gateway ............................................................................................................................. 2
3. General ............................................................................................................................................ 3
4. Requirements.................................................................................................................................. 4
5. Installation ...................................................................................................................................... 5
6. Configuration Process Gateway .................................................................................................... 7
6.1
Project configuration.................................................................................................................... 7
6.2
Module configuration................................................................................................................... 7
6.3
Security configuration.................................................................................................................. 7
7. DEC configuration .......................................................................................................................... 8
7.1
Module configuration................................................................................................................... 8
7.2
Logging ......................................................................................................................................... 9
7.3
Configuration file: specific entries for AccessDEC ....................................................................... 9
8. DNP3 slave configuration ............................................................................................................ 11
8.1
Module configuration................................................................................................................. 11
8.2
Logging ....................................................................................................................................... 12
8.3
Configuration file: specific entries for Access DNP3 ................................................................. 13
9. IEC870 slave configuration .......................................................................................................... 14
9.1
Module configuration................................................................................................................. 14
9.1.1
870-101 ......................................................................................................................... 15
9.1.2
870-104 ......................................................................................................................... 17
9.1.3
Device ........................................................................................................................... 19
9.1.4
Sector ............................................................................................................................ 21
9.1.5
104 settings ................................................................................................................... 30
9.1.6
XML-File ....................................................................................................................... 31
iii
9.2
Communication .......................................................................................................................... 35
9.2.1
Startup .......................................................................................................................... 36
9.2.2
General interrogation .................................................................................................... 37
9.2.3
Reset ............................................................................................................................. 37
9.2.4
Value changes ............................................................................................................... 38
9.2.5
Priority .......................................................................................................................... 38
9.2.6
Read .............................................................................................................................. 38
9.2.7
Process initialized.......................................................................................................... 39
9.2.8
File transfer ................................................................................................................... 39
9.2.9
Sequence of Events (SOE) ............................................................................................ 40
9.2.10 Time synchronization ................................................................................................... 43
9.2.11 DPI / DCS mapping ....................................................................................................... 44
9.2.12 Select before operate .................................................................................................... 45
9.2.13 INVALID bit handling ................................................................................................... 45
9.2.14 Monitoring command ................................................................................................... 45
9.2.15 Internal type T00 (status variables) ............................................................................. 46
9.2.16 Pulse generation ........................................................................................................... 47
9.2.17 Reload ........................................................................................................................... 48
9.2.18 Broadcasts ..................................................................................................................... 48
9.2.19 Realtime invalid - Statusbit T_INVAL .......................................................................... 49
9.2.20 Logging.......................................................................................................................... 49
9.2.21 Error codes .................................................................................................................... 53
9.3
Interoperability .......................................................................................................................... 53
10. MODBUS Slave configuration ..................................................................................................... 74
10.1 Module configuration................................................................................................................. 74
10.2 Hardware address of the MODBUS system ............................................................................... 75
10.3 Configuration file: specific entries for AccessMODBUS ............................................................ 75
11. SNMP agent configuration .......................................................................................................... 77
11.1 SNMP architecture ..................................................................................................................... 77
11.2 Management Information Base (MIB) ....................................................................................... 78
11.3 MIB structure ............................................................................................................................. 78
11.4 Module configuration................................................................................................................. 80
11.5 Configuration file: specific entries for Access SNMP ................................................................ 81
iv
11.6 Configuration of the Windows SNMP agent ............................................................................. 82
12. SQL configuration ........................................................................................................................ 84
12.1 Module configuration................................................................................................................. 84
12.2 Variable selection ....................................................................................................................... 85
12.3 Creating tables ............................................................................................................................ 86
12.4 Operation in a redundant system............................................................................................... 87
12.5 Configuration file: specific entries for AccessSQL ..................................................................... 87
12.6 Table format ............................................................................................................................... 88
12.6.1 Table for process image ................................................................................................ 88
12.6.2 Table for variable IDs .................................................................................................... 88
13. OPC UA server configuration ...................................................................................................... 89
13.1 Module configuration................................................................................................................. 89
13.2 Start ............................................................................................................................................ 91
13.3 Connection ................................................................................................................................. 92
13.4 Security ...................................................................................................................................... 92
13.5 Alarms and states ....................................................................................................................... 92
13.6 Service Sets ................................................................................................................................ 94
v
If you miss any information in this help chapter or have any suggestions for additions, please feel free to
contact us via e-mail: documentation@copadata.com (mailto:documentation@copadata.com).
If you have concrete questions relating to your project, please feel free to contact the support team via
e-mail: support@copadata.com (mailto:support@copadata.com)
If you realize that you need additional licenses or modules, please feel free to contact the sales team via
e-mail: sales@copadata.com (mailto:sales@copadata.com)
1
Info
The Process Gateway serves as a coupling to higher-level systems. Parts of the zenon
process image of other applications can be made available and be updated.
2
It is thought as an add-on to the Runtime of the control system and only works in combination with it.
3
Runtime:On the computer, where the Process Gateway should run, the Runtime with the according
release version and a loaded project according to the configuration has to be started before the add-on.
When the Runtime is closed, the add-on is also terminated automatically.
Info
The Process Gateway uses the COM interface to access zenon data. The COM interface is
used by VBA and is only available if zenon6.ini is present in the file under under [VBA] the
entry EIN=1.
Modules:There are different modules for the Process Gateway, that take over the communication to
external applications. At the moment these modules are:
AccessDEC.dll
Hundamp;S-DEC-System
AccessMODBUS.dll
Modbus master
AccessSQL.dll
SQL databases
AccessDNP3.dll
DNP3 master
AccessIEC870Sl.dll
IEC 60870 master
AccessSNMP.dll
SNMP client
AccessOPCUA.dll
OPC UA client
Attention
When using the Modbus IO driver:
The Process Gateway supports only Write Holding Register Function Code 16.
4
The add-on only consists of a single file (zenProcGateway.exe) which should preferably be copied
to the installation directory of zenon. But generally each directory is possible as installation directory.
The module to be used with the zenProcGateway has to be in the same directory as
zenProcGateway.exe.
The configuration file (zenProcGateway.ini) is in the system folder. In this file, an entry DLL in
the section [GENERAL] has to be set to the name of the module.
zenProcGateway.ini
DEC
[GENERAL]
DLL=AccessDEC.dll
SQL
[GENERAL]
DLL=AccessDEC.dll
MODBUS
[GENERAL]
DLL=AccessMODBUS.dll
DNP3
[GENERAL]
DLL=AccessDNP3.dll
IEC870Sl
[GENERAL]
DLL=AccessIEC870Sl.dll
SNMP:
[GENERAL]
DLL=AccessSNMP.dll
OPCUA
[GENERAL]
DLL=AccessOPCUA.dll
If you want to use a configuration file with a different name (e.g. for operation with multiple instances),
you have to start the zenProcGateway.EXE with the command line parameter /ini:<file> . That file
must be in the system folder, too.
Example
zenProcGateway.EXE /ini:MyConfig.INI
5
If the gateway is started without a valid configuration file or if this file does not contain an entry about
the communication module, you will be offered a selection list with all available communication modules
after the start.
6
If no special project name is defined in the configuration file (zenProcGateway.ini), all
specifications refer to the first project loaded by the Runtime (integration project). Any project in the
hierarchy of a multi project system can be accessed by setting the entry PROJECT in the section
[GENERAL] of the configuration file (zenProcGateway.ini) to the corresponding project name.
The configuration of a single module depends on the type of this module. With the configuration button
the configuration dialog of the module is opened.
The Process Gateway can be executed hidden to protect it from unauthorized access. If the Process
Gateway is started in the command line with the parameter /hide (or -hide), it starts invisible and
cannot be configured or stopped. The Process Gateway closes automatically when zenon is closed.
7
After clicking the configuration button the following dialog opens:
Here the variables that should be connected can be selected. In the list on the left-hand side all variables
which are available in zenon are displayed. There they can be selected and moved to the DEC export list
with the button >. With the button '<' they can be removed again. If a variable is moved to the export
list, a dialog for the name assignment of the zenon variable to the DEC variable opens:
8
The assignment is defined with a four digit press number and the four digit parameter name. Entered
characters are automatically changed to upper case. The variables selected in this way then are
continuously synchronized in zenon or in the connected DEC system.
In the lower part of the configuration dialog the TCP/IP connection to the DEC system can be
configured.
The port number indicates the port where the Process Gateway waits for incoming connections.
The timeout is the time without response, after that the connection is closed.
All telegrams received by the DEC system and the responds from the Process Gateway can be logged.
To do this an entry LOGFILE in the section [DEC] of the configuration file with the name of the log file
has to exist. This file then is created in the same directory as zenProcGateway.exe.
Example for this entry:
[DEC]
LOGFILE=zenProcGateway.log
The configuration file must be in the system folder.
[DEC]
LOGFILE
Name of the log file (if desired, e.g. zenProcGateway.log)
PORT
port number, where the Process Gateway waits for connection attempts
TCPTIMEOUT
timeout interval, after which the connection is closed
9
REFRESHRATE
time interval in milliseconds, in which the process image of zenon is checked on changes.
10
After clicking the configuration button the following dialog opens:
Here the variables that should be connected can be selected. On the left-hand side all variables which
are available in zenon are displayed. You can select them there and move them to the DNP3 export list
with the button >. You can remove them from the export list with the button <.
If a variable is moved to the export list, a dialog for the name assignment of the zenon variable to an
object and point number in DNP3 opens:
11
The variables selected in this way then are available in the DNP3 slave and are continuously
synchronized between zenon and the DNP3’s object database.
In the lower part of the configuration dialog the serial or TCP/IP connection for the DNP3 slave can be
configured.
The following settings are available for the configuration of the serial interface:
COM
the serial interface for the access to the DNP3 slave
Data bit
number of data bits (default: 8)
Stop bit
number of stop bits (default: 1)
Baud rate
baud rate of the serial interface (default: 9600)
Parity
parity setting even/odd/no (default: no)
For the configuration via TCP/IP only the listener-port can be defined; it should be 20000.
For the DNP3 session the local (slave’s) session link address and the remote (master’s) session link
address must be configured. Only one active session is supported. It does not matter if serial or TCP/IP is
used.
All diagnostic information of the DNP3 layer can be logged in a text file.
To enable this an entry LOGFILE in the section [DNP3] of the configuration file with the name of the log
file has to exist. This file then is created in the same directory as zenProcGateway.exe.
Example for this entry:
[DNP3]
LOGFILE=zenProcGateway.log
12
The configuration file must be in the system folder.
[DNP3]
SERIAL
serial communication (1) or communication via TCP/IP (0)
COMPORT
serial interface (COM1 = 0, COM2 = 1,...)
BAUD
baud rate of the serial interface
BYTESIZE
number of data bits of the serial interface
PARITY
Parity settings of the serial interface (0=no, 1=odd, 2=even)
STOPBITS
number of stop bits of the serial interface (0=1, 1=1.5, 2=2)
LINKADDRLOC
local session link address
LINKADDRREM
remote session link address
PORT
TCP/IP port
[VARIABLES]
COUNT
number of variables to be exported
NAME_n
name of variable number n (0<=n<COUNT)
OBJECT_n
DNP3 object type of variable number n (0<=n<COUNT)
POINT_n
DNP3 point number of variable number n (0<=n<COUNT)
13
The driver and its dialogs for configuration are only available in English.
PLCs addressed with the IEC870SI driver, are divided into sectors. These sectors contain IOs (information
objects) representing the actual variables. IOs refer to a variable of the process control system.
You can configure several PLCs with the IEC870SI driver. According to the used protocol, they are
associated directly to a Master or polled by a Master.

870-101: The PLC is identified by a link address.

870-104: The PLC is identified by the IP address of the Master.

Sector: Addressed by COA.

IO: Addressed by type identification and IOA.
In the following chapters, you will read how to configure the IEC870SI driver, how communication takes
place and you will read about compatibility issues.
There are many settings you can change in the IEC870SI driver All lists in the configuration window can
be sorted. To change the sorting sequence, simply click on the column title.
14
The settings for protocols 101 and 104 differ.
In the main window, you can choose the protocol you want to use and define general settings:

'Protocol 870-101' unlocks the settings for protocol 101 and locks all other input fields.

'Protocol 870-104' unlocks the settings for protocol 104 and locks all other input fields.
Under 'Device' and 'Sector', you can define all specific device settings.
9.1.1
870-101
870-101
activates protocol 101, unlocks all input fields for 101 and locks settings for 104.
15
Configuration file
Name of the configuration file. This is where all active settings are stored and also loaded from.
The name you enter must be a valid file name. Otherwise, no data can be stored. In this case,
you will get an error message.
Only enter the file name without path. You do not have to add the file extension XML, as it will
be added automatically during saving. The current INI directory will be used as path.
The file name will automatically be entered in the INI file of the process gateway as
configuration.
You can find the INI file in the system folder of the process control system. It is called
'SCADAProcGateway.ini' - SCADA is the placeholder for the name of the process control
system.
Import
Loads configuration data from an XML configuration file. The current settings are replaced by
the ones stored in the file. The current setting for the 'configuration file' remains the same.
Export
Stores the current settings in a file.
Attention: Device that still have the default ID '????' (defined during creation) will not be
exported. To export them, you must first configure the device in the configuration window
"Device" (on page 19).
Link address size
101
COM port
Length of the “Link address size” data field according to FT1.2 Frame.
Valid input: 1 or 2 octet
This setting must be the same as that of the master.
Number of the serial interface.
Interfaces available: 1 to 64
101
Baud
101
Interface speed.
The character format complies with TF 1.2 (870-5-1 6.2.4.2.1 R6) 8e1.
RTS is active when data is sent.
Slowest baud rate: 110, fastest 256000
Devices
List of configured devices.
101 master
polling timeout
[s]
Shows the time in seconds in which the master must execute a query to the slave. If there is no
query within this time, the connection is ended.
If you enter 0, you deactivate monitoring.
Add
Adds a new device with standard settings. By default, it gets the invalid ID '????' and invalid
IP/link addresses. Before you can use or export the device, you must configure it.
Delete
Deletes the selected device. If no device was selected, this button is locked.
16
OK
Accepts all changed settings. They will immediately be stored in the current configuration file
(as defined in 'Configuration file').
Attention: After clicking on 'OK', all active Master connections will be closed and
restarted with the new settings. There may be communication errors during that.
Cancel
Discards all changed settings. Nothing is stored.
Help
Opens the help window (like the F1 button). If the help file does not exist on your system,
please contact the COPA-DATA support team via <CD_MAMLSUPPORT>
(mailto:support@copadata.com)
9.1.2
870-104
870-104
activates protocol 104, unlocks all input fields for 104 and locks settings for 101.
17
Configuration
file
Name of the configuration file. This is where all active settings are stored and also loaded from.
The name you enter must be a valid file name. Otherwise, no data can be stored. In this case, you
will get an error message.
Only enter the file name without path. You do not have to add the file extension XML, as it will
be added automatically during saving. The current INI directory will be used as path.
The file name will automatically be entered in the INI file of the process gateway as configuration.
You can find the INI file in the system folder of the process control system. It is called
'SCADAProcGateway.ini' - SCADA is the placeholder for the name of the process control system.
Import
Loads configuration data from an XML configuration file. The current settings are replaced by the
ones stored in the file. The current setting for the 'configuration file' remains the same.
Export
Stores the current settings in a file.
Attention: Device that still have the default ID '????' (defined during creation) will not be
exported. To export them, you must first configure the PLC in the configuration window "Sector"
(on page 21).
Port
TCP port to which the Masters connect. Defined by the norm as 2404.
Our drivers allow you to have several instances of the Process Gateway running at the same time.
That is why you can change this port:
Allowed port numbers: 1200 to 65535
Devices
List of configured devices.
Add
Adds a new device with standard settings. By default, it gets the invalid ID '????' and invalid
IP/link addresses. Before you can use or export the device, you must configure it.
Delete
Deletes the selected device. If no device was selected, this button is locked.
OK
Accepts all changed settings. They will immediately be stored in the current configuration file (as
defined in 'Configuration file').
After clicking on 'OK', all active Master connections will be closed and restarted
with the new settings. There may be communication errors during that.
Cancel
Discards all changed settings. Nothing is stored.
Help
Opens the help window (like the F1 button). If the help file does not exist on your system, please
contact the COPA-DATA support team via <CD_MAMLSUPPORT>
(mailto:support@copadata.com)
18
9.1.3
Device
In the part of the main window called 'Device' you can define the settings of the device.
Name
101
104
Name of the device for easy identification
Ip address IP
104
IP address of the Master. This allows to identify the device that the
Master communicates with. All IP addresses except 255.255.255.255 are
allowed.
Link address
101
Link address Via the link address contained in the TF 1.2 frame, the
master specifies the device that the command is intended for. With link
addresses, a Master can communicate with multiple devices. The
allowed range of the address depends on the setting 'links address size'
in the main settings.
Link address size = 1 allows a range of 0 to 254
Link address size = 2 allows a range of 0 to 65534
COA size
101
Defines the size of the COA (common object address).
Valid: 1 or 2 octet.
You can only change the COA size for 101. For 104, the value is
automatically set to 2, according to the standard.
COT size
101
Defines the size of the COT (cause of transmission).
Valid: 1 or 2 octet.
You can only change the COT size for 101. For 104, the value is
automatically set to 2, according to the standard.
IOA size
101
Defines the size of the IOA (information object address).
Valid: 1, 2 or 3 octet
You can only change the IOA size for 101. For 104, the value is
19
automatically set to 2, according to the standard.
Commands active
101
104
This options allows you to activate write access. Process information in
control direction are executed. If this options is deactivated, an entry in
the error protocol is created.
Max APDU size
104
Maximum length of APDU data as defined in the standard 870-5-104 5.
Valid: between 25 and 253.
Max. user data
101
Maximum length of user data as defined in TF1.2 870-5-2 3.2 .
Valid: between (19 + LAF size + COA size + COT size + IOA size) and
(255).
Short pulse length
101
104
Defines the size of the pulse for the 'Qualifier of Command' with the
value 'short pulse duration' (QOC = 1) in milliseconds.
Possible values: 0 to 4294967295
In the debug mode, there will also be a pulse for values greater
than/equal to 10000, even with QOC = 0. This allows you to test the
pulse generation with our IEC870 drivers.
Long pulse length
101
104
Defines the size of the pulse for the 'Qualifier of Command' with the
value 'long pulse duration' (QOC = 2) in milliseconds.
Possible values: 0 to 4294967295.
File transfer directory
101
104
Defines the directory for transfer of files and directories.
20
9.1.4
Sector
The window 'Sector' lists all sectors defined in the device. If you select a sector, its Information
Objects (on page 26) (IOs) will be displayed.
Add
Activates the dialog for creating a new sector. By pressing OK, you end the dialog and
create a new sector.
Edit
Activates the dialog for editing the selected sector. You can also launch the editor by
double-clicking on the sector in the list.
This button is inactive if no sector was selected.
Delete
Deletes the selected sector.
This button is inactive if no sector was selected.
Add
Activates the dialog for creating new IOs. By pressing 'OK', you end the dialog and
create a new IO.
This button is inactive if no sector was selected.
Edit
Activates the dialog for editing the selected IO. You can also launch the editor by
double-clicking on the IO in the list.
This button is inactive if no IO was selected.
Delete
Deletes the selected IO.
This button is inactive if no IO was selected.
21
Name
Any name. For easy identification of a sector.
COA
The COMMON ADDRESS OF ASDUs (IEC 60870-5-101 7.2.4) by which the sector is
addressed.
This number must be unique on the device side (1..254).
Time for Background
scan [min]
Supports the requirements of IEC 60870 Norm Chapter 7.4.13 "Background Scan". The
values are sent with COT = 2. Cycle time is stated in minutes.
Values are transferred cyclically in the time grid set up for all IOs with the "Background
Scan" option activated.
Values are only transferred cyclically if no spontaneous value is transferred within the time
set.
If the value is "0", cyclical transfer of values is deactivated for this sector.
Time for periodic
transfer [s]
Support of cyclical data transfer corresponding to the norm (IEC 60870-5-5 6.3). The values
are sent with COT = 1. Cycle time is stated in seconds.
Values are transferred cyclically for all IOs with the "Periodic data transfer" option
activated. IOs are transferred cyclically and not spontaneously.
If the value is "0", cyclical transfer of values is deactivated for this sector.
Transmission of
integrated
totals
Selection of the transfer mode (see IEC 60870-5-101 7.4.8) for the integrated totals - the IOs
of type:
 15 (M_IT_NA_1)
 16 (M_IT_NA_1)
 37 (M_IT_NA_1)
22
No reset is supported. An FRZ with a reset triggers a warning.
For modes A to D, IOs are requested immediately after connecting to the master of
zenon/straton. Value changes to integrated totals IOs are administered in their own buffer.
This can buffer the larger value of (IT IO number) * 4, or 2048 value changes.
With general
interrogation
Integrated Totals are also transferred during a general interrogation (C_IC_NA_1).
Mode A: Local freeze
with spontaneous
transmission
Integrated Totals are transferred when a value is changed.
Mode B: Local freeze
with counter
interrogation
Integrated Totals are only transferred with a counter interrogation command (C_CI_NA_1).
To do this, a maximum of 5 seconds is waited after the interrogation is activated until all ITs
have been supplied with values. ITs without a value are transferred with an invalid
qualifier. The value changes are buffered until the interrogation is completed (freeze active).
All ITs thus transfer the value of the point in time, when the last IT was supplied with a
value.
Mode C: freeze and
transmit by counter
interrogation
Transmission of
integrated totals
commands
As with mode B.
Mode D: freeze by
counter interrogation
command, frozen
values spontaneous
Transfer as with mode C, mode A is activated after conclusion of the interrogation.
OK
By pressing the button OK, you can check whether the COA is available in the device. If it is
already in use you will receive an error message. If it is available, the setting is accepted and
the dialog is closed.
Cancel
Discards all entries and closes the dialog.
Help
Opens the help window (like the F1 button). If you cannot display the help file, please
contact <CD_MAMLSUPPORT> (mailto:support@copadata.com)
23
Version
The CNT_MODE field is expected from version 3 onwards.
CNT_MODE
Configured mode of integrated totals IOs.
0
With general interrogation. (Default)
1
Mode A
2
Mode B
3
Mode C
4
Mode D
13
Advise for integrated totals fail.
14
Queue overrun. Integrated totals values lost.
572
Counter interrogation. Unsupported QCC.
573
Counter interrogation. Unexpected IOA.
574
Counter interrogation. Unsupported COT.
575
Buffer for integrated totals interrogation data to small.
24
1011
QCC FRZ is only partly supported.
1012
Counter interrogation already active.
Unsupported qualifier of counter
interrogation. <command>
Unknown QCC. RQT is only supported with 5.
Counter interrogation processed
without reset. < command>
Warning. Reset is not supported.
Cannot advise IT data point.
Device:(<Device ID>)<Device name>
Sector:(<COA>)<Sector name>
adv:0x<Advise ID>
Data points for integrated totals could not be requested.
IT Values lost, queue full!
Device:(<device>)<device>
Sector:(<COA>)<Sector name> <Value
change>
The buffer for the value changes of IT IOs is full. The value
change is lost.
25
Settings for information objects
Information object address
Defines the address under which the IO is addressed (IEC 60870-5-101 7.2.5). In
combination with the type ID, it must be unique per sector.
Type identification
Contains the supported Type identifications (IEC 60870-5-101 7.2.1).
The setting also determines the variables of the process control system that can be
associated to the IO based on their data types.
SCADA variable
Defines the variable from the process control system associated with the IO.
Syntax: <Project name>#<variable name> define the project connection.
Variables without project reference are looked for in the default project.
While entering, the system checks if the specified variable exists in the according
project and if it has a data type compatible with the type identification.
The Button '...' opens the dialog for variable selection. Read more about this in the
section 'Variable selection'.
(Scada stands for the name of the process control system.)
Data transfer
Determines the type of data transfer for IOs
26
Spontaneous
IO data transfer is spontaneous.
Spontaneous - values will
be queued when master is
offline
The data is buffered until it can be read by the master again. All buffered data is sent
with the status COT spont (3). The last buffered value is sent with the status COT
inrogen (20) again.
The buffering can be activated for the following TID:
M_SP_TB_1, M_DP_TB_1, M_ST_TB_1, M_BO_TB_1, M_ME_TD_1, M_ME_TE_1,
M_ME_TF_1 und M_IT_TB_1
The setting is not available for any other TID.
Background scan
IOs are transferred according to IEC 60870 norm as a background scan. A data point
that does not receive a new spontaneous value within the set background scan time
is automatically sent by the gateway after the time expired.
The setting is inactive if the background scan is locked at the sector (Time=0) or if
the type ID used does not support the background scan.
The following type IDs support a background scan:
M_SP_NA_1, M_DP_NA_1, M_ST_NA_1, M_BO_NA_1, M_ME_NA_1,
M_ME_NB_1, M_ME_NC_1
Periodic data transfer
Periodic data transfer in accordance with IEC 60870-5-5-6.3 norm.
IOs are transferred cyclically and not spontaneously.
The setting is inactive if periodic data transfer is locked for the sector (Time=0) or if
the type ID used does not support periodic data transfer.
The following type IDs support a background scan:
M_ME_NA_1, M_ME_NB_1, M_ME_NC_1
Off
Changes in value are not transferred. No value is sent for the IO during a general
interrogation (GI).
Sequence of Events
These settings define the IO-specific behavior for SOE
Inactive
Data point is not used for SOE description. Is automatically used for all type IDs that
do not support SOE.
Corresponds to the default value for a new IO. See IEC Norm 60870-5-101 7.4.11.3.1
27
All events
Each value or status change triggers a write in the open file. The setting is blocked if
the type ID if not planned for the SOE function.
Raising Edge
If the value changes from 0 to <>, this instigates a write in the opened file. The
setting is blocked if the type ID if not planned for the SOE function.
Falling Edge
If the value changes from <> to 0, this instigates a write in the opened file. The
setting is blocked if the type ID if not planned for the SOE function.
Raising + Falling Edge
A change of value from 0 to <> 0 or from <> 0 to 0 triggers a write in the open file.
The setting is blocked if the type ID if not planned for the SOE function.
File trigger
If a value is to be written due to the settings previously described, a new file is
created and opened for the activated file, provided this has not yet been opened. The
triggering itself is also written in the SOE file. The setting is blocked if the type ID if
not planned for the SOE function.
OK
Your settings are verified after pressing the button "OK". If they are valid, they are
accepted and the dialog is closed.
Cancel
Discards all entries and closes the dialog.
Help
Opens the help window (like the F1 button). If you cannot display the help file,
please contact <CD_MAMLSUPPORT> (mailto:support@copadata.com)
Info
The communication for Spontaneous data transfer, Background scan and Periodic
data transfer starts once the first general request has been received (C_IC_NA_1). For
background scan and periodic data transfer, the start of the transfer cycle is calculated per
IO from the time of the answer to the general query.
28
This dialog lists all available projects and their variables.
Projects
An asterisk (*) marks the default project.
Variables
The list of variables is filtered. You only see the variables that can be used with the 'type identification'
selected for the IO. Selecting a project updates the list of variables.
OK
Assumes the selected variable. Alternatively, the variable can be assumed by double clicking. When
loading, the currently configured project and the variable will be selected.
The same variable can be used several times:
for several IOs in the same sector or other sectors,
for the same device or another one.
If the dialog remains open and there is a reload in the Runtime, all lists will be emptied and refilled after
the reload is finished.
Cancel
Discards all entries and closes the dialog.
Help
Opens the help window (like the F1 button). If you cannot display the help file, please contact
<CD_MAMLSUPPORT> (mailto:support@copadata.com)
29
9.1.5
104 settings
Set the timeout times and APDUs in the 104 tab.
The following settings are available.
104 time outs. [ms] 0 disable
the timeout
T0 time-out of connection establishment
Timeout for establishing connection.
Value range 0..4294967295, standard value 30000.
T1 time-out of send or test APDUs
Time-out for frame confirmation by the master.
Value range 0..4294967295, standard value 15000.
T2 time-out for ack. in case of no data msg.
Time-out, within which the master should confirm if no data is
exchanged.
Value range 0..4294967295, standard value 10000.
T3 time-out for sending test frames
Time after which a U-frame is sent to the master if no data is to
be transferred.
Value range 0..4294967295, standard value 20000.
APDUs
30
k max. diff. receive seq. no. to send state
Number of maximum I-frames not yet confirmed by the master.
Value range 0..4294967295, standard value 12.
w latest ack. after rec. w I format APDUs
Number of I-frames received after a confirmation is sent.
Value range 0..4294967295, standard value 8.
Set to default
9.1.6
Reverts the settings to their default values.
XML-File
The configuration of the IEC870SI is stored in an XML file. You can import and export different
configurations with the buttons 'Export' and 'Import' in the main window.
The active configuration is stored in the INI file, for example:
[IEC 870]
SETTINGS=IEC870SLAVE.XML
You can choose any name. The path is the same as in the INI file.
The names of most fields intuitively indicate their meaning. The settings correspond to those that are
permitted in the dialog.
The values and structure of the XML file are verified when the file is read. Erroneous entries trigger an
error message that is also logged.
Attention
XML entries are case sensitive. Pay attention to use correct upper and lower cases.
process_gateway_IEC870Slave
The root node must have this name. Otherwise, the reading process will stop with
an error.
31
VERSION
Contains the current version of attributes and nodes.
Device_x
Nodes for the device configuration. X is replaced by a consecutive number,
starting with 1.
This way of naming nodes is not obligatory. A device is created for every node.
LinkAdr
In protocol 101, the 'link address' is set here. It must be unique for all devices.
For protocol 104, this entry has no meaning.
IpAdr
In protocol 104, the IP address of the Master is entered here. It must be unique
for all devices. For protocol 101, this entry has no meaning.
Sector_x
Number of nodes per configured sector. X is replaced by the COA.
This way of naming nodes is not obligatory. A sector is created for every node.
IO_x
Number of nodes per information object. X is replaced by a consecutive number,
starting with 1.
This way of naming nodes is not obligatory. An IO is created for every node.
ScadaVar
When the document is loaded, the existence of the specified variable in the
project is verified. Variables without project reference are looked for in the
default project.
[ScadaProjectName#]ScadaVariableName. (Scada stands for the name of the
process control system.)
TypeId
Type identification. When the document is loaded, the system will check if the
type ID with the specified variable data type is possible.
COA
Common object address. Must be unique for every device per sector.
IOA
Information object address. In combination with the type ID, it must be unique
per sector.
Is101active
With the value '1', the protocol 101 is activated, otherwise 104 will be active.
BSTime
Time for background scan
Unit: ms.
0 deactivates the background scan.
Default: 0
CYTime
time for cyclical data transfer
Unit: ms.
32
0 deactivates the cyclical transfer.
Default: 0
Available in version 2 and above
KindOfTransfer
States the type of data transfer.
0
Spontaneous. Is also the default value.
1
Backscan
2
Cyclical
3
Off
4
Spontaneous transfer with buffering
Default: 0
Available in version 3 and above
DeActDPIStd
DPI /DCS compliant (IEC60870 compliant) data transfer or internal control
system format
Version
6: describes an XML file with the following fields for SOE support
EnableSOE
0 = inactive
1 = SOE active
MaxBufferedFilesSOE
Maximum number of buffered SOE files.
AutodeleteFilesSOE
0 = no Autodelete
1 = Autodelete if maximum file number reached
MaxEventsPerFileSOE
Maximum number of ASDUs per file
PostTrgToSOE
Post trigger timeout in [ms]
FileToSOE
File timeout in [ms]
Information Object setting for SOE
support
Additional settings that must be made for SOE support at Information Object.
Version
4: describes an XML file with the following fields for SOE support
33
KindOfTransfer
TrgSOE
Defines when an update triggers a transfer.
0
Spontaneous
1
Background scan
2
Periodic
3
No transfer
0 = inactive
1 = IO acts as trigger
EvDetectionSOE
determines when a change to an IO value or status can trigger a write in the SOE
file.
0
SOE deactivated
1
All changes
2
Raising edges
3
Falling edges
4
Raising and falling edges
Example configuration for protocol 101:
34
Example configuration for protocol 104:
This chapter explains details on the communication in the Process Gateway:

Startup

General interrogation

Reset

Value changes

Priority

Read

Process Initialized
35

File transfer

Storage and naming of files for transfer

Spontaneous directory transfer

Monitoring command

Internal type T00

Master connected

Pulse generation

Reload

Broadcasts

Logging
9.2.1

Client name

Modules

IEC870Slave

OSI2

OSI7

Runtime
Startup
When the process gateway is started, it loads the configured driver.
The driver then tries to read out its active configuration from the file entered in the INI file. If this is not
possible, you will receive an error message and the configuration dialog will be opened for you.
If you do not quit the configuration dialog with OK, the application will quit.
Attention
If the application is launched as invisible, there will be no configuration dialog. The Process
Gateway will automatically quit if its configuration is invalid or missing.
36
9.2.2
General interrogation
The general request causes the driver to connect to the Runtime. It is required for communication via
spontaneous data transfer, background scan or periodic data transfer. The connection will be
established in sectors.
If the connection cannot be established, there will be a negative response to the general request. If there
is an active general request for the sector, it will be terminated and a warning message will be logged.
Value changes for IOs that have already sent their values to the master will be buffered as long as the
general request is active.
During a project reload, it is not possible to connect to the RT. The general request will fail in this case.
9.2.3
Reset
The Master must be able to recognize a communication interrupt, so he can react with a new general
request. This is why no process commands will be executed until the Master has caused a reset.
Every time there is a chance of data loss (value changes were lost), a reset will be triggered.
101
All commands will be rejected until the function code for reset (0) has been received. The code causes a
reset in the link layer and the application layer.
104
When the connection is interrupted, the Master immediately reacts and restarts the initialization
process. The reset will be caused if a Master connects.
Reset process command
By creating an IO of type C_RP_NA_1 with IOA 0, you can enable the control system to recognize
received commands.
The value of the variable is set to '0' and then to the value of QRP.
37
9.2.4
Value changes
The driver receives all value changes of the requested variables..
As this may cause the list of process information not yet transferred to the master to become very large,
the list of buffered value changes has a limited size.
Limit: At least: 2048 values or 4 x number of IOs per sector.
If the list exceeds this limit, the Master connection will be terminated. In this way, the master is
requested to obtain the next connection with a general request and obtain current value changes.
Value changes can be logged.
9.2.5
Priority
The driver supports class1 and class2 files.
The whole file transfer is treated as class 2. This makes sure that value changes will be transferred to the
Master even during a file transfer.
9.2.6
Read
A maximum of 2048 read requests can be active at the same time. If this limit is reached, any further
request will be rejected.
A read request is executed for every IO with the requested IOA.
There can also be several active requests for the same IO.
Read requests will be processed even if the general request is not finished yet.
38
9.2.7
Process initialized
You can cause the process control system to send the command M_EI_NA_1 (end of initialization) to the
Master. For that,

create an IO of type M_EI_NA_1 (T70) with IOA '0'.
The command will be sent if the current value of the variable is 126 and changes to 127. For the COI
(cause of initialization), 2 (remote reset) is used.
9.2.8
File transfer
The following applies for file transfer:

in the AFQ UI4, the values 1-4 are supported

in the SCQ UI4, the values 0-6 are supported;
0 stands for 'select file'
If a new transfer is started while another one is still active, the currently active transfer will be
interrupted and the new one will be started.
Storage and naming
Use the following scheme for storage and naming:
<Configured folder>\<COA>\<IOA>.<NOF>
'Transparent' (1) as NOF is supported.
The maximum size of files for transfer is 16.711.680 Bytes.
Spontaneous directory transfer
Spontaneous transfer of files in the folder for file transfer can be triggered by the process control
system. To do this:

create an IO of type F_DR_NA_1 (T126) with IOA '0'.
39
Change from 1 to 2
Starting transfer
3
Transfer active
4
Transfer finished
5
Transfer failure
Nested activation is prevented.
9.2.9
Sequence of Events (SOE)
40
Use sequences of events
If active, the SOE for the selected device is activated. If inactive, all SOE settings
to the IOs are ignored.
Default: Inactive.
Buffered SOE Files
If the number set for SOE files in the directory is reached for the sector, a
spontaneous directory transfer (type ID "F_DT_TA_1") is triggered. If the number
of files in the directory is doubled, the oldest file will start to be deleted (ring
buffer function).
Value range 1 to 1024.
Default: 1024
Events per File
Number of value changes that are written in a file before it is closed.
Value range: 1 to 4096.
Default: 512
SOE file auto deleting
If active, the reaction is that this is then automatically closed for type ID
"F_AF_NA_1" (confirmation for file) for an SOE file.
Post trigger timeout
If no ASDU is written in the file within this period of time, this is then closed. The
time period starts over with each ASDU written.
Value range: 100ms to 120000ms
Default: 1000ms
File timeout
Maximum time for which the file remains open (regardless of the number of
events).
Value range: 100ms to 120000ms
Default: 5000ms
The exchange of data for SOE starts immediately once the Gateway has been initialized. The exchange of data for data in
monitoring direction only starts when a master has connected and triggered a general interrogation (GI). The first value that is
initialized does not trigger an event and is thus also not entered into the file. The same applies if Runtime is again ready to
exchange data after reloading.
As part of the SOE function for transparent (1), event (3) is also supported as NOF.
41
Files are not transferred automatically if the maximum number of SOE files to be buffered is exceeded.
The IEC 60870 norm describes this with "may be activated". The Gateway does not support any file
transfers activated by the salvo in the current version.
As part of the SOE function for transparent (1), event (3) is also supported as NOF.
Automatic directory transfer:
In accordance with the IEC 60870 norm, an automatic spontaneous directory transfer is activated for the
following reasons with existing SOE files:

24 hours after the last automatic directory transfer.

if the master connects

if the maximum number of files to be buffered is exceeded
Warnings
Sequences of events for device <Devicename>
sector <Sectorname> are activated but no
trigger defined
The device has SOE activated, there is an IO in the sector with
active SOE but the trigger was not activated by any IO. No file is
created without a trigger. At least one IO in the sector must have a
trigger activated.
SOE value change without trigger and file is
closed. Value lost! Device:(<Device
ID>)<Device-Name> Sector:(<COA>)<Sector
name> <Value information>
A value change is not written because the SOE file is not open.
Code:1010
Error messages
Sequence of events active but no directory for
the file transfer defined!
SOE files are archived in the file transfer directory. Therefore a
directory for file transfer must be present.
42
SOE values lost, queue full! Device:(<Device
ID>)<Device-Name> Sector:(<COA>)<Sector
name> <Value information>
for IOs that have a SOE activated, data is exchanged to the stack via
a queue. This can assume a value of 2048 or 4 * the number of SOE
IO’s in sector entries. If this number is exceeded, this error message
is created and the value change is lost.
Error code: 6
Can't create subdirectory for file transfer.
Device:(<Device ID>)<Device name>
Sector:(<COA>)<Sector name> system
error:<System error code>
The subdirectory for the sector is automatically created for SOE in
the directory for file transfers. This error shows that this directory
could not be created. SOE then indicates that this sector is NOT
available.
Error code: 10
System error code
Contains the error code returned from the operating system.
Can't advise SOE data point. Device:(<Device
ID>)<Device name> Sector:(<COA>)<Sector
name> adv:0x<Advise ID>
Data point request for SOE IOs failed. SOE then indicates that this
sector is NOT available.
Error code: 11
Write asdu to file <Filename> fail!
Device:(<Device ID>)<Device name>
Sector:(<COA>)<Sector name> <Value> system
error: <System error code>
ASDU write to SOE file failed.
Illegal file name <Filename> detected!
Device:(<Device ID>)<Device name>
Sector:(<COA>)<Sector name>
Filenames for the file transfer have a defined format <IOA>.<NOF>.
The file does not adhere to this convention.
Error code: 8
Error code: 12
Auto delete for file failed! System error:
<System error code> <File transfer
information>
Error code: 9
File transfer information
Contains the information that identifies the file transfer.
9.2.10
Time synchronization
In order for time synchronization to be carried out, an information object of type 103 must be linked to
a process variable for any desired device. The first IO that uses type 103 is used as an enable.
43
This variable must have a value of <> 0 and not have any of the following statuses:

Blocked bit 44

faulty bit 18

switched off bit 20 or substitute value bit 27
Non execution of the command due to a missing enable (or status) does not lead to the connection being
broken
The missing configuration of the enable variable or the missing value of the enable variable leads to the
connection being lost.
The enable variable connects to the control system if the device is reset.
9.2.11
DPI / DCS mapping
It is possible to configure whether DPI/DCS should be transferred in accordance with the norm or in
accordance with the control system internal display. The default is in accordance with the norm.
44
Deactivate standard
If active, the values for DPI / DCS correspond directly to the values of the control
system.
If inactive, the value for DPI / DCS is mapped as follows:
 zenon value 0 = DCS / DPI value 1
 control system value 1 = DCS / DPI value 2
 control system value 2 = DCS / DPI value 0
 control system 3 = DCS / DPI value 3
This setting is automatically activated if an XML File with version 1 is read.
9.2.12
Select before operate
If the Process Gateway receives an individual or double command including a Select command, this
select is always answered with N_CONF (P/N Bit) = 0 (Success).
9.2.13
INVALID bit handling
If the Process Gateway receives an INVALID bit for an information object to be sent (from the control
system), the following quality bits for the information object are placed before sending:

NT (Not Topical)

IV (Invalid)
9.2.14
Monitoring command
Monitoring command single, double and regulating supports qualifiers 0 to 3.
0 is the default value and is used like 1.
45
Command state is set as the value for the SCADA variable
9.2.15
Internal type T00 (status variables)
The internal type T00 is used for communication between the Slave and the process control system.
For the status variables, each numeric zenon variable can be assigned. This enables an internal variable
to be used as the source for a type ID.
The variable provides the status information as to whether there is already a connection to the master.
create an IO of type T00 with IOA '1'. If a connection is established, the value will change from 0 to 1.
A decision as to whether commands are carried out in control direction can be made for each sector by
means of the variable control system. In contrast to device enable, for sector-related enable the
connection to the master is not broken if a write command comes and this is rejected. Rejected CMDs
receive act_con + PN as confirmation. Rejected CMDs generate a warning.
The zenon variable must be of UINT or DWORD type and is assigned with IOA 2 at T00 (Internal status).
If the value of the <> variable is 0, the CMDs are approved. The variable may not have status IV (IEC
60870 Qualifier invalid). If no IO is configured, the CMDs are always approved.
Info
Attendant warning message:
Commands for sector deactivated, execution prohibited. <Command text>
Warning: 1009 command in control direction was received due to a missing enable.
Status variable is set to 1 if the number of SOE files in the transfer directory exceeds the maximum
number of buffered files.
46
Variable provides status information on the current or most recently processed SOE file:
0 - initialization. As long as no SOE file was written.
1 - SOE file is opened
2 - file was closed
3 - too many SOE files in the directory
4 - error when writing the SOE file
5 - errors when creating the SOE file
Variable provides status information on the file transfer.
0 - no transfer active
1 - section is selected
2 - section is requested
3 - waiting on section confirmation
4 - waiting on confirmation of file transfer
255 - error when transferring
Variable provides the number of SOE files present in the transfer directory.
9.2.16
Pulse generation
The driver supports pulse generation.
After the time for the pulse has passed, the system will write '0' to the variable.
47
After closing communication, the pulse for all other active pulse variables will be stopped (i.e. writing a
"0").
That means:

Application is quit

new configuration is activated

Runtime performs a reload

Overflow of the list of buffered value changes of the sector
If a pulse is triggered for a running pulse generation, the active pulse generation will be stopped. The
variable contains the value 0.
9.2.17
Reload
If one of the projects is reloaded in the Runtime, the connection to all projects using the IOs in the sector
will be closed. The device with the according sector must be reset. That means: The connection to the
master is closed.
While the reload is active, you cannot establish a connection to the Runtime. This means that general
requests are also not possible.
9.2.18
Broadcasts
Broadcasts are supported for the following TYPE IDs:
ID C_IC_NA_1
C_CS_NA_1
48
9.2.19
Realtime invalid - Statusbit T_INVAL
If the IEC870 driver receives a real time stamp that is marked is invalid, it sets the T_INVAL status bit. In
this case, the local PC time is stamped. In the process gateway IEC870 slave, this status bit is forwarded
in the direction of messaging in the time stamp.
9.2.20
Logging
The driver supports a comprehensive logging function for:

Client name

zenProcGateway_IEC870Slave

Modules
Client name
The way the name of the client is displayed in the diagnosis viewer depends on the configuration. That
is why the name changes if you change the TCP port, the COM port or the protocol. In this case, the
logging settings may also change.
If the Process Gateway is started several times with the same settings, the same client name will be used.
The error messages of the different instances can be distinguished by the process ID.
49
Example

104 protocol with standard port 2404

101 if COM1 selected.

If the configuration has not been loaded yet, error messages during startup
will always be visible under this client.

101 with COM4.
The name contains the used COM port.
104 with port 12345.
The name contains the port for the Master connection.
Modules
Error messages are shown for all modules:

IEC870 Slave

OSI2

OSI7

SCADA Runtime (ScadaRT)
50
IEC870Slave
Concerns the connection to the Process Gateway and its configuration.

Errors during engineering
OSI2
Concerns the protocol level. This where framing with its according functions is implemented.
Information about:
Received data as byte dump
Sent data as byte dump
Function codes for 101
Errors on this level, e.g. in the framing
APCI for 104 (870-5-104 5)

Msg: Frame interpreting

Debug:
Received and sent data
Frame analysis.
New Master connection.

Deep Debug: Every request about existence of characters. Produces a large number of logging
entries!
51
OSI7
Concerns the application layer.
This is where commands are interpreted and executed.

Logging 'process and system information'

Errors in the ASDUs

Warning: Recursive interrogation

Msg: Process information, System information

Debug: Confirmed I-frames

Deep Debug: Interrogation runs. Produces a large number of logging entries!
ScadaRT
Messages for connection to the Runtime:

advised and unadvised variables

updated variables

Deactivating the project

Debug:
changed values
project inactive
52
9.2.21
Error codes
The following error codes can be displayed in the diagnosis server:
570
Value change for unknown cyclic IO
571
Transfer buffer too small to transfer a cyclic IO
This companion standard presents sets of parameters and alternatives from which subsets must be
selected to implement particular telecontrol systems. Certain parameter values, such as the choice of
'structured' or'unstructured' fields of the informationobject address of ASDUs represent mutually
exclusive alternatives. This means that only one value of the defined parameters is admitted per system.
Other parameters, such as the listed set of different process information incommand and in monitor
direction allow the specification of the complete set orsubsets, as appropriate for given applications. This
clause summarizes theparameters of the previous clauses to facilitate a suitable selection for aspecific
application. If a system is composed of equipment stemming from different manufacturers, it is
necessary that all partners agree on the selected parameters.
The interoperability list is defined as in IEC 60870-5-101 and extended with parameters used in this
standard. The text descriptions of parameters which are not applicable to this companion standard are
strike-through (corresponding check box is marked black).
NOTE In addition, the full specification of a system may require individual selection of certain
parameters for certain parts of the system, such as the individual selection of scaling factors for
individually addressable measured values.
The selected parameters should bemarked in the white boxes as follows:
[
] Function or ASDU is not used
[ X ] Function or ASDU is used as standardized (default)
[ R ] Function or ASDU is used in reverse mode
[ B ] Function or ASDU is used in standard and reverse mode
The possible selection (blank, X , R , or B ) is specified for each specific clause or parameter.
53
A black check box indicates that the option cannot be selected in this companion standard.
(system-specific parameter, indicate definition of a system or a device by marking one of the following
with ' X ')
[
] System definition
[
] Controlling station definition (Master)
[ X ] Controlled station definition (Slave)
(network-specific parameter, all configurations that are used are to be marked ' X ')
[ X ] Point-to-point
[ X ] Multipoint
[ X ] Multiple point to point
[
] Multipoint-star
(network-specific parameter, all interfaces and data rates that are used are to be marked ' X ')
[
] 100 bit/s
[ X ] 2400 bit/s
[
] 2400 bit/s
[
] 200 bit/s
[ X ] 4800 bit/s
[
] 4800 bit/s
[ X ] 300 bit/s
[ X ] 9600 bit/s
[
] 9600 bit/s
[ X ] 600 bit/s
[ X ] 19200 bit/s
[
] 19200 bit/s
[ X ] 1200 bit/s
[ X ] 38400 bit/s
[
] 38400 bit/s
[ X ] 56000 bit/s
[
] 56000 bit/s
[ X ] 57600 bit/s
[
] 64000 bit/s
54
[ X ] 115200 bit/s
[ X ] 128000 bit/s
[ X ] 256000 bit/s
[
] 100 bit/s
[ X ] 2400 bit/s
[
] 2400 bit/s
[
] 200 bit/s
[ X ] 4800 bit/s
[
] 4800 bit/s
[ X ] 300 bit/s
[ X ] 9600 bit/s
[
] 9600 bit/s
[ X ] 600 bit/s
[ X ] 19200 bit/s
[
] 19200 bit/s
[ X ] 1200 bit/s
[ X ] 38400 bit/s
[
] 38400 bit/s
[ X ] 56000 bit/s
[
] 56000 bit/s
[ X ] 57600 bit/s
[
] 64000 bit/s
[ X ] 115200 bit/s
[ X ] 128000 bit/s
[ X ] 256000 bit/s
(network-specific parameter, all options that are used are to be marked ' X '. Specify the maximum
frame length. If a non-standard assignment of class 2 messages is implemented for unbalanced
transmission, indicate the Type ID and COT of all messages assigned to class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this
companion standard.
55
[
] Balanced transmission
[255] Maximum length L
(both directions)*
[ X ] Unbalanced transmission
[
] not present
(balanced transmission only)
[ X ] One octet
[ X ] Two octets
[ X ] Structured
[ X ] Unstructured
*may be reduced by the system
When using an unbalanced link layer, the following ASDU types are returned in class 2 messages (low
priority) with the indicated causes of transmission:
[
]
The standard assignment of ASDUs to class 2 messages is used as follows:
9, 11, 13, 21
[ X ]
120 - 126
<1>
A special assignment of ASDUs to class 2 messages is used as follows:
All (as specified in the standard)
Note: (In response to a class 2 poll, a controlled station may respond with class 1 data when there is no
class 2 data available).
Mode 1 (Least significant octet first), as defined in 4.10 of IEC 60870-5-4, is used exclusively in this
companion standard.
(system-specific parameter, all configurations that are used are to be marked ' X ')
56
101 only
[ X ] Two octets
[ X ] One octet
(system-specific parameter, all configurations that are used are to be marked ' X ')
101 only
[ X ] Structured
[ X ] One octet
101 only
[ X ] Unstructured
[ X ] Two octets
[ X ] Three octets
(system-specific parameter, all configurations that are used are to be marked ' X ')
101 only
[ X ] Two octets (with originator address)
Originator address is set to zero if not used.
[ X ] One octet
(system-specific parameter, specify the maximum length of the APDU per system)
The maximum length of APDU for both directions is 253. The maximum length may be reduced by the
system.
[ 253 ]
Maximum length of APDU per system
57
(station-specific parameter, mark each Type ID ' X ' if it is only used in the standard direction, ' R ' if
only used in the reverse direction, and ' B ' if used in both directions).
[ B ]
<1>: = Single-point information
M_SP_NA_1
[ B ]
<2>: = Single-point information with time tag
M_SP_TA_1
[ B ]
<3>: = Double-point information
M_DP_NA_1
[ B ]
<4>: = Double-point information with time tag
M_DP_TA_1
[ B ]
<5>: = Step position information
M_ST_NA_1
[ B ]
<6>: = Step position information with time tag
M_ST_TA_1
[ B ]
<7>: = Bitstring of 32 bit
M_BO_NA_1
[ B ]
<8>: = Bitstring of 32 bit with time tag
M_BO_TA_1
[ B ]
<9>: = Measured value, normalized value
M_ME_NA_1
[ B ]
<10>: = Measured value, normalized value with time tag
M_ME_TA_1
[ B ]
<11>: = Measured value, scaled value
M_ME_NB_1
[ B ]
<12>: = Measured value, scaled value with time tag
M_ME_TB_1
[ B ]
<13>: = Measured value, short floating point value
M_ME_NC_1
[ B ]
<14>: = Measured value, short floating point value with time tag
M_ME_TC_1
[ B ]
<15>: = Integrated totals
M_IT_NA_1
[ B ]
<16>: = Integrated totals with time tag
M_IT_TA_1
[
]
<17>: = Event of protection equipment with time tag
M_EP_TA_1
[
]
<18>: = Packed start events of protection equipment with time tag
M_EP_TB_1
58
[
]
<19>: = Packed output circuit information of protection equipment with time tag
M_EP_TC_1
[
]
<20>: = Packed single-point information with status change detection
M_SP_NA_1
[
]
<21>: = Measured value, normalized value without quality descriptor
M_ME_ND_1
[ B ]
<30>: = Single-point information with time tag CP56Time2a
M_SP_TB_1
[ B ]
<31>: = Double-point information with time tag CP56Time2a
M_DP_TB_1
[ B ]
<32>: = Step position information with time tag CP56Time2a
M_ST_TB_1
[ B ]
<33>: = Bitstring of 32 bit with time tag CP56Time2a
M_BO_TB_1
[ B ]
<34>: = Measured value, normalized value with time tag CP56Time2a
M_ME_TD_1
[ B ]
<35>: = Measured value, scaled value with time tag CP56Time2a
M_ME_TE_1
[ B ]
<36>: = Measured value, short floating point value with time tag CP56Time2a
M_ME_TF_1
[ B ]
<37>: = Integrated totals with time tag CP56Time2a
M_IT_TB_1
[
]
<38>: = Event of protection equipment with time tag CP56Time2a
M_EP_TD_1
[
]
<39>: = Packed start events of protection equipment with time tag CP56Time2a
M_EP_TE_1
[
]
<40>:= Packed output circuit information of protection equipment with time tag
CP56Time2a
M_EP_TF_1
Either the ASDUs of the set <2>, <4>, <6>, <8>, <10>, <12>, <14>, <16>, <17>, <18>, <19> or of the set
<30> – <40> are used.
(station-specific parameter, mark each Type ID ' X ' if it is only used in the standard direction, ' R ' if
only used in the reverse direction, and ' B ' if used in both directions).
[ X ]
<45>: = Single command
C_SC_NA_1
[ X ]
<46>: = Double command
C_DC_NA_1
59
[ X ]
<47>: = Regulating step command
C_RC_NA_1
[ X ]
<48>: = Set point command, normalized value
C_SE_NA_1
[ X ]
<49>: = Set point command, scaled value
C_SE_NB_1
[ X ]
<50>: = Set point command, short floating point value
C_SE_NC_1
[ X ]
<51>: = Bitstring of 32 bit
C_BO_NA_1
[ X ]
<58>: = Single command with time tag CP56Time2a
C_SC_TA_1
[ X ]
<59>: = Double command with time tag CP56Time2a
C_DC_TA_1
[ X ]
<60>: = Regulating step command with time tag CP56Time2a
C_RC_TA_1
[ X ]
<61>: = Set point command, normalized value with time tag CP56Time2a
C_SE_TA_1
[ X ]
<62>: = Set point command, scaled value with time tag CP56Time2a
C_SE_TB_1
[ X ]
<63>: = Set point command, short floating point value with time tag CP56Time2a
C_SE_TC_1
[ X ]
<64>:= Bitstring of 32 bit with time tag CP56Time2a
C_BO_TA_1
Either the ASDUs of the set <45> – <51> or of the set <58> – <64> are used.
(station-specific parameter, mark ' X ' if used)
[ X ]
<70> : = End of initialization
M_EI_NA_1
60
(station-specific parameter, mark each Type ID ' X ' if it is only used in the standard direction, ' R ' if
only used in the reverse direction, and ' B ' if used in both directions).
[ X ]
<100>: = Interrogation command*
C_IC_NA_1
[ X ]
<101>: = Counter interrogation command
C_CI_NA_1
[ X ]
<102>: = Read command
C_RD_NA_1
[ X ]
<103>: = Clock synchronization command (option see 7.6)*
C_CS_NA_1
[
<104>: = Test command
C_TS_NA_1
[ X ]
<105>: = Reset process command
C_RP_NA_1
[
]
<106>: = Delay acquisition command
C_CD_NA_1
[
]
<107>: = Test command with time tag CP56Time2a
C_TS_TA_1
]
*also Broadcast (with Common Address of ASDU = 0xFF or 0xFFFF)
(station-specific parameter, mark each Type ID ' X ' if it is only used in the standard direction, ' R ' if
only used in the reverse direction, and ' B ' if used in both directions).
[
]
<110>: = Parameter of measured value, normalized value
P_ME_NA_1
[
]
<111>: = Parameter of measured value, scaled value
P_ME_NB_1
[
]
<112>: = Parameter of measured value, short floating point value
P_ME_NC_1
[
]
<113>: = Parameter activation
P_AC_NA_1
61
(station-specific parameter, mark each Type ID ' X ' if it is only used in the standard direction, ' R ' if
only used in the reverse direction, and ' B ' if used in both directions).
[ X ]
<120>: = File ready
F_FR_NA_1
[ X ]
<121>: = Section ready
F_SR_NA_1
[ X ]
<122>: = Call directory, select file, call file, call section
F_SC_NA_1
[ X ]
<123>: = Last section, last segment
F_LS_NA_1
[ X ]
<124>: = Ack file, ack section
F_AF_NA_1
[ X ]
<125>: = Segment
F_SG_NA_1
[ X ]
<126>: = Directory {blank or X, only available in monitor (standard) direction}
F_DR_TA_1
(station-specific parameters)
Shaded boxes: option not required.
Blank: functions or ASDU not used.
Mark Type Identification/Cause of transmission combinations:
' X ' if only used in the standard direction;
' R ' if only used in the reverse direction;
' B ' if used in both directions.
1
<1>
M_SP_NA_1
2
3
B
B
4
5
X
6
7
8
9
1
0
1
1
1
2
1
3
2
0
to
3
6
3
7
to
4
1
4
4
4
5
4
6
4
7
X
62
1
<2>
M_SP_TA_1
<3>
M_DP_NA_1
<4>
M_DP_TA_1
<5>
M_ST_NA_1
<6>
M_ST_TA_1
<7>
M_BO_NA_1
<8>
M_BO_TA_1
<9>
M_ME_NA_1
<10>
M_ME_TA_1
<11>
M_ME_NB_1
<12>
M_ME_TB_1
<13>
M_ME_NC_1
<14>
<15>
2
3
4
5
B
X
B
X
B
X
B
X
B
X
B
X
B
X
B
X
B
X
B
X
B
X
B
X
M_ME_TC_1
B
X
M_IT_NA_1
B
X
B
B
B
B
B
B
B
B
B
6
7
8
9
1
0
1
1
1
2
1
3
2
0
to
3
6
3
7
to
4
1
4
4
4
5
4
6
4
7
X
X
X
X
X
X
X
X
1
<16>
M_IT_TA_1
<17>
M_EP_TA_1
<18>
M_EP_TB_1
<19>
M_EP_TC_1
<20>
M_PS_NA_1
B
X
X
63
1
2
3
4
5
<21>
M_ME_ND_1
<30>
M_SP_TB_1
B
X
<31>
M_DP_TB_1
B
X
<32>
M_ST_TB_1
B
X
<33>
M_BO_TB_1
B
X
<34>
M_ME_TD_1
B
X
<35>
M_ME_TE_1
B
X
<36>
M_ME_TF_1
B
X
<37>
M_IT_TB_1
B
X
<38>
M_EP_TD_1
<39>
M_EP_TE_1
<40>
M_EP_TF_1
<45>
C_SC_NA_1
<46>
<47>
<48>
<49>
C_DC_NA_1
C_RC_NA_1
C_SE_NA_1
C_SE_NB_1
6
7
8
9
1
0
1
1
1
2
1
3
2
0
to
3
6
3
7
to
4
1
4
4
4
5
4
6
4
7
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
2
2
X
X
2
2
X
X
2
2
X
X
2
2
X
X
2
2
64
1
<50>
<51>
2
3
4
5
C_SE_NC_1
C_BO_NA_1
6
7
8
9
1
0
X
X
X
X
2
2
X
X
2
2
X
X
1
1
1
2
1
3
2
0
to
3
6
3
7
to
4
1
4
4
4
5
4
6
4
7
X
X
X
X
X
X
<58>
C_SC_TA_1
X
X
X
X
X
X
X
<59>
C_DC_TA_1
X
X
X
X
X
X
X
<60>
C_RC_TA_1
X
X
X
X
X
X
X
<61>
C_SE_TA_1
X
X
X
X
X
X
X
<62>
C_SE_TB_1
X
X
X
X
X
X
X
<63>
C_SE_TC_1
X
X
X
X
X
X
X
<64>
C_BO_TA_1
X
X
X
X
X
X
X
<70>
M_EI_NA_1*
<100>
C_IC_NA_1
X
X
X
X
X
X
<101>
C_CI_NA_1
X
X
X
X
<102>
C_RD_NA_1
<103>
C_CS_NA_1
<104>
C_TS_NA_1
<105>
C_RP_NA_1
<106>
C_CD_NA_1
<107>
C_TS_TA_1
X
X
X
X
X
X
X
X
X
X
X
X
X
65
1
2
3
4
5
6
7
8
9
1
0
1
1
1
2
1
3
2
0
to
3
6
3
7
to
4
1
4
4
4
5
4
6
<110>
P_ME_NA_1
<111>
P_ME_NB_1
<112>
P_ME_NC_1
<113>
P_AC_NA_1
<120>
F_FR_NA_1
X
X
<121>
F_SR_NA_1
X
X
<122>
F_SC_NA_1
<123>
F_LS_NA_1
X
<124>
F_AF_NA_1
X
<125>
F_SG_NA_1
X
<126>
F_DR_TA_1*
X
X
X
X
4
7
X
X
X
X
X
X
* Blank or X only
1
Optional.
Slave confirms deactivations of write command (TI <45> ... <64>) but corresponding activation is
already transferred to execution; actcon and actterm were already sent .
2
<0>
not used
<1>
periodic, cyclic
per/cyc
<2>
background scan
back
<3>
spontaneous
spont
66
<4>
initialized
init
<5>
request or requested
req
<6>
activation
act
<7>
activation confirmation
actcon
<8>
deactivation
deacts
<9>
deactivation confirmation
deactcon
<10>
activation termination
actterm
<11>
return information caused by a remote command
retrem
<12>
return information caused by a local command
retloc
<13>
file transfer
file
<14...19>
reserved
<20>
interrogated by station interrogation
<21...36>
interrogated by interrogation of the group 1..16
<37>
requested by general counter request
<38...41>
requested by counter interrogation of the group 1 ... 4
<42, 43>
reserved
<44>
unknown type identification
<45>
unknown cause of transmission
<46>
unknown common address of ASDU
<47>
unknown information object address
<48, 63>
for special use (private range)
inrogen
reqcogen
67
(station-specific parameter, mark 'X' if function is used)
[
]
Remote initialization
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions)
[ X ] Cyclic data transmission
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions)
[ X ] Read procedure
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions)
[ B ] Spontaneous transmission
(station-specific parameter, mark each information type ' X ' where both a Type ID without time and
corresponding Type ID with time are issued in response to a single spontaneous change of a monitored
object)
The following type identifications may be transmitted in succession caused by a single status change of
an information object. The particular information object addresses for which double transmission is
enabled are defined in a project-specific list.
[
] Single-point information M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and M_PS_NA_1
[
] Double-point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
68
[
] Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
[
] Bitstring of 32 bit M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1 (if defined for a specific project)
[
] Measured value, normalized value M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and M_ME_TD_1
[
] Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
[
] Measured value, short floating point number M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[ X ] global
[
] group 1
[
] group 7
[
] group 13
[
] group 2
[
] group 8
[
] group 14
[
] group 3
[
] group 9
[
] group 15
[
] group 4
[
] group 10
[
] group 16
[
] group 5
[
] group 11
Information object addresses assigned to each group
must be shown in a separate table.
[
] group 6
[
] group 12
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[ X ] Clock synchronization
[
] Day of week used
[
] RES1, GEN (time tag substituted/ not substituted) used
[ B ] SU-bit (summertime) used
optional, see 7.6
69
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[ X ] Direct command transmission
[ X ] Direct set point command transmission
[ X ] Select and execute command
[ X ] Select and execute set point command
[
] C_SE ACTTERM used
[ X ] No additional definition
[ X ] Short-pulse duration (duration determined by a system parameter in the outstation)
[ X ] Long-pulse duration (duration determined by a system parameter in the outstation)
[ X ] Persistent output
[
] Supervision of maximum delay in command direction of commands and set point commands
[
] Maximum allowable delay of commands and set point commands
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[ X ] Mode A: Local freeze with spontaneous transmission
[ X ] Mode B: Local freeze with counter interrogation
[ X ] Mode C: Freeze and transmit by counter-interrogation commands
[ X ] Mode D: Freeze by counter-interrogation command, frozen values reported spontaneously
[ X ] Counter read
[ X ] Counter freeze without reset
[
] Counter freeze with reset
[
] Counter reset
[ X ] General request counter
[
] Request counter group 1
[
] Request counter group 2
[
] Request counter group 3
[
] Request counter group 4
70
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[
] Threshold value
[
] Smoothing factor
[
] Low limit for transmission of measured values
[
] High limit for transmission of measured values
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[
] Act/deact of persistent cyclic or periodic transmission of the addressed object
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[
] Test procedure
(station-specific parameter, mark 'X' if function is used).
File transfer in monitor direction
[ X*] Transparent file
[
] Transmission of disturbance data of protection equipment
[ X ] Transmission of sequences of events
[
] Transmission of sequences of recorded analogue values
* a data can be transparently transported by the system but not generated or evaluated. Maximum file
size is 16711680 bytes.
File transfer in control direction
[
]
Transparent file
71
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
[ X ] Background scan
(station-specific parameter, mark ' X ' if function is only used in the standard direction, ' R ' if only
used in the reverse direction, and ' B ' if used in both directions).
] Acquisition of transmission delay
[
t0
30 s
Time-out of connection establishment
not fixed
t1
15 s
Time-out of send or test APDUs
not fixed
t2
10 s
Time-out for acknowledges in case of no data messages; t2 < t1
not fixed
t3
20 s
Time-out for sending test frames in case of a long idle state; t3 >
t1
not fixed
Recommended range for timeouts t0 - t2 : 1s to 255s, accuracy 1s
Recommended range for timeout t3 : 0s to 48hrs, accuracy 1s
Long timeouts for t3 may be needed in special cases where satellite links or dialup connections are used
(e.g. to establish connection and collect values only once per day or week). For dialup connections it
may be necessary to give up the connection supervision completely. This is achievable by setting the
timeout t3 to zero.
k
12 APDUs
Maximum difference receive sequence number to send state
variable
not fixed
72
w
8 APDUs
Latest acknowledge after receiving w I format APDUs
not fixed
Recommended range of values k: 1 to 32767 (215–1) APDUs, accuracy 1 APDU
Recommended range of values w: 1 to 32767 APDUs, accuracy 1 APDU (Recommendation: w should not
exceed two-thirds of k)
Portnumber
[
2404
not fixed
] Number N of redundancy group connections used
RFC 2200 is an official Internet Standard which describes the state of standardization of protocols used
in the Internet as determined by the Internet Architecture Board (IAB). It offers a broad spectrum of
actual standards used in the Internet. The suitable selection of documents from RFC 2200 defined in this
standard for given projects has to be chosen by the user of this standard.
[
] Ethernet 802.3
[
] Serial X.21 interface
[
] Other selection from RFC 2200:
List of valid documents from RFC 2200
1. ..........................................................................
2. ..........................................................................
3. ..........................................................................
4. ..........................................................................
5. ..........................................................................
6. ..........................................................................
7. etc.
73
After clicking the configuration button the following dialog opens:
Here the variables that should be connected can be selected. In the list on the left-hand side all variables
which are available in zenon are displayed. There they can be selected and moved to the MODBUS
export list with the button '>'. With the button '<' they can be removed again. If a variable is moved to
the export list, a dialog for the name assignment of the zenon variable to an offset in MODBUS opens:
74
The variables selected in this way then are continuously synchronized in zenon or in the MODBUS
system.
In the lower part of the configuration dialog the serial or TCP/IP connection to the MODBUS system can
be configured.
The following settings are available for the configuration of the serial interface:
Com
the serial interface for the access to the MODBUS system
Data bit
number of data bits (default: 8) 8)
Stop bit
number of stop bits (default: 8) 1)
Baud rate
Baud rate of the serial interface (default: 9600)
Parity
parity setting even/odd/no (default: no) No)
For the configuration via TCP/IP the port and the timeout in seconds can be defined.
The MODBUS system of the Process Gateway has a MODBUS hardware address that can be defined.
As a default the hardware address 1 is used. This value can be changed with the entry HWADDRESS in
the zenProcGateway.ini file (see next chapter).
The configuration file must be in the system folder.
[MODBUS]
Description of the property
COMPORT
serial interface (COM1 = 0, COM2 = 1,...)
75
BAUD
baud rate of the serial interface
BYTESIZE
number of data bits of the serial interface
PARITY
parity settings of the serial interface (0=no, 1=odd, 2=even)
STOPBITS
Number of stop bits of the serial interface (0=1, 1=1.5, 2=2)
TIMEOUT
timeout interval for serial communication in milliseconds
HWADDRESS
Hardware address of the MODBUS system (default: 1)
REFRESHRATE
Update time in milliseconds
SERIELL
serial communication (1) or communication via TCP/IP (0)
PORT
TCP/IP port
TCPTIMEOUT
TCP/IP timeout interval in seconds
[VARIABLES]
Description of the property
COUNT
number of variables to be exported
NAME_n
name of variable number n (0<=n<COUNT)
76
The Windows SNMP agent supports SNMP version 2 (SNMPv2c). It also supports the SNMP functions
(GET, GETNEXT, GETBULK, SET, TRAP).
More details about Microsoft's implementation of the SNMP can be found on the Microsoft TechNet
Website: “How SNMP Works” http://technet2.microsoft.com/windowsserver/en/library/bf555774-
2d63-4e96-b432-c4b7bcac6b531033.mspx
(http://technet2.microsoft.com/windowsserver/en/library/bf555774-2d63-4e96-b432c4b7bcac6b531033.mspx)
77
The Management Information Base (MIB) is a tree structure, in which the SNMP agent provides
variables (OID - Object Identifiers). See below: the MIB structure, with additional variables provided via
the Process Gateway.
1.3.6.1.4.1.300.1.1.0
copadata.info.statusinfo,
Runtime is (Online,
Offline)
string
read
yes
1.3.6.1.4.1.300.1.2.0
copadata.info.statusval,
Runtime is 1=Online
0=Offline
integer
read
yes
1.3.6.1.4.1.300.1.3.0
copadata.info.watchdog
integer
read
no
string
read
no
1.3.6.1.4.1.300.1.4.0
copadata.info.project,
name of project which
the Process Gateway reads
78
variables from
1.3.6.1.4.1.300.2.1.0
copadata.variables.ifNumber, number of
configured variables=OID
integer
read
yes
1.3.6.1.4.1.300.2.2.1.X
copadata.variables.ifTables.ifIndex,
configured OID index from the Process
Gateway configuration
integer
read
no
1.3.6.1.4.1.300.2.2.2.X
copadata.variables.ifTables.ifName,
variable name
string
read
no
1.3.6.1.4.1.300.2.2.3.X
copadata.variables.ifTables.ifValue,
variable value as Integer. All numerical
data types are formatted to an SNMP
Integer data type.
ATTENTION: the decimal places of REAL
and DOUBLE are lost.
integer
according to
configuratio
n in Process
Gateway
no
1.3.6.1.4.1.300.2.2.4.X
copadata.variables.ifTables.ifValueAsStri
ng, variable value as String. All numerical
data types are formatted to an SNMP
String data type.
string
according to
configuratio
n in Process
Gateway
yes
1.3.6.1.4.1.300.2.2.5.X
copadata.variables.ifTables.ifStatus,
variablen status value
integer
read
yes
1.3.6.1.4.1.300.2.2.6.X
copadata.variables.ifTables.ifTimestamp,
integer
read
yes
79
variable time stamp
After clicking the configuration button the following dialog opens:
80
Here the variables that should be connected can be selected. On the left-hand side all variables which
are available in zenon are displayed. You can select them there and move them to the SNMP export list
with the button >. You can remove them from the export list with the button <. If you move a variable
to the export list, a dialog for the name assignment of the zenon variable to an OID address in the SNMP
structure appears:
The variables selected in this way are then available on the SNMP server and are continuously
synchronized between zenon and the SNMP OID structure. For every OID address you can define
whether it can be write-accessed via SNMP SET. The exact structure of every OID address is described in
the chapter "MIB structure.
[SNMP]
REFRESHRATE
Update time in milliseconds
[VARIABLES]
COUNT
number of variables to be exported
NAME_n
name of variable number n (0<=n<COUNT)
81
PARAM_n
Parameter SNMP OID table offset and the information R=read only / RW=read and write with
the number n (0<=n<COUNT)
For the successful export the project name in zenProcgateway.ini in folder %CD_SYSTEM% must
be entered correctly. Enter it here:
[DEFAULT]
PROJECT=
If the entry is wrong or missing the gateway is closed without any error messages. Thus the
variable is not available.
To make sure that the SNMP Agent by Windows (SNMP.exe) provides the zenon MIB partial structure,
you have to configure the Process Gateway file AccessSNMP.dll in the registry as follows:
1. Installation of the Windows SNMP service via the control panel:
- up to Windows Vista via module: Software, Add Windows components
- since Windows Vista via module: Programs and functions, Switch Windows functions on/off
2. Installation of the Process Gateway with the file AccessSNMP.dll in sample directory
'C:\ProcessGateway'
3. Add the following keys and character strings using the registry editor:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\Extensio
nAgents]
Name='ProcessGateway' Wert='SOFTWARE\\COPA-DATA\\SNMP\\CurrentVersion'
[HKEY_LOCAL_MACHINE\SOFTWARE\COPA-DATA\SNMP\CurrentVersion]
Name='Pathname' Wert='C:\ProcessGateway\AccessSNMP.dll'
4. Start the SNMP service. This loads the process gateway file AccessSNMP.dll via the registry
configuration. If you want to change any configuration settings for the Windows SNMP service, do so
via control panel - administration - services - SNMP service - properties - security or the Trap tab. See
Windows Help.
82
83
The configuration of the database connection consists of two parts. The first part deals with the OLE-DB
connection. In the configuration dialog this OLE-DB connection can be defined with the selection button
for the Connect-String. Then the standard dialog for data connection properties is opened.
Additionally the name of the table can be defined, if the standard name ONLINE_VALUES should not be
used. This can be set with the entry TABLE in the section [DATABASE] of the configuration file
(zenProcGateway.ini).
The settings are taken over by the add-on when starting it.
There is a problem of the Process Gateway and the AcessSQL.dll in combination with Oracle
databases. With certain ODBC drivers it can happen, that no online values are written to the database. In
the extended ODBC logging you will find the error message: 1843.
The problem can be solved by changing the ODBC driver.
The version identification of the ODBC driver for Oracle version 9.2, with which the tool works is the
following: 9.02.00.05
84
In the configuration dialog the zenon variables that should be written to the SQL process image can be
defined. In order to do this the variables available in the zenon project - listed in the left part - have to
be added to the image - listed in the right part.
85
After closing the configuration dialog with OK, the table structure of the SQL database is automatically
generated. For the case, that it is created by hand:
86
In redundant operation two alternatives are available. In the first way the SQL database runs locally on
both servers and the Process Gateway also runs on both servers. As only online values are handled no
further alignment between the databases is necessary. The big disadvantage of this version is the high
network load that is a result from the additional reading of online values on the standby server.
In the second version the Process Gateway only runs on the Runtime server and writes data to a local or
a remote SQL database. In this alternative no additional network load between the Runtime and the
standby server occurs and in the case of the remote SQL database the server is not strained by external
requests to that database.
The configuration file must be in the system folder.
[DATABASE]
INITSTRING
OLE-DB connect-string to the SQL database
TABLE_ONL
name of the table that receives the process image
TABLE_VAR
name of the table that receives the variable IDs
REFRESHRATE
maximum refresh rate in milliseconds
[VARIABLES]
COUNT
number of variables to be exported
NAME_n
name of variable number n (0<=n<COUNT)
87
12.6.1
Table for process image
VARIABLE
int[4]
ID of the zenon variable
VALUE
varchar[64]
current value as string
VALUE_NUM
float
current value as float
TIMESTAMP
int[4]
time stamp of the current value (as UNIX time)
TIMESTAMP2
datetime
time stamp of the current value (as datetime)
STATUS
int[4]
status word of the current value
12.6.2
Table for variable IDs
VARIABLE
int[4]
ID of the zenon variable
NAME
varchar[128]
name of the control system variable
88
The OPC UA driver and all dialogs are only available in English.
Info
The OPC UA server can be used for all zenon versions from 5.50.
To start the process gateway with the OPC UA module, this must be entered into the
zenProcGateway.ini (on page 5).The configuration of the certificate is queries when the
process gateway is first started with the OPC UA module.
If no independent certificates are to be used, the certificates can be automatically created by clicking on
Yes.
89
After the process gateway has been started, statistical information on the number of updates in the time
period displayed and the number of unsuccessful updates is displayed. The configuration can also be
started in this dialog.
Exit
Closes process gateway.
Configuration
Opens configuration dialog.
Help
Opens help.
Clicking on Configuration in the process gateway statistics dialog opens the configuration dialog:
90
Name
Name of the server as it is shown on the client.
Port
TCP Port via which the client establishes the connection.
Default: 4840
Certificate Revocation List
File with all invalid keys.
Certificate Trust List Location
Path that contains all trustworthy keys. Should correspond to
the server certificate.
Server Certificate Location
Public key of the server. Used by the client for
encrypting messages.
Server Private Key Location
Private key of the server. Is used by the server to decrypt the
messages from the client.
OK
Confirms all settings and closes the dialog.
All active connections are ended and the server is
restarted with the new settings. Connection errors may occur in
the process.
Cancel
Rejects all setting changes and closes the dialog.
Help
Opens online help. If there is no help on your system, please
contact the support team by email at support@copadata.com.
For the OPC UA process gateway, all zenon variables are automatically prepared in the OPC UA address
space below the object folder in the corresponding zenon folder.
When started, the process gateway loads the configured driver.
91
The driver tries to read the active configuration from the given INI file. If this is not possible, an error
message will be given and the configuration dialog (on page 89) will be opened for you. If the
configuration is not confirmed with OK, the process gateway is closed.
Attention
If the application is started as invisible, there is also no configuration dialog
displayed. If the configuration is invalid or not present, the process gateway is
automatically closed.
The OPC UA process gateway only supports the OPC UA TCP binary protocol and does not contain a
discovery server. The client must also connect directly to the server. The connection address
corresponds to the scheme: opc.tcp://hostname.of.server:port
The module uses the security procedures that correspond to OPC UA (signing and encrypting messages)
as defined in the standard. Certificates are no currently checked for trustworthiness; all client certificates
are thus accepted. Furthermore, users are not verified; a client can thus register with all usernames and a
password.
The OPC UA Process Gateway supports the zenon information model for alarms and states. It is
activated as soon as a variable has at least a limit value.
92
From the time of activation, a linked client can be informed about limit values of a variable being
exceeded. It is also in a position to confirm the alarm, as in zenon Runtime.
The OPC weighting, as defined in standard, is shown on the index of the alarm classes linked to the limit
value. The index of an alarm class is automatically incremented by zenon Editor with each new alarm
class and can be checked in the properties. Up to 20 classes with the following allocation are supported:
HIGH
MEDIUM HIGH
MEDIUM
MEDIUM LOW
LOW
20
1000
19
950
18
900
17
850
16
800
15
750
14
700
13
650
12
600
11
550
10
500
9
450
8
400
7
350
6
300
5
250
4
200
3
150
2
100
93
1
50
If a variable with no alarm class is linked, the lowest possible classification 1 (LOW) is used.
The driver supports a comprehensive logging function via the diagnosis viewer.
FindServers
yes
GetEndpoints
yes
RegisterServer
no
OpenSecureChannel
no
CloseSecureChannel
no
CreateSession
yes
ActivateSession
yes
CloseSession
yes
Cancel
no
AddNodes
no
94
AddReferences
no
DeleteNodes
no
DeleteReferences
no
Browse
yes
BrowseNext
no
TranslateBrowsePathsToNodeIds
yes
RegisterNodes
no
UnregisterNodes
no
QueryFirst
no
QueryNext
no
Read
yes
HistoryRead
no
Write
yes
HistoryUpdate
no
Call
yes
CreateMonitoredItems
yes
ModifyMonitoredItems
yes
SetMonitoringMode
yes
95
SetTriggering
no
DeleteMonitoredItems
yes
CreateSubscription
yes
ModifySubscription
yes
SetPublishingMode
yes
Publish
yes
Republish
yes
TransferSubscriptions
no
DeleteSubscriptions
yes
96
Download PDF