GTW EnM C57b Compressed

Gateway
Technical Manual
System version: 5.0.5
GTW/EN M/C57b
DS Agile Gateway Technical Manual
CONTENTS
INTRODUCTION GTW/IT EN/C57a
SAFETY AND HANDLING GTW/SA EN/C57
FUNCTIONAL DESCRIPTION GTW/FT EN/C57
HARDWARE GTW/HW EN/C57
CONNECTION GTW/CO EN/C57
COMMUNICATIONS GTW/CT EN/C57
INSTALLATION GTW/IN EN/C57
ADJUSTMENTS GTW/AJ EN/C57
LOGIC DIAGRAMS GTW/LG EN/C57
APPLICATION GTW/AP EN/C57b
HUMAN INTERFACE GTW/HI EN/C57
MAINTENANCE GTW/MF EN/C57
PROBLEM ANALYSIS GTW/PR EN/C57
RECORD SHEET GTW/RS EN/C57
TECHNICAL DATA GTW/TD EN/C57
GLOSSARY GTW/LX EN/C57a

Product /Project name – Type of document
WARNING
This guide gives instructions for installation, commissioning and operation of the DS Agile Gateway.
However, the guide can not cover all conceivable circumstances or include detailed information on all
topics. In the event of questions or specific problems, do not take any action without proper authorization.
Please, contact the appropriate Alstom technical sales office and request the necessary information.
Refer to the System Release Notes for new features.
Any agreements, commitments, and legal relationships and any obligations on the part of Alstom,
including settlement of warranties, result solely from the applicable purchase contract, which is not
affected by the contents of the guide.
INTRODUCTION
GTW/EN IT/C57A
DS Agile Gateway & WACU Introduction
Contents
1 INTRODUCTION 3
2 INTRODUCTION TO ALSTOM'S DS AGILE GATEWAY MANUAL 4

2.1 Chapter description 4
3 INTRODUCTION TO DS AGILE GATEWAY 6

3.1 Functions 6
3.2 Gateway environment 7
GTW/EN IT/C57a IT-1

Introduction DS Agile Gateway & WACU
IT-2 GTW/EN IT/C57a

1 INTRODUCTION
The present document is a chapter of the Alstom DS Agile Gateway documentation. It describes the
documentation’s chapters you can find in the different guides, the types of applications and how to use the
product. It is the Introduction (IT) chapter of this Product's manual.
GTW/EN IT/C57a IT-3

2 INTRODUCTION TO ALSTOM'S DS AGILE GATEWAY MANUAL

This manual provides functional and technical descriptions of the product and of a comprehensive set of
functions for the product’s use and applications.
It applies to the DS Agile Gateway function implemented in industrial PC-type computers. It also includes
the DS Agile WACU (Wide Area Control Unit), which, by combining a DS Agile Gateway with an IEC 61131-3
sequential automation, performs gateway and automation functions between either:
• two voltage levels within one DS Agile System, or

• separate substations.
Note:
It is also possible to interface a DS Agile System with an upper level SCADA using a C26x controller. Please refer to
the DS Agile C26x manuals for that application.
Important note:
The MiCOM Alstom range of C264 substation and bay computers is being widened to encompass new applications.
On this occasion, the name of the range becomes DS Agile. Because new models will soon be available, the name
C264 is replaced by C26x in the manuals.
Similarly, the C26x setting software will now be called DS Agile S1 instead of MiCOM Alstom S1.
Please note that this is a phased evolution, and where the text in the manual refers to software labels, there may still
some references to the previous names until the software update is completed.
In addition, the C26x units will now be referred to as "controllers" rather than "computers" in order to avoid any
confusion with the PC-type computers used in other DS Agile sub-systems.
2.1 CHAPTER DESCRIPTION

Introduction Chapter (IT)
This is the present document; it contains the description of each chapter of the DS Agile Gateway guides. It
presents a brief introduction to DS Agile Gateways capabilities.
Safety Chapter (SA)
This chapter contains the safety instructions, handling and reception of electronic equipment, packing and
unpacking of parts, Copyrights and Trademarks.
Functional Description Chapter (FT)
This chapter contains a description of the product. It describes the functions of the DS Agile Gateway.
Hardware Description Chapter (HW)
This chapter contains the hardware product description.
Connection Chapter (CO)
This chapter contains the external wiring connections.
IT-4 GTW/EN IT/C57a

Communications Chapter (CT)

This chapter provides detailed information on the communication interfaces of the product, i.e. it gives the
profiles of the implemented protocols.
Installation Chapter (IN)
This chapter contains the installation procedures.
Adjustments Chapter (AJ)
This chapter contains the list of the DCOM settings used with the SCADA OPC protocol.
Logic Diagrams Chapter (LG)
This chapter contains logic diagrams of the DS Agile Gateway.
Applications Chapter (AP)
This chapter contains instructions on how to configure the features of the DS Agile Gateway using SCE.
HMI, Local control and user interface Chapter (HI)
This chapter contains the operator interface description: Menu tree organisation and browsing, description of
items.
Maintenance, Fault finding, Repairs Chapter (MF)
This chapter advises on how to recognise failure modes, fault codes and describes the recommended
actions for repair.
Problem Analysis Chapter (PR)
This chapter contains identification and resolution of the main problems which might occur in the DS Agile
Gateway.
Record Sheet Chapter (RS)
This chapter contains record sheet to follow the maintenance of the DS Agile Gateway.
Technical Data Chapter (TD)
This chapter contains technical data, including accuracy limits, recommended operating conditions, ratings
and performance data. It also lists environment specification, compliance with technical standards.
Glossary Chapter (LX)
This chapter contains lexical description of acronyms and definitions.
GTW/EN IT/C57a IT-5

3 INTRODUCTION TO DS AGILE GATEWAY
3.1 FUNCTIONS
The Telecontrol Gateway is the DS Agile control system's gateway. It provides the system with a connection
to a Remote Control Point (RCP), located in a dispatching centre (SCADA), thus allowing the dispatcher to
perform remote control and monitoring of the system from the SCADA.
Main functions of the gateway are:
• Transmission of remote indications from the system to the control centre.

• Transmission of remote measurements from the system to the control centre.
• Transmission of commands to the system, issued from the remote control centre.
The Gateway and the RCP communicate together by data exchanges based on a specific communication
protocol. The Gateway name describes in fact a range of gateways, each supporting a protocol dedicated to
a specific remote control type.
The communication with the SCADA uses a RS232 or Ethernet links.
The Gateways may be redundant in the DS Agile system in order to ensure the quality of service in case of a
communication failure. Moreover, it is multi-protocol, this means it has to manage several different protocols
in order to communicate with several different SCADAs.
A standardised protocol is used in accordance with the choice of each project's SCADA supplier.
IT-6 GTW/EN IT/C57a

3.2 GATEWAY ENVIRONMENT

The DS Agile Gateway is a dedicated device (PC type): do not confuse it with the remote control interface
function which may be included in the DS Agile C26x computers.
Figure 1: DS Agile Gateway environment
GTW/EN IT/C57a IT-7

IT-8 GTW/EN IT/C57a

SAFETY & HANDLING
GTW/EN SA/C57
DS Agile Gateway & WACU Safety & Handling
Contents
1 INTRODUCTION 3
2 SAFETY 4
2.1 Health and Safety 4
2.2 Explanation of symbols and labels 4
2.3 Installing, Commissioning and Servicing 4
3 WARRANTY 5
4 COPYRIGHTS & TRADEMARKS 6

4.1 Copyrights 6
4.2 Trademarks 6
5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS 7
GTW/EN SA/C57 SA-1

Safety & Handling DS Agile Gateway & WACU
SA-2 GTW/EN SA/C57

1 INTRODUCTION
The present document is a chapter of the Alstom DS Agile Gateway documentation. It describes the safety,
handling, packing and unpacking procedures applicable to Alstom DS Agile Gateway software tools.
GTW/EN SA/C57 SA-3

2 SAFETY
Warning:
This Safety Section should be read before commencing any work on the equipment.
2.1 HEALTH AND SAFETY

The information in the Safety Section of the DS Agile System documentation is intended to ensure that
products are properly installed and handled in order to maintain them in a safe condition. It is assumed that
everyone who will be associated with the DS Agile System equipments will be familiar with the contents of
the different DS Agile System Safety Sections and all Safety documents related to the PC and
Communication networks.
2.2 EXPLANATION OF SYMBOLS AND LABELS

The meaning of symbols and labels may be used on the DS Agile System equipments or in the DS Agile
System product documentation, is given below.
2.3 INSTALLING, COMMISSIONING AND SERVICING
Equipment operating conditions

The DS Agile System equipments should be operated within the specified electrical and
environmental limits.
Fibre optic communication

Optical LED transceivers used in Switch boards are classified as IEC 825-1 Accessible Emission
Limit (AEL) Class 1 and consequently considered eye safe.
Optical power meters should be used to determine the operation or signal level of the device.
SA-4 GTW/EN SA/C57

3 WARRANTY
The media on which you receive Alstom’s software are warranted not to fail to execute programming
instructions, due to defects in materials and workmanship, for a period of 90 days from date of shipment, as
evidenced by receipts or other documentation. Alstom will, at its option, repair or replace software media that
do not execute programming instructions if Alstom receives notice of such defects during the warranty
period. Alstom does not warrant that the operation of the software shall be uninterrupted or error free.
A Return Material Authorization (RMA) number must be obtained from the factory and clearly marked on the
package before any equipment will be accepted for warranty work. Alstom will pay the shipping costs of
returning to the owner parts which are covered by warranty.
Alstom believes that the information in this document is accurate. The document has been carefully reviewed
for technical accuracy. In the event that technical or typographical errors exist, Alstom reserves the right to
make changes to subsequent editions of this document without prior notice to holders of this edition. The
reader should consult Alstom if errors are suspected. In no event shall Alstom be liable for any damages
arising out of or related to this document or the information contained in it.
Except as specified herein, Alstom makes no warranties, express or implied, and specifically disclaims any
warranty of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part of Alstom shall be limited to
the amount therefore paid by the customer. Alstom will not be liable for damages resulting from loss of data,
profits, use of products or incidental or consequential damages even if advised of the possibility thereof.
This limitation of the liability of Alstom will apply regardless of the form of action, whether in contract or tort,
including negligence. Any action against Alstom must be brought within one year after the cause of action
accrues. Alstom shall not be liable for any delay in performance due to causes beyond its reasonable
control.
The warranty provided herein does not cover damages, defects, malfunctions, or service failures caused by
owner's failure to follow the Alstom installation, operation, or maintenance instructions; owner's modification
of the product; owner's abuse, misuse, or negligent acts; and power failure or surges, fire, flood, accident,
actions of third parties, or other events outside reasonable control.
GTW/EN SA/C57 SA-5

4 COPYRIGHTS & TRADEMARKS
4.1 COPYRIGHTS
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or
mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in
whole or in part, without the prior written consent of Alstom.
4.2 TRADEMARKS
Alstom, the Alstom logo and any alternative version thereof are trademarks and service marks of Alstom.
The other names mentioned, registered or not, are the property of their respective companies.
SA-6 GTW/EN SA/C57

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS

Alstom products are not designed with components and testing for a level of reliability suitable for use in or in
connection with surgical implants or as critical components in any life support systems whose failure to
perform can reasonably be expected to cause significant injuries to a human.
In any application, including the above reliability of operation of the software products can be impaired by
adverse factors, including -but not limited- to fluctuations in electrical power supply, computer hardware
malfunctions, computer operating system, software fitness, fitness of compilers and development software
used to develop an application, installation errors, software and hardware compatibility problems,
malfunctions or failures of electronic monitoring or control devices, transient failures of electronic systems
(hardware and/or software), unanticipated uses or misuses, or errors from the user or applications designer
(adverse factors such as these are collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons (including the risk
of bodily injuries and death) should not be reliant solely upon one form of electronic system due to the risk of
system failure to avoid damage, injury or death, the user or application designer must take reasonably steps
to protect against system failure, including -but not limited- to back-up or shut-down mechanisms, not
because end-user system is customised and differs from Alstom testing platforms but also a user or
application designer may use Alstom products in combination with other products.
These actions cannot be evaluated or contemplated by Alstom; thus, the user or application designer is
ultimately responsible for verifying and validating the suitability of Alstom products whenever they are
incorporated in a system or application, even without limitation of the appropriate design, process and safety
levels of such system or application.
GTW/EN SA/C57 SA-7

SA-8 GTW/EN SA/C57

FUNCTIONAL DESCRIPTION
GTW/EN FT/C57
DS Agile Gateway & WACU Functional Description
Contents
1 INTRODUCTION 3
1.1 Scope of the document 3
1.2 Main features 3
2 PROCESS INTERFACE 4
3 DS AGILE GATEWAY MANAGEMENT 5

3.1 Configuration management 5
3.1.1 Configuration tool 5
3.1.2 Downloading tool 5
3.2 Database management 5
3.3 Time management 6
3.4 Operation mode management 7
3.4.1 Substation Remote/Local mode checking 7
3.4.2 SBMC mode checking 7
3.4.3 Taking Control 8
3.5 Redundancy management 8
4 COMMUNICATION LAYER 9
4.1 Telecontrol bus 9
4.2 Station bus 10
4.3 Loss of communication 10
5 SBUS ACQUISITION 11
5.1 IEC 61850-8-1 acquisition 11
5.2 IEC 61850-8-1 supported Common Class 11
5.3 IEC 61850-8-1 Controls 12
5.4 IEC 61850/IEC 61850 DS Agile Gateway 12
5.4.1 Reports transmission 12
5.4.2 IEC 61850/IEC 61850 DS Agile Gateway redundancy cluster 12
5.4.3 SBMC mode processing for lower network bays 14
5.4.4 FSS (Force/Suppress/Substitute) processing for lower network bays 15
6 LEGACY BUS IEC 60870-5-104 MASTER ACQUISITIONS 18

6.1 Basic redundant architecture 19
6.2 Complex architectures 20
7 ISAGRAF REDUNDANCY CLUSTER 21
GTW/EN FT/C57 FT-1

Functional Description DS Agile Gateway & WACU
FT-2 GTW/EN FT/C57

1 INTRODUCTION
1.1 SCOPE OF THE DOCUMENT

This document is a chapter of the DS Agile Gateway documentation. It is the functional description (FT) of
the DS Agile Gateway between DS Agile system and SCADA. The hardware description is defined in HW
(Hardware) chapter. The product's capabilities, specifications and environmental limits are grouped in
chapter GTW/EN TD.
1.2 MAIN FEATURES

The DS Agile Gateway is in charge of data exchange between two networks: the DS Agile Network with its
IEC 61850-8-1 devices and the dedicated network with remote SCADA (Supervisory Control And Data
Acquisition). Several protocols are implemented to make available communication with SCADA.
The implemented SCADA protocols are:
• IEC 60870-5-101
• IEC 60870-5-104
• Modbus
• DNP3
• OPC (this protocol is not available if the OS of the PC hosting DS Agile Gateway is Windows XP
Embedded)
• IEC 61850-8-1
GTW/EN FT/C57 FT-3

2 PROCESS INTERFACE
In the DS Agile system, direct process acquisition is done by DS Agile C26x controllers and IEDs. All data
are presented on the Station Bus IEC 61850-8-1 network. DS Agile Gateway gets all supervisory information
on SBUS network and stores them into its kernel. It is then able to transmit data to SCADA when it asks for
them. The DS Agile Gateway has several protocols implemented into DLL. There is one DLL started per
communication link with the SCADA to allow possibly several ways of transmission of the same data.
Figure 1: DS Agile Gateway architecture
DS Agile Gateway is then composed in three modular parts:
• Acquisition DLL:
IEC 61850-8-1 SBUS agency
• Kernel storing data changes
• Protocol DLL
To know the data to catch on SBUS and their respective mapping on SCADA Protocol, the DS Agile
Gateway uses a current database loaded from its hard disk at start-up. A second or stand-by database is
used for new database download while current is running.
FT-4 GTW/EN FT/C57

3 DS AGILE GATEWAY MANAGEMENT
3.1 CONFIGURATION MANAGEMENT

The Configuration files are divided into three main parts:
• SBUS mapping: Station Bus connecting the DS Agile system,

• TBUS mapping: Telecontrol Bus connecting to SCADA / remote control points i.e. slave protocols IEC
60870-5-101 (T101) & IEC 60870-5-104 (T104), Modbus...,
• LBUS mapping: Legacy Bus connecting Field Bus to IED i.e. legacy IEC 60870-5-101 and IEC 60870-
5-104 Master acquisitions
The kernel reads the configuration file during the initialisation phase of the DS Agile Gateway application. It
subscribes to SBUS predefined data, then runs as much Protocol DLL processes as defined in configuration
and product definition (each protocol DLL is under license).
3.1.1 CONFIGURATION TOOL

To operate the DS Agile Gateway needs a configuration file or database. It is generated by DS Agile SCE
(System Configuration Editor). The generated database has a specific configuration version incremented
when creating or updating the control system.
The database is a zip file that contains all data needed to operate the DS Agile Gateway. It is to be noticed
that there is no on line settings or parameterisation of the DS Agile Gateway.
Details of the configuration process are described in the chapter GTW/EN AP.
3.1.2 DOWNLOADING TOOL

DS Agile SCE provides a configuration file that has to be downloaded into the DS Agile Gateway possibly
through SBUS Ethernet network. DS Agile SMT (System Management Tool) is in charge of this operation.
Without database or in case of fault the DS Agile Gateway remains in a maintenance mode. DS Agile SMT
has the following features:
• to download a stand-by database

• to switch stand-by database to operational one
• to change by operator request the operating mode between maintenance and operational
• The transitions between modes are detailed in GTW/EN LG chapter.
3.2 DATABASE MANAGEMENT

The DS Agile Gateway has two databases, the current one (operational) and standby one (or reserved). New
database is downloaded over the standby one without interrupting DS Agile Gateway normal behaviour.
Starting with a current database, DS Agile Gateway checks database coherency to its inner needs.
When SBUS communication starts, DS Agile Gateway checks communication data coherency between itself
and other devices on IEC 61850-8-1.
It checks if IEC 61850-8-1 servers are present on Ethernet, if their database version and system revision are
the same.
After the database compatibility checking it subscribes on SBUS network data to transmit to SCADA.
GTW/EN FT/C57 FT-5

3.3 TIME MANAGEMENT

The data received from the SBUS servers are time stamped with UTC (Coordinated Universal Time). For
protocols T101 and T104 data sent to the SCADA may be time stamped with DS Agile Gateway local time
(which may be different than UTC). This choice is defined during the configuration step (available values
"UTC" or "Local" for "time reference" attribute of the related protocol). For the others available SCADA
protocols no change is made on the time stamping of the data sent to the SCADA.
There are several means to time synchronise the components of the DS Agile system:
• An external clock (GPS type usually) can distribute the time synchronisation signal (IRIG-B) to each
DS Agile components.
• Generally in order to limit the associated wiring, the IRIG-B signal is directly wired to the System
Master Clock (one - or two when redundant - C26x Bay Controller), which distributes the time
synchronisation signal to the DS Agile components via the IEC 61850 backbone as shown below. The
System Master Clock acts as an SNTP server.
• An alternative to the use of a System Master Clock is to use a third party SNTP server hosted by a PC
in the system, typically DS Agile OI. Then all IEC 61850 devices are SNTP clients.
SCADA
External DS Agile Gateway

Clock (GPS
typically) No time synchronisation
via SCADA Protocol
SBUS IEC 61850
Which
synchronises IRIG -B
System Master Clock C26x
Which synchronises Operator time

through Station Bus setting
SNTP Clients
IEC 61850 device
Which synchronises
through Legacy Bus
Legacy IEDs
S1046ENa
Figure 2: DS Agile standard time synchronisation scheme
Some serial SCADA protocols can also deliver the time synchronisation signal to a DS Agile Gateway fitted
with a HOPF board:
This signal updates the date and time of a clock (HOPF board) fitted in a PCI slot of the Gateway computer.
This clock delivers the IRIG-B signal to the System Master Clock.
The clock can also be connected to a GPS antenna in order to get the IRIG-B input.
The resulting scheme is shown below.
Priority is given to synchronisation via the GPS clock. If it fails, DS Agile switches to the SCADA
synchronisation mode. It reverts to the GPS mode when it is recovered.
Priority management between the different modes prevents possible toggling.
FT-6 GTW/EN FT/C57

SCADA synchronisation frame

GPS antenna DNP3, T101 - only one protocol at a
time may synchronise the HOPF clock
External Clock (GPS)

HOPF 6039 in DS Agile Gateway computer
IRIG-B
SNTP servers
System Master Clock
S1047ENa
Figure 3: Example of time synchronisation via a serial SCADA protocol
3.4 OPERATION MODE MANAGEMENT

DS Agile Gateway is designed to medium and large substations where operator interfaces are often present
at local room, or bay level. To avoid conflict between these control points, each control into the electric
substation is subject to checking.
Three levels of checking are managed by the DS Agile Gateway:
• Remote/Local substation,
• SBMC mode,
• Taking control.
3.4.1 SUBSTATION REMOTE/LOCAL MODE CHECKING

DS Agile Gateway checks the Local/Remote Substation mode to allow SCADA control only when control is
configured for exploitation check and Substation is in Remote mode.
The Remote/Local bay mode is checked by the computer.
3.4.2 SBMC MODE CHECKING

An electrical bay can be switched to SBMC mode (Site Based Maintenance Control), so that, even if the
substation is in remote mode, any control command received from a SCADA and configured as SBMC-
dependent is rejected and not forwarded to the bay(s).
An electrical bay is usually switched to SBMC mode while commissioning operations or tests are being
performed in it. The supervisory data from the bay can be configured so as to be filtered out by DS Agile
Gateway and not forwarded on to the SCADA. While the bay is in SBMC mode, its signals are transmitted to
its SCADA link with an “SBMC-suppressed” or "SBMC-substituted" state in order not to forward non-
significant events to the SCADA. Switching off the SBMC mode causes the SBMC data to be transmitted to
the SCADA with their current value.
GTW/EN FT/C57 FT-7

3.4.3 TAKING CONTROL

A specific SCADA control called “Taking Control” allows the SCADA to switch substation exploitation mode
from Local to Remote and to take control on one SCADA port. Only controls received on this port will be
accepted by DS Agile Gateway.
3.5 REDUNDANCY MANAGEMENT

DS Agile Gateway can have several kinds of redundancy into the system:
• Two identical DS Agile Gateways (referred to as a cluster of Gateways)

• Redundant SBUS with special Ethernet switch (managed by the board)
• Redundant protocols on same DS Agile Gateway (identical or same protocol with separate dynamic
data to transmit when asked by SCADA)
• Dual link protocol (same protocol and data on redundant link managed by SCADA)
Acquisitions of system information are sent simultaneously to the two DS Agile Gateways. The SCADA is in
charge of choosing the DS Agile Gateway it wants to communicate with.
FT-8 GTW/EN FT/C57

4 COMMUNICATION LAYER
DS Agile Gateway has two different types of communications:
• Telecontrol Bus (TBUS) to SCADA

• Station Bus (SBUS) to station
• That can use different physical means.
SCADA
Telecontrol bus
DS AGILE GTW
Station bus
(IEC61850)
IEC61850 devices
Figure 4: Communications
4.1 TELECONTROL BUS

DS Agile Gateway behaves as a slave into master/slave protocol. The chapter GTW/EN CT gives the
associated companion standard or supported function.
Protocols:
• IEC 60870-5-101 (T101)

• IEC 60870-5-104 (T104)
• Modbus MODICON
• DNP3
• OPC (OLE for Process Control)
• IEC 61850-8-1
Link layer:
• RS 232
• Ethernet 10 or 100 Mbps for IEC 61850-8-1, T104 and OPC
Physical support:
• Copper (DB9 connector)

• Optical fiber (multimode or single mode)
Number of communication links:
Up to four different protocols and up to 2 channels per protocol can be configured on a per DS Agile
Gateway basis.
GTW/EN FT/C57 FT-9

4.2 STATION BUS

DS Agile Gateway behaves mainly as a client of other IEC 61850-8-1 devices: DS Agile controllers, IEC
61850-8-1 IEDs, DS Agile OI.
Protocol:
IEC 61850-8-1
Link layer:
Ethernet 10 or 100 Mbps
Physical support:
Copper twisted pair (RJ45 connector)
Number of communication links:
One (an Ethernet DIN-rail switch can be used for redundancy Ethernet network).
4.3 LOSS OF COMMUNICATION

Refer to the FAQ in chapter GTW/EN MF.
FT-10 GTW/EN FT/C57

5 SBUS ACQUISITION
If server is connected with the same database version the DS Agile Gateway subscribes to the data defined
in its database.
5.1 IEC 61850-8-1 ACQUISITION

The DS Agile Gateway acquires data from SBUS Ethernet network using only REPORT mechanism. The DS
Agile Gateway does not translate GOOSE.
The REPORT acquisition done by the DS Agile Gateway gets:
• data value
• data state or quality attribute (validity and several kind of invalid state)
• time tag of latest data value change
• time tag quality attribute (server synchronised or not when event occurs)
Data quality defines if data is valid or not: Unknown when disconnected, Saturated, Undefined. An Invalid
quality attribute is translated to a specific SCADA invalid coding when correspondence exists. For more
details, refer to SII document for REPORT mechanism.
Reports are usually of class URCB, hence lost in event of communication loss.
Buffered reports can be configured; then, at DS Agile Gateway initialization, the Gateway receives:
• the Unknown status if the BRCB server is disconnected

• the BRCB content otherwise
The buffered reports are issued by a C26x, or an IEC/IEC gateway if the DS Agile Gateway is a node of an
upper network (refer to section 5.4).
Acquisition of a full buffer (100 reports for C26x) can take up to 10 s. A new event is acquired afterward. Any
Buffer overflow information is transmitted to all the TBUS clients as an SPS. (For details, refer to
C26x/EN AP.)
5.2 IEC 61850-8-1 SUPPORTED COMMON CLASS

DS Agile Gateway can pick up the following kind of data or common class on IEC 61850-8-1. Their
conversion to SCADA protocol is function of the protocol used (MODBUS MODICON has no mechanism for
time tag transmission, unknown state on IEC 61850-8-1 is converted by IV bit set on T101…). The upper
communication is detailed in protocol companion standard in the chapter GTW/EN CT.
IEC 61850-8-1 information Class Comment
With time tag, with quality attribute on DP on time
Single-point indication SPS_ST,SPC_ST
tag
Double-point indication DPS_ST, DPC_ST With/without time tag
Integer indication INS_ST, INC_ST With/without time tag
Protection activation indication ACT_ST With/without time tag
Is managed in 5 SPS_ST
Protection activation Phase indication ACT_ST_Phs
With/without time tag
Is managed in 1 SPS_ST & 1 INS_ST
Directional Protection activation indication ACD_ST
Directional Protection activation Phase Is managed in 5 SPS_ST & 5 INS_ST
ACD_ST_Phs
indication With/without time tag
Step position indication (transformers) BSC_ST With/without time tag
GTW/EN FT/C57 FT-11

IEC 61850-8-1 information Class Comment

MV_MX
WYE_MX
Measurement value (AI) Type: digital, analogue, 1 among N
DELTA_MX
Formats: floating point, scaled, normalised, integer
APC_MX
Integrated totals (counters) (Accl) BCR_ST With/without time tag
Single or double control SPC_DPC_CO Direct or Select/execute
Step position control (transformers) BSC_CO With/without time tag
Regulating step control APC_SP Direct or Select/execute
5.3 IEC 61850-8-1 CONTROLS

DS Agile Gateway supports Common Class expressed before (SPC_DPC_CO, BSC_CO, APC_CO).
Basically it writes the corresponding control onto the server common class and waits control termination
(possibly with NACK codes) to translate it to upper SCADA control termination.
DS Agile System defines Bypass controls on common control class by specific attribute. Bypass control has
usually no equivalence on common SCADA protocol, also each bypass control that may need to be defined
is treated as a specific protocol control. The DS Agile Gateway can manage only the synchrocheck bypass.
5.4 IEC 61850/IEC 61850 DS AGILE GATEWAY

An IEC 61850/IEC 61850 DS Agile Gateway connects together two IEC 61850-8-1 station bus networks
called the lower network and the upper network.
To configure the DS Agile Gateway, refer to chapter GTW/EN AP.
5.4.1 REPORTS TRANSMISSION

Reports are usually of class URCB, hence lost in event of communication loss on the upper network.
It is possible to configure the buffering of reports (class BRCB) and their transmission to the upper network
when the connection is back.
The buffer is circular (FIFO). Ex. where the oldest event has been overwritten due to overflow:
.996 997 998 999 1000 1001 2 3
. END START
Buffered reports of xPS can be configured; in this case, at DS Agile Gateway initialization, the upper network
DS Agile Gateway and/or OI receive from the server side of the IEC/IEC gateway:
• the Unknown status if the server is disconnected

• the BRCB content otherwise
When the buffer capacity (1000) is overrun, a Buffer overflow SPS is raised and is transmitted to TBUS
clients when the communication is recovered.
5.4.2 IEC 61850/IEC 61850 DS AGILE GATEWAY REDUNDANCY CLUSTER

An IEC 61850/IEC 61850 DS Agile Gateway can be duplicated. In this event, both DS Agile Gateways have
exactly the same configuration.
FT-12 GTW/EN FT/C57

IEC61850 upper network
Gateway A Gateway B
IEC61850 lower network

S0514ENa
The main features of the management of this redundancy are:
• both Gateways perform the same acquisition on the lower network and send the same information to
the upper network
• one Gateway is master at one time: an IEC object (RedSt: Redundancy status) is set for a master
Gateway and reset for backup Gateway; the Gateways are servers of this object
• an IEC 61850-8-1 client on the upper network takes only into account information coming from the
Gateway whose the RedSt is set. It sends controls only to this Gateway
• In event of failure of the active Gateway, the other one becomes active
• In event of network failure (upper network or lower network), the current Gateway goes in
Maintenance mode and the other one takes it over
Note: The reports buffered in the former Gateway are lost.
Buffered reports from C26x controllers can be configured for all the Gateways.
The C26x controllers in the upper network cannot send buffered reports to the IEC/IEC Gateways.
Example: the buffered report sending is depicted by arrows with interrupted stroke. Each C26x owns four
buffers for reports (drawn as circles). The GOOSE communication between C26x units is depicted by arrows
with continuous stroke:
GTW/EN FT/C57 FT-13

Note: ISaGRAF automation is allowed in IEC/IEC Gateways. Refer to the next section.
5.4.3 SBMC MODE PROCESSING FOR LOWER NETWORK BAYS

The IEC 61850/IEC 61850 Gateway could be connected to a client system on the upper network, such as a
SCADA, that may have a different way of managing the SBMC mode, which could cause compatibility
issues. Where this is the case, the IEC 61850/IEC 61850 Gateway must manage SBMC mode filtering itself.
The behaviour of the SBMC filtering feature depends on the type of upper network client:
• If the client is a DS Agile system that can process the SBMC specific features then the
IEC 61850/IEC 61850 Gateway does not need to manage SBMC mode filtering in the lower network's
bays.
• If the client is a third party IEC 61850 client that cannot process SBMC specific features then the
IEC 61850/IEC 61850 Gateway must filter the data coming from a lower network bay in SBMC mode.
The IEC 61850/IEC 61850 Gateway can process the SBMC mode in two possible ways:
• It manages SBMC mode filtering on behalf of its upper network client.

• It ignores the SBMC mode and lets its upper network client manage it.
FT-14 GTW/EN FT/C57

5.4.3.1 OPERATION
• If the Gateway is configured to manage SBMC mode filtering, it will apply predefined state changes to
SBMC-dependent datapoints whenever a lower network bay switches to SBMC mode. If it is not
configured to manage SBMC mode filtering, the Gateway will leave the datapoints unchanged.
• If the Gateway receives a control command for a bay that is in SBMC mode, that command will be
forwarded on to the bay only if the Gateway is configured NOT to manage SBMC mode filtering.
Otherwise the command will be blocked.
• If a datapoint changes states while the bay to which it is attached is in SBMC mode, that state change
will be forwarded on to the upper network only if the Gateway does NOT manage SBMC mode
filtering. It will be blocked if the Gateway manages SBMC mode filtering.
5.4.3.2 SBMC INTEGRATED CONTROL

Integrated control of datapoints is applied to the SBMC Control SPC/SBMC SPS pair managed by the
Gateway in order to feed back to the SCADA the SBMC status of bays controlled by IEDs or C26x on a lower
legacy network (T101M/T104M).
When SBMC is enabled for a bay or group of bays, the state of the associated SBMC SPS datapoint
switches to ON. When SBMC is disabled, the state of the SBMC SPS datapoint switches to OFF. When the
Gateway software starts up, the state of the SBMC SPS datapoint is UNKNOWN.
The current state, as it is perceived by the Gateway (ON, OFF or UNKNOWN), is transmitted to the SCADA.
Depending on the type of lower network and on whether the SCADA is connected to the upper or lower
network, several application cases are possible. Their configuration is explained in the Application chapter:
GTW/EN AP.
Note:
In order for the Gateway to manage the SBMC Control SPC/SBMC SPS pair, it must also manage the electrical bay
that they are attached to.
Note:
The SBMC Control SPC/SBMC SPS datapoints only affect SBMC-dependent datapoints attached to the same electrical
bay.
5.4.4 FSS (FORCE/SUPPRESS/SUBSTITUTE) PROCESSING FOR LOWER NETWORK

BAYS
The Gateway can receive from the DS Agile OI operator FFS commands to change the states of datapoints.
Processing is similar to that offered by the DS Agile C26x BCU except that automatic forcing of an invalid
datapoint to a preset state is not available; commands have to be issued by an operator.
Whenever an FSS command is received, the Gateway first checks that the target datapoint:
• is configured,
• is not the feedback of a command in progress.
If the target datapoint does not meet these requirements, the command is ignored.
If the target datapoint meets these requirements, the datapoint's FSS status is displayed on the Operator
Interface and the command is processed according to its type:
GTW/EN FT/C57 FT-15

5.4.4.1 SUBSTITUTION PROCESSING

When it receives a "Substitute" command, the Gateway checks that the datapoint state can be substituted
(set in configuration, see C26x/EN AP). It marks the datapoint as SUBSTITUTED and sends the substituted
value to the upper network(s).
While the datapoint is substituted, every state change received from the bay is saved but not forwarded to
the upper network(s).
When it receives an "Unsubstitute" command, the Gateway selects the latest received state and sends that
actual value to the upper network(s).
5.4.4.2 FORCING PROCESSING

Forcing is similar to substitution except that it is applied to invalid states. When it receives a "Force"
command, the Gateway checks that the datapoint state can be forced (set in configuration, see C26x/EN
AP). It marks the datapoint as FORCED and sends the forced value to the upper network(s).
While the datapoint is forced, if a valid state change is received from the bay, the Gateway considers the
datapoint state unforced and sends that valid value to the upper network(s).
Note:
Automatic forcing is only available for commands managed by the DS Agile C26x. For electrical bays managed by a
DS Agile Gateway, setting xPC datapoints to Automatic forcing (see C26x/EN AP) will be ineffective. The Gateway
only takes into account manual forcing commands received from the DS Agile Operator Interface.
5.4.4.3 SUPPRESSION PROCESSING

When it receives a "Suppress" command, the Gateway checks that the datapoint state can be suppressed
(set in configuration, see C26x/EN AP). If the upper network is managed by an IEC 61850-8-1 protocol, it
marks the datapoint as SUPPRESSED and sends that state to the upper network. If for instance, the upper
network is managed by an IEC 60870-5-101 or -104 protocol, transmission of the datapoint state is simply
blocked. (See GTW/EN CT Communications chapter for details on protocols.)
5.4.4.4 FSS INFORMATION STORAGE

The list of FSS datapoints and related information is saved in the Gateway's permanent flash memory and
updated each time one of the datapoints' FSS state is updated (added, modified or removed). Each time this
happens the updated list is transmitted to the standby gateway if there is one. The list is preserved in case
of power down or reboot of the Gateway but it is deleted whenever a new database is loaded or switched.
5.4.4.5 GATEWAY START UP

When the Gateway starts up, it loads the FSS list into active memory (database and protocols) before re-
acquiring the network's non-FSS datapoint states.
5.4.4.6 FSS PROCESSING IN REDUNDANT ARCHITECTURE

When the active Gateway receives an FSS command, it transmits the information to the standby Gateway.
The standby Gateway then updates its own FSS list.
FT-16 GTW/EN FT/C57

Initialisation of FSS synchronisation

When a Gateway starts up and after it recovers from a communications loss, it checks whether the other
Gateway is present and if so, whether it is active. It that is the case, the starting Gateway:
• sends a presence indication to the active Gateway,

• requests read access to the active Gateway's FSS file,
• reads and copies the FSS file into its own local directory,
• sends a read acknowledgement to the active Gateway,
• applies the received FSS states to its database kernel.
If the other Gateway is not detected when the starting Gateway checks whether it is present, it loads the FSS
file stored in its flash memory into its database kernel. There is no redundancy.
Switch-over
When the standby Gateway becomes the active Gateway, FSS commands are sent to it for as long as it
remains active.
Fault mode
Both Gateways exchange every second a health signal in which they indicate their redundancy mode (active
and standby). If both Gateways are simultaneously declaring standby, for instance when they are both
starting, each Gateway loads it own local FSS file and neither requests read access from the other. There is
no synchronisation of the FSS lists. As soon as a Gateway becomes active, the standby gateway initialises
FSS synchronisation (see above).
GTW/EN FT/C57 FT-17

6 LEGACY BUS IEC 60870-5-104 MASTER ACQUISITIONS
Figure 5: Example of system architecture for one link to a HVDC substation
In this example, the T104 master is used to interconnect substations at each end of the high-voltage DC link.
The T104 Master software acts as a master for the IEDs connected to the gateway using the IEC 60870-5-
104 protocol.
FT-18 GTW/EN FT/C57

6.1 BASIC REDUNDANT ARCHITECTURE

• The configuration contains 2 IEC 60870-5-104 communication networks per gateway.
• 2 IEDs are connected to the same network.
Figure 6: Basic redundant architecture
In this architecture, the following concepts are implemented:
• The Gateway is redundant.

• The IEDs may be redundant, with a main IED and a backup IED.
• Each gateway communicates with each IED on one network.
• An IED is connected to only one network.
• Network connectivity is ensured by Ethernet switches
GTW/EN FT/C57 FT-19

6.2 COMPLEX ARCHITECTURES

The following architectures are configurable using DS Agile SCE:
Standby
WACU
Redundant
WACU
Link dedicated to redundancy,
managed by RTX
Redundant IEDs
Standalone and/or Redundant

redundant IEDs IEDs
(1)
Should be 0.0.0.0 if no redundancy is defined.
(2)
This is the IP address of the WACU on one T104M network.
This IP address must be also attributed to a dedicated NIC (Network Internet Communication) interface.
(3)
This address is used by WACU to establish the TCP connection with the IED.
S1021ENb
Figure 7: Complex architecture
FT-20 GTW/EN FT/C57

7 ISAGRAF REDUNDANCY CLUSTER

If ISaGRAF is declared in a WACU (Wide Area Control Unit), the redundancy covers gateway activities and
ISaGRAF automation. The automation runs simultaneously on both WACUs (hot redundancy), but outputs
are allowed only on the active WACU.
The WACUs are linked by an Ethernet link.
On each WACU, the automation application is aware of both gateways communication and redundancy
statuses, and sends the switchover order according to the ISaGRAF program.
The switchover between the 2 WACUs can happen in different ways:
• The active WACU manages the network adapters and can decide on its own to switch over, e.g. to
change protocol
• The standby WACU decides to become active when the active one does not send any more activity
signal (e.g., the active WACU goes in Maintenance mode, or is disconnected from the SBUS network
(see the GTW/EN LG chapter).
The automation requires to install RTX on both WACUs, a real-time extension for Win32 platform. The RTX
allows Windows to run only when all real-time processing is finished.
Each WACU can be connected to an ISaGRAF workbench through an Ethernet link for debugging, stepwise
operation, etc. It is allowed to add additional programs on this computer (e.g.: SCE).
GTW/EN FT/C57 FT-21

FT-22 GTW/EN FT/C57

HARDWARE
GTW/EN HW/C57
DS Agile Gateway & WACU HW Hardware
Contents
1 INTRODUCTION 3
2 INDUSTRIAL PC DESCRIPTION 4
2.1 Main features 4
2.2 Description 5
2.2.1 Dimensions 5
2.2.2 Front panel 6
2.2.3 Rear panel 6
2.3 Communication 7
3 FANLESS EMBEDDED PC DESCRIPTION 8

3.1 Main features 8
3.2 Rear Panel External I/O 11
GTW/EN HW/C57 HW-1

HW Hardware DS Agile Gateway & WACU
HW-2 GTW/EN HW/C57

1 INTRODUCTION
This document is a chapter of the DS Agile Gateway documentation. It is the chapter Hardware Description
(HW) of this Product.
The gateway may be either an industrial PC or a fanless Embedded PC.
To get further details about the PC hardware, refer to the User’s Manual supplied with the industrial PC or
with the fanless Embedded PC.
GTW/EN HW/C57 HW-3

2 INDUSTRIAL PC DESCRIPTION
2.1 MAIN FEATURES

To increase environmental capabilities, an industrial PC may be used. This type of PC has a steel rugged
chassis, especially designed to run a high reliability application in a harsh environment.
Alstom has selected 2 variants of an Advantech™ design, fitted with the following modules:
Designation Description
A505Q variant A507Q variant
Chassis 4U rack mountable chassis (black) Advantech ACP 4320Q
Power Supply 400W ATX/PFC auto-switching power supply (100 – 240 VAC, 60 – 50 Hz, 8 – 4 A))
CD/DVD drive Optical Driver: 18X SATA DVD ROM
Removable HDD trays 2 3.5" SATA HDD trays
USB ports 2 USB 2.0 ports on front panel, 4 USB 2.0 ports on rear panel
Parallel ports 1 parallel port on rear panel
Serial ports 2 serial ports on rear panel
Ethernet ports 2 RJ45 ports on rear panel
Video ports 1 VGA and 1 DVI, both on rear panel
PS/2 ports 1 for keyboard and 1 for mouse, both on rear panel
Air filter
Cooling
Fans: 1 (12 cm / 114 CFM) + 1 (6 cm / 28 CFM)
Cooler LGA1155/1156 CPU cooler
LGA1155 Intel® Core™ i7/i5/i3/Pentium ATX with DVI/VGA, Dual Gigabit LAN, DDR3,
Mother Board
SATA III
Intel® Core™ i5-2400, 3.1 GHz clock speed / Intel® Core™ i7-2600, 3.4 GHz clock speed /
Processor
6 MB cache 8 MB cache
Dual channel DDR3 SDRAM at 1333 MHz, SDRAM DDR3 at 1333 MHz,
RAM Memory
240-pin, 4 GB (1 x 4 GB module) 240-pin, 8 GB (2 x 4 GB modules)
Hard disks Seagate 3"5, 1 TB, 7000 rpm (2 HD in RAID 1 configuration on PCIe slot)
RAID controller card CPU board, Highpoint RAID 10 card, SAS 4 channels, (PCIe x 4)
LAN/NIC Additional NIC Card: Dlink / Intel Network Card 10/100/1000 M PCI Slot
Keyboard Standard keyboard according to location
Mouse Logitech® M100 3-Button USB Optical Mouse (Black)
Microsoft® Windows Embedded Microsoft® Windows 7 Ultimate 64 bits, MUI,
Operating System
XP Professional SP3 OEM BIOS on USB with secure boot
Test IPC System Installation and 8-hour burn-in-test included
Table 1: Industrial PC specification
Note: This PC cannot host ISaGRAF in a redundant architecture
HW-4 GTW/EN HW/C57

2.2 DESCRIPTION
2.2.1 DIMENSIONS
482 mm x 526.4 mm x 177 mm
Figure 1: Industrial PC dimensions
GTW/EN HW/C57 HW-5

2.2.2 FRONT PANEL
DVD-ROM
System reset button drive
Alarm reset button
Filter cover(*)
Two SATA
HDD trays
Dual USB ports
(*)
Filter cover: see PC
user manual for
instructions on how to
replace the filter S1045ENa
Figure 2: Front panel
2.2.3 REAR PANEL

You will need to reserve sufficient space at the back of the device to fit the wiring connections.
Fan Serial ports VGA screen RJ45 Ethernet Parallel

connector connectors port
Power supply Power supply Keyboard DVI-D screen

connector on/off switch connector connector USB ports PCI slots S1044ENb
Figure 3: Rear panel
HW-6 GTW/EN HW/C57

2.3 COMMUNICATION
Mother board 14 slots ISA/PCI
3 Com Ethernet board Station Bus (IEC61850 devices)
Serial port board (2 ports) Remote connection to SCADA
CPU board 2 serial ports Remote connection to SCADA

S0133ENb
Figure 4: Communication
GTW/EN HW/C57 HW-7

3 FANLESS EMBEDDED PC DESCRIPTION

Advantech's UNO-3000 series are high-performance Pentium M/Celeron M grade, embedded automation
computers with four PCI expansions.
UNO-3000 series feature a rugged and field-proven design offering dual power inputs and battery backed-up
SRAM.
Different from most industrial PCs, UNO-3000 series are more compact and reliable.
These are open platforms that can fulfill any demanding requirements from the industrial field, and it is an
ideal solution for industrial automation and control.
UNO-30x4 provides embedded operating system with a pre-configured image that has optimized onboard
device drivers, and support Windows XP Embedded to fulfill the toughest requirements for comprehensive
functionality and high reliability.
Note: The product specification is detailed in chapter GTW/EN TD (Technical Data).
3.1 MAIN FEATURES

• Supplier: Advantech
• Model reference: UNO-3074/UNO-3074A
• Onboard Atom® or Core 2 Duo processor (DB15 or DVI-D depending on the model)
• Onboard 512 KB battery-backed SRAM
• Two RS232 & two RS232/422/485 ports with RS-485 automatic flow control
• Four USB 2.0 ports
• Additional NIC Card: Dlink / Intel Network Card 10/100/1000 M PCI Slot
• Four PCI-bus expansion slots for versatile applications
• Industrial proven design; anti-shock up to 50 G, anti-vibration up to 2 G, 4 GB Flash memory in place
of hard disk
• 4-ch isolated DI, 4-ch isolated DO with timer, counter and interrupt handling
• Supports dual power inputs
• Windows XP (SP2) Embedded ready platforms with write protection (EWF)
• Onboard system & I/O LED indicators
• Supports Boot from LAN function
• Fanless design with no internal cabling
• Reset button
• Display connector (VGA DB15 or DVI-D depending on the model)
HW-8 GTW/EN HW/C57

WARNING:
If ISaGRAF is installed in a WACU redundancy cluster, it is mandatory to add on both
WACU units a special NIC Card: Intel Network Card PRO/1000 GT Desktop Adapter (it
includes the chipset INTEL 82541PI GEth). Advantech Product code: 96NIC-1G-P-IN4
185.40
151.80
17.6
60.00
63.00 248.60
12.00
80 237.40
R2.
14.05
R
3.
50
7.00
0
R6.0
10.90
210.44
212.04
179.70
80
R2.
10.90
21.90
0
R6.0
Figure 5: Fanless embedded PC dimensions: A300/A400 model (Advantech UNO-3074)
GTW/EN HW/C57 HW-9

Figure 6: Fanless embedded PC dimensions: A301 model (Advantech UNO-3074A)
HW-10 GTW/EN HW/C57

3.2 REAR PANEL EXTERNAL I/O
Four USB 2.0 ports

Two 10/100Base-T
RJ-45 ports
VGA Port
LED Indicators for Power, Power input 1,
Power input 2, Power fault, IDE, Diagnosis, 4
COM ports Tx/Rx, and Alarm for battery
backup.
4 Serial Ports
Keyboard/Mouse
Four PCI-bus expansion slots
Dual power inputs

4-ch isolated DI and 4-ch isolated DO
S0590ENb
Figure 7: Rear panel of the A300/A400 model (Advantech UNO-3074)
Two 10/100/1000Base-T
RJ-45 ports
LED Indicators for Power, Standby,
HDD (unused), SRAM battery, Tx/Rx
for COM ports. Keyboard/Mouse
VGA Port
Four PCI-bus expansion slots

Four USB 2.0 ports
4 Serial Ports
One eSATA port
4-ch isolated DI and 4-ch isolated DO
Two IEEE-1394 ports Dual power inputs
S1044ENa
Figure 8: Rear panel of the A301 model (Advantech UNO-3074A)
GTW/EN HW/C57 HW-11

HW-12 GTW/EN HW/C57

CONNECTION
GTW/EN CO/C57
DS Agile Gateway & WACU Connection
Contents
1 INTRODUCTION 3
2 CONNECTOR BLOCKS 4
2.1 RJ 45 connection 4
2.2 DB9 Serial connection 5
2.3 DB26 Serial connection 6
2.4 Power supply connectors 7
GTW/EN CO/C57 CO-1

Connection DS Agile Gateway & WACU
CO-2 GTW/EN CO/C57

1 INTRODUCTION
The present document is a DS Agile Gateway chapter of the documentation. It describes the connections
you will need to make with the gateway. It is the chapter Connection (CO) of this Product.
To get further details about connections you can see the User’s Manual supplied with the industrial PC the
gateway works on.
GTW/EN CO/C57 CO-3

2 CONNECTOR BLOCKS
The DS Agile Gateway is a software and hardware package. The hardware platform the gateway runs on is
an industrial PC or a fanless Embedded PC. To see the description of these PCs, refer to the HW chapter.
The fanless Embedded PC can host a switch; to get information about the connections, refer to the
dedicated documentation.
2.1 RJ 45 CONNECTION
A connection is required to connect the DS Agile Gateway to:
• the Station Bus (via a switch generally)

• the SCADA through IEC 60870-5-104 protocol) you need an RJ 45 male cable.
• In case of redundancy with ISaGRAF, a connection is required to the other Gateway via a dedicated
and specific card added on both Gateways (see GTW/EN IN)
The connections are per EIA/TIA T568A or EIA/TIA T568B with a patch (straight-through cable) for Station
Bus and SCADA and crossover cable for the redundancy cluster.
CO-4 GTW/EN CO/C57

Figure 1: RJ 45 connections
2.2 DB9 SERIAL CONNECTION

To connect the DS Agile Gateway to the modem dialling with the remote SCADA you will need a DB9 female
cable. On the male connector, the pin numbers are: 1 …5 (upper row), 6…9 (lower row):
1 2 3 4 5
DCD RxD TxD DTR GND
6 7 8 9
DSR RTS CTS RI
Figure 2: Serial DB9 male connector
GTW/EN CO/C57 CO-5

To connect a SCADA simulator or a Network spy you can use a null modem cable plugged to a serial port
wired as follows:
Figure 3: Null modem wiring
2.3 DB26 SERIAL CONNECTION

For protocol T101, the gateway may be equipped with a board ACKSYS MCXPCI/570-2 which has two
DB26 female connectors.
9 1
18 16 19 10
Figure 4: Serial female DB26 connection
This serial port connector assignment is given in the following table:

Pin nb Signal Mnemonic Direction
1 P.G Protective Ground
2 TxD Transmit Data Output (A)
3 RxD Receive Data Input (A)
4 RTS Request To Send Output (A)
5 CTS Clear To Send Input (A)
6 DSR Data Set Ready Input (A)
7 GND
8 DCD Data Carrier Detect Input (A)
9 RxClkIn Receive Clock Input (B)
10 DCD Data Carrier Detect Input (B)
CO-6 GTW/EN CO/C57

Pin nb Signal Mnemonic Direction

11 TxClkOut Transmit Clock Output (B)
12 TxClkIn Transmit Clock Input (B)
13 CTS Clear To Send Input (B)
14 TxD Transmit data Output (B)
15 TxClkIn Transmit Clock Input (A)
16 RxD Receive Data Input (B)
17 RxClkIn Receive Clock Input (A)
18 DSR Data Set Ready Input (B)
19 RTS Request To Send Output (B)
20 DTR Data Terminal ready Output (A)
21 RI Ring Indicator Input (B)
22 RI Ring Indicator Input (A)
23 DTR Data Terminal ready Output (B)
24 TxClkOut Transmit Clock Output (A)
25 +5V (used in RS485 mode for line polarization)
26 GND
2.4 POWER SUPPLY CONNECTORS

PC type Voltage Connector
Industrial PC 100-240 VAC with auto-switching IEC type
Fanless Embedded PC 24VDC Rectangular with 3 terminals
GTW/EN CO/C57 CO-7

CO-8 GTW/EN CO/C57

COMMUNICATIONS
GTW/EN CT/C57
DS Agile Gateway & WACU Communications
Contents
1 SCOPE OF THE DOCUMENT 5
2 60870-5-101 IEC:1995-> 2001 EDITION 2 – INTEROPERABILITY 6

2.1 System or device 6
2.2 Network configuration (Network-specific parameter) 6
2.3 Physical layer (Network-specific parameter) 6
2.4 Link layer (Network-specific parameter) 7
2.5 Protocol Requirements 8
2.5.1 Class 1 data 8
2.5.2 Class 2 data 8
2.6 Application Functions 8
2.7 Application layer 12
2.7.1 Selection of standard ASDUs 13
2.8 Basic application functions 17
3 IEC 60870-5-104 PROFILE - INTEROPERABILITY 20

3.1 System or device 20
3.2 Physical layer (Network-specific parameter) 20
3.3 Link layer (Network-specific parameter) 21
3.4.1 Event 22
3.4.2 Static 22
3.5 Application layer 22
3.5.1 Selection of standard ASDUs 23
3.6 Basic application functions 28
3.7 SOE file management 32
3.8 Disturbance file management 33
4 MODBUS PROFILE 34
4.1 Introducing MODBUS 34
4.1.1 Device address field 34
4.1.2 Function code field 34
4.1.3 Data field 34
4.1.4 Error check field 35
4.2 Slave responses 35
4.2.1 When the slave answers 35
4.2.2 Exception Responses Codes 35
4.3 Serial transmission mode 36
4.4 MODBUS Functions 36
4.4.1 Supported functions 36
4.4.2 General format of MODBUS functions 37
4.4.3 MODBUS Data Addresses 37
4.5 Function 01 / 02: Read Coil Status – Read Input Status 38
4.6 Function 03 / 04: Read Holding Registers / Input Registers 39
4.6.1 Signed normalised coding 39
4.6.2 Unsigned normalised coding 40
4.6.3 Natural coding 40
GTW/EN CT/C57 CT-1

Communications DS Agile Gateway & WACU
4.7 Function 05: Force Single Coil 40

4.8 Function 08: Diagnostic [Sub-function 0 only] 41
4.9 Function 15: Force Multiple Coils 41
5 DNP3 PROTOCOL 43
5.1 Profile 43
5.2 Implementation table 45
5.3 “On-line” Quality bit management: 49
6 OPC PROTOCOL 51
6.1 Implementation 51
6.2 OPC Standard layer 54
6.2.1 OPCServer object 54
6.2.2 OPCGroup object 56
6.3 OPC server Alstom specificities 58
6.3.1 Historisation mechanism 58
6.3.2 State inversion 58
6.3.3 Conversion of a double TS (system side) in two TS (OPC side) 58
6.3.4 Conversion of two simple TS (OPC side) in a double TC (system side) 58
7 IEC 61850-8-1 PROTOCOL 59

7.1 General 59
7.2 ACSI basic conformance statement 59
7.3 ACSI models conformance statement 60
7.4 ACSI service conformance statement 61
8 COMMUNICATIONS WITH IEDS: LEGACY T101 MASTER NETWORK 65

8.1 Master IEC 60870-5-101 profile 65
8.1.1 System or device 65
8.1.2 Network configuration 65
8.1.3 Physical layer 65
8.1.4 Link layer 66
8.1.5 Application layer 67
8.1.6 Basic application functions 71
8.3 Application Functions 75
9 COMMUNICATIONS WITH IEDS: LEGACY T104 MASTER NETWORK 77

9.1 Master IEC 60870-5-104 profile 77
9.1.1 Application layer 77
9.1.2 Basic application functions 81
9.1.3 Limits 85
9.2 System functions 85
9.3 Application functions 87
9.3.1 Data received from IEDs 87
9.3.2 Data sent to IEDs 87
9.4 Redundancy management 88
9.4.1 Nominal behaviour 89
CT-2 GTW/EN CT/C57

9.4.2 Behaviour in case of failure 92

9.4.3 Principles and rules 96
GTW/EN CT/C57 CT-3

CT-4 GTW/EN CT/C57

1 SCOPE OF THE DOCUMENT

This document describes the various standard communications protocols implemented in the DS Agile
Gateway.
DS Agile Gateway supports three different types of communications:
• SCP Communications: communications over Ethernet IEC 61850-8-1

• SCADA Communications:
communications with an upper level SCADA system over serial protocols
(IEC 60870-5-101, MODBUS, DNP3)
communications with an upper level SCADA system over IP protocols
(IEC 60870-5-104,OPC, IEC 61850-8-1)
• Communications with legacy IEDs (IEC 60870-5-101 master and IEC 60870-5-104 master)
GTW/EN CT/C57 CT-5

2 60870-5-101 IEC:1995-> 2001 EDITION 2 – INTEROPERABILITY

This companion standard presents sets of parameters and alternatives from which subsets have to be
selected to implement particular telecontrol systems. Certain parameter values, such as the number of bytes
in the COMMON 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 in command and in monitor direction allow the specification of the complete set or
subsets, as appropriate for given applications. This clause summarises the parameters of the previous
clauses to facilitate a suitable selection for a specific application. If a system is composed of equipment
stemming from different manufacturers it is necessary that all partners agree on the selected parameters.
The selected parameters should be filled up (N => S).
Note 1:
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.
To simplify the PID, we use the following conventions:

N Not supported
S Supported
C This is configurable
T The time-tag is not sent to the host (accepted but not used).
R Could be received, but not managed.
2.1 SYSTEM OR DEVICE

N System definition
N Controlling station definition
S Controlled station definition (Slave)
2.2 NETWORK CONFIGURATION (NETWORK-SPECIFIC PARAMETER)

S Point-to-point S Multipoint-party line
S Multiple point-to-point S Multipoint-star
2.3 PHYSICAL LAYER (NETWORK-SPECIFIC PARAMETER)

Transmission speed (control direction):
Unbalanced interchange Unbalanced interchange
circuit V.24/V.28 circuit V.24/V.28 Balanced interchange
circuit X.24/X.27, V35
Standard Recommended if >1 200 bit/s
S 100 bit/s S 2 400 bit/s N 2 400 bit/s
S 1 200 bit/s S 38 400 bit/s N 38 400 bit/s
N 56 000 bit/s
S 64 000 bit/s
CT-6 GTW/EN CT/C57

Transmission speed (monitor direction):

Unbalanced interchange Unbalanced interchange
circuit V.24/V.28 circuit V.24/V.28 Balanced interchange
circuit X.24/X.27, V35
S 1 200 bit/s S 38 400 bit/s N 38 400 bit/s
N 56 000 bit/s
S 64 000 bit/s
2.4 LINK LAYER (NETWORK-SPECIFIC PARAMETER)

(Network-specific parameter, all options that are used should be filled up (N => S). 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.
Link transmission procedure Address field of the link
S Balanced transmission S Not present (balanced transmission only)
S Unbalanced transmission S One octet
S Two octets
N Structured
S Unstructured
Frame length
255 (configurable) Maximum length L (number of bytes control direction)
255 (configurable) Maximum length L (number of bytes monitor direction)
Repetition parameters
S Number of repetitions on non acknowledge frame
S Maximum time between information frame and controlling station acknowledgement.
GTW/EN CT/C57 CT-7

2.5 PROTOCOL REQUIREMENTS
2.5.1 CLASS 1 DATA

The following types of information are to be configured at the controlled station to be Class 1:
S Single point information with or without time tag (on change)
S Double point information with or without time tag (on change)
S Step position information with or without time tag (on change)
S Measured value, normalised with or without time tag (on change)
S Measured value, scaled with or without time tag (on change)
S Measured value, floated with or without time tag (on change)
S Integrated totals with or without time tag (on change)
S Time messages
S All command responses (ACT_CONF, and ACT_TERM)
2.5.2 CLASS 2 DATA

The following types of information are be configured at the controlled station to be Class 2:
S Single point information (GI scan, or BackGroundScan cycle)
S Double point information (GI scan, or BackGroundScan cycle)
S Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
S Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
S Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
S Step position values (GI scan, or BackGroundScan cycle)
S Integrated totals (Counter GI scan)
2.6 APPLICATION FUNCTIONS

The following IEC-60870-5-5 standard application processes are required to be supported.
Station Initialisation
Depending on the value of register key GI_Compulsory the station initialisation is done by two different
ways:
• if GI_Compulsory is set to 1 the station initialisation consists of a reset of the communications link,
followed by a general interrogation of the controlled station
• if GI_Compulsory is set to 0 the station initialisation consists of only a reset of the communications
link
Once this initialisation sequence is performed the controlling station can start the polling for data
report.
Communications failure
In balanced mode, a communication failure occurs when:
• SCADA does not acknowledge a data emission within specific time after 3 repetitions.
• No Test Link frame is received within specific time
In unbalanced mode, a communication failure occurs when:
CT-8 GTW/EN CT/C57

Communications to the controlled station must be re-initialised by the controlling station where the frame
repeat process has completed without successfully transmitting the frame (i.e.: the frame time-out period
times the number of repeats).
If the controlled station fails to communicate with the controlling station then the controlling station should
perform a communications system initialisation for that controlled station.
Controlled station failure
If its register key Send_init_asdu_70 is set to 1 the controlled station shall indicate to the controlling station
that it has initialised by sending a frame indicating End of Initialisation (ASDU 70) with a Cause of
Initialisation (COI) field, which will identify the reason for the initialisation.
Data Acquisition by Polling
The default for all analogue values shall be reporting as Class 2 data (COT=1, periodic, cyclic, or COT = 2,
BackgroundScan cyclic).
Values returned as Class 2 data do not have a time tag (since they are constantly repeated).
The controlled station may return Class 1 data in response to a Class 2 request if no Class 2 data is
available and Class 1 data is awaiting transmission. This is configurable in Registry.
At the controlled station, if a request for Class 2 data is received and no data is available a negative
response, data not available, shall be returned to the controlling Station. The negative response may be a
fixed length frame (FC=9) or the Single Control Character (E5), which in this case is treated as a NACK.
Normal Acquisition of Events
The default for all status changes are reported as Class 1 data (COT=3, spontaneous).
Values returned as Class 1 data shall have a time tag (either CP24Time2a, or CP56Time2a).
Status changes at the controlled station shall cause the ACD bit to be set in the next Class 1 or Class 2 data
response. The controlling station shall respond to ACD set by inserting a scan for Class 1 (spontaneous)
data as the next scan.
The response to a Class 1 data request shall also have the ACD bit set if more Class 1 data is awaiting
transmission. In this case a further scan for Class 1 data shall be scheduled by the controlling station.
Abnormal Acquisition of Events
At the controlled station, if a request for Class 1 data is received and no data is available an error should be
raised and a negative response, data not available, returned to the controlling Station. The negative
response shall be a fixed length frame (FC=9) or the single Control Character (E5), which in this case is
treated as a NACK.
At the controlling station, if a response to a scan for Class 1 data indicates no data is available an error shall
be raised and scanning returned to Class 2 data requests.
General Interrogation
The GI returns the current status information directly from the Controlled station database.
If register key timetag_in_GI is set to 0 time tags are not used for data items returned as part of the GI
response. if this register key is set to 1 DI and AI are time-tagged.
The GI groups are supported so, these will be set up in the database and each of the (up to 16) groups shall
be requested/reported individually.
Synchronisation
Class 1 data can be time-tagged with the 3 bytes time-stamp (CP24Time2a), giving minutes and
milliseconds within the hour, or with the 7 bytes time-stamp (CP56Time2a), giving minutes and milliseconds
within the hours, day, month, year. The format of time-stamp can be defined, for all class1 data, in
configuration.
The invalid bit in the time-stamp is set when the time source is not available.
GTW/EN CT/C57 CT-9

If its register key Inhibition_Clock_Synchro is set to 0 the controlled station reports its change of hour by
sending a clock synchronisation message (ASDU 103) to the controlling station, as Class 1 data, with a
cause of transmission spontaneous (3). If this register key is set to 1 no clock synchronisation message is
sent.
Command transmission
All control/set point commands shall be Select before Execute, or Direct Execute.
For only the set point commands: Activation termination (C_SE_ACTTERM) shall be returned to the
controlling station to signal the end of a control sequence. This is configurable in Registry.
For only the control commands: Activation termination is returned to the controlling station to signal the end
of a control sequence. This isn’t configurable in Registry.
The QU field of the Qualifier of Command shall be set to zero (0), no additional definition. Short Pulse Long
duration, Long Pulse long duration are managed at bay-computer level.
Test procedure
A test command may be issued by the controlling station to ensure the availability of the communications link
and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled station mirrors the
test command, on the link from which it was received, with a cause of transmission indicating activation
confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission indicating
negative activation confirmation.
SBMC mode
Suppressed state does not exist in T101. So when a bay switches to SBMC mode, the C26x will tag the data
with “Substituted” state with a configured value.
Redundancy
Both devices have 3 redundancy types.
1 Line Redundancy – e.g. – 2 lines for the one protocol
For Gateway, Switch over on received frame:
The switch over from the active link to the passive link is performed when a frame is
received.
2 Protocol Redundancy * – e.g. – same protocol on the 2 devices. Events are synchronised at the
connection of the controlling station.
3 Equipment Redundancy – e.g. – 2 apparatus with the same data. Events are synchronised on SBUS
*only available in multi-rack mode
In all cases, only controlling station decides which line, protocol or equipment to use.
CT-10 GTW/EN CT/C57

Packed mode Flag SQ

The flags SQ are used to decrease the passband in monitor direction for data without time-tagging with
COT= 1, 2 and 20 to 36.
Each ASDU contains the type of data (SPS/DPS/TM float/…) the frame conveys the value and quality of.
Several data can be conveyed in the same frame:
Example:
68 0c 0c 68 08 01 01 02 14 01 07 00 08 01 09 00 xx yy
68 0c 0c 68
08 Control byte
01 Link Address
01 ASDU1 (Single-point information without time tag)
02 Number of objects = 2 DI, SQ=0
14 COT = 20 (general interrogation)
01 Common address
07 DI 7 (Information Object Address)
00 state OFF, Valid
09 DI 9
00 state OFF, Valid
[xx yy] checksum and stop byte
In SCE, you must map separately the various types of datapoints. Create type-related
slices with spare addresses to NEVER intertwine a data address stretch with another
type.
If the Gateway detects another type of data interspersed, some data might be lost.
In the registry, a flag SQ can be configured for each type of datapoint. Refer to the GTW/EN MF chapter.
Flag SQ = 0 (default value): the frame is transferred as usual.
Flag_SQ = 1: the frame includes only the first Information Object Address
Max Gaps_DP is the maximum number of address holes allowed. It can be configured in the registry from 0
to 100. This is a way to adjust the passband.
If Max Gaps_DP = 0 (default value) and the addresses are not contiguous, the frames will always be split by
segments with contiguous addresses.
Example with Max Gaps_DP = 0:
68 0c 0c 68 08 01 01 02 14 01 07 00 01 xx yy
68 0c 0c 68
08 Control byte
01 Link Address
01 Common address
00 state OFF, Valid
68 0c 0c 68 08 01 01 02 14 01 09 00 xx yy
68 0c 0c 68
08 Control byte
01 Link Address
GTW/EN CT/C57 CT-11


01 Common address
00 state OFF, Valid
If Max Gaps_DP > 0, the potential holes are taken care of by adding padding in place of them if the number
of holes in the address range is lesser than Max_Gaps_DP. If it is larger, the frame is split as if Max
Gaps_DP = 0.
Example with Max Gaps_DP = 2:
68 0c 0c 68 08 01 01 03 14 01 07 00 01 00 xx yy
68 0c 0c 68
08 Control byte
01 Link Address
01 Common address
00 state OFF, Valid
01 state ON, Valid for DI 8 (padding)
00 state OFF, Valid for DI 9
Flag SQ = 2:
If the Gateway detects a hole in the address stretch, then the frame is split and the flag SQ is set. All frames
will be sent with flag SQ=1 even if only one datapoint is sent in the frame.
2.7 APPLICATION LAYER

Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively in this
companion standard.
Common address of ASDU
(System-specific parameter)
The address field of the link and the common address of ASDU could have a different number of bytes
S One octet S Two octets
Information object address

S One octet S Structured
S Two octets S Unstructured
S Three octets
Cause of transmission
S One octet S Two octets (with originator address)
CT-12 GTW/EN CT/C57

2.7.1 SELECTION OF STANDARD ASDUS

Process information in monitor direction
(Station-specific parameter)
S <1>: = Single-point information M-SP-NA-1
S <2>: = Single-point information with time tag M-SP-TA-1
S <3>: = Double-point information M-DP-NA-1
S <4>: = Double-point information with time tag M-DP-TA-1
S <5>: = Step position information M-ST-NA-1
S <6>: = Step position information with time tag M-ST-TA-1
S <7>: = Bit-string of 32 bit M-BO-NA-1
S <8>: = Bit-string of 32 bit with time tag M-BO-TA-1
S <9>: = Measured value, normalised value M-ME-NA-1
S <10>: = Measured value, normalised value with time tag M-ME-TA-1
S <11>: = Measured value, scaled value M-ME-NB-1
S <12>: = Measured value, scaled value with time tag M-ME-TB-1
S <13>: = Measured value, short floating point value M-ME-NC-1
S <14>: = Measured value, short floating point value with time tag M-ME-TC-1
S <15>: = Integrated totals M-IT-NA-1
S <16>: = Integrated totals with time tag M-IT-TA-1
N <17>: = Event of protection equipment with time tag M-EP-TA-1
S <18>: = Packed starts events of protection equipment with time tag M-EP-TB-1
S <19>: = Packed output circuit information of protection equipment with time tag M-EP-TC-1
N <20>: = Packed single-point information with status change detection M-PS-NA-1
N <21>: = Measured value, normalised value without quality descriptor M-ME-ND-1
Process information in monitor direction with the Extension of time tag

S <30>: = Single-point information with time tag CP56Time2a M-SP-TB-1
S <31>: = Double-point information with time tag CP56Time2a M-DP-TB-1
S <32>: = Step position information with time tag CP56Time2a M-ST-TB-1
S <33>: = Bit-string of 32 bit with time tag CP56Time2a M-BO-TB-1
S <34>: = Measured value, normalised value with time tag CP56Time2a M-ME-TD-1
S <35>: = Measured value, scaled value with time tag CP56Time2a M-ME-TE-1
S <36>: = Measured value, short floating point value, time tag CP56Time2a M-ME-TF-1
S <37>: = Integrated totals with time tag CP56Time2a M-IT-TB-1
N <38>: = Event of protection equipment with time tag CP56Time2a M-EP-TD-1
S <39>: = Packed start event of protection equipment, time tag CP56Time2a M-EP-TE-1
S <40>: = Packed output circuit information of protection equipment with time tag CP56Time2a M-EP-TF-1
Process information in control direction

(station-specific parameter)
GTW/EN CT/C57 CT-13

S <45>: = Single command C-SC-NA-1

S <46>: = Double command C-DC-NA-1
S <47>: = Regulating step command C-RC-NA-1
S <48>: = Set point command normalised value C-SE-NA-1
S <49>: = Set point command scaled value C-SE-NB-1
S <50>: = Set point command, short floating point value C-SE-NC-1
N <51>: = Bit-string of 32 bit C-BO-NA-1
System information in monitor direction

S <70>: = End of initialisation M-EI-NA-1
System information in control direction

S <100>: = Interrogation commands C-IC-NA-1
S <101>: = Counter interrogation command C-CI-NA-1
S <102>: = Read command C-RD-NA-1
S <103>: = Clock synchronisation command C-CS-NA-1
S <104>: = Test command C-TS-NA-1
C <105>: = Reset process command C-RP-NA-1
Note:
Following a Reset Process command, the controlled station has two possible behaviours depending on register key
Reset_Process_Hard:
if Reset_Process_Hard is set to 0 only the gateway restarts (soft restart)

if Reset_Process_Hard is set to 1 the PC restarts (hard restart)
N <106>: = Delay acquisition command C-CD-NA-1
Parameter in control direction

N <110>: = Parameter of measured value, normalised value P-ME-NA-1
N <111>: = Parameter of measured value, scaled value P-ME-NB-1
N <112>: = Parameter of measured value, short floating point value P-ME-NC-1
N <113>: = Parameter activation P-AC-NA-1
File transfer
CT-14 GTW/EN CT/C57

S <120>: = File ready F-FR-NA-1

S <121>: = Section ready F-SR-NA-1
S <122>: = Call directory, select file, call file, call section F-SC-NA-1
S <123>: = Last section, last segment F-LS-NA-1
S <124>: = Ack file, ack section F-AF-NA-1
S <125>: = Segment F-SG-NA-1
S <126>: = Directory F-DR-TA-1
Special use
(private range)
N <136>: = Data base version M-DB-NA-1
N <137>: = Regulating delay command C-RC-NB-1
Type identifier and cause of transmission assignments

(station-specific parameters)
X Mark type identification/cause of transmission combinations: ‘X’ if used
Shaded boxes are not required
Blank = function or ASDU is not used
. Required in 1995 standard, suppressed in 2000.
Type
C O T
ID
20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45* 46 47
..36 ..41
<1> M_SP_NA_1 X X X X X X
<2> M_SP_TA_1 X X X X X
<3> M_DP_NA_1 X X X X X X
<4> M_DP_TA_1 X X X X X
<5> M_ST_NA_1 X X X X X X
<6> M_ST_TA_1 X X X X X
<7> M_BO_NA_1 X X X
<8> M_BO_TA_1 . .
<9> M_ME_NA_1 X X X X X
<10> M_ME_TA_1 X X X
<11> M_ME_NB_1 X X X X X
<12> M_ME_TB_1 X X X
<13> M_ME_NC_1 X X X X X
<14> M_ME_TC_1 X X X
<15> M_IT_NA_1 X X
<16> M_IT_TA_1 X X
<17> M_EP_TA_1
<18> M_EP_TB_1 X
<19> M_EP_TC_1 X
<20> M_PS_NA_1
<21> M_ME_ND_1
GTW/EN CT/C57 CT-15

Type
C O T
ID
<30> M_SP_TB_1 X X X X
<31> M_DP_TB_1 X X X X
<32> M_ST_TB_1 X X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X X
<35> M_ME_TE_1 X X
<36> M_ME_TF_1 X X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1 X
<40> M_EP_TF_1 X
<45> C_SC_NA_1 X X X X X X
<46> C_DC_NA_1 X X X X X X
<47> C_RC_NA_1 X X X X X X
<48> C_SE_NA_1 X X X X X X
<49> C_SE_NB_1 X X X X X X
<50> C_SE_NC_1 X X X X X X
<51> C_BO_NA_1
<70> M_EI_NA_1 X
<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 X
<103> C_CS_NA_1 X X X X
<104> C_TS_NA_1 X X X
<105> C_RP_NA_1 X X X
<106> C_CD_NA_1
<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 X X
<123> F_LS_NA_1 X X
<124> F_AF_NA_1 X X
<125> F_SG_NA_1 X X
<126> F_DR_TA_1 X X X
* COT <45>:= Unknown Cause of Transmission
CT-16 GTW/EN CT/C57

2.8 BASIC APPLICATION FUNCTIONS

Station initialisation
S Remote initialisation
(Between Reset User ASDU’s).
Cyclic data transmission
S Cyclic data transmission
(It is the same cyclic for all data).
Read procedure
S N Read procedure
Spontaneous transmission
S Spontaneous transmission
Link state between Controlling and Controlled station

S Management of the COM lost (Problem detecting on the link)
S Management of the COM recovering (Problem not detecting on the link)
General interrogation
(System or station-specific parameter)
S Global
S Group 1 S Group 7 S Group 13
S Group 5 S Group 11
S Group 6 S Group 12 Addresses per group have to be defined
Counter General interrogation

S global
S group 1 S group 3
S group 2 S group 4
Clock synchronisation
C Clock synchronisation
GTW/EN CT/C57 CT-17

Notes:
The controlling station cannot synchronize the system (includes controlled station).
When the controlling station sends to controlled station a clock synchronisation, the clock synchronisation
response is positive (if register key ack_pos_clock_synchro equals 1) or negative (if register key
ack_pos_clock_synchro equals 0).
(Object-specific parameter)
S Direct command transmission S Select and execute command
S Direct set point command transmission S Select and execute set point command
C C-SE ACTTERM used
S No additional definition
N Short pulse duration (duration determined by a system parameter in the outstation)
N Long pulse duration (duration determined by a system parameter in the outstation)
N Persistent output
Transmission of integrated totals

(Station or object-specific parameter)
S Mode A: local freeze with spontaneous.
N Mode B: local freeze with counter.
S Mode C: freeze and transmit by counter interrogation.
N Mode D: freeze by counter interrogation command, frozen values reported.
S Counter read S General request counter

S Counter freeze without reset S Request counter group 1
S Counter freeze with reset S Request counter group 2
S Counter reset S Request counter group 3
S Request counter group 4
Note : The status flags are only modified when the value is determined. This may be in response to a counter
interrogation command or in response to an automatic internal function that performs the counter freeze or freeze and
reset command.
Parameter loading
N Threshold value
N Smoothing factor
N Low limit for transmission of measured value
N High limit for transmission of measured value
Parameter activation
N Act/Deactivation of persistent cyclic or periodic transmission of the addressed object
CT-18 GTW/EN CT/C57

Test procedure
S Test procedure
File transfer
File transfer in monitor direction
S Transparent file (for disturbance files)
N Transmission of disturbance data of protection equipment
S Transmission of sequences of events
N Transmission of sequences of recorded analogue values
File transfer in control direction

N Transparent file
Background scan
S Background scan
Acquisition of transmission delay

N Acquisition of transmission delay
Management events priorities
S Digital Inputs, Step-position, Analogues Inputs and Integrated Totals, management events priorities.
See: T101 standard Amendment 2 §7.2.2.2
GTW/EN CT/C57 CT-19

3 IEC 60870-5-104 PROFILE - INTEROPERABILITY

This companion standard presents sets of parameters and alternatives from which subsets have to be
selected to implement particular telecontrol systems. Certain parameter values, such as the choice of
“structured” or “unstructured” fields of the INFORMATION OBJECT ADDRESS of ASDU 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 in command and in monitor direction
allow the specification of the complete set or subsets, as appropriate for given applications. This clause
summarises the parameters of the previous clauses to facilitate a suitable selection for a specific application.
If a system is composed of equipment stemming from different manufacturers it is necessary that all partners
agree on the selected parameters.
Paragraph in grey are those which are not applicable for the IEC 60870-5-104 profile.
The selected parameters should be filled up (N => S).
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.
To simplify the PID , we use the following conventions:
N Not supported
S Supported
C This is configurable
R Could be received, but not managed.
3.1 SYSTEM OR DEVICE

N System definition
N Controlling station definition (Master)
S Controlled station definition (Slave)
Network configuration (Network-specific parameter)
N Point-to-point N Multipoint-party line
N Multiple point-to-point N Multipoint-star
3.2 PHYSICAL LAYER (NETWORK-SPECIFIC PARAMETER)

Transmission speed (control direction):
Unbalanced interchange circuit
Unbalanced interchange circuit V.24/V.28 Balanced interchange circuit
V.24/V.28
Recommended if >1 200 bit/s X.24/X.27, V35
Standard
N 100 bit/s N 2 400 bit/s N 2 400 bit/s
N 1 200 bit/s N 38 400 bit/s
N 56 000 bit/s
N 64 000 bit/s
CT-20 GTW/EN CT/C57

Transmission speed (monitor direction):

Unbalanced interchange circuit Unbalanced interchange circuit
V.24/V.28 V.24/V.28 Balanced interchange circuit
X.24/X.27, V35
N 1 200 bit/s N 38 400 bit/s
N 56 000 bit/s
N 64 000 bit/s
3.3 LINK LAYER (NETWORK-SPECIFIC PARAMETER)

(Network-specific parameter, all options that are used should be filled up (N => S).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.)
companion standard.
N Balanced transmission N Not present (balanced transmission only)
N Unbalanced transmission N One octet
N Two octets
N Structured
N Unstructured
Frame length
_255_ Maximum length L (number of bytes)
When using an unbalanced link layer, the following ASDU types are returned in class 2 messages (low
priority) with the indicated causes of transmission:
N The standard assignment of ASDUs to class 2 messages is used as follows:
Type Identification Cause of transmission
9,11,13,21 <1>
N A special assignment of ASDUs to class 2 messages is used as follows:

Type Identification Cause of transmission
1,3,5 <20> to <41>
Note: In response to a class 2 poll, a controlled station prevent the controlling station with ACD parameter, when
there is no class 2 data available.
GTW/EN CT/C57 CT-21

3.4.1 EVENT
The following types of information are to be configured at the controlled station to be Event:
S Single point information with or without time tag (on change)
S Double point information with or without time tag (on change)
S Step position information with or without time tag (on change)
S Measured value, normalised with or without time tag (on change)
S Measured value, scaled with or without time tag (on change)
S Measured value, floated with or without time tag (on change)
S Integrated totals with or without time tag (on change)
3.4.2 STATIC
The following types of information are to be configured at the controlled station to be Static:
S Single point information (GI scan, or BackGroundScan cycle)
S Double point information (GI scan, or BackGroundScan cycle)
S Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
S Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
S Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
S Step position values (GI scan, or BackGroundScan cycle)
S Integrated totals (Counter GI scan)
3.5 APPLICATION LAYER

companion standard.
The address field of the link and the common address of ASDU could have a different number of bytes
N One octet S Two octets

N One octet S Structured
N Two octets S Unstructured
S Three octets
N One octet S Two octets (with originator address)
CT-22 GTW/EN CT/C57

Length of APDU
The maximum length of APDU is 253 (fixed)
3.5.1 SELECTION OF STANDARD ASDUS

S <1>: = Single-point information M-SP-NA-1
N <2>: = Single-point information with time tag M-SP-TA-1
S <3>: = Double-point information M-DP-NA-1
N <4>: = Double-point information with time tag M-DP-TA-1
S <5>: = Step position information M-ST-NA-1
N <6>: = Step position information with time tag M-ST-TA-1
N <7>: = Bit-string of 32 bit M-BO-NA-1
N <8>: = Bit-string of 32 bit with time tag M-BO-TA-1
S <9>: = Measured value, normalised value M-ME-NA-1
N <10>: = Measured value, normalised value with time tag M-ME-TA-1
S <11>: = Measured value, scaled value M-ME-NB-1
N <12>: = Measured value, scaled value with time tag M-ME-TB-1
S <13>: = Measured value, short floating point value M-ME-NC-1
N <14>: = Measured value, short floating point value with time tag M-ME-TC-1
S <15>: = Integrated totals M-IT-NA-1
N <16>: = Integrated totals with time tag M-IT-TA-1
N <17>: = Event of protection equipment with time tag M-EP-TA-1
N <18>: = Packed starts events of protection equipment with time tag M-EP-TB-1
N <19>: = Packed output circuit information of protection equipment with time tag M-EP-TC-1
N <20>: = Packed single-point information with status change detection M-PS-NA-1
N <21>: = Measured value, normalised value without quality descriptor M-ME-ND-1
Process information in monitor direction with the Extension of time tag

S <30>: = Single-point information with time tag CP56Time2a M-SP-TB-1
S <31>: = Double-point information with time tag CP56Time2a M-DP-TB-1
S <32>: = Step position information with time tag CP56Time2a M-ST-TB-1
N <33>: = Bit-string of 32 bit with time tag CP56Time2a M-BO-TB-1
S <34>: = Measured value, normalised value with time tag CP56Time2a M-ME-TD-1
S <35>: = Measured value, scaled value with time tag CP56Time2a M-ME-TE-1
S <36>: = Measured value, short floating point value, time tag CP56Time2a M-ME-TF-1
S <37>: = Integrated totals with time tag CP56Time2a M-IT-TB-1
N <38>: = Event of protection equipment with time tag CP56Time2a M-EP-TD-1
S <39>: = Packed start event of protection equipment, time tag CP56Time2a M-EP-TE-1
Packed output circuit information of protection equipment with time tag
S <40>: = M-EP-TF-1
CP56Time2a
GTW/EN CT/C57 CT-23


S <45>: = Single command C-SC-NA-1
S <46>: = Double command C-DC-NA-1
S <47>: = Regulating step command C-RC-NA-1
S <48>: = Set point command normalised value C-SE-NA-1
S <49>: = Set point command scaled value C-SE-NB-1
S <50>: = Set point command, short floating point value C-SE-NC-1
N <51>: = Bit-string of 32 bit C-BO-NA-1
S <58>: = Single command with time tag CP56Time2a C_SC_TA_1
S <59>: = Double command with time tag CP56Time2a C_DC_TA_1
S <60>: = Regulating step command with time tag CP56Time2a C_RC_TA_1
S <61>: = Set point command normalized value with time tag CP56Time2a C_SE_TA_1
S <62>: = Set point command scaled value with time tag CP56Time2a C_SE_TB_1
S <63>: = Set point command short floating point value with time tag CP56Time2a C_SE_TC_1
N <64>: = Bitstring of 32 bits with time tag CP56Time2a C_BO_TA_1
Note:
Time tag command (ASDU 58 to 63) are managed as standard command (ASDU 45 to 50), i.e. the time tag is not
used.

S <70>: = End of initialisation M-EI-NA-1

S <100>: = Interrogation commands C-IC-NA-1
S <101>: = Counter interrogation command C-CI-NA-1
S <102>: = Read command C-RD-NA-1
R <103>: = Clock synchronisation command C-CS-NA-1
N <104>: = Test command C-TS-NA-1
C <105>: = Reset process command C-RP-NA-1
N <106>: = Delay acquisition command C-CD-NA-1
S <107>: = Test command with time tag CP56time2a C-TS-TA-1
Note applicable for Gateway PC:

Following Reset Process, the controlled station has two possible behaviours (according to configurable
parameter in the Registry):
the first: only the controlling station restart (soft restart )
the second: the completely PC restart (hard restart )
CT-24 GTW/EN CT/C57


N <110>: = Parameter of measured value, normalised value P-ME-NA-1
N <111>: = Parameter of measured value, scaled value P-ME-NB-1
N <112>: = Parameter of measured value, short floating point value P-ME-NC-1
N <113>: = Parameter activation P-AC-NA-1
File transfer
S <120>: = File ready F-FR-NA-1
S <121>: = Section ready F-SR-NA-1
S <122>: = Call directory, select file, call file, call section F-SC-NA-1
S <123>: = Last section, last segment F-LS-NA-1
S <124>: = Ack file, ack section F-AF-NA-1
S <125>: = Segment F-SG-NA-1
S <126>: = Directory F-DR-TA-1
File transfer is only implemented in computer gateway.

Special use
(private range)
N <136>: = Data base version M-DB-NA-1
N <137>: = Regulating delay command C-RC-NB-1

X Mark type identification/cause of transmission combinations: ‘X’ if used
Shaded boxes are not required
Type
C O T
ID
20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 44 45* 46 47
..36 ..41
<1> M_SP_NA_1 X X X X
<2> M_SP_TA_1
<3> M_DP_NA_1 X X X X
<4> M_DP_TA_1
<5> M_ST_NA_1 X X X X
<6> M_ST_TA_1
<7> M_BO_NA_1 X
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X X
<10> M_ME_TA_1
<11> M_ME_NB_1 X X X X X
GTW/EN CT/C57 CT-25

Type
C O T
ID
<12> M_ME_TB_1
<13> M_ME_NC_1 X X X X
<14> M_ME_TC_1
<15> M_IT_NA_1 X X
<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
<21> M_ME_ND_1
<30> M_SP_TB_1 X X
<31> M_DP_TB_1 X X
<32> M_ST_TB_1 X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X
<38> M_EP_TD_1
<39> M_EP_TE_1
<40> M_EP_TF_1
<45> C_SC_NA_1 X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1
<58> C_SC_TA_1 X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X
<64> C_BO_TA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X
<101> C_CI_NA_1 X X X X X
<102> C_RD_NA_1 X X X
<103> C_CS_NA_1
<104> C_TS_NA_1
<105> C_RP_NA_1 X X X X
<106> C_CD_NA_1
<107> C_TS_TA_1 X X X X
CT-26 GTW/EN CT/C57

Type
C O T
ID
<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
<121> F_SR_NA_1 X
<122> F_SC_NA_1 X* X X
<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
* COT <45>:= Unknown Cause of Transmission
Note: For ASDU 122 COT 5 is used only for Call Directory and COT 13 is used for all except Call Directory.
GTW/EN CT/C57 CT-27

3.6 BASIC APPLICATION FUNCTIONS

S Remote initialisation
(Between Reset User ASDU’s).
S Cyclic data transmission
(It’s the same cyclic for all data).
Read procedure
S Read procedure
S Spontaneous transmission
Double transmission of information objects with cause of transmission spontaneous

(station-specific parameter), each information is marked 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.
M_SP_NA_1, M_SP_TA_1, M_SP_TB_1 and
N Single point information
M_PS_NA_1
N Double point information M_DP_NA_1, M_DP_TA_1 and M_DP_TB_1
N Step position information M_ST_NA_1, M_ST_TA_1 and M_ST_TB_1
M_BO_NA_1, M_BO_TA_1 and M_BO_TB_1
N Bitstring of 32 bit
(if defined for a specific project)
M_ME_NA_1, M_ME_TA_1, M_ME_ND_1 and
N Measured value, normalized value
M_ME_TD_1
N Measured value, scaled value M_ME_NB_1, M_ME_TB_1 and M_ME_TE_1
N Measured value, short floating point number M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
CT-28 GTW/EN CT/C57

S Global
Information Object Addresses assigned to each
group must be shown in a separate table

S Global
S Group 1 S Group 3
S Group 2 S Group 4
N Clock synchronisation
S Direct command transmission S Select and execute command
S Direct set point command transmission S Select and execute set point command
S C-SE ACTTERM used
S No additional definition
N Short pulse duration (duration determined by a system parameter in the outstation)
N Long pulse duration (duration determined by a system parameter in the outstation)
N Persistent output

(Station or object-specific parameter)
S Mode A: local freeze with spontaneous.
S Mode B: local freeze with counter.
S Mode C: freeze and transmit by counter interrogation.
N Mode D: freeze by counter interrogation command, frozen values reported.
GTW/EN CT/C57 CT-29

S Counter read S General request counter

S Counter freeze without reset S Request counter group 1
S Counter freeze with reset S Request counter group 2
S Counter reset S Request counter group 3
S Request counter group 4
Note : The status flags are only modified when the value is determined. This may be in response to a counter
interrogation command or in response to an automatic internal function that performs the counter freeze or freeze and
reset command.
Parameter loading
N Threshold value
N Smoothing factor
N Low limit for transmission of measured value
N High limit for transmission of measured value
N Act/Desactivation of persistent cyclic or periodic transmission of the addressed object
Test procedure
S Test procedure
File transfer
File transfer in monitor direction
S Transparent file (only for disturbance file)
N Transmission of disturbance data of protection equipment
S Transmission of sequences of events
N Transmission of sequences of recorded analogue values

N Transparent file
Background scan
S Background scan
CT-30 GTW/EN CT/C57


N Acquisition of transmission delay

N Digital Inputs, Step-position, Analogues Inputs and Integrated Totals, management events priorities.
Definition of time outs

Parameter Default value Remarks Selected value
t0 30s Time out of connection establishment configurable
t1 15s Time out of send or test APDUs configurable
Time out for acknowledges in case of no data
t2 10s configurable
messages t2 < t1
Time out for sending test frames in case of a long
t3 20s configurable
idle state
Maximum range of values for all time outs: 1 to 255 s, accuracy 1 s
Maximum number of outstanding I format APDUs k and latest acknowledge
Maximum difference receive sequence number to
K 12 APDUs configurable
send state variable
Latest acknowledge after receiving w I-format
W 8 APDUs configurable
APDUs
Maximum range of values k: 1 to 255 APDUs, accuracy 1 APDU
Maximum range of values w: 1 to 255 APDUs, accuracy 1 APDU (Recommendation: w should not exceed
2/3 of k).
Portnumber
Parameter Value Remarks
Portnumber 2404 In all cases, but configurable in Registry
RFC 2200 suite

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.
S Ethernet 802.3
N Serial X.21 interface
N Other selection from RFC 2200
GTW/EN CT/C57 CT-31

3.7 SOE FILE MANAGEMENT

The number of SOE files, SOE104 files, in the directory defined by keys Drive+Path is limited. When the limit
is reached, the oldest file is replaced by a new one.
A SOE file creation is divided into 3 steps:
• until the maximum number of events in a SOE number is reached, events are stored in a xxxx.tmp file,
where xxxx is the IEC name (number in [1…65535],
• when the xxxx.tmp file is full, it is immediately in xxxx.tmp_ready,

• every 20 seconds the dll looks for .tmp_ready files: if any, it tries to rename it in .SOE104 file. If the file
couldn’t have been renamed, a new trial will be done
20 seconds later, an so on. In a normal processing, the only thing which prevents from renaming a
.tmp_ready in a .SOE104 is when the directory is full and the oldest file is being read by the SCADA
(i.e. this oldest file cannot be deleted and replaced by the new .tmp_ready). When the file is
successfully renamed, a “directory” ASDU is sent with Cause of Transmission = spontaneous.
When the dll starts, some .tmp and .tmp_ready can be present in the directory: .tmp will be then renamed in
.tmp_ready, and .tmp_ready will be renamed in .SOE104, as in the normal processing, but no “directory”
ASDU will be sent. However that may be, “directory” ASDU is never sent on dll starting.
“directory” ASDU is sent when a new SOE file appears in the directory or, if delete_file_after_read registry
key is set to 1, after a file deletion. “directory”. ASDU is not sent if the SCADA deletes a file explicitly with
ASDU F_SC_NA_1 (122).
IOA and file name management:
The directory content is ordered by increasing file name: base IOA generally fit to oldest file, which name
(=IEC name = a number) is the smallest (exception if files a 1, 2, 65534, 65535). Example (=”dir” ASDU
content):
• 25.SOE104 IOA = 1000
• 26.SOE104 IOA = 1001
• 27.SOE104 IOA = 1002
• 28.SOE104 IOA = 1003

If file 25.SOE104 is read and deleted, the “dir.” ASDU content will become:
• 26.SOE104 IOA = 1000
• 27.SOE104 IOA = 1001
• 28.SOE104 IOA = 1002

Or if file 25.SOE104 is replaced by 29.SOE104
• 26.SOE104 IOA = 1000
• 27.SOE104 IOA = 1001
• 28.SOE104 IOA = 1002
• 29.SOE104 IOA = 1003

Only one file can be transferred at a time, it’s not possible to read 2 files or more simultaneously: i.e if a file is
currently selected, a selection on a second file will be refused.
If a loss of communication with the SCADA occurs while a transfer is in progress, on communication
recovery the processing has to be resumed from the beginning.
A SOE104 file is a binary file, which contains only the ASDUs (no other information is present in the file).
CT-32 GTW/EN CT/C57

Caution:
If the directory is full, while the oldest file is locked by SCADA (file selected and not
acknowledged) it is not possible to rename the new .tmp_ready in .SOE104 in this
case, if this situation last a very long time, the number of .tmp_ready file can increase,
without limit. Such a situation should not happen if there’s no bug in the SCADA
For dll point of view there’s no correlation between the way a digital input is sent to SCADA, and the way it is stored in
the SOE file: an event, if configured as recorded, is always time tagged in the SOE file (even if in SCE user chooses to
sent it with no date to the SCADA).
3.8 DISTURBANCE FILE MANAGEMENT

Disturbances files are not produced by the gateway. The producer has just to put the files in the disturbance
directory, naming them 1.tmp_ready, 2. tmp_ready, etc … If file x.DIS104 is present when producer starts,
the first file s/he has to add is x+1.tmp_ready. Tmp_ready files are after managed exactly as SOE files,
except their extension is DIS104.
GTW/EN CT/C57 CT-33

4 MODBUS PROFILE
The purpose of this chapter is to describe the support of the MODBUS RTU protocol in the Alstom DS Agile
system for Gateway PC.
The MODBUS RTU protocol defines a message structure that controllers will recognise and use. It describes
the process a controller uses to request access to another device, how it will respond to requests from other
devices, and how errors will be detected.
4.1 INTRODUCING MODBUS

Controllers communicate using a master-slave scheme, in which only the master (called SCADA) can initiate
requests. The MODBUS gateway is a slave device that responds by supplying the requested data to the
master.
Transmission mode used is the MODBUS RTU. Queries and replies have the same format on a master-
slave query-response cycle:
Query message from Server Response message from Slave
Function code Function code
Eight-bit Data bytes Eight-bit data bytes
Error check Error check
4.1.1 DEVICE ADDRESS FIELD

The device address field of a message frame contains eight bits. Valid slave device addresses in queries are
in the range 0 – 247, but individual slave devices are assigned addresses in the range 1- 247 and address 0
is reserved for broadcast operations.
The device address field of a message frame always identifies a slave (slave destination in master to slave
queries and slave source in slave to master responses).
If the gateway receives a frame with a broadcast device address, no reply is returned.
If the gateway receives a frame with a not expected device address, no reply is returned.
4.1.2 FUNCTION CODE FIELD

The function code field of a message frame contains eight bits. Valid codes are in the range of 1-255.
In master to slave queries, the function code identifies the operation that is to be executed by the slave.
In slave to master responses, the function code is used to indicate either a normal (error-free) response or a
failure of the operation execution (called an exception response).
For a normal response, the slave simply echoes the original function code.
For an exception response, the slave returns a code that is equivalent to the original function code with its
MSB set to 1. In addition to the modification of the function code the slave places a unique code into the data
field of the response message, which identifies the reason for the exception.
4.1.3 DATA FIELD

The data field of a message frame is constructed using sets of two hexadecimal digits, in the range of 00h to
FFh.
In master to slave queries, the data field contains additional information to be used by the slave to execute
the operation defined by the function code.
In slave to master responses, the data field contains the data requested by the master.
CT-34 GTW/EN CT/C57

The data field can be non-existent in some kind of messages.
4.1.4 ERROR CHECK FIELD

The error-checking field contains a 16-bit value implemented as two 8-bit bytes [low significant byte first].
The error check value is the result of a Cyclical Redundancy Check [CRC] calculation performed on the
message contents.
The gateway does not reply to corrupted data messages, i.e when the CRC is not correct or when parity is
not correct.
4.2 SLAVE RESPONSES
4.2.1 WHEN THE SLAVE ANSWERS

Except for broadcast messages (no response in this case), when a master device sends a query to a slave
device it expects a normal response.
One of four possible events can occur from the master’s query:
• If the slave device receives the query without communication error, and can handle the query
normally, it returns a normal response.
• If the slave does not receive the query due to a communication error, no response is returned. The
master program will process a timeout condition for query.
• If the slave receives the query, but detect a communication error [bad CRC or framing error for
example ], no response is returned. The master program will process a timeout condition for query.
• If the slave device receives the query without communication error, but cannot handle it, the slave will
return an exception response informing the master of the nature of the error.
4.2.2 EXCEPTION RESPONSES CODES

The exception code is sent as an 8-bit data, the range of valid codes is 1-8 in the protocol.
Supported exception responses codes are:
Code Name Meaning
The function code received in the query is not an allowable action for the slave.
An illegal function will be sent in the main following cases:
01 ILLEGAL FUNCTION
An unsupported request [ see after, the table with the functions supported ]
An unsupported sub-function code for Diagnostic request
The data address received in the query is not an allowable address for the slave.
An illegal data address will be sent in the main following cases:
A read coil / input status starting to a none existent point in configuration
ILLEGAL DATA
02 A read holding registers / input registers starting to a none existent point in
ADDRESS
configuration
A force coil / multiple coils request starting on a non-configured address.
A preset single / multiple register(s) on an non-configured point
A value contained in the query data field is not an allowable value for the slave.
An illegal data value exception will be sent in the main following cases:
03 ILLEGAL DATA VALUE An illegal value received in force coils request ( so value different from FF00h and
0000h )
Illegal count value for multiple preset registers
04 SLAVE DEVICE FAILURE Not used in the gateway
GTW/EN CT/C57 CT-35

Code Name Meaning

05 ACKNOWLEDGE Not used in the gateway
06 SLAVE DEVICE BUSY Not used in the gateway
The slave cannot perform the program function received in the query.
A negative acknowledge will be sent in the main following cases:
NEGATIVE Some errors in the frame
07
ACKNOWLEDGE A read coil / input status on more than 2000 points
Force coil refused if command is incorrect or cannot be executed (equipment absent,
invalid, in local, ..)
MEMORY PARITY
08 Not used in the gateway
ERROR
4.3 SERIAL TRANSMISSION MODE

When messages are transmitted on standard MODBUS serial networks, each byte is sent with LSB first.
The format for each byte in MODBUS RTU mode is:
Coding system: 8-bit binary, hexadecimal 0-9, A-F
Two hexadecimal characters contained in each 8-bit field of the message
Bits per Byte: 1 start bit, 8 data bits,
LSB sent first, 2 stop bits if no parity, or 1 parity bit and 1 stop bit
Error Check Field: Cyclical Redundancy Check (CRC-16)
4.4 MODBUS FUNCTIONS

MODBUS defines 24 functions, valid codes are in the range of 1-24.
4.4.1 SUPPORTED FUNCTIONS

Code Function name Supported
01 READ COIL STATUS [ identical to function code 02 ] YES
02 READ INPUT STATUS [ identical to function code 01 ] YES
03 READ HOLDING REGISTERS [ identical to function code 04 ] YES
04 READ INPUT REGISTERS [ identical to function code 03 ] YES
05 FORCE SINGLE COIL YES
06 PRESET SINGLE REGISTER NO
07 READ EXCEPTION STATUS NO
08 DIAGNOSTICS [ only sub function 0 is supported ] YES
09 PROGRAM 484 NO
10 POLL 484 NO
11 FETCH COMM. EVENT CTR. NO
12 FETCH COMM. EVENT LOG NO
13 PROGRAM CONTROLLER NO
14 POLL CONTROLLER NO
15 FORCE MULTIPLE COILS YES
16 PRESET MULTIPLE REGISTERS NO
17 REPORT SLAVE ID NO
CT-36 GTW/EN CT/C57

Code Function name Supported

18 PROGRAM 884/M84 NO
19 RESET COMM. LINK NO
20 READ GENERAL REFERENCE NO
21 WRITE GENERAL REFERENCE NO
22 MASK WRITE 4X REGISTER NO
23 READ/WRITE 4X REGISTERS NO
24 READ FIFO QUEUE NO
4.4.2 GENERAL FORMAT OF MODBUS FUNCTIONS

• A query message typically contains some of the following 8-bit fields:
Starting Address Hi
Starting Address Lo
No. of Registers / Points Hi
No. of Registers / Points Lo
Force / Preset Data Hi
Force / Preset Data Lo
• A response message typically contains some of the following fields:

Byte Count *
Data
Data Hi
Data Lo
No. of Registers / Points Hi
No. of Registers / Points Lo
Force / Preset Data Hi
Force / Preset Data Lo
( * ) Byte Count Field:
A Byte Count Field is used in slave responses to indicate the number of 8-bit bytes in the Data field; the
value is exclusive of all other field contents, including the Byte Count field.
4.4.3 MODBUS DATA ADDRESSES

Point addresses in the data field are 16-bit values in the range of 0 – 65535 for each item type.
That’s means that you can have a coil item configured at address 100 for example, and a holding register
item configured at address 100 too.
Starting addresses in queries from SCADA may begin from address 0.
GTW/EN CT/C57 CT-37

Example:
Request to read the 16 first coils on device 11.
• Slave address 11
• Function 01
• Starting address HI 00
• Starting address LO 00
• Number of points HI 00
• Number of points LO 10
• CRC XX
4.5 FUNCTION 01 / 02: READ COIL STATUS – READ INPUT STATUS

The request function 01 or 02 reads the ON / OFF status of digital inputs in the slave. These status may be
any digital points (physical, automations, system information, grouping, … ).
These two functions are the only way to read digital points with the MODBUS protocol. Sequence of events,
digital flags (validity, topical, .. ) are not supported.
This is equal using the Read Coil Status request or the Read Input Status request.
Broadcast is not supported.
Addresses in frames may start from 0…65535.
Query:
Function Starting Starting
Slave No. of No. of CRC CRC
Code Address Address
Address Points (H) Points (L) (L) (H)
= 01 (H) (L)
The query message specifies the starting coil address and the quantity of coils to be read.
Response:
Function
Slave Byte Count Data Byte Data Byte Data Byte CRC CRC
Code
Address = <nbytes> #1 #i #nbytes (L) (H)
= 01
The coil or status in the response message is packed as one coil per bit of the data field. Status is indicated
as: 1 = ON, 0 = OFF. The less significant bit of the first data byte contains the coil addressed in the query.
The other coils follow toward the high order end of this byte, and from 'low order to high order' in subsequent
bytes, as described in the frame example.
CT-38 GTW/EN CT/C57

Important notes:
• If the returned coil quantity is not a multiple of eight, the remaining bits in the final byte will be padded
with zeros ( toward the high order end of the byte ). The Byte Count Field specifies the quantity of
complete bytes of data.
For easiest understanding between the gateway and the SCADA, it is recommended to read a number
of points which is a multiple of 8.
• If the starting address is not a point in configuration, the message will not be accepted, and an error
exception 2 will be returned.
• If the starting address is in configuration and if there is some “holes” ( addresses not in configuration )
theses holes will be padded with 0 ( i.e value OFF ).
• Maximum number of points allowed: 2000
4.6 FUNCTION 03 / 04: READ HOLDING REGISTERS / INPUT REGISTERS

The request function 03 or 04 reads the values of analogue inputs in the slave. These registers may be any
analogue points (physical, automations, and even counters).
These two functions are the only way to read registers points with the MODBUS protocol. Flags (validity,
topical…) are not supported in the MODBUS protocol base.
This is equal using the Read Holding Registers request or the Read Input Registers request.
Broadcast is not supported.
Addresses in frames may start from 0…65535.
Query:
Function Starting Starting No. of No. of CRC CRC
Slave
Code Address Address Points Points
Address
= 03 (H) (L) (H) (L) (L) (H)
The query message specifies the starting register and the quantity of registers to be read.
Response:
Function Data Data Data Data Data Data
Slave Byte Count CRC CRC
code (H) (L) (H) (L) (H) (L)
address = <nbytes> (L) (H)
= 03 #1 #1 #i #i # nbytes/ 2 # nbytes/2
The register data in the response message are packed as two bytes per register, with the binary contents
right justified within each byte. For each register, the first byte contains the high order bits and the second
contains the low order bits.
Important notes:
If the starting address is not a point in configuration, the message will not be accepted, and an error
exception 2 will be returned.
If the starting address is in configuration and if there is some “holes” (addresses not in configuration) theses
holes will be padded with the value 0
4.6.1 SIGNED NORMALISED CODING

The signed normalised coding is used to encode the 16 bits-registers. Analogue maximal value will be coded
7FFFh (decimal value + 32767), and minimal value will be coded 8000h (decimal value –32768).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register will be used ].
But, 16 bits is normally the standard to use the full scale conversion.
GTW/EN CT/C57 CT-39

Example:
In configuration the maximal value for an analogue point is +3000 and minimum value for this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway will send to the
SCADA the register with 8000h value. If this analogue is equal to the maximal value +3000, the value sent to
the SCADA is 7FFFh. Calculation is linear for the coding between the min and max values.
4.6.2 UNSIGNED NORMALISED CODING

The unsigned normalised coding is used to encode the 16 bits-registers. Analogue maximal value will be
coded FFFFh (decimal value + 65535), and minimal value will be coded 0000h (decimal value 0).
For this mode, the gateway may now code the value on 8 to 16 bits [ low part of the register will be used ].
But, 16 bits is normally the standard to use the full scale conversion.
Example:
In configuration the maximal value for an analogue point is +3000 and minimum value for this analogue is 0.
That means that when the analogue is received with value 0 from the system, the gateway will send to the
SCADA the register with 0h value. If this analogue is equal to the maximal value +3000, the value sent to the
SCADA is FFFFh. Calculation is linear for the coding between the min and max values.
4.6.3 NATURAL CODING

The natural coding is used to encode data without any calculation. That’s means that integer value will be
send.
Example:
if the gateway receives the value 10.xxxx, the value 0Ah will be set in the appropriate register. The gateway
receives the value –10,xxxx the value FFF6h will be coded.
In this example, the SCADA needs to know that FFF6h is value –10, and not 65525 decimal, by checking
analogue min and max value for example.
Counters are considered as TM but subject to NATURAL coding only.
4.7 FUNCTION 05: FORCE SINGLE COIL

This request function 05 is used to realise a control on an address point.
When broadcast, the function forces the same coil reference in all attached slaves.
setpoints are not available in the Modbus protocol
Query:
Function Point Point
Slave Force Data Force Data CRC CRC
Address (H) (L) (L) (H)
= 05 (H) (L)
The query message specifies the coil reference to be forced. Points addresses are between 0…65535. The
requested ON / OFF state is specified by a constant in the query data field.
A value of FF00h requests the coil to be ON.
A value of 0000h requests it to be OFF.
CT-40 GTW/EN CT/C57

Response:
Function Point Point
Slave Force Data Force Data CRC CRC
= 05 (H) (L)
The normal response is an echo of the query, returned after the command has been sent to the system.
Notes:
SCADA communication needs quick replies from the gateway. The reply returned is always sent when the
control is sent to the system. That means that the SCADA needs to check for the digital change in order to
know if the command is successful or not.
If value is incorrect, or if the control is refused for any reason (equipment absent, equipment present and in
local mode, equipment invalid, …) an exception error 7 is returned.
4.8 FUNCTION 08: DIAGNOSTIC [SUB-FUNCTION 0 ONLY]

This request function 08 sub-function 0 is used to test the transmission.
Query:
Sub Sub
Function
Slave Function Function Data Data CRC CRC
Code
Address code code (H) (L) (L) (H)
= 08
(H) (L)
The query message specifies the data that will be echoed.

Response:
Sub Sub
Function Echoed Echoed
Slave Function Function CRC CRC
Code Data Data
Address code code (L) (H)
= 08 (H) (L)
(H) (L)
The normal response is an echo of the query with the same data sent in the request.
Note: If the sub-function is different from 0, an exception error “illegal function” is returned.
4.9 FUNCTION 15: FORCE MULTIPLE COILS

This request function 15 is used to realise a control on several contiguous addresses.
Query:
Function Start Start
Slave Count Count
Code address address Byte count =>
Address (H) (L)
= 15 (H) (L)
Force Data Force Data

Force Data Force Data Force Data Force Data CRC CRC
Hi #nbytes / Lo #nbytes /
Hi #1 Lo #1 Hi #i Lo #i (L) (H)
2 2
The query message specifies the points addresses to be controlled. Addresses may start from 0 to 65535.
GTW/EN CT/C57 CT-41

The requested ON / OFF states are specified in the query data field. A logical ' 1 ' in a bit position of the field
requests the corresponding address to be ON. A logical ' 0 ' requests it to be OFF. Of course, the control will
be executed if the configuration allows this operation.
Response:
Function Start Start
Slave Count Count CRC CRC
Code address address
= 15 (H) (L)
The normal response returns the slave address, function code, starting address, and quantity of points
forced (echo of the request).
Notes:
1) The response always echo the number of points to be controlled by the SCADA (even if the control of the point
was not successful).
2) It is recommended to force small quantities of points, especially for time response.
CT-42 GTW/EN CT/C57

5 DNP3 PROTOCOL
In this section is described the support of the DNP3 protocol in the Alstom DS Agile system for Gateway PC.
5.1 PROFILE
Device Name: ALSTOM DS AGILE Telecontrol
Gateway
Highest DNP Level Supported:
Device Function:
For Requests Level 3
Master Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported: supported in addition to the Highest DNP Levels
Management event priorities are supported
…………………………………………………………………… ……………………………………………………………………
………………………………………… ………………………………………
Maximum Application Fragment Size (octets):
Maximum Data Link Frame Size (octets):
Transmitted 2048
Transmitted: 292
(configurable: 15 to 2048 bytes)
Received: (must be 292)
Received 2048
Maximum Application Layer Re-tries:

Maximum Data Link Re-tries:
None
None
Configurable, range ____ to ___
Fixed at 3
( Fixed is not permitted )
Configurable, range ____ to ______
Requires Data Link Layer Confirmation:

Never
Always
Sometimes - If ’Sometimes’, when?
………………………………………………………
…………………………………………………………
 Configurable If ’Configurable’, how?
User option to set Data Link Confirmation to:
Always – device will always request Data Link Confirmations.
Multi-packet only – the device will request Data Link Confirmations when sending multi-packet responses.
Never – the device will never request Data Link Confirmations.
Requires Application Layer Confirmation:
Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes - If 'Sometimes', when?
………………………………………………………………….
Configurable - If 'Configurable', how?
………………………………………………………………….
GTW/EN CT/C57 CT-43

Timeouts while waiting for:

Data Link Confirm None
Complete Appl. Fragment None Fixed at __ Variable Configurable
Application Confirm  None Fixed at __ Variable Configurable
Complete Appl. Response None Fixed at __ Variable Configurable
Others Fixed at __ Variable Configurable
………………………………………………
Attach explanation if 'Variable' or 'Configurable' was checked
for any timeout
 Data Link Confirm timeout is configurable: 0.1s to
30s
Sends/Executes Control Operations:
WRITE Binary Outputs Never
SELECT/OPERATE Never Always Sometimes Configurable
DIRECT OPERATE Never Always Sometimes Configurable
DIRECT OPERATE - NO ACK Never Always Sometimes Configurable

Always Sometimes Configurable
Count > 1 Never

Pulse On Never Always Sometimes Configurable
Pulse Off Never Always Sometimes Configurable
Latch On Never Always Sometimes Configurable
Latch Off Never Always Sometimes Configurable
Queue Never Always Sometimes Configurable
Clear Queue Never Always Sometimes Configurable
Select timeout : configurable (same value for all controls) Always Sometimes Configurable
A pulse duration can be specified from Scada, for trip & close
control with transient DO
When no value is specified, the default configured value is
used.
FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:
Reports Binary Input Change Events when no
Specific variation requested:
Never
Reports time-tagged Binary Input Change Events
Only time-tagged
When no specific variation requested:
Only non-time-tagged
Never
Configurable to send both, one or the other (explanation
Binary Input Change With Time
below)
Binary Input Change With Relative Time
User option to have all Binary Input
Configurable (attach explanation)
Change Events returned as either:
 time-tagged OR
non-time-tagged
Send Unsolicited Responses:
Send Static Data in Unsolicited Responses:
Never
Never
Configurable (attach explanation)
When Device Restarts
Only certain objects
When Status Flags Change
Sometimes (attach explanation)
ENABLE/DISABLE UNSOLICITED
No other options are permitted.
Function codes supported
CT-44 GTW/EN CT/C57

Default Counter Object/Variation:

Counters Roll Over at:
No Counters Reported
No Counters Reported
Configurable (explanation below)
Configurable (explanation below)
Default Object _____20_______
16 Bits
Default Variation _____02_______
32 Bits
Point-by-point list attached
Other Value _____________
User option to return all static counters in one of the following
Point-by-point list attached
variations:
User option to select roll over:
32-Bit Binary Counter
32 bit counters roll over at 2^32.
32-Bit Binary Counter Without Flag
16 bit counters roll over at 2^16
 16-Bit Binary Counter
 16-Bit Binary Counter Without Flag
Sends Multi-Fragment Responses: Yes No
5.2 IMPLEMENTATION TABLE

Unavailable information is shaded.
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Function Quality Codes Function Qual Codes
Obj Var Description
Codes (dec) (hex) Codes (hex)
1 0 Binary Input – All Variations 1 00,01,06
1 1 Binary Input 1 00,01,06 129,130 00,01
1 2 Binary Input with Status 1 00,01,06 129,130 00,01
2 0 Binary Input Change - All Variations 1 06,07,08
2 1 Binary Input Change without Time 1 06,07,08 129,130 17,28
2 2 Binary Input Change with Time 1 06,07,08 129,130 17,28
Binary Input Change with Relative
2 3 1 06,07,08 129,130 17,28
Time
10 0 Binary Output - All Variations 1 00,01,06
10 1 Binary Output
10 2 Binary Output Status 1 00,01,06 129,130 00,01
12 0 Control Block - All Variations (1)
12 1 Control Relay Output Block (1) 3,4,5,6 17,28 129 Request echo
12 2 Pattern Control Block 5,6 17,28 129 Request echo
12 3 Pattern Mask 5,6 00,01 129 Request echo
20 0 Binary Counter - All Variations 1,7,8,9,10,22 00,01,06
20 1 32-Bit Binary Counter 1 00,01,06 129,130 00,01
20 2 16-Bit Binary Counter 1 00,01,06 129,130 00,01
20 3 32-Bit Delta Counter 1 00,01,06 129,130 00,01
20 4 16-Bit Delta Counter 1 00,01,06 129,130 00,01
20 5 32-Bit Binary Counter without Flag 1 00,01,06 129,130 00,01
20 6 16-Bit Binary Counter without Flag 1 00,01,06 129,130 00,01
20 7 32-Bit Delta Counter without Flag 1 00,01,06 129,130 00,01
GTW/EN CT/C57 CT-45

REQUEST RESPONSE
OBJECT
Obj Var Description
20 8 16-Bit Delta Counter without Flag 1 00,01,06 129,130 00,01
21 0 Frozen Counter - All Variations 1 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 2 16-Bit Frozen Counter 1 00,01,06 129,130 00,01
21 3 32-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
21 4 16-Bit Frozen Delta Counter 1 00,01,06 129,130 00,01
32-Bit Frozen Counter with Time of
21 5
Freeze
16-Bit Frozen Counter with Time of
21 6
Freeze
32-Bit Frozen Delta Counter with
21 7
Time of Freeze
16-Bit Frozen Delta Counter with
21 8
Time of Freeze
21 9 32-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129,130 00,01
32-Bit Frozen Delta Counter without
21 11
Flag
16-Bit Frozen Delta Counter without
21 12
Flag
Counter Change Event - All
22 0 1 06,07,08
Variations
32-Bit Counter Change Event without
22 1 1 06,07,08 129,130 17,18
Time
16-Bit Counter Change Event without
22 2 1 06,07,08 129,130 17,18
Time
32-Bit Delta Counter Change Event
22 3 1 06,07,08 129,130 17,18
without Time
22 4 1 06,07,08 129,130 17,18
without Time
32-Bit Counter Change Event with
22 5
Time
16-Bit Counter Change Event with
22 6
Time
22 7
with Time
22 8
with Time
23 0 Frozen Counter Event - All Variations 1 06,07,08
32-Bit Frozen Counter Event without
23 1 1 06,07,08 129,130 17,18
Time
16-Bit Frozen Counter Event without
23 2 1 06,07,08 129,130 17,18
Time
32-Bit Frozen Delta Counter Event
23 3 1 06,07,08 129,130 17,18
without Time
23 4 1 06,07,08 129,130 17,18
without Time
CT-46 GTW/EN CT/C57

REQUEST RESPONSE
OBJECT
Obj Var Description
32-Bit Frozen Counter Event with
23 5
Time
16-Bit Frozen Counter Event with
23 6
Time
23 7
with Time
23 8
with Time
30 0 Analog Input - All Variations 1 00,01,06
30 1 32-Bit Analog Input 1 00,01,06 129,130 00,01
30 2 16-Bit Analog Input 1 00,01,06 129,130 00,01
30 3 32-Bit Analog Input without Flag 1 00,01,06 129,130 00,01
30 4 16-Bit Analog Input without Flag 1 00,01,06 129,130 00,01
31 0 Frozen Analog Input - All Variations
31 1 32-Bit Frozen Analog Input
31 2 16-Bit Frozen Analog Input
32-Bit Frozen Analog Input with Time
31 3
of Freeze
16-Bit Frozen Analog Input with Time
31 4
of Freeze
32-Bit Frozen Analog Input without
31 5
Flag
16-Bit Frozen Analog Input without
31 6
Flag
32 0 Analog Change Event - All Variations 1 06,07,08
32-Bit Analog Change Event without
32 1 1 06,07,08 129,130 17,18
Time
16-Bit Analog Change Event without
32 2 1 06,07,08 129,130 17,18
Time
32-Bit Analog Change Event with
32 3
Time
16-Bit Analog Change Event with
32 4
Time
0 Frozen Analog Event - All
33 0
Variations
32-Bit Frozen Analog Event without
33 1
Time
16-Bit Frozen Analog Event without
33 2
Time
32-Bit Frozen Analog Event with
33 3
Time
16-Bit Frozen Analog Event with
33 4
Time
Analog Output Status - All Variations
40 0 1 00,01,06
(2)
40 1 32-Bit Analog Output Status (2) 1 00,01,06 129,130 00,01
40 2 16-Bit Analog Output Status (2) 1 00,01,06 129,130 00,01
GTW/EN CT/C57 CT-47

REQUEST RESPONSE
OBJECT
Obj Var Description
41 0 Analog Output Block - All Variations 3,4,5,6 17,28 129 Request echo
41 1 32-Bit Analog Output Block (2) 5,6 17,28 129 Request echo
41 2 16-Bit Analog Output Block (2) 5,6 17,28 129 Request echo
50 0 Time and Date - All Variations
50 1 Time and Date 2 07 (quantity=1)
50 2 Time and Date with Interval
51 0 Time and Date CTO - All Variations
51 1 Time and Date CTO 129,130 07 (quantity=1)
51 2 Unsynchronized Time and Date CTO 129,130 07 (quantity=1)
52 0 Time Delay - All Variations
52 1 Time Delay Coarse 129,130 07 (quantity=1)
52 2 Time Delay Fine 129,130 07 (quantity=1)
60 0
60 1 Class 0 Data 1 06,07,08
60 2 Class 1 Data 1 06,07,08
20,21,22 06
60 3 Class 2 Data 1 06,07,08
20,21,22 06
60 4 Class 3 Data 1 06,07,08
20,21,22 06
70 1 File Identifier
00 (index=7 ou
80 1 Internal Indications 2
index=4)
1 00,01
81 1 Storage Object
82 1 Device Profile
83 1 Private Registration Object
Private Registration Object
83 2
Descriptor
90 1 Application Identifier
100 1 Short Floating Point
100 2 Long Floating Point
100 3 Extended Floating Point
101 1 Small Packed Binary-Coded Decimal
Medium Packed Binary-Coded
101 2
Decimal
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)
No Object (Warm Restart)
No Object (Delay Measurement
(1) Commands must be selected/executed on one point

(2) May be possible
CT-48 GTW/EN CT/C57

5.3 “ON-LINE” QUALITY BIT MANAGEMENT:

The table below described the management of the DNP3 binary input status object for each Alstom DS Agile
xPS status. This management is the same whether the information is with or without time tag. The SBMC is
off.
SPS:
Remote Forced
On-line BS1[0]
RestartBS1[1]
Local Forced
Chatter filter
State BS1[7]
Comm.lost
Reserved
BS1[2]
BS1[3]
BS1[4]
BS1[5]
BS1[6]
Alstom DS Agile SPS Status
SBMC is Off
RESET 1 - - - - - - 0
SET 1 - - - - - - 1
TOGGLING 1 - - - - 1 - 0
SELFCHECKFAULT 0 - - - - - - 0
(1)
UNKNOWN 1 - 1 - - - -
(2)
SUPPRESSED 1 - - 1 - - -
(2)
FORCED 1 - - 1 - - -
(2)
SUBSTITUTED 1 - - 1 - - -
DPS:
DNP Add. (CO) DNP Add. +1 (CC)
Reserved BS1[6]
Reserved BS1[6]
Remote Forced
Remote Forced
On-line BS1[0]
On-line BS1[0]
RestartBS1[1]
RestartBS1[1]
Local Forced
Local Forced
Chatter filter
Chatter filter
State BS1[7]
State BS1[7]
Comm.lost
Comm.lost
Alstom DS Agile
BS1[2]
BS1[3]
BS1[4]
BS1[5]
BS1[2]
BS1[3]
BS1[4]
BS1[5]
DPS Status
SCE Inversion = No
SBMC is Off
OPEN 1 - - - - - - 1 1 - - - - - - 0
CLOSED 1 - 0 1 - - - - - - 1
JAMMED 0 - 0 0 - 1
UNDEFINED 0 - - - 0 0 - 1
TOGGLING 1 - - - - 1 - 0 1 - - - - 1 - 1
SELFCHECKFAULT 0 - - - - - - 0 0 - - - - - - 1
(1) (1)
UNKNOWN 1 - 1 - - - - 1 - 1 - - - -
(2) (2)
SUPPRESSED 1 - - 1 - - - 1 - - 1 - - -
(2) (2)
FORCED 1 - - 1 - - - 1 - - 1 - - -
(2) (2)
SUBSTITUTED 1 - - 1 - - - 1 - - 1 - - -
(1)
If information comes from IEC 61850-8-1 then BS1[7] is as transmitted on 61850.If the c264 detects a
disconnection of a IEC 61850-8-1 server then Information of this server are reset. If information comes from
a VDEW IED or a MODBUS IED there is no change from the previous status. If information comes from a
T101 IED or DNP3 IED, the bit is reset.
(2)
Value is given by the client that forces, suppresses or substitutes the information.
“-“ stands for 0 except when 0 is significant, in this case the 0 appears in the cell.
“X stands for No change. It means no change from the previous status.
GTW/EN CT/C57 CT-49

The table below described the management of the DNP3 Object coding status Flag and current value for
each Alstom DS Agile MV and SPI status. This management is the same whether the information is with or
without time tag. The SBMC is off.
Over-range BS1[5]
Comm.lost BS1[2]
Reference check
Reserved BS1[7]
Remote Forced
On-line BS1[0]
RestartBS1[1]
Local Forced
BS1[3]
BS1[4]
BS1[6]
Alstom DS Agile MV and SPI Status DNP3 object
coding status
SBMC is Off Current value
VALID 1 - - - - - - - VALUE*
SELFCHECK FAULT 0 - - - - - - - X*
UNKNOWN 1 - 1 - - - - - X*
FORCED 1 - - 1 - - - - VALUE*
SUPPRESSED 1 - - 1 - - - - VALUE*
SUBSTITUTED 1 - - 1 - - - - VALUE*
OVERRANGE (0x6000) 0 - - - - - - - Min or Max or (1)*
UNDEFINED 0 - - - - - - - X*
OPENCIRCUIT 0 - - - - - - - X*
*value can be scaled and depends to the format (Natural or Adjusted). If the result of the scaling is not
between min and max defined in the configuration, then the MV is OVERRANGE
(1)
If the scaling value is between min and max then this value is transmitted
The table below described the management of the DNP3 Object coding status Flag and delta value for each
Alstom DS Agile COUNTER status. This management is the same whether the information is with or without
time tag. The SBMC is off.
Remote Forced
On-line BS1[0]
RestartBS1[1]
check BS1[6]
Local Forced
Over-range
Comm.lost
Reference
Reserved
BS1[2]
BS1[3]
BS1[4]
BS1[5]
BS1[7]
Alstom DS Agile Counter DNP3 object coding status

Status Value
VALID 1 - - - - - - - VALUE
SELFCHECK FAULT 0 - - - - - - - X
UNKNOWN 1 - 1 - - - - - X
OVERRANGE 0 - - - - - - - X
UNDEFINED 0 - - - - - - - X
CT-50 GTW/EN CT/C57

6 OPC PROTOCOL
6.1 IMPLEMENTATION
All required OPC Interfaces are supported for both OPC 1.0 and OPC 2.0 Data Access Standards as well as
the Browse Interface (OPC DA 2.05).
The OPC Protocol basically operates as a data librarian. The controlling application creates Process Tags by
passing a name and value to the DLL. The DLL records the data point and makes it available to any OPC
Client application by name. The controlling application may change the value of the data at any time, and all
attached clients would be automatically notified. Callback notification is provided for any Process Tag that is
modified by an OPC Client connection. (The application has control over which tags are OPC_WRITEABLE
only for control datapoints.)
Registration
The Opc Server registration is made by the gateway installation software if you chose OPC Protocol.
Two arguments are needed for this phase: CLSID and PROGID
CLSID: {8087E613-3ED9-11D7-827E-00E029555839}
PROGID: ALSTOM.OPC SERVER.V2.0
Initialization
When this phase is executed, the DLL performs all necessary initialization of COM/DCOM and creates the
OPCServer Interface object to be used for client connections. The specified ServerRate defines how fast the
OPC Client data connections are refreshed (ServerRate is configured in registry)
Creating Process Tags
As each process tag is created, the DLL returns a HANDLE to identify the point for future references,
(updates), from the application. The naming convention used for browsing operations, (OPC_NS_FLAT or
OPC_NS_HIERARCHIAL), is a function of how the names are assigned by the controlling application. If
segmented names are used to create the tags, (strings containing the delimiter ‘.’), the DLL will automatically
configure the name space as hierarchial, otherwise a flat name space is used. The names are configured by
Alstom DS Agile SCE.
Each process tag is configured with a type which identifies the type of Variant used for update.
Type of datapoint Type of TAG configurable Type of VARIANT used
SPS (single point status) BOOL,BYTE VT_BOOL,VT_UI1
DPS (double point status) BOOL,BYTE VT_BOOL,VT_UI1
MPS (multiple point status) BYTE,WORD VT_UI1,VT_UI2
MV (measurement) FLOAT VT_R4
TPI (Tap changer indicator) WORD VT_I2
Counter DWORD VT_I4
SPC (single point control) BOOL,BYTE VT_BOOL,VT_UI1
DPC (double point control) BOOL,BYTE VT_BOOL,VT_UI1
Setpoint FLOAT VT_R4
Only SPC,DPC and Setpoint are OPC_WRITABLE tags.
GTW/EN CT/C57 CT-51

Updating Process Tags

A process tag is updated with:
• HANDLE TagHandle defines the datapoint (Process Tag),
• VARIANT Value defines the new datapoint value,

• WORD Quality defines the new Quality,
• FILETIME timestamp defines the UTC source timestamp of the datapoint (This structure is a 64-bit
value representing the number of 100-nanosecond intervals since January 1, 1601).
OPC Quality flags
These flags represent the quality state for a item’s data value. The low 8 bits of the Quality flags are currently
defined in the form of three bit fields; Quality, Substatus and Limit status. The 8 Quality bits are arranged as
follows: QQSSSSLL. The high 8 bits of the Quality Word are available for vendor specific use.If these bits
are used, the standard OPC Quality bits must still be set as accurately as possible to indicate what
assumptions the client can make about the returned data. In addition it is the responsibility of any client
interpreting vendor specific quality information to insure that the server providing it uses the same ‘rules’ as
the client.
Details of the OPC standard quality bits follow:
The Quality BitField
QQ BIT VALUE DEFINE
0 00SSSSLL Bad
1 01SSSSLL Uncertain
2 10SSSSLL N/A
3 11SSSSLL Good
The Substatus BitField

The layout of this field depends on the value of the Quality Field.
Substatus for BAD Quality
SSSS BIT VALUE DEFINE
0 000000LL Non-specific
1 000001LL Configuration Error
2 000010LL Not Connected
3 000011LL Device Failure
4 000100LL Sensor Failure
5 000101LL Last Known Value
6 000110LL Comm Failure
7 000111LL Out of Service
8-15 N/A
CT-52 GTW/EN CT/C57

Substatus for UNCERTAIN Quality

1 010001LL Last Usable Value
2-3 N/A
4 010100LL Sensor Not Accurate
5 010101LL Engineering Units Exceeded
6 010110LL Sub-Normal
7-15 N/A
Sub-status for GOOD Quality

1-5 N/A
6 110110LL Local Override
7-15 N/A
The Limit BitField

LL BIT VALUE DEFINE
0 QQSSSS00 Not Limited
1 QQSSSS01 Low Limited
2 QQSSSS10 High Limited
3 QQSSSS11 Constant
For a good interoperability, the Quality is configured by the SCE for each quality
IEC 61850-8-1.
GTW/EN CT/C57 CT-53

6.2 OPC STANDARD LAYER

This layer provides a way to access (read/write) to a set of data sources. The OPC Client connects to the
OPC Server and communicates to it through the OPC interfaces. The OPC Server object provides
functionality to the OPC client to create and manipulate group objects. OPC Group objects allow the OPC
Client to manage the data it wants to access.
The following sections deals with these interfaces and how they are implemented in the toolkit. For a
complete reference of the OPC Data Access interfaces see OPC Data Access Custom Interface Standard
version 2.05A.
6.2.1 OPCSERVER OBJECT

This is the only one COM object available from an OPC Client point of view. All the others object will be
created or accessed through the server. The set of interfaces provided by this object includes:
• IOPCServer
• IOPCCommon
• IOPCBrowseServerAddressSpace
• IOPCItemProperties
• IOPCServerPublicGroups
• IOPCEventServer
• IConnectionPointContainer
IOPCServer interface:
This is the main interface of an OPC server. This interface is used to manage the group of an OPC server
(add, remove, browse, get). This interface is also used to get the current status of an OPC server.
IOPCommon interface:
This interface is used to specify the localization of the CCOMOPCServer class. In the current implementation
of the class the only localization supported is the one of the machine the server is running on. This interface
also enables the client to give its name to the server. It can be useful to get a list of client from the toolkit.
IOPCBrowseServerAdressSpace interface:
This interface allows clients to get information about tags managed by servers. Implementation lies on a
COM object named CCOMOPCTagPtr. Each time a tag is created, a CCOMOPCTagPtr is created and it
keeps a reference on the tag. All the tag pointers are linked together, either in a hierarchical way or in a flat
way.
IOPCItemProperties interface:
This interface can be used by clients to browse the available properties associated with a tag and to read the
current values of theses properties.
IOPCServerPublicGroups interface:
This interface is used to create public groups. These groups can be share by many clients. Standard group
created by the AddGroup method of the IOPCServer interface is private to the server which created it. With a
public group many client can have access to the same group of items.
IOPCEventServer interface:
This interface is used to manage the alarms and events functionality.
CT-54 GTW/EN CT/C57

IConnectionPointContainer
This interface allows the client to retrieve connection points so it can setup callback mechanism for
asynchronous communication from the server. As defined by the OPC specification the only callback
mechanism available from the OPCServer is the IOPCSutdown interface. The OPCServer is provided by the
CCOMOPCServer object. The following diagram presents it:
<<coclass>> <<default>>
COMOPCServer
(from COClasses)
IConnectionPointlmpl
(from Connection Points) IHiddenOPCServer
AddClonedGroup()
Advise() CheckGroupName()
EnumConnections() GetUniqueGroupValues()
GetConnectionInterface() StartWorkerThread()
GetConnectionPointContainer() SendData()
Unadvise() <<Implements>> RequestDisconnect()
GetClientName()
IOPCBrowseServerAddress
Space
IConnectionPointContainerlmpl <<atIobject>>
(from Connection Points) CCOMOPCServer QueryOrganization()
ChangeBrowsePosition()
<<stdmethod>> FindConnectionPoint() BrowseOPCItemIDs()
<<stdmethod>> EnumConnectionPoint() GetItemID()
BrowseAccessPaths()
IOPCEventServer
IOPCServerPublicGroups
IOPCCommon
GetStatus()
GetPublicGroupByName()
CreateEventSubscription()
SetLocaleID() RemovePublicGroup()
QueryAvailableFilters()
GetLocaleID()
QueryEventCategories()
QueryAvailableLocaleIDs()
QueryConditionNames()
GetErrorString()
QuerySubConditionNames()
SetClientName()
QuerySourceConditions()
QueryEventAttributes() IOPCServer
TranslateToItemsIDs()
GetConditionState()
AddGroup()
IOPCItemProperties EnableConditionByArea()
GetErrorString()
EnableConditionBySource()
GetGroupByName()
DisableConditionByArea()
QueryAvailableProperties() GetStatus()
DisableConditionBySource()
GetItemProperties() RemoveGroup()
AckCondition()
LookupItemIDs() CreateGroupEnumerator()
CreateAreaBrowser()
S0429ENa
The non standard IHiddenOPCServer interface is provided for internal use only the CCOMOPCServer object
can easily interact with other objects within the toolkit.
Every CCOMOPCServer object maintains a map of group and the current and root TagPtr.
GTW/EN CT/C57 CT-55

6.2.2 OPCGROUP OBJECT

The OPC Group object is delivered by the server to manage a collection of items. The set of interfaces
provided by this object includes:
• IOPCItemMgt
• IOPCGroupStateMgt
• IOPCSyncIO
• IOPCAsyncIO2
• IConnectionPointContainer
IOPCItemMgt
This interface allows the client to add, remove and control the behaviour of items in the group.
IOPCGroupStateMgt
This interface allows the client to manage the overall state of the group (mainly update rate control and
active state management).
IOPCSyncIO
This interface allows the client to perform synchronous read and write operations to the server. These
operations will run to completion.
IOPCAsyncIO2
This interface allows the client to perform asynchronous read and write operations to the server. Theses
operations will be queued and the methods of the interface will return immediately so that the client can go
on running. When the operations are completed, a callback will be made to the IOPDataCallback in the
client.
IConnectionPointContainer
This interface allows the client to retrieve connection points so it can setup callback mechanism for
asynchronous communication from the server. As defined by the OPC specification the callback mechanism
available from the OPCGroup is the IOPCDataCallback interface.
The OPCGroup is provided by the CCOMOPCGroup object. The following diagram presents it:
CT-56 GTW/EN CT/C57

<<default>>
<<coclass>>
COMOPCGroup
IHiddenOPCGroup
IConnectionPointImpl
SetDara()
(from Connection Point)
SetServerHandle()
SetServer()
Advise() SendData()
EnumConnections() <<Implements>> ProcessAsyncIO()
GetConnectionInterface() CheckName()
GetConnectionPointContainer() SetMarkedForDeletion()
Unadvise() EnumNextItems()
EnumCanSkip()
IConnectionPointContainerImpl <<atlobject>>
(from ConnectionPoints) CCOMOPCGroup
m_csItems : CComAutoCriticalSection
<<stdmethod>> FindConnectionPoint() m_ItemMap : ItemMap
<<stdmethod>> EnumConnectionPoints() m_dwItemMapIdx : DWORD
m_csData : Sections::CComAutoCriticalSection
m_dwUpdateRate : DWORD
m_bActive : BOOL
m_wszName : std::wstring
m_lTimeBias : LONG
IOPCItemMgt IOPCGroupStateMgt
m_fPercentDeadband : FLOAT
m_dwLCID : DWORD
m_hClientGroup : OPCHANDLE
AddItems() GetState()
m_hServerGroup : OPCHANDLE
ValidateItems() SetState()
m_bMarkedForDeletion : BOOL
RemoveItems() SetName()
m_bAsyncIOEnabled : BOOL
SetActiveState() CloneGroup()
...
SetClientHandles()
SetDatatypes()
CreateEnumerator()
IOPCSyncIO IOPCPublicGroupStateMgt IOPCAsyncIO2
Read() GetState() Read()

Write() MoveToPublic() Write()
Rf h2()
S0430ENa
The non standard IHiddenOPCGroup interface is provided for internal use only so the OPCServer object can
easily interact with it.
Every group maintains a map of items and a map of asynchronous operations called AsyncIORequests.
GTW/EN CT/C57 CT-57

6.3 OPC SERVER ALSTOM SPECIFICITIES
6.3.1 HISTORISATION MECHANISM

A historisation mechanism is available in the OPC server. For each Digital Input a buffer of maximum ten
changes of state allows to defer the transmission of the update to the OPC server. A timer (Historic Timer) is
configured in the base of registers. If this timer equals 0 this mechanism will not be activated, otherwise the
server will be updated each time the timer ends (default value: 250ms). This mechanism avoids to lose the
changes of state of the same digital input during the same cycle of ServerRate and allows to transmit
cyclically (period Historic Time) to the server every change of state.
If the buffer is full and a new change of state occurs, the older change of state is deleted and replaced by the
new one.
A Boolean information is created to give to the OPC client the overflow status of all the buffer. The tag name
of this boolean information is configurable in registry by the key PIF_name (default:
HKLM\SOFTWARE\Alstom\protocol\OPC\svritfc\PIF_name=PERTE INFO)
The information “LOOSE INFO” is set to “ON” as soon as a buffer is full. It is reset to “OFF” when all the
buffers have less than thee changes of state.
6.3.2 STATE INVERSION

By configuration it is possible to invert the state of a TS
• simple TS: “SET” is replaced “RESET” and vice versa

• double TC: “JAMMED” (00) is replaced by “UNDEFINED” (11) and vice versa
and “OPEN” (01 is replaced by “CLOSE” (10) and vice versa.
6.3.3 CONVERSION OF A DOUBLE TS (SYSTEM SIDE) IN TWO TS (OPC SIDE)

By configuration it is possible to define for a double system TS a double addressing. In this case, two OPC
tag names have to be defined: one for the tag “Open”, one for the tag “Close”. States are coded as follows:
state “Undefined“
double system TS state “Jammed“ (00) state “Open“ (01) state “Close“ (10)
(11)
Tag Open Value “Reset“ Value “Set“ Value “Reset“ Value “Set“
Tag Close Value “Reset“ Value “Reset“ Value “Set“ Value “Set“
The Set and Reset values of the tags Open and Close will be taken in the configured value corresponding to
the same type as the double TS (byte or Boolean).
6.3.4 CONVERSION OF TWO SIMPLE TS (OPC SIDE) IN A DOUBLE TC (SYSTEM SIDE)

By configuration it is possible to define for a double system TC a double addressing. In this case, two OPC
tag names have to be defined: one for the tag “Open”, one for the tag “Close”. States of the commands are
coded as follows:
double system TS Command Open Command Close
Tag Open order Value Set Value Reset

Tag Close order Value Reset Value Set
The Set and Reset values of the tags Open and Close will be taken in the configured value corresponding to
the same type as the double TC (byte or Boolean).
CT-58 GTW/EN CT/C57

7 IEC 61850-8-1 PROTOCOL
7.1 GENERAL
The following ACSI conformance statements shall be used to provide an overview and details about a device
claiming conformance with ACSI:
• ACSI basic conformance statement,

• ACSI models conformance statement,
• ACSI service conformance statement,
to specify the communication features mapped to a SCSM.
Note 1 The conformance statements of this annex are abstract in the sense that the ACSI models and their services
are mapped to application layer models, services, and protocols. Additional details on the conformance are defined in
the SCSM.
Note 2 For several features the conformance requirement is implicitly defined with the common data class contained in
part IEC 61850-7-3 and the compatible LOGICAL-NODE classes and DATA classes contained in part IEC 61850-7-4.
E.g., a TrgOp (trigger option) of the value qchg (quality change) of DataAttribute requires the support of the TrgOpEna
(trigger option enabled) qchg of the BRCB or URCB.
7.2 ACSI BASIC CONFORMANCE STATEMENT

The basic conformance statement is defined in the following table.
Table A.1 – Basic conformance statement
Client/ Server/ Value/
Subscriber Publisher Comments
Client-Server roles
Server side (of TWO-PARTY-APPLICATION-
B11 - Y
ASSOCIATION)
Client side of (TWO-PARTY-APPLICATION-
B12 Y -
ASSOCIATION)
SCSMs supported
A-Profile A-Profile
B21 SCSM: IEC 6185-8-1 used client/server client/server
T-Profile TCP/IP T-Profile TCP/IP
B22 SCSM: IEC 6185-9-1 used N N
B23 SCSM: IEC 6185-9-2 used N N
B24 SCSM: other N N
Generic substation event model (GSE)

B31 Publisher side - N
B32 Subscriber side N -
Transmission of sampled value model (SVC)

B41 Publisher side - N
GTW/EN CT/C57 CT-59


B42 Subcriber side N -
c1 – shall be ‘M’ if support for LOGICAL-DEVICE model has been declared
7.3 ACSI MODELS CONFORMANCE STATEMENT

The ACSI models conformance statement are defined in the following table.
Table A.2 – ACSI models conformance statement
If Server side (B1) is supported
M1 Logical device Y
M2 Logical node Y
M3 Data Y
M4 Data set Y
M5 Substitution N
M6 Setting group control N
Reporting
.M7 Buffered report control Y
.M7-1 sequence-number Y
.M7-2 report-time-stamp Y
.M7-3 reason-for-inclusion Y
.M7-4 data-set-name Y
.M7-5 data-reference Y
.M7-6 buffer-overflow Y
.M7-7 entryID Y
.M7-8 BufTim Y
.M7-9 IntgPd Y
.M7-10 GI Y
M7-11 Conf-revision Y
M8 Unbuffered report control Y
M8-1 sequence-number Y
M8-2 report-time-stamp Y
M8-3 reason-for-inclusion Y
M8-4 data-set-name Y
M8-5 data-reference Y
M8-6 BufTim Y
M8-7 IntgPd Y
M8-10 GI Y
M8-11 Conf-revision Y
Logging N
M9 Log control N
M9-1 IntgPd
M10 Log N
CT-60 GTW/EN CT/C57


M11 Control Y
If GSE (B31/32) is supported
GOOSE N
M12-1 entryID N
M12-2 DataRefInc N
M13 GSSE N
If SVC (41/42) is supported
M14 Multicast SVC N
M15 Unicast SVC N
Time source
with required
M16 Time N
accuracy shall
be available
M17 File Transfer N
c1 – Shall be ‘M’ if support for LOGICAL-DEVICE model has been declared

c2 – Shall be ‘M’ if support for LOGICAL-NODE model has been declared
c3 – Shall be ‘M’ if support for DATA model has been declared
c4 – Shall be ‘M’ if support for DATA-SET, Substitution, Report, Log Control, or Time model has been
declared
c5 – shall be ‘M’ if support for Report, GSE, or SMV models has been declared
7.4 ACSI SERVICE CONFORMANCE STATEMENT

The ACSI service conformance statement is defined in the following table.
Table A.3 – ACSI service Conformance statement
AA: Client Server
Services Comments
TP/MC (C) (S)
Server (clause 6)
S1 ServerDirectory TP - Y
Application association (clause 7)

S2 Associate Y
S3 Abort Y
S4 Release Y
Logical device (clause 8)

S5 LogicalDeviceDirectory TP Y
Logical node (clause 9)

S6 LogicalNodeDirectory TP Y
S7 GetAllDataValues TP Y
Data (clause 10)

S8 GetDataValues TP Y
GTW/EN CT/C57 CT-61

AA: Client Server

Services Comments
TP/MC (C) (S)
S9 SetDataValues TP Y
S10 GetDataDirectory TP Y
S11 GetDataDefinition TP Y
Data set (clause 11)

S12 GetDataSetValues TP Y
S13 SetDataSetValues TP N
S14 CreateDataSet TP N
S15 DeleteDataSet TP N
S16 GetDataSetDirectory TP Y
Substitution (clause 12)

S17 SetDataValues TP N
Setting group con trol (clause 13)

S18 SelectActiveSG TP N
S19 SelectEditSG TP N
S20 SetSGValues TP N
S21 ConfirmEditSGValues TP N
S22 GetSGValues TP N
S23 GetSGCBValues TP N
Reporting (clause 14)

Buffered report control block (BRCB)
.S24 Report TP Y
.S24-1 data-change (dchg) Y
.S24-2 qchg-change (qchg) Y
.S24-3 data-update (dupd) Y
.S25 GetBRCBValues TP Y
.S26 SetBRCBValues TP Y
Unbuffered report control block (URCB)
S27 Report TP Y
S27-1 data-change (dchg) Y
S27-2 qchg-change (qchg) Y
S27-3 data-update (dup) Y
S28 GetURCBValues TP Y
S29 SetURCBValues TP Y
c6-shall declare support for at least one (BRCB/ URCB)
Logging (clause 14)

Log control block
S30 GetLCBValues TP N
S31 SetLCBValues TP N
Log
CT-62 GTW/EN CT/C57

AA: Client Server

Services Comments
TP/MC (C) (S)
S32 QueryLogByTime TP N
S33 QueryLogByEntry TP N
S34 GetLogStatusValues TP N
c7–shall declare support for at least one: QueryLogByTime or QueryLogByEntry
Generic substation event model (GSE) (clause 14.3.5.3.4)

GOOSE- CONTROL- BLOCK
S35 SendGOOSEMessage MC N
S36 GetReference TP N
S37 GetGOOSEElementNumber TP N
S38 GetGoCBValues TP N
S39 SetGoCBValues TP N
GSSE- CONTROL-BLOCK
S40 SendGSSEMessage MC N
S41 GetReference TP N
S42 GetGSSEElementNumber TP N
S43 GetGsCBValues TP N
S44 SetGsCBValues TP N
c8–shall declare support for at least one Send GOOSE Message or Send GSSE Message
c9–shall declare support if TP association is available
Transmission of sampled value model (SVC) (clause 16)

Multicast SVC
S45 SendMSVMessage MC N
S46 GetMSVCBValues TP N
S47 SetMSVCBValues TP N
Unicast SVC
S48 SendUSVMessage TP N
S49 GetUSVCBValues TP N
S50 SetUSVCBValues TP N
c10–shall declare support for at least one SendMSVMessage/SendUSVMessage
Control (clause 16.4.8)

S51 Select N
S52 SelectWithValue TP Y
S53 Cancel TP Y
S54 Operate TP Y
S55 Command-Termination TP Y
S56 TimeActivated-Operate TP N
File transfer (clause 20)
S57 GetFile TP N
S58 SetFile TP N
S59 DeleteFile TP N
S60 GetFileAttributeValues TP Y
GTW/EN CT/C57 CT-63

Control (clause 16.4.8)
Time (clause 5.5)

T1 Time resolution of internal clock 10 nearest negative power of 2 in seconds
T2 Time accuracy of internal clock N T0
N T1
N T2
N T3
N T4
N T5
Supported TimeStamp
T3 - 10 nearest negative power of 2 in seconds
resolution
AA: Application association type

MC:Multicast (for GOOSE and SMV)
TP: Two part (for MMS)
CT-64 GTW/EN CT/C57

8 COMMUNICATIONS WITH IEDS: LEGACY T101 MASTER

NETWORK
A Gateway can communicate as an IEC 60870-5-101 master with networked IEDs.
8.1 MASTER IEC 60870-5-101 PROFILE

The companion standard presents sets of parameters and alternatives from which subsets have to be
selected to implement particular telecontrol systems. Certain parameters values, such as the number of
bytes in the COMMON ADDRESS of ASDUs represent mutually exclusive alternatives. This means that only
one value of the defined parameters is admitted per system.
The selected parameters are marked in the white boxes as follows:
Function or ASDU is NOT used
Function or ASDU is used as standardised (default)
Note: In addition, the full specification of a system may require individual selection of some parameters for some
parts of the system, such as the individual selection of scaling factors for individually addressable measured values.
8.1.1 SYSTEM OR DEVICE

(system specific parameter, indicates the definition of a system or a device by marking one of the following
with ‘X’)
For C26x Standalone:
System definition
Controlling station definition (Master)
Controlled station definition (Slave)
8.1.2 NETWORK CONFIGURATION

(network specific parameter, all configurations that are used are marked ‘X’)
Point-to-point Multipoint-party line
Multiple point-to-point Multipoint-star
8.1.3 PHYSICAL LAYER

(network specific parameter, all interfaces and data rates that are used are marked ‘X’)
RS232 or RS485 depending on configuration
GTW/EN CT/C57 CT-65

Transmission speed (control and monitor directions)

Unbalanced interchange
Circuit V24/V28 Balanced interchange
Recommended if Circuit X24/X27
Standard
> 1200 bits/s
⌧ 100 bits/s ⌧ 2400 bits/s ⌧ 2400 bits/s 56000 bits/s
⌧ 200 bits/s ⌧ 4800 bits/s ⌧ 4800 bits/s 64000 bits/s
⌧ 300 bits/s ⌧ 9600 bits/s ⌧ 9600 bits/s
⌧ 600 bits/s ⌧ 19200 bits/s ⌧ 19200 bits/s
⌧ 1200 bits/s ⌧ 38400 bits/s
8.1.4 LINK LAYER

Unbalanced mode
Polling process:
Gateway C26x
Status Link frame
answer
Reset Link frame
acknowledgement
Status Link frame
answer
Reset Link frame
acknowledgement
End of Initialisation
Global Interrogation
Counter Interrogation (if applicable)
Balanced mode
Unlike the unbalanced mode, there is no C26x polling.
The Master sends periodically a “Test command” message to make sure the connections with the C26x units
are still active.
The Slave can also send a “Test command” message to make sure the connection is still active.
The Slave sends spontaneously ASDU messages, on BI change of state/quality or on MEAS and SPI
change of value/quality.
(network specific parameter, all used options are 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
& COT of all messages assigned to class 2.)
companion standard.
Balanced transmission Not present (balanced transmission only)
Unbalanced transmission One octet
Two octets
CT-66 GTW/EN CT/C57

Structured
Unstructured
Frame length (number of bytes)
50 to 255 in control direction
50 to 255 in monitor direction
Repetition parameters (only in balanced mode)
Number of repetitions on non acknowledged frame
Maximum time between information frame and controlling station acknowledgement
8.1.5 APPLICATION LAYER

companion standard.
(system-specific parameter, all configurations that are used are to be marked ‘X’)
One octet Two octets

One octet Structured
Two octets Unstructured
Three octets
One octet Two octets (with originator address)

Selection of standard ASDUs
(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’ is used in both directions)
⌧ <1> := Single-point information M_SP_NA_1
⌧ <2> := Single-point information with time tag M_SP_TA_1
⌧ <3> := Double-point information M_DP_NA_1
⌧ <4> := Double-point information with time tag M_DP_TA_1
⌧ <5> := Step-position information M_ST_NA_1
⌧ <6> := Step-position information with time tag M_ST_TA_1
<7> := BitString of 32 bit M_BO_NA_1
<8> := BitString of 32 bit with time tag M_BO_TA_1
⌧ <9> := Measured value, normalized value M_ME_NA_1
⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1
⌧ <11> := Measured value, scaled value M_ME_NB_1
⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1
GTW/EN CT/C57 CT-67

⌧ <13> := Measured value, short floating point value M_ME_NC_1

⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1
⌧ <15> := Integrated totals M_IT_NA_1
⌧ <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
⌧ <19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1
<20> := Packed single-point information with status change detection M_PS_NA_1
<21> := Measured value, normalized value without quality descriptor M_ME_ND_1
⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1
⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1
⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1
<33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1
⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1
⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1
⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1
⌧ <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 M_EP_TF_1
CP56Time2a

⌧ <45> := Single command C_SC_NA_1
⌧ <46> := Double command C_DC_NA_1
⌧ <47> := Regulating step command C_RC_NA_1
⌧ <48> := Set point command, normalized value C_SE_NA_1
⌧ <49> := Set point command, scaled value C_SE_NB_1
⌧ <50> := Set point command, short floating point value C_SE_NC_1
<51> := BitString of 32 bits C_BO_NA_1
⌧ <70> := End of initialisation M_EI_NA_1

⌧ <100> := Interrogation command C_IC_NA_1
⌧ <101> := Counter Interrogation Command C_CI_NA_1
<102> := Read command C_RD_NA_1
⌧ <103> := Clock synchronisation command C_CS_NA_1
⌧ <104> := Test command C_TS_NB_1
<105> := Reset process command C_RP_NC_1
CT-68 GTW/EN CT/C57

⌧ <106> := Delay acquisition command C_CD_NA_1

<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
File transfer
(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’ is used in both directions)
⌧ <120> := File ready F_FR_NA_1
⌧ <121> := Section ready F_SR_NA_1
⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1
⌧ <123> := Last section, last segment F_LS_NA_1
⌧ <124> := Ack file, ack section F_AF_NA_1
⌧ <125> := Segment F_SG_NA_1
⌧ <126> := Directory F_DR_TA_1
Special use (private range)

⌧ <136> := Database version M_DB_NA_1
⌧ <137> := Regulating delay command C_RC_NB_1

Shaded boxes are not required.
Mark type identification/cause of transmission combinations:
‘X’ if used only in the standard direction
‘R’ if used only in the reverse direction
‘B’ if used in both directions
Type ID Cause of transmission
20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<2> M_SP_TA_1 X X
<4> M_DP_TA_1 X X
GTW/EN CT/C57 CT-69


<6> M_ST_TA_1 X X
<7> M_BO_NA_1
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X
<10> M_ME_TA_1 X
<11> M_ME_NB_1 X X X X
<12> M_ME_TB_1 X
<14> M_ME_TC_1 X
<15> M_IT_NA_1 X X
<16> M_IT_TA_1 X X
<17> M_EP_TA_1
<18> M_EP_TB_1 X
<19> M_EP_TC_1 X
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<32> M_ST_TB_1 X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1 X
<40> M_EP_TF_1 X
<51> C_BO_NA_1 X
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X
<106> C_CD_NA_1 X X X
<110> P_ME_NA_1 X
<111> P_ME_NB_1 X
CT-70 GTW/EN CT/C57


<112> P_ME_NC_1 X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1 X X
<136> M_DB_NA_1 X
<137> C_RC_NB_1 X X X X X X X X
8.1.6 BASIC APPLICATION FUNCTIONS

(station-specific parameter, mark ‘X’ if function is used)
Remote initialisation
between Reset User ASDU’s
⌧ Cyclic data transmission

Read procedure
Read procedure
Link state between Controlling and Controlled Station
Management of the COM lost (Problem detecting on the link)
Management of the COM recovering (Problem not detecting on the link)

(system or 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’ is used in both directions)
global
group 1 group 7 group 13
GTW/EN CT/C57 CT-71

group 5 group 11 Addresses per group have to be defined
group 6 group 12
(system or 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’ is used in both directions)
global
group 4
Notes:
– The controlled station does not report the change of hour by sending a clock synchronisation message (ASDU
103) to the controlling station.
– When the controlling station send to controlled station a clock synchronisation and if the system (includes
controlled station), isn’t synchronized by an other source : the clock synchronisation response is positive.
– When the controlling station send to controlled station a clock synchronisation and if the system (includes
controlled station), is synchronized by an other source : the clock synchronisation response is negative.
(object -specific parameter, mark each type ID ‘X’ if it is used)
Direct command transmission
Direct set point command transmission
Select and execute command
Select and execute set-point command
C_SE ACTTERM used
No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output
Note: Pulse duration can be defined in configuration. Short & long pulse bit on ASDU command is supported
by link level but not transmitted to application level.
CT-72 GTW/EN CT/C57


(station-specific or object -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’ is used in both directions)
Mode A: local freeze with spontaneous transmission
Mode B: local freeze with counter interrogation
Mode C: freeze and transmit by counter interrogation commands
Mode D: freeze by counter interrogation command, frozen values reported spontaneously

(object -specific parameter)
Counter read General request counter
Counter freeze without reset Request counter group 1
Counter freeze with reset Request counter group 2
Counter reset Request counter group 3
Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction, ‘R’ if only used in
Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured value

(object-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction, ‘R’ if only used in
Act/deactivation of persistent cyclic or periodic transmission of the addressed object

Test procedure
Test procedure
File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction
Transparent file
Transmission of disturbance data of protection equipment
Transmission of sequences of events
Transmission of sequences of recorded analogue values
GTW/EN CT/C57 CT-73

Transparent file
Background scan
Background scan

Digitals Inputs and Analogs Inputs, management events priorities.

See T101 standard Amendment 2, section 7.2.2.2

Class 1 data
The following types of information must be configured at the controlled station to be Class 1:
● Single point information with or without time tag (on change)
● Double point information with or without time tag (on change)
● Step position information with or without time tag (on change)
● Measured value, normalised with or without time tag (on change)
● Measured value, scaled with or without time tag (on change)
● Measured value, floated with or without time tag (on change)
● Integrated totals with or without time tag (on change)
● Time messages
● All command responses (ACT_CONF, and ACT_TERM)
Class 2 data
The following types of information must be configured at the controlled station to be Class 2:
● Single point information (GI scan, or BackGroundScan cycle)
● Double point information (GI scan, or BackGroundScan cycle)
● Step position information (GI scan, or BackGroundScan cycle)
● Measured values, normalised (GI scan, or Periodic cycle, or BackGroundScan cycle)
● Measured values, scaled (GI scan, or Periodic cycle, or BackGroundScan cycle)
● Measured values, floated (GI scan, or Periodic cycle, or BackGroundScan cycle)
● Integrated totals (Counter GI scan)
CT-74 GTW/EN CT/C57


The following IEC-60870-5-5 standard application processes are supported.
Station initialisation consists of a reset of the communications link (a Reset CU frame and Time
Synchronisation message are sent to the station), followed by a general interrogation of the controlled
station. Once this initialisation sequence is performed the controlling station can start the polling for data
report.
Communications to the controlled station must be re-initialised by the controlling station when the frame
repeat process has completed without successfully transmitting the frame (ie the frame time-out period times
the number of repeats).
If the controlled station fails to communicate with the controlling station then the controlling station should
perform a communications system initialisation for that controlled station.
Controlled station failure
If Activate ASDU 70 is configured, the controlled station indicates to the controlling station that it has
initialised by sending a frame indicating End of Initialisation with a Cause Of Initialisation (COI) field, which
identifies the reason for the initialisation in unbalanced mode only).
Data Acquisition by Polling
The default for all analogue values shall be reporting as Class 2 data (COT=1, periodic/cyclic, or COT = 2,
BackgroundScan cyclic).
Values returned as Class 2 data do not have a time tag (since they are constantly repeated).
The controlled station may return Class 1 data in response to a Class 2 request if no Class 2 data is
available and Class 1 data is awaiting transmission.
At the controlled station, if a request for Class 2 data is received and no data is available a negative
response, data not available, shall be returned to the controlling Station. The negative response may be a
fixed length frame (FC=9) or the Single Control Character (E5), which in this case is treated as a NACK.
By default C26x is polled by a “Polling C2” frame, allowing to get “non priority information”.
If C26x signals it has “priority information” (ACD bit set), it is polled with a “Polling C1” frame.
The default for all status changes are reported as Class 1 data (COT=3, spontaneous).
Values returned as Class 1 data have a time tag (either CP24Time2a, or CP56Time2a).
Status changes at the controlled station causes the ACD bit to be set in the next Class 1 or Class 2 data
response. The controlling station responds to ACD set by inserting a scan for Class 1 (spontaneous) data as
the next scan.
The response to a Class 1 data request has also the ACD bit set if more Class 1 data is awaiting
transmission. In this case a further scan for Class 1 data is scheduled by the controlling station.
Abnormal Acquisition of Events
At the controlled station, if a request for Class 1 data is received and no data is available an error should be
raised and a negative response, data not available, returned to the controlling Station. The negative
response shall be a fixed length frame (FC=9) or the single Control Character (E5), which in this case is
treated as a NACK (configurable).
The GI returns the current status information directly from the C26x database.
Time tags are NOT used for data items returned as part of the GI response.
The GI groups are NOT supported.
GTW/EN CT/C57 CT-75

The System (including the controlled station) may have different synchronisation sources (IRIG-B, SCADA).
When the controlling station sends to controlled station a clock synchronisation:
• if system isn’t synchronized by another source: clock synchronisation response is positive

• if system is synchronized by another source: clock synchronisation response is negative
Time stamping
All Class 1 data are time-tagged with:
• either the 3 bytes time-stamp (CP24Time2a), giving minutes & millisec within the hour,
• or the 7 bytes time-stamp (CP56Time2a), giving minutes, milliseconds, hours, day, month and year
according to the Computer configuration.
The invalid bit in the time-stamp is set when the time source is not available.
If the datapoint validity changes to “unknown” then it can be time-stamped as the latest received event or at
the date of the change.
All control commands are Select Before Operate or Direct Execute.
For only the control commands: Activation termination can be returned to the controlling station to signal the
end of a control sequence.
The QU field of the Qualifier of Command is set to zero (0), no additional definition.
The C26x can use the ASDU 137, which is a Regulating Delay Command. This ASDU allows the Gateway to
send a control with particular pulse duration. This message is available only for double contacts output or tap
changer controls, and is used with the Select before operate command procedure.
Test procedure
A test command may be issued by the controlling station to ensure the availability of the communications link
and the commands subsystem.
Test commands are received at the controlled station on the active link. The controlled station mirrors the
test command, on the link from which it was received, with a cause of transmission indicating activation
confirmation.
An error response should be sent if the command is incorrect, with a cause of transmission indicating
negative activation confirmation.
In the case of balanced mode, the controlled station may also send a test command to the controlling station,
to ensure the availability of the communications link as there is no polling made by the controlling station.
CT-76 GTW/EN CT/C57

9 COMMUNICATIONS WITH IEDS: LEGACY T104 MASTER

NETWORK
A Gateway can communicate as an IEC 60870-5-104 master with networked IEDs.
A Gateway may be connected to up to 4 * IEC 60870-5-104 networks.
Each network may contain up to 16 * IEC 60870-5-104 IEDs.
9.1 MASTER IEC 60870-5-104 PROFILE

The user interface presents sets of parameters and alternatives from which subsets have to be selected to
implement particular telecontrol systems. Certain parameters values, such as the choice of “structured” or
“unstructured” fields of the INFORMATION OBJECT ADDRESS of ASDUs represent mutually exclusive
alternatives. This means that only one value of the defined parameters is admitted per system.
The selected parameters are marked in the white boxes as follows:
Function or ASDU is NOT used
⌧ Function or ASDU is used as standardised (default)
Note 1: In addition, the full specification of a system may require individual selection of some parameters for some
parts of the system, such as the individual selection of scaling factors for individually addressable measured values.
Note 2: Reverse mode is NOT implemented.
9.1.1 APPLICATION LAYER

user interface.
One octet ⌧ Two octets

One octet ⌧ Structured
Two octets ⌧ Unstructured
⌧ Three octets
One octet ⌧ Two octets (with originator address)
GTW/EN CT/C57 CT-77

⌧ Structured ⌧ Unstructured
Length of APDU
The maximum length of APDU for both directions is 253. It is a fixed system parameter.
Selection of standard ASDUs
(station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
⌧ <1> := Single-point information M_SP_NA_1
<2> := Single-point information with time stamp M_SP_TA_1
⌧ <3> := Double-point information M_DP_NA_1
<4> := Double-point information with time stamp M_DP_TA_1
⌧ <5> := Step-position information M_ST_NA_1
<6> := Step-position information with time stamp M_ST_TA_1
<7> := BitString of 32 bit M_BO_NA_1
<8> := BitString of 32 bit with time stamp M_BO_TA_1
⌧ <9> := Measured value, normalised value M_ME_NA_1
<10> := Measured value, normalised value with time stamp M_ME_TA_1
⌧ <11> := Measured value, scaled value M_ME_NB_1
<12> := Measured value, scaled value with time stamp M_ME_TB_1
⌧ <13> := Measured value, short floating point value M_ME_NC_1
<14> := Measured value, short floating point value with time stamp M_ME_TC_1
⌧ <15> := Integrated totals M_IT_NA_1
<16> := Integrated totals with time stamp M_IT_TA_1
<17> := Event of protection equipment with time stamp M_EP_TA_1
<18> := Packed start events of protection equipment with time stamp M_EP_TB_1
<19> := Packed output circuit transmission of protection equipment with time stamp M_EP_TC_1
<20> := Packed single-point information with status change detection M_PS_NA_1
<21> := Measured value, normalised value without quality descriptor M_ME_ND_1
⌧ <30> := Single-point information with time stamp CP56Time2a M_SP_TB_1
⌧ <31> := Double-point information with time stamp CP56Time2a M_DP_TB_1
⌧ <32> := Step-position information with time stamp CP56Time2a M_ST_TB_1
<33> := Bistring of 32 bits with with time stamp CP56Time2a M_BO_TB_1
⌧ <34> := Measured value, normalised with time stamp CP56Time2a M_ME_TD_1
⌧ <35> := Measured value, scaled with time stamp CP56Time2a M_ME_TE_1
⌧ <36> := Measured value, short floating point number with time stamp CP56Time2a M_ME_TF_1
⌧ <37> := Integrated totals with time stamp CP56Time2a M_IT_TB_1
<38> := Event of protection equipment with time stamp CP56Time2a M_EP_TD_1
<39> := Packed start events of protection equipment with time stamp CP56Time2a M_EP_TE_1
<40> := Packed output circuit information of protection equipment with time stamp CP56Time2a M_EP_TF_1

⌧ <45> := Single command C_SC_NA_1
⌧ <46> := Double command C_DC_NA_1
⌧ <47> := Regulating step command C_RC_NA_1
⌧ <48> := Set point command, normalised value C_SE_NA_1
⌧ <49> := Set point command, scaled value C_SE_NB_1
CT-78 GTW/EN CT/C57

⌧ <50> := Set point command, short floating point value C_SE_NC_1

<51> := BitString of 32 bits C_BO_NA_1
<58> := Single command with time tag CP56Time2a C_SC_TA_1
<59> := Double command with time tag CP56Time2a C_DC_TA_1
<60> := Regulating step command with time tag CP56Time2a C_RC_TA_1
<61> := Set point command, normalized value with time tag CP56Time2a C_SE_TA_1
<62> := Set point command, scaled value with time tag CP56Time2a C_SE_TB_1
<63> := Set point command, short floating point value with time tag CP56Time2a C_SE_TC_1
<64> := Bitstring of 32 bit with time tag CP56Time2a C_BO_TA_1

⌧ <70> := End of initialisation M_EI_NA_1

⌧ <100> := Interrogation command C_IC_NA_1
⌧ <101> := Counter Interrogation Command C_CI_NA_1
<102> := Read command C_RD_NA_1
⌧ <103> := Clock synchronisation command C_CS_NA_1
⌧ <104> := Test command C_TS_NB_1
<105> := Reset process command C_RP_NC_1
<106> := Delay acquisition command C_CD_NA_1

<110> := Parameter of measured value, normalised 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
Special use (private range)

<136> := Database version M_DB_NA_1
<137> := Regulating delay command C_RC_NB_1

Shaded boxes are not required.
Mark type identification/cause of transmission combinations:
‘X’ if used only in the standard direction
‘R’ if used only in the reverse direction
GTW/EN CT/C57 CT-79

‘B’ if used in both directions

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<2> M_SP_TA_1
<4> M_DP_TA_1 X X
<6> M_ST_TA_1
<7> M_BO_NA_1
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X
<10> M_ME_TA_1 X
<11> M_ME_NB_1 X X X X
<12> M_ME_TB_1
<14> M_ME_TC_1 X
<15> M_IT_NA_1 X X
<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
<21> M_ME_ND_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<32> M_ST_TB_1 X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1
<40> M_EP_TF_1
<51> C_BO_NA_1
<58> C_SC_TA_1
<59> C_DC_TA_1
CT-80 GTW/EN CT/C57


<60> C_RC_TA_1
<61> C_SE_TA_1
<62> C_SE_TB_1
<63> C_SE_TC_1
<64> C_BO_TA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X
<106> C_CD_NA_1 X X X
<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
<121> F_SR_NA_1
<122> F_SC_NA_1
<123> F_LS_NA_1
<124> F_AF_NA_1
<125> F_SG_NA_1
<126> F_DR_TA_1
<127> C_RC_NB_1
9.1.2 BASIC APPLICATION FUNCTIONS

(station-specific parameter, mark ‘X’ if function is used)
⌧ Remote initialisation
between Reset User ASDU’s

Read procedure
Read procedure
⌧ Spontaneous transmission
GTW/EN CT/C57 CT-81

Double transmission of information objects with cause of transmission spontaneous

(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
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
(system or station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
⌧ Global
Group 1 Group 7 Group 13
Group 5 Group 11
Group 6 Group 12
Information object addresses assigned to each group must be shown in a separate table.
⌧ Clock synchronisation
Notes:
– The controlled station does not report the change of hour by sending a clock synchronisation message (ASDU
103) to the controlling station.
– When the controlling station sends the controlled station a clock synchronisation and if the system (includes
controlled station), is not synchronised by an other source: the clock synchronisation response is positive.
– When the controlling station sends the controlled station a clock synchronisation and if the system (includes
controlled station), is synchronised by an other source : the clock synchronisation response is negative.
(object -specific parameter, mark each type ID ‘X’ if it is used)
⌧ Direct command transmission
CT-82 GTW/EN CT/C57

⌧ Direct set point command transmission
⌧ Select and execute command
⌧ Select and execute set-point command
⌧ C_SE ACTTERM used
⌧ No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)

Persistent output
Note: Pulse duration can be defined in configuration. Short and long pulse bit on ASDU command is
supported by link level but not transmitted to application level.
(station-specific or object-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Mode A: local freeze with spontaneous transmission
Mode B: local freeze with counter interrogation
Mode C: freeze and transmit by counter interrogation commands
Mode D: freeze by counter interrogation command, frozen values spontaneously reported

(object -specific parameter)
Counter read ⌧ General request counter
Counter freeze without reset Request counter group 1
Counter freeze with reset Request counter group 2
Counter reset Request counter group 3
Request counter group 4

Parameter loading
(object-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured value

(object-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Act/deactivation of persistent cyclic or periodic transmission of the addressed object

Test procedure
GTW/EN CT/C57 CT-83

⌧ Test procedure
File transfer
(not implemented)
Background scan
⌧ Background scan
Definition of timeouts
t0 30 s Time-out of connection establishment
t1 15 s Time-out of send or test APDUs
t2 10 s Time-out for acknowledges in case of no data messages t2 < t1
t3 20 s Time-out for sending test frames in case of a long idle state
• Maximum range for timeouts t0 to t2: 1 s to 255 s, accuracy 1 s.

• Recommended range for timeout t3: 1 s to 48 h, resolution 1 s.
• Long timeouts for t3 may be needed in special cases where satellite links or dialup connections are
used (for instance to establish connection and collect values only once per day or week).
Maximum number of outstanding I format APDUs k and latest acknowledge APDUs (w)
Maximum difference receive sequence number to send state
k 12 APDUs
variable
w 8 APDUs Latest acknowledge after receiving w I format APDUs
• Maximum range of values k: 1 to 32767 (215–1) APDUs, accuracy 1 APDU

• Maximum range of values w: 1 to 32767 APDUs, accuracy 1 APDU
(Recommendation: w should not exceed two-thirds of k).
Port number
Parameter Value Notes
Portnumber 2404 In all cases
Redundant connections
Number N of redundancy group connections used
CT-84 GTW/EN CT/C57

9.1.3 LIMITS
Reverse mode is not implemented.
The following ASDU are not implemented:
• ASDU 7: Bitstring of 32 bits

• ASDU 102: Read command
• ASDU 105: reset process command
• ASDU 106: delay acquisition command
• ASDU 110 to 113 concerning Parameters in control direction
• ASDU 120 to 127 concerning File transfer
• ASDU 58 to 64: commands with time tag CP56Time2a (only commands without time-tag are
implemented)
9.2 SYSTEM FUNCTIONS

In order to establish a connection with an IED, the T104 Master sends a "STARTDT.act" frame. The IED
answers with a “STARTDT.con”. After it receives an "End of Initialisation" message, the T104 Master sends
a "General Interrogation" message and also a "Counter Interrogation" message if at least one counter is
configured.
There is no IED polling.
In the absence of I-frame transmission (“long idle state”), the T104 Master or the slave IED periodically
sends a "TESTFR" message to check whether the link is still active.
A Time Synchronisation message is sent upon each IED connection and every time synchronisation period.
A General Interrogation message is sent upon each IED connection.
Once this initialisation sequence is complete, the T104 master can wait for the data ASDU messages from
the slave IEDs.
A communication failure occurs when:
• The IED does not acknowledge a data transmission within a specific time-delay: ADPU timeout T1.
• No Test Link frame (TESTFR) is received within a specific time-delay: see ADPU timeout T1.
The communications link with the controlled IED is re-initialised by the controlling T104 master when the
frame repeat process was completed without successfully transmitting the frame (i.e.: the frame timeout
period * the number of repeats).
If the controlled IED fails to communicate with the controlling T104 master then the latter performs a
communications system initialisation for that controlled IED.
Controlled IED failure
Depending on the configuration, the controlled IED can let the controlling T104 master know that it has
initialised by sending a frame indicating End of Initialisation (ASDU 70) with a Cause of Initialisation (COI)
field, which will identify the reason for the initialisation.
Data Acquisition
The defaults for all analogue values are reported as data with COT=1 (periodic/cyclic) or COT=3
(spontaneous).
GTW/EN CT/C57 CT-85

The transmitted values do not have a time stamp (since they are constantly repeated).
The Slave sends spontaneously ASDU message, on BI change of state/quality or on MEAS and SPI change
of value/quality.
The default for all status changes are reported with COT=3 (spontaneous).
Transmitted Values shall have a time stamp (CP56Time2a).
Depending on configuration, time stamp reference can be Local or UTC.
The General Interrogation returns the current status information directly from the IED's database.
General Interrogation groups are not supported, only the global general interrogation is supported
Time stamps are not used for data items returned as part of a response to the General Interrogation.
Synchronisation
The T104 master uses ASDU 103 (CCSNA1) to synchronise the IEDs.
The first ASDU 103 is broadcast to the IEDs. Thereafter each synchronisation signal will be sent point to
point.
The IEDs are not synchronised during initialisation or disconnection.
The time stamp "invalid" bit is set to 1 when the IED is not synchronised or when the time source is not
available.
Time Stamping
In case of time-stamped ASDUs received by the gateway, the data (binary inputs, measurements, step
position indication and counters) are tagged with a 7-byte time stamp (CP56Time2a), giving minutes,
milliseconds, hours, day, month and year according to the Computer configuration.
If the datapoint validity changes to “unknown” then it can be time-stamped as the latest received event or at
the date of the change.
Test procedure
A test command (TESTFR) can be issued by the controlling T104 master to ensure the availability of the
communications link and the commands subsystem.
Test commands are received by the controlled IED via the active link. The controlled IED answers the test
command over the same link with the cause of transmission "acknowledgement of activation".
If the command is incorrect, an error response is sent with the cause of transmission "negative
acknowledgement of activation".
The controlled IED can also send a test command to the controlling T104 master to ensure the availability of
the communications link as there is no polling from the T104 master.
All the control/set point commands are set to either Select before Execute (SE) or Direct Execute (DE). The
protocol and system sides can be set independently to SE or DE.
For command requests, Activation termination (C_SE_ACTTERM) can be returned to the controlling T104
master to signal the end of a control sequence.
The QU field of the Command Qualifier is not taken into account.
CT-86 GTW/EN CT/C57

9.3.1 DATA RECEIVED FROM IEDS

Binary inputs
A BI is identified by an ASDU number: 1 and 30 for Single Point Status (SPS), 3 and 31 for Double Point
Status (DPS).
A BI is also identified by its configurable point information address.
Any change of state or quality is transmitted by the T104 master to the Gateway kernel.
If there is no change to the input or the validity, no received ASDU is forwarded to the gateway's kernel.
BIs without time stamp are time-stamped to the gateway's time.
If the IED has accepted the time synchronisation, the time stamp is considered synchronous, if it has not, it is
considered asynchronous.
Measured values
An MV is identified by an ASDU number: 9, 11, 13, 21, 34, 35, or 36.
An MV is also identified by its configurable information object address.
Any change in value or quality is transmitted by the T104 master to the gateway kernel.
3 MV formats can be transmitted using the T104 protocol: normalized (ASDU 9, 34 and 21), scaled (ASDU
11 and 35) and floating (ASDU 13 and 36).
If the IED has accepted the time synchronization, the time stamp is considered as synchronous, not
synchronous otherwise.
Step Position Indication
A SPI is identified by an ASDU number: 5 and 32.
A SPI is also identified by its configurable information object address.
Any change in value or quality is transmitted by the slave IED to the T104 master.
Counters
A CT is identified by an ASDU number: 15 and 37.
A CT is also identified by its configurable information object address.
Any change in value or quality is transmitted by the T104 master to the slave IED.
BitString 32-bits : not supported.
9.3.2 DATA SENT TO IEDS

Controls
A CO is identified by an ASDU number 45 for Single Point Command (SPC), 46 for Double Point Command
(DPC) and 47 for regulating step command.
A CO is also identified by its configurable information object address.
The acknowledgement of a control is expected to be an ASDU 45, 46 or 47 with an appropriate "Cause Of
Transmission" (activation confirmation, deactivation confirmation, activation termination).
GTW/EN CT/C57 CT-87

Set point Commands (SP)

A SP is identified by an ASDU number 48 (normalized), 49 (scaled) and 50 (floating).
A SP is also identified by its configurable information object address.
The acknowledgement of a control is expected to be an ASDU 48, 49 or 50 with an appropriate "Cause Of
Transmission" (activation confirmation, deactivation confirmation, activation termination).
9.4 REDUNDANCY MANAGEMENT

This section describes the behaviour of a typical system constituted by two redundant gateways and two
redundant IEDs. The Gateways and the IEDs communicate through an IEC 60870-5-104 link.
IEC 60870-5-104 communications is also called T104 in the diagrams of this section.
The two gateways are called GTW_1 and GTW_2.
The two IEDs are called IED_1 and IED_2.
The status of a gateway can be "Active" or "Standby". An active gateway can send commands and setpoints
to the IEDs. An active gateway must have an up-to-date configuration database. A standby gateway does
not have to send commands and setpoints to IEDs. Its database is not necessarily up-to-date.
The status of an IED can be "Active" or "Standby".
An active IED can control the electrical process, a standby IED cannot.
An active IED sends data in the monitor direction and receive commands and setpoints in the control
direction. A standby IED cannot transmit data in the monitor direction and cannot receive commands and
setpoints in the control direction.
Figure 1: Typical network connection
CT-88 GTW/EN CT/C57

Key:
• GTW1_L1N: Ethernet link #1 between GTW_1 and IEC 60870-5-104 Ethernet network #1
(IEC 60870-5-104_1).
(IEC 60870-5-104_2).
(IEC 60870-5-104_1).
(IEC 60870-5-104_2).
• IED1_LN: Ethernet link #1 between IED_1 and IEC 60870-5-104 Ethernet network #1
(IEC 60870-5-104_1).
• IED2_LN: Ethernet link #2 between IED_2 and IEC 60870-5-104 Ethernet network #2
(IEC 60870-5-104_2).
Note: An IED can be connected to one network only.
9.4.1 NOMINAL BEHAVIOUR
9.4.1.1 NOMINAL CASE 1: CONNECTION BETWEEN AN ACTIVE GATEWAY AND AN ACTIVE IED
State of GTW_1- IED_1 State of GTW_1- IED_2

GTW_1 GTW_2 IED_1 IED_2
connexion connexion
TCP OK TCP OK
Active StandBy Active StandBy
T104 stopped T104 stopped
STARTDT.act
STARTDT.con
T104 started
TESTFR.act
TESTFR.con
TESTFR.act
TESTFR.con
S1024ENa
Figure 2: Connection between an active gateway and an active IED - Sequence diagram
In this figure, all the TCP connections are assumed open and all the IEC 60870-5-104 connections are
assumed stopped.
• GTW_1 is the active Gateway and GTW_2 is the standby Gateway.

• IED_1 is the active IED and IED_2 is the standby IED.
GTW_1 initiates the IEC 60870-5-104 connection by sending a STARTDT.act to IED_1.
Since IED_1 is the active IED, it answers the STARTDT.act with a STARTDT.con to confirm the start.
From then on, it is assumed that the connection is established from an IEC 60870-5-104 point of view (the
GTW_1 to IED_1 connection state becomes OK).
GTW/EN CT/C57 CT-89

If there is no data transfer between the Gateway and the IED, either the gateway or the IED sends a
TESTFR.act message every T3 seconds, and the other answers with a TESTFR.con.
This exchange confirms that the TCP connection remains operational.
9.4.1.2 NOMINAL CASE 2: CONNECTION BETWEEN AN ACTIVE GATEWAY AND A STANDBY

IED
Figure 3: Connection between an active gateway and a standby IED - Sequence diagram
In this figure, all the TCP connections are assumed open and all the IEC 60870-5-104 connections are
assumed stopped.
• GTW_1 is the active Gateway and GTW_2 is the standby Gateway.

• IED_1 is the active IED and IED_2 is the standby IED.
GTW_1 initiates the IEC 60870-5-104 connection by sending a STARTDT.act to IED_2 which is the standby
IED.
Since IED_2 is the standby IED, it does not answer the STARTDT.act. This failure to answer informs GTW_1
that IED_2 is a standby IED.
GTW_1 starts the T1 time-delay after sending the STARTDT.act message. When T1 elapses without
receiving an answer from IED_2, GTW_1 closes its TCP connection with IED_2.
GTW_1 starts the "T0" time-delay.
After "T0" elapses, GTW_1 retries to establish a TCP connection with IED_2.
GTW_1 sends a TESFR.act to IED_2 and IED_2 answers with a TESTFR.con.
This exchange confirms that the TCP connection is again operational.
From then on, GTW_1 is able to know which IED_x is active by trying to initiate the IEC 60870-5-104
connection with IED_1.
CT-90 GTW/EN CT/C57

9.4.1.3 NOMINAL CASE 3: SWITCHOVER BETWEEN GATEWAYS

connexion connexion
TCP OK TCP OK
STARTDT.act
STARTDT.con
T104 started
TESTFR.act
TESTFR.con
TCP connection
TCP connection rejected
StandBy Active
Active close
TCP NOK
active open TCP OK
T104 stopped
STARTDT.act
STARTDT.con
T104 started
S1026ENa
Figure 4: Switchover between gateways - Sequence diagram
An IED cannot accept a TCP connection from a gateway if it is already communicating, from a TCP point of
view, with another gateway.
GTW_2 attempts to initiate an IEC 60870-5-104 connection with IED_1 while the latter is already
communicating with GTW_1. As a consequence of the above rule, a TCP connection between GTW_2 and
IED_1 is not allowed, so IED_1 rejects the connection attempt.
From a process point of view, GTW_1 is the active gateway and GTW_2 is the standby gateway, IED_1 is
the active IED and IED_2 is the standby IED.
When the switchover occurs, GTW_2 becomes the active gateway and GTW_1 becomes the standby
gateway.
GTW_2 then needs to establish an IEC 60870-5-104 connection with IED_1.
The TCP connection between GTW_2 and IED_1 remains unavailable as long as the TCP connection
between GTW_1 and IED_1 is still active.
It is therefore necessary to terminate the connection between GTW_1 and IED_1 in order to be able to
establish a connection between GTW_2 and IED_1. This is done by a TCP active close performed by
GTW_1.
GTW/EN CT/C57 CT-91

9.4.1.4 NOMINAL CASE 4: SWITCHOVER BETWEEN IEDS

connexion connexion
TCP OK TCP OK
STARTDT.act
STARTDT.con
T104 started
Startdt.act
Does not answer

to STARTDT
T1 TCP NOK
Active Close (TCP)
T0
Active Open (TCP)

TCP OK
Testfr.act
Testfr.con
StandBy Active
Active Close (TCP)
TCP NOK
T0
STARTDT.act
STARTDT.con
T104 started
Active Open (TCP)
TCP OK
S1027ENa
Figure 5: Switchover between IEDs - Sequence diagram
IED_1 was the active IED and becomes the standby IED. The switchover is due to an internal cause in the
IED.
The IEC 60870-5-104 must follow this switchover.
This figure shows an active close at the moment of the switchover. This active close has been initiated by
the new standby IED (IED_1).
Following the detection by GTW_1 of a disconnection between GTW_1 and IED_1, GTW_1 tries to establish
an IEC 60870-5-104 connection with IED_2. This first attempt fails. The gateway tries again to establish an
IEC 60870-5-104 connection with IED_2. This second attempt succeeds.
9.4.2 BEHAVIOUR IN CASE OF FAILURE
9.4.2.1 FAILURE CASE 1: DISCONNECTION OF GATEWAY 1-LINK 1 (GTW1_L1N) FROM THE

NETWORK
This failure can be worked around using a gateway switchover.
Since GTW_1 no longer has access to IED_1, GTW_2 may become active and establish an
IEC 60870-5-104 connection with IED_1.
Procedure:
GTW_1 detects the failure when a TESTFR.act (or any ASDU in the control direction) is not answered by
IED_1.
CT-92 GTW/EN CT/C57

GTW_1 declares GTW1_L1N failed by means of CommST (GTW_1, IED_1).

CommSt is transmitted to GTW_2 over the SBUS.
GTW_2 tries to establish a TCP connection to IED_1.
The remainder of the procedure is identical to that for "Nominal case 3":
GTW_2 transmits a STARTDT.act in order to establish the IEC 60870-5-104 connection with IED_1.
IED_1 answers GTW_2 with a STARTDT.con.
GTW_2 must then decide to become Active.
Detection time
The Maximum Time before detecting this failure is "T3" + "T1": if there is no activity on the connection
between GTW_1 and IED_1, GTW_1 waits for "T3" seconds before attempting to transmit a TESTFR.act.
Then, it waits for "T1" seconds before deciding that the answer TESTFR.con will never be received.
Gateway switchover time
The CommSt exchanges must have a defined periodicity. When the set time-delay elapses, GTW_2 can
decide to become the active gateway.
Condition
This switchover can happen only if IED_1 accepts the TCP connection from GTW_2. This could not be done
if IED_1 has not detected the connection failure between GTW_1 and IED_1.
9.4.2.2 FAILURE CASE 2: DISCONNECTION OF IED 1 LINK (IED1_LN ) FROM THE NETWORK
This failure can be worked around using an IEC 60870-5-104 connection of GTW_1 to the redundant IED
(IED_2) but an IED switchover is also mandatory in order to complete the connection.
Statement
Because of IED1_LN failure, both the connection between GTW_1 and IED_1 and the connection between
GTW_2 and IED_1 are no longer available.
Both gateways detect this failure in a maximum time of "T3" + "T1" for primary and the same + "Trf_time" for
secondary. ("Trf_time" is the delay to send data from a gateway to another).
As 2 TCP connections are not allowed by IED_1, GTW_2 must try to connect to IED_1 only after "T1" + "T3"
seconds max. After "T1" + "T3" seconds, GTW_1 has detected the failure of the link and IED_1 should have
done the same: GTW_1 and IED_1 perform an active close.
Procedure
If GTW_1 detects the link failure to IED_1 before GTW_2 does, GTW_1, as the active gateway, tries to
connect to IED_2. It sends a STARTDT.act to IED_2.
There are 2 cases: either the IED switchover has succeeded or not.
If the switchover has succeeded, then IED_2 answers GTW_2 with a STARTDT.con. The IEC 60870-5-104
connection is established between GTW_2 and IED_2.
If the switchover has not succeeded, then IED_2 does not answer to GTW_2. Then, GTW_1 tries to connect
to IED_2.
If no gateway has managed to connect to IED_2, RedSt indicates that no IEC 60870-5-104 connection is
established with IED_2. In that case, the active gateway must initiate a Nominal 1 procedure in order to
establish a connection.
9.4.2.3 FAILURE CASE 3: DISCONNECTION OF GATEWAY 1 LINK 2 (GTW1_L2N) FROM

NETWORK
Initial context
Each link is healthy.
GTW/EN CT/C57 CT-93

GTW_1 is the active gateway, GTW_2 is the standby gateway.

IED_1 is the active IED, IED_2 is the standby IED.
An IEC 60870-5-104 connection is initiated between GTW_1 and IED_1.
Failure Event: Failure of GTW1_L2N
There is no effect on the IEC 60870-5-104 connection between GTW_1 and IED_1.
Procedure:
Failure detection is done when a TESTFR.act is sent by GTW_1 to IED_2 and no answer is returned to
GTW_1.
GTW_1 signals a failure on link 2 by updating CommSt.
Then periodically, every "T0" seconds, GTW_1 tries to establish a TCP connection with IED_2. The detection
of a link failure by IED_2, between GTW1 and IED_2, occurs T3 + T1 seconds after the link failure. After that
time, IED_2 performs an active close on the link between GTW_1 and IED-2, and IED-2 is then able to
accept a TCP connection with GTW_2.
9.4.2.4 FAILURE CASE 4: DISCONNECTION OF GATEWAY 2 LINK 1 (GTW2_L1N ) FROM THE

NETWORK
Initial context
Failure Event: Failure of GTW2_L1N
There is no effect on on the IEC 60870-5-104 connection between GTW_1 and IED_1.
Procedure:
Because of the TCP connection between GTW_1 and IED_1, every attempt to establish a TCP connection
between GTW_2 and IED_1 is rejected by IED_1 (only one TCP connection is permitted).
Then periodically, every "T0" seconds, GTW_2 tries to establish a TCP connection with IED_1.
The disconnection can either be due to an Ethernet link failure or to a previous connection of another
gateway to IED_1.
9.4.2.5 FAILURE CASE 5: DISCONNECTION OF GATEWAY 2 LINK 2 (GTW2_L2N ) FROM THE

NETWORK
This case is similar to a TCP disconnection (case 3 or 4) where the IEC 60870-5-104 connection has not
been established.
9.4.2.6 FAILURE CASE 6: DISCONNECTION OF IED 2 LINK (IED2_LN ) FROM THE NETWORK
Initial context:
GTW_1 is connected to IED_2 by a TCP link.
Failure Event: Failure of IED2_LN
CT-94 GTW/EN CT/C57

Procedure
Because of the IED2_LN failure, both the connection between GTW_1 and IED_2 and the connection
between GTW_2 and IED_2 are no longer available.
Failure detection between GTW_1 and IED_2 takes a maximum of T1 + T3 seconds and then the failure
between GTW_2 and IED_2 is detected by GTW_2 when it tries to establish a TCP connection.
GTW_1 and GTW_2 signal a failure on link 2 by updating CommSt.
Then periodically, every "T0" seconds, GTW_1 and GTW_2 try to establish a TCP connection with IED_2.
9.4.2.7 FAILURE CASE 7: SHUTDOWN OF GTW_1

Initial context:
Procedure:
Because of a gateway failure, CommSt (GTW1, X) is no longer transmitted over the SBUS to GTW_2.
CommSt (GTW1, X) on gateway GTW_2 becomes invalid.
GTW_2 must then decide to become Active.
From then on, the procedure is identical to "Nominal case 3":
GTW_2 performs a STARTDT.act in order to establish the IEC 60870-5-104 connection with IED_1.
IED_1 answers GTW_2 with a STARTDT.con.
9.4.2.8 FAILURE CASE 8: SHUTDOWN OF GTW_2

Initial context:
Failure Event: Failure of GTW_2
Procedure:
Because of a gateway failure, CommSt (GTW2, X) is no longer transmitted over the SBUS to GTW_1.
CommSt (GTW2,X) on gateway GTW_1 becomes invalid.
9.4.2.9 FAILURE CASE 9: SHUTDOWN OF IED_1

This failure can be worked around by an IEC 60870-5-104 connection of GTW_1 to the redundant IED
(IED_2) but an IED switchover is also mandatory in order to complete the connection.
This failure is identical to case 2: a gateway cannot differentiate between a link failure on IED_1 and a failure
of IED_1.
9.4.2.10 FAILURE CASE 10: SHUTDOWN OF IED_2

This failure is identical to case 6.
GTW/EN CT/C57 CT-95

9.4.3 PRINCIPLES AND RULES
9.4.3.1 REDUNDANCY PRINCIPLES FOR GATEWAYS

Both redundant gateways update the following data about each TCP and IEC 60870-5-104 communications
link with each IED potentially managed by them:
• CommSt(Equipment_y)
• RedSt(Equipment_y)
CommSt
CommSt(Equipment_y) gives the state of the TCP communications link between the local gateway and the
IED_y.
CommSt(Equipment_y) has 2 attributes: State and Validity
State is OK if a TCP communications link between the local gateway and equipment_y is established (TCP
connection available).
State is NOK otherwise.
Validity is always OK on the local gateway. It can be NOK, on the receiving gateway, if the communications
link between the redundant gateways is down.
RedSt
RedSt(IED_y) gives the state of the IEC 60870-5-104 communications link between the local gateway and
IED_y.
RedSt(Equipment_y) has 2 attributes: State and Validity
State is ON if the IEC 60870-5-104 communications link between the local gateway and equipment_y is
established (STARTDT.con confirmed).
State is OFF otherwise.
Note: Even a confirmed TESTFR.con is not sufficient to declare an IEC 60870-5-104 communications link
established.
Validity is always OK on the local gateway. It can be NOK, on the receiving gateway, if the communications
link between the redundant gateways is down.
Each gateway sends the redundant gateway both CommSt() and RedSt() for each IED it manages. The
periodic transmission is done every "T_Exch" seconds. "T_Exch" is usually equal to 5 seconds (default
setting).
9.4.3.2 REDUNDANCY RULES

In order to enable the gateway switchover, the following rules should be observed by the gateway:
Rule 1:
Upon initialization, Gateway 1 has priority over Gateway 2. If both gateways are available to perform an
action, Gateway 1 acts and Gateway 2 waits.
Rule 2:
When a gateway detects a change on a link (TCP or IEC 60870-5-104), this gateway waits for 2 x "T_Exch"
seconds before deciding on an action.
Rule 3:
If both redundant gateways detect a TCP communication failure with the same IED, one gateway must try to
establish a connection with the redundant IED (STARTDT + general interrogation).
CT-96 GTW/EN CT/C57

Rule 4:
If during at least 2 x "T_Exch", a gateway (gateway A) detects a healthy TCP connection with an IED and
receive a CommSt from its redundant gateway (gateway B) indicating a connection failure with this IED, then
gateway A must try to establish the IEC 60870-5-104 connection with this IED.
Rule 5:
If a gateway has lost the communications link with its redundant gateway (all CommSt and RedSt are
invalid), this gateway must try to establish an IEC 60870-5-104 connection with all the IEDs (but only one of
each pair of redundant IEDs).
Rule 6:
When a STARTDT.con has been confirmed by an IED, the gateway must perform a general interrogation
GTW/EN CT/C57 CT-97

CT-98 GTW/EN CT/C57

INSTALLATION
GTW/EN IN/C57
DS Agile Gateway & WACU Installation
Contents
1 DS AGILE GATEWAY SOFTWARE INSTALLATION 3
2 CHECKING SOFTWARE INSTALLATION 16
3 AUTOSTART CONFIGURATION (OPTION) 18

3.1 Automatic Logging Configuration 18
3.2 Automatic start of the Gateway application 19
4 TIME SYNCHRONISATION WITH HOPF 22
5 INSTALLATION UNDER WINDOWS XP EMBEDDED 23

5.1 Flash disk partitioning 23
5.2 DS Agile Gateway software installation 23
5.2.1 File location 23
5.2.2 Registry 23
5.2.3 Shortcuts 24
5.2.4 Disk C protection against writing 24
6 ADDITIONAL INSTALLATION FOR DS AGILE WACU 26

6.1 Activation of ISAGRAF in the WACU 26
6.2 RTX installation 26
6.3 Installation of a WACU redundancy 33
6.3.1 Disabling system devices 33
6.4 Inter-WACU link installation 36
6.5 External hardware 36
6.6 BIOS setup 37
6.7 RTX2011 configuration 42
6.8 Configuration files and RTX start-up check 48
6.9 Redundancy check 53
6.9.1 Redundant link check 53
6.9.2 RTX processes and dll check out 53
6.10 Enabling USB controllers 54
GTW/EN IN/C57 IN-1

Installation DS Agile Gateway & WACU
IN-2 GTW/EN IN/C57

1 DS AGILE GATEWAY SOFTWARE INSTALLATION

On a standard PC and on an industrial PC, the operating system can be Windows XP or Windows 7 Ultimate
64 bits. On an embedded automation computer (DS Agile A301), the operating system is necessarily
Windows XP Embedded.
If a previous release of the DS Agile Gateway is already installed, save the registry (create a restoration
point), remove the previous release using the “Add/Suppress programs” item in the control panel. If a
previous version of SBUS Agency is installed, uninstall it (start menu).
Redundant architectures
In redundant architectures ("clusters"), both Gateways must have identical configurations:
• Hardware: same PC model and additional boards,

• Software: same Operating System version and same DS Agile Gateway software version,
• Configuration: same file names, installation paths, ports etc.
Steps specific to Windows 7

If the Gateway is being installed on a PC running Windows 7, extra steps must be taken to ensure that it is
installed and run by an administrator and NOT in Windows XP compatibility mode:
Set-up file:
1 Right-click on the file and select Properties
2 Make sure that Run this program in compatibility mode for: is NOT ticked
3 Make sure that Run this program as an administrator IS ticked
GTW/EN IN/C57 IN-3

4 Click Apply and close the window.

Executable file (after installation):
1 Repeat the above procedure but instead of closing the window, click Change settings for all users.
2 Make sure that Run this program in compatibility mode for: is NOT ticked
3 Make sure that Run this program as an administrator IS ticked
IN-4 GTW/EN IN/C57

Standard installation
1 Install SBUS Agency: refer to SBUS/EN IN.
2 Launch GTW_x.y.z.exe to install the DS Agile Gateway application (x.y.z is DS Agile Gateway’s
release number)
GTW/EN IN/C57 IN-5

3 Cycle through the screens (buttons Next).
4 Read the license agreement, select I accept the agreement and click Next.
IN-6 GTW/EN IN/C57

5 Select DS Agile 5.0.2 and onward (Pidd 3.0.3) and click Next.
6 In the Select Destination Location dialog box define the installation folder (the default installation
folder is C:\Program Files\DCS\Gateway).
GTW/EN IN/C57 IN-7

7 By default a full installation is proposed (IEC 61850 SBUS Protocol and all SCADA protocols except
GI74). With the check boxes select the components you want to be installed or clear the components
you do not want to be installed.
8 In the Select Start Menu Folder dialog box choose where you want the program's shortcuts.
IN-8 GTW/EN IN/C57

9 Select whether or not the Gateway software should start automatically and click Next.
10 In the Select Additional Tasks dialog box select whether or not to create a desktop icon.
GTW/EN IN/C57 IN-9

11 Check that the proposed settings are the correct ones and click Install.
12 If you selected SCADA Protocol OPC, the setup installs and registers OPC libraries and the server
OPC. Click OK. Do the same for these files: opchda_ps.dll, OPCProxy.dll and opc.dll.
IN-10 GTW/EN IN/C57

13 Depending on whether or not the Gateway software has been previously installed on the PC, this
screen may appear. If it does, click Cancel and confirm this choice in the resulting dialog box:
GTW/EN IN/C57 IN-11

14 If this is the first time that the Gateway software is installed, then Microsoft Visual C++2008
Redistributable should be installed:
IN-12 GTW/EN IN/C57

15 Click Next.
16 Read the License Terms, then tick I have read and accept the license terms. and click Install.
GTW/EN IN/C57 IN-13

17 Wait while the setup files are being extracted and installed.
18 Click Finish.
IN-14 GTW/EN IN/C57

19 The installation is complete. Unselect the Launch DS Agile Gateway check box and click Finish in
the two following cases:
you do not want to immediately launch the application
it is the 1st installation
For OPC, refer also to the chapter GTW/EN AJ.

In order to avoid the transmission of transitory states to the SCADA whenever the Gateway starts (or
switches into the operational mode), configure the timer timer_init in the registry (refer to the chapter
GTW/EN MF). To activate the timer, set a value different than 0.
During the start phase and until the timer expires, no message is sent to the protocols.
When the timer expires, the Gateway performs a general control and sends to the protocols all the
configured data. Data belonging to non-present equipment is set to “unknown” state with the Gateway time-
stamp (the time depends on the Gateway attribute Timestamped ‘unknown’ for SCADA).
GTW/EN IN/C57 IN-15

2 CHECKING SOFTWARE INSTALLATION

If you have installed the DS Agile Gateway under a directory named
Program Files\ALSTOM\DCS, the Gateway sub-directory looks like this:
IN-16 GTW/EN IN/C57

Note: The presence/absence of .dll files depends on which protocols have been installed:
• gi74.dll if the GI74 protocol (obsolete) is installed

• iec.dll if the IEC60870-5-101 protocol is installed
• iec104.dll if the IEC60870-5-104 protocol is installed
• cdctypeII.dll if the CDC Type II protocol (obsolete) is installed
• dnp3.dll if the DNP3 protocol is installed
• modbus.dll if the Modbus protocol is installed
• opc.dll, OPCSvr.dll and WtOPCSvr.dll if the OPC server protocol is installed
• sas.dll if the T101-SAS protocol (obsolete) is installed
• Projet101M.dll and Projet104M.dll for the T101 Master and T104 Master acquisitions
• prot_uca_iec.dll if the IEC 61850 protocol is installed
GTW/EN IN/C57 IN-17

3 AUTOSTART CONFIGURATION (OPTION)

The goal is that, at power-on, the Gateway application start automatically as soon as the operating system is
launched. Autostart can be selected during the setup process. If this was not the case, it can still be done
manually, as explained below.
3.1 AUTOMATIC LOGGING CONFIGURATION

To bypass the initial authentication:
1 In the control panel, select Users and Passwords
(alternative: run control userpasswords2).
2 In the Users tab, clear the “Users must enter a user name and password to use this computer”
check box:
3 In the Advanced tab, clear the “Require users to press Ctrl-Alt-Delete before logging on” check
box:
IN-18 GTW/EN IN/C57

3.2 AUTOMATIC START OF THE GATEWAY APPLICATION

This is possible only in the standard/professional variants of Windows XP and Windows 7. Under Windows
XP Embedded (embedded automation computer), a launcher adding a delay is also needed; please contact
Alstom. In order to add the Gateway shortcut to the Startup list:
1 Right click the icon of the DS Agile Gateway application: a sub-menu appears as shown in the figure
below.
2 Left click the item Copy
3 In Windows Explorer select the folder:

C:\Documents and Settings\Gateway User\Start Menu\Programs\Startup
4 (Assumption is made that the folder of the user is named Gateway User)
GTW/EN IN/C57 IN-19

5 Right click on this folder: a sub-menu appears as described in the following figure.
6 Left click on the item Paste. A shortcut to the DS Agile Gateway application is added to this folder.
IN-20 GTW/EN IN/C57

7 Restart the PC.
GTW/EN IN/C57 IN-21

4 TIME SYNCHRONISATION WITH HOPF

The HOPF 6039 board has two BNC sockets:
• an IRIG-B input connected to the GPS antenna

• an IRIG-B output that can be connected to a C26x to synchronize it
As no time accuracy is defined between the time provided by the SCADA and the time in the Master Clock,
the PC cannot be considered a Master Clock.
Use the documentation of the board for installation.
The date/time messages received from SCADA allows to update the Hopf clock. This facility is available for
CDC II (obsolete), DNP3 and T101 protocols through a register key: only one key can be activated, i.e. only
one protocol can update the Hopf board if the Gateway supports several protocols.
T101 protocol:
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy\Configuration]
Key: "Hopf_present" - This indicates if a HOPF 6039 is present or not: 0 not present; 1: present
DNP3 protocol:
[HKEY_CURRENT_USER\Software\DCS\Te\Dnp3\Protx_COMy\Configuration]
IN-22 GTW/EN IN/C57

5 INSTALLATION UNDER WINDOWS XP EMBEDDED

Usually a fanless PC (DS Agile A300) is delivered with Windows XP Embedded already installed. However,
if, for cybersecurity reasons, you have to partition the flash disk, read the section 6.1.
5.1 FLASH DISK PARTITIONING

For partitioning, you need:
• a USB disk with a Windows XP image created with Bart's PE Builder

• a screen
• a keyboard and mouse
Switch on the power supply, then switch on the PC.
In the first seconds, press F2 (generally) to enter the BIOS setup.
Modify the boot sequence: pass "First boot device" from "USB FDD" to "USB CDROM".
Cycle the power: Bart PE starts.
About 2 minutes later the á start button shows.
Click the á start button; this displays a ribbon with various items:
ALSTOM X
Programs X
About X
Shut Down X
In the folder ALSTOM X there are two items:
• Prepare Flash Media

• Copy XPEmbedded files
To prepare flash media click on Start/Alstom/Prepare Flash media. This cleans the flash disk and creates
two logical disks:
• C: is reserved for XP Embedded operating system; this disk is protected by Enhanced Write Filter
(EWF) to avoid writing on flash disk.
• D: is reserved for DS Agile Gateway software
5.2 DS AGILE GATEWAY SOFTWARE INSTALLATION

The installation of the DS Agile Gateway software is described in a previous section of this document.
Installation is similar to that of a standard PC except for the following items.
5.2.1 FILE LOCATION

When you select the installation folder choose "D:\Program Files\DCS\Gateway" instead of "C:\Program
Files\DCS\Gateway" folder.
Note: for the agency choose "D:\Program Files\DCS\" instead of "C:\Program Files\DCS".
5.2.2 REGISTRY
To create the DS Agile Gateway registry, launch the DS Agile Gateway software and install a database.
GTW/EN IN/C57 IN-23

Note: As registry is associated to "C:" partition and this partition will be write-protected, after modifying registry, you
must save modification using
"Ewfmngr c: -commit" command)
To set the keys, use the Registry Configuration Tool supplied in the package (or run regedit).
SOE file transfer with T101 or T104: by default the key is created with drive "C"; as "C:" is usually write-
protected (see further), change the value of the key drive to "D".
For other keys and KEMA compliance, refer to GTW/EN MF.
5.2.3 SHORTCUTS
If you add a shortcut on your desktop to C:\windows\system32\cmd.exe, don't forget to click on desktop with
right button, select "arrange icon by" check "show desktop icons".
5.2.4 DISK C PROTECTION AGAINST WRITING

The Enhanced Write Filter (EWF) protects a volume against write access. EWF provides the following
benefits:
• Write-protects one or more partitions on your system

• Enables read-only media, such as CD-ROM or flash, to boot and run
5.2.4.1 PROCEDURE TO SETUP EWF
On the D: we provide ewfntldr and ewf.reg files.
Installation is automatic:
1 Rename the c:ntldr file to ntldr.bak.
2 Move the d:\ewfntldr file to c:\ntldr.
3 Merge the file d:\ewf.reg by double-clicking on it.
4 Reboot the system.
Once the system boots, pull up a command line and run “ewfmgr C:”.
The output should be similar to this:
Protected Volume Configuration
Type RAM
State ENABLED
Volume ID C8 35 2A 0B 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
Max Levels 1
Clump Size 512
Current Level 1
Memory used for data 1294336 bytes
Memory used for mapping 4096 bytes
If instead you get an error stating that no EWF volume unplug any other hard drives, and restart. Ewfmgr
gives you some important information about your protected volume and tells you how much RAM your
overlay is taking up. That’s an important factor to keep in mind: the more changes you make to your
protected volume, the more RAM it’ll take up until you finally run out of memory. So be careful what you do to
your system with EWF running. Here are two important commands to remember:
ewfmgr c: -commitanddisable –live
• This will immediately disable EWF and commit all changes to the volume.
This should be done each time you modify the registry to adapt protocol library behavior to SCADA.
ewfmgr c: -enable
IN-24 GTW/EN IN/C57

• This will enable EWF on the next boot up.

The typical process for making persistent changes to your volume is to run the commitanddisable command,
make your changes, run the enable command, and restart
5.2.4.2 HOW TO TEST EWF ON REMOVABLE MEDIA

To easily test EWF, follow these steps:
1 Enable EWF: run the ewfmgr c: -enable command
2 Restart the computer
3 Modify something in the OS image
4 Restart the computer again
5 Verify that the modifications that you made in step 3 do not persist
GTW/EN IN/C57 IN-25

6 ADDITIONAL INSTALLATION FOR DS AGILE WACU
Note: The DS Agile Wide Area Control Unit (WACU) was formerly known as ISaGRAF Gateway (ISaGRAF GTW).
The first stages of installing a DS Agile WACU are identical to the Gateway installation described above.
The steps below should then be followed in order to complete the WACU installation and configuration.
6.1 ACTIVATION OF ISAGRAF IN THE WACU

When the WACU is installed, a “clef activation code isagraf.reg” file is provided (default path: C:\Program
Files\ALSTOM\DCS\Gateway\Conf\). Launch this file and define whether the computer will be used
with ISaGRAF or not:
• If the value is 1 (default value), ISaGRAF can be used, i.e. the device is a DS Agile WACU
• If the value is 0, ISaGRAF cannot be used, i.e. the device is a DS Agile Gateway
• If there no key is defined, the computer starts without ISaGRAF, i.e. the device remains a
DS Agile Gateway.
WARNING:
Do not try to download a database containing ISAGRAF logic schemes if the application
is not running in ISAGRAF mode as this case is not supported.
6.2 RTX INSTALLATION

This section describes the installation of the RTX 2011 Runtime Solo in both WACUs supporting ISaGRAF.
SP1 is optional.
1 Download the RTX2011 installer from the IntervalZero website in the URL
http://www.IntervalZero.com/rtx_purchased.htm
2 Open the archive and launch the executable RTX2011Setup.exe
3 Fill in the information fields especially:
the user email address to receive the licence number dedicated to the WACU
the PAC code supplied by IntervalZero
IN-26 GTW/EN IN/C57

4 If the WACU has an Internet connection, answer Yes to the question. Otherwise, answer No and skip
to step 7.
5 The PAC codes, machine ID and email address may have been filled in automatically. Select “Terms
& Conditions” to view the terms of the software license. Then tick the box “I agree with the [..] “ then
click on “GET LICENCE”, to obtain the license number dedicated to the Gateway (required to continue
with installation).
GTW/EN IN/C57 IN-27

IN-28 GTW/EN IN/C57

6 The license key, PAC number and identifier specific to the WACU is also sent by e-mail to the
previously entered address
7 If the WACU does not have an Internet connection, refer to the information in the dialogue box below.
GTW/EN IN/C57 IN-29

Using a PC with Internet access connect to

https://Licensing.IntervalZero.com/Licensing.aspx
and follow the instructions starting from step 2.

8 Enter the license key obtained
9 Enter the target folder for the installed files if the default folder does not match
IN-30 GTW/EN IN/C57

10 Select the default configuration (recommended)
11 Select the desired shortcuts and then click on “Install”
GTW/EN IN/C57 IN-31

12 When the installation is complete, re-boot the WACU.
IN-32 GTW/EN IN/C57

6.3 INSTALLATION OF A WACU REDUNDANCY
Warning:
WACU redundancy is only possible using embedded automation computers (Advantech
UNO-3074). It requires the installation of an additional network board. (See GTW/EN HW
for technical details on this board.)
The following steps describe how to add the board and configure the system consequently
6.3.1 DISABLING SYSTEM DEVICES

The following procedure describes how to arrange the IRQ addresses by disabling:
PCMCIA adapter Microsoft PS/2 Mouse USB Universal Host Controller - 24C4
In addition to BIOS settings, this will require arranging A400 IRQ addresses in order to obtain a dedicated
address for the NIC board.
Step Explanation Display
Open Device Manager.
There are several ways to access the Device
Manager in Windows XP. The quickest
method is to enter “devmgmt.msc” in the
“Start” Æ “Run” box.
01
Note:
Alternatively, right-click “My Computer” Æ
“Properties”, to bring up the “System
Properties” applet, and then click the
“Hardware” tab followed by the “Device
Manager” button.
Disable PCMCIA adapters by right-clicking Æ

02
“Disable”.
GTW/EN IN/C57 IN-33

Click “Yes” to confirm PCMCIA adapter

03
disabling.
As shown in the screenshot, the PCMCIA

04 adapter is now disabled (red cross over the
icon).
Disable Intel® 82801DB/DBM USB Universal

05 Host Controller - 24C4 by right-clicking Æ
“Disable”.
Click “Yes” to confirm Disable Intel®

06 82801DB/DBM USB Universal Host Controller
- 24C4 disabling.
IN-34 GTW/EN IN/C57

As shown in the screenshot, the Disable

Intel® 82801DB/DBM USB Universal Host
07
Controller - 24C4 is now disabled (red cross
on the icon).
Disable Microsoft PS/2 Mouse by right-

08
clicking Æ “Disable”.
Click “Yes” to confirm Microsoft PS/2 Mouse

09
disabling.
Click “Yes” to confirm restarting of the

10 DS Agile A4xx in order for changes to take
effect.
The PS/2 Mouse must be disconnected before restarting the DS Agile A400 in order to free
IRQ resources. It can be replaced by a USB Mouse.
Shutdown the DS Agile A400 BEFORE installing the NIC adapter.
GTW/EN IN/C57 IN-35

6.4 INTER-WACU LINK INSTALLATION

Electrical Warning
Æ Turn off the power supply and lock out the system power BEFORE opening the UNO-3074 chassis and
installing the NIC board. Refer to the PC User manual for other recommendations.
INTEL® PRO/1000 GT Desktop Adapter must be installed in the 4th PCI slot of the DS Agile WACU A400.
PS/2 connector
for keyboard
PCI slot numbers c d e f
6.5 EXTERNAL HARDWARE

USB ports situated on the DS Agile A400 front panel can be used by Project teams to:
• Connect the keyboard / mouse for local access

• Connect the software protection dongle
• Connect the memory stick / hard drive for data transfer
Figure 1 - USB connectors
The table below describes the USB interfaces’ capabilities:

USB Connectors
USB Interfaces USB1 USB2 USB3 USB4
Mouse × ×
IN-36 GTW/EN IN/C57

USB Connectors
Dongle × ×
Keyboard × ×
Removable hard drive or memory stick × × × ×
After setting the Windows XPe System Devices, it is still possible to connect a PS/2 keyboard for local
access through the PS/2 port situated on the DS Agile A400 front panel.
PS/2 accessories must be connected before the DS Agile A400 is powered ON.
The PS/2 splitter cable provided by Advantech with each DS Agile A300 box can be used but is not
mandatory for single keyboard use.
Figure 2 - PS/2 cable
Several software applications can be used to remotely access the DS Agile A400 (for file
transfer, monitoring, taking control…), for example:
Microsoft Windows "Remote Desktop Connection" (already included with Microsoft Windows
XP Pro & Embedded).
VNC server (to be installed before BIOS setting and shortcut to be added in Windows Start
menu).
6.6 BIOS SETUP

The following section describes procedure to set DS Agile A400 BIOS in order to assign IRQ addresses for
INTEL® PRO/1000 GT Desktop Adapter use with RTX real time software.
TO NAVIGATE IN THE BIOS SETUP UTILITY

To SELECT/ENTER a MENU/ITEM: press “Enter”.
To move the cursor between items: press s t u v arrows
To return to previous menu: press “ESC”.
GTW/EN IN/C57 IN-37

POWER-ON the DS Agile A400.

01 At system start-up, in order to enter the
BIOS setup utility, press “DEL”.
The following screenshot shows the main

menu of the BIOS setup utility.
02
Enter in the following menu:
- “Integrated Peripherals”.
Enter in the following menu:

03
- “OnChip IDE Device”.
IN-38 GTW/EN IN/C57

Disable the following item: “On-Chip

Primary PCI IDE”.
04
Back to the previous menu (refer to step
03).
Enter the following menu: “Onboard

05
Device”.
Enable the following items:

- “USB Controller”
06
- “USB 2.0 Controller”
- “USB Keyboard Support”
GTW/EN IN/C57 IN-39

Return to the main menu of the BIOS

setup utility (refer to step 02).
07
Enter the following menu: “Power
management Setup”.
Disable the following item: “MODEM Use

IRQ” (set to NA - Non Available).
Note:
08 As the HAL dedicated to UNO-3074 by
Advantech for XPe SP2 image is
“Standard PC”, the defaults settings
“ACPI Function” (but also “Power-Supply
Type”) do not have to be changed.
Enter in the following menu: “PnP/PCI

09
Configuration”.
IN-40 GTW/EN IN/C57

Set the following item: “Resources

Controlled By” to “Manual”.
10
Enter the following menu: “IRQ
Resources”.
Set the “IRQ-5” to “IRQ-10”: “assigned to”

11
: “PCI/ISA PnP”.
Press the F10 hotkey; or select the item

12
“Save & Exit Setup”.
GTW/EN IN/C57 IN-41


In order to save all the settings, in the
“SAVE to CMOS and EXIT” red window,
type “Y” then press “Enter”.
13
Note:
After “SAVE to CMOS and EXIT”
validation, the DS Agile A300 will
automatically reboot.
6.7 RTX2011 CONFIGURATION

At the Operating System start-up, Windows

XPe will detect automatically the new
Ethernet controller (INTEL® PRO/1000 GT
Desktop Adapter - previously added in the
01 4th PCI slot of the UNO-3074).
Windows XPe open “Found New Hardware
Wizard” and suggest board’s drivers
installation.
Click “Cancel”.
A pop-up window appears indicating that a

problem occurred during hardware
02 installation.
Ignore this message.
Open RTX 2011 properties window:

“Start” Æ “All Programs” Æ “IntervalZero” Æ
03 “RTX 2011” Æ “RTX Properties”
Or by “Start” Æ “Control Panel” Æ RTX
Properties”
IN-42 GTW/EN IN/C57

In order to configure INTEL® PRO/1000 GT

Ethernet board management by RTX 2011,
click the “Hardware” tab, then “Settings”.
04 This will open “Pnp Device Settings” window
which allows enabling and disabling device
management by RTX (as well as some
properties information).
“Ethernet controller” is displayed under the

tree showing the devices managed by
MS Windows XPe.
01. Right-click “Ethernet controller”.
02. Select “Remove RTX INF Support”.
03. Click “Apply”.
As shown in the screenshot, the icon
displayed next to “Ethernet Controller” has
been modified.
05
Note:
Due to an IntervalZero known bug for RTX
2011 introduced by SP1 it is necessary to
first remove RTX INF Support; and then
associate Ethernet Controller for it to be
taken into account.
For RTX 2011 release without SP1 or for
RTX 2011 release with SP1 Update: step
05-02 becomes “Add RTX INF Support”.
Then, click “Apply”, move to step 06 and
finally jump directly to step 09.
Warning message due to Ethernet Controller

removal from RTX 2011 management could
06 be displayed.
Just click “OK” to confirm.
GTW/EN IN/C57 IN-43

01. Right click “Ethernet Controller”.

02. Select “Add RTX INF support”.
07 04. Click the “Device Manager” button under
the device list. This action opens the
Microsoft XPe Device Manager windows.
05. Move directly to STEP 09.
01. Right click “Ethernet Controller”.

02. Select “Undo Removal of RTX INF
Support”.
Note:
In some cases, the same warning message
as in step 06 (but due to Ethernet Controller
management by RTX 2011) may be
08 displayed. Just click “OK” to confirm.
Then, click the “Device Manager” button

under the device list. This action opens the
Microsoft XPe Device Manager windows.
IN-44 GTW/EN IN/C57

The Device Manager window shows the

devices implemented in the DS Agile A400.
Ethernet Controller is displayed under “Other
devices”. This is due to the fact that the
09
associated driver must be installed (see step
02).
Right-click “Ethernet Controller” and click
“Update Driver”.
The Hardware Update Driver procedure

begins.
10 Select the following radio button:
“No, not this time”
Then, click “Next”.
Select the following radio button:

“Install from a specific list or specific location
11
(Advanced)”
GTW/EN IN/C57 IN-45

Select the following radio button:

“Don’t search, I will chose the driver to
12
install”
Scroll down the bar in order to select the

following item:
13
“RTX Drivers”
Click “Show compatible hardware” if it is not

already selected.
14 Click “Ethernet Controller RTX Supported” if
it is not already selected.
IN-46 GTW/EN IN/C57

The software “Ethernet Controller RTX

Supported” is installed by the Hardware
Update Wizard.
15
This will allow the INTEL® PRO/1000 GT
Ethernet board to be managed by RTX
2011.
The Hardware Update Driver procedure is

16 now finished.
Click “Finish” in order to close the wizard.
The DS Agile A400 must be rebooted in

order the change take effect.
If a dedicated window appears, click

“Yes” in order to restart the gateway.
Otherwise reboot it.
After reboot, by running the Microsoft

Windows XPe Device Manager (refer to
§6.3.1 Disabling system devices – step 01),
18
it is now possible to show the INTEL®
PRO/1000 GT Ethernet board managed by
RTX.
GTW/EN IN/C57 IN-47

By opening RTX2011 “Pnp Device Settings”

(refer to §6.7 RTX2011 configuration – step
01), it is now possible to show the INTEL®
19 PRO/1000 GT Ethernet board managed by
RTX.
Right click “Ethernet Controller” and click
“Properties”.
Information regarding INTEL® PRO/1000

GT Ethernet board are displayed in the “RTX
PCI Device Properties” window.
20
It is possible to see that the IRQ address 11
is exclusive to the Ethernet board and
dedicated to RTX management.
6.8 CONFIGURATION FILES AND RTX START-UP CHECK

Two files dedicated to redundancy must be checked on both gateways:
• RtxTcpIp.ini
• rdnpars.txt
By default the current path is C:\Program Files\ALSTOM\RDN_GTW.
IN-48 GTW/EN IN/C57

Step Description Display
- Open the file rdnpars.txt

- Check the parameters:
auxlinitimeout = 5
auxltimeout = 4000
maxresources = 1
01 unit = 1 (for the main WACU)
Note:
For the redundant WACU, the “rdnpars.txt”
configuration file has to be set
with the following unit number:
unit = 2 (for the secondary WACU)
- Select Start > All Programs > IntervalZero > RTX

2011 > RTX Properties. This opens the RTX 2011
properties window
- Select the tab TCP/IP
- Check the boxes “Enable RT-TCP/IP support” and
02 “Run in verbose mode”
- Browse to RtxTcpIp.ini in the GTW installation
directory (the text area shows by default <current
path>\RtxTcpIp.ini)
- Check the parameters in RtxTcpIp.ini:

NumOfInterfaces=1
Driver=RTE1000
03
IPAddr=192.168.10.1 for WACU 1, 192.168.10.2
for WACU 2
Netmask=255.255.255.0
- Close the file

- Click Apply in the Properties window
04
- Click OK to acknowledge a warning message and
wait for a while
GTW/EN IN/C57 IN-49

- Select the tab System

- Set the RTX Subsystem automatically start up at
Windows Xpe Start-up to Automatic (System
05 Startup)
- Click Apply
- Select the tab Control

- Click Start; this starts the drivers and opens a
06
RTXServer log console
07 The RTX 2011 drivers are starting.
IN-50 GTW/EN IN/C57

08 RTX Drivers are running.
NOTE:
RTXServer log window automatically open when
RTX drivers start.
It is possible to see Ethernet board well
configuration.
Launch Microsoft Windows XPe

MS-DOS window “Command Prompt”:
The quickest method is to enter “cmd” in the “Start”
Æ “Run” box.
Or, it is possible to access by
“C:\WINDOWS\system32\cmd.exe”
01. Under “C:\” ; type:
C:\Program Files\IntervalZero\RTX\ bin\rtsskill
It is possible to see that “RtE1000.rtdll” driver used
09 for INTEL® PRO/1000 GT Ethernet board
management is well loaded.
NOTE:
No RTSS process is currently running because the
WACU is not launched.
GTW/EN IN/C57 IN-51

- 02. Under C:\, type: C:\Program Files\

IntervalZero\RTX\bin\rtssrun rtssipconfig.rtss
- on the RTXServer log console, check out the
WACU RTX RT-TCP-IP Address Configuration

10 127.0.0.1 (interface loopback address)
WACU own ping response under RTX

192.168.10.1
WACU own ping response under RTX
IN-52 GTW/EN IN/C57

6.9 REDUNDANCY CHECK
6.9.1 REDUNDANT LINK CHECK

A link has been established as described in the chapter GTW/EN CO.
STEP DESCRIPTION DISPLAY
- Run cmd in the Start>Run to launch the

MS-DOS console
- Under C:\, type: C:\Program Files\
01 IntervalZero\RTX\bin\rtssrun rtssipconfig.rtss
192.168.10.2
- on the RTXServer log console, check out the other
WACU’s ping response under RTX
6.9.2 RTX PROCESSES AND DLL CHECK OUT

STEP DESCRIPTION DISPLAY
- Under C:\, type: C:\Program Files\

01 IntervalZero\RTX\bin\rtsskill
- Check out the active RTSS processes and RTDLLs
GTW/EN IN/C57 IN-53

6.10 ENABLING USB CONTROLLERS

If a USB controller has been disabled, re-enable all USB items as described below.
STEP EXPLANATION DISPLAY
Open the BIOS setup utility.

Open the following menu:
01
- “Integrated Peripherals”
- “Onboard Device”
Enable the following items:

- “USB Controller”
02 - “USB 2.0 Controller”
- “USB Keyboard Support”
Save changes to the BIOS setup

03
utility by pressing the F10 hotkey).
IN-54 GTW/EN IN/C57

ADJUSTMENTS
GTW/EN AJ/C57
DS Agile Gateway & WACU Adjustments
Contents
2 SCADA PROTOCOL OPC 4

2.1 DCOM Configuration for Windows 2003 Server 4
2.2 DCOM Configuration for Windows XP 12
2.3 DCOM Configuration for Windows 7 14
3 ISAGRAF ADJUSTMENTS FOR A REDUNDANCY CLUSTER 18
GTW/EN AJ/C57 AJ-1

Adjustments DS Agile Gateway & WACU
AJ-2 GTW/EN AJ/C57


This document is a chapter of the DS Agile Gateway documentation. It describes the DCOM adjustments
required by the SCADA OPC protocol. It is of no use if this protocol is not used.
GTW/EN AJ/C57 AJ-3

2 SCADA PROTOCOL OPC

OPC libraries use DCOM technology and need to be registered in order to be found by a local or a remote
system.
The DS Agile Gateway setup installs and registers these libraries (only for Data Access).
2.1 DCOM CONFIGURATION FOR WINDOWS 2003 SERVER

Run dcomcnfg.exe application to configure permissions. By default, we configure it with all rights and control
allowed. When the DS Agile Gateway behaviour will be checked, rights may be changed to match
customers' requirements.
When running the DCOM configuration application, you normally must see the DS Agile Gateway entry
named “OPC DATA IMPLEMENTATION” as in the following snapshot:
Select the Default Properties tab and match the configuration as below:
AJ-4 GTW/EN AJ/C57

Select the Default Security tab and do the following:

In the Default Access Permissions frame add Everyone and INTERACTIVE entries and allow access
In the Default Launch Permissions frame add Everyone and INTERACTIVE entries and deny launch for
every items
GTW/EN AJ/C57 AJ-5

In the Default Configuration Permissions frame add Everyone and INTERACTIVE and give full control
AJ-6 GTW/EN AJ/C57

GTW/EN AJ/C57 AJ-7

In Applications sheet, select OPC DATA IMPLEMENTATION and click on Properties. Then set the
different sheets as the following snapshots:
In the General tab check that the DS Agile Gateway application is in your working directory
In the Location tab choose Run application on this computer:
AJ-8 GTW/EN AJ/C57

In the Security tab select Use default access permissions for access and launch and Use custom
configuration permissions for configuration permissions.
Edit the custom configuration permissions and give the permissions for the Registry Key
Don’t forget to click on the Apply button
GTW/EN AJ/C57 AJ-9

AJ-10 GTW/EN AJ/C57

In the Identity tab select The interactive user:
In the Endpoints tab add default system protocols
GTW/EN AJ/C57 AJ-11

2.2 DCOM CONFIGURATION FOR WINDOWS XP

Run DCOMcnfg
1 In the "Components°Services" dialog box select ConsoleRoot\Components Services\Computers
2 In the control panel right click on My Computer and select the Properties sub-menu item
3 In the "My Computer Properties" dialog box select the "COM Security" tab
AJ-12 GTW/EN AJ/C57

4 In the Access Permissions frame left click on the Edit Limits button
5 For "ANONYMOUS LOGON" allow "Local Access" and "Remote Access" then left click on "OK"
6 In the Launch and Permissions frame left click on the Edit Limits button
7 For "Everyone" deny "Local Launch", "Remote Launch" then left click on "OK"
GTW/EN AJ/C57 AJ-13

2.3 DCOM CONFIGURATION FOR WINDOWS 7
1 In the Control Panel, select System and Security/Administrative Tools/Component Services:
2 Right click on the My Computer icon to display the contextual menu, select "Properties".
3 Select the “Default Properties” tab in the My Computer Properties window.
4 Verify that the following default properties are checked and selected. This should be the case by
default:
Enable Distributed DCOM on this computer should be ticked.
The Default Authentication Level should be Connect.
The Default Impersonation Level should be Identify
AJ-14 GTW/EN AJ/C57

5 In the tab COM Security, check the settings for Edit Limits for Access Permissions & for Launch
and Activation Permissions. These adjustments control security permissions related to objects,
accessed or launched locally/remotely by programs.
6 Click on the "Edit Limits” button under "Access Permissions". The default values are ANONYMOUS
LOGON for Local Access and Everyone for Local and Remote Access.
Note: There is no need to change the default values of the “Edit Default…” for ”Access” & “Launch and Activation”
permissions.
GTW/EN AJ/C57 AJ-15

AJ-16 GTW/EN AJ/C57

7 Click on the Edit Limits button under Launch and Activation Permissions. The default values are
MACHINE\Administrators for Local and Remote Launch and Local and Remote Activation, and
Everyone for Local Launch and Local Activation:
GTW/EN AJ/C57 AJ-17

3 ISAGRAF ADJUSTMENTS FOR A REDUNDANCY CLUSTER

To connect ISaGRAF workbench to both redundant targets (for example in the aim of target loading, debug
or monitoring…), it is possible to set network properties with mirror target IP addresses.
- In Hardware architecture, select the

connection between the ETCP process and
01 the configuration
- Right-click it and select Properties
- Set the target 1 IP address in the tab

Network Parameters
02
- Select the tab Mirror targets

- Click the button Add and set the target 2 IP
address
03
- Click to build/rebuild project
library; this takes into account the addresses
AJ-18 GTW/EN AJ/C57

- Connect to either station using or
(respectively Download, Debug Target,

Simulation); the mirror targets show
- Check one of the listed out targets
GTW/EN AJ/C57 AJ-19

AJ-20 GTW/EN AJ/C57

LOGIC DIAGRAMS
GTW/EN LG/C57
DS Agile Gateway & WACU Logic Diagrams
Contents
1 INTERNAL AUTOMATION 3
2 COMMAND PROCESSING 5
GTW/EN LG/C57 LG-1

Logic Diagrams DS Agile Gateway & WACU
LG-2 GTW/EN LG/C57

1 INTERNAL AUTOMATION
The DS Agile Gateway operates as an IEC 61850-8-1 application. The operating modes can be described as
follows:
Power on or Reset
INITIALISATION
[Init OK]
and [Init OK]
[Current DB not valid] and
[Valid current DB]
Run and [valid current DB] Switch DB

or [Switch DB performed] and
DB unchanged
MAINTENANCE OPERATIONAL
Switch DB
Stop
or (Switch DB and [DB changed])
or [DB processing failure]
or [Loss of communication and Key "maintenance_if_dcnx_ethernet" = 1]
Major fault
XXXX: operator order (from SMT)
[yyyy]: application event/status
HALT mode not visible from the network FAULT
Key "maintenance_if_dcnx_ethernet" is described in section 2.1 of chapter Maintenance (GTW/EN MF) S0137ENd
Figure 1: Operating modes of the gateway
Modes:
 INIT: transitory mode not seen from the network, OS starting, Application starting
SBUS starting: Check servers, Subscribe servers with the same DB version
PROT DLL starting: starts one protocol DLL by protocol defined in DB (if exists & valid)
 MAINTENANCE: Database error (coherency, system revision), DLL error.

 OPERATIONAL: this mode can be qualified as OK or downgraded. Downgraded corresponds to a
redundant application failure in case of redundant configuration.
Database downloading is possible in Maintenance and Operational modes.
Application event/status:
 Valid Current DB: the Application owns a Current ApplicationDataBag, which is valid (correct
signature).
 DB Changed: the Stand-by ApplicationDataBag is different from the Current one (this is known by the
Application).
 DB Unchanged: the Stand-by ApplicationDataBag is the same as the Current one (this is known by
the Application).
 Switch DB performed: the new Current ApplicationDataBag has been correctly processed.
 DB processing failure: the Current ApplicationDataBag processing has failed.
GTW/EN LG/C57 LG-3

Operator orders (received from the System Management Tool in point-to-point exchange):
 Stop
 Run
 Switch DB: Stand-by DB becomes Current, and vice-versa
For more details about IEC 61850-8-1 applications, refer to the DS Agile SII reference document.
LG-4 GTW/EN LG/C57

2 COMMAND PROCESSING
The SCADA's commands are translated into IEC 61850-8-1 controls:
DS Agile
G
SCADA T System
W
Commands Controls
Figure 2 : Command processing
By configuration (dependencies), it is defined which SCADA controls are accepted and refused.
GTW/EN LG/C57 LG-5

LG-6 GTW/EN LG/C57

APPLICATION
GTW/EN AP/C57B
DS Agile Gateway & WACU Application
Contents
2 REQUIREMENTS 4
3 DS AGILE GATEWAY CONFIGURATION SCOPE 5

3.1 General DS Agile system configuration 5
3.2 DS Agile Gateway configuration 5
3.3 Sparing an object 6
4 DEFINING A DS AGILE GATEWAY CONFIGURATION IN THE SYSTEM

HIERARCHY 8
4.1 Adding a Gateway in the system hierarchy 8
4.2 Configuring the Gateway 9
4.2.1 General attributes 9
4.2.2 Communication channels 9
4.3 Creating a backup gateway 11
4.4 Networking a Gateway on the station-bus network 11
4.4.1 Connecting a Gateway to other station-bus sub-systems 11
4.4.2 Defining addressing mapping of station-bus network 13
4.4.3 Addressing datapoint on station-bus network 14
4.5 Networking IEDs on a Gateway's legacy network 14
4.5.1 Creating a legacy network of IEDs 14
4.5.2 Defining the address map of a legacy IED 20
4.6 Networking a SCADA on a Gateway's SCADA network 21
4.6.1 Creating a SCADA network 21
4.6.2 Defining the address map of a legacy SCADA network 36
4.6.3 Addressing a datapoint on a SCADA legacy network 62
4.7 Setting system information for Gateway components 62
4.7.1 Setting the general system information of a Gateway 64
4.7.2 Setting system information of PLC 65
4.7.3 Setting system information of SCADA network 65
5 DEFINING A DS AGILE GATEWAY CONFIGURATION IN THE ELECTRICAL

HIERARCHY 67
5.1 Defining Substation and Bay Local/Remote dependencies 67
5.1.1 Introduction 67
5.1.2 Setting the ‘Local/remote dependencies’ attributes of a control datapoint 67
5.2 Defining the SBMC mode for a bay 69
5.2.1 Introduction 69
5.2.2 SBMC state indication: Main topologies 69
5.2.3 Setting the ‘SBMC dependency’ attribute of a control point 79
5.3 Defining Taking Control for substation and SCADA links 79
5.4 Defining FFS (Force/Suppress/Substitute) processing for datapoints 81
6 DEFINING AN IEC61850/IEC61850 GATEWAY CONFIGURATION 82

6.1 Configuring the gateway in the lower network 83
GTW/EN AP/C57b AP-1

Application DS Agile Gateway & WACU
6.2 Configuring the gateway in the upper network 85
7 ISAGRAF IN A WIDE AREA CONTROL UNIT (WACU) 89

7.1 Defining an ISaGRAF project 89
7.1.1 Create a bay managed by the WACU 89
7.1.2 Defining an ISaGRAF slow automation 90
7.2 Specific ISaGRAF for redundancy cluster 90
AP-2 GTW/EN AP/C57b


The present document is a chapter of the DS Agile Gateway documentation binder. This document teaches
you how to configure DS Agile Gateway.
GTW/EN AP/C57b AP-3

2 REQUIREMENTS
First, if it is not already done, you will need to install the DS Agile SCE (System Configuration Editor), see the
chapter IN (Installation) of this product.
This document presents the objects and the attributes of a referenced database made with the DS Agile
SCE. For understanding this document you first need to be familiar with DS Agile SCE.
Moreover, this document only describes the part of the configuration relating to DS Agile Gateway-specific
functionality, i.e. datapoint real-time values and controls transmitted to and from the SCADA. These
datapoints are globally produced and managed by other DS Agile sub-systems mainly DS Agile C26x
controllers. So, the configuration of datapoints, and by extension of the substation electrical topology where
datapoints are attached are pre-requirequisites to Gateway configuration. They are not described is the
present document, but in the DS Agile C26x application chapter (C26x/EN AP). Nevertheless, some items of
datapoint and electrical topology configuration can be repeated and developed in the present document as
far as Gateway functionality are concerned by.
To add a DS Agile Gateway into an existing system you need to have the mapping of the system (IP
address, Network names of equipment…).
To generate a template, for an existing Gateway, refer to the chapter SCE/EN HI (menu Tools).
AP-4 GTW/EN AP/C57b

3 DS AGILE GATEWAY CONFIGURATION SCOPE
3.1 GENERAL DS AGILE SYSTEM CONFIGURATION

To define a complete DS Agile system, three aspects should be taken into account.
The first one is the system topology. It consists of device composition that manages the customer’s electrical
process. Generally, this is supplied by ALSTOM and corresponds to ALSTOM system process definition to
respond customer’s needs.
The second one is the electrical topology. It consists of the customer’s electrical process definition in term of
typed electrical devices (transformer, disconnector, circuit-breaker…) that are connected each other through
busbars or lines. Generally, this is supplied by the customer.
The third one is the graphical topology. It consists of the mimic and their graphical animation descriptions
that appear at substation control points (operator interface) and bay control points (DS Agile C26x controller
local HMI).
When creating a new configuration using SCE, these 3 topologies are automatically instantiated via root
objects:
 A ‘Site’ object for the electrical topology, containing one ‘Substation’ object
 A ‘Scs’ object for the system topology, containing one ‘Station network’ object (Scs is an abbreviation
of Substation Control System)
 A ‘Graphic’ object for the graphical topology.
Figure 1: General architecture of a DS Agile configuration in SCE
3.2 DS AGILE GATEWAY CONFIGURATION

In the general DS Agile system configuration, the Gateway is concerned by these two topologies:
 System topology (Scs):

As of DS Agile version 5.0.5, there are only 2 types of objects at the root of the Ethernet network in the
System hierarchy:
 the SMT (System Configuration Tool): The SMT object is unique. It is automatically added when a
database is created (as of DS Agile version 5.0.4) or imported from an earlier version (before
DS Agile version 5.0.4), and must be configured (see SMT/EN AP for details),
 the System Group: The System group contains the devices managing, monitoring and/or
protecting one or more electrical bays.
The Gateway is a direct sub-component of the System Group.
 Electrical topology (Site): the Gateway's behaviour depends on substation and bay mode facilities.
GTW/EN AP/C57b AP-5

3.3 SPARING AN OBJECT

At DS Agile SCE level, a spare object is an object created for possible ulterior use or in order to disable an
HMI command.
The label of a spare object is displayed in gray italic text in the Explorer window. The configuration of this
object and of its spare attribute is the same as that of any other object and attribute.
To configure an object as spare, simply set its ‘spare’ attribute to 'Yes'.
Any object can be spared, including those used in the gateway's configuration.
Spare objects are not passed on to the generator tools.
Object sparing follows these two rules:
 Objects O2, O3, O4, etc., not individually spared, are considered as spare objects if they are linked,
directly or not, to a spare composite parent object (O1):
O1 (Spare = Yes) is equivalent to: O1 (Spare = Yes)
O2 (Spare = No) O2 (Spare = Yes)
S0387ENb
AP-6 GTW/EN AP/C57b

 A relation defined on an object O1, not spare, and linked to a spare object O2, is considered as a
relation with no link:
GTW/EN AP/C57b AP-7

4 DEFINING A DS AGILE GATEWAY CONFIGURATION IN THE

SYSTEM HIERARCHY
4.1 ADDING A GATEWAY IN THE SYSTEM HIERARCHY

To add a Gateway definition, at System Group level, under Ethernet network, right-click IEC61850 gateway
in the “Objects entry” area and select Add (alternative: double-click IEC61850 gateway ):
Figure 2: Adding a Gateway
Default components of a Gateway

On addition, SCE prompts to enter the substation name via the mandatory relation “is located in“ and shows
binders:
 Hardware, that groups all available communication channels of the Gateway

 System infos, that groups the general system datapoints of the Gateway (see section 4.7 Setting
system information for Gateway components)
 PLC, that hosts one system datapoint, dedicated to automation
Figure 3: Default components & general attributes of the Gateway
AP-8 GTW/EN AP/C57b

4.2 CONFIGURING THE GATEWAY
4.2.1 GENERAL ATTRIBUTES

When adding a Gateway on Ethernet network, some of its attributes must be set:
 short name and long name: used for logging, alarms, …

 timestamped ‘unknown’ for SCADA (No / Yes): defines the way datapoints are time-stamped when
the Gateway connects to a Station Bus server (after a loss of communication with this server). If set to:
 No, the datapoints are time-stamped with the ACQUISITION time (which can precede the loss of
communication)
 Yes, the datapoints are time-stamped with the CONNECTION time (in this case the acquisition
time-stamp provided by the station bus server is lost)
 GI74 usage (No / Yes): indicates if GI 74 protocol is used at Gateway level. Use the default value. The
value ‘Yes’ must not be used. It is still proposed for maintenance
 Acquisition available on IEC61850 (No / Yes): Default value: No. Set it to Yes in the lower ring of an
IEC 61850/IEC 61850 architecture; refer to section 6.1
 TCP/IP address and network name

Configuration rules and checks
 The "TCP/IP address" value of a device, must be unique among all the devices per Ethernet Network
(except for OI server and OI client). It is the TCP/IP address on the SBUS
 The "network name" value of a device, must be unique among all the devices per Ethernet Network
(except for OI server and OI client). It is the PC’s name limited to 15 characters
Note: The attributes in Miscellaneous are of lesser importance.
4.2.2 COMMUNICATION CHANNELS

Up to eight serial ports for communication with SCADA are automatically created when adding a Gateway.
Depending on PC architecture running the Gateway software, less than eight ports can be useable.
Generally, two serial ports are provided with a PC. By using extra boards, the number of serial ports can be
increased.
Once used by a communication link, the physical port has to be set relatively to the communication link
characteristics:
 protocol type (Usual protocol / GI 74 protocol / V35 ACKSYS-MCX): use the default value. The value
‘GI 74’ must not be used. It is still proposed for maintenance reason. The V35 ACKSYS-MCX value
must be selected only if a board Acksys MCXPCI/570-2 is installed in the Gateway.
 baud rate (bits/s): of the serial link (100 / 200 / 300 / 600 / 1200 / 4800 / 9600 / 19200 / 38400).
 plug com. number (range [1,16],step 1): attached to the port.
 transmitted clock (given by RXClockIn ext signal / given by TXClockIn ext signal / given by bauds
generator): this attribute exists only if the attribute protocol type is set to V35 ACKSYS-MCX): this
attribute defines the origin of the clock for the transmitted signal when the board is used in
synchronised asynchronous mode. When this attribute is set to given by bauds generator the baud
rate is actually forced to 64000 bits/s.
 received clock (given by RXClockIn ext signal / given by TXClockIn ext signal / given by bauds
generator); this attribute exists only if the attribute protocol type is set to V35 ACKSYS-MCX): it
GTW/EN AP/C57b AP-9

defines the origin of the clock for the received signal when the board is used in synchronised
asynchronous mode. When this attribute is set to given by bauds generator the baud rate is actually
forced to 64000 bits/s.
 clock signal (high permanent / transmit clock / bauds generator clock): this attribute exists only if the
attribute protocol type is set to V35 ACKSYS-MCX)
(1)
(2)
(3)
(4)
(5)
(6)
Figure 4: Configuring a communication channel (e.g. for port 1)
AP-10 GTW/EN AP/C57b

4.3 CREATING A BACKUP GATEWAY

To create a backup of an existing Gateway, right-click the Gateway and select Create backup:
Being a replica, the backup gateway inherits all the attributes from the mother gateway except for the names
and TCP/IP address. The symbol in the tree view is a reminder of this status.
The only available relation “is backup of” is automatically filled.
4.4 NETWORKING A GATEWAY ON THE STATION-BUS NETWORK

Gateway connection to the station-bus is implicitly done by adding the Gateway hierarchically to the Ethernet
network (see section 4.1 Adding a Gateway in the system hierarchy) and by setting its IP characteristics (see
4.2 Configuring the Gateway).
4.4.1 CONNECTING A GATEWAY TO OTHER STATION-BUS SUB-SYSTEMS

To transmit information between DS Agile sub-systems, the IEC 61850-8-1 protocol is used.
The data modelling of the IEC 61850-8-1 protocol is based on a client-server architecture. Each IEC
61850-8-1 communicating DS Agile sub-system (DS Agile OI server, DS Agile C26x controller, and DS Agile
Gateway) owns an IEC 61850-8-1 mapping of data which it is server of. A DS Agile sub-system is server of a
datapoint if it manages it, that is to say it produces its real-time value (in case of input datapoint such as
status, measurement, counter) or executes its real-time controls (in case of output datapoint such as binary
controls and setpoints).
To connect a Gateway (A) to a specific IEC 61850-8-1 communicating sub-system (B) on the station-bus, an
extra relation ‘has for IEC61850 server’ must be created for (A) and point to (B). That means the Gateway
(A) is client of sub-system (B) and can access to data managed by the sub-system (B), i.e. read relevant
real-time values from (B) and send real-time controls to (B).
GTW/EN AP/C57b AP-11

Figure 5: Connecting a Gateway to other station-bus sub-systems
When you select C26x as server to IEC 61850-8-1 gateway, the ‘has for IEC61850 client’ relation shows on
C26x side. On the Gateway side, the default relation attribute value is:
 modelling/goose usage: Data model only

Select another value if the need arises. This value is automatically repeated as a C26x read-only attribute.
4.4.1.1 DEFINING BUFFERED REPORTS

A gateway can receive and/or send buffered reports depending on the situation.
If you want the Gateway to receive buffered reports, it is done exactly in the same way as for the OI. To
configure it, please, refer to C26x/EN AP, chapter “Report based mode“

If the Gateway is an IEC 61850/IEC 61850 gateway, it can also send buffered reports. This will happen if
there are clients for BRCB defined in upper network (OI or/and protocol Gateway).
Configuring buffered reports for the Gateway is done as the same way as for C26x.
The buffered reports for the Gateway are configured on Scs level (regardless of the value of the latter
attribute). You cannot have more than one Gateway (and its backup) configured.
For details, refer to C26x/EN AP.
The corresponding relation shown on the Gateway side:
 Keep the attribute "timestamped 'unknown' for SCADA" to No. Refer to section 4.2.
Refer to GTW/EN FT for the register key “maintenance_if_dcnx_ethernet”.
4.4.2 DEFINING ADDRESSING MAPPING OF STATION-BUS NETWORK

An IEC 61850-8-1 mapping is an aggregation of logical devices, composed of bricks. Generally, a brick
corresponds to an electrical device or function. It provides its real-time data (status, measurements, and
controls…) and some configuration aspects. To do that, a brick groups data by categories (Status,
Measurement, Control, Configuration), called functional components.
A functional component groups data objects. A data object must be seen as a real-time equivalent of a DS
Agile datapoint. So, when a DS Agile sub-system (IEC 61850-8-1 client) needs the real-time value of a
datapoint manages by another sub-system (IEC 61850-8-1 server), this last one transmits the information via
a data object of its own IEC 61850-8-1 mapping. At SCE data modelling level, IEC 61850-8-1 clients must
precise which IEC 61850-8-1 servers it retrieves information from (see section 4.4.1 Connecting a Gateway
to other station-bus sub-systems).
Generally, an IEC 61850-8-1 data object has a stereotype, called common class. The structures of these
ones are known by all DS Agile IEC 61850-8-1 communicating sub-systems. For DS Agile sub-systems, the
number and structure of common classes are fixed. They are the terminal description of IEC 61850-8-1 DS
Agile data modelling.
In the IEC 61850-8-1 Mapping of DS Agile sub-system, there is a native logical device LD0 with fixed and
hard-coded bricks (DBID, DI (LPHD), GLOBE (LLN0), and DIAG). When creating a DS Agile Gateway at
SCE level, an IEC 61650-8-1 mapping with LD0 and its default bricks is also created. LD0 is a system logical
device that groups all system diagnostics and controls relevant to the Gateway. Datapoints addressed in the
brick of LD0 are only relevant to system topology.
Extra logical devices can not be created in the IEC 61850-8-1 mapping of a Gateway. Their usages are
reserved for DS Agile C26x controller configuration.

Overview of Gateway IEC 61850-8-1 mapping’s LD0

The LD0 of DS Agile Gateway is fixed and composed of the following bricks:
 DBID (DataBase IDentity) used for DS Agile C26x controller databases identification and management
 DI (Device IDentity)/LPHD used for DS Agile C26x controller identification
 GLOBE/LLN0 used for DS Agile C26x controller mode management
 TGDIAG brick, grouping statuses relevant to SCADA links managed by the Gateway
Figure 6: Standard LD0 extension for Gateway (SCE)
4.4.3 ADDRESSING DATAPOINT ON STATION-BUS NETWORK

For details refer to the C26x application chapter (C26x/EN AP).
4.5 NETWORKING IEDS ON A GATEWAY'S LEGACY NETWORK
4.5.1 CREATING A LEGACY NETWORK OF IEDS

Generally, specific devices called protection relays, or IEDs, ensure the protection of electrical processes
and bays. A legacy network managed by DS Agile Gateway can connect IEDs to the DS Agile system.
In the SCE data model, up to 4 IEC 60870-5-101 ("T101") and up to 4 IEC 60870-5-104 ("T104") networks
can be placed under a gateway. Each T101 legacy network must be linked to a communication port provided
by a computer board. Up to sixteen IEDs can be added under each T101 or T104 legacy network.

4.5.1.1 ADDING A LEGACY NETWORK

To create a legacy network:
 Add a Gtw T101 master or Gtw T104 master network at the gateway level from the contextual
Object entry window. It will be inserted under "Gateway legacy networks".
 Set the legacy network attributes relevant to its protocol characteristics

 If required, set the attribute Acquisition available on IEC61850 to Yes (see section 7.1)
 T101 only: Set its ‘has for main comm. port’ relation and the communication port characteristics (see
section 4.2.2)
Figure 7: Adding a legacy network
4.5.1.2 SETTING THE GENERAL ATTRIBUTES OF A LEGACY NETWORK

Set the short name and long name attributes for correct logging and alarm discrimination concerning the
IED status datapoint connected to the legacy network.
Figure 8: General attributes of a legacy network
4.5.1.3 SETTING THE ACQUISITION ATTRIBUTES OF A T101 LEGACY NETWORK

When adding a T101 legacy network, set the following attributes that will be used for all its IEDs:
1 number of retries (range [1, 10]): number of tries of the same frame without IED response, the
computer sends it before setting it disconnected
2 station address size (range [1 byte, 2 bytes]): size of the IED addresses
3 ASDU address size (range [1 byte, 2 bytes]): size of the ASDU
4 info address size (range [1 byte, 3 bytes]): size of the information addresses
5 transmission cause size (range [1 byte, 2 bytes]): size of the transmission cause
6 acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an IED answer is
awaited when the computer asks it for information

7 synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation period of the IED by
the gateway
8 downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by the computer, it
tries to re-connect it regularly at this cycle
9 Type of link (Balanced / Unbalanced): if unbalanced link, only master (here the Gateway) interrogates
the IED. If balanced link, IED can also interrogate the master (here the Gateway) without solicitation
10 test frame time-out (range [0 s, 255 s], step 1 s): in case of ‘balanced link’ (cf. attribute (10)), a life
message (test frame) is sent periodically between the Gateway and IED. This attribute corresponds to
maximum delay to receive this life message, to the Gateway’s point of view. If no reception within this
delay, IED is set disconnected
11 inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum time, expressed in
number of characters, that must exist between two frames
Figure 9: Setting acquisition attributes of a T101 legacy network
4.5.1.4 SETTING THE ACQUISITION ATTRIBUTES OF A T104 LEGACY NETWORK

When adding a T104 legacy network, set the following attributes that will be used for all its IEDs:
1 local IP address (xxx.xxx.xxx.xxx): local IP address of the gateway on the T104 Master network
2 t0: connection establishment time out (s) (range [1 s, 255 s], step 1 s): Time-out of connection
establishment
3 t1: APDUs send or test time out (s) (range [1 s, 255 s]): Time-out of send or test APDUs
4 t2: acknowledges in case of no data time out (s) (range [1 s, 255 s], step 1 s): Time-out for
acknowledges in case of no data messages t2 < t1
5 t3: test frames sending in case of long idle state time out (s) (range [1 s, 255 s], step 1 s): Time-
out for sending test frames in case of a long idle state
6 k: window size of transmitted unacknowledged frames (range [1, 255], step 1): Maximum
difference receive sequence number to send state variable
7 w: window size of acknowledged received frames (range [1, 255], step 1): Latest acknowledge
after receiving w I format APDUs
8 synchronisation cycle (x 10 s) (range [10 s, 655350 s], step 10 s): time synchronisation period of the
IED by the gateway
9 inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum time, expressed in
number of characters, that must exist between two frames

Figure 10: Setting acquisition attributes of a T104 legacy network
4.5.1.5 ADDING AN IED TO A LEGACY NETWORK

To create an IED on a legacy network:
 add an IED from object entry available either at ‘Gtw T101 master’ level or at ‘Gtw T104 master’ level
 set the IED attributes
Figure 11: Adding an IED to a legacy network
4.5.1.6 SETTING THE ATTRIBUTES OF A LEGACY IED

IEDs in T101 networks:
The following attributes must be updated for all types of IEDs:
1 short name and long name: used for correct logging and alarm discrimination of the IED's status
datapoints
2 network address of the IED on the legacy network (4 byte-address)
3 common address of ASDU: value of ASDU common address
4 automatic disturbance (No / Yes)
5 localisation for disturbance file: used for basic file name upload by SMT on OWS hard disk:
<localisation>_N#. Do not put any space in the directory name

Figure 12: Setting the general attributes of a legacy IED in a T101 network

For each IED, the values of the network address and short name attributes must be unique in any given
network.
IEDs in T104 networks:
The following attributes must be updated for all types of IEDs:
1 short name and long name: used for correct logging and alarm discrimination of the IED's status
datapoints
2 network address of the IED on the legacy network (4 byte-address)
3 IP address (xxx.xxx.xxx.xxx): IP address of the IED on the T104 Master network
4 common address of ASDU: value of ASDU common address
Figure 13: Setting the general attributes of a legacy IED in a T104 network

For each IED, the values of the network address, short name and IP address attributes must be unique in
any given network.

Configuration of IED redundancy

1 Add a redundant IED link from the contextual Objects entry window available at IED level
2 Select the redundant IED in the Relation link editor Window
3 Configure the redundancy attributes (if needed)

4.5.2 DEFINING THE ADDRESS MAP OF A LEGACY IED

To transmit information between IEDs and the DS Agile system, an IED legacy network connected to a DS
Agile computer is used.
To receive or send information between legacy IEDs and the DS Agile system, each relevant data must have
a specific address on the legacy network. General modelling of legacy network address mapping can be
done. At SCE level, an IED of a legacy network owns an “IED mapping” object, that is split in categories of
mapping on a per datapoint type basis. In each category of mapping, elementary IED addresses can be
created. This mapping is implicitly created when an IED is added at the legacy network level.
For details on the address map of a given IED, refer to its documentation.
In the IED Mapping, the xxx addr. on IED identifier of each IED datapoint must be unique.
 T101 and T104: the datapoint is identified by either of the following combinations of its attribute
values:
 MPS and Setpoints: { "information object address" }
 Other datapoints: { "information object address"; "common address of ASDU" }

There are two ways to map the datapoints:
 Select the attributes of the sub-nodes of the various IED xxx Mapping folders
 To speed up the configuration process (especially after importing a file from MS Excel), use a smart
table in the Wiring editor and link it to the individual tables in the hierarchy. Refer to C26x/EN AP.
4.6 NETWORKING A SCADA ON A GATEWAY'S SCADA NETWORK
4.6.1 CREATING A SCADA NETWORK

An electrical substation can be supervised and controlled from many points inside the substation via DS
Agile operator interfaces (Substation Control Point or SCP) and/or C26x controller bay panels (Bay Control
Point or BCP), and outside the substation. Generally, remote control of the substation (Remote Control Point
or RCP) is done via specific networks called SCADA networks.
Several SCADA networks can be connected to one DS Agile system, via DS Agile C26x or DS Agile
Gateway sub-systems. SCADA networks are managed as master by remote SCADA and can be redundant
for safety reasons. A DS Agile Gateway can manage up to four SCADA networks.
At SCE data modelling level, only the SCADA networks and their protocols are modelled and connected to
Gateway sub-systems. Each SCADA network has to be linked to a main communication port and an auxiliary
communication port in case of redundancy.

4.6.1.1 ADDING A SCADA NETWORK

To create a SCADA network on a Gateway:
 Add a SCADA network ("Usual protocol" is given as an example in the figure below) from the Objects
entry window available at Gateway level (1),
 Update the SCADA network attributes relevant to its protocol characteristics (see following sections),
 Update its ‘has for main communication port’ relation and the communication port characteristics (see
section 4.2.2 Communication channel). This relation is not significant for T104 protocol using an
Ethernet protocol.
 To create a redundant SCADA link, add the relation ‘has for aux. comm. port’ (2) to the Gateway
SCADA network and type in the relevant serial port if required. The T104 protocol does not support
the redundant SCADA link.
(1)
Figure 14: Adding a SCADA network
(2)
Figure 15: Creating a redundant SCADA link

4.6.1.2 SETTING THE GENERAL ATTRIBUTES OF A SCADA NETWORK

Whatever the kind of SCADA network, its short name and long name attributes (1) must be updated for
correct logging and alarm discrimination concerning status datapoints managed by the Gateway for each
connected SCADA network as shown in figure 13.
Figure 16: Setting general attributes of a SCADA network
4.6.1.3 SETTING THE SPECIFIC ATTRIBUTES OF A T101 SCADA NETWORK

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to ‘T101’. For this
protocol an additional attribute 'time reference' (2) is displayed and has to be set. Available values for this
attribute are UTC or local. This attributes defines which time reference is used to stamp events transmitted to
SCADA as shown in figure 14 and figure 15.
Figure 17: Setting the protocol type of a SCADA network
When setting a T101 SCADA network, some specific attributes available for the protocol must be updated
(Protocol and SOE tabbed panes):
(1) link address length (1 byte / 2 bytes)
(2) link address (range [1, 65534], step 1)
(3) redundant link address (range [1, 65534], step 1): this attribute is significant if a line redundancy is
configured for the protocol (refer to 4.6.1.1 Adding a SCADA network)
(4) ASDU common address length (range [1, 65534], step 1)
(5) ASDU common address (range [1, 65534], step 1)
(6) information object length (Address on 8 bits (1 byte) / Address on 16 bits (2 bytes) / Address on 8
bits.8 bits / Address on 8 bits.16 bits / Address on 16 bits.8 bits / Address on 8 bits.8 bits.8 bits /
Address on 24 bits (3 bytes))
(7) frame max length (range [1, 255], step 1)
(8) cause of transmission length (Address on 8 bits / Address on 16 bits)
(9) MV periodic cycle (range [0 s, 65534 s], step 1 s)
(10) binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
(11) background scan cycle (range [0 s, 65535 s], step 1 s)

(12) quality value for toggling xPS ( BL only (blocked) / IV only (invalid): this attribute defines the value
of the Quality Descriptor field when the event to transmit is an xPS in the TOGGLING state.
(13) SOE file support (No / Yes (Standard) / Yes (Microsol)): set to ‘Yes’ if SOE file management is
supported by the SCADA; then you must select CP56Time2A as binary time size
(14) SOE file base address: this attribute is significant only if SOE file support is not set to No.
(15) SOE file nb max of events (range [10, 4200], step 1): this attribute is significant only if SOE file
support is not set to No.
(16) nb max of SOE files (range [1,99], step 1): this attribute is significant only if SOE file support is not
set to No.
(17) Buffer overflow support (No / Yes): this attributes defines if the buffer overflow is managed. If set
to Yes the following attribute is significant and has to be updated.
(18) Buffer overflow address (No / Yes): this attributes defines the address of the buffer overflow
datapoint sent to SCADA.
(19) Quality value for 'Jammed' state (valid \ IV invalid): this attribute defines the value of the Quality
Descriptor field when the event to transmit in the 'Jammed' state.
(20) Quality value for 'Unknown' state (Not topical only \ Not topical and IV invalid): this attribute
defines the value of the Quality Descriptor field when the event to transmit in the 'Unknown' state.
(21) Balanced mode (No/Yes): this attribute defines balanced mode if set to yes.
(22) Balanced mode retry number (range [1,10]): in balanced mode, defines the maximum number of
unsuccessful polls before the slave is declared disconnected (default number: 3)
(23) Balanced mode link timeout (range [2000,10000]): in balanced mode, defines the timeout in ms
between a gateway information frame and SCADA acknowledgement (default number: 2000)

Figure 18: Setting the protocol and SOE attributes of a T101 SCADA network
The disturbance tab is reserved for future use.

4.6.1.4 SETTING THE SPECIFIC ATTRIBUTES OF A DNP3 SCADA NETWORK

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to ‘DNP3’. Then
SCADA network tabbed panes are refreshed relatively to the selected protocol.
(1)
Figure 19: Setting the protocol type of a DNP3 SCADA network
When setting a DNP3 SCADA network, some specific attributes available for the protocol must be updated
(Protocol tabbed pane):
(2) SPS/DPS class (1 / 2 / 3)
(3) MV class (1 / 2 / 3)
(4) Counter class (1 / 2 / 3)
(1)
(2)
(3)
(4)
Figure 20: Setting the protocol of a DNP3 SCADA network
4.6.1.5 SETTING THE SPECIFIC ATTRIBUTES OF A T104 SCADA NETWORK

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to ‘T104’. For this
protocol an additional attribute 'time reference' (2) is displayed and has to be set. Available values for this
attribute are UTC or local. This attributes defines which time reference is used to stamp events transmitted to
SCADA.
(1)
(2)
Figure 21: Setting the protocol type of a T104 SCADA network

When setting a T104 SCADA network, some specific attributes available for the protocol must be updated
(Protocol and SOE tabbed panes):
(1) TCP/IP address of the Gateway
(3) information object length (Address on 8 bits.16 bits / Address on 16 bits.8 bits / Address on 8
bits.8 bits.8 bits / Address on 24 bits (3 bytes))
(4) MV periodic cycle (in s) (range [0 s, 65534 s], step 1 s)
(5) background scan cycle (s) (range [0 s, 65535 s], step 1 s)
(6) t0: connection establishment time out (s) (range [1 s, 255 s], step 1 s)
(7) t1: APDUs send or test time out (range [1 s, 255 s], step 1 s)
(8) t2: acknowledges in case of no data time out (s) (range [1 s, 255 s], step 1 s)
(9) t3: test frame sending in case of long idle state time out (s) (range [1 s, 255 s], step 1 s)
(10) k: window size of transmitted unacknowledged frames (range [1, 255], step 1)
(11) w: window size of acknowledged received frames (range [1, 255], step 1)
(12) max command delay (s) (range [0 s, 32767 s], step 1 s)
(13) quality value for ‘Jammed' state: (Valid/ Invalid) this attribute defines the value of the Quality
Descriptor field when the event to transmit is an xPS in the 'Jammed' State
(14) quality value for toggling xPS( BL only (blocked) / IV only (invalid): this attribute defines the value
of the Quality Descriptor field when the event to transmit is an xPS in the ‘Toggling’ state.
(15) quality value for 'unknown' state: (Not topical/ Not topical and IV invalid) this attribute defines the
value of the Quality Descriptor field when the event to transmit is an xPS in the 'Unknown' state
(16) SOE file support (No / Yes (Standard) / Yes (Microsol)): set to ‘Yes’ if SOE file management is
supported by the SCADA; then you must select CP56Time2A as binary time size
(17) SOE file base address: this attribute is significant only if SOE file support is not set to No.
(18) SOE file nb max of events (range [10,4200], step 1): this attribute is significant only if SOE file
support is not set to No.
(19) nb max of SOE files (range [1,99], step 1): this attribute is significant only if SOE file support is not
set to No.
(20) Disturb file support (No / Yes): this attributes defines if the disturbance file is managed. If set to
Yes the following attribute is significant and has to be updated
(21) Disturb file base address: address of the datapoint that is SET when a new disturbance file
becomes available (this attribute is significant only if Disturb file support is set to Yes).
(22) nb max of Disturb files (range [1,99], step 1): maximum number of disturbance files stored on the
Gateway
(23) Buffer overflow support (No / Yes): this attributes defines if the buffer overflow is managed. If set
to Yes the following attribute is significant and has to be updated.
(24) Buffer overflow address (No / Yes): this attributes defines the address of the buffer overflow
datapoint sent to SCADA.

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
(24)
Figure 22: Setting the protocol and SOE attributes of a T104 SCADA network

 The following constraints between the attributes must be respected:

"SOE file nb of events" > "'full' SOE file nb of events"
"t2" < "t1"
"t3" > "t1"
"w"  "k"
4.6.1.6 SETTING THE SPECIFIC ATTRIBUTES OF A MODBUS SCADA NETWORK

When adding a SCADA network, the supported protocol must be updated (1). Here, set it to ‘MODBUS’.
Then SCADA network tabbed panes are refreshed relatively to the selected protocol.
(1)
Figure 23: Setting the protocol type of a MODBUS SCADA network
When setting a MODBUS SCADA network, some specific attributes available for the protocol must be
updated (Protocol tab):
(2) parity (None / Odd / Even) used at communication level.
(1)
(2)
Figure 24: Setting the specific attributes of a MODBUS SCADA network

4.6.1.7 SETTING THE SPECIFIC ATTRIBUTES OF A CDC TYPE II SCADA NETWORK

(OBSOLETE PROTOCOL)
When adding a SCADA network, the supported protocol must be updated (1). Here, set it to ‘CDC type II’.
(1)
Figure 25: Setting the protocol type of a CDC Type II SCADA network (obsolete)
When setting a CDC type II SCADA network, some specific attributes available for the protocol must be
updated (Protocol tab):
(1) T0: connection time-out (range [1 s, 255 s], step 1 s)
(2) minimal int value for MV (range [-2048, 0], step 1)
(3) maximal int value for MV (range [0,2047], step 1)
(4) int value for invalid MV (None / 2047 / -2048)
(1)
(2)
(3)
(4)
Figure 26: Setting the specific attributes of a CDC Type II SCADA network (obsolete)
4.6.1.8 SETTING THE SPECIFIC ATTRIBUTES OF AN OPC SCADA NETWORK

When adding a SCADA network, you can choose directly OPC Protocol. Then OPC Protocol tabbed panes
are refreshed relatively to the selected protocol.
When setting an OPC SCADA network, some specific attributes available for the protocol must be updated:
General tabbed pane
Figure 27: General attributes of an OPC protocol

OPC values tab pane

(1) OPC value for ‘Reset’ (byte format): indicates the value for the Tag OPC to represent the state Reset
for all SPS with the format byte (0 to 255).
(2) OPC value for ‘Reset’ (bool format): indicates the value for the Tag OPC to represent the state Reset
for all SPS with the format bool (0 for False,1 for True).
(3) OPC value for ‘Set’ (byte format): indicates the value for the Tag OPC to represent the state Set for
all SPS with the format byte (0 to 255).
(4) OPC value for ‘Set’ (bool format): indicates the value for the Tag OPC to represent the state
Jammed for all SPS with the format bool (0 for False,1 for True).
(5) OPC value for ‘Jammed’ (byte format): indicates the value for the Tag OPC to represent the state
Jammed for all DPS with the format byte (0 to 255).
(6) OPC value for ‘Jammed’ (bool format): indicates the value for the Tag OPC to represent the state
Jammed for all DPS with the format bool (0 for False,1 for True).
(7) OPC value for ‘Open’ (byte format): indicates the value for the Tag OPC to represent the state Open
for all DPS with the format byte (0 to 255).
(8) OPC value for ‘Open’ (bool format): indicates the value for the Tag OPC to represent the state Open
for all DPS with the format bool (0 for False,1 for True).
(9) OPC value for ‘Closed’ (byte format): indicates the value for the Tag OPC to represent the state
Close for all DPS with the format byte (0 to 255).
(10) OPC value for ‘Closed’ (bool format): indicates the value for the Tag OPC to represent the state
Close for all DPS with the format bool (0 for False,1 for True).
(11) OPC value for ‘Undefined’ (byte format): indicates the value for the Tag OPC to represent the state
Undefined for all DPS with the format byte (0 to 255).
(12) OPC value for ‘Undefined’ (bool format): indicates the value for the Tag OPC to represent the state
Undefined for all DPS with the format bool (0 for False,1 for True).
(13) OPC value for ‘Order open’ (byte format): indicates the value for the Tag OPC to represent the state
order open for all DPC with the format byte (0 to 255).
(14) OPC value for ‘Order open’ (bool format): indicates the value for the Tag OPC to represent the state
order open for all DPC with the format bool (0 for False,1 for True).
(15) OPC value for ‘Order close’ (byte format): indicates the value for the Tag OPC to represent the state
order close for all DPC with the format byte (0 to 255).
(16) OPC value for ‘Order close’ (bool format): indicates the value for the Tag OPC to represent the state
order close for all DPC with the format bool (0 for False,1 for True).
(17) OPC value for ‘Order reset’ (byte format): indicates the value for the Tag OPC to represent the state
order reset for all SPC with the format byte (0 to 255).
(18) OPC value for ‘Order reset’ (bool format): indicates the value for the Tag OPC to represent the state
order reset for all SPC with the format bool (0 for False,1 for True).
(19) OPC value for ‘Order set’ (byte format): indicates the value for the Tag OPC to represent the state
order set for all SPC with the format byte (0 to 255).
(20) OPC value for ‘Order set’ (bool format): indicates the value for the Tag OPC to represent the state
order set for all SPC with the format bool (0 for False,1 for True).

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
Figure 28: Setting the OPC values attributes of an OPC SCADA network
OPC qualities tab pane

(1) OPC quality for ‘SelfCheckFault’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to SelfCheckFault for all datapoints (0 to 65535).
(2) OPC quality for ‘Unknown’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Unknown for all datapoints (0 to 65535).
(3) OPC quality for ‘Toggling’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Toggling for all datapoints (0 to 65535).
(4) OPC quality for ‘Suppressed’ indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Suppressed for all datapoints (0 to 65535).
(5) OPC quality for ‘Forced’: indicates the value for the Tag OPC quality to represent the IEC 61850-8-1
quality set to Forced for all datapoints (0 to 65535).
(6) OPC quality for ‘Substituted’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Substituted for all datapoints (0 to 65535).
(7) OPC quality for ‘Undefined’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Undefined for all MPS,MV,Counter (0 to 65535).
(8) OPC quality for ‘OverRange’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to OverRange for all MV,Counter (0 to 65535).
(9) OPC quality for ‘OpenCircuit’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to OpenCircuit for all MV (0 to 65535).

(10) OPC quality for ‘LLLThreshold’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to LLLThreshold for all MV (0 to 65535).
(11) OPC quality for ‘LLThreshold’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to LLThreshold for all MV (0 to 65535).
(12) OPC quality for ‘LThreshold’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to LThreshold for all MV (0 to 65535).
(13) OPC quality for ‘HThreshold’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to HThreshold for all MV (0 to 65535).
(14) OPC quality for ‘HHThreshold’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to HHThreshold for all MV (0 to 65535).
(15) OPC quality for ‘HHHThreshold’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to HHHThreshold for all MV (0 to 65535).
(16) OPC quality for ‘Jammed’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Jammed for all DPS (0 to 65535).
(17) OPC quality for ‘Undefined’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Undefined for all DPS (0 to 65535).
(18) OPC quality for ‘Valid Set/Closed’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Set or Closed for all SPS/DPS (0 to 65535).
(19) OPC quality for ‘Valid Reset/Opened’: indicates the value for the Tag OPC quality to represent the
IEC 61850-8-1 quality set to Reset or Opened for all SPS/DPS (0 to 65535).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13
(14)
(15)
(16)
(17)
(18)
(19)
Figure 29: Setting the OPC quality attributes of an OPC SCADA network

4.6.1.9 SETTING THE SPECIFIC ATTRIBUTES OF AN IEC 61850-8-1 SCADA NETWORK

When setting an IEC 61850-8-1 SCADA network the following attributes must be updated:
(1) short name and long name: used for logging, alarms, …
(2) TCP/IP address of the Gateway on the SCADA network
(3) Check Local/Remote (Yes / No) of the Gateway on the SCADA network
This attribute defines whether the Substation Local/Remote indication should be used by the
IEC 61850/IEC 61850 gateway. The Substation Local/Remote xPS comes from the lower IEC 61850-8-1
network.
If L/R is managed (attribute set to Yes), the controls coming from the upper network:
 are sent to the lower network if the Substation mode is “Remote” and if the controls are dependent
on the L/R mode.
 are sent to the lower network if the controls are independent of the L/R mode.
 are negatively acknowledged (“bay-substation mode fault” ack) if the Substation mode is “Local”
and if the controls are dependent on the L/R mode
If the L/R is not managed (attribute set to No), the controls coming from the upper network are sent to the
lower network whatever is the L/R state.
(4) Check SBMC (Yes / No) of the Gateway on the SCADA network
This attribute defines whether the managed bays' SBMC indication should be used by the
IEC 61850/IEC 61850 gateway. The SBMC SPS comes from the lower IEC 61850-8-1 network. This
check affects how the states of SBMC-dependent datapoints are processed before transmission to the
upper level as well as which commands are forwarded down to bay controllers and which commands are
"suppressed".
If SBMC filtering is managed (attribute set to Yes):
 SBMC-dependent indications (xPS datapoints) have their states changed according to their profile
definition even if their state changes while the bay they belong to is in SBMC mode,
 SBMC-dependent control commands (xPC datapoints) received while the bay they target is in
SBMC mode are blocked at Gateway level,
 The state changes of SBMC-independent xPS/xPC datapoints are always transmitted, regardless
of whether the bay is in SBMC mode or not.
If SBMC filtering is not managed (attribute set to No):
 All commands and state change indications are transmitted in both directions without any changes.
SBMC filtering can then be managed by another Gateway connected to the upper network if one is
available and has been set to that effect.
Notes:
If there are other SCADA protocols (such as T101, T104 etc.) present on the Gateway in addition to the IEC 61850-8-1
SCADA protocol, the setting for Check SBMC in the Attributes of: IEC61850prot panel applies to all of them.
If no IEC 61850-8-1 SCADA protocol is defined, the attribute Check SBMC is neither visible nor settable and is fixed to
Yes, i.e. SBMC filtering is always managed.

 The "TCP/IP address" value of a device must be unique among all the devices per Ethernet Network.
(1)
(2)
(3)
(4)
Figure 30: Setting the attributes of an IEC 61850-8-1 SCADA protocol
4.6.1.10 SETTING GENERAL ATTRIBUTES OF A T101-SAS SCADA NETWORK

(OBSOLETE PROTOCOL)
When adding a SCADA network, the supported protocol must be updated (1). Here, set it to ‘T101-SAS’.
When setting a T101-SAS SCADA network the following attributes must be updated:
(1) short name and long name: used for logging, alarms, …
Figure 31: Setting the protocol type of a T101-SAS SCADA network (obsolete)
When setting a T101-SAS SCADA network, some specific attributes available for the protocol must be
updated (Protocol tabbed pane):
(1) ASDU common address length (1 byte / 2 bytes)
(3) Address structure (address on 8 bits.8 bits.8 bits)
(4) Frame max length (range [1, 255], step 1)
(5) MV periodic cycle (in s) (range [0 s, 65534 s], step 1 s)
(6) Binary time size (CP24 Time2A 3bytes / CP56 Time2A 7bytes)

(1)
(2)
(3)
(4)
(6) (5)
Figure 32: Setting the protocol of a T101-SAS SCADA network (obsolete)
4.6.2 DEFINING THE ADDRESS MAP OF A LEGACY SCADA NETWORK

To transmit information between DS Agile system and SCADA, a SCADA legacy network is used. So, each
concerned data must have a specific address on this network relatively to its protocol. General modelling of a
SCADA legacy network address mapping can be done. At SCE level, a SCADA legacy network owns a
“SCADA mapping” object, that is split in categories of mapping on a per datapoint type basis. In each
category of mapping, elementary SCADA addresses can be created. This mapping is implicitly created at
SCADA network creation.
Addressing MPS datapoint on SCADA legacy network is not available.
Figure 33: Structure of the address map of a legacy SCADA network

There are two ways to map the datapoints:
 Select the attributes of the subnodes of the various Gtw xxx Mapping folders
 To go faster, use a smart table, linked to the individual tables (refer to sections 4.6.2.2, 4.6.2.4,
4.6.2.5, 4.6.2.6 for details on attributes)
 In the SCADA Mapping, the address identification of each "Gtw xxx addr." must be unique. In the
particular cases of T101 and T104 protocols, the uniqueness constraint is applicable only for
addresses of the same type. Addresses of different types can have identical addresses and therefore
this does not lead to an error but to a warning.
 On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos ind" datapoint,
must have its "Format" attribute set to the "Natural" value.
4.6.2.1 SMART TABLE

When a SCADA network is selected in the browser, an extra item is present in the contextual menu: “Edit
Scada mapping”. When selected, a window appears. It allows to enter all datapoint addresses for the
SCADA mapping. The datapoints are tabbed by type; 5 types exist:
 xPS for SPS / DPS addresses

 xPC for SPC / DPC addresses
 MV for measurement addresses
 SetPoint for SetPoint addresses
 Counter for Counter addresses
Each tab presents a table featuring:
 in the left part (white background), the predefined list of datapoints

 in the right part (blue background), empty cells for addresses, labels and protocol-dependent attributes
The white part indicates for each datapoint of the type:
 Variants (pictogram)
 Path (read only)
 Short name (read only)
 Long name (editable, copy/paste enabled)

To adjust a column width, pass the cursor over the border in the header till the cursor turns to ; then drag
and drop.
Procedure to fill the blue part:
 Click in an address cell

 Enter the address
 Click another cell to change the selection; the other cells in the row are automatically filled with default
values (an address which contains letters is corrected to 255)
 Click two times a cell in the column Label and edit the text
 Click three times a cell in a column different than Addr or Label; click the button v and select one
value in the drop-down list
 Select a cell or several contiguous cells with at least one Addr cell; copy, select target, paste the label
is recomputed; if the Addr is void, 255 is pasted
 To check the address uniqueness, click button Validate in upper left corner:
 the wrong lines turn red and show a red pictogram in the first column
 the tab tag turns red (resp. green) if it contains errors (resp. it is error-free); to display a tooltip, pass
the mouse over a red line:
Possible errors:
 Address is not unique in the mapping
 Address is not associated with a datapoint (delete the address)
 Address value doesn’t respect the predefined format
 Datapoint is not visible by the SCADA equipment
 To delete a set of addresses in contiguous rows, click in the first or Addr column and drag to select
the rows, right click and click Suppress address

 To sort out the rows alphabetically/numerically/hierarchically in decreasing order, click each column
header several times till the arrow  shows after the column label
 To filter the rows according to a column field, click v and select one value in the combo list; as a
result, a funnel shows before the column label. To suppress the filter, select the value (All).
For the path column, the sub-nodes of the selected nodes are displayed as well.
If the desired value is not in the list, stop the cursor on any value and type in the value (in red):

 Click the button Close; when you resume the procedure, click v in the Addr header and select
Defined address to retrieve the entered values
4.6.2.2 DEFINING A SCADA ADDRESS FOR AN SPS DATAPOINT

A SCADA address is added to an SPS datapoint from the contextual Objects entry window at the SCADA
SPS mapping level:
Figure 34: Adding a SCADA SPS address
Once added, SCADA SPS address attributes must be set in SCE:

(1) short name of the address used for internal SCE identification
For T101/T104 protocols:
(2) object address
(3) priority level (range [1,255], step 1) gives the priority of emission (1: higher). Only significant if
Event attribute is different from No. Is fixed to 1 for T104 protocol.
(4) Event (No / Yes with time tag / Yes without time tag): when set to Yes with time tag, indicates that
change of state of the datapoint are transmitted spontaneously with time Tag.
(5) Event record
 T101 – (Does not involved in a transfer of file / Create a RECORD EVENT if there is not it current /
Add to the current record EVENT / Create a RECORD EVENT and adds to the current record
EVENT):
 When set to a value different from Does not involved in a transfer of file indicates if change of
state of the datapoint must be saved in the Sequence of Event file.

 Values different from Does not involved in a transfer of file are associated to the same
treatment, because only one SOE file is managed by the Gateway. The set of available values
is maintained for compatibility with legacy Gateway addressing in DS Agile Gateway.
 T104 – (No / Yes): indicates if state changes of the datapoint must be saved in the SOE file.
(6) Inversion (No / Yes): Indicates that the datapoint value needs to be inverted before transmission.
(7) Background scan (No / Yes): indicates if the datapoint belongs to the background scan cycle.
(8) Group ([0..16)] / 0=no group) (range [0,16], step 1) indicates to which “T101/T104 General
Interrogation group” the datapoint is assigned. 0 means ‘no group’ assignation.
For DNP3 protocol:
(9) object address - index.
(10) Event (No / Yes with time tag): when set to ‘Yes with time tag’, indicates if change of state of the
datapoint are transmitted spontaneously with time Tag
(11) Inversion (No / Yes): indicates that the datapoint value needs to be inverted before transmission
For Modbus protocol:
(12) object address – register
For OPC protocol:
(14) OPC address: indicates the name’s tag for OPC (limited to 48 characters). The character “.”
indicates that the name is hierarchical
(15) Historization (No / Yes): indicates if this tag is sent at historic timer frequency (refer to section 7.3.1
of chapter GTW/EN CT)
(16) Format (boolean / byte): indicates the type of value which is associated with the tag. Boolean is for
VT_BOOL a boolean (True/False) value. A value of 0xFFFF (all bits at 1) indicates True; a value of 0
(all bits at 0) indicates False. No other value is valid. Byte is for VT_UI1 an unsigned 1-byte
character

T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
Modbus
(12)
(13)
OPC
(14)
(15)
(16)
(17)
Figure 35: Defining a SCADA address for an SPS datapoint

4.6.2.3 DEFINING A SCADA ADDRESS FOR A DPS DATAPOINT

A SCADA address is added to a DPS datapoint from the contextual Objects entry window at the SCADA
DPS mapping level:
Figure 36: Adding a SCADA DPS address
Once added, SCADA DPS address attributes must be set at SCE level:
(2) For T101/T104 protocol:
(3) priority level (from 1 to 255): gives the priority of emission (1: higher). Only significant if the Event
attribute is different from No. It is fixed to 1 for T104 protocol
(4) Event (No / Yes with time tag / Yes without time tag): when set to Yes with time tag (resp. Yes
without time tag) indicates if state changes of the datapoint are transmitted spontaneously with (resp.
without) time tag
(5) Event record
 T101 – (Does not involved in a transfer of file / Create a RECORD EVENT if there is not it current /
Add to the current record EVENT / Create a RECORD EVENT and adds to the current record
EVENT):
 When set to a value different from Does not involved in a transfer of file indicates if change of
state of the datapoint must be saved in the Sequence of Event file.
 Values different from Does not involved in a transfer of file are associated to the same
treatment, because only one SOE file is managed by the Gateway. The set of available values
is maintained for compatibility with legacy Gateway addressing in DS Agile Gateway.
 T104 – (No / Yes): indicates if state changes of the datapoint must be saved in the SOE file.
(7) Background scan (No / Yes): indicates if the datapoint belongs to the background scan cycle

(8) Group ([0..16]) / 0 = no group): indicates to which “T101/T104 General Interrogation group” the
datapoint is assigned. 0 means ‘no group’ assignation
(9) object address: for DS Agile Gateway, only one address is useable to transmit DPS value
For DNP3 protocol:
(10) Event (No / Yes with time tag): when set to ‘Yes with time tag’ indicates if changes of state of the
datapoint are transmitted spontaneously with time tag
(12) object address - index
(14) object address - register: for DS Agile Gateway, only one address is useable to transmit a DPS
value
For OPC protocol:
(15) OPC address (mono addressing): indicates the name’s tag for OPC (limited to 48 characters). The
character “.” indicates that the name is hierarchical
(16) double address usage (No / Yes): this attribute defines if double addressing mechanism is used or
not. If this attribute is set to Yes attributes (22) and (23) must be defined (refer to section 7.3.2 of
chapter GTW/EN CT)
(17) Historization (No / Yes): indicates if this tag is sent at historic timer frequency (refer to section 7.3.1
of chapter GTW/EN CT)
(18) format (Boolean / Byte): indicates the type of value which is associated with the tag. Boolean is for
VT_BOOL a boolean (True/False) value. A value of 0xFFFF (all bits 1) indicates True; a value of 0
(all bits 0) indicates False. No other value is valid. Byte is for VT_UI1 an unsigned 1-byte character
(19) Inversion (No / Yes): before being transmitted the value of the DPS is inverted as defined here after:
- JAMMED (00) is replaced by UNDEFINED and vice-versa

- OPEN (01) is replaced by CLODSE (10) and vice versa
(20) open state address: this attribute is only significant if attribute double address usage is set to Yes.
It defines the OPC tag name for the OPEN state
(21) Closed state address: this attribute is only significant if attribute double address usage is set to
Yes. It defines the OPC tag name for the CLOSE state

T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
Modbus
(12)
(13)
OPC
(14)
(15)
(16)
(17)
(18)
(19)
(20)
Figure 37: Defining a SCADA address for a DPS datapoint

4.6.2.4 DEFINING A SCADA ADDRESS FOR AN MV DATAPOINT

A SCADA address is added to an MV datapoint from the contextual Objects entry window at the SCADA
MV mapping level:
Figure 38: Adding a SCADA MV address
Once added, SCADA MV address attributes must be set at SCE level:

(2) object address
(3) priority level (range [1, 255], step 1) gives the priority of emission (1: higher). Only significant if
Event attribute is different from ‘No’. Is fixed to 1 for T104 protocol.
(4) Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’, indicates that
changes of state of the datapoint are transmitted spontaneously with time Tag.
(5) Event record (No / Yes): indicates if the datapoint has to be recorded in the SOE file
(6) Format (Normalized / Adjusted / Float): transmission format.
(7) Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation group” the
datapoint is assigned to. 0 means ‘no group’ assignation.
(8) cycle type (None / Periodic / Background scan): indicates which transmission cycle the MEAS
belongs to.
(9) minimum value (range [-3.4E38, +3.4E38]): minimum scaled value. Not used if minimum value =
maximum value.
(10) maximum value (range [-3.4E38, +3.4E38]): maximum scaled value. Not used if minimum value =
maximum value.

For DNP3 protocol:

(11) object address [0..65535]
(12) Event (No / Yes with time tag): when set to ‘Yes with time tag’, indicates if changes of state of the
datapoint are transmitted spontaneously with time Tag.
(13) Format (Natural / Adjusted).
maximum value.
maximum value
(16) defined as counter (Yes / No). To send the measurement as a counter, state Yes; to send the
measurement as a measurement, state No
(17) object address - register
(18) Format (Natural / Unsigned normalized / Signed normalized): transmission format.
(19) Precision (8..16) (range [8, 16),step 1): number of transmitted bits.
maximum value.
maximum value.:
For OPC protocol:
indicates that the name is hierarchical. For OPC MV the format is VT_R4 (an IEEE 4-byte real value)

T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
DNP3
(11)
(12)
(13)
(14)
(15)
(16)
Modbus
(17)
(18)
(19)
(20)
(21)
OPC
(22)
Figure 39: Defining a SCADA address for an MV datapoint

4.6.2.5 DEFINING A SCADA ADDRESS FOR A COUNTER DATAPOINT

A SCADA address is added to a Counter datapoint from the contextual Objects entry window at the SCADA
Counter mapping level:
Note: Handling the counters (freeze, reset, etc....) affects only the SCADA; the counters are NOT modified in the
C26x
Figure 40: Adding a SCADA counter address
Once added, SCADA Counter address attributes must be set at SCE level:
(1) short name and long name of the address used for internal SCE identification
(2) object address
(3) priority level (range [1,255], step 1) gives the priority of emission (1: higher). Only significant if
Event attribute is different from ‘No’. Is fixed to 1 for T104 protocol.
(4) Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’, indicates that
change of state of the datapoint are transmitted spontaneously with time Tag.
(5) Event record (No / Yes): indicates if the datapoint has to be recorded in the SOE file
(6) Group ([0..4] / 0=no group): indicates which “T101/T104 General Interrogation group” the datapoint
is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:
(7) object address [0..65535].
(8) Event (No / Yes with time tag): when set to ‘Yes with time tag’, indicates if changes of state of the
datapoint are transmitted spontaneously with time Tag.


(10) Format (Natural / Unsigned normalized): transmission format.
For OPC protocol:
indicates that the name is hierarchical. For OPC counter the format is VT_I4 (a 4-bytes integer value)
T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
DNP3
(7)
(8)
Modbus
(9)
(10)
OPC
(11)
Figure 41: Defining a SCADA address for a counter datapoint
Note: Energy values transmitted as counters for the DNP3 protocol.

4.6.2.6 DEFINING A SCADA ADDRESS FOR A SPC DATAPOINT

A SCADA address is added to an SPC datapoint from the contextual Objects entry window at the SCADA
SPC mapping level:
Figure 42: Adding a SCADA SPC address
Once added, SCADA SPC address attributes must be set at SCE level:
(2) object address
(3) SCADA execute order type (Select execute / Direct execute): this attribute defines which kind of
sequence is used by the SCADA to send a control to the datapoint.
(4) SBO time-out (s) (range [0 s, 65535 s], step 1 s): time-out DS Agile system has to acknowledge the
selection.
For DNP3 protocol:
For OPC protocol:
indicates that the name is hierarchical.
(9) format (Boolean / Byte): indicates the type of value associated to the tag. Boolean is for VT_BOOL a
boolean (True/False) value. A value of 0xFFFF (all bits at 1) indicates True; a value of 0 (all bits at 0)
indicates False. No other value is valid. Byte is for VT_UI1 an unsigned 1-byte character.

T101/T104
(1)
(2)
(3)
(4)
DNP3
(5)
(6)
Modbus
(7)
OPC
(8)
(9)
Figure 43: Defining a SCADA address for an SPC datapoint

4.6.2.7 DEFINING A SCADA ADDRESS FOR A DPC DATAPOINT

A SCADA address is added to a DPC datapoint from the contextual Objects entry window at the SCADA
DPC mapping level:
Figure 44: Adding a SCADA DPC address
Once added, SCADA DPC address attributes must be set at SCE level:
(2) object address
(4) SBO time-out (range [0 s, 65535 s], step 1 s): time-out DS Agile system has to acknowledge the
selection.
For DNP3 protocol:
For OPC protocol:
(9) double address usage (No / Yes): this attribute defines if double addressing mechanism is used or
not. If this attribute is set to Yes attributes (22) and (23) must be defined (refer to section 7.3.2 of
chapter GTW/EN CT).

(10) format (Boolean / Byte): indicates the type of value associated to the tag. Boolean is for VT_BOOL a
boolean (True/False) value. A value of 0xFFFF (all bits at 1) indicates True; a value of 0 (all bits at 0)
indicates False. No other value is valid. Byte is for VT_UI1 an unsigned 1-byte character.
(11) open order address: this attribute is only significant if the attribute double address usage is set to
Yes. It defines the OPC tag name for the OPEN state
(12) Closed order address: this attribute is only significant if the attribute double address usage is set
to Yes. It defines the OPC tag name for the CLOSE state
T101/T104
(1)
(2)
(3)
(4)
DNP3
(5)
(6)
Modbus
(7)
OPC
(8)
(9)
(10)
(11)
(12)
Figure 45: Defining a SCADA address for a DPC datapoint

4.6.2.8 DEFINING A SCADA ADDRESS FOR A SETPOINT DATAPOINT

A SCADA address is added to a SetPoint datapoint from the contextual Objects entry window at the
SCADA SetPoint mapping level:
Figure 46: Adding a SCADA setpoint address
Once added, SCADA SetPoint address attributes must be set at SCE level:
(2) object address
(4) minimal value (range [-2147483648, 2147483647], step 1): available minimal value on the protocol
(used for scaling and checks)
(5) maximal value (range [-2147483648, 2147483647], step 1): available maximal value on the protocol
(used for scaling and checks)
(6) format (Normalized / Adjusted / Float)
(7) SBO time-out (s) (range [0 s, 255 s], step 1 s): time afforded the DS Agile system to acknowledge
the selection.
For DNP3 protocol:
(9) SCADA execute order type (Select execute / Direct execute): this attribute defines which type of
For OPC protocol:
(10) OPC address

T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
(7)
DNP3
(8)
(9)
Modbus
OPC
(10)
Figure 47: Defining a SCADA address for a setpoint datapoint

4.6.2.9 DEFINING A SCADA ADDRESS FOR AN MPS DATAPOINT

A SCADA address is added to an MPS datapoint from the contextual Objects entry window at the SCADA
MPS mapping level:
Figure 48: Adding a SCADA MPS address
Once added, SCADA MPS address attributes must be set at SCE level:
(2) bitstring usage (No / Yes): must be set to Yes. Indicates if the MPS is split or not.
(3) priority level (from 1 to 255): gives the priority of emission (1: higher). Only significant if Event
attribute is different from ‘No’. Is fixed to 1 for T104 protocol.
(4) Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’ (resp. ‘Yes
without time tag’), indicates if change of state of the datapoint are transmitted spontaneously with
(resp. without) time tag
(5) Event record: indicates if the datapoint will be recorded in the SOE file
(6) Background scan (No / Yes): indicates if the datapoint belongs to the background scan cycle
(7) Group ([0..16)] / 0=no group) (range [0,16], step 1) indicates to which “T101/T104 General
Interrogation group” the datapoint is assigned. 0 means ‘no group’ assignation.
(8) multistate address: not used, because the MPS is not split
(9) state_X address (0 to 15 for X): indicates the T101/T104 address which will be set if the MPS takes
the value X

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Figure 49: General attributes of an MPS address for the T101/T104 protocols
For DNP3 protocol:

(10) bitstring usage ( No / Yes): must be set to Yes. Indicates if the MPS is split or not.
(11) Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’ (resp. ‘Yes
without time tag’), indicates if change of state of the datapoint are transmitted spontaneously with
(resp. without) time tag
(12) multistate address: not used, because the MPS is not split
(13) state_X address (0 to 15 for X): indicates the DNP3 address which will be set if the MPS takes the
value X

(10)
(11)
(12)
(13)
Figure 50: General attributes of an MPS address for the DNP3 protocol


(14) state_X register address (0 to 15 for X): indicates the Modbus address which will be set if the MPS
takes the value X
(14)
Figure 51: General attributes of an MPS address for the Modbus protocol
For OPC protocol:

(16) Historization (No / Yes): indicates if this tag is sent at historic timer frequency
For MPS the format is set to VT_I2 (two-bytes integer)
(15)
(16)
Figure 52: Defining the general attributes of MPS address for the OPC protocol

4.6.2.10 DEFINING A SCADA ADDRESS FOR BYPASS SYNCHROCHECK

For details about synchronised circuit-breakers, refer to the C26x application chapter (C26x/EN AP).
Synchronised circuit-breakers can be controlled through a SCADA network. In that case, the SPC (resp.
DPC) control of the synchronised breaker is linked to a SCADA SPC (resp. DPC) address. Unfortunately,
bypass synchrocheck is not implemented in SCADA protocol. To solve this problem, an extra SCADA SPC
(resp. DPC) address that will bypass the synchro-check, must be given to the SPC (resp. DPC) control of the
breaker. At SCE level, this extra address is linked to the SCADA address of the SPC (resp. DPC) control of
the synchronised breaker.
To define a SCADA address for bypass synchrocheck:
 Create the SCADA SPC (resp. DPC) address (A) to send SPC (resp. DPC) control of the
synchronised breaker
 Create a SCADA SPC (resp. DPC) address (B) for bypass synchro-check in the SCADA mapping,
 Add the relation ‘has for bypass synchrocheck address’ via the “Object entry” area at SCADA address
(A) and fill it with the SCADA address (B).
Address (B)
Address (A)
C1112ENa
Figure 53: Adding a bypass synchrocheck address to a SCADA SPC/DPC address (example for a SCADA DPC
address)

4.6.3 ADDRESSING A DATAPOINT ON A SCADA LEGACY NETWORK

To exchange datapoint values between station-bus sub-systems and SCADA, datapoints should be linked to
specific SCADA addresses, by adding at datapoint level the relation ‘has for SCADA address’ (1) and filling it
with the corresponding SCADA address in a pre-configured SCADA addressing mapping (refer to section
4.6.2 Defining the address map of a legacy SCADA network, for SCADA mapping definition).
Addressing MPS datapoint on SCADA legacy network is not available.
Figure 54: Realising the SCADA addressing of a datapoint (example for a bay SPS datapoint)
4.7 SETTING SYSTEM INFORMATION FOR GATEWAY COMPONENTS

When creating a Gateway, specific datapoints are automatically added in ‘system infos’ binder (1) at
Gateway level or PLC sub-component.
So it is when adding a SCADA network (2) attached to a Gateway. In that case, the ‘system infos’ binder is
located under the relevant added object.
SCE calls such ‘system infos’ datapoints, system datapoints.
System datapoints provide real-time statuses and controls on system software or hardware components.
As datapoints, system datapoints must be linked to a profile. For details about datapoint and datapoint profile
configuration, refer to the C26x application chapter (C26x/EN AP). Depending on its kind, the system
datapoint and its relevant profile have specific attributes to be set correctly to ensure healthy behaviour of
DS Agile C26x controller. Hereafter, are listed the datapoint and profile requirements for each kind of system
datapoint.

Generally system datapoints are automatically addressed in IEC61850-8-1 mapping of the relevant DS Agile
C26x controller at their creation. If manual addressing is necessary, it is stressed in following chapters by
given the associated available data object of a given DS Agile C26x controller brick in LD0 (<brick
name>.<data object name>). For details about IEC61850-8-1 addressing see section 4.4 Networking a
Gateway on the station-bus network.
(2)
(1)
Figure 55: ‘System infos’ binders for a Gateway

4.7.1 SETTING THE GENERAL SYSTEM INFORMATION OF A GATEWAY

When creating a Gateway, the following mandatory datapoints are implicitly added.
(1)
(2)
(3)
(4)
(5)
Figure 56: Mandatory ‘System infos’ datapoints for a Gateway
These datapoints must be configured according to their described features:
 Control and status for database management

 DB switch ctrl SPC (1): only used by the SMT to turn device functioning mode to Maintenance or
Operational/Run
 Communication status
 Device link SPS (2): although this datapoint is under the Gateway, it is not managed by it. Each
IEC 61850-8-1 client of the Gateway computes locally this datapoint status by supervising the
IEC61850 real-time link with the Gateway. In fact, there are as many ‘Device link SPS’ per
Gateway as IEC 61850-8-1 clients connected to the Gateway. Fixed to ‘SET’ state if the device link
is operational.
 Controls and statuses for functioning mode

 Mode control DPC (3): only used by the SMT to turn device functioning mode to Maintenance or
Operational/Run
IEC 61850-8-1 addressing Available states
1 Operational/Run
2 Blocked
 LLN0.Mod
3, 4 Test, Test/Blocked
Automatic at datapoint creation
5 Maintenance
0 Faulty
 Operating mode MPS (4): the available states of this datapoint are:


0 Faulty mode
 LLN0.Mod 1 Operational mode
Automatic at datapoint creation 3 Test mode
5 Maintenance mode
 Synchronisation status
 Synchronisation SPS (5): fixed to ‘SET’ state if device is synchronised.
TGDIAG.SyncSt ‘RESET’: Not synchronised
Automatic at datapoint creation ‘SET’: Synchronised
4.7.2 SETTING SYSTEM INFORMATION OF PLC

 ISaGRAF status: common to both gateways in the cluster
0 ISaGRAF is running normally
1 not activated
Not automatic 2 cycle too long
3 queue overflow
4 Program Organisation Unit faulty
Note: In ISaGRAF (via the debugger), the values range from 1 to 5.
4.7.3 SETTING SYSTEM INFORMATION OF SCADA NETWORK

When creating a SCADA network, the following mandatory datapoints are implicitly added.
(1)
(2)
Figure 57: Mandatory ‘System infos’ datapoint for a SCADA network
These datapoints must be configured according to their described features:

 SCADA communication status SPS (1): fixed to ‘SET’ state if communication with the SCADA is
operational.
 TGDIAG.CommSt<i>
where <i> corresponds to the SCADA number (from 0 to 3).
‘RESET’: Communication not OK
Manually addressed in an IEC 61850-8-1 TGDIAG brick
‘SET’: Communication OK
Or
IEC 61850-8-1 SBUS Automatic addressing usage
 SCADA redundancy status SPS (2): fixed to ‘SET’ state if redundancy with the SCADA is active.
 TGDIAG.RedSt<i>
where <i> corresponds to the SCADA number (from 0 to 3).
‘RESET’: StandBy
Manually addressed in an IEC 61850-8-1 TGDIAG brick
‘SET’: Active
Or
IEC 61850-8-1 SBUS Automatic addressing usage

5 DEFINING A DS AGILE GATEWAY CONFIGURATION IN THE

ELECTRICAL HIERARCHY
The Gateway configuration is affected by the electrical architecture definition for the 3 following features:
 Defining Substation and Bay Local/remote dependencies

 Defining SBMC dependency
 Defining Taking control for substation and SCADA links
For other details about the definition of electrical topology, refer to the C26x application chapter
(C26x/EN AP).
5.1 DEFINING SUBSTATION AND BAY LOCAL/REMOTE DEPENDENCIES
5.1.1 INTRODUCTION
Local/remote for substation
A substation can be in remote or local control mode.
The Remote mode indicates that the substation is controlled from the Remote Control Point (RCP), via a
Gateway. No controls can be sent from the Substation Control Point level, except if the concerned bay is in
SBMC mode.
The Local mode indicates that the substation is controlled from DS Agile Operator Interface (Substation
Control Point). The controls issued from RCP are not taken into account by the system, they are refused.
Some controls, defined during the configuration phase, can be independent of the substation control mode: it
means they can be issued from SCP or RCP whatever the current control mode is. For details about the
configuration of this dependency attribute, refer to the following sub-sections.
For details about definition of Local/remote for substation, refer to the C26x application chapter
(C26x/EN AP).
Local/remote for bay
More, each bay can be independently in Remote or Local mode.
The Remote mode indicates that the bay is controlled from the upper level, i.e. Remote Control Point (RCP)
or Substation Control Point (SCP) depending on the current substation control mode. No controls can be
sent from Bay Control Point (BCP) level, i.e. operator interface at the DS Agile C26x controller that manages
the bay.
The Local mode indicates that the bay is controlled from BCP. The controls issued from upper level are not
taken into account by the bay.
Some controls, defined during the configuration phase, can be independent of the bay control mode: it
means they can be issued from any control points whatever was the current control mode. For details about
the configuration of this dependency attribute, refer to the following sub-sections.
In Local or Remote mode, the information issued from the bay is always sent to SCP and RCP.
To configure Local/remote bay refer to the C26x application chapter (C26x/EN AP).
5.1.2 SETTING THE ‘LOCAL/REMOTE DEPENDENCIES’ ATTRIBUTES OF A CONTROL

DATAPOINT
Control datapoints are SPCs, DPCs, and SetPoints.
Local/remote dependencies for controls at levels lower than or equal to bay
(1) Bay mode dependency (No / Yes)
(2) Bay control uniqueness dependency (No / Yes)

(3) Local Substation dependency (Command from SCADA is accepted / Command from SCADA is
refused).
(4) Remote substation dependency (Command from OI is accepted / Command from OI is refused).
Figure 58: Setting local/remote dependencies attributes to control datapoint (sample given at bay level for
generic SPC)
Local/remote dependencies for control at levels higher than bay

(1) Substation control uniqueness dependency (No / Yes)
Figure 59: Setting local/remote dependencies attributes to SPC datapoint (sample given at voltage level for a
generic SPC)

5.2 DEFINING THE SBMC MODE FOR A BAY
5.2.1 INTRODUCTION
Any electrical bay can be separately switched to SBMC mode (Site Based Maintenance Control mode) using
a dedicated control datapoint (SBMC control SPC). While the bay is in SBMC mode, its datapoints that have
been defined as SBMC-dependent are processed according to different rules:
 While in SBMC mode, an electrical bay does not receive, and therefore does not execute, SBMC-
dependent xPC commands received from the Remote Control Point (RCP), even if the substation is in
remote mode and whatever device manages them.
It is possible, however, to configure some xPC datapoints to be independent of the SBMC mode. For
details about the configuration of the dependency attribute, refer to section 5.2.3 Setting the ‘SBMC
dependency’ attribute of a control point.
 Whatever the device that manages it, if an indication datapoint belonging to a bay that is in SBMC
mode is configured as SBMC-dependent (in its profile), the Gateway sends the SBMC state defined in
its profile to the RCP. It is, however, still processed normally at the substation control system level (i.e.
none of the processes inside the system are impacted by the state alteration of an information at the
RCP interface).
Note:
The SBMC Control SPC/SBMC SPS datapoints only affect SBMC-dependent datapoints attached to the same electrical
bay.
The states of indication datapoints sent to the RCP in SBMC mode are configured in their profile. The
available SBMC states vary depending on the type of datapoint:
SPS SUPPRESSED, SET, RESET
DPS SUPPRESSED, OPEN, CLOSE, JAMMED
MPS SUPPRESSED, UNDEFINED
MV, TPI and Counter SUPPRESSED
Datapoint configuration is described in the C26x Application chapter and is not repeated
in this manual. Please refer to C26x/EN AP for details, in particular section 4.2 Creating a
datapoint profile.
5.2.2 SBMC STATE INDICATION: MAIN TOPOLOGIES

Configuration constraints vary depending on:
 for IEC 61850-8-1 lower networks, whether the SCADA is connected to the upper or lower network
 whether or not there is a legacy IEC 60870-5-101 Master (T101M) / IEC 60870-5a104 Master (T104M)
network connected to the Gateway
Note:
See section 6 Defining an IEC61850/IEC61850 Gateway configuration for information on how to create an
IEC 61850/IEC 61850 configuration database.

5.2.2.1 SBMC STATE INDICATION WITH SCADA CONNECTED TO THE LOWER NETWORK
IEC/IEC WITH SCADA CONNECTED TO LOWER NETWORK
Operator Interface
(only receives SBMC
state indication)
UPPER IEC 61850-8-1 NETWORK
No SBMC control
through IEC/IEC
gateway
SCADA
IEC/IEC (manages SBMC)
Gateway
Gateway
LOWER IEC 61850-8-1 NETWORK
IEC 61850 IED

C26x-1
SBMC L-Bay2
SBMC L-Bay1
System Bay 2
System Bay 1
S1053ENb
Figure 60: Example of IEC 61850-8-1/IEC 61850-8-1 dual network with SCADA connected directly to the lower
network
Lower network database

The SBMC function must first be added at bay level:
 add the datapoints SBMC SPS (1) and SBMC control SPC (2), from the contextual Objects entry
window at bay level,
 configure them (see C26x Application chapter, C26x/EN AP),

 do not forget to link the control of the SBMC with the SBMC status datapoint using a has for
feedback relation.

(2)
(1)
Figure 61: Defining the SBMC mode for a bay in the lower level database where the SCADA is connected to the
lower network
Only the SPS datapoint can have a SCADA address and be transmitted to the upper network: Select each
datapoint in the Object view, then add a relation is transmitted on IEC 61850 SCADA network from the
contextual Objects entry window and set it. If the SPS datapoint is to be transmitted to the lower network's
SCADA, also add a relation has for SCADA address.
Neither SBMC datapoint may be used in an ISaGRAF automation.
Upper network database

If the SCADA is directly connected to the lower network, its Gateway manages SBMC filtering. Since SBMC
enable/disable control commands cannot be sent through the IEC 61850/IEC 61850 Gateway, any Operator
Interface connected to the upper network can only receive the SBMC state indications from the lower
network. Therefore, the SBMC control SPC datapoints must be deleted from the upper network database,
keeping only the SBMC SPS datapoints.

5.2.2.2 SBMC STATE INDICATION WITH SCADA CONNECTED TO THE UPPER NETWORK
IEC/IEC WITH SCADA CONNECTED TO UPPER NETWORK
Operator Interface SCADA

(manages SBMC)
(manages SBMC)
Gateway
UPPER IEC 61850-8-1 NETWORK
No SBMC control
through IEC/IEC
gateway
IEC/IEC
Gateway
In lower DB SBMC is replaced

with standard Bay SPC/SPS,
set to be SBMC-dependent
In upper DB "true" SBMC
LOWER IEC 61850-8-1 NETWORK pairs linked to L-Bay1 SBMC
and L-Bay2 SBMC, seen as
coming from an IED
C26x-1 C26x-2
SBMC L-Bay1 SBMC L-Bay2
S1054ENb
Figure 62: Example of IEC 61850-8-1/IEC 61850-8-1 dual network with SCADA connected to the upper network


SBMC SPS (1)/SBMC Control SPC (2) datapoints must be added under each SBMC-dependent bay.
Figure 63: Defining the SBMC mode for a bay in the lower level database where the SCADA is connected to the
upper network

An SBMC indication datapoint (SBMC SPS (1)) must be configured under each SBMC-dependent bay. They
must be given the same IEC 61850-8-1 address as their source datapoints in the lower network database.
 add the SBMC SPS (1) datapoint from the contextual Objects entry window at bay level
 configure it (see C26x Application chapter, C26x/EN AP)
Figure 64: Defining the SBMC mode for a bay in the upper level database where the SCADA is connected to the
upper network
The SBMC-dependent datapoints must all have a SCADA address: Select each datapoint in the Object
view, then add a relation has for SCADA address from the contextual Objects entry window and set it.
None of the SBMC datapoints may be used in an ISaGRAF automation.

5.2.2.3 GLOBAL SBMC STATE INDICATION FROM A LEGACY NETWORK (T101M/T104M) VIA AN
IEC 61580 NETWORK
A group of legacy IEDs connected to a IEC 60870-5-101 or IEC 60870-5-104 lower network can be assigned
a global SBMC enable/disable using the Integrated control function of an IEC 61850/IEC 61850 Gateway.
Note:
Global legacy network SBMC state indication can only be sent to the SCADA if the Gateway also manages an
IEC 61850 master communications protocol.
In the upper network, SBMC

LEGACY T10xM (WITH FICTICIOUS LOWER IEC NETWORK) datapoints are replaced with Bay
SPS/SPC.
UPPER NETWORK DB SCADA In the lower network, "true" SBMC
(manages SBMC) datapoints are used.
Operator Interface
(manages SBMC)
Gateway Datapoints to and from IEDs are

"SBMC-dependent" in the database
that contains the Gateway that
manages SBMC (upper level if it is the
Gateway to the SCADA, lower level if
UPPER IEC 61850-8-1 NETWORK is the IEC/IEC Gateway).
Legacy T10x IED group

IEC/IEC Legacy T10xM protocol
Gateway
IED1
Integrated control Integrated control manages SBMC IED Bay1
datapoints: 1 SBMC datapoint pair
common for all bays under T10xM
IED2
IED Bay2
C26x
FICTICIOUS LOWER
IEC 61850-8-1 NETWORK ficticious C26x managing
L/R for S/S (not used)
LOWER NETWORK DB
S1055ENb
Figure 65: Example of legacy network connection to an upper IEC 61850-8-1 Station Bus
Create and configure the legacy network as explained in section 4.5 Networking IEDs on a Gateway's legacy
network of this chapter.


The SBMC function must first be added at bay level:
 add the datapoints SBMC SPS (1) and SBMC control SPC (2), from the contextual Objects entry
window at bay level. This bay must be managed by the Gateway.
 configure them (see C26x Application chapter, C26x/EN AP),

 do not forget to link the control of the SBMC with the SBMC status datapoint using a has for
feedback relation.
In this topology the state of the SBMC SPS is UNKNOWN by default whatever the value
set in its profile. Therefore, ensure that the attribute "status check for command" is not
set to "Control authorized only if the device is in the opposite state" in order to be able to
send a command to the SBMC SPS.
(2)
(1)
Figure 66: Defining the SBMC mode for a bay in the lower level database containing the legacy network
Both datapoints must have a SCADA address in order to be transmitted to the upper network: Select each
datapoint in the Object view, then add a relation is transmitted on IEC 61850 SCADA network from the
contextual Objects entry window and set it.
Neither SBMC datapoint can have an SBUS address and they must not be used in an
ISaGRAF automation.
In addition to the SBMC datapoints, add a C26x. Configure this C26x to virtually "manage" Local/Remote for
the substation. This is due to the fact that although Local/Remote is not used, its presence is mandatory to
generate the configuration databag.

In the Scs branch:
 Select the IEC 61850 protocol and set the attribute Check Local/Remote to No.
Figure 67: Setting the IEC 61850-8-1 network's Check Local/Remote attribute to No so that no datapoint states
nor commands are blocked by the IEC 61850/IEC 61850 Gateway
(1) Select the Gateway's System Group and add to it a "C264" from the contextual Objects entry
window.
(2) Select the C264 and fill in the relation is located in: substation
Figure 68: Adding a "virtual" C26x

In the Site branch:

(3) Select the substation and add the local/remote datapoints (Loc/rem control DPC/Local/remote DPS)
from the contextual Objects entry window.
(4) Set the relation has for default IEC61850 server to the C264.
(3)
(4)
Figure 69: Adding local/remote datapoints to the substation and linking it to the "virtual" C26x


Since SBMC enable/disable control commands cannot be sent through the IEC 61850/IEC 61850 Gateway,
a pair of standard SBMC SPS (1)/SBMC control SPC (2) datapoints must be added under one of the
electrical bays. They must be given the same IEC 61850-8-1 addresses as their SBMC counterparts in the
lower network database.
(2)
(1)
Figure 70: Defining the SBMC mode for a bay in the upper level database
SBMC dependency for datapoints in electrical bays managed by legacy IEDs on the T10xM network
Because SBMC is managed by the upper network Gateway connected to the SCADA, the datapoints
transmitted to and from the legacy IEDs and the electrical bays they manage should be SBMC-dependent
(SBMC and value parameters in profile for xPS and SBMC mode dependency attribute for xPC) in the
upper network database.
For details about SBMC configuration at datapoint profile level, refer to the C26x Application chapter
(C26x/EN AP).

5.2.3 SETTING THE ‘SBMC DEPENDENCY’ ATTRIBUTE OF A CONTROL POINT

Control datapoints are SPC, DPC, and SetPoint.
SBMC dependencies for control whose level is less or equal to bay
(1) SBMC mode dependency (No / Yes)
(1)
Figure 71: Setting SBMC dependency attributes to control datapoint (example given at bay level for a generic
SPC)
5.3 DEFINING TAKING CONTROL FOR SUBSTATION AND SCADA LINKS

This facility allows a Remote Control Point (RCP) to force the mode of the substation from LOCAL to
REMOTE and to define on which link the SCADA controls must be accepted.
So, Local/remote for substation must be defined before any Taking control configuration.
To activate Taking control facilities for a given SCADA network:
 add the optional datapoints ‘Taking Control’ (2) and ‘Taking status’ (1), via the contextual Object entry
window at substation level by clicking on mouse’s right button
 configure them
 add the relation ‘is taken control of’ at ‘Taking status’ datapoint level (3), and fill it with the relevant
given SCADA network
 do not forget to link via ‘has for feedback’ relation, the control with the status datapoint

Figure 72: Defining taking control for a SCADA link

 If, at least, one SCADA network is linked to a Taking Control function, all the SCADA Networks of the
system must be linked to a Taking Control function.
 If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a "Taking
Control" datapoint through the relation "has for feedback".
 A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the relation "has for
feedback".
 The "Taking Control" datapoint must have its "activation mode" attribute set to a "Permanent…" value.
The "Taking Status" datapoint must have its "detection mode" attribute set to the "Permanent" value.
 Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA address in the
mapping of their SCADA network.
 If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" for substation must be present and
not wired.
 The Server of the Local/Remote Datapoints is the Server of each Datapoints couple "Taking Status" /
"Taking Control".
 All the devices having a SCADA network linked to a Taking-Control function are:
- Clients of each Datapoints couple "Taking Status" / "Taking Control".
- Clients of the Datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
5.4 DEFINING FFS (FORCE/SUPPRESS/SUBSTITUTE) PROCESSING FOR

DATAPOINTS
The states of some datapoints can be manually changed from the Operator Interface using an FSS viewer
(see the DS Agile OI manual for information on how to configure (AP chapter) and use (HI chapter) FSS
viewers.
Defining which datapoints are available for an FSS operation is done in their profile by setting the attribute
FSS to Yes for each associated profile.
Datapoint configuration is described in the C26x Application chapter and is not repeated
in this manual. Please refer to C26x/EN AP for details, in particular section 4.2 Creating a
datapoint profile.
Note that automatic forcing is not managed by the DS Agile Gateway. Any forcing management settings in xPS
attributes is applicable only to the DS Agile C26x BCU.

6 DEFINING AN IEC61850/IEC61850 GATEWAY CONFIGURATION

An IEC61850/IEC61850 Gateway connects two IEC 61850-8-1 station bus networks called the lower
network and the upper network.
In this section is described the way to configure the Gateway on both networks
a
ad
Sc
Figure 73: Two-network architecture

6.1 CONFIGURING THE GATEWAY IN THE LOWER NETWORK

The actions described below are the last things the user has to do: s/he has already built the configuration
for this network. In the example given below the name of the database is Energy_lower.mpc
Caution:
Make sure that in this database, all entity names are unique; entity refers to substation,
voltage level, bay, module, datapoint, IEC physical device.
1 Open this database, add a Gateway. Enter the name and the TCP/IP address of this Gateway on the
lower network (GTWM, 192.168.0.15 in our example). If required, set the attribute Acquisition
available on IEC61850 to Yes.
Figure 74: General attributes of the Gateway in the lower network
2 Add an IEC 61850-8-1 protocol SCADA network to this Gateway, then set the TCP/IP address of this
Gateway on the upper network, in this example: 192.169.0.55
Figure 75: General attributes of the IEC 61850-8-1 SCADA protocol
The attribute Check Local/Remote defined if the Substation Local/Remote information has to be used by an
IEC61850/IEC61850 gateway. The Substation Local/Remote xPS comes from the lower IEC 61850-8-1
network.

If the L/R function is managed (attribute set to Yes), the controls coming from the upper network:
 are sent to the lower network if the substation mode is “Remote” and if the controls are dependent on
the L/R mode
 are sent to the lower network if the controls are independent of the L/R mode
 are negatively acknowledged (“bay-substation mode fault” ack) if the substation mode is “Local” and if
the controls are dependent on the L/R mode
If the L/R is not managed (attribute set to No), the controls coming from the upper network are sent to the
lower network regardless of the L/R mode.
1 From IEC61850 protocol, launch the Edit relation in the contextual menu, click on the tab To, click on
the item transmits: Datapoint [0..65535].
Figure 76: Defining datapoints to be transmitted to the upper network

In the list of the datapoints that can be linked to this protocol select those you want to be transmitted to the
upper network and then click the Apply button.
Do not transmit the Operating mode of the Gateway from lower network to upper network.
Please note that the selected datapoints must have an IEC address.
2 Check in and Generate the lower database.
Before starting the next steps, make sure that the files: Energy_lower.x.y.bup.zip, Energy_lower.x.y.zip
and Energy_lower.x.y.scadaSbusDm.zip are under the directory target of the generation (C:\Temp).
3 Extract the GTWM_PROT1_x.y.xml file from the Energy_lower.x.y.scadaSbusDm.zip archive.
4 Copy the lower database file (Energy_lower.mpc) in order to use it as base of work for the upper
database file (Energy_upper.mpc).
6.2 CONFIGURING THE GATEWAY IN THE UPPER NETWORK

The actions described below are the first things the user has to do.
1 Open the upper database (Energy_upper.mpc) and delete all IEC physical devices from system part
(Scs) and all FBD equations. Do not change the name of the substation. In the Scs node, change the
TCP/IP addressing for SMT and for SNTP server.
2 On the system part, add an IEC61850 generic IED, set its short name, long name, network name and
its TCP/IP address, the same as the IEC61850/IEC61850 gateway on the lower network, in our
example: GTWM and TCP/IP address: 192.169.0.55
Figure 77: General attributes of the Gateway in the upper network
3 From the Gateway, launch the Edit relation in the contextual menu, click on the tab To, click on the
item "manages: Bay [0..65535]".

The list of bays which can be managed by the gateway is displayed. Select those you want to be managed
by the Gateway, then click on the Apply button. The datapoints you wish to use on the upper network need
to be part of the selected bays.
Figure 78: Defining the bays to be managed by the gateway
4 Import the xml model GTW_IEC_PROT1_x.y.xml file.

Figure 79: Importing the XML model of the Gateway
5 Click on Import… to browse the PC in order to find out the xml file
6 In the upper area, select the xml file, then in the tree, select the gateway then click on Set (a message
box is displayed “IED model import in progress please wait”)
7 Click on Close (a message box is displayed “IED model setting in progress, please wait"); the attribute
model file name takes the name of the xml file

At the completion of the import process, a binder called Virtual nodes is created; transfer all their has for IEC
address relations to the electrical part (menu Edit relations), then delete the virtual nodes.
1 On GTW_IEC, change the short name and long name of the Operating mode (MPS). These names
must not be the same as name of Operating mode of the Gateway on the lower network.
Figure 80: Change short name & long name of operating mode
2 Change the short name, long name, network name and TCP/IP address of OI server to match the
upper network.
3 Fill the relation between OI server and IEC 61850/IEC 61850 Gateway (named "has for IEC61850
server").
4 Remove any unlinked wiring.
5 Check in and generate the upper database before completing the rest of the configuration.
Note:
Some errors might appear for example due to SBMC dependency being set to Yes in the bay attributes of upper level;
in this event, suppress the datapoint or make sure that SBMC is defined in the lower network database.
If the IEC 61850/IEC 61850 Gateway provides xPS through BRCB to the upper network clients (refer to
section 4.3), SCE creates automatically a Buffer overflow SPS in a virtual node. To make it available to
TBUS clients, it must be assigned an IEC 61850-8-1 address through the relation ‘has for IEC address’.

7 ISAGRAF IN A WIDE AREA CONTROL UNIT (WACU)

ISaGRAF can be installed in a single WACU or in a WACU redundancy cluster (in this case, it is mandatory
to install ISaGRAF on both WACUs).
Refer to:
 chapter SCE/EN AP for a description of the main ISaGRAF concepts and the electrical configuration
 section 4.7.2 for the system information ISaGRAF status
7.1 DEFINING AN ISAGRAF PROJECT
7.1.1 CREATE A BAY MANAGED BY THE WACU

First of all, create a bay managed by the WACU. Add slow automation managed by the WACU in this bay.
Figure 81: Bay managed by a WACU
Reminder:
The WACU sends inputs (xPS, counter and MV) only upwards (to SCADA, or upper network in
IEC 61850/IEC 61850 configuration). This means that the inputs of the bay managed by a WACU are only
transmitted to SCADA or upper network, not to the lower network. Consequently, for example, a lower OI
cannot display any information about the bay.
Outputs (xPC and SetPoints) are only sent downwards. This means that the outputs of the bay are only
transmitted to the lower network.

7.1.2 DEFINING AN ISAGRAF SLOW AUTOMATION

Creating the slow automation for GTW is identical to creating a slow automation for C26X. Refer to chapter
SCE/EN AP, “Defining ISaGRAF slow automation” for detailed description.
7.2 SPECIFIC ISAGRAF FOR REDUNDANCY CLUSTER

In case of WACU redundancy, ISaGRAF is duplicated, and has to switch together with the WACU. As it
depends on client requirements, the automation is not defined in advance.
So, in addition to the automation(s) already created, the automation engineer must create a switching
program. Refer to the chapter SCE/EN AP, section “Switch automation for redundancy”. This program
doesn’t need any datapoint declared.

HUMAN INTERFACE
GTW/EN HI/C57
DS Agile Gateway & WACU Human Interface
Contents
1 RUNNING THE GATEWAY 3
2 DS AGILE GATEWAY INTERFACE 4

2.1 “Equipment status” button 4
2.2 “Digital status” button 5
2.3 “Analog status” button 6
2.4 “Bay status” button 6
2.5 “Control history” button 7
2.6 “Components Versions” button 8
2.7 “Erase All” button 8
2.8 “Protocols” information 9
2.9 “About” information 9
3 EXIT THE PROGRAM 10
GTW/EN HI/C57 HI-1

Human Interface DS Agile Gateway & WACU
HI-2 GTW/EN HI/C57

1 RUNNING THE GATEWAY

As for all other executables programs, double-click on the shortcut “DS Agile Gateway” on the desktop, to
run it. Gateway‘s console looks like this:
Figure 1: DS Agile Gateway default window
Check first that there is no starting problem (initialisation problem, configuration problem, running the
processes, ...) by checking information on the main application list box. If no error message occurs, all is
right.
The “Analog log” check-box allows to display the traces of measurements (if checked).
The “Digital log” check box allows to display the traces of digital measurements.
The “Protocol in Taking Control” area gives the current protocol which is in taking control.
GTW/EN HI/C57 HI-3

2 DS AGILE GATEWAY INTERFACE
2.1 “EQUIPMENT STATUS” BUTTON

This button allows you to access some information about equipment for example information coming from
the configuration (like equipment type: computers, …) and some other information on the equipment states.
Information are automatically refreshed every 10 seconds or by clicking on “Refresh now!” button.
Equipment states are brought from system . On the following window we can look what information are
displayed:
General information:
• Field Ref: equipment ident [equipment ident is network number x 256]

• Field Type: this is the equipment type: "CXXX", "HMI", "GTW", "IED"
• Field Coherency: this field indicates coherency equipment.
System information:
• Field Presence: Present if the equipment is seen as present, or Absent when equipment is
disconnected, or when the link is broken between Gateway and equipment. If this field is Absent all
the other following fields are filled with ‘*’ symbol.
• Field L/R: state of the LocRemDS, so the Local/Remote information. When equipment is in local
mode, SCADA cannot send a command on it.
• Field Status: state of the ModeDS. The states are: Maintenance or Operational or Test or Faulty
• Field Date Synchronised: Synchronised or Not synchronised.
Redundancy information:
• Field Use Red.: This field means if the equipment used the redundancy Yes or No.
• Field Red. Type: This field indicates if the equipment is Master or Slave.
• Field Red. Eqp. associated: This field indicates the name of redundant equipment.
• Field Redundancy Mode: state of the RedSt equipment. The states are: Standby, Active or if
indeterminate*.
Figure 2: Equipment status window
HI-4 GTW/EN HI/C57

2.2 “DIGITAL STATUS” BUTTON

This button allows having some information about Digital Inputs. You just have to choose the desired server
and the desired equipment with selecting them with the drop list boxes, and indications about these digital
inputs are displayed. Indications are automatically refreshed every 10 seconds, but you can also refresh
them immediately by clicking the “Refresh now !” button. The check box Configured only allows you to
see the not configured points in configuration when you disable it.
Displayed indications about digital inputs are the following:
Figure 3: Digital input status window
• Field Index: you can see here the Digital Input type and the offset of the Digital Input in the equipment
(network physical DI: PHYS, system DI: SYST).
• Field Reference: this is the internal reference of the Digital Input in the configuration. Two Digital
Inputs cannot have the same reference.
• Field Status: indicates the State and the Quality Descriptor of the information.
• Field Type: Single, Double, MPS_POC, MPS_PSE or Bitstr type.
• Field Date: this is the date of the last change for the Digital input.
• Field Date Synchronised: Synchronised or Not-Synchronised.
GTW/EN HI/C57 HI-5

2.3 “ANALOG STATUS” BUTTON

This button allows having some information about Analog Inputs. You just have to choose the desired server
and the desired equipment with selecting them with the droplist box, and informations about these analog
inputs are displayed. Informations are automatically refreshed every 10 seconds, but you can also refresh
them immediately by clicking the “Refresh now !” button. The check box Configured only allows you to
see the not configured points in configuration when you disable it.
Displayed informations about analog inputs are the following:
Figure 4: Analogue input status window
• Field Index: you can see here the AI type and the offset of the Analog Input in the equipment.
[network AI: physical AI: PHYS, accumulators: ACCU].
• Field Reference: this is the internal reference of the Analog Input in the configuration.
• Field Status: this is the current status of the analogue. It could be VALID, INVALID, SUBSTITUTED,
FORCED, SUPPRESSED, UNKNOWN, SATURATED, UNDEFINED, OPEN CIRCUIT, THRESHOLD
L, LL, LLL, H, HH or HHH.
• Field Value: the value of the Analog Input displayed in a float format.
• Field Date: this is the date of the last change for the AI.
• Field Date Synchronised: Synchronised or Not synchronised.
2.4 “BAY STATUS” BUTTON

This button allows having the local/remote mode and the SBMC mode of a bay. You just have to choose the
desired server with selecting them with the droplist box, and informations about the managed bays are
displayed. Informations are automatically refreshed every 10 seconds, but you can also refresh them
immediately by clicking the “Refresh now !” button.
HI-6 GTW/EN HI/C57

2.5 “CONTROL HISTORY” BUTTON

This window is used to follow step by step what happen during the commands. This window is not refreshed
automatically, but you can also refresh them immediately by clicking the “Refresh” button.
Each time a command is processed a new line is added to the history. The next window shows you one
example of commands sent to the gateway (it’s the state COM between SCADA command whose indicated
the LOST com with SCADA).
Figure 5: Command history window
The information available on this window is the date of the event, the protocol number [following the
configuration range] who sent the command. You can erase history by clicking the “Erase” button.
The messages that can be displayed for commands are:
• Organe send to the system (waiting now the Acknowledge)

The Organe is sent to the system and the gateway expects now an acknowledge from the equipment.
• Organe has failed (Status point invalid or absent)

The Organe has been sent to the system, but there is a problem with the checkback point. Point is
disconnected or invalid.
• Delay time has expired (no change detected)

Organe has been sent, but not change has been detected.
• System L/R DI error

Equipment is invalid or disconnected, or link has been lost between client and server, so the L/R DI
state cannot be checked.
• System L/R DI not in remote mode

Organes are not allowed because the system is in local mode.
• Equipment reference X (network: N equipment: E) is not present

The equipment with reference X is not present.
GTW/EN HI/C57 HI-7

• Equipment reference X (network: N equipment: E) is not accessible because the associated bay is in
SBMC mode.
The equipment with reference X is not accessible with the Organes, because the associated bay has
been switched to SBMC Mode.
• Scada Organ is not compatible with configuration

The SCADA Organ sent to the gateway does not match what is configured in database. For example,
this error may occur when you send an OPEN command on a CLOSE point.
2.6 “COMPONENTS VERSIONS” BUTTON

This button is used to display the different versions of components (used in Gateway):
Figure 6: Component version display
2.7 “ERASE ALL” BUTTON

This button is used to erase all main list boxes. Warning: this action doesn’t erase the log book information.
HI-8 GTW/EN HI/C57

2.8 “PROTOCOLS” INFORMATION

This field is used to indicate which protocols are currently running:
Figure 7: Protocols information
2.9 “ABOUT” INFORMATION

You can access the “About” information by clicking the “About” button. Information displayed is the
following:
Figure 8: Gateway component version
This is here that you can check the gateway version, and all components Gateway versions. Provided
informations are the same as with the “Components versions” button.
GTW/EN HI/C57 HI-9

3 EXIT THE PROGRAM

To exit the program, click the cross on the right upper corner of the window. Closing might take some time.
HI-10 GTW/EN HI/C57

MAINTENANCE
GTW/EN MF/C57
DS Agile Gateway & WACU Maintenance
Contents
2 REGISTRY 6
2.1 DS Agile kernel 6
2.2 GENECDD 9
2.3 Redundancy 9
2.4 T101 10
2.5 T104 20
2.6 Common T101 / T104 24
2.7 Modbus 25
2.8 IEC 61850-8-1 25
2.9 DNP3 26
2.10 OPC 27
2.11 Additional board Hopf for time synchronization 28
3 FILES INSTALLED BY SETUP PROCEDURE 29

3.1 Directory Ecdd1 and 2 29
3.2 Other executables and DLLs 29
3.3 Data model file 30
3.4 Debugging tools 30
4 OPERATION TRACES 31
4.1 Translation of DS Agile Gateway’s ID tool 31
4.2 Find the translation manually 31
4.3 Run-time traces 32
5 DIFFERENT COMPONENTS TO DEBUG 33

5.1 Traces 33
5.2 LogBook 33
5.3 Translatefile 33
5.4 WatchDog 33
5.5 Configuration files 33
6 DBGVIEW 34
6.1 Installation Dbgview 34
6.2 Capturing Debug Output 34
6.3 Parameter setting 35
6.3.1 Depth of History 35
6.3.2 Time Format 36
6.3.3 Filters 36
6.4 Stop traces 37
6.5 Saving and Logging of traces 38
6.5.1 Parameter setting: «Logging to a File» 38
6.5.2 Saving Output 39
GTW/EN MF/C57 MF-1

Maintenance DS Agile Gateway & WACU
7 VIEWTRACE 40
7.1 Installation View Trace 40
7.2 Capturing Debug Output 40
7.3 Parameter setting and Use 41
7.4 Depth of History 42
7.5 Select Protocol 43
7.6 Filters 44
7.7 Start/Stop traces 45
7.8 Saving of traces 46
7.9 Comment File 47
7.10 Import File 48
7.11 Frame Analysis 49
7.12 Backup mode 49
8 INTERPRETATION OF TRACES 50
8.1 Protocol Trace Format 50
8.1.1 Message dump 50
8.1.2 Tele-status Trace Format 50
8.1.3 Tele-measurement Trace Format 51
8.2 Redundant Trace Format 51
8.3 DS Agile Gateway kernel trace Format 51
9 DS AGILE GATEWAY HMI 53

9.1 Components versions 53
9.2 Server Equipment Status Trace Format 54
9.3 Digital Trace Format 54
9.4 Analog Trace Format 55
9.5 Command Trace Format 55
9.6 Communication Trace Format 55
10 INSTALLATION TRANSLATEFILE 56
10.1 TranslateFile 56
11 WATCHDOG.LOG 57
12 CONFIGURATION FILES 59
12.1 Uca2_OMM.xml 59
12.2 Gateway.txt 59
12.3 Gateway_comp.txt 59
12.4 GTWIdToUca2 59
13 PORTMON 60
13.1 Installation PortMon 60
13.2 How to use 60
14 FAQ 62
14.1 T101: How to convert a T10x decimal address into a structured address? 62
MF-2 GTW/EN MF/C57

14.2 Filtering & traces 62

14.3 Command & traces 62
14.4 Loss of communication 65
GTW/EN MF/C57 MF-3

MF-4 GTW/EN MF/C57


This document describes maintenance (MF) procedures and tools of DS Agile Gateway for debugging and
traces.
This chapter explains how to use the DS Agile Gateway registry allowing you to control the DS Agile
Gateway behaviour and to recover from minor fails. It describes the files installed by the setup.exe procedure
the check the installation.
GTW/EN MF/C57 MF-5

2 REGISTRY
2.1 DS AGILE KERNEL

[HKEY_CURRENT_USER\Software\DCS\Tg\Main]
Key Format Default Min Max Modifiable Comment
Time (in milliseconds) of reading an
acquisition
"st_SO_Lire" dword 2500 ms 5000 ms 30000 ms Y
This key is created by the DS Agile
Gateway’s kernel.
Time (in milliseconds) of polling an
acquisition.
"st_SO_Remon" dword 30 ms 15 ms 100 ms Y
Gateway’s kernel.
Time (in seconds) of waiting to send
states information to protocols after a
DS Agile Gateway initialization.
Gateway’s kernel.
"timer_init" dword 0s 0s 120 s Y
A value different than 0 might result in
bufferized events in an IEC/IEC
gateway (if bufferization is
configured) being not.sent to the
SCADA
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg]
Path where kernel is
"InstallPath" string "C:\\Program Files\\Alstom\\DCS\\Gateway" NA NA N installed. Updated
by setup wizard.
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\acq]
This value is entirely controlled
by the DS Agile Gateway’s
kernel.
The DS Agile’s setup wizard
creates this key with the
default value 0
The DS Agile's kernel initializes
this key with the value set in
key NbDetectWDDefault.
NbDetectWD- Each time a watchdog
"NbDetectWDCurrent" dword 0 0 N
Default occurred this value is
decreased.
When NbDetectWDCurrent < 0
or null the PC is automatically
rebooted
Each time DS Agile Gateway
changes exploitation mode
from maintenance to
exploitation, the value is set to
NbDetectWDDefault
MF-6 GTW/EN MF/C57


Number of maximum
consecutive detection of
watchdog failure authorized
before automatic reboot of the
"NbDetectWDDefault" dword 3 1 10 N PC.
The DS Agile Gateway's setup
wizard creates this key with the
default value 3.
Period in seconds of the IEC
61850-8-1 SBUS Agency’s
HeartBeat
= 0: no HeartBeat
"PeriodHeartBeat" dword 7s 0s 120 s Y > 0: Period in Seconds of the
HeartBeat
The DS Agile Gateway 's setup
default value 7.
Delay in seconds.
The DS Agile Gateway 's setup
"PeriodScrutation" dword 25 0 120 Y default value 25.
At timeout DS Agile Gateway
kernel verifies that it received,
at least, one heartbeat
Acquisition type
1: DS Agile Station Bus
Acquisition
"typeacq" dword 01 0 3 N
At the creation process this key
is created by the DS Agile
Gateway 's kernel.
Acquisition type on DS Agile
SBUS
1: UCA2
"typeSBUS" dword 02 1 2 N
2 : IEC 61850-8-1 Acquisition
This key is created by the
setup.
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\BD]
Version of the BD N°1
x.y: version.revision
"bd1" string "0.0" NA NA N
Value entirely controlled by the DS
Agile Gateway’s kernel
Version of the BD N°2
x.y: bd version.revision
"bd2" string "0.0" NA NA N
Number of the BD actually loaded
1: BD N°1
"current_bd" dword 1 1 2 N 2: BD N°2
GTW/EN MF/C57 MF-7

[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\Main]
Boolean that defines DS Agile
Gateway behaviour in case of SBUS
disconnection.
"maintenance_if_
dword 0 0 1 Y 0: no action
dcnx_ethernet"
1: DS Agile Gateway pass in
maintenance while cable is
disconnected
Time (in minutes) to display DI or AI
in DS Agile Gateway logbook. In "DI
"timer_log" dword 60 mn 1 mn 120 mn Y log" or "analogue log" is checked, DS
Agile Gateway displays AI and or DI
during this time.
This key indicates if traces are
available on hard disk:
In Windows XP Embedded, the key is
always created with value = 0.
In Windows XP Professional and
Windows 7 Ultimate 64 bits, the key
is always created with value=1
This key is periodically read (period
(heartbeat or
Flag_log maintenance_dcnx_ethernet)). The
dword 0 0 2 y key can be set at any time
If the key value = 2 then when the
Gateway restarts the key will be
written with the value 1 to allow the
write while the start.
If the key value = 0 or 1 then when
the Gateway restarts the key will be
written with the value 0 in Windows
XP Embedded or 1 in Windows XP
professional and Windows 7 Ultimate
64 bits (default values).
This key indicates the behaviour of
the SCADA time stamping of a
"Unknown" Datapoint, when
equipment is disconnected.
KEY_T0_T1_T0 dword 0 0 1 y 0 : behaviour of the specification :
time stamped at T0 (Date of the last
state change)
1 : New behaviour : time stamped at
T1 (Date of the disconnection)
Boolean that defines DS Agile
Gateway behaviour in case of C26x
connection /disconnection.
1: in T101 and T104 all events are
cot3_at_
dword 0 0 1 Y sent with COT 3 in case of
reconnexion
connection/disconnection of a piece
of equipment on SBUS.
0: on connection all data are sent with
an ORCAT relative to origin event.
MF-8 GTW/EN MF/C57

[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\System]
System Revision
x: system revision
The DS Agile Gateway’s kernel
"SystRev" dword 1 0 1 N creates this key with the default
value 0 (in version V1,V2,V3.xx)
The DS Agile Gateway’s kernel
creates this key with the default
value 1 (in version V4.xx)
2.2 GENECDD
[HKEY_CURRENT_USER\Software\Gateway\GENECDD]
Updated by genECDD.dll.
"STRUCT_MAIN" dword NA 0 255 N Version of configuration
structure.
Updated by genECDD.dll
"STRUCT_REVISION" dword NA 0 255 N Revision of configuration
structure.
2.3 REDUNDANCY
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\GATEWAY\PROTOCOL\REDUND]
This information is used
during checking on events
data. Particularly on
parameter date-time of
"redundantDll_datetime_Prot0" dword 1 0 1 Y each event data.
= 0: no check date-time
= 1: check date-time
(default value)
Boolean that indicates if
traces are activated or not.
"redundantDll_debug_Prot0" dword 0 0 1 Y = 0: no trace (default
value)
= 1: all traces
This information indicates
the current mode of
redundancy.
"redundantDll_mode_Prot0" dword 0 0 2 N = 0: Mode Backup
= 1: Mode Primary
= 2: Mode KO
GTW/EN MF/C57 MF-9

2.4 T101
[HKEY_CURRENT_USER\Software\DCS\Te\T101]
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy]
When the SCADA sends an
ASDU 103 (Clock
synchronisation), the protocol
negative responds when the
value is set to 1, and positive
when the value is set to 0.
"ack_pos_clock_ synchro" dword 0 0 1 Y
1 positive acknowledgement
(KEMA compliance)
0 negative acknowledgement
This indicates to SCADA that
ASDU103 is not managed.
SCADA address in balanced
mode. This value is an integer
"Adresse_SCADA" dword 1 1 65535 Y
taken into account only if
balanced_mode key is set to 1.
Boolean. If file transfer is
"ASDU126_BS" dword 0 0 1 Y enable it possible to set
ASDU126 in background scan.
Indicates the state of FCB bit in
"balance_mode_FCB" dword 1 0 1 Y the first frame with bit FCV = 1
in balanced mode.
This key indicates the class
used to send event
measurements.
When this value is set to 1, the
Analogue Outputs are sent on
a class 1 request. And when
"Class_Event_tm" dword 1 1 2 Y the value is set to 2, AO are
sent on a class 2 request.
1 Class1
2 Class2
This key is created with the
default value: 1 (Class 1
request).
Set COT (Cause Of
Transmission) value of
information feedback sent after
a command.
"Cot_remote_cmd" dword 11 3 11 Y This key is created with the
default value: 11 (return
information caused by a
remote command); can be set
to 3 (spontaneous)
MF-10 GTW/EN MF/C57


Boolean. According to T101
standard, counter value are
returned only if FREEZE is set
in the SCADA's counter
request. With this key counter
"COUNT_FREEZE_ value can be returned even if
dword 1 0 1 Y
COMPULSORY" the FREEZZE is not set.
0 -Counters interrogation
without FREEZE
1 - Counters interrogation with
FREEZE
Mode 0 is the normal mode,
the dead band is calculated
regarding to the last AI event
sent to the SCADA.
Mode 1 makes it possible to
"Dead_Bande_Mode" dword 0 0 1 Y calculate the dead band
regarding the last value of AI
sent (event or GI or periodical)
to the SCADA.
0 - Mode 0
1 - Mode 1
Defines a timeout ( in seconds)
of communication with SCADA.
After this delay if the SCADA
don't send any request. It's
considered as disconnected.
"delai_mesures_non_date The DS Agile Gateway stop
dword 0s 0s 1200 s Y
es" memorising AI without time-
stamp in its database.
In case of lost of
communication this permit to
avoid saturation of event stack.
Maximum delay (in
milliseconds) between two
characters in a fixed length
frame (Frame starting with
"Delay_After_1st_ 0x10, Class1 request for
dword 0 ms 0 ms 1000 ms Y
Byte_Fixed_Msg" example).
This can be increased in case
of trouble on communications
link (value 100).
Maximum delay (in
characters in a variable length
frame (Frame starting with
"Delay_After_1st_ 0x68, request of general
dword 0 ms 0 ms 1000 ms Y
Byte_Var_Msg" interrogation for example).
This can be increased in case
of trouble on communications
link (value 100).
GTW/EN MF/C57 MF-11


In case of communication lost
with SCADA. If the loose of
communication is too long, the
circular stack for recording
event could be saturated. In
this case, old events are lost.
"di_lost_events" dword 0 0 0xFFFFFF Y When communication is
available the DS Agile
Gateway indicates the lost of
old event by a special DI. This
key defines the T101 address
of the DI to send to SCADA. If
this key is 0 no DI will be sent
Indicates that during a GI we
want to upload events
0: Possibility to receive events
"EndGIBeforeEvent" dword 0 0 1 Y
during a GI.
1: Receiving events during a
GI is inhibited.
'Activation termination'
message during a DO
sequence. According to the
T101 standard, the Activation
"Flag_Act_Term_TC" dword 1 0 1 Y Termination is not mandatory.
01: 'Activation termination' is
sent,
not sent.
message during a setpoint
sequence. According to the
T101 standard, the Activation
"Flag_Act_Term_TVC" dword 1 0 1 Y Termination is not mandatory.
sent,
not sent.
This key indicates that when a
class is uploaded (Y=1 or
Y=2), the protocol uploads
firstly the Class X (1 or 2) if
available and this at the time of
"Flag_Priority_ClassX_Bef TimeSwitchDataClass in s.
dword 0 0 2 Y
ore_ClassY" = 0: inactive
= 1: for class 1 before
= 2: for class 2 before
ÖDefault value at creation
process: 0
MF-12 GTW/EN MF/C57


This key is a mask that
authorises the use of certain
information (Validity,
Actualisation,…) in the byte of
Quality concerning the
uploading of DI, AI, counter.
This byte is composed as
follows: |7|6|5|4|3|2|1|0|
"Flag_Quality" dword 255 0 255 Y
Bit N°7: INVALIDITY
Bit N°6: NOT TOPICAL
Bit N°5: SUBSTITUED
Bit N°4: BLOQUED
Bit N°3-2-1: Reserved
Bit N°0: OVERFLOW
This key indicates, when a
class is uploaded (1 or 2), that
"Flag_Remontee_ the DS Agile Gateway can
Autre_Class_Si_Pas_Data switches to the other class is
dword 0 0 1 Y the case that there are no data
_Dispo_Sur_
Class_En_Cours" available on the first class.
1 if switching is authorised
0 if not
This key indicates how the SQ
bit is used when a PA is
uploaded.
"Flag_SQ_PA" dword 0 0 2 Y 0: the SQ bit is forced to 0

1: the SQ bit is forced to 1
2: no forcing
See key Max_Gaps_DP.
bit is used when a AI is
uploaded.
"Flag_SQ_TM" dword 0 0 2 Y 0: the SQ bit is forced to 0

2: no forcing
bit is used when a DI is
uploaded.
"Flag_SQ_TS" dword 0 0 2 Y 0: the SQ bit is forced to 0

2: no forcing
Indicates Management of the
time tag in AI generated as
event.
"Flag_Tm_Gestion_Event" dword 0 0 2 Y 0 - AI with Time Tag
1 - AI with Time Tag if AISoe=1
2 - AI without Time Tag
GTW/EN MF/C57 MF-13


Indicates Management of the
time tag in DI generated as
event.
"Flag_Ts_Gestion_ Event" dword 0 0 2 Y 0 - DI with Time Tag
1 - DI with Time Tag if
DISoe=1
2 - DI without Time Tag
Boolean that indicates if
"GI_Compulsory" dword 0 0 1 Y protocol is expecting GI before
sending events.
This indicates if a HOPF 6039
"Hopf_Present" dword 0 0 1 Y
is present or not
This parameter can take
values 0 or 1. 0 indicates that
the DS Agile Gateway sends
the message of Clock
Synchronisation has each
"Inhibition_Clock_ change of hour. Value 1 makes
dword 1 0 1 Y it possible to inhibit the sending
Synchro"
of this message.
0 - Sending of the Clock
Synchronisation
1 - Inhibition of the clock
synchronisation
This parameter can take
values 0 or 1.
0: indicates that the DS Agile
Gateway does not reverse the
state of the DI of interlock. It is
"Invert_DI_Interlock" dword 0 0 1 Y the normal case.
1: the DI of interlock is
reversed.
This treatment allows or not
the authorisation of the
sending of command.
Size of the stack to memorise
events.
1= 1000 events.
"max_events" dword 10 1 60 Y
default value: 10 (up to 10 000
events)
Number of consecutive holes
in the configuration of
corresponding object if flag SQ
is set.
If this value is greater than
configuration, the T101 frames
"Max_Gaps_DP" dword 1 0 100 Y
are completed with invalid not
topical point.
If this value is less than the
information in configuration,
frame is splitting regarding the
holes
1 is for compliance with
"NUC" dword 0 0 1 Y Norwegian User Convention &
KEMA
MF-14 GTW/EN MF/C57


When the System pulse can be
reset by an operator, this key is
"Reset_compteur" dword 0 0 1 Y
made for a particularly
sequence of the counter value.
This key allows to know how
the protocol stopped last time.
Request of user or Watchdog.
POWER_ON 0
"Reset_Process" dword 0 0 1 N
MANUAL_RESET 1
REMOTE_RESET 2
The DLL IEC101 controls this
value.
When the DS Agile Gateway
receives an ASDU ‘Reset
Process’ 2 cases must be
considered depending on the
"Reset_Process_ Hard" dword 0 0 1 Y value of this key:
1: the operating system reboot
0: only the DS Agile Gateway
reboot
This key indicates if ASDU End
of Init will be sent or not.
0 Don't send of ASDU 70 at
"Send_init_asdu_70" dword 1 0 1 Y
initialisation
1 - Send ASDU 70 at
initialisation
Indicates if a positive
acknowledge is coded on a
short.
"ShortAck" dword 0 0 1 Y 1: positive ack is coded on a
short (0xE5)
0: positive ack is coded on a
standard format
Indicates if a negative
acknowledge is coded on a
short.
"ShortNack" dword 0 0 1 Y 1: negative ack is coded on a
short (0xA2)
0: negative ack is coded on a
standard format
This key indicates that when a
file is uploaded (File Transfer)
the file will be erased from the
"Sup_File_After_Ack_Tran hard drive or not.
dword 0 0 1 Y
sfer_OK"
0: if you want to always keep
the file
1: if not
Defines the maximum delay (in
frames transmissions. Beyond
this value a Test link frame is
“Test_Link_Cycle” dword 0 ms 0 ms 300 000 ms Y
sent in balanced mode by the
protocol. If value 0 is set the
protocol doesn’t transmit test
link frame
GTW/EN MF/C57 MF-15


Defines the maximum delay (in
seconds) of receiving two
frames from the SCADA. If this
"TimeOut_Communication" dword 60 s 10 s 1200 s Y delay is exceeded the DS Agile
Gateway will consider that the
communication with the
SCADA is shutdown.
Defines the maximum time (in
milliseconds) that library T101
will wait for receiving all the
datapoints from kernel.
"TimeOut_ Initialisation" dword 60 000 ms 0 ms 300 000 ms Y At the end of this time DS Agile
Gateway starts communicating
with SCADA.
If key is 0 library waits till all
datapoint are received.
This key indicates a time (in
seconds) linked to the timer
"TimeSwitchData Class" dword 30 s 1s 600 s Y attached to the key
Flag_Priority_ClassX_before_
ClassY.
If set to 1, send DI and AI with
"timetag_in_BS" dword 0 0 1 Y
time tag in background SCAN
If set to 1, send counter with
"timetag_in_CI" dword 0 0 1 Y time tag in counter
interrogation
If set to 1, send DI and AI with
"timetag_in_GI" dword 0 0 1 Y time tag in general
interrogation
This key indicates that the
periodic AI (by configuration) is
uploaded during a general
"TM_Periodique_GI" dword 1 0 1 Y interrogation (GI).
0: AI should not been uploaded
during a GI
1: AI should uploaded
Only for SPACE2000 system.
Allows to make a distinction
between SCADA to generate
"type_SCADA" dword 0 0 1 Y different control sequence to
system.
0: SCADA standard
1: SCADA ARS / IED master
Complementary state 00
validity for DI.
0 - Complementary state 00 is
"VALID_NON_COMP_00" dword 0 0 1 Y
invalid.
valid.
validity for DI.
invalid.
valid.
MF-16 GTW/EN MF/C57


This key indicates what version
of the norm IEC870-5-101 is
used.
0: if the ‘Revision 2’ is taking
into account
"Version_Norme_T101" dword 01 0 1 Y
1: if the ‘Edition 2’ is taking into
account
The difference between these
two options is at the COT level
used by the ASDU 30 to 36.
Boolean indicating the T101
acknowledgment mode in
balanced mode.
1: DS Agile Gateway always
acknowledge at link level ,
balanced_mode_Ack dword 0 0 1 Y
even if it waiting a scada
acknowledgment.
0: DS Agile Gateway not reply
to scada, if it waiting
acknowledgment
If set to 1 the Gateway clear
"ClearEventsOnResetLink" dword 0 0 1 Y events buffer on reset_link
request
This key indicates if
Suppression in a frame of
several analog with same
address is needed:
ConcatAnalogEvent dword 0 0 1 Y
- 0 : No effect,
- 1 : Suppression in a frame of
several analog with same
address
This key indicates the
behaviour of the SCADA time
stamping of a "Unknown"
Datapoint, when equipment is
disconnected:
- 0 : behaviour of the
key_T0_T1_T0 dword 0 0 1 Y
specification : time stamped at
T0 (Date of the last state
change),
- 1 : New behaviour : time
stamped at T1 (Date of the
disconnection)
GTW/EN MF/C57 MF-17


This key indicates the
behaviour of the transmission
of counter datapoints:
- 0 : the value of counter is
sent to the SCADA each
sample,
- #0 : the value of the counter
is cumulated each sample and
this calculated value is also
nb_counter_sample dword 0 Y sent to SCADA each sample.
This calculated value is set to 0
each "nb_counter_sample".
When this mode is used, don't
send a ‘counter interrogation’
from SCADA because this
operation sends a
‘reset+freeze’ request. So, the
value is erased and will be
indicated as ‘invalid’
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy\FileTransfert]
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy\FileTransfert\EventRecord]
Corresponds to the base IOA
(Information Object Address)
address of SOE (Sequence Of
Event) File (given in format of
IOA configured in the T101:
"AdresseIOAFile" dword 10000 1 0XFFFFFF See comment one, two or three bytes).
This key is not used by system
where the IOA address is set in
configuration. In such system
the key indicates the IOA value
and is not modifiable.
Defines the Time Tag format
for the SOE (Sequence Of
Event) file. In recent version
this value is just updated with
configuration file value. This
"Cp56TimeTag" dword 1 0 1 See comment key is not used by system
where it is set in configuration.
0: events are recorded in file
with Cp24Time2a,
1: events are recorded in file
with Cp56Time2a.
Defines if a file is deleted or
not by the DS Agile Gateway
after reception of a positive file
"Delete_File_after_read dword 0 0 1 Y transfer acknowledgement
from the SCADA
0: file not deleted
1: file deleted
MF-18 GTW/EN MF/C57


Corresponds to the drive
where the files are recorded.
This value is used for the file
"Drive" string "C" NA NA Y transfer under IEC101.
In case of XP embedded
operating system if C: is write
protect, use D:
Extension to the files recorded
on the hard drive of the PC.
"FileExtension" string "101" NA NA Y
transfer under IEC101.
Suppressed in recent version
"NbMaxEvent" dword 10000 See comment of T101: Gives the max event
number recorded in the file.
Corresponds to the directory
where the files are recorded.
"Path" string "\\T101\\" NA NA Y
transfer under IEC101.
Gives the percentage of event
number compared with
"PercentOfEventForFileSe NbMaxEvent. When the file
dword 25 10 100 Y
nd" reaches this event number an
ASDU File Ready is sent to
SCADA
Gives the IOA size of event
recorded in SOE file. In recent
"SizeIOAofEvent" dword 3 1 3 Y
version, this value is update
with configuration file.
Type of file transfer
0 No file.
1 or 4 Standard SOE
8 Microsol
"TypeFile" dword 0 0 8 See comment
This key is not used by system
where the type of file is set in
configuration.
In such system the key just
indicates the type of file
[HKEY_CURRENT_USER\Software\alstom\Te\T101\Protx_COMy\Port]
if value is –1, the port baud
rate is this configured by SCE
else it is the baud rate of the
"BaudRate" dword ffffffff N port.
default value: -1
Gives a GPT trace level. Not
"Debug" string "N" Y N N
used for DS Agile
GTW/EN MF/C57 MF-19


Communication port parity.
The parity for the IEC101
protocol must be even. Not in
configuration. Can be used to
"Parity" string "E" N
accommodate a modem which
does not support an even
parity. E: Even, N None, O:
Odd.
2.5 T104
[HKEY_CURRENT_USER\Software\DCS\Te\T104]
[HKEY_CURRENT_USER\Software\DCS\Te\T104\Prot1]
[HKEY_CURRENT_USER\Software\DCS\Te\T104\Prot1\Configuration]
8 (bit 3 set): each digital input,
each analog input, each step
position and counter state
"Debug_Flags" dword 0 0 8 Y change will be recorded in
SOE files, regardless of their
current SCE configuration (to
use for test only)
In case of communication lost
with SCADA. If the loose of
communication is too long, the
circular stack for recording
event could be saturated. In
this case, old events are lost.
"di_lost_events" dword 0 0 0xFFFFFF Y When communication is
available the DS Agile
Gateway indicates the lost of
old event by a special DI. This
key defines the T101 address
of the DI to send to SCADA. If
this key is 0 no DI will be sent
message during a DO
sequence. Accor-ding to the
standard, the Activation
"Flag_Act_Term_TC" dword 1 0 1 Y Termination is not mandatory.
sent.
not sent.
message during a setpoint
sequence. Ac-cording to
standard, the Activation
"Flag_Act_Term_TVC" dword 1 0 1 Y Termination is not mandatory.
sent.
not sent.
MF-20 GTW/EN MF/C57


0: event generation is made
according to each counter own
configuration of “evt” “value in
SCE. (for memory value of
“evt” can be “no event”, “event
with time tag”, “event without
time tag”).
1: no event generated if “evt” is
"Flag_Pa_Gestion_Event" dword 0 0 2 Y “ no event ”, otherwise counter
events are always time tagged
(even if “evt” is “event without
time tag”).
“ no event ”, otherwise counter
events are never time tagged
(even if “evt” is “event with time
tag”).
This key is a mask that
authorise the use of certain
information (Validity,
Actualisation,…) in the byte of
Quality concerning the
uploading of DI, AI, counter.
This byte is composed as
follows:
"Flag_Quality" dword 255 0 255 Y |7|6|5|4|3|2|1|0|
Bit N°7: INVALIDITY
Bit N°6: NOT TOPICAL
Bit N°5: SUBSTITUED
Bit N°4: BLOCKED
Bit N°3-2-1: Reserved
Bit N°0: OVERFLOW
bit is used when a PA is
uploaded
"Flag_SQ_PA" dword 0 0 2 Y 0: the SQ bit is forced to 0

2: no forcing
bit is used when an AI is
uploaded
"Flag_SQ_TM" dword 0 0 2 Y
2: no forcing (KEMA
compliance)
GTW/EN MF/C57 MF-21


bit is used when a DI is
uploaded.
"Flag_SQ_TS" dword 0 0 2 Y
2: no forcing (KEMA
compliance)
acc. to each analogue input
own configuration of “evt”
“value in SCE. (for memory
value of “evt” can be “no
event”, “event with time tag”,
“event without time tag”).
“ no event ”, otherwise
"Flag_Tm_Gestion_Event" dword 0 0 2 Y
analogue input events are
always time tagged (even if
“evt” is “event without time
tag”).
“ no event ”, otherwise
analogue input events are
never time tagged (even if “evt”
is “event with time tag”).
according to each digital input
own configuration of “evt”
“value in SCE ( for memory
value of “evt” can be “no
event”, “event with time tag”,
“event without time tag”).
"Flag_Ts_Gestion_Event" dword 0 0 2 Y “ no event ”, otherwise digital
input events are always time
tagged (even if “evt” is “event
without time tag”).
“ no event ”, otherwise digital
input events are never time
tagged (even if “evt” is “event
with time tag”).
"Flag_Nack_Answer_Time
dword 0 0 1 Y 1 for KEMA compliance
Tag_Cmd"
"GI_Compulsory" dword 0 0 1 Y 0: the SQ bit is forced to 0
"NUC" dword 0 0 1 Y 1: the SQ bit is forced to 1
MF-22 GTW/EN MF/C57


0: for counters Management in
mode A or B (in these modes
the SCADA only reads
counters values). In this case
values received by DS Agile
Gateway are considered as
frozen values, and will be
transmitted as received
following a counter
"PA_freeze_in_dll" dword 1 0 1 Y interrogation (no need of
freeze command).
1: for counters Management in
mode C. In this case values
received by DS Agile Gateway
are considered as current
values, and a freeze command
is necessary from the SCADA.
The freeze command is done
inside the dll.
0: not compatible with T101
norm amendment 2, means a
counter freeze (or freeze reset
or reset) command will trigger
directly a counter interrogation.
1: compatible with T101 norm
amendment 2, means a
"PA_T101_amendment_2_ counter freeze (or freeze reset
dword 0 0 1 Y or reset) command will not
compatibility"
trigger directly a counter
interrogation. A new counter
interrogation command has to
be performed in order to read
frozen values calculated
following a previous freeze (or
freeze reset or reset)
command. (KEMA compliance)
When the DS Agile Gateway
receives an ASDU ‘Reset
Process’ two cases must be
considered depending on the
"Reset_Process_Hard" dword 0 0 1 Y value of this key:
1: the operating system reboot
0: only the DS Agile Gateway
reboot
milliseconds) that library T104
datapoints from kernel. At the
"TimeOut_Initialisation" dword 60 000 ms 0 ms 300 000 ms Y end of this time DS Agile
Gateway start communicating
with SCADA. If key is 0 library
waits till all datapoint are
received.
GTW/EN MF/C57 MF-23


validity for DI.
invalid.
valid.
default value: 0
sent,
not sent.
valid.
default value: 0
[HKEY_CURRENT_USER\Software\DCS\Te\T104\port]
Reserved for R&D department to test
"Debug" string "N" "Y" "N" N
T104
T104 with database of the site: First
"IP1" dword 0xFFFFFFFF 0 255 N
byte of T104 IP address if debug is
set to Y
T104 with database of the site:
Second byte of T104 IP address if
debug is set to Y
T104 with database of the site: Third
set to Y
T104 with database of the site: fourth
set to Y
2.6 COMMON T101 / T104

[HKEY_CURRENT_USER\Software\DCS\Te\synchro]
Indicates if the DS Agile
Gateway is synchronised with
the system or not
= 0: DS Agile Gateway is not
"synchro" dword 0 0 1 N synchronised
= 1: DS Agile Gateway is
synchronised
Default value at creation
process: 0
MF-24 GTW/EN MF/C57

[HKEY_CURRENT_USER\Software\DCS\Te\TakingControl]
Nominal serial port physical
"num_Port_Control_ number
dword ff 255 255 N
Principal"
not used in DS Agile
Redundant serial port physical
"num_Port_Control_ number
dword ff 255 255 N
Redondant"
not used in DS Agile
Used to know if the check of
the interlock operation is done
in the kernel of the DS Agile
Gateway or at the level of the
DLL IEC101.
"UseDllsInterlockProt" dword 1 0 1 N = 0: Check is done in the
protocol library
= 1: Check is done in the
kernel
Ö Default value at installation:
1 in DS Agile
2.7 MODBUS
As of version 3.1 of ModBus library, the path is changed.
[HKEY_CURRENT_USER\Software\Gateway\Protocol\Modbus\Protx_COMy]
Boolean that indicates if multiple coils
"support_multiple_coils" dword 1 0 1 Y
are managed or not.
milliseconds) that library Modbus
waits for receiving all the datapoints
from kernel. At the end of this time
"TimeOut_Initialisation" dword 60 000 ms 0 ms 300 000 ms Y
DS Agile Gateway start
communicating with SCADA. If key is
0 library waits till all datapoint are
received.
2.8 IEC 61850-8-1

[HKEY_CURRENT_USER\Software\Gateway\Protocol\IEC61850\Protx]
validity for DI.
invalid. Flag quality 0x4000).
valid. Flag quality 0x0000).
validity for DI.
invalid. Flag quality 0x4000).
valid. Flag quality 0x0000).
GTW/EN MF/C57 MF-25

2.9 DNP3
[HKEY_CURRENT_USER\Software\DCS\Te\Dnp3]
"Carrier" dword 0
"DataLen" dword 8
Defines variation of AI static:
0 - Analogue Input All
Variations
1 - 32 Bits Analogue Input
"DefaultVariationAnalog" dword 2 0 4 Y 2 - 16 Bits Analogue Input
without Flag
without Flag
Define variation of AI as event:
0 - Analogue Input All
Variations
1 - 32 Bits Analogue Change
Event without Time
"DefaultVariationAnalog
dword 2 0 4 Y 2 - 16 Bits Analogue Change
Chgt"
Event without Time
Event with Time
Event with Time
Define variation of static DI.
0 - Binary Input All Variations
"DefaultVariationDigital" dword 2 0 2 Y
1 - Binary Input
2 - Binary Input with Status
Define variation of Di SOE.
0 - Binary Input Change All
Variations
1 - Binary Input Change
"DefaultVariationDigital
dword 2 0 3 Y without Time
Chgt"
2 - Binary Input Change with
Time
3 - Binary Input Change with
Relative Time
"Filter_AI_self_check_fault
dword 0
"
"Filter_AI_unknown" dword 0
"Filter_DI_self_check_
dword 0
fault"
"Filter_DI_unknown" dword 0
This indicates if a HOPF 6039
"Hofp_Present" dword 0 0 1 Y
is present or not
"Idle" dword 0
MF-26 GTW/EN MF/C57


"Parity" dword 0
"PostTransmissionDelay" dword 0
"PreTransmissionDelay" dword 0
"SCADA1_ADR_MAX" dword 0
Boolean that indicates if Binary
"Send_BO_Class0" dword 0 0 1 Y Output must be sent on class 0
request
"Squelch" dword 1
"StopBits" dword 1
Maximum time (in seconds)
between the receptions of two
frames from the SCADA. If a
"TimeOut_Communication" dword 3600 s 0s 65536 s Y time out occurred, the DS Agile
Gateway considers the
communication with the
SCADA is lost.
milliseconds) that library DNP3
data points from kernel.
"TimeOut_Initialisation" dword 0 ms 0 ms 65536 ms Y At the end of this time DS Agile
Gateway start communicating
with SCADA.
If key is 0 library wait till all
data point are received.
Maximum time (in milliseconds)
before an acknowledgement
"TimeOut_Organes" dword 1310 0 65536 ms Y from the generic part during an
order (Selection / Execution /
Cancel).
This key indicates the counter
format.
"TYPE_COUNTER" dword 0 0 1 Y
0 - 16 bits
1 - 32 bits (CHEM SCADA)
This key indicates the kind of
SCADA.
"TYPE_SCADA" dword 0 0 1 Y 0 - Standard SCADA
1 - CHEM SCADA
If set to 1 (static DI on class1)
2.10 OPC
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\protocol\OPC\svritfc]
Gives the name of the DS Agile Gateway
"Exe_Name" String "tg_rcc.exe" NA NA N
executable for the OPC Server
"Historic Timer" Dword 250
"PERTE
"PIF_name" string NA NA Y
INFO"
The specified ServerRate defines how fast
"Server Rate" dword 250 the OPC Client data connections are
refreshed (for synchronous reads).
GTW/EN MF/C57 MF-27

2.11 ADDITIONAL BOARD HOPF FOR TIME SYNCHRONIZATION

T101 protocol:
DNP3 protocol:
MF-28 GTW/EN MF/C57

3 FILES INSTALLED BY SETUP PROCEDURE

If you install the DS Agile Gateway under a directory named Program Files\ALSTOM\DCS\Gateway, you
will find the following directory-tree after the setup:
3.1 DIRECTORY ECDD1 AND 2

These directories are created for the DS Agile Gateway to store the configuration files for the current and the
standby databases. At every time you can check the registry to see which one is used for the current and
which one is for the standby database (see the section DS Agile Gateway registry).
3.2 OTHER EXECUTABLES AND DLLS

TG_RCC.exe is the executable of the DS Agile Gateway to launch the DS Agile Gateway just double click
on this executable. This executable use prot.exe, and uca2_omm.exe which constitute with the
so_uca2.dll and dll_ecdd.dll the DS Agile Gateway itself.
Protocol DLLs are listed in the figure here above.
GTW/EN MF/C57 MF-29

3.3 DATA MODEL FILE

At the installation level the procedure creates a data model for the DS Agile Gateway. If the network name of
the PC where you install the DS Agile Gateway is for example: PCNETNAM the installation procedure will
create the file PCNETNAM.dm that is the data model of the DS Agile Gateway.
Take a good care that this name must not be longer then 8 characters otherwise when you will launch the
DS Agile Gateway executable it will reboot the PC. If it is not the case, just cut this name to 8 characters.
3.4 DEBUGGING TOOLS

If you have problems with the communication between the DS Agile Gateway and the SCADA, you can be
interested in launching the view_trace.exe executable to see the messages exchange between these
two pieces of equipment.
You can also use the Dbgview.exe.
Caution:
DebugView uses the same mechanism as ViewTrace. You should not launch those two
softwares at the same time or you will have half of your traces on ViewTraces and half on
DbgView and it will be very hard to debug.
MF-30 GTW/EN MF/C57

4 OPERATION TRACES
4.1 TRANSLATION OF DS AGILE GATEWAY’S ID TOOL

Put the executable GtwIDToUCA2.exe into the directory ECDD1 or ECDD2 and double-click on it to make
the file infos_uca2.txt with the needed information. For more details open the file readme.txt delivered with
this tool.
As this tool runs under the same PC where the DS Agile Gateway is installed, make sure the PC has enough
resources to run the tool.
4.2 FIND THE TRANSLATION MANUALLY

The following figure can help retrieve the IEC 61850-8-1 name of DI, AI or a DO. Below is an example for an
AI but the same applies to DI or DO.
In the main window a log line concerns the AI that has changed the “unique gateway identifier” will help you
to retrieve the IEC 61850-8-1 name.
In the file Gateway.txt retrieve the “Server number” (1 in the example) and the name of the server
(C264_SIM).
Then open the file C264_SIM.dm which is the data model of the C264_SIM server. The IEC 61850-8-1
identifier helps you retrieve the IEC 61850v name of the concerned data:
C264_SIMCONTROL/GGIO1$ST$Cnt1$frTm.
GTW/EN MF/C57 MF-31

4.3 RUN-TIME TRACES

Two files are available for run-time traces:
• Log<x>.txt (x = 0 to 9) stores all traces displayed in the Gateway window

• Watchdog.txt gives information in case of Gateway reboot due to a watchdog failure
These files are available in the DS Agile Gateway installation folder.
MF-32 GTW/EN MF/C57

5 DIFFERENT COMPONENTS TO DEBUG

DS Agile Gateway software proposes different files to help debugging.
Files can be Traces, Logbook, T101 file transfer files, watchdog.log or configuration files
5.1 TRACES
DS Agile Gateway, at kernel, acquisition and protocol level, uses a Microsoft Windows primitive to display
traces.
This primitive is OutputDebugString.
When OutputDebugString() is called by an application, it maps data segment into memory , copy up to about
4kbytes of data to the memory buffer, store the current process and set event signal.
On the debugger front wait for event to be signalled and extract the process ID, NUL-terminated string from
memory buffer.
To display those traces two tools are delivered with DS Agile Gateway (folder Tools):
• DbgView.exe (freeware from Sysinternals)

• Viewtraces.exe (software implemented by Alstom)
DebugView.exe is an application that lets you monitor debug output on your local system, or any computer
on the network that you can reach via TCP/IP. It is capable of displaying both kernel-mode (output generated
by device drivers and/or the Windows kernel) and Win32 debug mode (output generated by standard debug
print APIs).
ViewTrace.exe is an application that lets you monitor debug output on only your local system. It is capable to
translate protocol frame format data into user readable format.
5.2 LOGBOOK
When a screen and a keyboard are connected to DS Agile Gateway-PC, an HMI is displayed with a logbook.
The Logbook helps know product, components, configuration, protocols versions, status of equipments and
transmitted Analog/Digital information, State of communication and Execute command status etc…
5.3 TRANSLATEFILE
So protocol can memorize Sequence Of Event (SOE) in a file to transfer it if SCADA required.
Those files are formatted to be transmitted to SCADA so they are note readable. To edit those files a tool is
delivered with DS Agile Gateway TranslateFile.exe
TranslateFile helps translate T101 SOE file format into readable format.
5.4 WATCHDOG
When a watchdog is detected the DS Agile Gateway saves it in a readable file. This file is named
WatchDog.log and memorized in same directory than the application.
5.5 CONFIGURATION FILES

System Configuration Editor (SCE) generates files of configuration in binary format, and data model of each
server that DS Agile Gateway will connect to.
As the configuration is not readable in binary format, a text file is generated.
To help set the relationship between data model and protocol configuration, use GTWIdToUca2.
GTW/EN MF/C57 MF-33

6 DBGVIEW
6.1 INSTALLATION DBGVIEW

The Debugview software is automatically installed with the application DS Agile Gateway.
It is recommended to create a shortcut on the desk of the PC DS Agile Gateway if setup does not create
shortcut. To create a shortcut, use the following procedure.
• Open Windows Explore, Browse the directory C:\ProgramFiles\DCS\Gateway\Tools

• Select the Dbgview.exe application, Right click the application
• Use Send To Desktop (create shortcut) option
6.2 CAPTURING DEBUG OUTPUT

DebugView registers to receive and print debug output generated by Win32 programs that call
OutputDebugString. The toolbar button, the Capture|Capture Win32 menu item, and the Ctrl+W hot-key
sequence can toggle this capture on and off.
MF-34 GTW/EN MF/C57

6.3 PARAMETER SETTING

Menus, hot-keys, or toolbar buttons can be used to set parameters, clear the window, save the monitored
data to a file, search output, change the window font, and etc.
6.3.1 DEPTH OF HISTORY

DebugView output is to limit the number of lines that are retained in the display. You use the Edit|History
Depth menu item, Toolbar button, or the Ctrl+H hot-key sequence to activate the history-depth editor. Enter
the number of output lines you want DebugView to retain and it will keep only that number of the most recent
debug output lines, discarding older ones. A history-depth of 0 represents no limit on output lines retained.
Caution:
It is important to configure a number of events, otherwise the number of recording would
be limited only by the sharp memory size of the PC
=> saturation of virtual memory.
GTW/EN MF/C57 MF-35

6.3.2 TIME FORMAT

DebugView displays time stamps of captured debug output in one of two formats: as clock-time (the time of
day), or as relative time.
When displaying relative time DebugView represents the time of a debug output record as the difference
between its timestamp and the timestamp of the first record in the display. This mode is helpful when you
debug timing-related problems, but it's preferable to use clock-time. Use the Options|Clock Time menu
item, Toolbar button, or Ctrl+T hot-key sequence to toggle between clock time and relative time modes.
When DebugView is in clock-time mode you can select the Options|Show Milliseconds menu item to have
DebugView show timestamps that include millisecond resolution.
6.3.3 FILTERS
To isolate output that you are interested in is to use DebugView’s filtering capability. Use the
Edit|Filter/Highlight menu item, toolbar button, or Ctrl-L hot-key to activate the filter dialog. The dialog
contains two edit fields: <<include>> and <<exclude>>.
The <<include>> field is where you enter substring expressions that match debug output lines that you want
DebugView to display, and the <<exclude>> field is where you enter text for debug output lines that you do
not want DebugView to display. You can enter multiple expressions, separating each with a semicolon (‘;’).
Do not include spaces in the filter expression unless you want the spaces to be part of the filter.
Notes: The filters are interpreted in a case-insensitive manner. The wildcard ‘*’ is allowed.
MF-36 GTW/EN MF/C57

Possibilities of various filters:
• IEC 61850-8-1 to filter traces the acquisition part of DS Agile Gateway

• bytes to filter that traces in hexadecimal of frames sent on the communication link
• MODBUS to filter that traces Modbus protocol
• IEC101 to filter that traces T101 protocol
• T101-SAS to filter that traces T101-SAS protocol
• TG_RCC to filter that traces kernel DS Agile Gateway
• Etc, …
To remove a filter, click “reset” then “OK”.
6.4 STOP TRACES

Use the Capture|Capture Events menu item, Toolbar button, or the Ctrl+E hot-key sequence to stop the
traces for user to analyse the recording data.
GTW/EN MF/C57 MF-37

6.5 SAVING AND LOGGING OF TRACES
6.5.1 PARAMETER SETTING: «LOGGING TO A FILE»

To have DebugView log output to a file as it displays it, use the File|Log to File or File |Log to File As
menu items, the toolbar button, or the Ctrl+O hot-key sequence.
Log file settings you specify include:
• the name of the log file

• the maximum size it should be allowed to grow
• whether or not DebugView restarts the log or appends to it if the file specified already contains output
If you select the wrap option, DebugView wraps around to the beginning of the file when the file's maximum
specified size is reached.
If you select the Create New Log Every Day option, DebugView does not limit the size of the log file, but
creates a new log file every day that has the current date appended to the base log file name you enter.
Caution: This can fill your hard disk.
To stop logging simply select the toolbar button or the File |Log to File menu item.
Caution:
If the size is not specified, the size of the file IS limited only by the disk size of the PC
CAUSING A risk of saturation of storage disk.
MF-38 GTW/EN MF/C57

6.5.2 SAVING OUTPUT

To save the contents of the DebugView output window as a text file (.log extension), select the File|Save or
File|Save As menu items, or the Ctrl+S hot-key sequence.
To copy the debug output contained within selected output lines to the clipboard, select Edit|Copy or the
Ctrl+C hot-key sequence.
GTW/EN MF/C57 MF-39

7 VIEWTRACE
7.1 INSTALLATION VIEW TRACE

The Viewtrace software is automatically installed with the DS Agile Gateway application.
It is recommended to create a shortcut on the desk of the PC DS Agile Gateway if setup has not created
one. To create a shortcut:
• Open Windows Explore, Browse the directory C:\ProgramFiles\DCS\Gateway.

• Select the view_trace.exe application, Right click the application.
• Use Send To Desktop (create shortcut) option.
7.2 CAPTURING DEBUG OUTPUT

Viewtrace will register to receive and print debug output generated by Win32 programs that call
OutputDebugString. With recent versions of Viewtrace, it is not necessary to click on Start_Traces to toggle
this capture on.
Clicking on Start_Traces / Stop_Traces can toggle this capture on and off.
Caution:
DebugView uses the same mechanism as Viewtrace. Do not launch both at the same time
otherwise half of the traces are on viewTraces and the other half on Dbgview, making it
very hard to debug.
MF-40 GTW/EN MF/C57

7.3 PARAMETER SETTING AND USE

Menus, Buttons can be used to set parameters, clear the window, save the monitored data to a file, use the
Filter, find the string (only if traces acquisition is stopped), and etc.
GTW/EN MF/C57 MF-41

7.4 DEPTH OF HISTORY

View Trace output allows to limit the number of lines that are retained in the display.
Use the NB events list box to select the history-depth.
Select the number of output lines you want View trace to retain and it will keep only that number of the most
recent debug output lines, discarding older ones.
Caution:
It is important to configure a number of events, otherwise the number of recording will be
limited only by the sharp memory size of the PC => risk of saturation of virtual memory.
The default value of 20 000 is sufficient.
MF-42 GTW/EN MF/C57

7.5 SELECT PROTOCOL

View Trace allows you to interpret protocol frames. You must at first select Protocols and set required
properties. Use the File|Protocol|IEC101 or IEC104 or DNP3 menu item to activate properties dialog box.
GTW/EN MF/C57 MF-43

7.6 FILTERS
To isolate output that you are interested in, use the View Trace filtering capability. Click the Use Filter check
box to activate the filter.
In View Trace the filter is case sensitive.
Possibilities of various filters:
• IEC 61850-8-1 to filter traces the acquisition part of DS Agile Gateway

• bytes to filter that traces in hexadecimal of frames sent on the communication link
• MODBUS to filter that traces Modbus protocol
• T101-SAS to filter that traces T101-SAS protocol
• Etc, …
To remove a filter, uncheck “use filter”.
MF-44 GTW/EN MF/C57

7.7 START/STOP TRACES

Use the Start Traces / Stop Traces button to start/stop the traces for user to analyse the recording data.
GTW/EN MF/C57 MF-45

7.8 SAVING OF TRACES

To have View Trace log output to a file as it displays it, use the Save x button. Log file will record as
traceX.txt where X is 0 to 65535.
MF-46 GTW/EN MF/C57

7.9 COMMENT FILE

You can save the contents of the View Trace output window (only RX and TX) as a Comment File (.txt
extension) using the File|Generate Comment File menu item.
GTW/EN MF/C57 MF-47

7.10 IMPORT FILE

You can import an existing file to ViewTrace output window using the File|Import Fichier menu item.
The content of this file will be appended to the existing content of the output windows (you can click on
Delete Traces before importation if you do not want to).
MF-48 GTW/EN MF/C57

7.11 FRAME ANALYSIS

You can analyze the protocol frame in details by clicking on frame.
You gain access to details of frame in the lower windows.
7.12 BACKUP MODE

To memorise traces for a long period you can:
• launch ViewTrace
• click on "stop traces" to be able to increase "Nb Events", set it to 60000 for example.
• set filter to a value, not compulsory, "use filter" must be checked
• "backup mode" must be checked
• click on "start traces"
Viewtrace memorizes traces and creates numerous zipped files with 60000 lines in each file.
This way you can observe what has happened during several days.
GTW/EN MF/C57 MF-49

8 INTERPRETATION OF TRACES
8.1 PROTOCOL TRACE FORMAT

All the protocols share a very similar format of traces.
8.1.1 MESSAGE DUMP

[HH:MM:SS:MS ] NNNNN[Z] [RX/TX nnn bytes: XX XX XX XX ………..]
HH:MM:SS:MS : Time stamp of the traces
(format is different on viewtrace and dbgview)
NNNNN : Name of Protocol
Z : Protocol instance number
RX : Received Bytes from SCADA
TX : Transmitted Bytes from DS Agile Gateway
nnn : Number of Bytes
XX XX XX XX : Data Frame
Example:
[15:41:06:949] IEC101[0] [TX 72 bytes: 68 42 42 68 08 02 03 14 02 01 f4 01 01
f6 01 01 f8 01 01 fa 01 01 fc 01 01 fe 01 01 00 02 01 02 02 01 05 02 01 08 02 01
0c 02 01 10 02 01 15 02 01 19 02 01 1d 02 01 22 02 01 27 02 01 2c 02 01 30 02 01
31 02 01 7c 16]
Time : 15:41:06:949
Name of Protocol : IEC101
Protocol instance number: 0
Received Bytes : RX
Number of Bytes : 72
Data Frame : 68 42 42 68 08 02 03 14 02 01 f4 01 01 f6 01 01 f8 01
01 fa 01 01 fc 01 01 fe 01 01 00 02 01 02 02 01 05 02 01 08 02 01 0c 02 01 10 02
01 15 02 01 19 02 01 1d 02 01 22 02 01 27 02 01 2c 02 01 30 02 01 31 02 01 7c 16
8.1.2 TELE-STATUS TRACE FORMAT

[HH:MM:SS:MS ] NNNNN[Z] [MajTs var.no_conf = NNN var.maj.etat = VVV status = SSS
initialization = YES/NO DD/MM/YYYY HH:MM:SS:MS]
HH:MM:SS:MS : Time stamp
MajTs : Tele-status
NNN : Point identification
VVV : Value
SSS : Status
DD/MM/YYYY : Date
Example:
[10:44:54:550] IEC101[0] MajTs: var.no_conf=1024 var.maj.etat=0 status=65535
initialisation=NO 17/07/2036 09:44:54.550
Time: : 10:44:54:550
Point identification : 1024
Value : 0
Status : 65535
Date and Time : 17/07/2036 09:44:54.550
MF-50 GTW/EN MF/C57

8.1.3 TELE-MEASUREMENT TRACE FORMAT

[HH:MM:SS:MS ] NNNNN[Z] [MajTm no_conf = nnn etat = SSS value = VVV init =
YES/NO]
MajTm : Tele-measurement
nnn : Point identification
VVV : Value
SSS : Status
Example:
[10:44:54:457] IEC101[0] MajTm: no_conf=1102, etat=0, value=0.000000 Init=YES
]
Time : 10:44:54:457
Point identification : 1102
Value : 0.000000
Status : 0
Initailization : YES
8.2 REDUNDANT TRACE FORMAT

[HH:MM:SS:MS ] REDUNDANT[PROT = T: INST = Z] [S/R][SUCCESS/FAILED]: <DDDDD> HHHH…….
T : Type of Protocol
S/R : Send/Receive
< DDDDD > : Message description
HHHH : Message Identification
Example:
[11:29:34:053] REDUNDANT[PROT=1:INST=0] [R][SUCCESS]: <Health Gateway>
H0003|1|0|10.22.90.141|0|0|1015524246|
Time : 11:29:34:053
Type of Protocol : 1 (IEC101)
Message description : <Health Gateway>
Message Identification : H0003(Health Message)
Note: Refer redundant specifications document for detailed information of each message type
8.3 DS AGILE GATEWAY KERNEL TRACE FORMAT

[HH:MM:SS:MS ] [NNNNN] xxxxx
HH:MM:SS:MS : Time stamp of traces
NNNNN : Name of DS Agile Gateway part (TG_RCC, UCA2_OMM …)
Xxxxx : Message of the trace
Example:
[11:29:32:853] [SO_UCA2][callback]ODCOnReportReceived
Time stamp of traces : 11:29:32:853
Name of Alstom DS Agile Gateway part SO_UCA2 = library that manage agency
Message of the trace : [callback]ODCOnReportReceived
GTW/EN MF/C57 MF-51

MF-52 GTW/EN MF/C57

9 DS AGILE GATEWAY HMI

At DS Agile Gateway start, a Logbook is Creates/Opened (C:\ProgramFiles\DCS\Gateway). DS Agile
Gateway records Product Version, Components versions, Configuration Components versions, Protocols
versions, status of tasks, State of communication, Execute command status etc...
Timestamp on the left part indicates the time when the traces in generated.
Logbook
9.1 COMPONENTS VERSIONS

While starting DS Agile Gateway records components information in Logbook.
You can display this information using the Components Versions button.
If you write a fault or assistance report indicates, at least, the product version.
GTW/EN MF/C57 MF-53

9.2 SERVER EQUIPMENT STATUS TRACE FORMAT

If a server is connected or disconnected it is logged in the logbook part.
HH:MM:SS:MS Server XXXXXX, Equipment Y is connected/ disconnected
HH:MM:SS:MS : Time stamp indicating when the
DS Agile Gateway was advertised of the
connection change
XXXXXX : Name of Server
Y : Equipment # 1 for a C26x 2 and more for
an IED connected to C26x.
Example:
16:20:46:383 Server C264_R_M, Equipment 2 is disconnected
Time: : 16:20:46:383
Name of Server : C264_R_M
Equipment number : 2
9.3 DIGITAL TRACE FORMAT

Digital trace format is displayed only if "Digital Log" is checked.
If a DI status change it is logged in the logbook part.
HH:MM:SS:MS Sending SINGLE / DOUBLE DI ident:X V ACQ PHYS ZZZ DD/MM/YYYY
HH:MM:SS:MS
HH:MM:SS:MS : Time stamp indicating when the DS Agile Gateway
received the DI.
X : Point Number
V : Value
ZZZ :
DD/MM/YYYY : Date
Example:
16:33:58:539 Sending SINGLE DI ident:1173 OFF ACQ PHYS 002.001.011 07/06/2006 14:33:48:195
Time: : 16:33:58:539
Point Number : 1173 Internal number of DS Agile Gateway
MF-54 GTW/EN MF/C57

Value : OFF
Date and Time : 07/06/2006 14:33:48:195
9.4 ANALOG TRACE FORMAT

HH:MM:SS:MS Sending AI ident:X V INI PHYS ZZZ DD/MM/YYYY HH:MM:SS:MS
HH:MM:SS:MS : Time stamp indicating when the DS Agile Gateway received the AI.
X : Point Number
V : Value
ZZZ :
DD/MM/YYYY : Date
Example:
10:34:28:383 Sending AI ident:1307 UNKNOWN Value:0.000000 INI PHYS 010.001.000
07/07/2006 08:34:28:383
Time: : 10:34:28:383
Point Number : 1307
Value : 0.000000
Date and Time : 07/07/2006 08:34:28:383
9.5 COMMAND TRACE FORMAT

HH:MM:SS:MS PROT# Y:DDDD: configuration ident:XXX, Execute command, SSSS
DDDD : Description
Y : Instance of protocol
XXX : Point Number
SSSS : State
Example:
1:04:03:710 PROT# 0:Command structure information read: configuration ident:1000, Execute command,
Close
Time: : 1:04:03:710
Description : Command structure information read
Instance of protocol : 0
Point Number : 1000
State : Close
9.6 COMMUNICATION TRACE FORMAT

HH:MM:SS:MS DDDDDD PROT#0. [State COM = LOST COM]
11:04:03:710 This is a State Communication TC 1000 from PROT#Y. [State COM = SSSS]
DDDDDD : Description
Y : Instance of protocol
SSSS : State
Example:
11:04:03:710 This is a State Communication TC 1000 from PROT#0. [State COM = LOST COM]
Time : 11:04:03:710
Description : This is a State Communication TC 1000
Instance of protocol : 0
State : LOST COM
GTW/EN MF/C57 MF-55

10 INSTALLATION TRANSLATEFILE
The TranslateFile software is automatically installed with the application DS Agile Gateway.
10.1 TRANSLATEFILE
TranslateFile allows you to select a Microsol or standard file and set required protocol parameters.
Click the “Traduire” button to translate file into User readable format. TranslateFile application
It reads SOE file from specified location and translates it into a .gen file.
MF-56 GTW/EN MF/C57

11 WATCHDOG.LOG
A new line is added in this file each time a watchdog signals an issue. This can help you to determine which
part of the DS Agile Gateway is involved in the problem.
The format of the line is as follows:
1 Day (yyyy/mm/dd)
2 Time (hh:mm:ss)
3 Thread name
4 Exception code
Example 1
Day Time
Thread code
(yyyy/mm/dd) (hh:mm:ss)
Detection Watchdog Thread
2006:7:17 5:36:16 Exception code: -2147483645
[T_OMM_BD]
This can occur when Agency is stopped.

Example 2
Since the Gateway version 4.22.4, an exception code has been modified. In previous versions the code was
always 0xC0000005. As of that version, the code is different depending of origin of the issue.
Code Indication
0xC000008D DS Agile Gateway kernel didn't received Heart Beat from agency
0xC000008E An error occurred while calling ODSEnableAssociations ()
0xC000008F An error occurred while calling ODSLoadModel()
0xC0000090 An error occurred while calling ODSOpenSession ()
0xC0000091 An error occurred while calling OdLoadDll ()
0xC0000092 An error occurred while calling ODStartAgency ()
If, in Watchdog.log, you have such a line:

2007:06:12 10:01:53 Detection Watchdog Thread [T_OMM_BD] code exception:0xc000008d
This indicates that, on the 12th of June 2007, at 10 o’clock, DS Agile Gateway kernel raised an exception to
restart DS Agile Gateway software because it didn't receive the heartbeat from the agency.
Example 3
Since Gateway version 5.2.6, an exception code has been modified. As of that version, the code is different
depending of origin of the issue. There are two cases:
• internal exceptions: when DS Agile Gateway detects an major error, this error is logged in
watchdog.log with the internal code
Code Indication
0x00000008 DS Agile Gateway kernel did not received a Heart Beat from the Agency.
0x00000007 An error occurred while calling ODSEnableAssociations ()
0x00000003 An error occurred while calling ODSLoadModel()
0x00000005 An error occurred while calling ODSOpenSession ()
0x00000006 An error occurred while calling OdLoadDll ()
0x00000004 An error occurred while calling ODStartAgency ()
GTW/EN MF/C57 MF-57

Code Indication
0x00000002 An error occurred while initializing acquisition (client part over IEC 61850-8-1)
0x00000001 An error occurred while initializing a protocol
A line such as:

2007:06:12 10:01:53 Detection Watchdog Thread [T_OMM_BD] code exception:0x00000008
indicates that, on June 2007 12th, at 10 o’clock, DS Agile Gateway kernel raised an exception to restart
DS Agile Gateway software because it didn't receive the heartbeat from agency
• windows exceptions: when the DS Agile Gateway catches a windows exception, this exception will
be logged in watchdog.log with exception code, fault address,registers and call stack. The track can
be diagnosed the cause of the exception. Only a maintenance site could do it. Send the watchdog.log
to maintenance site.
//=====================================================
Time: Thu Mar 13 08:23:17 2008
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 00438B1D 01:00037B1D C:\Program Files\DCS\Gateway\tg_rcc.exe
Registers:
EAX:0170FFD8
EBX:00000000
ECX:00AD6A80
EDX:00000036
ESI:00AD6A80
EDI:00000000
CS:EIP:001B:00000000
SS:ESP:0023:00000048 EBP:00000000
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010206
Call stack:
Address Frame
00000044 0000:00000000 C:\Program Files\DCS\Gateway\tg_rcc.exe
MF-58 GTW/EN MF/C57

12 CONFIGURATION FILES
12.1 UCA2_OMM.XML
In the recent versions of DS Agile Gateway, a UCA2_OMM.xml file is delivered.
This enables the user to have information on the database.
This file presents three fields:
• bd1: version of database in folder ECDD1
• bd2: version of database in folder ECDD2
• current_bd: 1 (resp. 2) indicates that current datatbase is the one in folder ECDD1 (resp. ECDD2)
Example:
BD1 =0.0. indicates that there is no database in ECDD1 folder. DS Agile Gateway is running with database
version 18.2, installed in folder ECDD2.
12.2 GATEWAY.TXT
This is a readable file that describes configuration of kernel part of DS Agile Gateway.
For each datapoint there is an internal number that you can retrieve in the logbook
12.3 GATEWAY_COMP.TXT
This is a readable file that describes configuration of protocol part of DS Agile Gateway.
12.4 GTWIDTOUCA2
The GTWIdToUca2 software is automatically installed in ECDD1 and ECDD2 folders at DS Agile Gateway
application.
This allows you to link the data models and the DS Agile Gateway configuration.
GTW/EN MF/C57 MF-59

13 PORTMON
13.1 INSTALLATION PORTMON

Portmon is a freeware available on the Internet.
Portmon is useful to spy on the communications port. It can be used for testing hardware.
The HMI of Portmon is close to dbgview's one (same provider).
13.2 HOW TO USE

Stop DS Agile Gateway software if launched and work permit available.
Launch Portmon before running DS Agile Gateway software (double click on portmon.exe)
Do CTRL+H to display the dialog box that permit to define the maximum number of events to memorize. Set
it to 50000.
Click Apply; it will be then taken into account.

Chose the displaying mode as indicated:
Launch the Gateway software.
MF-60 GTW/EN MF/C57

When communication is establish between SCADA and, traces looks like:
GTW/EN MF/C57 MF-61

14 FAQ
14.1 T101: HOW TO CONVERT A T10X DECIMAL ADDRESS INTO A

STRUCTURED ADDRESS?
Question:
I have address 4 194 306 on a T101 configured to transmit Address on 8 bits.16 bits
What is the structured address?
Reply:
Pass 4 194 306 to hexadecimal: 0x400002 with structure on 8 bits.16 bits. It is 0x40.00002.
0x40 = 64; 0x0002=2. Decimal result is 64.2.
14.2 FILTERING & TRACES

Question:
What kind of filter can I set on traces to show only the frames sent on SCADA line?
Reply:
All the dumps of protocol traces begin with the size of the frame expressed in bytes.
Example [RX 5 bytes: 10 69 01 6a 16]
So you can put the filter bytes then trace tools will display only frames exchanged between SCADA and
DS Agile Gateway.
Question:
What is the signification of the number in "[ ]" after protocol name.
Example IEC101[0] … IEC101[1] … T104[2]?
Reply:
This is the instance of the protocol in configuration. The example you give indicates that you configured 3
protocols. First one was T101, second one was T101 too. Third one was T104. This permits to do the
filtering on one particular protocol. In your example you can do the filtering on second protocol by setting the
filter to "IEC101[1]".
14.3 COMMAND & TRACES

Question:
How can I understand the reason of interpret the acknowledgment of a DO ?
Reply:
The traces of DS Agile Gateway give you two cues: Ack / Ack_uca.
Ack Description
35 Negative acknowledgement received
36 Positive acknowledgement received on select
37 Negative acknowledgement received on select
38 Positive acknowledgement received on cancel select
39 Negative acknowledgement received on cancel select
40 // cancel select spontaneous (timeout)
MF-62 GTW/EN MF/C57

Signification of Ack_uca in case of IEC 61850-8-1 SBUS agency.

Ack_uca Description
0 UNKNOWN
1 NOT SUPPORTED
BLOCKED BY SWITCHING HIERARCHY: Topological interlocking is not supported by DS Agile
2
system at the time
3 SELECT FAILED
4 INVALID POSITION
5 POSITION REACHED
6 PARAMETER CHANGE IN EXECUTION: Not DS Agile
7 STEP LIMIT
8 BLOCKED BY MODE
9 BLOCKED BY PROCESS
10 BLOCKED BY INTERLOCKING
11 BLOCKED BY SYNCHROCHECK
12 COMMAND ALREADY IN EXECUTION
13 BLOCKED BY HEALTH
14 AMONG N CONTROL: not supported by DS Agile system
15 ABORTION BY CANCEL
16 TIME LIMIT OVER
17 ABORTION BY TRIP ????, not supported by DS Agile system
Extension in private range in case of IEC 61850-8-1 SBUS agency from C26x
Ack_uca Description
-1 Incoherent command received (device not existing, wrong command, ..)
-2 Command received, C26x not Ready.(initialization)
-3 Error on bay substation mode
-4 Command received, C26x in maintenance mode, faulty
-5 Device locked
Command (exec) received while command running on this device or command received during
-6
(inter-control delay)
-7 Refused by interlock
-8 Command already in position.
-9 Hardware default on DO board of C26x
-10 Invalid position of device
-11 Time-out between select and exec or time-out de response of IED
-12 Device locked by automatism DI associated
-13 Select received on a device selected yet
-14 Reception of "Select" command on a "Direct Execute".
-15 Refused cause of uniqueness incoherency (bay or site level)
-16 "Exec" command received on a "select Exec" device not selected before
-17 Cancel operator received
-18 Time-out feedback DI
-19 NO execution of the order, Used in UCA MXM
-20 used by the transformer: Time-out waiting DI TCIP present
GTW/EN MF/C57 MF-63

Ack_uca Description
-21 used by the transformer: Time-out waiting DI TCIP absent
-22 used by the transformer: bad TAP position following command
-23 used by the transformer: "Lower " received but TPI is min value yet
-24 used by the transformer: "Raise" received but TPI is max value yet
-25 Command on a not connected IED
-26 Time out searching for good conditions Synchrocheck
-27 GLOBAL ATCC in off state only GLOBAL ATCC ON can be accepted
-28 More than 4 transformers are connected, ATCC can't manage the busbar
-29 Invalid topology. At lest one organ is invalid
-30 TPI transformer is invalid
-31 C26x that manage transformer bay is disconnected
-32 Disjunction of transformer's tap changer is tripped
-33 Invalid transformer voltage
-34 Invalid Busbar voltage
Signification of ack_uca in case of UCA2 agency. Same as "Extension in private range in case of IEC61850
agency" but with a positive value.
Example1:
In dbgview
[18:37:52:282] [TG_RCC][Traite_TC_ACQ_Evt_UCA2] Anneau:1, Num TC:2427, Ack:36 Ack_uca: 0
[18:37:53:282] [TG_RCC][Traite_TC_ACQ_Evt_UCA2] Anneau:1, Num TC:2427, Ack:238 Ack_uca: 238.
36 = Positive acknowledgement received on select
238 = -18 Indicates "Device locked by automatism DI associated"
Example2:
36 = Positive acknowledgement received on select
16 = TIME LIMIT OVER
Example3:
At logbook level:
11:12:04:509 PROT# 1:Command structure information read: configuration ident:1017, Execute command,
Open
11:12:04:509 Possible to control Organe 1017 by PROT#1.
11:12:04:509 It's a TC 1017 configured S/E side System, and D/E side Scada on PROT#1.
11:12:04:509 Organe send to system: waiting acknowledge ...
11:12:04:743 Anneau:1, Num TC:1017, Ack:35 Ack_uca:12
11:12:04:743 Acknowledgement received from Organe 1017: EXECUTE FAILURE.
11:12:04:759 PROT# 1:A negative acknowledgment [NACK] has been sent to protocol
35 = Negative acknowledgement received
12 = COMMAND ALREADY IN EXECUTION
MF-64 GTW/EN MF/C57

14.4 LOSS OF COMMUNICATION

DS Agile Gateway stores SBUS data changes in its kernel. It is then able to answer quickly to any kind of
query from a remote master. It is a key advantage when communication with SCADA is subject to
disconnection and reconnection (PSTN network).
DS Agile Gateway detects TBUS disconnection from SCADA (time out) and provides this information on
SBUS to the central archiving/logging (or other DS Agile Gateway).
• In event of disconnection from SCADA, DS Agile Gateway stores events in a queue. For protocols IEC
60870-5-101 or IEC 60870-5-104 the DS Agile Gateway manages an internal datapoint which
indicates if this buffer (managed as a circular buffer) is full. Once the communication with SCADA is
recovered, this information can be transmitted as first event. The SOE file transfer must have been
enabled in configuration step: the time tag format must be Cp56Time2A
Note:
In T101, if, by mistake, Cp24Time2A has been selected, a text file named IEC-101-n warning is generated in the
installation folder and gives details
• In event of SBUS disconnection (means the lower connection is lost), DS Agile Gateway behaves
according to the value of the register Key "maintenance_if_dcnx_ethernet":
1: the communication with the SCADA is stopped, because DS Agile Gateway goes into maintenance
mode
0: All server datapoints are transmited to SCADA with quality field set to “Unknown”. Depending on the
TBUS protocol “Unknown” state of data is translated to specific invalid state.
Note:
The Gateway is NOT in maintenance mode.
• In event of disconnection of server on SBUS, DS Agile Gateway sets all information of server to
Unknown and generates the time-stamp. This enables the user to configure a time-stamping at
reconnection. This version does not involve repetition of information while SCADA switches between
Gtw and Gtw backup.
If buffered reports are configured:
• the datapoints are transmitted when the communication is recovered with the quality field set to Valid.
They are time-stamped with the time of the original acquisition.
• in a two-ring architecture, if there is no IEC/IEC Gateway redundancy, set the

maintenance_if_dcnx_ethernet of the single Gateway to 0 to prevent it to go to maintenance in
event of lower-ring S-Bus failure
Detection of disconnection and data invalidity are also transmitted to SCADA when it is an IED on Legacy
BUS under a DS Agile C26x that is disconnected. The difference is that unknown state is then emitted by the
IEC 61850-8-1 server and not by DS Agile Gateway itself.
GTW/EN MF/C57 MF-65

MF-66 GTW/EN MF/C57

PROBLEM ANALYSIS
GTW/EN PR/C57
DS Agile Gateway & WACU Problem Analysis
Contents
2 PROBLEM IDENTIFICATION 4
GTW/EN PR/C57 PR-1

Problem Analysis DS Agile Gateway & WACU
PR-2 GTW/EN PR/C57

DS Agile Gateway & WACU Problem Analysis

This chapter supplements the GTW/EN MF chapter.
GTW/EN PR/C57 PR-3

Problem Analysis DS Agile Gateway & WACU
2 PROBLEM IDENTIFICATION
Refer to the table that follows to find the description that best matches the experienced problem, then consult
the section referenced to perform a more detailed analysis of the problem.
Symptom What to check ?
Station bus break down
IEC 61850-8-1 server IP address
It is not possible to connect an If this IEC 61850-8-1 server is declared as “server of” the gateway in the
IEC 61850-8-1 server configuration database
"Lean.cfg" file (located in InstallGTW \Ecdd1 or InstallGTW \Ecdd2) does
not contain the name of this IEC 61850-8-1 server or the right IP address
Station bus break down
IEC 61850-8-1 client IP address
It is not possible to connect an
IEC 61850-8-1 Client (case of the GTW If this IEC 61850-8-1 client is declared as “client of” the gateway in the
IEC/IEC upper network) configuration database
"Lean.cfg" file (located in InstallGTW \Ecdd1 or InstallGTW \Ecdd2) does
not contain the name of this IEC 61850-8-1 client or the right IP address
The IEC 61850-8-1 client is connected but all
information is “unknown” (case of the GTW Database version in DS Agile GTW and the IEC 61850-8-1 client
IEC/IEC upper network)
The IEC 61850-8-1 server is connected but
Database version in DS Agile Gateway and the IEC 61850-8-1 server
all information is “unknown”
DS Agile Gateway is not synchronised If a DS Agile C26x is defined as the Master Clock of the system
Modem (if used) configuration
SCADA communication is not established Serial link connections / wiring
T104 or OPC server IP address
PR-4 GTW/EN PR/C57

RECORD SHEET
GTW/EN RS/C57
DS Agile Gateway & WACU Record Sheet
Contents
1 WORKSTATION CHARACTERISTICS 3
1.1 PC Characteristics 3
1.2 OS Characteristics 3
2 INSTALLATION 4
2.1 Software Delivery 4
2.2 DS AGILE Gateway Installation 4
2.3 Setup check 5
2.3.1 General check 5
2.3.2 Settings check 5
GTW/EN RS/C57 RS-1

Record Sheet DS Agile Gateway & WACU
RS-2 GTW/EN RS/C57

1 WORKSTATION CHARACTERISTICS
1.1 PC CHARACTERISTICS
PC Name
Clock Frequency (GHz)
RAM Size (KB)
1.2 OS CHARACTERISTICS
WINDOWS OS VERSION
WINDOWS OS SERVICE PACK
WINDOWS OS LANGUAGE
GTW/EN RS/C57 RS-3

2 INSTALLATION
2.1 SOFTWARE DELIVERY

DS AGILE SYSTEM VERSION
DS AGILE SYSTEM Release Note Checked:
Yes
No
DS AGILE GATEWAY VERSION
DS AGILE GTW Release Note Checked:
Yes
No
DS AGILE SBUS AGENCY VERSION
IEC 61850-8-1
DS AGILE SBUS Agency IEC 61850-8-1 Release Note Checked:
Yes
No
2.2 DS AGILE GATEWAY INSTALLATION

DS AGILE Gateway installed using GTW/EN IN Manual:
Yes
No
DS AGILE Gateway Installation directory:
Standard (C:\Program Files\ALSTOM\DCS\Gateway)
Other (precise): ____________________________
DS AGILE Gateway Installation Choice:
Complete (All protocols)
Partial (precise protocols): ____________________________
DS AGILE Gateway Installation problem:
Yes
No
DS AGILE SBUS Agency IEC 61850-8-1 Installation directory
Standard (C:\Program Files\ALSTOM\DCS\61850agency)
Other (precise): ____________________________
RS-4 GTW/EN RS/C57

2.3 SETUP CHECK
2.3.1 GENERAL CHECK

Check that the following files or directories are in the correct path (refer to GTW/EN IN):
DS AGILE Gateway version directory
DS AGILE SBUS Agency IEC 61850-8-1
Check that the following items are in the Start Menu:
DS AGILE Gateway gateway
DS AGILE SBUS Agency IEC 61850-8-1
2.3.2 SETTINGS CHECK

Check that the following registry keys are set:
• HKEY_CURRENT_USER\Software\ALSTOM\Tg\Main\st_SO_Lire
• HKEY_CURRENT_USER\Software\ALSTOM\Tg\Main\st_SO_Remon
• HKEY_CURRENT_USER\Software\ALSTOM\Tg\Main\timer_init
• HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\Tg\ACQ
• HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\Tg\BD
• HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\Tg\System
• HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\Tg\Main\maintenance_if_dcnx_ethernet
DS Agile Gateway launched:
Yes
No
GTW/EN RS/C57 RS-5

RS-6 GTW/EN RS/C57

TECHNICAL DATA
GTW/EN TD/C57
DS Agile Gateway & WACU Technical Data
Contents
1 INTRODUCTION 2
1.1 General features 2
2 FANLESS EMBEDDED PC CHARACTERISTICS 3

2.1 Operating system 3
2.2 Configuration 3
2.3 Communication ports with SCADA 3
2.4 Mechanical Characteristics 4
2.5 Power Supply 4
2.6 Environmental Tests 4
2.7 Mechanical Tests 4
2.8 EMC Tests 5
2.9 Electrical Tests 6
2.10 Wiring 6
2.10.1 Serial connection 6
2.10.2 Ethernet connection 6
3 INDUSTRIAL AND STANDARD PC CHARACTERISTICS 7

3.1 Operating System 7
3.2 Configuration 7
3.3 Communication ports with SCADA 7
3.4 Ethernet Communication port 7
3.5 Minimum Rated Values 7
3.6 DC auxiliary supply 8
3.7 AC auxiliary supply 8
3.8 Insulation 8
3.9 Environmental 9
3.10 Mechanical 9
3.11 Safety 9
3.12 EMC Tests 9
3.13 Wiring 10
3.14 A5xx industrial PC particular characteristics 10
4 SOFTWARE GATEWAY CHARACTERISTICS 13

4.1 Number of Data Points 13
4.2 Response time 13
4.3 SBUS Avalanche 13
4.4 Exchanging message with SCADA 13
4.5 SBUS acquisition 13
4.6 Time specifications 13
5 SYSTEM DEPENDABILITY 14
5.1 MTBF 14
5.2 Availability 14
GTW/EN TD/C57 TD-1

Technical Data DS Agile Gateway & WACU
1 INTRODUCTION
This document is a chapter of the Alstom DS Agile Gateway documentation. It is the chapter Technical Data
(TD) of this Product.
Alstom DS Agile Gateway is a software package installed on an industrial PC or on a fanless Embedded PC
to increase environmental capabilities. Technical characteristics of these PCs are described thereafter.
For more information about hardware description see chapter GTW/EN HW. For more information about
connection diagrams see chapter GTW/EN CO.
1.1 GENERAL FEATURES

An Alstom DS Agile Gateway can manage up to 4 protocols and up to 8 channels.
Different kinds of links are available (list is not limited to the ones given):
• PSTN MODEM (external device)

• Radio link through MODEM
• Ethernet
Features Limit
Number of devices (IEC 61850-8-1 devices - Legacy Bus devices:
256
C26x, HMI, Gateway, IED)
Binary inputs (SP, DP, SI, 1 among N) 2048/device
Measurements 512/device
Counters 64/device
Output controls 1024/device
Setpoints outputs (binary and analogue) 512/device
Table 1: General features
TD-2 GTW/EN TD/C57

2 FANLESS EMBEDDED PC CHARACTERISTICS
2.1 OPERATING SYSTEM

The Gateway software is intended to run on a dedicated fanless Embedded PC with the following
characteristics:
• Model: ADVANTECH UNO-3074/UNO-3074A fanless Embedded Box Computer

• Processor: M 1.4/Atom1.66 GHz
• Memory: 2 GB DDR SDRAM, 4 GB Compact Flash (no rotating hard disk)
• 24 V Power Supply
• OS Support Windows XP embedded
2.2 CONFIGURATION
The configuration of the gateway is given in chapter GTW/EN HW. This configuration complies with the
environmental constraints given hereafter.
2.3 COMMUNICATION PORTS WITH SCADA

• Clock Battery-backup RTC for time and date
• LAN 2 x 10/100Base-T RJ-45 ports (Built-in boot ROM in flash BIOS)
• Serial Ports 2 x RS-232, 2 x RS-232/422/485 with DB9 connectors Automatic RS-485 data flow
control
• Serial Port Speed RS-232: 50 bps ~ 115.2 kbps RS-422/485: 50 bps ~ 921.6 kbps (max.)
• USB Ports 4 x USB, USB EHCI, Rev. 2.0 compliant
• Digital Inputs (4-ch. wet contact DI0 ~ DI3)
2,000 VDC isolation
50 ~ 70 VDC over-voltage protection
±50 VDC input range and 10 kHz speed
Interrupt handling speed: 10 kHz
• Digital Outputs (4 ch. DO0 ~ DO3)

2,000 VDC isolation and 200 mA max/channel sink current
Keep output status after system hot reset
0 ~ 40 VDC output range and 10 kHz speed
• Counters/Timers (2 x 16-bit)
Counter source: DI1 & DI3, Pulse output: DO2 & DO3
Can be cascaded as one 32-bit counter/timer
Down counting, preset counting value
Timer time base: 100 kHz, 10 kHz, 1 kHz, 100 Hz
GTW/EN TD/C57 TD-3

The ADVANTECH PC's configuration given below offers four serial communication ports and 2 Ethernet
communication ports:
Telecontrol bus: up to four different protocols and up to 2 channels per protocol can be configured
on a per DS Agile Gateway basis.
Station bus: one (an Ethernet DIN-rail switch can be used for redundancy Ethernet network).
2.4 MECHANICAL CHARACTERISTICS

Construction Aluminum housing
Mounting Wall/Panel/Stand
UNO-3074: 193 x 179 x 238 mm
Dimensions (W x H x D)
UNO-3074A: 181 x 177 x 237 mm
Weight 7 kg
2.5 POWER SUPPLY

Output Rating 24 W (typical, no PCI cards)
9 ~ 36 VDC (e.g. +24 V @ 2 A) (Max. 5 A),
Input Voltage
AT. (16 ~ 36 VDC for 12 V PCI boards)
2.6 ENVIRONMENTAL TESTS

Test Standard UNO-3074 UNO-3074A
Dry Heat IEC 60068-2-2 +60° / 24h +70°C / 24h
Cold IEC 60068-2-1 -15°C / 24h -20°C / 24h
Damp Heat Storage IEC 60068-2-56 +60°C / 95% humidity / 48h +60°C / 95% humidity / 24h
Low Temperature Storage IEC 60068-2-1 -40°C / 48h -40°C / 24h
Damp Heat Storage IEC 60068-2-3 +40°C / 95% humidity / 48h
Damp Heat Storage IEC 60068-2-56 +40°C / 95% humidity / 48h
Temperature Cycle IEC 60068-2-14 -10°C to 50°C in 5h30; 10 cycle
Thermal Profile IEC 60068-2-2 25°C/55°C/60°C; 6h each 28.3°C/60°C; 6h each
Cold Start IEC 60068-2-1 -15°C / 20 cycle of on/off-on/off -20°C / 20 cycles of on/off
-20°C: 1000 power on, 1000 power
off
Power ON/OFF IEC 60068-2-1; IEC 60068-2-2
+70°C: 1000 power on, 1000
power off
2.7 MECHANICAL TESTS

0.008G²/Hz , 2 Grms, 5-500Hz, X,Y 0.092G²/Hz , 2 Grms, 5-500Hz,
Random Vibration (Operation) IEC 60068-2-64
and Z axis, 1h per axis X,Y and Z axis, 1h per axis
2 Grms, 5-500Hz, 1 Octave / min, 2 Grms, 5-500Hz, 1 Octave / min,
Sine Vibration (Non-operation) IEC 60068-2-6
X,Y and Z axis, 1h per axis X,Y and Z axis, 1h per axis
0.026G²/Hz , 2.16 Grms, 5-500Hz,
Package Vibration IEC 60068-2-64
X,Y and Z axis, 30h per axis
Federal Standard 101 Method 5007
Package Drop 1 corner, 3 edges, 6 faces, 91cm 1 corner, 3 edges, 6 faces, 92cm
Testing procedure B
TD-4 GTW/EN TD/C57


Half sine wave, 50G, pulse Half sine wave, 50G, pulse
Shock (Operation) IEC 60068-2-27 duration 11 ms, six sides, each duration 11 ms, six sides, each
3 times 3 times
2.8 EMC TESTS

EN 55022/1998+ A1:2000+A2:2003 N/A on Power supply: the device is
EN 55011:1998+ A1:1999+A2:2000 not intended to be connected to AC
Conducted Emission
(G1 Class A) 150kHz-30MHz Class A main supply
Measurement
EN 61000-6-4 (2001): CISPR 11 Ethernet com port: 55011 Group 1
Class A (1990) class A; 150kHz to30MHz
EN 55022/1998+ A1:2000+A2:2003
EN 55011:1998+ A1:1999+A2:2000
Radiated Emission Measurement (G1 Class A) 30MHz-1GHz Class A 30MHz-1GHz Class A
EN 61000-6-4 (2001): CISPR 11
Class A (1990)
N/A on Power supply: the
Power Harmonic Measurement EN 61000-3-2/2000 Class D equipment is not intended to be
connected to AC main supply
N/A on Power supply: the device is
Voltage Fluctuations EN 61000-3-3/1995+A1:2001 Pass not intended to be connected to AC
main supply
IEC 61000-4-2 (2001)
EN 55024 (1998)+
Electrostatic Discharge Immunity 8kV (Air); 4kV (contact) 8kV (Air); 4kV (contact)
A1(2001)+A2(2003)
EN 61000-6-2:2001
IEC 61000-4-3 (2002) Level 2 and 3
EN 55024 (1998)+ Level 2 and 3 3V/m and 10V/m; 80~1000MHz
Radiated Emission Measurement
A1(2001)+A2(2003) 2V/m and 10V/m; 80~1000MHz 3V/m; 1400~2000MHz
EN 61000-6-2:2001 1V/m; 2000~2700MHz
IEC 61000-4-4 (2004) Power Line: +/-0.5kV; +/- 1kV; +/-
EN 55024 (1998)+ 2kV Power Line: +/-0.5kV; 2kV
Electrical Fast Transient/Burst
A1(2001)+A2(2003) Signal Control Line: +/-0.25kV; +/- Signal Control Line: +/-0.5kV; 1kV
EN 61000-6-2:2001 0.5kV; +/- 1kV
DC input and DC output Power
IEC 61000-4-5 (2001) ports: 1.2/50(8/20) +/-0.5kV (CM);
DC input and DC output Power
EN 55024 (1998)+ +/- 0.5kV (DM)
Surge Immunity ports: 1.2/50(8/20) +/-0.5kV (CM);
A1(2001)+A2(2003) AC input and AC output Power
+/- 0.5kV (DM)
EN 61000-6-2:2001 ports: 1.2/50(8/20) +/-2kV (CM); +/-
1kV (DM)
IEC 61000-4-6 (2003)+A1(2004)
EN 55024 (1998)+ Level 2 and 3 0.15MHz~80MHz; 3Vrms and
Conducted Disturbance Immunity
A1(2001)+A2(2003) 0.15MHz~80MHz; 3 and 10V (CM) 10Vrms(CM)
EN 61000-6-2:2001
IEC 61000-4-8 (2001)
EN 55024 (1998)+ 50Hz; 1A/M 50Hz; 1A/M
Power Frequency Magnetic Field
A1(2001)+A2(2003) 50HZ; 30A/M 50HZ; 30A/M
EN 61000-6-2:2001
GTW/EN TD/C57 TD-5

2.9 ELECTRICAL TESTS

Dip 30% during ½ period no effect.
IEC 61000-4-11 (2004)
Other -> criteria C N/A on Power supply: the device is
EN 55024 (1998)+
AC Voltage Dips and Interruption Dip 0% during ½ period no effect. not intended to be connected to AC
A1(2001)+A2(2003)
Other -> criteria C main supply
EN 61000-6-2:2001
Short interruptions -> criteria C
2.10 WIRING
2.10.1 SERIAL CONNECTION

The connection with the Alstom DS Agile Gateway is full compatible with standard RS-232/422/485 (Two
RS-232 & two RS-232/422/485 ports with RS-485 automatic flow control).
COM1 and COM2 are compatible with standard RS-232 serial communication interface ports.
COM3 and COM4 are compatible with standard RS-232/422/485 serial communication interface ports. The
default setting for COM3 and COM4 is for RS422/485
A SCADA communication can be established on one serial port. One more serial port is needed for
redundancy.
A Null-Modem cable can be connected to a SCADA simulator or a Network Analyser.
For more information about the connection see the chapter GTW/EN CO.
2.10.2 ETHERNET CONNECTION

The connection with the Alstom DS Agile Gateway is fully compatible with standard 10/100 Mbps RJ45.
A SCADA communication can be establish on one Ethernet port. One more Ethernet port is needed for
redundancy.
A crossover Ethernet cable can be connected to a SCADA simulator or a Network Analyser.
For more information about connections see the chapter GTW/EN CO.
TD-6 GTW/EN TD/C57

3 INDUSTRIAL AND STANDARD PC CHARACTERISTICS
3.1 OPERATING SYSTEM

The Gateway software can run on a standard or an industrial PC with one of the following operating systems:
• Windows 2003 Server,

• Windows XP SP 3 or
• Windows 7 Ultimate 64 bits
Minimum RAM size: 256 MB.
Using a 256 MB RAM you will not need a swap memory, i.e. the gateway and the system will run in RAM
only.
3.2 CONFIGURATION
The configuration of the gateway is given in table 1 of chapter GTW/EN HW. This configuration complies with
the environmental constraints given hereafter.
3.3 COMMUNICATION PORTS WITH SCADA

• Number of simultaneous protocols: 4
• Number of serial ports by protocol: 2 (main, backup)
• Thus 8 ports maximum on one gateway: 2 cards with 4 ports
• Number of communication ports: 8 at the most, set by Alstom DS Agile SCE
• Baud rate (bits/s): from 100 to 38400, set by Alstom DS Agile SCE
The motherboard has 2 serial communication ports. You can use them for one communication with SCADA
plus a redundant port or 2 communications with SCADA. For additional communication ports, add a PCI or
an ISA communication card into the PC.
3.4 ETHERNET COMMUNICATION PORT

The Ethernet communication port is a 10 / 100 Mbps RJ45 connector.
3.5 MINIMUM RATED VALUES

Test Standard Conditions
Minimum requirement
Rated Auxiliary Voltage DC IEC 60255-6
48 VDC, 110/125 VDC, 220/250 VDC
Rated Frequency IEC 60255-6 50 or 60 Hz.
Rated AC Voltage No Standard 84 à 240 VAC
GTW/EN TD/C57 TD-7

3.6 DC AUXILIARY SUPPLY

Vn +/- 20%
Supply variations IEC 60255-6
Vn + 30% & Vn - 25% for information
From Vn down to 0 within 1mn
Ramp down to zero /
From Vn down to 0 within 100mn
From 0 up to Vn within 1 mn
Ramp up from zero /
From 0 up to Vn within 100mn
Supply interruption IEC 60255-11 From 2 ms to 100 ms at 0.88 Vn
40s interruption IEC 60255-11 /
Reverse polarity / Continuous withstand
12% x Vn AC ripple, frequency =100 Hz or 120 Hz
Ripple (frequency fluctuations) IEC 60255-11
12% x Vn AC ripple, frequency = 200 Hz for information
3.7 AC AUXILIARY SUPPLY

Supply variations IEC 60255-6 Vn +/- 20%
2 ms to 20 ms
Dips & Short interruptions IEC 61000-4-11
50 ms to 1 s
Frequency fluctuations IEC 60255-6 From 44 to 55 Hz
Harmonics Immunity IEC 61000-4-7 5% over the range 2nd to 17th
3.8 INSULATION
Dielectric IEC 60255-5: 2000 2 kV, 50 Hz, 1 mn CM
2 kV, 50 Hz, 1 mn CM
IEEE C37.90.1: 1989
1 kV, 50 Hz, 1 mn DM
Insulation Resistance IEC 60255-5: 2000 > 100 MΩ at 500 VDC
Class 1:
5 kV, 1.2/50 μs, 0.5 J, 500Ω CM on power supplies
HV Impulse IEC 60255-5: 2000 3 kV, 1.2/50 μs, 0.5 J, 500 Ω DM on power supplies
Class 1:
1 kV, 1.2/50 μs, 0.5 J, 500 Ω CM on communications
TD-8 GTW/EN TD/C57

3.9 ENVIRONMENTAL
Cold Operating IEC 60068-2-1 Test Ad: -10°C, 96h
Cold Storage IEC 60068-2-1 Test Ad: -40°C, 96h
Test Bd:
Dry Heat Operating IEC 60068-2-2
+40°C, 96h, accurate +55°C, 2h, errors acceptable
Dry Heat Storage IEC 60068-2-2 Test Bd: +70°C, 96h
IEC 60068-2-3 Test Ca: +40°C, 10 days, 93% RH
Damp Heat Operating
IEC 60068-2-30 +25°C to +55°C, 93% RH, 3 cycles of 24h
3.10 MECHANICAL
Vibration response (energised) IEC 60255-21-1 Class 1
Vibration endurance (non-
IEC 60255-21-1 Class 1
energised)
Shock response (energised) IEC 60255-21-2 Class 1
Bump (non-energised) IEC 60255-21-2 Class 1: 10g, 16ms, 2000/axis
Seismic (energised) IEC 60255-21-3 Class 1
Drop
no packaging IEC 60068-2-31 Test Ec: 2 drops from 50mm corner drop, and topple test
with packaging IEC 60068-2-32 Test Ed: 2 drops from 0.5m on each face, edge and corner
3.11 SAFETY
CAPIEL draft Product
Product Safety Safety document under CE mark conformity
preparation
3.12 EMC TESTS

Cover on: Class III:
Electrostatic Discharge IEC 61000-4-2 8 kV air discharge
6 kV contact discharge
Class III:
10 V/m, 80 to 1000 MHz
IEC 61000-4-3 Modulation: 1 kHz, 80%
RFI Immunity-radiated
ENV 50204 Polarisation H & V
10 V/m, 900 to 1800 MHz
Modulation: 50%
Class IV on power supply: 4 kV, 2.5 kHz
Fast Transient Burst IEC 61000-4-4
Class III on communications: 2 kV, 5 kHz
GTW/EN TD/C57 TD-9


Level 3 on power supply:
2kV CM / 1kV DM
Surge Immunity IEC 61000-4-5
Level 3 on communication:
2 kV CM
Conducted RFI Immunity IEC 61000-4-6 10 Vrms, 150 KHz to 80 MHz
Power Frequency Magnetic
IEC 61000-4-8 30 A/m continuous
Field Immunity
Damped Oscillatory Magnetic
IEC 61000-4-10 10 A/m
Field Immunity
Class III on power supply:
2.5 kV CM / 1 kV DM
High Frequency Disturbance IEC 61000-4-12 1 MHz, 400 bursts/s & 100 kHz, 50 bursts/s
Class II n communications:
1 kV CM / 0.5 kV DM
RFI Emissions
Class A: 0.15 to 30 MHz:
Conducted Emissions IEC 60255-25 0.15 to 0.5 MHz: 79 dBμV quasi peak
0.5 to 30 MHz: 73 dBμV quasi peak
Class A:
Radiated Emissions IEC 60255-25
30 to 1000 MHz: 30 dBμV/m at 30 m or 40 dBμV/m at 10 m
3.13 WIRING
The connection with the Alstom DS Agile Gateway is fully compatible with the standard RS232C.
A SCADA communication can be establish on one serial port. One more serial port is needed for
redundancy.
A Null-Modem cable can be connected to a SCADA simulator or a Network Analyser.
For more information about the connection see the chapter GTW/EN CO.
3.14 A5XX INDUSTRIAL PC PARTICULAR CHARACTERISTICS

In harsh environments, the DS Agile Gateway & WACU can be set up on a rugged DS Agile A505Q or
A507Q industrial-type computer.
Its technical characteristics are as follows:
Operating conditions
Quantity Operating conditions
Operating: 0°C to +40°C
Temperature:
Non-operating: -20 to +60°C
Operating: 10 ~85% @ 40°C non condensing
Humidity:
Non-operating: 10 ~95% @ 40°C non condensing
Operating: 1 Grms
Vibration (5 ~500 Hz):
Non-operating: 2 G
400W ATX/PFC auto-switching power supply
Power supply:
(100 – 240 VAC, 60 – 50 Hz, 8 – 4 A )
Cooling including air filter: Fans: 1 (12 cm / 114 CFM) + 1 (6 cm / 28 CFM)
TD-10 GTW/EN TD/C57

Quantity Operating conditions

Operating: 10 G (with 11 ms duration, half sine wave)
Shock:
Non-operating: 30 G
Design
Quantity Size and weight
Dimensions (WxHxD) : 482 x 177 x 479 mm
Weight: 17.6 kg
Mechanical tests
Tests Standard Conditions
Random vibration (operation) IEC60068-2-64 1 Grms, 5-500Hz
Sine vibration (non-operation) IEC60068-2-64 2 G, 5-500Hz
Shock (operation) IEC60068-2-27 10G (Half sine wave, pulse duration 11ms)
Shock (non-operation) IEC60068-2-27 30G
EMC tests
EN 55022 (2006) +A2 (2010)
EN 55011 (2009) Power port: meet Class A limit
Conducted emission measurement
(Group 1 class A) Telecom port: meet Class A limit
EN 61000-6-4 (2007)
EN 55022 (2006) +A2 (2010)
EN55011 (2009)
Radiated emission measurement Meet Class A limit
(Group 1 class A)
EN 61000-6-4 (2007)
EN 61000-3-2 (2006) + A2
Power harmonic measurement emission Meet Class A limit
(2009)
Voltage fluctuations and flicker emission EN 61000-3-3 (2008) Meets the requirements.
EN 61000-6-2 (2005),
EN 55024 (2010), Meets the requirements of Performance
Electrostatic discharge immunity
Criterion A
IEC 61000-4-2 (2008)
EN 61000-6-2 (2005),
Radiated emission immunity
IEC 61000-4-3 (2006) + A1 Criterion A
(2007) + A2 (2010)
EN 61000-6-2 (2005),
Electrical fast transient/burst immunity
IEC 61000-4-4 (2004) + A1 Criterion A
(2010)
EN 61000-6-2 (2005),
Surge immunity
Criterion A
IEC 61000-4-5 (2005)
EN 61000-6-2 (2005),
High frequency conducted immunity
Criterion A
IEC 61000-4-6 (2008)
GTW/EN TD/C57 TD-11


EN 61000-6-2 (2005),
Power frequency magnetic field immunity EN 55024 (2010), 50Hz or 60Hz; 1A/m, 1 minute, Criterion A
IEC 61000-4-8 (2009)
Electrical tests
Meets the requirements of

Voltage dips:
1. 100% reduction Performance Criterion A
IEC 61000-4-11 (2004)
EN 61000-6-2 (2005)
Voltage Interruptions:
1. 100% reduction Performance Criterion C
AC Voltage dips and voltage variations
Meets the requirements of

Voltage dips:
1. >95% reduction Performance Criterion A
EN 55024 (2010)
Voltage Interruptions:
1. >95% reduction Performance Criterion C
TD-12 GTW/EN TD/C57

4 SOFTWARE GATEWAY CHARACTERISTICS
4.1 NUMBER OF DATA POINTS

Refer to § 1.1.
4.2 RESPONSE TIME

Time to receive a response after sending a request: 100ms
4.3 SBUS AVALANCHE

The linked list that manage events can memorise 15 000 events by protocol process.
4.4 EXCHANGING MESSAGE WITH SCADA

Response time to a SCADA request after the parameter settings phase for the parameters, synchronisation
pre and post transmission times:
less than 30 milliseconds regardless of the protocol
4.5 SBUS ACQUISITION

The gateway can support avalanche of events without loss during a short period of time.
4.6 TIME SPECIFICATIONS

Operations Gateway
Time between DI change of state at bay computer and gateway reception 500 ms
Time between AI change of value at bay computer and gateway reception sampling period + 1 s
Time between gateway control initiation and DO activation 750 ms
Table 2: Time specifications
GTW/EN TD/C57 TD-13

5 SYSTEM DEPENDABILITY
5.1 MTBF
Device MTBF
Industrial PC Gateway 50,000h
Fanless embedded UNO-3074 Gateway 303,534h @30°C,Telcordia method Issue 2
Fanless embedded UNO-3074A Gateway 345,000h @30°C,Telcordia method Issue 2
Table 3: MTBF
5.2 AVAILABILITY
Device MTTR (in minutes)
Industrial PC Gateway 30 to 60
Fanless embedded PC Gateway 14 to 16
Table 4: Availability
TD-14 GTW/EN TD/C57

GLOSSARY
GTW/EN LX/C57A
DS Agile Gateway & WACU Glossary
Term/Acronym Description
100Base Fx Fiber optic ports are full/half duplex at 100 Mbps only.
The copper ports are full/half duplex and auto-sense the transmission speed. They will auto-
10Base Tx and negotiate with the connected device to determinate the optimal speed. When the connected
100Base TX device is only capable of transmitting at 10 Mbps, the Ethernet switch unit or board follows
10 Mbps.
BRCB Buffered Report Control Block
LPHD Logical node PHysical Device
URCB Unbuffered Report Control Block
A/D Analog/Digital
A/R Auto-Reclose(r)
Abstract Communication Service Interface
ACSI Mapping from standard IEC 61850 abstract specification of a communication service to a
concrete communication infrastructure based on the CORBA standard.
ADC Analog to Digital Converter
AE qualifier Application Entity qualifier (Used internally by IEC 61850 to identify a server Application)
Analogue Input (Measurement Value including state attribute)
AI Usually voltage or current DC signals delivered by transducers, and representing an external
value (refer to CT/VT for AC).
AIS Air Insulated Substation
Analogue Input Unit
AIU
C26x controller's board for DC analogue inputs
Alarm An alarm is any event set as alarmed during the configuration process
Analogue Merging Unit
Interface device which acquires analogue signals from conventional CTs and VTs and
AMU performs digital signal processing to generate and distribute output sampled value streams
according to IEC 61850-9-2LE standardised definitions for communication with substation IEDs
and controllers
Analogue Output
AO
Value corresponding to a desired output current applied to a DAC
AOU Analogue Output Unit (C26x controller's board for analogue outputs)
ApccI Accumulator Input
API Application Programming Interfaces
ASCII American Standard Code for Information Interchange
Application Specific Data Unit
ASDU
Name given in the OSI protocol for applicative data (T101, T103, T104)
Automatic Tap Change Control
ATCC
Automation of secondary voltage regulation, more specific than AVR
Automatic Voltage Regulator
AVR Automation used to regulate secondary voltage using an automatic tap change control (see
ATCC). A set of features can be added, see C26x/EN FT
Set of LV, MV or HV apparatus (switching devices and transformers) and IEDs (Protection,
Bay
Measurement…) usually built around a Circuit Breaker and controlled by a Bay Controller Unit.
Binary Coded Decimal
C26x-supported coding on a set of Digital Inputs that determines a Digital Measurement, then
BCD
a Measurement value (with a specific invalid code when coding is not valid). Each decimal digit
is coded over 4 binary digits.
Bay Control Point
BCP Name given to the device or part used to control a bay. It can be a Mosaic Panel, a C26x unit's
LCD,… Usually associated with Remote/Local control.
GTW/EN LX/C57a LX-1

Glossary DS Agile Gateway & WACU
Bay Control Unit
BCU
Name given to the C26x that manages a bay. Usually as opposed to “Standalone” (RTU).
BGD BackGrounD scan (low priority scan of status in T101/T104)
Binary Input (or Information)
BI Name given in the C26x controller to information that has already been filtered, before it
becomes an SPS, DPS… with time tag and quality attributes.
Basic Interface Unit
BIU
C26x controller's board for auxiliary power supply, watchdog relay, redundancy I/O.
BNC Bayonet Neill–Concelman: RF connector for coaxial cables.
Category 5 unshielded twisted pair (UTP) cabling. An Ethernet network operating at 10 Mbps
(10BASE-T) will often tolerate low quality cables, but at 100 Mbps (10BASE-Tx) the cable must
be rated as Category 5, or Cat 5 or Cat V, by the Electronic Industry Association (EIA). This
Cat. 5
rating will be printed on the cable jacket. Cat. 5 cable contains eight conductors, arranged in
four twisted pairs, and is terminated with an RJ45 type connector. In addition, there are
restrictions on the maximum cable length for both 10 and 100 Mbps networks.
Circuit Breaker
CB Specific dipole switch with capability to make line current and break fault current. Some have
isolation capability (nominal earth on each side)
Compact Bay Controller, small capacity Bay Controller Unit for Medium Voltage applications,
CBC
typically C26x in 40TE case
Complemented Contact
CC A double counter is acquired from two contacts. One is called the true contact (TC), the other is
the complemented contact (CC). Normally these contacts have complementary states.
Circuit breaker Control Unit
CCU
C26x controller's board dedicated to switch control with 8 DIs, and 4 DOs
Conceptual Data Modeling
Modeling of system/device data using a hierarchy of structured data (called object of class)
CDM
with their attributes, method or properties and the relations between them. It maps common
data to devices or components of devices, with a guaranty of interoperability.
Defined in IEC 61850 as the description of a set of objects that share the same attributes,
Class
services, relationships, and semantics.
Defined in IEC 61850 as an entity that requests a service from a server and that receives
Client
unsolicited messages from a server.
Cluster Pair of two redundant controllers or computers
CMT Controller Management Tool
CO Command, logic information Output (Functional Component) / Contact Open
COMTRADE COMmon format for TRAnsient Data Exchange (IEC 60255-24 international standard)
Central Processing Unit
CPU
C26x controller's main board, based on a PowerPC micro-processor.
Cyclic Redundancy Check
CRC Coding result send with packet of transmitted data to guarantee their integrity. Usually the
result of a division of data transmitted using a polynomial code.
Character Separate Values
CSV
ASCII values separated by a predefined character or string as in Excel or Comtrade ASCII.
Current Transformer
Basically the device connected to the electrical process used to extract a current
CT
measurement. By extension part of a device (C26x) that receives AC values and converts it to
a numerical measurement value.
CT/VT Current and Voltage transformers
conventional By extension, it is the C26x controller's TMU board.
DAC Data Acquisition component of the GPT
Digital to Analogue Converter
DAC
Used to generate analogue signals (usually DC) from a digital value.
LX-2 GTW/EN LX/C57a

Double Attached Node implementing PRP (defined by IEC 62439-3)
DANP
Such an IED sends the messages over two separate networks.
DataBase
Tool or set of data that define all the configuration of a system or specific device such as a
DB
substation computer or bay controller. Contrary to setting parameters, a DB has a structure
that cannot be modified on-line. DBs are always versioned.
DB-9 A 9-pin family of plugs and sockets widely used in communications and computer devices.
Don’t Believe It
DBI Term used to describe the undefined state of a double point when its inputs are not
complementary. DBI00 is state motion or jammed. DBI11 is undefined.
DBID Database Identity Brick
External master clock and protocol transmission
DCF77 LF transmitter located at Mainflingen, Germany, about 25 km south-east of Frankfurt ,
broadcasting legal time on a 77.5 kHz standard frequency.
DCO Double Control Output
Device Control Point
DCP
Located at device level (electric device or IED). It should have its own Remote/Local switch.
Digital Control System
DCS Generic name of system based on numeric communication and devices, to be opposed to
traditional electrically wired control.
Double CounTer
DCT Counter based on 2 DIs with complementary states (counting switchgear operations for
example).
DE Direct Execute
DELTA MV Phase–phase analogue values received from the "delta" winding connections of a transformer.
DFT Discrete Fourier Transform
Digital Input
DI Binary information related to the presence or to the absence of an external signal, delivered by
a voltage source.
DC Input Unit
DIU
C26x controller's board hosting digital inputs
Dynamic Link Library. Available with Windows XP. Feature allowing executable code modules
to be loaded on demand and linked at run time. This enables the library-code fields to be
DLL
updated automatically, transparent to applications, and unloaded when they are no longer
needed.
Digital Measurement
DM
Measurement value acquired from DIs with a specific encoding: BCD, Gray, 1 among N…
Distributed Network Protocol
DNP3.0 DNP3 is a set of communication protocols used between components in process automation
systems.
Digital Output
DO Used to apply a voltage to an external device via a relay, in order to execute single or dual,
transient or permanent commands.
Degree Of Freedom
DOF Used for a template attribute, that can be modified or not when used. An attri-bute has a
degree of freedom if a user can modify the values of its instances.
Digital Output Unit
DOU
C26x controller's board hosting digital outputs.
DP Data Point, low-level object in the structure, wired or not, with or without links
Double (Point) Control
DPC Two digit and/or relays outputs with complementary states (OPEN, CLOSE) used for device
control.
DPC Double Point Control, control sent over 2 digital outputs.
GTW/EN LX/C57a LX-3

Double Point Status, information derived from 2 digital inputs
DPS
Usually used for Position indication of switching devices (OPEN, CLOSE).
Extended Communication Unit
ECU External module connected to the CPU board. This module converts non-insulated RS232
signals into optical or insulated RS485/RS422 signals.
Transmission protocol dedicated to time synchronisation and standardised by EDF.
EH90
Specification document: D.652/90-26c, March 1991.
"Ensemble de Protection Ampèremétrique de Terre Résistante" (French legacy very resistive
EPATR
earth current module).
EQL Equation Logic, especially for interlocking.
An event is a time-stamped change of state/value acquired or transmitted by a digital control
Event
system.
Fast Ethernet An Ethernet system that is designed to operate at 100 Mbps.
Factory Acceptance Test
FAT
Validation procedures executed with the customer at the factory.(i.e. SAT)
Functional Block Diagram
FBD One of the IEC 61131-3 programming languages (language used to define configurable
automations).
FIFO First In First Out
FLS Fast Load Shedding
FO Fibre Optic
FP Front Panel
FSS Force Suppress Substitute
FTP Foil Twisted Pair
Level 6 session of OSI, the gateway can be any device transferring data between different
networks and/or protocols. The RTU function of the C26x behaves like a gateway at the
Gateway
SCADA or RCP level. The DS Agile Gateway is a separate PC-based application dedicated to
this function.
Graphic Human interface Unit
GHU
C26x controller's front panel interface (LCD, buttons, front RS port)
GIS Gas Insulated Substation
GIS-Watch Monitoring and control device for GIS substations
GLOBE GLOBE hard-coded brick used in DS Agile IEC 61850 mapping for C26x mode management
GMT Greenwich Mean Time, former absolute time reference. Replaced by UTC.
GOOSE Generic Object Oriented Substation Event
Global Positioning System
GPS Based on triangulation from satellite signal, that transmit also absolute GMT time used to
synchronise a master clock.
GPT Generic Protocol Translator software, supplied by ASE
Group Logical combination of BIs (i.e. SP, DP, SI or other groups)
GSSE Generic Substation Status Event
A system that allows packets to transmitted and received, but not at the same time. Contrasts
Half-duplex
with full-duplex.
Facility for an operator to set manually the position of a device (acquired by other means) from
Hand Dressing the HMI at SCP level; e.g. from OPEN to CLOSE (without any impact on the “physical” position
of the electrical switching device).
HMGA Horizontal Measurement Graphical Area
Human Machine Interface
HMI Can be DS Agile OI (Operator Interface) or C26x LCD (Local Control Display) or LEDs,
Mosaic...
LX-4 GTW/EN LX/C57a

HSR High Speed auto-Reclose, i.e. first shot of an AR cycle
Hyper Text Mark-up Language
HTML
Used as standard for formatting web display.
HV High Voltage (for example 30 kV to 150 kV)
I/O Input/Output
ICD IED Capability Description
IEC International Electro-technical Commission
Intelligent Electronic Device
IED Global term covering a whole range of microprocessor-based products capable of data
collection and information processing.
Inter-Range Instrumentation Group standard format B. This is an international standard for
IRIG-B
time-synchronisation based on an analogue signal.
Invalid state of a Double Point:
JAMMED Occurs when the 2 associated digital inputs are still in state 0 after a user- settable time-delay,
i.e. when the transient state “motion” is considered as ended.
Kbus (Kbus Courier) Term used to designate the Courier protocol on a K-Bus network (similar to RS422)
L/R Local / Remote
When set to local for a given control point it means that the commands can be issued from that
L/R Control Mode
point, else in remote control are issued for upper devices.
Legacy Bus
Generic name of Legacy or field networks and protocols used to communicate between C26x
L-BUS
(Legacy Gateway function) and IED on field bus. Networks are based on (RS232,) 422, 485.
Protocols are IEC 60850-5-103 (T103 or VDEW), Modbus.
LC Fibre optic snap-on connector, IEC 61754-20-compliant, for high density connection.
LCD Liquid Crystal Display on the C26x front panel HMI
Ladder Diagram, one of the IEC 1131-3 programming languages (language used to define
LD
configurable automations).
Logical Device, defined in IEC 61850 as: An entity that represents a set of typical substation
LD
functions.
LHMI Front panel Local HMI
Logical Node
LN
Defined in IEC 61850 as an entity that represents a typical substation function.
LOC Local Operator Console, dedicated to maintenance operations
LSB Least Significant Bit
LSP Load Shedding Pre-selection
LV Low Voltage
The Media Access Control address is a unique 48-bit hardware address assigned to every
MAC address
network interface card. Usually written in the form 01:23:45:67:89:ab
MC Modular Controller
Miniature Circuit Breaker. In the SCE configuration, its position is associated with the tap
MCB
changer.
Management Data Input/Output
MDIO
A standard driven, dedicated-bus approach that is specified in IEEE802.3
MEAS Values acquired through digital or analogue inputs (with value, state, and time stamp)
Metering Values computed depending on the values of digital or analogue inputs during variable periods
(non-tariff) of time (time integration).
Values computed depending on the values of digital or analogue inputs during variable periods
Metering
and dedicated to energy tariff metering. These values are provided by dedicated “tariff
(tariff)
computers” which are external to the control system.
MIDOS connector Alstom 28-pin terminal block used for CT/VT acquisition
GTW/EN LX/C57a LX-5

MMS Manufacturing Message Specification (ISO 9506)
Communication protocol used on secondary networks with IEDs or with a SCADA RCP. There
Modbus
are 2 versions: standard MODICON and Alstom.
Term used in DS Agile SCE to encompass all electrical HV devices: switchgear, transformers,
Module
motors, generators, capacitors, …
Transient state of a Double Point
Occurs when the two associated digital inputs are momentarily in state 0 (e.g. position
MOTION
indication when a switching device is operating). The acceptable duration of the transient state
is user-settable.
MPC Protection Module for Controller
Merging Unit
Interface device which takes signals from the instrument transformer sensors and performs
MU digital signal processing to generate and distribute output sampled value streams according to
IEC 61850-9-2LE standardised definitions for communication with substation IEDs and
controllers.
MV Medium Voltage or Measurement Value
MVAR Mega Volt Ampere Reactive
NBB Numerical BusBar protection
NC Normally Closed (for a relay/contact)
Non-Conventional Instrument Transformers
New generation of captor-based, for example using light diffraction under an electric field,
NCIT
CT/VTs, without spires, that provide direct voltage and current numerical values to the
communicating IEDs.
NO Normally Open (for a relay/contact)
One Box Solution
Controller that provides protection & control functions with local HMI. Mainly intended for use in
OBS substations up to distribution voltage levels, although it may also be used as backup protection
in transmission substation. Likewise the OBS may be applied to the MV part of a HV substation
that is being controlled by the same substation control system.
OI Operator Interface
Object Linking and Embedding
OLE
OLE is a Microsoft specification and defines standards for interfacing objects.
OMM Operating Mode Management
OLE for Process Control
OPC OPC is a registered trademark of Microsoft, and is designed to be a method to allow business
management access to plant floor data in a consistent manner.
Sum of time periods under which a primary device is running whilst carrying energy, e.g. circuit
Operation hours
breaker is in Close state and the current is not null.
Open System Interconnection
OSI ISO standard that splits and defines communication in 7 layers : physical, link, network,
transport, session, presentation, application.
OWS Operator WorkStation (DS Agile OI)
OSI Physical Layer: The physical layer provides for transmission of cells over a physical
PHY
medium.
Programmable Logic Control: Includes PSL and ISaGRAF
PLC Within the PLC-programs are defined the configurable control sequences or automations used
by DS Agile IEDs and Gateway (ISaGRAF only).
PPC Power PC, chip on the CPU270 board (MPC8270VR)
PRP Parallel Redundancy Protocol (defined in IEC 62439-3:2010)
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
LX-6 GTW/EN LX/C57a

Remote Control Centre: computer or system that is not part of the substation control system.
RCC
RCC communicates with and supervises the DS Agile system using a protocol.
Remote Control Point
Name given to the device or part used to remotely control several bays or substations. Usually
RCP
associated with Remote/Local substation control. It is a SCADA interface managed through the
Telecontrol BUS. Several RCPs can be managed with different protocols.
RedBox PRP Redundancy Box
When set for a control point it means that the commands are issued from an upper level and
Remote Control Mode
are not allowed from that point.
Remote HMI is a client of the substation HMI server. The client may provide all or part of
Remote HMI
functions handled by the substation HMI.
Read Inhibit, output that indicates the availability of an analogue output (e.g. during DAC
RI
processing time).
Registered Jack-45
RJ-45
An 8-pin female connector for 10/100 Base-T Ethernet networks.
Root Mean Square
RMS
Average value of a sinusoid that is used for calculations.
Short for remote monitoring, a network management protocol that allows network information
to be gathered at a single workstation. Whereas SNMP gathers network data from a single
type of Management Information Base (MIB), RMON 1 defines nine additional MIBs that
RMON provide a much richer set of data about network usage. For RMON to work, network devices,
such as hubs and switches, must be designed to support it. The newest version of RMON,
RMON 2, provides data about traffic at the network layer in addition to the physical layer. This
allows administrators to analyze traffic by protocol.
Recommended Standard 232
RS-232
A standard for serial transmission between computers and peripheral devices.
Standard for serial interfaces that extends distances and speeds beyond RS-232 capability.
RS-422
Intended for use in multipoint lines.
Standard for serial multipoint communication lines. RS485 allows more nodes per line than
RS-485
RS422
Régime Spécial d’Exploitation
RSE
French grid function to indicate that there are works in progress on an HV feeder.
RSVC Relocatable Static Var Compensator.
RTC Real Time Clock
Remote Terminal Unit
RTU Standalone controller that acquires data and transmits it to RCP or SCADA. Typically it is the
C26x-Standalone. The RTU is attached to the T-BUS.
Single Attached Node (defined by IEC 62439-3). Unlike DANP, such an IED requires a
SAN
REDundancy Box to send the messages over two separate networks.
SAN Singly Attached Node (PRP unaware)
Site Acceptance Test
SAT
Validation procedures performed on site with the customer.
Site-Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands issued from the RCP;
SBMC
moreover, some of its digital points and measurements (defined during the configuration
process) are no longer sent to the RCP (they are “automatically” suppressed).
Select Before Operate
Control made of two steps, selection and execution. The selection step returns a feedback. It
SBO can be used to select a circuit before execution of the command. Commands are included in a
protocol frame between the Operator Interface and the BCU and sent over wired outputs to the
switching device (e.g. DO select with DI Select, then DO execute).
S-BUS Station Bus, federal network between DS Agile devices.
SCADA Supervisory Control And Data Acquisition, equivalent to RCC.
GTW/EN LX/C57a LX-7

scd Description file extension (in SCE)
SCE System Configuration Editor
SCL System Configuration Language (IEC 61850-6) for substation automation
Substation Control Point
Name given to the device or part used to control locally several bays or substations. Usually
SCP
associated with Remote/Local substation control. It normally refers to DS Agile’s Operator
Interface.
SCS Substation Control System
SCSM Specific Communication Service Mapping
SCT Single Counter
Sequence of Event Recorder: combines SOE with accurate Time synchronisation and
SER
Maintenance facilities over Ethernet communications.
Defined in IEC 61850 as an entity that provides services to clients or issues unsolicited
Server
messages.
Analogue setpoints are analogue outputs delivered as current loops. Used to send instruction
Setpoints (analogue)
values to the process or auxiliary device.
Digital values sent on multiple parallel wired outputs. Each wired output represent one bit of the
Setpoints (digital) value. Digital setpoints are used to send instruction values to the electrical process or to
auxiliary devices.
Sequential Function Chart
SFC
IEC 61131-3 programming language (used to define configurable automation)
Small Form-factor Pluggable transceiver
SFP Hot-pluggable transceiver used for both telecommunication and data communications
applications.
Single Input or System Indication:
Binary information that does not come from an external interface, but is related to an internal
SI
state of the controller (time status, hardware faults…) or the result of an inner function (AR, …)
PSL or ISaGRAF.
SIG Status Input Group (idem MPS)
SINAD Signal-plus-Noise-plus-Distorsion to Noise-plus-Distorsion ratio, in dB
SIT Status Input Double Bit (idem DPS)
Simple Network Management Protocol: protocol governing network management and
SNMP
monitoring of network devices and their functions.
SNTP Simple Network Time Protocol
SOE Sequence Of Events, i.e. the event list
SP Single Point
SPS Single Point Status
SPC Single Point Control
SPI Step Point Indication (same as TPI)
Switch Redundancy Protocol, PRP Ethernet switch board fitted in H38x Ethernet switch and in
SRP
C26x BCU.
Structured Text
ST
An IEC 61131-3 programming language to define configurable automation.
STP Shielded Twisted Pair.
Substation controller Bay controller used at substation level
Suppression A binary information belonging to a bay in SBMC mode is automatically suppressed for the
(Automatic) remote controller. However changes of state are indicated locally, at SCP level.
A binary information can be suppressed by a command issued by an operator. No subsequent
Suppression (Manual) change of state on a “suppressed information” can trigger any action such as display, alarm or
transmission.
LX-8 GTW/EN LX/C57a

SWitch for Dual homing
SWD
C26x controller's board acting as an Ethernet switch on a redundant Ethernet star network.
SWitch Redundant
SWR
C26x controller's board acting as an Ethernet switch on a redundant Ethernet ring network.
SWitch Unit
SWU
C26x controller's board acting as an Ethernet switch on a single Ethernet network.
T10x Term used to designate IEC 60870-5-10x protocols (x= 1, 3, 4)
TBC / TBD To Be Completed / Defined
Telecontrol Bus, generic name of networks and protocols used for communications between
DS Agile Gateway or the C26x Telecontrol Interface function and the RCP. Networks use
T-BUS
RS232, RS485, or Ethernet (T104). Protocols are IEC 60850-5-101 (T101) or MODICON
Modbus.
True Contact
TC A double counter is acquired on two contacts. One is called the true contact (TC), the other is
the complemented contact (CC). Normally these contacts have complementary states.
TCIP Tap Changer In Progress
Total Demand Distortion, similar to the THD but applied to currents and with a rated current (In)
TDD
used as reference.
TG Telecontrol Gateway
THD Total Harmonic Distortion, sum of all voltage harmonics.
TM Tele-Measurement (remote measurement)
TMU Transducerless Measurement Unit
Interlocking algorithm, based on the evaluation of topological information on the switchgear
Topological interlocking arrangement in the HV network, the type of switchgear and its location, as well as defined rules
for controlling this type of switchgear (e.g. power supply continuity).
Tap Position Indication (for transformers).
TPI
Frequently acquired via a Digital Measurement.
Tele-Signalling
TS
Logic position transmitted by a remote signal
Utility Communications Architecture
UCA
Communications standard mainly used in the US
Unit Per Impulse
UPI Counter parameter used to convert a number of pulses into a measurement value. Both data
(integer and scaled floating point) are in a common class UCA2 accumulator.
Universal Time Co-ordinates (or Universal Time Code)
UTC
UTC replaces GMT and it is identical.
VdBS Versioned data Base System, SCE-generated databag ready for download.
VDEW German subset of the IEC 60870-5-103 protocol.
VMGA Vertical Measurement Graphical Area
Voltage level Set of bays in which plants and devices operate at the same voltage (e.g. 275 kV).
Voltage Transformer
Basically the device connected to the electrical process used to extract a voltage
VT
measurement. By extension part of a device (C26x) that receives this AC value & converts it to
a numerical measurement value. VTs are wired in parallel.
Wide-Area Control Unit
WACU
High-level controller
WTS Windows Terminal Server, Microsoft’s remote desktop connection.
Phase-neutral analogue values received from the "wye"(also known as “star”) winding
WYE MV
connections of a transformer .
GTW/EN LX/C57a LX-9

LX-10 GTW/EN LX/C57a

Alstom Grid
© - ALSTOM 2014. All rights reserved.

Information contained in this document is
indicative only. No representation or warranty
is given or should be relied on that it is
complete or correct or will apply to any
particular project. This will depend on the
technical and commercial circumstances. It is
provided without liability and is subject to
change without notice. Reproduction, use or
disclosure to third parties, without express
written authority, is strictly prohibited.
Alstom Grid Worldwide Contact Centre
www.alstom.com/grid/contactcentre/
Tel: +44 (0) 1785 250 070
www.alstom.com

GTW EnM C57b Compressed

Uploaded by

Copyright:

Available Formats

GTW EnM C57b Compressed

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GTW EnM C57b Compressed

Uploaded by

Copyright:

Available Formats

Gateway

System version: 5.0.5

INTRODUCTION GTW/IT EN/C57a

SAFETY AND HANDLING GTW/SA EN/C57

FUNCTIONAL DESCRIPTION GTW/FT EN/C57

HARDWARE GTW/HW EN/C57

CONNECTION GTW/CO EN/C57

COMMUNICATIONS GTW/CT EN/C57

INSTALLATION GTW/IN EN/C57

ADJUSTMENTS GTW/AJ EN/C57

LOGIC DIAGRAMS GTW/LG EN/C57

APPLICATION GTW/AP EN/C57b

HUMAN INTERFACE GTW/HI EN/C57

MAINTENANCE GTW/MF EN/C57

PROBLEM ANALYSIS GTW/PR EN/C57

RECORD SHEET GTW/RS EN/C57

TECHNICAL DATA GTW/TD EN/C57

GLOSSARY GTW/LX EN/C57a

Refer to the System Release Notes for new features.

2 INTRODUCTION TO ALSTOM'S DS AGILE GATEWAY MANUAL 4

3 INTRODUCTION TO DS AGILE GATEWAY 6

GTW/EN IT/C57a IT-1

IT-2 GTW/EN IT/C57a

GTW/EN IT/C57a IT-3

2 INTRODUCTION TO ALSTOM'S DS AGILE GATEWAY MANUAL

• two voltage levels within one DS Agile System, or

2.1 CHAPTER DESCRIPTION

IT-4 GTW/EN IT/C57a

Communications Chapter (CT)

GTW/EN IT/C57a IT-5

3 INTRODUCTION TO DS AGILE GATEWAY

• Transmission of remote indications from the system to the control centre.

IT-6 GTW/EN IT/C57a

3.2 GATEWAY ENVIRONMENT

Figure 1: DS Agile Gateway environment

GTW/EN IT/C57a IT-7

IT-8 GTW/EN IT/C57a

4 COPYRIGHTS & TRADEMARKS 6

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS 7

GTW/EN SA/C57 SA-1

SA-2 GTW/EN SA/C57

GTW/EN SA/C57 SA-3

2.1 HEALTH AND SAFETY

2.2 EXPLANATION OF SYMBOLS AND LABELS

2.3 INSTALLING, COMMISSIONING AND SERVICING

Equipment operating conditions

Fibre optic communication

SA-4 GTW/EN SA/C57

GTW/EN SA/C57 SA-5

4 COPYRIGHTS & TRADEMARKS

SA-6 GTW/EN SA/C57

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS

GTW/EN SA/C57 SA-7

SA-8 GTW/EN SA/C57

3 DS AGILE GATEWAY MANAGEMENT 5

6 LEGACY BUS IEC 60870-5-104 MASTER ACQUISITIONS 18

7 ISAGRAF REDUNDANCY CLUSTER 21

GTW/EN FT/C57 FT-1

FT-2 GTW/EN FT/C57