Professional Documents
Culture Documents
GTW Enm C6p
GTW Enm C6p
Technical Manual
GTW/EN M/C6p
DS Agile Gateway & WACU Technical Manual
CONTENTS
This guide gives instructions for installation, commissioning and operation of the DS Agile
Gateway & WACU. 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
GE Grid Solutions technical sales office and request the necessary information.
Any agreements, commitments, and legal relationships and any obligations on the part of
GE Grid Solutions, including settlement of warranties, result solely from the applicable
purchase contract, which is not affected by the contents of the guide.
Depending on when the system is installed or upgraded, some of the hardware components
described in this manual may be no longer available. Please check currently approved
hardware in the latest release.
INTRODUCTION
GTW/EN IT/C6P
DS Agile Gateway & WACU Introduction
Contents
1 INTRODUCTION 3
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.
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 such as the process bus Ethernet network. 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.
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:
GTW/EN SA/C6P
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
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.
2 SAFETY
Warning:
This Safety Section should be read before commencing any work on the equipment.
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.
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.
GTW/EN FT/C6P
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
4 COMMUNICATION LAYER 9
4.1 Telecontrol bus 9
4.2 Station bus 12
4.3 Loss of communication 12
1 INTRODUCTION
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
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.
Acquisition DLL:
IEC 61850-8-1 SBUS agency
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).
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
SNTP Clients
Which synchronises
through Legacy Bus
Legacy IEDs
S1046ENa
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.
IRIG-B
SNTP servers
System Master Clock
S1047ENa
SBMC mode,
Taking control.
Note:
The "Taking Control" command cannot be used in conjunction with the Substation L/R mode per bay.
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.
4 COMMUNICATION LAYER
DS Agile Gateway has two different types of communications:
SCADA
Telecontrol bus
DS AGILE GTW
Station bus
(IEC61850)
IEC61850 devices
Figure 4: Communications
Front Front Front Front Front Front Front Front Front Front Front Front Front Front Front Front
end 1 end 2 end 3 end 4 end 1 end 2 end 3 end 4 end 1 end 2 end 3 end 4 end 1 end 2 end 3 end 4
IP interfaces
Redundant
link/interface
Unique Unique Unique Unique
IP address for IP address for IP address for IP address for
main main redundant redundant
Main protocol 1 Main protocol 2 Redundant protocol 1 Redundant protocol 2
T104 T104 T104 T104
protocol 1 protocol 2 protocol 1 protocol 2
for for for for
Client 1 Client 2 Client 1 Client 2
Active Standby
Gateway Gateway
S1093ENa
Priorities
Each received STARTDT signal activates the corresponding client connection. There is no minimum “active”
time for a connection: If 2 or more clients try to simultaneously interrogate the Gateway, the last STARTDT
signal to be received will determine which connection remains active.
Note:
This function is totally independent from the Local/Remote Taking Control function.
5 SBUS ACQUISITION
If server is connected with the same database version the DS Agile Gateway subscribes to the data defined
in its database.
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:
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:
Gateway A Gateway B
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:
Note: ISaGRAF automation is allowed in IEC/IEC Gateways. Refer to the next section.
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:
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.
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.
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:
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.
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.
Standby
WACU
Redundant
WACU
Link dedicated to redundancy,
managed by RTX
Redundant 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
Caution:
The ISaGRAF/RTX features are only available with DS Agile WACU.
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 function receives the communication and redundancy states of both active
and standby units. It can use that information in its ISaGRAF scheme logic to determine whether to send a
switchover command.
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 the installation of RTX 2011 on both WACUs: RTX 2011 is a real-time extension for
the Windows 32-bit platform. The RTX 2011 software transforms the MS Windows general purpose
operating system (GPOS) into a real-time operating system (RTOS) in which all WACU real-time processes
have priority over Windows processes.
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).
8 GROUP PROCESSING
A group is a logical OR, AND, NOR or NAND combination of Binary Inputs (BIs) or groups.
Only SPS/DPS datapoints can be used as inputs of a group. These datapoints can originate from:
SET
RESET
INVALID
A datapoint can belong to several groups. When its state INVALID or UNKNOWN, it can be computed as:
SET
RESET
INVALID
This is defined in the database, using the SCE software.
Special cases
SUPPRESSED inputs are not taken into account in the group's resulting state.
If an input defined as SBMC-dependent originates from a bay in SBMC mode, the group uses its SBMC
forced state (defined in the datapoint's profile) in its calculation.
A group's output is processed as an SPS datapoint.
It is time-stamped with the date / time of the last datapoint that changed the group's output status.
Note:
Contrary to Group SPS managed by the C26x, a Group SPS managed by the Gateway CANNOT be substituted, forced
nor suppressed.
Input processing
The binary inputs states are taken into account as follows:
Single Point Status treated in a group as
SET, FORCED SET, SUBSTITUTED SET SET
RESET, FORCED RESET, SUBSTITUTED RESET RESET
INVALID, SELFCHECK FAULTY, TOGGLING, UNKNOWN INVALID or SET or RESET (configurable)
Not processed. (Group calculated without the
SUPPRESSED
datapoint)
Note:
Whatever the selected operand, if a group contains at least one "invalid" input, the state of the Group SPS is invalid.
A group is time-stamped with the date / time of the last datapoint that last changed the group status.
A group SPS can be used as an input into an ISaGRAF scheme.
Caution:
A group SPS computed by a Gateway can be sent to any upper level
protocols: Upper Station Bus network or SCADA.
IT CANNOT BE SENT TO THE LOWER STATION BUS NETWORK.
9 EVENT LOGS
The DS Agile Gateway can manage a log of the SPS and DPS datapoints that it transmits to a SCADA or to
the upper level of an IEC/IEC gateway.
Note:
The log does not include SMBC- nor FSS-blocked datapoints.
A new .csv log file is generated every day, except on days when no event occurred.
Its name follows the following structure: gtw_log_YY_MM_DD.csv. Its content is plain UTF8-encoded text.
Datapoint logging is automatically enabled when the Gateway software is installed.
If the default installation path of the Gateway software (C:\Program Files\ALSTOM\DCS\Gateway) was
kept, the folder containing the log files is C:\Program Files\ALSTOM\DCS\Gateway\LogTS.
The total disk space allotted to the log files is fixed at 100 MB. When this size limit is reached, the oldest
daily file is deleted.
Each log entry is a line of text structured as follows:
DD:MM:YYYY hh:mm:ss;label;value;validity
where:
the date and time are those of the time of transmission of the datapoint to the SCADA, using the
Gateway's local time
label is a text string with a maximum length of 256 characters, structured as follows:
Substation_Name | Voltage_Level | Bay_name | Module | datapoint_name
GTW/EN CO/C6P
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
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.
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:
Figure 1: RJ 45 connections
1 2 3 4 5
DCD RxD TxD DTR GND
6 7 8 9
DSR RTS CTS RI
To connect a SCADA simulator or a Network spy you can use a null modem cable plugged to a serial port
wired as follows:
9 1
18 16 19 10
GTW/EN CT/C6P
DS Agile Gateway & WACU Communications
Contents
4 MODBUS PROFILE 36
4.1 Introducing Modbus 36
4.1.1 Device address field 36
4.1.2 Function code field 36
4.1.3 Data field 36
4.1.4 Error check field 37
4.2 Slave responses 37
4.2.1 When the slave answers 37
4.2.2 Exception Responses Codes 37
4.3 Serial transmission mode 38
4.4 Modbus Functions 38
4.4.1 Supported functions 38
4.4.2 General format of Modbus functions 39
4.4.3 Modbus Data Addresses 39
4.5 Function 01 / 02: Read Coil Status – Read Input Status 40
4.6 Function 03 / 04: Read Holding Registers / Input Registers 41
4.6.1 Signed normalised coding 41
4.6.2 Unsigned normalised coding 41
4.6.3 Natural coding 42
4.7 Function 05: Force Single Coil 42
4.8 Function 08: Diagnostic [Sub-function 0 only] 43
4.9 Function 15: Force Multiple Coils 43
5 DNP3 PROTOCOL 45
5.1 Profile 45
5.2 Implementation table 47
5.3 “On-line” Quality bit management: 51
6 OPC PROTOCOL 54
6.1 Implementation 54
6.2 OPC Standard layer 57
6.2.1 OPCServer object 57
6.2.2 OPCGroup object 59
6.3 OPC server Alstom specificities 61
6.3.1 Historisation mechanism 61
6.3.2 State inversion 61
6.3.3 Conversion of a double TS (system side) in two TS (OPC side) 61
6.3.4 Conversion of two simple TS (OPC side) in a double TC (system side) 61
Communications with legacy IEDs (IEC 60870-5-101 master and IEC 60870-5-104 master)
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.
K Structured
K 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
C Number of repetitions on non acknowledge frame
C Maximum time between information frame and controlling station acknowledgement.
Cause of transmission
(System-specific parameter)
K One octet K Two octets (with originator address = 0)
Note:
Following a Reset Process command, the controlled station has two possible behaviours depending on
register key Reset_Process_Hard:
1 if Reset_Process_Hard is set to 0 only the gateway restarts (soft restart)
2 if Reset_Process_Hard is set to 1 the PC restarts (hard restart)
N <106>: = Delay acquisition command C-CD-NA-1
File transfer
(station-specific parameter)
K <120>: = File ready F-FR-NA-1
K <121>: = Section ready F-SR-NA-1
K <122>: = Call directory, select file, call file, call section F-SC-NA-1
K <123>: = Last section, last segment F-LS-NA-1
K <124>: = Ack file, ack section F-AF-NA-1
K <125>: = Segment F-SG-NA-1
K <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
Spontaneous transmission
(Station-specific parameter)
K Spontaneous transmission
General interrogation
(System or station-specific parameter)
K Global
K Group 1 K Group 7 K Group 13
K Group 2 K Group 8 K Group 14
K Group 3 K Group 9 K Group 15
K Group 4 K Group 10 K Group 16
K Group 5 K Group 11
K Group 6 K Group 12 Addresses per group have to be defined
K global
K group 1 K group 3
K group 2 K group 4
Clock synchronisation
(Station-specific parameter)
N Clock synchronisation
Notes:
The controlling station cannot synchronize the system (including the controlled station).
When the controlling station sends the controlled station a clock synchronisation message, the clock
synchronisation response is positive or negative depending on the configuration.
The controlled station does not change its time following a Clock synchronization command.
The controlled station reports the change of hour by sending a clock synchronisation message (ASDU
103) to the controlling station, as Class 1 data, with a spontaneous (3)cause of transmission.
The clock Synchronisation message may be sent before each event (this is configurable in the
Windows Registry).
Command transmission
(Object-specific parameter)
K Direct command transmission K Select and execute command
K Direct set point command transmission K Select and execute set point command
C C-SE ACTTERM used
K No additional definition
K Short pulse duration (duration determined by a system parameter in the outstation)
K Long pulse duration (duration determined by a system parameter in the outstation)
K Persistent output
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
(Object-specific parameter)
N Threshold value
N Smoothing factor
N Low limit for transmission of measured value
N High limit for transmission of measured value
Parameter activation
(Object-specific parameter)
N Act/Deactivation of persistent cyclic or periodic transmission of the addressed object
Test procedure
(Station-specific parameter)
K Test procedure
File transfer
(Station-specific parameter)
File transfer in monitor direction
K Transparent file (for disturbance files)
N Transmission of disturbance data of protection equipment
N Transmission of sequences of events
N Transmission of sequences of recorded analogue values
Background scan
(Station-specific parameter)
K Background scan
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 polling for data reports.
SCADA does not acknowledge a data emission within a specific time after a settable number of
repetitions (3 by default).
Communications with the controlled station must be re-initialised by the controlling station that
terminated the frame repeat process without successfully transmitting the frame (i.e.: the frame time-
out period x 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.
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.
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.
The controlled station reports the change of all time by sending a clock synchronisation message
(ASDU 103) to the controlling station, as Class 1 data, with a cause of transmission spontaneous (3). This
case is optional (configurable in the Windows Registry).
The controlled station reports any time correction by sending a clock synchronisation message (ASDU 103)
to the controlling station, as Class 1 data, with a cause of transmission spontaneous (3).
For 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 the Windows Registry.
For control commands: Activation termination is returned to the controlling station to signal the end of
a control sequence. This is not configurable in the Windows 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.
2.8.12 REDUNDANCY
Both devices have 3 redundancy types.
3 Line Redundancy – e.g. – 2 lines for the one protocol
For Gateway, Switchover on received frame:
The switchover from the active link to the passive link is performed when a frame is received. The
response differs depending on the type of frame received on the Stand-by Link:
68 0c 0c 68
08 Control byte
01 Link Address
01 ASDU1 (Single-point information without time tag)
81 Number of objects = 1 DI, SQ=1
14 COT = 20 (general interrogation)
01 Common address
09 DI 9 (Information Object Address)
00 state OFF, Valid
[xx yy] checksum and stop byte
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 ASDU1 (Single-point information without time tag)
83 Number of objects = 3 DI, SQ=1
14 COT = 20 (general interrogation)
01 Common address
07 DI 7 (Information Object Address)
00 state OFF, Valid
01 state ON, Valid for DI 8 (padding)
00 state OFF, Valid for DI 9
[xx yy] checksum and stop byte
Flag SQ = 2:
If the Gateway detects in the address range one or several gaps longer than the Max Gaps_DP setting, it
will, depending on the number and size of those gaps, select the most appropriate action and choose to
process the frame in either SQ=0 or SQ=1 mode.
When datapoints are assigned SCADA addresses in DS Agile SCE, these addresses must
be grouped per datapoint type (SPS, DPS, CPT, etc.) in unique ranges that must not
overlap. There must not be a mix of addresses for different types of datapoints
anywhere in the mapping.
Should the Gateway read a datapoint interspersed within the address range of another
datapoint type, its data may be lost.
Recommendation:
Before beginning to configure the database, define and reserve for each datapoint type a unique address
range. For instance set object address to: 0 to 1000 for CPT, 1001 to 2000 for DPC, 2001 to 3000 for DPS,
etc., keeping aside enough free addresses to cover future needs.
Alternatively, set the address format (information object length protocol attribute) to address on 8 bits.16
bits and use the first part of the address to group each address range (e.g. 1.xxxx for CPT, 2.xxxx for DPC
etc.).
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
K Supported and certified by KEMA
C Configurable
R Could be received, but not managed.
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>
Cause of transmission
(System-specific parameter)
N One octet K Two octets (with originator address)
Length of APDU
(System-specific parameter)
The maximum length of APDU is 253 (fixed)
File transfer
(station-specific parameter)
N <120>: = File ready F-FR-NA-1
N <121>: = Section ready F-SR-NA-1
N <122>: = Call directory, select file, call file, call section F-SC-NA-1
N <123>: = Last section, last segment F-LS-NA-1
N <124>: = Ack file, ack section F-AF-NA-1
N <125>: = Segment F-SG-NA-1
N <126>: = Directory F-DR-TA-1
Type
Cause Of Transmission
ID
20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45* 46 47
36 41
<1> M_SP_NA_1 X X X X X X
<2> M_SP_TA_1
<3> M_DP_NA_1 X X X X X X
<4> M_DP_TA_1
<5> M_ST_NA_1 X X X X 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 X
<10> M_ME_TA_1
<11> M_ME_NB_1 X X X X X
<12> M_ME_TB_1
<13> M_ME_NC_1 X 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
Type
Cause Of Transmission
ID
<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
<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 X
<46> C_DC_NA_1 X X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X X
<50> C_SE_NC_1 X 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 X
<59> C_DC_TA_1 X X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X X
<63> C_SE_TC_1 X 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 X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X X X
<103> C_CS_NA_1 X X X X X
<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
<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
Type
Cause Of Transmission
ID
<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.
Spontaneous transmission
(Station-specific parameter)
K Spontaneous transmission
General interrogation
(System or station-specific parameter)
K Global
K Group 1 S Group 7 S Group 13
S Group 2 S Group 8 S Group 14
S Group 3 S Group 9 S Group 15
S Group 4 S Group 10 S Group 16
S Group 5 S Group 11
Information Object Addresses assigned to each
S Group 6 S Group 12
group must be shown in a separate table
Clock synchronisation
(Station-specific parameter)
K Clock synchronisation
Note:
Clock synchronization commands are supported but the Controlled Station does not change its clock following a T104
command.
See section 2.8.8 Clock Synchronisation for details.
Command transmission
(Object-specific parameter)
K Direct command transmission K Select and execute command
K Direct set point command transmission K Select and execute set point command
K C-SE ACTTERM used
K 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
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
(Object-specific parameter)
N Threshold value
N Smoothing factor
N Low limit for transmission of measured value
N High limit for transmission of measured value
Parameter activation
(Object-specific parameter)
N Act/Deactivation of persistent cyclic or periodic transmission of the addressed object
Test procedure
(Station-specific parameter)
K Test procedure
File transfer
(Station-specific parameter)
File transfer in monitor direction
N Transparent file (only for disturbance file)
N Transmission of disturbance data of protection equipment
N Transmission of sequences of events
N Transmission of sequences of recorded analogue values
Background scan
(Station-specific parameter)
K Background scan
S Ethernet 802.3
N Serial X.21 interface
N Other selection from RFC 2200
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, selecting a second file is not possible.
If a loss of communication with the SCADA occurs while a transfer is in progress, upon communication
recovery the process must be restarted from the beginning.
A .SOE104 file is a binary file that contains only the ASDUs (no other information is present in the file).
Caution:
If the directory is full, while the oldest file is locked by the SCADA (file selected and not
acknowledged) it is not possible to rename the new .tmp_ready to .SOE104. In this case,
if this situation lasts a very long time, the number of .tmp_ready files can increase,
without limit. Such a situation should not happen if the SCADA operates correctly.
From the dll's point of view, there is 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 send it to the SCADA with no date).
3.9.1 EVENT
The following types of information are to be configured at the controlled station to be Event:
K Single point information with or without time tag (on change)
K Double point information with or without time tag (on change)
K Step position information with or without time tag (on change)
K Measured value, normalised with or without time tag (on change)
K Measured value, scaled with or without time tag (on change)
K Measured value, floated with or without time tag (on change)
K Integrated totals with or without time tag (on change)
3.9.2 STATIC
The following types of information are to be configured at the controlled station to be Static:
Event data can be time-tagged with the 7 bytes time-stamp (CP56Time2a), giving minutes and milliseconds
within the hours, day, month, year.
The invalid bit in the time-stamp is set when the time source is not available.
The controlled station reports the change of hour by sending a clock synchronisation message (ASDU 103)
to the controlling station, as Event data, with a cause of transmission spontaneous (3).
The controlled station reports the change of time by sending a clock synchronisation message (ASDU 103)
to the controlling station, as Event data, with a cause of transmission spontaneous (3). This case is optional
(configurable in the Windows Registry).
The controlled station reports any time correction by sending a clock synchronisation message (ASDU 103)
to the controlling station, as Event data, with a cause of transmission spontaneous (3).
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.
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.
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
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.
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 ).
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
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.
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.
Response:
Function Point Point
Slave Force Data Force Data CRC CRC
Code Address Address
Address (H) (L) (L) (H)
= 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.
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.
The query message specifies the points addresses to be controlled. Addresses may start from 0 to 65535.
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
Address (H) (L) (L) (H)
= 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.
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
………………………………………………
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 Always Sometimes Configurable
controls)
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
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
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Function Quality Codes Function Qual Codes
Obj Var Description
Codes (dec) (hex) Codes (hex)
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
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
16-Bit Delta Counter Change Event
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
32-Bit Delta Counter Change Event
22 7
with Time
16-Bit Delta Counter Change Event
22 8
with Time
23 0 Frozen Counter Event - All Variations 1 06,07,08
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Function Quality Codes Function Qual Codes
Obj Var Description
Codes (dec) (hex) Codes (hex)
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
16-Bit Frozen Delta Counter Event
23 4 1 06,07,08 129,130 17,18
without Time
32-Bit Frozen Counter Event with
23 5
Time
16-Bit Frozen Counter Event with
23 6
Time
32-Bit Frozen Delta Counter Event
23 7
with Time
16-Bit Frozen Delta Counter Event
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
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Function Quality Codes Function Qual Codes
Obj Var Description
Codes (dec) (hex) Codes (hex)
32-Bit Frozen Analog Event with
33 3
Time
16-Bit Frozen Analog Event with
33 4
Time
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Function Quality Codes Function Qual Codes
Obj Var Description
Codes (dec) (hex) Codes (hex)
101 3 Large Packed Binary-Coded Decimal
No Object (Cold Restart)
No Object (Warm Restart)
No Object (Delay Measurement
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 - - - -
(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.
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]
VALID 1 - - - - - - - VALUE
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
SELFCHECK FAULT 0 - - - - - - - X
UNKNOWN 1 - 1 - - - - - X
OVERRANGE 0 - - - - - - - X
UNDEFINED 0 - - - - - - - X
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
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
For a good interoperability, the Quality is configured by the SCE for each quality
IEC 61850-8-1.
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.
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.
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:
<<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()
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.
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).
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).
7.1 GENERAL
The following ACSI conformance statements shall be used to provide an overview and details about a device
claiming conformance with ACSI:
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.
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
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.
System definition
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.)
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
Two octets
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)
Three octets
Cause of transmission
(system-specific parameter, all configurations that are used are to be marked ‘X’)
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
Remote initialisation
between Reset User ASDU’s
Cyclic data transmission
(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)
Read procedure
Spontaneous transmission
(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)
Spontaneous transmission
Link state between Controlling and Controlled Station
global
group 6 group 12
Counter General interrogation
(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
Clock synchronisation
(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)
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 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.
Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is used)
No additional definition
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.
Threshold value
Smoothing factor
Test procedure
File transfer
(station-specific parameter), mark ‘X’ if function is used)
File transfert in monitor direction
Transparent file
Transparent file
Background scan
(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)
Background scan
Acquisition of transmission delay
(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)
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)
Station Initialisation
Station initialisation consists in 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 polling for data reports.
Communications failure
Communications with the controlled station must be re-initialised by the controlling station when 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 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.
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 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).
General Interrogation
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.
Clock synchronisation
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:
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.
Command transmission
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.
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.
Three octets
Cause of transmission
(system-specific parameter, all configurations that are used are to be marked ‘X’)
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
Process information in monitor direction
(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
Remote initialisation
between Reset User ASDU’s
Cyclic data transmission
(station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Read procedure
Spontaneous transmission
(station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Spontaneous transmission
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, short floating point number M_ME_NC_1, M_ME_TC_1 and M_ME_TF_1
General interrogation
(system or station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Global
Group 5 Group 11
Group 6 Group 12
Information object addresses assigned to each group must be shown in a separate table.
Clock synchronisation
(station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
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.
Command transmission
(object -specific parameter, mark each type ID ‘X’ if it is used)
No additional definition
Threshold value
Smoothing factor
Test procedure
File transfer
(not implemented)
Background scan
(station-specific parameter, mark each type ID ‘X’ if it is used in the standard direction)
Background scan
Definition of timeouts
Parameter Default value Remarks Selected value
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
Redundant connections
Number N of redundancy group connections used
9.1.3 LIMITS
Reverse mode is not implemented.
The following ASDU are not implemented:
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).
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.
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.
If the IED has accepted the time synchronization, the time stamp is considered as synchronous, not
synchronous otherwise.
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.
If the IED has accepted the time synchronization, the time stamp is considered as synchronous, not
synchronous otherwise.
BitString 32-bits : not supported.
Note:
Should IEDs in the network require this information, the QOC/QU field of the ASDU used to indicate the type of
command signal can be set using a Windows Registry key. See Adjustments chapter.
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).
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).
Key:
GTW1_L1N: Ethernet link #1 between GTW_1 and IEC 60870-5-104 Ethernet network #1
(IEC 60870-5-104_1).
GTW1_L2N: Ethernet link #2 between GTW_1 and IEC 60870-5-104 Ethernet network #2
(IEC 60870-5-104_2).
GTW2_L1N: Ethernet link #1 between GTW_2 and IEC 60870-5-104 Ethernet network #2
(IEC 60870-5-104_1).
GTW2_L2N: Ethernet link #2 between GTW_2 and IEC 60870-5-104 Ethernet network #2
(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).
9.4.1.1 NOMINAL CASE 1: CONNECTION BETWEEN AN ACTIVE GATEWAY AND AN ACTIVE IED
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.
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.
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.
TCP OK TCP OK
Active StandBy Active StandBy
T104 stopped T104 stopped
STARTDT.act
STARTDT.con
T104 started
TESTFR.act
TESTFR.con
TCP connection
StandBy Active
Active close
TCP NOK
active open TCP OK
T104 stopped
STARTDT.act
STARTDT.con
T104 started
S1026ENa
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.
TCP OK TCP OK
Active StandBy Active StandBy
T104 stopped T104 stopped
STARTDT.act
STARTDT.con
T104 started
Startdt.act
T0
Testfr.con
StandBy Active
TCP NOK
T0
STARTDT.act
STARTDT.con
T104 started
Active Open (TCP)
TCP OK
S1027ENa
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.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.6 FAILURE CASE 6: DISCONNECTION OF IED 2 LINK (IED2_LN ) FROM THE NETWORK
Initial context:
Each link is healthy.
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.
GTW_1 is connected to IED_2 by a TCP link.
Failure Event: Failure of IED2_LN
There is no effect on the IEC 60870-5-104 connection between GTW_1 and IED_1.
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.
CommSt(IED_y)
ProtSt(IED_y)
LinkSt(IED_y)
These datapoints are not redundant. They can be configured for display on a DS Agile Operator Interface in
the State, Event, FSS and Alarm viewers as well as sent to a SCADA gateway for dispatching.
Each gateway also updates a redundancy datapoint on the SCADA link:
RedSt()
CommSt
CommSt(IED_y) gives the state of the active T104 communications link between the local gateway and the
IED_y.
CommSt(IED_y) has 2 attributes:
State
The DP’s state is set, i.e. OK, if the "Startdt" to the IED is established between the gateway and the
IED_y.
The DP’s state is reset, i.e. NOK, otherwise.
Validity
The DP’s validity is always OK on the gateway.
ProtSt
ProtSt(IED_y) gives the state of the Active or Passive T104 communications link between the local gateway
and the IED_y.
ProtSt(IED_y) has 2 attributes:
State
The DP’s state is set, i.e. OK, if the "TestFR" (or "Startdt") to the IED is established between the
gateway and the IED_y.
The DP’s State is reset, i.e. NOK, otherwise.
Validity
Validity is always OK on the gateway.
LinkSt
LinkSt(IED_y) gives the state of Ethernet link between the local gateway and the IED_y.
LinkSt(IED_y) has 2 attributes:
State
The DP’s state is set, i.e. OK, if the result of the ping command to the IED is established between
the gateway and the IED_y.
The DP’s state is reset, i.e. NOK, otherwise.
Validity
The DP’s validity is always OK on the gateway.
RedSt
RedSt() gives the redundancy state (active/standby) of the gateway.
RedSt() has 2 attributes:
State
The DP’s state is set, i.e. ON, if the gateway is receiving the controls and setpoints from an OI
client or a SCADA gateway.
The DP’s state is reset, i.e. OFF, otherwise (standby mode).
Validity
The DP’s validity is always OK on the gateway. It can be NOK on the receiving gateway if the
communications link between the redundant gateways is down.
Note:
This function is only effective if the IEDs have a buffering capability for the frames that they transmit.
This feature ensures that no event indicated by a buffering-capable IED is lost during a switch-over between
redundant gateways.
Events received from an IED are transferred from the Active gateway to the Standby gateway in 4 steps:
1 The IED sends a T104 frame containing one or several data points (state, quality, time-stamp) that the
gateway does not acknowledge immediately.
2 The Active gateway forwards this frame to the Standby gateway without making any changes.
3 The Standby gateway responds by sending a frame acknowledgement to the Active gateway.
4 The Active gateway then sends an acknowledgment to the T104 IED.
This way no IED event is acknowledged by the Active gateway before it has been received by both
gateways.
Communications between the active and the Standby gateways use the lower SBUS link.
Note:
The process is totally transparent for the user and no specific configuration is required, except for the fact that the
gateways must be in an IEC 61850/IEC 61850 configuration, in addition to managing an IEC 60870-5-104 master
network.
Both active and Standby gateways forward the datapoint information on to the upper network or SCADA link.
Once an event has been acknowledged by the gateway, the IED erases it from its buffer. If it has not
received an acknowledgement before a communications loss, the IED transmits the frame again when the
connection is re-established.
Note:
Control acknowledgement frames are ignored by the Standby gateway.
Note:
Memory is dynamically allocated, without any software-imposed limitation. It is protected against overflow by the limit
that the IEC 60870-5-104 standard imposes on IEDs to stop sending frames when “k” frames are already awaiting
acknowledgement.
Note:
When both the Standby and the Active gateways restart, some overlapping between the two General Interrogations
may occur. This is of no consequence.
Switch-Over
All the datapoints received by the Active gateway have been forwarded and acknowledged.
Before the switch-over:
GTW1 is the Active gateway. All the datapoints have been transmitted to the upper network.
GTW2 is the Standby gateway.
When the switch-over occurs, GTW2 becomes active.
GTW2 sends a GI (General Interrogation) over the T104 link and receives all the datapoints’ states.
If GTW1 is still alive, but has switched to standby, GTW1 asks GTW2 to send a GI.
If GTW2 has already sent a GI, the request is postponed until after the end of the current GI, when all
the datapoints’ states are received: The 2 GIs are sent in succession.
If no GI is currently running on GTW2, the GI requested by GTW1 is sent by GTW2 to the T104 IEDs.
While the IEDs are answering the GI, all frames are sent to the Active gateway (GTW2)
GTW2 forwards these frames to GTW1, which acknowledges them.
The Standby gateway, GTW1, stores the datapoints’ states in its kernel database, and forwards them to the
upper network.
Note that usually, all these datapoints’ states will have already been sent to the upper network by the Active
gateway.
The Active gateway (GTW2) acknowledges the frames to the IEDs when it receives the corresponding
acknowledgements from the Standby gateway (GTW1).
9.4.3.3.6 Failure modes
During Switch-Over
Some datapoints received by the Active gateway have not yet been forwarded to the Standby gateway.
In that case, datapoints not transmitted to the Standby gateway have not been acknowledged.
Upon switch-over, i.e. when the Active gateway switches to standby mode, the newly Standby gateway
erases all its pending buffers. Therefore it stops sending frame acknowledgements. This ensures that all
events waiting for acknowledgement will be kept in the IED’s buffer and will be resent when the IED receives
a new General Interrogation.
Failure of lower SBUS link between gateways
The SBUS link is used to transmit T104 frames from the active to the Standby gateway.
If this link fails, the transfer of T104 frames from the Active gateway to the Standby gateway is stopped but:
Communications must carry on between the Active gateway and the IEDs connected to the T104
network
This failure is indicated by the Active gateway to the upper network and displayed/alarmed on SCADA
or OI depending on configuration.
In this case, all the buffers on the Active gateway are erased and the frames received from the IEDs are all
acknowledged.
The path from the T104 IEDs to the upper network is fully operational using only the Active gateway.
Note:
A restart of the gateways while the link between them is down has no negative impact on the DS Agile OI display of
events:
Its SBUS agency would automatically eliminate a datapoint in “unknown” state if it also receives a valid event from the
other Gateway.
An “unknown” state is only taken into account if both gateways send the same datapoint with that state.
If the link between the Active gateway and the switch fails, but the switch is otherwise operational, the
Active gateway switches to maintenance mode, and the previously Standby gateway becomes Active-
Standalone (no redundancy).
If the switch itself is faulty, then both gateways switch to maintenance mode and the communications
between the SCADA/Upper SBUS (DS Agile OI) and the T104 IEDs are down. Use redundant
switches to prevent this risk.
Failure of the IEC 61850 upper network detected by the Active gateway
The Active gateway does not immediately detect when it is disconnected from the upper network.
During the time between the disconnection and its detection, frames received from IEDs are still transmitted
to the Standby gateway and acknowledged by the Active gateway to the IED.
However, no frames are lost because they are still being transmitted to the upper network by the Standby
gateway.
Failure of the Active gateway
When the Active gateway fails, the Standby gateway detects the Active gateway’s failure and takes over as
Active gateway.
Although the new Active gateway is not yet connected to the T104 IEDs, it does not set all its datapoints to
"unknown", as would a standalone gateway. The new Active gateway tries to reconnect to the IEDs. If it fails
to reconnect to some or all IEDs, all the datapoints produced by any non-reconnected IEDs are set to
"unknown".
GTW/EN IN/C6P
DS Agile Gateway & WACU Installation
Contents
6 OTHER OPERATIONS 24
6.1 Add access rights to standard user accounts 24
6.1.1 Folder Configuration 24
6.1.2 Registry configuration 26
6.2 Add/Remove Remote access to Non-Administrator users 28
6.2.1 Remote desktop access management 28
6.2.2 Adding a non-administrator remote user 29
6.2.3 Delete a non-administrator remote user 30
6.2.4 Troubleshooting 30
6.3 Serial Communications 32
6.4 OdTimeService settings 32
1.1 CYBER-SECURITY
Caution:
Before starting to configure the PC and install applications, you should be
thoroughly familiar with the DS Agile Network and System Security Guide
(DS Agile/EN CS).
Before installing the DS Agile software, a number of pre-requisite steps are needed in order to properly
secure the system.
These steps are documented in the DS Agile Network and System Security Guide.
The Network and System Security Guide is available both as a chapter of the DS Agile technical manual and
as a stand-alone document. This guide describes the security-related steps that must be implemented
BEFORE, DURING and AFTER the installation and adjustments of DS Agile software applications.
Before moving on to installing the DS Agile software, make sure these pre-requisite steps are executed.
Caution:
Run an anti-virus scan of the PC hard disk and memory using an up-to-
date anti-virus program run from a USB drive.
4 If you want to, choose a different storage folder for the Gateway's log files, and then click Next.
5 Read the license agreement, select I accept the agreement and click Next.
Note:
The logs will be activated whichever compatibility version you select.
6 Select DS Agile 5.0.5 and onward (Pidd 3.0.5) and click Next.
7 In the Select Destination Location dialog box define the installation folder (the default installation
folder is C:\Program Files\DCS\Gateway).
8 By default a full installation is proposed: IEC 61850 SBUS Protocol (compulsory) and all SCADA
protocols (optional). Using the tick boxes select the required components or clear the unnecessary
components.
9 In the Select Start Menu Folder dialog box choose where you want the program's shortcuts.
10 Select whether or not the Gateway software should start automatically and click Next.
Note:
Further adjustments have to be made to Windows configuration to enable the Gateway to automatically start. See
section 3 Automatic Start configuration (option).
11 In the Select Additional Tasks dialog box select whether or not to create a desktop icon.
12 Check that the proposed settings are the correct ones and click Install.
13 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.
14 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:
15 If this is the first time that the Gateway software is installed, then Microsoft Visual C++2008
Redistributable should be installed:
16 Click Next.
17 Read the License Terms, then tick I have read and accept the license terms. and click Install.
18 Wait while the setup files are being extracted and installed.
19 Click Finish.
20 The installation is complete. Unselect the Launch DS Agile Gateway tick box and click Finish in the
two following cases:
you do not want to immediately launch the application
it is the 1st installation
Note:
The presence/absence of .dll files depends on which protocols have been installed:
4 Enter the password for the DCS_User account and confirm it.
5 Click OK.
6 In the Advanced tab, clear the Require users to press Ctrl-Alt-Delete tick box:
Note:
When the Gateway is set to start automatically when the PC starts, the Windows session is locked immediately: the
Gateway is launched but a password will be needed to unlock the session and access the Gateway (as well as any
other Window applications/settings).
ALSTOM
Programs
About
Shut Down
C: is reserved for XP Embedded operating system; this disk is protected by Enhanced Write Filter
(EWF) to avoid writing on flash disk.
5.2.2 REGISTRY
To create the DS Agile Gateway registry, launch the DS Agile Gateway software and install a database.
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".
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
6 OTHER OPERATIONS
2 Select Properties
7 Click OK.
All the accounts in the group "DSAgile Users" are now allowed to modify the selected folder and its
subfolders.
Windows 7:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ALSTOM\DCS
Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS
3 In the Remote Desktop panel of the System Properties window, tick Allow users to connect remotely
to this computer, and then click Select Remote Users... The Remote Desktop User window is
displayed.
Note:
As indicated in the Remote Desktop Users window, only users that are not members of the Administrators group need
to be manually added. Members of the Administrators group, such as DCS_Master, are automatically granted remote
access.
2 Enter the user name, in this example, DCS_User, and then click Check Names.
3 Click OK. The remote user is added to the list in the Remote Desktop Users window:
6.2.4 TROUBLESHOOTING
If, after applying the above procedure to allow users to connect remotely, they are still denied access, it may
either be due to the Remote desktop having been manually disabled during when the machine was
"hardened" or that the Windows Firewall is not configured to permit remote desktop access
(see DS Agile/EN CS - Network & System Security Guide) .
3 Double-click Services.
The column Startup Type indicates whether the start-up of the Terminal Services is Disabled, Manual or
Automatic. For remote desktop access to be available, it must set to Automatic.
Enabling Terminal Services
To set the Startup Type to Automatic:
1 Right-click Terminal Services and select Properties.
2 In the Terminal Services Properties window, set Startup type to Automatic:
3 Click Apply, and then restart the PC for the changes to take effect.
3 In the Exceptions tab-pane of the Windows Firewall window, make sure that Remote Desktop is
selected.
5 Click OK.
Caution:
If you do not have to install the AEE application, revert here to the Network
& System Security Guide (DS Agile/EN CS), DS Agile Post-Installation
Process section to complete the configuration.
7.1.1.1 CONFIGURATION
Note:
In the BIOS Setup Utility:
- To SELECT/ENTER a MENU/ITEM: press “Enter”.
- To move the cursor between items: press the arrows
- To return to previous menu: press “ESC”.
Note:
As displayed in screenshot, USB
keyboard and USB mouse devices stay
enabled and useable.
Cyber-security recommends that all USB
ports be disabled. In that case, the PS/2
keyboard/mouse on the extension board
must be used. Refer to Cyber-Security
guide, DS Agile/EN CS, for information
on how to disable all USB ports on a
DS Agile A301 PC.
05
Press F10.
06
Note:
The DS Agile A301 will automatically
reboot.
06 Click No.
Caution:
The RTX Realtime
Subsystem must be in
“Stopped” mode,
otherwise update 5
can’t be installed.
Note:
If this windows appears, click Yes in
order to stop the RTX Realtime
Subsystem.
Close the RtsServer Console if it is
launched.
S1069XXa
Depending on the project's requirements and the number of Ethernet networks, several NIC boards may be
fitted to add Ethernet ports (BUS, SCADA T104, SCADA IEC61850, T104Master…).
In the procedure given below, the top Ethernet port is used for RTX-managed redundancy (device name:
“Intel® 82574L Gigabit Network connection #2”).
The bottom Ethernet port is used for the SBUS network connection (device name: “Intel® 82574L Gigabit
Network connection”).
Note:
The same operation must be done for
the redundant WACU.
Caution:
Restart the DS Agile A301 WACU in order to ensure that the above changes
take effect.
RtxTcpIp.ini
rdnpars.txt
By default the current path is C:\Program Files\ALSTOM\RDN_GTW.
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)
Note:
By default, the “RtxTcpIp.ini” configuration file
should be delivered upon WACU installation and
can be found at the following path:
C:\Program Files\ALSTOM\RDN_GTW\
RtxTcpIp.ini
Note:
For the redundant WACU, the “RtxTcpIp.ini”
configuration file has to be set with the following IP
and MAC addresses:
- IPAddr=192.168.10.2 (for the secondary WACU)
- EA=xxxxxxxxxxxx (of the redundant WACU
“Intel® 82574L Gigabit Network connection” used
for RTX redundancy link)
Note:
The RTXServer log window automatically opens
when the RTX drivers start.
It is possible to see Ethernet board well
configuration.
Note:
No RTSS process is currently running because the
WACU is not launched.
Note:
When both redundant WACUs are running, it is possible
to see the active RTSS processes and RTDLLs.
Under “C:\” ; type:
C:\Program Files\IntervalZero\RTX\ bin\rtsskill
GTW/EN AJ/C6P
DS Agile Gateway & WACU Adjustments
Contents
Select the Default Properties tab and match the configuration as below:
In the Default Launch Permissions frame add Everyone and INTERACTIVE entries and deny launch for
every items
In the Default Configuration Permissions frame add Everyone and INTERACTIVE and give full control
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 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
3 In the "My Computer Properties" dialog box select the "COM Security" tab
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"
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
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.
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:
02
4.1 PROCEDURE
This procedure applies to DS Agile A300/A301 PCs, with the Windows XPE operating system.
1 Install a H152 board in each gateway PC, without the Ethernet 3*RJ45 optional kit: Follow the
procedure described in the Installation section of the MiCOM H15x manual, ref. H15x/EN GL.
2 Connect the H152’s RJ45 port to a free RJ45 port on the PC.
3 Set the IP addresses for each board’s RJ45 link:
The first three byte fields of the IP address are set using the Switch Manager software.
The last byte field is set by jumpers, see the Settings section of the MiCOM H15x manual,
ref. H15x/EN GL.
4 Install the Gateway software version gtw-7.2.13.0-build1 on each PC: Follow the procedure described
in the Installation chapter of the Gateway & WACU manual, ref. GTW/EN M.
5 Launch the Windows Registry Editor: Click Start, then enter Regedit in the search box.
6 Find HKLM\SOFTWARE\DCS\GATEWAY\Tg\Main, and then set the registry key
maintenance_if_dcnx_ethernet to 1. This will cause the Gateway to switch to maintenance mode if
SBUS communications are lost.
7 Find HKLM\SOFTWARE\DCS\GATEWAY\T104M, and then add the following registry keys:
IPAddrHxxxSynchro: set its type to REG_SZ (string type) and enter the IP address of the local
H152 board. Do so on each gateway, with a different IP address.
IPAddrPrimarySynchro: set its type to REG_SZ (string type) and enter the IP address of the local
primary gateway’s interface (set using the Windows Control Panel > Network Connections > Local
Area Connection properties on the primary gateway PC). Do so for the secondary gateway.
TimeOutBeforeUnknown: set its type to DWORD and enter the timeout value that the Gateway
must use to setwait before it sets datapoints to UNKNOWN if when an IED (and its backup) cannot
be connected after a gateway switchover. If this key does not exist, the default value is 120
seconds. Do so on each gateway.
System
HMI
Station Bus network
Switch 1 Switch 2
Redundant
optical ring
H H
Primary LAN1 1 1 LAN1 Secondary
Gateway GTW1 5 5 GTW2 Gateway
(server) LAN2 2 2 LAN2 (client)
IP@1 IP@2 IP@3 IP@4
T104M network
IED
S1124ENa
You need to define four different IP addresses for the four RJ45 ports illustrated in the figure above:
Reference Description Value (example) Where to define it Registry key to be added
On GTW1: IP address
IP@1 In GTW1 PC, Network On both GTW1 and GTW2 PCs:
on the gateway to
“LAN2” RJ45 192.168.2.56 Connections in the set IPAddrPrimarySynchro to
communicate with the
on GTW1 Windows Control Panel this IP address
local H152
IP@2 Switch manager/jumpers On GTW1: set
On GTW1: IP address
H152 RJ45 on 192.168.2.12 on board (not in the IPAddrHxxxSynchro to this IP
for the H152 board
GTW1 Control Panel) address
IP@3 Switch manager/jumpers On GTW2: set
On GTW2: IP address
H152 RJ45 on 192.168.2.13 on board (not in the IPAddrHxxxSynchro to this IP
for the H152 board
GTW2 Control Panel) address
On GTW2: IP address
IP@4 In GTW2 PC, Network
on the gateway to
“LAN2” RJ45 192.168.2.55 Connections in the N/A (no registry configuration)
communicate with
on GTW2 Windows Control Panel
local H152
3 persistent output
4..8 reserved for standard definitions of the IEC 60870-5-101 ed. 2 companion standard
(compatible range)
* May be used when the attributes (for example pulse duration, etc.) of the addressed control function
are fixed (predefined) in the controlled station and not selected by the controlling station.
** May be used to control functions with fixed attributes, which are predefined in the controlled station.
The QuFieldCommandType key is optional. If it is not present, it is considered set to its default value,
i.e. 0.
Similarly, if an out-of-range value, i.e. >31, is entered, the key is also considered set to its default value,
i.e. 0.
Procedure
1 Open the Registry Editor (open the Start menu, select Run, then enter regedit and click OK).
2 Scroll down to HKEY_LOCAL_MACHINE\SOFTWARE\DCS\GATEWAY\T104M
3 Double-click the DWORD QuFieldCommandType
Note:
When a command is sent, a trace event is recorded. This event is then displayed in the DebugView module, it shows
which Qu value was read.
GTW/EN LG/C6P
DS Agile Gateway & WACU Logic Diagrams
Contents
1 INTERNAL AUTOMATION 3
2 COMMAND PROCESSING 5
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]
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
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)
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.
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.
2 COMMAND PROCESSING
The SCADA's commands are translated into IEC 61850-8-1 controls:
DS Agile
G
SCADA T System
W
Commands Controls
By configuration (dependencies), it is defined which SCADA controls are accepted and refused.
GTW/EN AP/C6P
DS Agile Gateway & WACU Application
Contents
2 REQUIREMENTS 4
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).
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)
Electrical topology (Site): the Gateway's behaviour depends on substation and bay mode facilities.
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):
S0387ENb
A relation defined on an object O1, not spare, and linked to a spare object O2, is considered as a
relation with no link:
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.
protocol type (Usual protocol / V35 ACKSYS-MCX): use the default value. 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
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)
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.
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:
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”.
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
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".
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
add an IED from object entry available either at ‘Gtw T101 master’ level or at ‘Gtw T104 master’ level
set the IED attributes
Figure 12: Setting the general attributes of a legacy IED in a T101 network
Figure 13: Setting the general attributes of a legacy IED in a T104 network
T101 and T104: the datapoint is identified by either of the following combinations of its attribute
values:
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.
(1)
(2)
(3)
(4)
S1119ENa
T101M
(1)
(2)
(3)
(4)
T104M
(1)
(2)
(3)
(4)
(5)
S1118ENa
(1)
(2)
(3)
(4)
(5)
(6)
(7)
S1116ENa
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)
(2)
When setting a T101 SCADA network, some specific attributes available for the protocol must be updated
(Protocol and SOE tabbed panes):
(6) link address length (1 byte / 2 bytes)
(7) link address (range [1, 65534], step 1)
(8) 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)
(9) ASDU common address length (range [1, 65534], step 1)
(10) ASDU common address (range [1, 65534], step 1)
(11) 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))
(12) frame max length (range [1, 255], step 1)
(13) cause of transmission length (Address on 8 bits / Address on 16 bits)
(14) MV periodic cycle (range [0 s, 65534 s], step 1 s)
(15) binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
(16) background scan cycle (range [0 s, 65535 s], step 1 s)
(17) 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.
(18) 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
(19) SOE file base address: this attribute is significant only if SOE file support is not set to No.
(20) 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.
(21) nb max of SOE files (range [1,99], step 1): this attribute is significant only if SOE file support is
not set to No.
(22) 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.
(23) Buffer overflow address (No / Yes): this attributes defines the address of the buffer overflow
datapoint sent to SCADA.
(24) 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.
(25) 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.
(26) Balanced mode (No/Yes): this attribute defines balanced mode if set to yes.
(27) 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)
(28) 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 26: Setting the protocol and SOE attributes of a T101 SCADA network
(1)
When setting a DNP3 SCADA network, some specific attributes available for the protocol must be updated
(Protocol tabbed pane):
(29) link address (range [1, 65534], step 1)
(30) SPS/DPS class (1 / 2 / 3)
(31) MV class (1 / 2 / 3)
(32) Counter class (1 / 2 / 3)
(1)
(2)
(3)
(4)
(1)
(2)
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 protocol
Note:
If you define several T104 protocols (maximum 4), make sure that each TCP/IP address is unique.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
(24)
(25)
Figure 30: Setting the protocol and SOE attributes of a T104 SCADA network
(1)
When setting a MODBUS SCADA network, some specific attributes available for the protocol must be
updated (Protocol tab):
(1) link address (range [1, 247], step 1)
(2) parity (None / Odd / Even) used at communication level.
(1)
(2)
(1)
Figure 33: 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 34: Setting the specific attributes of a CDC Type II SCADA network (obsolete)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
Figure 36: Setting the OPC values attributes of an OPC SCADA network
(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 37: Setting the OPC quality attributes of an OPC SCADA network
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 39: 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)
(2) ASDU common address (range [1, 65534], step 1)
(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)
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)
Configuration rules and checks
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.
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 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:
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
T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
Modbus
(12)
(13)
OPC
(14)
(15)
(16)
(17)
Once added, SCADA DPS address attributes must be set at SCE level:
(1) short name of the address used for internal SCE identification
(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.
(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): 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
(11) Inversion (No / Yes): indicates that the datapoint value needs to be inverted before transmission
(12) object address - index
For Modbus protocol:
(13) Inversion (No / Yes): indicates that the datapoint value needs to be inverted before transmission
(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)
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)
Note: Handling the counters (freeze, reset, etc....) affects only the SCADA; the counters are NOT modified in the
C26x
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
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 (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.
T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
DNP3
(7)
(8)
Modbus
(9)
(10)
OPC
(11)
Once added, SCADA SPC address attributes must be set at SCE level:
(1) short name of the address used for internal SCE identification
For T101/T104 protocols:
(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:
(5) object address [0..65535]
(6) 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.
For Modbus protocol:
(7) object address - register
For OPC protocol:
(8) OPC address: indicates the name’s tag for OPC (limited to 48 characters). The character “.”
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)
Once added, SCADA DPC address attributes must be set at SCE level:
(1) short name of the address used for internal SCE identification
For T101/T104 protocols:
(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 (range [0 s, 65535 s], step 1 s): time-out DS Agile system has to acknowledge the
selection.
For DNP3 protocol:
(5) object address [0..65535]
(6) 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.
For Modbus protocol:
(7) object address - register
For OPC protocol:
(8) OPC address: indicates the name’s tag for OPC (limited to 48 characters). The character “.”
indicates that the name is hierarchical.
(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)
Once added, SCADA SetPoint address attributes must be set at SCE level:
(1) short name of the address used for internal SCE identification
For T101/T104 protocols:
(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) 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:
(8) object address [0..65535]
(9) SCADA execute order type (Select execute / Direct execute): this attribute defines which type of
sequence is used by the SCADA to send a control to the datapoint.
For OPC protocol:
(10) OPC address
T101/T104
(1)
(2)
(3)
(4)
(5)
(6)
(7)
DNP3
(8)
(9)
Modbus
OPC
(10)
Once added, SCADA MPS address attributes must be set at SCE level:
(1) short name of the address used for internal SCE identification
For T101/T104 protocols:
(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 57: General attributes of an MPS address for the T101/T104 protocols
(10)
(11)
(12)
(13)
Figure 58: General attributes of an MPS address for the DNP3 protocol
(14)
Figure 59: General attributes of an MPS address for the Modbus protocol
(15)
(16)
Figure 60: Defining the general attributes of MPS address for the OPC protocol
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 61: Adding a bypass synchrocheck address to a SCADA SPC/DPC address (example for a SCADA DPC
address)
Figure 62: Realising the SCADA addressing of a datapoint (example for a bay SPS 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)
(1)
(2)
(3)
(4)
(5)
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.
Operating mode MPS (4): the available states of this datapoint are:
IEC 61850-8-1 addressing Available states
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.
IEC 61850-8-1 addressing Available states
TGDIAG.SyncSt ‘RESET’: Not synchronised
Automatic at datapoint creation ‘SET’: Synchronised
(1)
(2)
SCADA communication status SPS (1): fixed to ‘SET’ state if communication with the SCADA is
operational.
IEC 61850-8-1 addressing Available states
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.
IEC 61850-8-1 addressing Available states
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.1.1 INTRODUCTION
Global Substation Local/Remote mode (Station Bus level)
A substation can be in remote or local control mode.
Remote mode means that the substation is controlled from the Remote Control Point (RCP), via a Gateway.
No control commands can be sent from the Substation Control Point (SCP) level, except if the target bay is
in SBMC mode.
Local mode means that the substation is controlled from the DS Agile Operator Interface (Substation Control
Point). The control commands issued from the RCP are not taken into account by the system, they are
refused.
Some control commands, defined during the configuration stage, can be independent of the substation
control mode: It means that they can be issued from the SCP or RCP, regardless of the current L/R control
mode. For details about the configuration of this dependency attribute, refer to the sub-sections below.
For details about definition of Local/Remote for substation, refer to the C26x application chapter
(C26x/EN AP).
Substation Local/Remote mode per bay (Station Bus level)
This feature is similar to the Global Substation L/R mode described above, except that each bay can be
independently switched to Remote or Local mode.
Remote mode means that the bay is controlled from the Remote Control Point (RCP), via a Gateway. Control
commands sent by the Substation Control Point (SCP) are not taken into account by the BCU, except if the
bay is in SBMC mode.
Local mode means that the bay is controlled from the DS Agile Operator Interface (Substation Control Point).
The control commands issued from the RCP are not taken into account by the system, they are refused.
Some control commands, defined during the configuration stage, can be independent of the substation
control mode: It means that they can be issued from SCP or RCP, regardless of the current L/R control
mode. For details about the configuration of this dependency attribute, refer to the sub-sections below.
For details about definition of Local/Remote for substation, refer to the C26x application chapter
(C26x/EN AP).
Note:
The global substation L/R mode and the substation L/R mode per bay are mutually exclusive. When the L/R mode per
bay is declared in a database, the global L/R mode MUST be set to REMOTE by default and must not be switchable.
Note:
These settings are identically applicable to the Global Substation L/R mode and the Substation L/R mode per bay.
(1) Bay mode dependency: Applicable to Bay L/R mode at C26x level.
No: The datapoint will INDEPENDENT of the Bay L/R mode.
Yes: The datapoint will be DEPENDENT on the Bay L/R mode.
(2) Bay control uniqueness dependency: Only significant if Control uniqueness is set to Bay level at
substation level.
No: The command does not need to be unique, i.e. it can be sent from a different while it is already
being processed.
Yes: The command must be unique, i.e. if it is received from another source while it is already
being processed the second instance will be refused.
(3) Local Substation dependency: Applicable to both Global substation L/R mode and Substation L/R
mode per bay.
Command from SCADA is accepted: The command is ACCEPTED even when it is sent from the
RCP while the substation L/R mode is LOCAL.
Command from SCADA is refused: The command is REFUSED when it is sent from the RCP while
the substation L/R mode is LOCAL.
(4) Remote substation dependency: Applicable to both Global substation L/R mode and Substation
L/R mode per bay.
Command from OI is accepted: The command is ACCEPTED even when it is sent from the SCP
while the substation L/R mode is REMOTE.
Command from OI is refused: The command is REFUSED when it is sent from the SCP while the
substation L/R mode is REMOTE.
Figure 66: Setting local/remote dependencies attributes for an SPC datapoint (example given at bay level for
generic SPC)
Configuration of local/remote dependencies for datapoints declared directly under the substation or
a voltage level
(1) Substation control uniqueness dependency: Only significant if Control uniqueness is set to
Substation level.
No: The command does not need to be unique, i.e. it can be sent from a different while it is already
being processed.
Yes: The command must be unique, i.e. if it is received from another source while it is already
being processed the second instance will be refused.
(2) Local Substation dependency: Applicable only to Global Substation L/R mode.
Command from SCADA is accepted: The command is ACCEPTED even when it is sent from the
RCP while the substation L/R mode is LOCAL.
Command from SCADA is refused: The command is REFUSED when it is sent from the RCP while
the substation L/R mode is LOCAL.
(3) Remote substation dependency: Applicable only to Global Substation L/R mode.
Command from OI is accepted: The command is ACCEPTED even when it is sent from the SCP
while the substation L/R mode is REMOTE.
Command from OI is refused: The command is REFUSED when it is sent from the SCP while the
substation L/R mode is REMOTE.
Figure 67: Setting local/remote dependencies attributes for an SPC datapoint (example given at voltage level for
a generic SPC)
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.
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
Operator Interface
(only receives SBMC
state indication)
No SBMC control
through IEC/IEC
gateway
SCADA
IEC/IEC (manages SBMC)
Gateway
Gateway
SBMC L-Bay2
SBMC L-Bay1
System Bay 2
System Bay 1
S1053ENb
Figure 68: Example of IEC 61850-8-1/IEC 61850-8-1 dual network with SCADA connected directly to the lower
network
add the datapoints SBMC SPS (1) and SBMC control SPC (2), from the contextual Objects entry
window at bay level,
(2)
(1)
Figure 69: 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.
5.2.2.2 SBMC STATE INDICATION WITH SCADA CONNECTED TO THE UPPER NETWORK
Gateway
No SBMC control
through IEC/IEC
gateway
IEC/IEC
Gateway
C26x-1 C26x-2
S1054ENb
Figure 70: Example of IEC 61850-8-1/IEC 61850-8-1 dual network with SCADA connected to the upper network
Figure 71: Defining the SBMC mode for a bay in the lower level database where the SCADA is connected to the
upper network
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 72: 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.
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.
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 73: 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.
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.
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 74: 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.
Select the IEC 61850 protocol and set the attribute Check Local/Remote to No.
Figure 75: 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
(3)
(4)
Figure 77: Adding local/remote datapoints to the substation and linking it to the "virtual" C26x
(2)
(1)
Figure 78: 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).
(1)
Figure 79: Setting SBMC dependency attributes to control datapoint (example given at bay level for a generic
SPC)
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
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".
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.
Caution:
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:
An ISaGRAF output can be used as a component of a datapoint group and a Group SPS can be used as an input into
an ISaGRAF scheme. Be careful not to create any loops.
A Group SPS can belong to a bay or a module (any module except circuit-breaker). The Gateway that
manages the bay (or the bay containing the module) computes it. It is composed of the relations that link it to
its inputs: SPS, DPS, and/or Group SPS.
A group SPS can be seen as a particular fast automation reduced to one Boolean function (gate) with one
implicit output (the group SPS itself) and inputs corresponding to each component of the group.
To add a group SPS, select the bay or module level in the electrical topology and add the group SPS from
the contextual Objects entry window.
For details on electrical topology creation, see C26x manual, Application chapter.
Figure 81: Adding a group SPS (example for a feeder at bay level)
Contrary to Group SPSs managed by the C26x, a Group SPS managed by the Gateway cannot be totally
configured as an SPS datapoint. The interlock profile configuration of its components is not taken into
account by the Gateway's Group SPS. Instead, there are additional attributes to set for the Group SPS that
are applicable to all its components ("inputs").
There are 3 attributes to set for a Group SPS managed by the Gateway:
(1) group type must be set for the group. It corresponds to the logical function (OR, AND, NOR or
NAND) applied on all the components of the group.
(2) Interpretation of invalid inputs: Defines how a component with an "INVALID" state is actually read
in the group: as ON (i.e. "set"), OFF (i.e. "reset") or as "INVALID".
(3) Interpretation of unknown inputs: Defines how a component with an "UNKNOWN" state is
actually read in the group: as ON (i.e. "set"), OFF (i.e. "reset") or as "INVALID".
Note:
A Group SPS containing at least one input read as "INVALID" takes the state "INVALID" until all its inputs are ON/OFF
(no INVALID input) again, whatever the selected group type operand.
(1)
(2)
(3)
Add the relation contains the <XXX> (1) at Group SPS level, where XXX corresponds to the
datapoint type (SPS or DPS)
(1)
a
ad
Sc
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, 127.0.0.1 in our example).
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
The attribute Check Local/Remote defined if the global Substation Local/Remote information has to be
used by an IEC61850/IEC61850 gateway. The global Substation Local/Remote xPS comes from the lower
IEC 61850-8-1 network.
Note:
Substation Local/Remote per bay can only be used in single ring Station Bus networks; it cannot be used in an
IEC 61850/IEC 61850 architecture.
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 Edit relations from the contextual menu, select the tab To, click the
item transmits: Datapoint [0..65535].
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).
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.
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 91: 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’.
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
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.
GTW/EN HI/C6P
DS Agile Gateway & WACU Human Interface
Contents
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.
Field Type: this is the equipment type: "CXXX", "HMI", "GTW", "IED"
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 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*.
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 Date: this is the date of the last change for the Digital input.
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.
Note:
The state of the Substation L/R mode per bay is not indicated here.
Simply select the desired server by selecting it in the drop-down list, and state indications about the
managed bays are displayed. They are automatically refreshed every 10 seconds, but you can also refresh
them immediately by clicking the Refresh now ! button.
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:
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.
Select the modules that you want to include in the output traces (log files):
Module Name Log contents
GENERAL Kernel and TGRCC application traces
PROT-x Protocol traces
REDUNDANCY Gateway redundancy traces
OMM Operating Mode Management: Database/DLLs loading operations
SO PACIS IEC 61850 Agency traces
Note:
In order to save memory space, select only the traces you actually need.
If you do not use DebugView, tick the box Store on File?. The output logs will be found in the folder:
C:\ProgramData\ALSTOM\DCS\Gateway\Config
C:\ProgramData\ALSTOM\DCS\Gateway\Config
W0286ENa
For each module, click the corresponding Log Level button to set which types of traces are to be included in
the log files:
(1) Decode and display the received frames (time tag and event label)
(2) Decode and display the transmitted frames (time tag and event label)
(3) Add DLL/application file information. Debugging information: Unselect this box for normal
operation.
Note:
This action doesn’t erase the log book information.
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 MF/C6P
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
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
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
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
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
2 REGISTRY
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg]
Key Format Default Min Max Modifiable Comment
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]
Key Format Default Min Max Modifiable Comment
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
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\BD]
Key Format Default Min Max Modifiable Comment
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
Value entirely controlled by the DS
Agile Gateway’s kernel
Number of the BD actually loaded
1: BD N°1
"current_bd" dword 1 1 2 N 2: BD N°2
Value entirely controlled by the DS
Agile Gateway’s kernel
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\Main]
Key Format Default Min Max Modifiable Comment
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.
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\Tg\System]
Key Format Default Min Max Modifiable Comment
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]
Key Format Default Min Max Modifiable Comment
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]
Key Format Default Min Max Modifiable Comment
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
2.4 T101
[HKEY_CURRENT_USER\Software\DCS\Te\T101]
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy]
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy\Configuration]
Key Format Default Min Max Modifiable Comment
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)
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy\FileTransfert]
[HKEY_CURRENT_USER\Software\DCS\Te\T101\Protx_COMy\FileTransfert\EventRecord]
Key Format Default Min Max Modifiable Comment
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
[HKEY_CURRENT_USER\Software\alstom\Te\T101\Protx_COMy\Port]
Key Format Default Min Max Modifiable Comment
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.
This key is created with the
default value: -1
Gives a GPT trace level. Not
"Debug" string "N" Y N N
used for DS Agile
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]
Key Format Default Min Max Modifiable Comment
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
'Activation termination'
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.
01: 'Activation termination' is
sent.
00: 'Activation termination' is
not sent.
'Activation termination'
message during a setpoint
sequence. Ac-cording to
standard, the Activation
"Flag_Act_Term_TVC" dword 1 0 1 Y Termination is not mandatory.
01: 'Activation termination' is
sent.
00: 'Activation termination' is
not sent.
[HKEY_CURRENT_USER\Software\DCS\Te\T104\port]
Key Format Default Min Max Modifiable Comment
Reserved for R&D department to test
"Debug" string "N" "Y" "N" N
T104
Reserved for R&D department to test
T104 with database of the site: First
"IP1" dword 0xFFFFFFFF 0 255 N
byte of T104 IP address if debug is
set to Y
Reserved for R&D department to test
T104 with database of the site:
"IP2" dword 0xFFFFFFFF 0 255 N
Second byte of T104 IP address if
debug is set to Y
Reserved for R&D department to test
T104 with database of the site: Third
"IP3" dword 0xFFFFFFFF 0 255 N
byte of T104 IP address if debug is
set to Y
Reserved for R&D department to test
T104 with database of the site: fourth
"IP4" dword 0xFFFFFFFF 0 255 N
byte of T104 IP address if debug is
set to Y
[HKEY_CURRENT_USER\Software\DCS\Te\TakingControl]
Key Format Default Min Max Modifiable Comment
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]
Key Format Default Min Max Modifiable Comment
Boolean that indicates if multiple coils
"support_multiple_coils" dword 1 0 1 Y
are managed or not.
Defines the maximum time (in
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.9 DNP3
[HKEY_CURRENT_USER\Software\DCS\Te\Dnp3]
[HKEY_CURRENT_USER\Software\DCS\Te\Dnp3\Protx_COMy\Configuration]
Key Format Default Min Max Modifiable Comment
"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
3 - 32 Bits Analogue Input
without Flag
4 - 16 Bits Analogue Input
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
3 - 32 Bits Analogue Change
Event with Time
4 - 16 Bits Analogue Change
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
2.10 OPC
[HKEY_LOCAL_MACHINE\SOFTWARE\DCS\protocol\OPC\svritfc]
Key Format Default Min Max Modifiable Comment
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).
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.
4 OPERATION TRACES
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.
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):
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.
6 DBGVIEW
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.
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.
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.
7 VIEWTRACE
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.
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.
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.
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.
8 INTERPRETATION OF TRACES
Note: Refer redundant specifications document for detailed information of each message type
Timestamp on the left part indicates the time when the traces in generated.
Logbook
Value : OFF
Date and Time : 07/06/2006 14:33:48:195
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.
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]
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 ()
Code Indication
0x00000002 An error occurred while initializing acquisition (client part over IEC 61850-8-1)
0x00000001 An error occurred while initializing a protocol
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
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:
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.
13 PORTMON
14 FAQ
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
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:
[18:37:55:704] [TG_RCC][Traite_TC_ACQ_Evt_UCA2] Anneau:17, Num TC:2437, Ack:36 Ack_uca: 0
[18:38:05:704] [TG_RCC][Traite_TC_ACQ_Evt_UCA2] Anneau:17, Num TC:2437, Ack:40 Ack_uca: 16
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
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.
GTW/EN PR/C6P
DS Agile Gateway & WACU Problem Analysis
Contents
2 PROBLEM IDENTIFICATION 4
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
GTW/EN RS/C6P
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
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
2 INSTALLATION
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 TD/C6P
DS Agile Gateway & WACU Technical Data
Contents
1 INTRODUCTION 2
1.1 General features 2
5 SYSTEM DEPENDABILITY 14
5.1 MTBF 14
5.2 Availability 14
1 INTRODUCTION
This document is a chapter of the DS Agile Gateway documentation. It is the chapter Technical Data (TD) of
this Product.
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.
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
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
2.8 WIRING
3.7 INSULATION
Minimum characteristics
Test Standard Conditions
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
3.8 ENVIRONMENTAL
Minimum characteristics
Test Standard Conditions
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.9 MECHANICAL
Minimum characteristics
Test Standard Conditions
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.10 SAFETY
Minimum characteristics
Test Standard Conditions
CAPIEL draft Product
Product Safety Safety document under CE mark conformity
preparation
3.12 WIRING
Minimum characteristics
The connection with the 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.
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
Tests Standard Conditions
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),
EN 55024 (2010), Meets the requirements of Performance
Radiated emission immunity
IEC 61000-4-3 (2006) + A1 Criterion A
(2007) + A2 (2010)
Electrical tests
Tests Standard Conditions
5 SYSTEM DEPENDABILITY
5.1 MTBF
Minimum characteristics
Device MTBF
Industrial PC Gateway 50,000h
Fanless embedded Gateway 345,000h @30°C,Telcordia method Issue 2
Table 3: MTBF
5.2 AVAILABILITY
Minimum characteristics
Device MTTR (in minutes)
Industrial PC Gateway 30 to 60
Fanless embedded PC Gateway 14 to 16
Table 4: Availability
GTW/EN LX/C6P
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.
Term/Acronym Description
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.
Term/Acronym Description
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.
Term/Acronym Description
Double Point Status, information derived from 2 digital inputs
DPS
Usually used for Position indication of switching devices (OPEN, CLOSE).
DPU Digital Process Unit: BCU board used to interface with switchgear control units (SCU).
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).
HBU High Break Unit: BCU board used in applications requiring high rupture capacity.
HMGA Horizontal Measurement Graphical Area
Term/Acronym Description
Human Machine Interface
HMI Can be DS Agile OI (Operator Interface) or C26x LCD (Local Control Display) or LEDs,
Mosaic...
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).
Term/Acronym Description
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
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)
Term/Acronym Description
PRP Parallel Redundancy Protocol (defined in IEC 62439-3:2010)
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
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).
Term/Acronym Description
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.
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
SCU Switchgear Control Unit used in Process Bus applications.
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.
Term/Acronym Description
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.
Sample Value Unit
SVU IEC 61850-9-2LE-compliant C26x controller's board interfacing with analogue merging units
through the substation's Process Bus.
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 for Teaming
SWT C26x controller's board acting as an Ethernet switch with hot standby redundancy between an
Ethernet network and end nodes
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
Term/Acronym Description
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 .
www.GEGridSolutions.com