easergy micom p30

Easergy MiCOM P30

IEC 60870-5-104 Protocol

Application Guide

[Communication] IEC 60870-5-104 Protocol

Schneider Electric

CONTENTS

1 SCOPE OF APPLICATION ....................................................................................................................... 5

2 INTEGRATION OF THE IEC 60870-5-104 PROTOCOL INTO EASERGY MICOM P30 ........................ 6

2.1 ETHERNET BOARD ................................................................................................................................ 6 2.2 DEVICE SETTINGS ................................................................................................................................ 6

2.2.1 Protocol settings ........................................................................................................................ 6 2.2.2 Signal and command blocking ................................................................................................... 7 2.2.3 Time synchronization ................................................................................................................. 7 2.2.4 Virtual inputs and status information ......................................................................................... 7

2.3 DATABASES ......................................................................................................................................... 7 2.3.1 Initial state .................................................................................................................................. 7 2.3.2 Creating and loading databases ................................................................................................ 8

3 IEC 60870-5-104 SOFTWARE ARCHITECTURE .................................................................................... 9

3.1 OVERVIEW ........................................................................................................................................... 9 3.2 PROGRAM OBJECTS ............................................................................................................................. 9

3.2.1 Kernel ......................................................................................................................................... 9 3.2.2 Device interface ....................................................................................................................... 10 3.2.3 IEC 60870-5-104 telecontrol lines ........................................................................................... 10 3.2.4 IEC 60870-5-104 master station bus and client ...................................................................... 10 3.2.5 IEC 60870-5-104 server .......................................................................................................... 10 3.2.6 Logic and station interlocking .................................................................................................. 10

4 ENGINEERING ........................................................................................................................................ 11

4.1 X30 STUDIO ...................................................................................................................................... 11 4.1.1 Introduction .............................................................................................................................. 11 4.1.2 Access rights............................................................................................................................ 11

4.2 ENGINEERING STEPS OF AN IEC 60870-5-104 PROJECT ...................................................................... 11 4.2.1 Profile ....................................................................................................................................... 11 4.2.2 Typicals .................................................................................................................................... 12 4.2.3 IEDs ......................................................................................................................................... 12 4.2.4 Configuration............................................................................................................................ 12 4.2.5 Parameterization ...................................................................................................................... 13

5 DATA MODEL AND LOGIC LIBRARY .................................................................................................. 23

5.1 APPROACH ........................................................................................................................................ 23 5.2 INTEGRATION INTO PROGRAM OBJECTS ............................................................................................... 23

5.2.1 Program objects with logic library ............................................................................................ 23 5.2.2 Implementation differences ...................................................................................................... 24

5.3 FORMAT OF DATA MODEL FILES ........................................................................................................... 24 5.3.1 Basic structure of data model files ........................................................................................... 24 5.3.2 Data model file for device interface ......................................................................................... 25 5.3.3 Data model file for telecontrol lines and master station bus .................................................... 26 5.3.4 Data model file for logic / station interlocking .......................................................................... 27

5.4 PROCESSING DATA MODEL FILES ......................................................................................................... 27 5.4.1 Device interface, telecontrol lines, and master ........................................................................ 27 5.4.2 Logic / station interlocking ....................................................................................................... 28

5.5 TELEGRAM PROCESSING..................................................................................................................... 29

6 FUNCTIONS OF THE LOGIC LIBRARY ................................................................................................ 30

6.1 DATA FORMATS .................................................................................................................................. 30 6.2 IMPLICIT CONVERSION ........................................................................................................................ 31 6.3 BIT FIELD ASSIGNMENT ....................................................................................................................... 32 6.4 INPUT-RELATED FUNCTIONS ................................................................................................................ 33

6.4.1 Overview .................................................................................................................................. 33 6.4.2 Negation - 'not' ......................................................................................................................... 34 6.4.3 Arithmetic operations - 'add', 'sub', 'mult', 'div', 'sqrt' ............................................................... 35 6.4.4 Polygon scaling - 'scal' ............................................................................................................. 36 6.4.5 Comparing functions - 'ifeq', 'ifne', 'ifneq', 'ifgt', 'iflt', 'iftc', 'ifntc' ................................................ 37 6.4.6 Comparing functions - 'cmpeq', 'cmpne', 'cmpgt', 'cmpge', 'cmplt', 'cmple' ............................. 38


Schneider Electric

6.4.7 Comparing functions for control state messages - 'isdef', 'istra' .............................................. 39 6.4.8 Test of quality descriptors - 'isgood', 'isbad', 'isiv', 'isnt', 'isbl', 'issb', 'isov' .............................. 40 6.4.9 Switch-on delay - 'ton' .............................................................................................................. 41 6.4.10 Switch-off delay - 'toff' .............................................................................................................. 42 6.4.11 Switch-on and switch-off delay - 'tonoff' .................................................................................. 43 6.4.12 Impulse function - 'timp' ........................................................................................................... 44 6.4.13 Timer - 'timer' ........................................................................................................................... 45 6.4.14 Cycle supervision - 'cycsup' ..................................................................................................... 46 6.4.15 Input information of select function - 'sel', 'case', 'deflt' ........................................................... 46 6.4.16 Inputs of the output function D-Flip-Flop - 'set', 'res', 'dat', 'clk' ............................................... 46 6.4.17 Inputs of the output function invalid control - 'sig', 'con' ........................................................... 46 6.4.18 Inputs of the interlocking functions - 'cmd', 'req', 'enon', 'enoff', 'send', 'conf' .......................... 46

6.5 OUTPUT-RELATED FUNCTIONS ............................................................................................................ 47 6.5.1 Overview .................................................................................................................................. 47 6.5.2 Setting the output value - 'set' .................................................................................................. 48 6.5.3 Setting the cause of transmission of the output telegram - 'settc' ........................................... 48 6.5.4 Setting data and cause of transmission - 'setcmd', 'setcon', 'settrm' ....................................... 49 6.5.5 Setting the impulse duration in commands - 'pulse' ................................................................ 50 6.5.6 Setting of quality descriptors – 'setbl', 'setnt', 'setsb', 'setiv', 'setov', 'setqds', 'setca', 'setcy' .. 50 6.5.7 Logical operations - 'or', 'nor', 'and', 'nand', 'iff', 'xor' ................................................................ 51 6.5.8 Dynamic OR operation - 'dynor' ............................................................................................... 53 6.5.9 Bitstring, bitstring of 32 bits - 'bs', 'bs32' .................................................................................. 54 6.5.10 Arithmetic functions - 'sum', 'diff', 'prod', 'quot' ......................................................................... 55 6.5.11 Threshold processing (deadband) - 'db' .................................................................................. 56 6.5.12 Deadband integrated - 'dbi' ..................................................................................................... 57 6.5.13 Average value calculation - 'avg' ............................................................................................. 58 6.5.14 Selecting function (switch) - 'swi' ............................................................................................. 59 6.5.15 Flip-flop (output Q) - 'ffq' .......................................................................................................... 60 6.5.16 Interlocking functions - 'lock', 'elock' ........................................................................................ 61 6.5.17 Invalid control - 'ivcon' .............................................................................................................. 63

6.6 STATUS INFORMATION ........................................................................................................................ 64 6.6.1 Input status information ........................................................................................................... 64 6.6.2 Output status information ......................................................................................................... 65

7 SPECIAL FUNCTIONS OF PROGRAM OBJECTS ............................................................................... 66

7.1 PRIORITY-CONTROLLED DATA TRANSMISSION ...................................................................................... 66 7.1.1 Function ................................................................................................................................... 66 7.1.2 Possibilities of engineering ...................................................................................................... 66

7.2 COMMAND PROCESSING ..................................................................................................................... 67 7.2.1 Function ................................................................................................................................... 67 7.2.2 Possibilities of engineering ...................................................................................................... 68

7.3 CHECK OF CONTROL UNIQUENESS ....................................................................................................... 68 7.4 TRANSMISSION IN REVERSE DIRECTION ............................................................................................... 68 7.5 IEC 60870-5-104 REDUNDANT TRANSMISSION .................................................................................... 69 7.6 TREATMENT OF SIGNALS REPORTED IN ACTIVE STATE ONLY (TRANSIENT SIGNALS) ................................. 69 7.7 CHATTER SUPPRESSION ..................................................................................................................... 70 7.8 SIGNAL AND COMMAND BLOCKS IN THE DATA MODEL ............................................................................ 71

8 STATION INTERLOCKING ..................................................................................................................... 72

8.1 OPERATION WITH STATION INTERLOCKING ........................................................................................... 72 8.2 CONTROL PROCEDURES WITH STATION INTERLOCKING ......................................................................... 72

8.2.1 Remote control with station interlocking .................................................................................. 72 8.2.2 Local control with station interlocking ...................................................................................... 73

8.3 SYSTEM ARCHITECTURES WITH STATION INTERLOCKING ....................................................................... 74 8.3.1 Station interlocking in central substation unit .......................................................................... 74 8.3.2 Station interlocking in field unit ................................................................................................ 75

9 CHECKING AND TEST FUNCTIONS .................................................................................................... 76

9.1 PERMANENT LOGGING FUNCTIONS ...................................................................................................... 76 9.2 CONFIGURABLE LOGGING FUNCTIONS .................................................................................................. 76

10 INTERNAL TELEGRAM INTERFACE ................................................................................................ 77

10.1 TELEGRAM FORMAT AND ENCODING .................................................................................................... 77


Schneider Electric

10.1.1 Introduction .............................................................................................................................. 77 10.1.2 Data types used ....................................................................................................................... 77 10.1.3 Cause of transmission ............................................................................................................. 78 10.1.4 Data formats ............................................................................................................................ 78 10.1.5 Quality descriptors ................................................................................................................... 79 10.1.6 Device addresses of program objects ..................................................................................... 79

10.2 TELEGRAM EXCHANGE WITH THE DEVICE ............................................................................................. 79 10.2.1 Telegrams from protection part................................................................................................ 79 10.2.2 Telegrams from control part ..................................................................................................... 80 10.2.3 Signals from the communication module to the device ........................................................... 83 10.2.4 Settings from the device for the communication module ......................................................... 84

10.3 SYSTEM TELEGRAMS OF THE COMMUNICATION MODULE ....................................................................... 84 10.3.1 Introduction .............................................................................................................................. 84 10.3.2 Telegram interface of the kernel .............................................................................................. 85 10.3.3 Telegram interface of the device interface .............................................................................. 85 10.3.4 Telegram interface of the IEC 60870-5-104 telecontrol line .................................................... 85 10.3.5 Telegram interface of the IEC 60870-5-104 server ................................................................. 88 10.3.6 Telegram interface of the IEC 60870-5-104 master station bus .............................................. 89 10.3.7 Telegram interface of the IEC 60870-5-104 client ................................................................... 90 10.3.8 Telegram interface of the logic/station interlocking ................................................................. 90


Schneider Electric

1 Scope of application

This document applies to all device types of the Easergy MiCOM P30 series and refers to the following ver-sion of the devices' communication software:

version 4.50

The version of the communication software can be verified in the device under the following address:


Schneider Electric

2 Integration of the IEC 60870-5-104 protocol into Easergy MiCOM P30

2.1 Ethernet board

Depending on the setting IEC prot. variant in function group /Parameters/Config. parame-

ters/IEC, one of the following software packages is started:

• IEC 61850 Edition 2,

• IEC 61850 Edition 1,

• IEC 60870-5-104.

The IEC 60870-5-104 communication software can be used on all redundant (REB) and not-redundant (SEB) Ethernet board variants.

The firmware for IEC 60870-5-104 is the same for all Easergy MiCOM P30 device types and is adapted to the specific device type during engineering through the database.

2.2 Device settings

2.2.1 Protocol settings

The IEC 60870-5-104 protocol settings are configured in the function group Parameters/Config. pa-

rameters/IEC.

In order to configure the protocol settings, they must first be made visible by parameter IEC60870-5-

104enable. As soon as the IEC 60870-5-104 protocol has been selected, after processing by the device,

status information on the installed databases and network parameters are displayed.

General enable USER is used to enable or disable IEC 60870-5-104 communication.

Visibility of IEC 60870-5-104

Setting of IEC 60870-5-104

Status of IEC 60870-5-104

Enabling the communication


Schneider Electric

The settings ETH COMM Mode, Block Port A/B, Block Port C and the time zone settings have the

same effect as in the IEC 61850 Edition 1 and 2 protocols.

2.2.2 Signal and command blocking

In function group /Parameters/Function parameters/Global/IEC, command blocks and sig-

nal/measurement blocks similar to those in the IEC 60870-5-103 protocol can be set:

Blocks can also be set via binary inputs by allocating the functions Command block. EXT or Sig.meas.

block EXT.

The blocking function depends on the Ethernet board configuration. Therefore, it must be defined on the Ethernet board by engineering, which telecontrol lines are to be blocked. For further details, see section 10.2.4.2.

2.2.3 Time synchronization

The settings for the time synchronization interface are configured within function group Parameters/Con-

fig. parameters/IRIGB. If parameter General enable USER is set to Yes, synchronization will be

done via the IRIG-B interface on the communication module, otherwise via SNTP.

The SNTP protocol parameters are set at the communication module; for details, see section 4.2.5.2. For synchronization via IRIG-B, no further settings are required.

2.2.4 Virtual inputs and status information

Virtual inputs are binary signals that are transmitted from the communication module to the CPU. In function group /Parameters/Config. parameters/VINP, device functions can be mapped to those 64 signals.

Furthermore, the quality of the virtual inputs VINP Input xx faulty can be processed.

Addressing of virtual inputs from an Ethernet board perspective is described in section 10.2.3.2.

The IEC 60870-5-104 protocol software assigns status information to matrix points in the device. They can be displayed and processed in the device in the following function groups:

• Operation/Cyclic measurements/Phys. state signals/VINP,

• Operation/Cyclic measurements/Log. state signals/VINP,

• Operation/Cyclic measurements/Log. state signals/MAIN,

• Operation/Cyclic measurements/Log. state signals/IEC.

The addressing of signals on the communication module is described in section 10.2.3.

2.3 Databases

2.3.1 Initial state

The IEC 61850 approach of an active and an inactive configuration database has also been adopted to the IEC 60870-5-104 protocol.

For the IEC 60870-5-104 protocol, after loading the firmware for the active and inactive configuration, a de-fault database default.db is installed. This database contains a minimal configuration, consisting of

• system starter,

• communication kernel, and

• device interface.


Schneider Electric

Initially, the configuration does not include any IEC 60870-5-104 communication functions. Network inter-faces are initialized with the following default addresses:

• port A/B: 192.168.0.4

• port C: 192.168.1.4

The following system services are operative:

• system administration with X30 Studio, flash loader,

• communication with the setting software over network or serial interface,

• user management with the Security Administration Tool (SAT).

2.3.2 Creating and loading databases

The program X30 Studio is used to engineer Ethernet board for the IEC 60870-5-104 protocol,. The proce-dure is described in this document. The result is a database file, which can be uploaded over Ethernet or se-rial interface from X30 Studio into the device and can then be activated.

The file names of the active and inactive configuration databases and their versions are displayed in the Easergy Studio setting software in function group /Parameters/Config. parameters/IEC. In order for

the file names to be displayed correctly, they must comply with the following rules:

• total number of characters: max. 20

• file type: ".db"

• version information: “_V<Version>.<Revision>“.

Databases can be switched either in X30 Studio or in Easergy Studio with matrix point /Parameters/Con-

fig. parameters/IEC/Switch Config. Bank – execute.


Schneider Electric

3 IEC 60870-5-104 software architecture

3.1 Overview

The above figure shows the maximum configuration of the IEC 60870-5-104 software in the communication module. Each functional block represents one program object. The program objects system starter, kernel and device interface are always started, all other objects are optionally available, depending on the configu-ration.

The central communication node of the system is the kernel. All objects are connected to and communicate with each other via the kernel.

The program objects IEC 60870-5-104 server and client are driver programs at the communication module's Ethernet interfaces. They have a special client-server interface to the application programs telecontrol line and master station bus.

The communication module is connected to the device's CPU via the program object device interface.

In order for the program objects to be managed by the kernel, each of them has a unique address.

3.2 Program objects

3.2.1 Kernel

When the system is started, the program objects register themselves and the data types of the telegrams they need to the kernel. During operation, the kernel distributes the telegrams to the program objects that have registered for the corresponding data type.

In addition, the program objects, e.g. the master station bus, register all devices they are connected with to the kernel. Thus, the kernel can send commands via the destination addresses to the addressed objects.

The program objects connected to the kernel communicate by means of telegrams in the internal telegram format as described in section 10.

Telecontrol line 1

Kernel Device

Interface

Telecontrol line 2

Master 1 station bus


Logic

Station interlocking

IEC 60870-5-104 server

IEC 60870-5-104 client 1

Telecontrol line 3

Telecontrol line 4

Telecontrol line 5

IEC 60870-5-104 client 2

System starter

Eth

ern

et


Schneider Electric

3.2.2 Device interface

The device interface manages the communication with the CPU. Thereby, telegrams addressed according to IEC 60870-5-103 from the device are converted into the communication module's internal telegram format. Simultaneously, the required information is selected from the great number of telegrams offered by the de-vice.

The internal telegram format is based on the IEC 60870-5-104 format, so that already at this point, telegrams can be addressed according to the IEC 60870-5-104 customer profile.

The addresses of CPU telegrams consist of IEC 60870-5-103 function type and information number, except for measured values and commands from the protection part, whose addresses consist of matrix points.

In both cases, the address list provided for each device type can be used to identify telegrams.

Besides communication functions, the device interface also provides the following system functions:

• network interface to the Easergy Studio setting software

• interface to the Security Administration Tool (SAT)

• time synchronization via SNTP or IRIG-B

3.2.3 IEC 60870-5-104 telecontrol lines

Together with a channel of the IEC 60870-5-104 server, an IEC 60870-5-104 telecontrol line realizes an IEC 60870-5-104 server interface, that can work either at the station bus or as a SCADA line.

The telecontrol line is responsible for the application layer of the OSI model. It contains a data model for as-signing information and logic functions, in order to carry out simple data manipulations or logical operations.

Telegrams between telecontrol lines and the IEC 60870-5-104 server are exchanged in the IEC 60870-5-104 ASDU format.

3.2.4 IEC 60870-5-104 master station bus and client

These two program objects together realize one IEC 60870-5-104 master that can connect with up to 32 servers. In terms of the OSI model, the master station bus thus operates as application layer and the IEC 60870-5-104 client operates as transport and network layer.

The master station bus contains a data model for each connected server to map the information. In addition, telegrams can be processed through logic functions, e.g. for the generation of group signals.

Telegrams between the master station bus and the IEC 60870-5-104 client are exchanged in the IEC 60870-5-104 ASDU format.

3.2.5 IEC 60870-5-104 server

The IEC 60870-5-104 server operates as transport and network layer of the IEC 60870-5-104 protocol. For this purpose, it manages all TCP/IP sockets and assigns telecontrol lines to it. Thereby several telecontrol lines can work at one socket. The IEC 60870-5-104 server offers 8 channels for the connection of telecontrol lines.

3.2.6 Logic and station interlocking

The logic and station interlocking program objects can process central logic functions. In contrast to the pro-gram objects device interface, telecontrol lines and master station bus, in the logic and station interlocking, logical operations can be cascaded. This allows even complex logic functions to be processed.

For station interlocking, special interlocking functions are implemented.


Schneider Electric

4 Engineering

4.1 X30 Studio

4.1.1 Introduction

The program X30 Studio is used to engineer the communication modules of Easergy MiCOM 30 devices for the IEC 60870-5-104 communication protocol, and also to engineer the MiCOM S30 central unit, in which also the IEC 60870-5-101/-103 and IEC 61850 protocols can be applied. X30 Studio is a comprehensive tool for the configuration of devices and systems communicating by means of above protocols.

This document does not contain a detailed description of how to use X30 Studio. Here only the principal pro-cedure and the necessary steps for configuring MiCOM 30 devices with the IEC 60870-5-104 protocol are described, without entering into the details about its use.

4.1.2 Access rights

Software programs for engineering devices and systems mostly have a very large scope of functions, which can make them rather complicated to use. In addition, there are different users who need to fulfill different tasks and who have a different level of knowledge of communication functions.

In order to meet the different user requirements, to simplify the use of the software, and to minimize applica-tion errors, a hierarchical user management has been implemented that offers each user only those func-tions they require for fulfilling their tasks.

There are 3 user levels:

• Operator - lowest access level At this level, program objects can be configured for typical application cases. To use the program, basic knowledge of the functions of program objects, of network technology and of the IEC 60870-5-104 protocol is required.

• Engineer - medium access level At this level, program objects can be adapted to special application cases. To use the program, ad-vanced knowledge of the functions of program objects, of network technology and of the IEC 60870-5-104 protocol is required.

• Expert – highest access level At this level, all parameters are visible. They permit controlling the system behavior of program ob-jects. To use the program, detailed knowledge (at software specialist level) of the functions of pro-gram objects is required. This level is required only in exceptional cases.

Program objects, in particular, are designed to be adapted to as many application cases as possible. For this reason, there is a great variety of sometimes very specific parameters. In this context, access levels are particularly important, because otherwise parameters can appear complicated and difficult to overlook.

Besides parameters, also all other functions in X30 Studio are assigned to specific access levels.

4.2 Engineering steps of an IEC 60870-5-104 project

4.2.1 Profile

Data addresses in the IEC 60870-5-104 protocol consist of the common address of ASDU and the address of the information object. For technological addressing of telegrams, typically addresses are structured into bit fields. The designations and values of those bit fields are used during engineering.

The first step when configuring a project is to define the profile in the project data folder of the project tree. The profile can be selected from the profile catalogue. If the required profile does not exist yet, it needs to be created.

A profile defines the following:

• Structure of the common address of ASDU Definition of the length and designations of the bit fields


Schneider Electric

• Structure of the information object address Definition of the length and designations of the bit fields

• Names of wildcards in typicals Definition of the variable fields in the typicals

• Data model typicals Definition of the device program objects for which data model templates are included in the typical

• Format of data model entry Definition of the appearance of the tables for editing of data models, i.e. configuration of the visibility of columns, the column headers, etc.

4.2.2 Typicals

The first step in engineering a device is to create a typical.

The general principle of X30 Studio projects is the handling of communication systems that have repeating data addresses, e.g. device types, field types, etc. To engineer those systems as effectively as possible, it is appropriate to use those types (hereinafter referred to as "typicals") also during engineering.

A typical in an X30 Studio project contains parts of data models and assignment information for program ob-jects that have wildcards (variables) for specific fields. By replacing those wildcards, instances of the typicals can be created.

The basis for creating a typical in X30 Studio is the device catalogue. This catalogue contains all the infor-mation about Easergy MiCOM 30 series, earlier device series and supported third-party devices, that are of-fered at the communication interfaces.

A typical in X30 Studio is created by dragging and dropping an entry from the device catalogue into the IED typicals section.

After defining the device type, the typical is edited: To this aim, the required information is selected from the total amount of data in the catalogue. In the next step the information targets, the assignment to the single telecontrol lines, the logic etc. are entered.

In all data model parts of the typical, wildcards are entered depending on project requirements.

4.2.3 IEDs

In X30 Studio, an IED is created by instantiating a typical. This is done in two steps: 1. Drag and drop the typical into the 'IED-Fields' list, and 2. drag and drop the appropriate field unit into the 'IEDs' list.

Every created IED tree structure now has branches for parameterization and function, which, however, are still empty. In order to continue working, now the device needs to be configured.

4.2.4 Configuration

When engineering a device, as a first step, it must be defined which program objects are started.


Schneider Electric

As a result of the configuration dialogue, the parameter file for the system starter is created, which normally does not need to be further edited. Also, it has been defined which program objects must be parameterized. The program system contains the following system and driver objects:

• system starter,

• kernel,

• IEC 60870-5-104 server,

• IEC 60870-5-104 client.

Normally, those program objects need not be parameterized and their parameters can only be accessed by Engineer or higher-level accounts. Only the following user objects need to be engineered:

• device interface,

• telecontrol lines,

• master station bus,

• logic

• station interlocking.

The configuration consists of one parameter file for each program object and one or several data model files (master station bus).

4.2.5 Parameterization

4.2.5.1 User interface

In X30 Studio, parameters are entered through appropriate input masks. If necessary, help texts provide the user with support.

Only those parameters are visible that correspond to the current or to lower-level user accounts. Also, those parameters are hidden that are not relevant because they correspond to a higher-level setting: For example, in the telecontrol line, parameters 'IP Adresse Client 2 - 8' and 'Modus Redundanzbetrieb' are hidden if pa-rameter 'Protokoll' is set to 'IEC60870-5-104 SBUS'.

The following sections describe parameters for the Operator and Engineer account level.

4.2.5.2 Device interface

Setting group: Ethernet port A/B

Parameter Description

IP-Adresse (IP address)

These parameters describe the subnet at Port A/B. On the network interface a second IP address either inside or outside of the subnet can be assigned. 2. IP-Adresse

(2nd IP address)

Subnetzmaske (Subnet mask)


Schneider Electric


Gatewayadresse (Gateway address)

Address of a gateway to other networks

VLAN1 IP-Adresse (VLAN1 IP address)

IP address of virtual LAN 1

VLAN1 Anzahl Bits Subnetzmaske (VLAN1 subnet mask number of bits)

Subnet mask of virtual LAN 1, beginning at the highest bit number, e.g. 24 bits correspond to the subnet mask 255.255.255.0

VLAN1 ID Unique number to identify virtual LAN 1, 0 - 4094

VLAN1 Priorität (VLAN1 priority)

Priority of virtual LAN 1. The priority can be set from 0 to 7. Priority 7 is the highest.

VLAN1 Gatewayadresse (VLAN1 gateway address)

Address of a gateway in virtual LAN 1 to other networks

VLAN2 IP-Adresse (VLAN2 IP address)

IP address of virtual LAN 2

VLAN2 Anzahl Bits Subnetzmaske (VLAN2 subnet mask number of bits)

Subnet mask of virtual LAN 2, beginning at the highest bit number, e.g. 24 bits correspond to the subnet mask 255.255.255.0

VLAN2 ID Unique number to identify virtual LAN 2, 0 - 4094

VLAN2 Priorität (VLAN2 priority)

Priority of virtual LAN 2. The priority can be set from 0 to 7. Priority 7 is the highest.

VLAN2 Gatewayadresse (VLAN2 gateway address)

Address of a gateway in virtual LAN 2 to other networks

Setting group: Ethernet port C



These parameters describe the subnet at Port C. On the network in-terface a second IP address either inside or outside of the subnet can be assigned. 2. IP-Adresse

(2nd IP address)

Subnetzmaske (Subnet mask)

Gatewayadresse (Gateway address)

Address of a gateway to other networks at port C

Setting group: SNTP configuration


Überwachungszeit Abfrage (Supervision time request)

Within this time interval the requested NTP server must send the re-ply. The supervision time is also the cycle time of the request.

Anzahl der Versuche (Number of time requests)

After the configured number of unsuccessful time requests a mes-sage 'SNTP time request disturbed' is generated

IP-Adresse Server 1 (IP address server 1)

IP address of the first NTP time server

IP-Adresse Server 2 (IP address server 2)

IP address of the alternative NTP time server

Setting group: Services


Einstellprogramm (Configuration interface)

The setting program Easergy Studio uses TLS encrypted communi-cation services (Transport Layer Security) for the communication with the Ethernet board.

Benutzerverwaltung RBAC (RBAC interface)

The role-based access control (RBAC) for users of P30 devices is managed with the Security Administration Tool (SAT). An interface can be chosen for SAT access.

Zeitsynchronisierung NTP (NTP interface)

This parameter limits the visibility of the port for SNTP time re-quests.


Schneider Electric


Systemadministration (System administration)

For the maintenance of the Ethernet board it is necessary to have access to the system services. Those services are used by e.g. MiCOM-Loader and the engineering program X30 Studio.

Setting group: RSTP


Bridge-Prioriät (Bridge priority)

The switch with the lowest bridge priority will be the root bridge. If the bridge priority is configured equal, the MAC address is used to distinguish the priority.

Maximales Alter (Maximum age)

The maximum age is the maximum number of bridge/switch layers in the network topology. In a ring topology, it must be greater than the number of bridges/switches minus the root bridge. In a star to-pology, it must be greater than the number of hops to get from the root bridge to the furthermost switch. The rule for configuration is: 'Maximum age' > 2 x ('Hello time' + 1s). During the time ‘Maximum age’, the bridges/switches hold their network configuration.

Weiterleit-Verzögerung (Forward delay)

This is the maximum time the switch stays in the 'listening' and 'learning' states before it starts forwarding data telegrams. The rule for configuration is: 2 x ('Forward delay' - 1s) > 'Maximum age'.

Hello-Zeit (Hello time)

The hello time is the cycle time of sending the BDPU (Bridge Proto-col Data Unit).

Setting group: Device


interne Geräteadresse (Internal device address)

This device address is used by the communication kernel to identify the device. It is not transmitted outside the board and it is not nor-mally necessary to change the default value.

Setting group: MVs and counters


Zyklus Aktualisierung Messwerte (Cycle time update MVs)

Within this cycle time, the CPU updates the measured values on the communication module. The cycle time may be increased to re-duce the number of transmitted measurement telegrams if the filter functions on the communication module (deadband) are not appli-cable.

Zyklus Aktualisierung Zähler (Cycle time update counters)

Within this cycle time, the CPU updates the energy counter values on the communication module. If energy counters are not used, the cyclic transmission may be switched off by setting the value 65535.

Setting group: Logic


Init Datenmodell mit "nicht aktuell" (Init data model with 'not topical')

By default, all data points are initialized with the quality descriptor 'invalid'. If this option is chosen, they are initialized with quality de-scriptor 'not topical'.

Berechnung Qualitätskennungen (Calculation of quality descriptor)

In logical operations (AND, OR, NAND, NOR, DYNOR), the quality descriptor can be calculated in two ways: a) OR operation of all inputs b) Special conditions are considered. If in an OR or NOR operation at least one input is logical '1' and valid, then the output will be set valid. If in an AND or NAND operation at least one input is logical '0' and valid, then the output will be set valid.

Zykluszeit AZI-Berechnung (Cycle integrated deadband calcu-lation)

In this cycle, the integrated deadband is calculated by adding the deviation (appropriately signed) from the last value transmitted.

Grenzwert Nullpunktunterdrückung (Threshold value zero suppressing)

If the absolute value to be transmitted is less than the threshold value, then 0 will be transmitted. In the data model, the output sta-tus 'z' must be set for data points to switch on zero forcing.


Schneider Electric


Zustandswechsel Setzen Flatter-sperre (Transitions set chatter suppres-sion)

If more transitions than the threshold value occur within the test in-terval, then the data point will be reported with quality 'blocked'. Af-ter this, further reporting is suppressed.

Zustandswechsel Aufhebung Flat-tersperre (Transitions reset chatter suppres-sion)

If less transitions than the threshold value occur within the test inter-val, then chatter suppression will be reset for the data point. The data point will be reported with quality 'not blocked'.

Testintervall Flattersperre (Test interval chatter suppression)

Time interval during which the number of transitions is counted.

Blockierzeit Flattersperre (Blocking time chatter suppression)

After setting a chatter suppression, the data points concerned will be blocked from transmission for the configured time.

Setting group: Operating test


Logdatei schreiben (Write to log file)

Telegram traffic and processing information is recorded in log files.

Dezimal (Decimal)

The number format in log files is decimal (default: hexadecimal).

Maximale Zeilenzahl je Logdatei (Number of lines in the log file)

When the maximum number of lines in the log file is reached, a new file is started with incremented index in its file name.

Maximale Anzahl Logdateien (Number of log files)

After the maximum number of indexed log files has been written, the index of the next log file restarts at 0, overwriting the oldest file.

4.2.5.3 Telecontrol line

Setting group: Main settings


Protokoll (Protocol)

The setting 'IEC60870-5-104 SBUS' is used for operation at the sta-tion bus. One client can be connected to the server. The mode 'IEC60870-5-104 server' is used for SCADA lines. Up to 8 clients can be connected in 2 redundancy modes (see setting group 'IEC 60870-5-104 server').

Setting group: IEC 60870-5-104 server


IP-Socketadresse (IP socket address)

Socket address at which the IEC 60870-5-104 server waits for con-nections with clients. If this address is set to 0.0.0.0, the server will wait at all TCP/IP sockets.

IP-Port (IP port)

The default port number for IEC 60870-5-104 is 2404.

IP-Adresse Client 1 (IP address of client 1)

Address of the client entitled to connect to the server. If this IP ad-dress is set to 0.0.0.0, clients with any address can connect.


Like IP-Adresse Client 1, available in SCADA mode only












Like IP-Adresse Client 1, available with remote operation only


Schneider Electric


Zeitfenster Empfang Quittung (t1) (Timeout receiving confirmation (t1))

The time after which a confirmation telegram on a data APDU or a test APDU should have been received.

Wartezeit Senden Quittung (t2) (Timeout transmitting confirmation (t2))

The time after which a confirmation telegram has to be transmitted in the case that no data was transmitted.

Ruhezeit Senden Testtelegramm (t3) (Idle time until test telegram (t3))

The time after which test telegrams have to be transmitted in the case of a long idle state.

Nichtquittierte APDU Senden (k) (Num. of non-ack. APDUs transmit (k))

The maximum difference between transmit sequence number and receive sequence number; if this number is reached, no further tele-grams will be transmitted.

Nichtquittierte APDU Empfang (w) (Num. of non-ack. APDUs receive (w))

The maximum difference between receive sequence number and transmit sequence number; if this number is reached, a confirma-tion telegram will be transmitted.

Verzögerungszeit Verbindungsstö-rung (Communication error delay)

After detecting a communication error, this delay gives the client time to perform retries to reconnect the link. During this delay time, FIFO data will be held.

Modus Redundanzbetrieb (Redundancy mode)

Available in SCADA mode only. In mode 'Active and standby links', acc. to IEC 60870-5-104, one link is active, i.e. data will be transmitted over this link. All other links are in passive mode. No data will be sent over those links. To control which link is active, the master station uses 'Start and stop data transmission'. Standby links are in state 'Stop data transmis-sion'. In mode 'Multiple active links', data will be sent simultaneously over all links. The master station decides from which link the data will be processed and over which link commands will be sent.

Setting group: Application layer


Gemeinsame Adresse der ASDU (Common address of ASDU)

This address is used if the 'Common address of ASDU' field in the data model is empty.

Packungsverfahren Anwenderdaten (Methods for packing user data)

The following methods can be used: 1. Ausgeschaltet (Switched off) Only one information object is packed into the telegram. 2. Packung von Informationsobjekten (Sequence of infor-mation objects) Two or more information objects are packed into the telegram. 3. Packung von Informationselementen (sequenzielle Packung) (Sequence of information elements) Two or more information elements are packed into the telegram. The information objects must have consecutive addresses. The ad-dresses must be sorted in ascending order. 4. Beide Packungsverfahren (Combined method) ASDUs without time tag are packed as a sequence of information elements (e.g. response telegrams in general interrogation and cy-clic telegrams). ASDUs with time tag are packed as a sequence of information objects. For both methods, the following conditions must be fulfilled: 1. The type identification is suitable for packed messages. 2. Information objects resp. information elements must have identi-cal type identification, cause of transmission and common address of ASDU.

Maximale Länge der Anwenderda-ten (Maximum length of user data)

In monitoring direction – if possible – several information objects are packed into one telegram. The telegram buffer is filled with in-formation objects up to the maximum length of user data.


Schneider Electric


ASDU 70 (Initialisierungsende) (ASDU 70 (End of initialization))

ASDU 70 is used according to standard.

Setting group: General protocol functions


FIFO-Daten halten (Hold FIFO data)

If this checkbox is activated, the data will be stored in the FIFO queues if the connection is disturbed.

Setting group: Cyclic data transmission


Zykluszeit (Cycle time)

When this timer expires, all data points marked for cyclic transmis-sion will be transmitted. If the cycle time is set to 0, the function is disabled.

Setting group: Station interrogation


GA an Informationsquellen (GI to sources of information)

If this option is set, and if a general interrogation is received on the SCADA line, also a general interrogation is sent to the devices where the information for the SCADA line comes from.

Setting group: Clock synchronization


UTC auf der Kommunikationslinie (UTC on SCADA)

UTC is used on SCADA.

Differenzzeit Zeitzone (Offset time zone)

The offset time is used to make a time zone based on UTC on SCADA. It is also possible to add a time offset to the local time. In this case, the switching of summertime is performed on SCADA.

Sommerzeit-Bit (Summer time bit)

The summer time bit is used.

Setting group: Command transmission


Befehlsprozedur (Command procedure SCADA)

The configured command procedure is expected as default setting by the IEC 60870-5-104 interface. Internally, 'Direct execute' is the default setting.

Beendigung der Aktivierung (Signal control 'ACTTERM')

If this checkbox is activated, the ACTTERM confirmation will be used with commands on the telecontrol line. This means that de-vices have to transmit ACTTERM with every command they exe-cute. When the timer (see below) expires and no ACTTERM is re-ceived, the telecontrol software has to generate a negative ACT-TERM. In the case of commands for protective functions, the ACT-TERM confirmation must be defined in the telecontrol data model.

Maximales Alter von Befehlen (Maximum age of commands)

This parameter is used for commands with time tag (IEC 60870-5-104, ASDU 58...64). If a command telegram is too old, it is dis-carded without any confirmation.

Anzahl Befehlsprozeduren (Number of command procedures)

This parameter defines the number of command procedures that can be executed at the same time. If the maximum number of pro-cedures is exceeded, further commands are discarded and a nega-tive confirmation is transmitted. If a command generates two or more internal commands, a command procedure for every internal command is started.

Überwachungszeit Befehl Ausfüh-ren (Timeout execute command)

The time interval starts after receiving the select command. The peer station must send the execute command within this time.

Überwachungszeit Befehlsquit-tungen (Timeout command confirmation)

Interval between transmitting the command to the device and re-ceiving the last confirmation from the device. When this time inter-val expires, a negative confirmation is transmitted (ACTCON or ACTTERM).


Schneider Electric


Verzögerung Beendigung der Akti-vierung (Delay of Activation Termination)

This delay ensures that the confirmation ACTTERM is sent after the return info if this is not provided by the command target.

1 aus n - Kontrolle (Check control uniqueness)

If activated, it is checked whether only one command runs at a time. Further commands will not be executed and rejected with a nega-tive confirmation.

Geräteadresse Befehl läuft ext. (Device address order running ext.)

With this message, it is possible to include external signals into the check of control uniqueness.

Datenpunktdresse Befehl läuft ext. (Datapoint address order running ext.)

With this message, it is possible to include external signals into the check of control uniqueness.

Setting group: Transmission of integrated totals


Betriebsart (Mode of transmission)

The following modes are available: 'Local freeze with spontaneous transfer' and 'Local freeze with counter interrogation'.

Setting group: Background scan


Zykluszeit (Cycle time)

When this timer expires, one data point will be transmitted. This function is disabled if the cycle time is set to 0.

Setting group: Transmission in reverse direction


Virtuelle Geräteadresse Partner-station (Virtual device address of peer sta-tion)

With this device address (virtual address), the peer station is man-aged by the kernel. The parameterized address must be unique within the system. If the device address is set to a value not equal 0, the device will be registered to the kernel so that commands can be sent over the virtual device to the peer station.

GA nach Verbindungsaufbau (General interrogation on link OK)

If this option is selected, a global general interrogation command is sent to the peer station when the link changes status from disturbed to connected.

Setting group: Data model


ASDU- und Objektadresse eindeu-tig (ASDU and object adress unique)

If this checkbox is selected, the uniqueness of the combination of common address of ASDU and address of data object are checked. Otherwise using the same combination of addresses with a different type identification is tolerated.


See the same setting group in section 4.2.5.2, Device interface.



4.2.5.4 IEC 60870-5-104 master station bus

Setting group: Master station bus IEC104


Direktmodus (Direct mode)

In direct mode, the IEC 60870-5-104 master station bus works with-out data models. In this mode, the transmission of signals in control direction is not possible because the used data types are not regis-tered to and assigned to by the kernel.

Interne Adresse 1. Gerät (Internal address of the first device)

Connected servers with consecutive addresses are allocated, start-ing at this internal device address.


Schneider Electric

Setting group: Table of connected servers

Column Description

Gerätename (Device name)

The device name is not evaluated. It can be freely allocated with a maximum length of 127 characters and it is used for documentation.


IP address of the connected servers.

Datenmodelldatei (Data model file)

Here the name of the data model file of the connected server is en-tered without path specification. The file name is displayed only. For handling data models, X30 Studio is used.

Setting group: Master station bus IEC104


Überwachungszeit Verbindungsauf-bau (t0) (Timeout connect (t0))

Within this time interval the server being contacted must reply to the connection request.

Zeitfenster Empfang Quittung (t1) (Timeout receiving confirmation (t1))

The time after which a confirmation telegram on a data APDU or a test APDU should have been received.

Wartezeit Senden Quittung (t2) (Timeout transmitting confirmation (t2))

After this time, unconfirmed receive telegrams are confirmed if no data is to be sent.

Ruhezeit Senden Testtelegramm (t3) (Idle time until test telegram (t3))

After this idle time, a test telegram is sent if no data are to be sent.

Nichtquittierte APDU Senden (k) (Num. of non-ack. APDUs transmit (k))

The maximum difference between transmit sequence number and receive sequence number; if this number is reached, no further tele-grams will be transmitted.

Nichtquittierte APDU Empfang (w) (Num. of non-ack. APDUs receive (w))

The maximum difference between receive sequence number and transmit sequence number; if this number is reached, a confirma-tion telegram will be transmitted.

Anzahl der Verbindungsversuche (Number of attempts on errors)

If this number is reached, the link is marked as disturbed.



4.2.5.5 Logic / station interlocking

Setting group: Main settings


Geräteadresse des 'Virtual Logic Device' (VLD) (Device address of Virtual Logic Device (VLD))

At this virtual device address, logic functions will be registered to and handled by the kernel. This means that all signal outputs and command inputs should be engineered with this device address.

Setting group: Station interlocking (only effective in station interlocking)


Zeitüberwachung Steuerprozedur (Timeout control procedure)

The overall time of the control procedure from the select command until receiving the confirmation of activation for the execute com-mand is supervised. If the procedure 'Select and execute' is used on the telecontrol line, this timeout must be longer than the timeout for the execute command after the select.

Überwachungszeit erweiterte Ver-riegelungsfunktion (Timeout time extended locking function)

This supervision time is used by the extended locking function 'elock' to supervise the confirmation telegram after sending the query telegram.


Schneider Electric

Setting group: Data model


ASDU- und Objektadresse eindeu-tig (ASDU and object adress unique)

If this checkbox is selected, the uniqueness of the combination of common address of ASDU and address of data object is checked. Otherwise using the same combination of addresses with a different type identification is tolerated.



Setting group: Command transmission

See the same setting group in section 4.2.5.3, Telecontrol line.



4.2.5.6 IEC 60870-5-104 server



Logdatei schreiben (Write to log file)

Telegram traffic and processing information is recorded in log files.

Dezimal (Decimal)

The number format in log files is decimal (default: hexadecimal).

Schalter Logfunktion Kanal 0 (Switch logging channel 0)

Enabling/disabling of logging channel 0















Maximale Zeilenzahl je Logdatei (Number of lines in the log file)

When the maximum number of lines in the log file is reached, a new file is started with incremented index in its file name.

Maximale Anzahl Logdateien (Number of log files)

After the maximum number of indexed log files has been written, the index of the next log file restarts at 0, overwriting the oldest file.

4.2.5.7 IEC 60870-5-104 client.



4.2.5.8 Communication kernel




Schneider Electric

4.2.5.9 Functions

Here the data model files of the program objects can be found, which were generated from typicals by re-placing wildcards. Data models can be opened for editing, e.g. for adding data points not provided in the typi-cals. However, post-editing of data models should remain an exception. The aim is to generate all data points from typicals.

4.2.5.10 Generating and transmitting a database

The database generating function can be found in the context-sensitive menu of the IEDs, option 'Datenüber-tragung' ('Data transmission'). After confirming with the button 'DB Erzeugen' ('Generate DB') and further confirmation with the button 'Erzeugen' ('Generate'), the user is prompted to enter the version number and a comment. After confirming the input, a new database file will be generated in the tree structure.

The user can then select this database for transmission. It is saved in the device as an inactive (standby) da-tabase. In order to activate the loaded database, databases must be switched. After restarting the Ethernet board in the device and after the connection has been reestablished, the updated database configuration is displayed.


Schneider Electric

5 Data model and logic library

5.1 Approach

The data model and logic library was developed especially for the realization of communication functions. Although in most cases, simple logical operations are sufficient, e.g. group signals through logical OR opera-tion, sometimes also specialized functions are required in order to comply with standards.

Frequently used functions, like the assignment of telegrams, are easily possible, but so are the more com-plex logical operations, e.g. in application cases of station interlocking or logic.

Compared to classical programmable logic controllers, processing in this approach is realized in a different way. The processing of logic functions occurs event-driven, i.e. inputs and outputs of the functions are time-tagged telegrams generated at changes of state. There is no cyclic processing of logic functions with a de-fined cycle time. As a result, signal processing is typically very fast and the logic library does not cause a constantly high processor load. Moreover, it is possible to use the data model and logic library in multiple program objects or instances of program objects without overloading the system.

5.2 Integration into program objects

5.2.1 Program objects with logic library

The data model and logic library is integrated into all colored program objects of the system configuration:

This architecture allows to apply logic functions very effectively:

• A logic function in the device interface is effective on all telecontrol lines. However, the same func-tion can also be used in one telecontrol line if it is required selectively.

• By distributing to program objects, logic functions can be cascaded.

Telecontrol line 1

Kernel Device

interface

Telecontrol line 2



Logic

Station interlocking


IEC 60870-5-104 client 1

Telecontrol line 3

Telecontrol line 4

Telecontrol line 5

IEC 60870-5-104 client 2

Eth

ern

et

System starter


Schneider Electric

5.2.2 Implementation differences

The logic library is integrated into the program objects illustrated in the above graphic. However, there are differences in the availability of the functions. The following table shows the functions and their availability depending on their implementation:

Function Logic SI Telec. Line

SBUS master

Device interface

Time functions (ton, toff, cycsup, …) x x x - x

Cyclic transmission, background scan

- - x - -

Filtering functions (deadband, chatter sup-pression, …)

x x x - x

Command procedure management, checking of control uniqueness

x x x - -

Interlocking (lock, elock) - x - - -

Chapter 6 describes, for which objects the respective function is available.

5.3 Format of data model files

5.3.1 Basic structure of data model files

A line in the data model consists of fields, separated by semicolons (Microsoft Excel® ‘.csv‘ format).

Numbers in data models are displayed in decimal format by default, hexadecimal numbers are marked by a preceding “0x“. All numbers are integers, only the parameters of input and output functions can have a frac-tional part, e.g. “3.14“, “-1.55“, etc.

Fields marked as optional may remain empty. Furthermore, after the second parameter field of the function, the line evaluation ends. Behind this, comments may be entered.

In principle, a data model line describes the allocation of an input to an output of the data model. Processing functions can be defined optionally.

Direction of transmission

The first field in the data model defines the allocation to the data model:

‘M‘ - data model entry in monitoring direction ‘C‘ - data model entry in control direction ‘I‘ - data model entry logic data model ‘P‘ - polygon definition ‘#‘ - comment line

This field also defines if, depending on the application, the line is to be processed from the right to the left or vice versa and hence defines the position of input and output information.

Data type, type identification

This field defines the type of input and output telegrams.

Address fields

Depending on the application, data model files vary in length and designation of address field designation. The structures of the address fields for input and output described here are standard format. In X30 Studio they can be overlayed by a customer-specific address profile, so that for the user, only the address fields and identifiers defined in the profile are visible.

Bit field

Here the following optional information can be given: start bit in the input telegram, length of the bit field and the target bit in the output telegram, separated by blanks. The bits are counted in the order of arithmetic sig-nificance, starting at 0 from the right.


Schneider Electric

Status, functions, and parameter

The information in these fields is optional. If the fields remain empty, the data model line is processed as per default. The positions of input and output status, functions and parameters depend on the application and direction information.

Group

Group within the general interrogation or counter group.

5.3.2 Data model file for device interface

The left-hand part of the line shows the information at device end, the right-hand part shows the internal in-formation at the communication kernel.

Field Optional Description

D no Direction of transmission 'M' = data model entry in monitoring direction 'C' = data model entry in control direction

DT no Data type (device end)

DEV no Address (device end) always to be set at 1

TYP no Function type (in certain cases also matrix point address X)

INF no Information number (in certain cases also matrix point address Y)

STAT yes Status Information (device end) Entry in monitoring direction: input status Entry in control direction: output status

FKT yes Processing function (device end) Entry in monitoring direction: input function Entry in control direction: output function

PAR yes Parameters for function (device end) Entry in monitoring direction: parameter for input function Entry in control direction: parameter for output function

ST_LN_ZI yes Bit field

DT no Internal data type

DEV yes Internal device address

DPA4 - 0 no Internal data point address

GR yes Group - not used

STAT yes Internal status information Entry in monitoring direction: output status Entry in control direction: input status

FKT yes Internal processing function Entry in monitoring direction: output function Entry in control direction: input function

PAR yes Parameters for internal function Entry in monitoring direction: parameter for output function Entry in control direction: parameter for intput function


Schneider Electric

5.3.3 Data model file for telecontrol lines and master station bus

The left-hand part of the line shows the internal information at the communication kernel, the right-hand part shows the information at the IEC 60870-5-104 interface.

The IEC 60870-5-104 master station bus contains a data model file for each connected server.

Field Op-tional

Description

D no Direction of transmission 'M' = data model entry in monitoring direction 'C' = data model entry in control direction

DT no Internal data type

DEV no Internal device address

DPA4 - 0 no Internal data point address

STAT yes Internal status information Telecontrol line: Entry in monitoring direction: input status

Entry in control direction: output status

Master station bus: Entry in monitoring direction: output status Entry in control direction: input status

FKT yes Internal processing function Telecontrol line: Entry in monitoring direction: input function

Entry in control direction: output function

Master station bus: Entry in monitoring direction: output function Entry in control direction: input function

PAR yes Parameters for internal function Telecontrol line: Entry in monitoring direction: parameter for input function

Entry in control direction: parameter for output function

Master station bus: Entry in monitoring direction: parameter for output function Entry in control direction: parameter for input function


TK no IEC 60870-5-104 type identification

ASDU1 - 0 yes IEC 60870-5-104 common address of asdu OBJ2 - 0 no IEC 60870-5-104 information object address

GR yes Group

STAT yes IEC 60870-5-104 status information Telecontrol line: Entry in monitoring direction: output status

Entry in control direction: input status

Master station bus: Entry in monitoring direction: input status Entry in control direction: output status

FKT yes IEC 60870-5-104 processing function Telecontrol line: Entry in monitoring direction: output function

Entry in control direction: input function

Master station bus: Entry in monitoring direction: input function Entry in control direction: output function

PAR yes IEC 60870-5-104 parameters for processing functions

Telecontrol line: Entry in monitoring direction: parameter for output function Entry in control direction: parameter for input function

Master station bus: Entry in monitoring direction: parameter for input function Entry in control direction: parameter for output function


Schneider Electric

5.3.4 Data model file for logic / station interlocking

The left-hand part of the line shows the information of the input data model, the right-hand part shows the information of the output data model.

Field Op-tional

Description

D no Direction of transmission ‘I‘ – Identifier for input information

DT no Data type of input telegram

DEV no Device address of input telegram

DPA4…0 no Data point address of input telegram

STAT yes Status of input processing

FKT yes Processing function for input

PAR yes Parameter for input function


DT no Data type of output telegram

DEV no device address of output telegram

DPA4..0 no Data point address of output telegram

GR yes Group (not used)

STAT yes Status of output processing

FKT yes Processing function for output

PAR yes Parameter for output function

5.4 Processing data model files

5.4.1 Device interface, telecontrol lines, and master

The following description refers to telecontrol lines. For the IEC 60870-5-104 master station bus, the monitor-ing / control direction flow is reversed.

From the data model file read at program start, two separate data models are generated. They are managed by two instances of the logic library:

• data model and processing in monitoring direction

• data model and processing in control direction

Telegrams from the kernel are processed via the data model in monitoring direction. Output telegrams are converted into the IEC 60870-5-104 format and sent via the IEC 60870-5-104 server to the network inter-face.

In control direction, first telegrams are converted into the internal telegram format. Then they are processed via the data model. The output telegrams are sent to the kernel.

Hence within the telecontrol line, cascading logical operations is not possible.

DMD and logic control direction

DMD and logic monitoring direction

Kernel Telegram conversion

IEC 104 server


Schneider Electric

5.4.2 Logic / station interlocking

For the application case of logic / station interlocking, there is only one data model. The following graphic shows the communication mechanisms between logic and kernel.

An input telegram is received from the kernel, it is processed, and the generated output telegrams are sent to the kernel.

The kernel distributes the telegrams to all objects having registered for the corresponding data type, also back to the logic. Hence even without special engineering, cascading logical operations is possible.

If an output in the data model is marked with status flag 'm' (“memory”), the generated output telegram is not sent to the kernel but directed internally to input processing. Thus, cascaded logical operations are pro-cessed with minimal delay.

To map the output data points of the logic and their management by the kernel, a virtual logical device is de-fined. Thus, the logic / station interlocking consists of 2 parts, each with their own unique device address:

1. the logic / Interlocking object for coupling to the kernel, and 2. the virtual logic device (VLD), the actual logic device.

Seen from the kernel, the VLD is a remote device that can be reached via the logic object – similar to a field unit coupled via the IEC 60870-5-104 master:

One logic / station interlocking object manages only one VLD.

The station interlocking is realized by a second start of the logic with other parameters. Object addresses and default addresses of the virtual logic devices are defined as follows:

Object Object address VLD address

Logic 5 56

Station interlocking 6 57

Processing via memory

Logic / station interlocking

Logic object

Virtual logic device

Kernel

Kernel

Data model and logic functions


Schneider Electric

5.5 Telegram processing

A line in the data model is processed as shown in the following graphic:

If a telegram is received by input processing and the address is found in the data model, an input-related en-gineerable function is called, carrying out conversions, arithmetic operations, etc.

Certain functions need further information to fulfill their tasks. This information is provided by parameters (e.g. scaling factor). Input status information can also influence processing.

If no input function is defined, by default

• telegram quality descriptors are copied into the new quality descriptors,

• telegram data are copied and converted implicitly into the new data,

• the telegram time tag is copied into the new tag.

After that, an optional output function is called to carry out special treatments like threshold processing, logic operations, etc. and to update the data model. The output function can access status information and can use one parameter (e.g. threshold value).

If no output function is defined, by default

• data model quality descriptors are compared against the new quality descriptors,

• data model data are compared against the new data,

• data model data, quality descriptors and the time tag are updated,

• if data or quality descriptors are changed, an output telegram is created.

All processing, whether via input or output functions or via implicit conversion, depends on the input and out-put data format. For commands and counters, in spontaneous transfer mode, an output telegram is gener-ated for each input telegram.

The output status ‘q‘ – quiet allows to suppress the generation of spontaneous telegrams. With status ‘f‘ – force an output telegram is always generated as a rule.

Multiple entries in the data model

1. One input can be linked to multiple outputs by inserting it multiple times into the data model.

2. Multiple inputs can be linked to one output by inserting the same output address and the same type identification / data type. In doing so, the same output function (bitstring, group signal, etc.) must be defined in all lines of the logical operation.

Output telegram

Output-related

function

Data model

Status information

Parameter

Input-related

function

Input telegram

Status information

Parameter


Schneider Electric

6 Functions of the logic library

6.1 Data formats

Processing of data within the logic is based at defined data formats.

During runtime of the logic, when processing a telegram, first the data formats of input and output in the data model are determined. On that basis, the logic functions can then be processed.

The following table provides an overview of the data formats supported and the related data types/type iden-tifications in the internal telegram interface and/or in the IEC 60870-5-104 standard.

Short form Data format long form DT internal

TI IEC 104

Description

SPI Single-point information 30

1 30

Single-point information Single-point information with time tag

DPI Double-point infor-mation

31

3 31

Double-point information Double-point information with time tag

VTI Value with transient state indication

32

5 32

Step position information Step position information with time tag

SCO Single command 45

45 58

Single command Single command with time tag

DCO Double command 46

46 59

Double command Double command with time tag

RCO Regulating step com-mand

47

47 60

Regulating step command Regulating step command with time tag

BS8 Bitstring of 8 bits 70 100 101

70 100 101

End of initialization General interrogation Counter read command

BS16 Bitstring of 16 bits 104 104 Test command

BS32 Bitstring of 32 bits 33

51

7 33 51 64

Bitstring of 32 bits Bitstring of 32 bits with time tag Bitstring command of 32 bits Bitstring command of 32 bits with time tag

INT16 Integer value of 16 bits 9 11 21 34 35

Measured value, normalized value Measured value, scaled value Measured value, normalized value without quality descriptor Measured value, normalized value with time tag Measured value, scaled value with time tag

INT32 Integer value of 32 bits 34 35

Measured value, normalized value Measured value, scaled value

FP32 Floating point value of 32 bits

36 36 Measured value, short floating point value with time tag

BCR32 Binary counter of 32 bits

37

15 37

Counter Counter with time tag

INT16BS8 Integer value of 16 bits with bitstring of 8 bits

48 61 49 62

Set point command, normalized value Set point command, normalized value with time tag Set point command, scaled value Set point command, scaled value with time tag

INT32BS8 Integer value of 32 bits with bitstring of 8 bits

48 49

Set point value, normalized value with time tag Set point command, scaled value with time tag

FP32BS8 Floating point value of 32 bits with bitstring of 8 bits

50

50 63

Set point command, short floating point value Set point command, short floating point value with time tag


Schneider Electric

6.2 Implicit conversion

Implicit format conversion is applied if no input function and no bit field have been specified. Please note the following particularities:

• Binary information When converting binary information (DPI) into SPI, bit 1 is assigned to bit 0. Thus, a faulty state is signaled by SPI=1 and an intermediate state is signaled by SPI=0.

• Analogue information If during conversion of the greater integer format, its value exceeds the maximum value of the smaller integer format, the overflow bit is set.

• Integer floating point During the conversion of 32 bit integer values into floating point values and vice versa, a loss of ac-curacy may occur.

The following table shows the converting possibilities between the different data formats:

Output

SP

I

DP

I

VT

I

SC

O

DC

O

RC

O

BS

8

BS

16

BS

32

INT

16

INT

32

FP

32

BC

R3

2

INT

16

BS

8

NT

32

BS

8

FP

32B

S8

Input

SPI x x x x x

DPI x x x x x

VTI x x x x

SCO x x x x x

DCO x x x x x

RCO x x x x x

BS8 x

BS16 x

BS32 x

INT16 x x x x x

INT32 x x x x x

FP32 x x x x x

BCR32 x x x

INT16BS8 x x x x x x


FP32BS8 x x x x x x

Examples (telecontrol line):

D DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 STAT FKT PAR ST_LN_ZI DT ASD1 ASD0 OBJ2 OBJ1 OBJ0 GR STAT FKT PAR TEXT

M 30 60 0 0 0 0 2 31 1 128 0 0 2 SPI->DPI

M 31 60 0 0 0 1 1 30 1 128 0 1 1 DPI->SPI

M 32 60 0 0 0 2 1 32 1 128 0 2 1 VTI->VTI

M 32 60 0 0 0 5 5 34 1 128 0 5 5 VTI->INT16

C 30 60 0 0 0 3 1 45 1 128 0 2 2 SCO->SPI

C 31 60 0 0 0 3 2 45 1 128 0 3 2 SCO->DPI

C 46 60 0 0 0 3 4 45 1 128 0 3 4 SCO->DCO

C 30 60 0 0 0 4 1 46 1 128 0 3 1 DCO->SPI

C 31 60 0 0 0 4 2 46 1 128 0 4 2 DCO->DPI

M 34 60 0 0 0 5 5 36 1 128 0 5 5 INT32->FP32

M 37 60 0 0 0 5 11 35 1 128 0 5 11 BCR32->INT16


Schneider Electric

6.3 Bit field assignment

Bit fields can be specified either with or without input and output functions. If no input function is defined, the relevant bit field is copied from the input data and inserted into the target position of the output telegram.

If an input function (e.g. 'not') is defined, the copied bit field is used as input variable for the function.

If a bit field has been specified, in contrast to implicit format conversion, the compatibility of input and output formats is not checked. Any combinations of data formats are allowed.

Unlike implicit format conversion, where, for example, qualifiers are also copied, here the bit field only is cop-ied. Its limits are checked depending on the input and output format. A data format conversion, like implicit conversion, does not take place.



M 33 60 0 0 0 248 112 8 2 0 31 1 0 60 248 128 Sig./meas.block

M 33 60 0 0 0 248 112 10 2 0 31 1 0 60 248 129 Command block

M 33 60 0 0 0 248 112 12 2 0 31 1 0 60 248 130 Blocked/faulty


Schneider Electric

6.4 Input-related functions

6.4.1 Overview

Logic:

not - Bitwise negation

Arithmetic:

add - Addition of constant value sub - Subtraction of constant value mult - Multiplication with constant value div - Division by constant value sqrt - Square root scal - Polygon scaling

Comparison:

cmpeq - Result is true in case of equality cmpne - Result is true in case of inequality cmpgt - Result is true in case of greater than cmpge - Result is true in case of greater than or equal to cmplt - Result is true in case of less than cmple - Result is true in case of less than or equal to isdef - Result is true in case of defined switch position istra - Result is true in case of undefined switch position ifeq - Output telegram in case of equality ifne, ifneq - Output telegram in case of inequality ifgt - Output telegram in case of greater than ifge - Output telegram in case of greater than or equal to iflt - Output telegram in case of less than ifle - Output telegram in case of less than or equal to iftc - Output telegram in case of cause of transmission equal to ifntc - Output telegram in case of cause of transmission unequal to

Quality descriptors:

isgood - Result is true if no quality descriptor is set isbad - Result is true if quality descriptor is set isiv - Result is true if 'invalid' is set isnt - Result is true if 'not topical' is set isbl - Result is true if 'blocked' is set issb - Result is true if 'substituted' is set isov - Result is true if 'overflow' is set

Timing:

ton - Switch-on delay toff - Switch-off delay tonoff - Switch-on and switch-off delay timp - Impulse (monoflop) timer - Timer cycsup - Cycle supervision

Switch:

sel, case, deflt - Inputs of the switch function

Invalid control:

sig, con - Inputs of the invalid control function

D flip-flop

set, res, dat, clk - Inputs of the D flip-flop

Interlocking:

cmd, req, enon, enoff, send, conf

- Inputs of the interlocking function


Schneider Electric

6.4.2 Negation - 'not'

Function: Negation of binary data and bit fields

Availability: Logic SI Line Master Device

x x x x x

Parameter: Not required

Status: No particular status information

Data formats:

Output

SP

I

DP

I

SC

O

DC

O

RC

O

BS

8

BS

16

BS

32

Input

SPI x x x x x

DPI x x x x x

SCO x x x x x

DCO x x x x x

RCO x x x x x

BS8 x

BS16 x

BS32 x

Bit field: Applicable

Description: Bitwise negation of data field or bit field

Application: Negation of binary data formats or bit fields

Particularities: The data field is negated. Qualifiers, quality descriptors, etc. are copied.


The negation function can be used for binary data formats together with default conversions.


M 30 60 0 0 0 160 18 not 30 1 0 134 160 18 Dev ice off-line

M 33 60 0 0 0 248 1 1 2 not 8 2 0 31 1 0 134 248 128 Bit field negation


Schneider Electric

6.4.3 Arithmetic operations - 'add', 'sub', 'mult', 'div', 'sqrt'

Function: Arithmetic operations with constant operand

Availability:

Logic SI Line Master Device

x x x x x

Parameter: Operand, exception: function “sqrt“ has no parameter


Data formats:

Output

V

TI

INT

16

INT

32

FP

32

BC

R3

2

INT

16

BS

8

INT

32

BS

8

FP

32B

S8

Input

VTI x x x x

INT16 x x x x x

INT32 x x x x x

FP32 x x x x x

BCR32 x x x



FP32BS8 x x x x x x


Description: Input data are arithmetically combined by the following parameters:

add - addition sub - subtraction mult - multiplication div - division sqrt - square root

Application: Scaling of measured values, curve offset

Particularities: The bit field is calculated after the arithmetic operation.


Scaling of floating point value 0 to 1 to normalized value with 240% nominal value = +/-4096


M 36 60 12 34 0 248 50 mult 1706 34 12 34 0 248 50 CurrentI1norm.




Schneider Electric

6.4.4 Polygon scaling - 'scal'

Function: Polygon scaling of analogue values

Availability:


x x x x x

Parameter: Polygon reference number


Data formats:

Output

V

TI

INT

16

INT

32

FP

32

BC

R3

2

INT

16

BS

8

INT

32

BS

8

FP

32B

S8

Input

VTI x x x x

INT16 x x x x x

INT32 x x x x x

FP32 x x x x x

BCR32 x x x



FP32BS8 x x x x x x

Bit field: Not applicable

Data model: Polygon definition

1. Direction identifier = ‘P‘ 2. Polygon reference number 3. Number of pairs of interpolation points 4. Pairs of interpolation points x; y; with x values sorted in ascending order

Polygon reference

A polygon must be defined before it can be used. This reference is given by the pa-rameter of the function 'scal'.

Description: Calculation of the function value from the input value and the corresponding polygon curve. If the input value lies outside the polygon curve, the quality of the output is set to 'overflow'.

Particularities: The bit field is calculated after the arithmetic operation.

Application: Scaling of measured values

Examples:

P 1 2 0 0 32767 32767

P 2 6 -32767 -32767 -1000 -500 -500 -500 500 500 1000 500 32767 32767

P 3 7 -32767 32767 -1000 500 500 500 0 0 500 500 1000 500 32767 32767


M 34 60 0 0 0 160 1 scal 1 34 1 128 135 160 1

M 34 60 0 0 0 160 2 scal 2 34 1 128 135 160 2

M 34 60 0 0 0 160 3 scal 3 34 1 128 135 160 3


Schneider Electric

6.4.5 Comparing functions - 'ifeq', 'ifne', 'ifneq', 'ifgt', 'iflt', 'iftc', 'ifntc'

Function: Generation of an output telegram depending on the result of comparing operation Availability:


x x x x x

Parameter: Comparison value


Data formats: Input: all data formats Output: command data formats


Description: An output telegram is created only if the following conditions are fulfilled:

ifeq - Test data for equality ifne, ifneq - Test data for inequality ifgt - Test data for greater than ifge - Test data for greater than or equal to iflt - Test data for less than ifle - Test data for less than or equal to iftc - Test cause of transmission for equality ifntc - Test cause of transmission for inequality

The state in the data model is updated in any case.

Application: With output function 'set', for instance, depending on the data content, a command can be converted into two alternative commands and assigned to two different ad-dresses. Also converting two commands into one command is possible. With output function 'settc', for instance, depending on the cause of transmission, a command confirmation can be derived from the return info. With function 'ifneq 0', the intermediate state in control state messages can be sup-pressed.

Particularities: If the input function is a comparing function, outputs with the same address can be specified several times in the data model. They are created within the data model several times and reported in general interrogations several times. For this reason, the usage of identical output addresses should be limited to commands and com-mand confirmations.


Conversion of one regulating step command into two single commands, and conversion of two single com-mands into one regulating step command

Suppressing of intermediate state in control state message


C 45 60 0 0 0 242 100 set 1 47 1 128 134 242 65 ifeq 1 'Low er' command

C 45 60 0 0 0 242 101 set 1 47 1 128 134 242 65 ifeq 2 'Higher' command




M 31 60 0 0 0 242 1 ifneq 0 31 1 128 60 242 1 CB status


Schneider Electric

6.4.6 Comparing functions - 'cmpeq', 'cmpne', 'cmpgt', 'cmpge', 'cmplt', 'cmple'

Function: Setting of an output value depending on the result of the comparing operation

Availability:


x x x x x

Parameter: Comparison value


Data formats: Input: all data formats Output: SPI or DPI


Description: The result of the comparing operation is true if the following conditions are fulfilled:

cmpeq equality cmpne inequality cmpgt greater than cmpge greater than or equal to cmplt less than cmple less than

The result is encoded as SPI or DPI, depending on the output format.

Application: When evaluating switching states in interlocking equations, for example, the compar-ing function can be used to define which states of the double-point information are to be considered as 'ON' and 'OFF'.

This function is also used for decoding bitstrings or bit fields.

Additionally, this function can be used for generating threshold messages for meas-ured values or for voltage present tests.

Particularities: -


Comparing functions for the accurate detection of control states


M 31 60 0 0 1 0 2 cmpeq 2 30 1 128 0 249 1 Q11 closed

M 31 60 0 0 1 0 6 cmpeq 1 30 1 128 0 249 2 Q15 open

M 33 60 0 0 1 0 6 cmpeq 1 0 2 0 30 1 128 0 249 3 Q16 open


Schneider Electric

6.4.7 Comparing functions for control state messages - 'isdef', 'istra'

Function: Setting of the output value depending on the state of double-point information

Availability: Logic SI Line Master Device

x x x x x



Data formats: Input: DPI Output: SPI or DPI



isdef - defined control state (value 1 or 2) istra - transient control state (value 0 or 3)

Application: When evaluating switching states in interlocking equations, for example, the compar-ing function can be used to define which states of the double-point information are to be considered as defined or undefined.

Particularities: None


Testing of control state messages for defined or undefined state


M 31 60 0 0 1 0 2 istra 30 1 128 0 249 10 Q11 undefined

M 31 60 0 0 1 0 6 isdef 30 1 128 0 249 15 Q15 closed/open


Schneider Electric

6.4.8 Test of quality descriptors - 'isgood', 'isbad', 'isiv', 'isnt', 'isbl', 'issb', 'isov'

Function: Setting of the output value depending on the state of quality descriptors

Availability:


x x x x x



Data formats: Input: all data formats Output: SPI or DPI

Bit field: rrelevant


isgood Result is true if no quality descriptor is set isbad Result is true if at least one quality descriptor is set isiv Result is true if 'invalid' is set isnt Result is true if 'not topical' is set isbl Result is true if 'blocked' is set issb Result is true if 'substituted' is set isov Result is true if 'overflow' is set

Application: Processing of quality information in logical operations




M 32 60 0 0 0 248 86 isgood 30 1 128 0 0 250 Voltage OK


Schneider Electric

6.4.9 Switch-on delay - 'ton'

Function: Switch-on delay of binary signals

Availability:


x x x - x

Parameter: Time delay in seconds

Status: : ‘r‘ - re-trigger, ‘w‘ - transient signal

Data formats: Input: SPI, DPI, SCO, DCO Output: SPI, DPI, SCO, DCO


Description: a) Edge-triggered

If the input signal changes from logical '0' to logical '1', the delay time is started. If the input signal is logical '1' after the delay time has expired, also the output takes on the state logical '1'.

b) State-triggered

The mode ‘state-triggered’ is used in case of command delays or if input status 'w' (transient signal) is set. If the input telegram has the state logical '1', the delay time is started. If the input signal is logical '1' after the delay time has expired, also the out-put state is set to logical '1'.

Re-trigger

If the input status is set to 'r', the delay time is re-triggered by further rising edges of the input signal or telegrams with the state logical '1'.

The (edge-triggered) function is illustrated in the following diagram:

Application: Signaling delays

Particularities: The delay time tolerance is +1 second.

If a quality descriptor has been set in the input signal, there is no delay, the mes-sage is generated immediately.


Delay in case of a communication error, bit 5 in bitstring


M 33 16 0 0 0 128 128 ton 15 5 1 0 30 1 128 0 60 10 Fault P139_128

M 33 16 0 0 0 128 129 ton 15 5 1 0 30 1 128 0 60 11 Fault P139_129

Input signal

t t t

Output without re-trigger

t t

Output with re-trigger t t t


Schneider Electric

6.4.10 Switch-off delay - 'toff'

Function: Switch-off delay of binary signals

Availability:


x x x - x


Status: Input status: ‘r‘ - re-trigger, ‘w‘ - transient signal




If the input signal changes from logical '1' to logical '0', the delay time is started. If the input signal is logical '0' after the delay time has expired, also the output takes on the state logical '0'.

b) State-triggered

The mode ‘state-triggered’ is used in case of command delays or input state 'w' (transient signal). If the input telegram has the state logical '0', the delay time is started. If the input signal is logical '0' after the delay time has expired, also the out-put takes on the state logical '0'.

Re-trigger

If the input status is set to 'r', the delay time is re-triggered by further falling edges of the input signal or telegrams with the state logical '0'.






Delay of inputs in multiple signals


M 33 16 0 0 0 128 130 toff 10 5 1 0 30 1 128 0 60 100 or Fault P139_130

M 33 16 0 0 0 128 131 toff 10 5 1 0 30 1 128 0 60 100 or Fault P139_131

M 33 16 0 0 0 128 133 5 1 0 30 1 128 0 60 100 or Fault P139_133

Input signal t t t

Output without re-trigger t t t

Output with re-trigger t


Schneider Electric

6.4.11 Switch-on and switch-off delay - 'tonoff'

Function: Switch-on and switch-off delay of binary signals

Availability:


x x x - x






If the input signal changes its state, the delay time is started. If the delay time has expired and the input signal has the same state as at the start of the delay time, also the output takes on that state.

b) State-triggered

The mode ‘state-triggered’ is used in case of command delays or input state 'w' (transient signal). At each input telegram, the delay time is started. If the delay time has expired and the input signal has the same state as at the start of the delay time, also the output takes on that state.

Re-trigger

If the input status is set to 'r', the delay time is re-triggered by further edges of the input signal and/or telegrams with the same status as at the start of the delay.







M 30 60 0 0 0 249 1 tonoff 4 30 1 128 1 10 19 Edge-triggered

M 30 60 0 0 0 249 1 w tonoff 4 30 1 128 1 10 20 State-triggered

C 45 60 0 0 0 249 1 45 1 128 1 10 30 tonoff 5 Command delay

Input signal t t t t

Output without re-trigger t t t t

Output with re-trigger t


Schneider Electric

6.4.12 Impulse function - 'timp'

Function: Monoflop

Availability:


x x x - x

Parameter: Impulse duration in seconds



: Not applicable


If the input signal changes from logical '0' to logical '1', also the output is set to logi-cal '1' and the impulse duration is started. After the impulse duration has expired, the output drops back into the state logical '0'.

b) State-triggered

The mode ‘state-triggered’ is used in case of command delays or input state 'w' (transient signal). An input signal with logical '1' sets the output to logical '1' and starts the impulse duration. After the impulse duration has expired, the output drops back into the state logical '0'.

Re-trigger

If the input status is set to 'r', the impulse duration is re-triggered by further 0-1 edges of the input signal or telegrams with the state logical '1'.


Application: Impulse generation

Particularities: The tolerance is +1 second.

If a quality descriptor has been set in the input signal, there is no impulse.



M 30 60 0 0 0 249 10 timp 10 30 1 128 1 10 40 Edge-triggered

M 30 60 0 0 0 249 20 w timp 10 30 1 128 1 10 41 State-triggered

Input signal

t t t

Output without re-trigger

t t t t t

Output with re-trigger


Schneider Electric

6.4.13 Timer - 'timer'

Function: Timer

Availability:


x x x - x

Parameter: Cycle time in seconds

Status: Input status: ‘e‘ - enabling of timer

Data formats: Input: SPI, DPI, SCO, DCO Output: all


Description: The elements of the data model line have the following functions:

• Input data point: enabling input

• Input function: 'timer' + cycle time parameter

• Output data point: cyclic telegram

An input telegram with status ‘1‘ enables the timer, an input telegram with status '0' disables the timer.

By default, the timer is blocked after initialization. With input status 'e', the timer works without an enabling telegram.

The timer sends cyclically an output telegram. After the configured cycle time has expired, the binary output is switched between logical '0' and logical '1' (bistable mul-tivibrator with duty cycle 1:1).

If the cycle time is set with post-decimal positions, the pre-decimal positions corre-spond to the time for logical '0' and the post-decimal positions correspond to the time for logical '1', one hundred thousandth corresponding to one second (e.g. 9.00001

9 s logical ‘0‘ and 1 s logical ‘1‘).

If the output value is set to a fixed value by the function 'set', the telegram with set data is sent cyclically.

The cause of transmission of output telegrams is 3 - 'spontaneous' for signals and 6 - 'Activation' for commands.

Application: Timer




M 30 60 255 255 255 255 255 e timer 3 30 1 128 0 249 200 start + SPI alternating

M 30 60 0 0 0 249 1 timer 3 30 1 128 0 249 201 set 1 starttele + SPI=1

M 30 60 255 255 255 255 255 e timer 4 30 1 128 0 249 202 set 1 start + SPI=1

M 30 60 255 255 255 255 255 e timer 5 45 1 128 0 249 203 set 1 start + single command=1

M 30 60 255 255 255 255 255 e timer 600 ## 1 128 0 249 250 set 20 cy cl. general interrogation


Schneider Electric

6.4.14 Cycle supervision - 'cycsup'

Function: Supervision of cyclic signal updating

Availability:


x x x - x

Parameter: Supervision time in seconds


Data formats: Input: all Output: all, or depending on output function


Description: The input signal is processed and its format is converted as per default. If within the specified time window, no input telegram is received, the input is set to 'not topical'. This state is transferred to the output data by default output processing or calling the optional output function.

Application: Supervision of cyclically updated signals


Example (telecontrol line):

6.4.15 Input information of select function - 'sel', 'case', 'deflt'

The functions 'sel' and 'case' must only be used in connection together with the output function 'swi'; for de-tails, see section 6.5.14.

Beside its use in the switch function, the input function 'deflt' can also be used separately for initializing in-puts,

6.4.16 Inputs of the output function D-Flip-Flop - 'set', 'res', 'dat', 'clk'

The functions 'set', 'res', 'dat' and 'clk' must only be used together with the output function D flip-flop, 'ffq'; for details, see section 6.5.15.

6.4.17 Inputs of the output function invalid control - 'sig', 'con'

The functions 'sig' and 'con' must only be used together with the output function invalid control, 'ivcon'; for details, see section 6.5.17.

6.4.18 Inputs of the interlocking functions - 'cmd', 'req', 'enon', 'enoff', 'send', 'conf'

The functions 'cmd', 'req', 'enon', 'enoff', 'send' and 'conf' must only be used together with the output func-tions 'lock' or 'elock'; for details, see section 6.5.16.


M 30 60 0 0 0 249 50 cy csup 30 30 1 128 1 10 50 Cy cle superv ision 30s


Schneider Electric

6.5 Output-related functions

6.5.1 Overview

The following output functions are implemented:

Setting functions set - Setting the output value settc - Setting the cause of transmission of the output telegram setcmd - Setting the output value and cause of transmission = 6, 'Activation' setcon - Setting the output value and cause = 7, 'Confirmation of activation' settrm - Setting the output value and cause = 10, 'Activation termination' pulse - Setting the qualifier of command

Setting of quality de-scriptors

setnt - Setting of 'not topical' setbl - Setting of 'blocked' setsb - Setting of 'substituted' setiv - Setting of 'invalid' setov - Setting of 'overflow' setqds - Setting of the quality descriptor byte setca - Setting of 'preset' (counters) setcy - Setting of 'carryover' (counters)

Logic or - OR operation of inputs nor - NOR operation of inputs and - AND operation of inputs nand - NAND operation of inputs iff - Equivalence function xor - Exclusive OR dynor - Dynamic OR bs - Bitstring synthesis bs32 - Synthesis bitstring of 32 bits

Arithmetic sum - Sum of input values diff - Difference of input values prod - Product of input values quot - Quotient of input values

Attenuation of measured values

db - Deadband function (threshold processing) dbi - Integrated deadband function avg - Average value calculation

Selecting function switch - Switch function

Flip-flop

ffq - D flip-flop

Interlocking lock - Interlocking function elock - Advanced interlocking function

Quality descriptors

ivcon - Invalid control


Schneider Electric

6.5.2 Setting the output value - 'set'

Function: Setting the output to a constant value

Availability:


x x x x x

Parameter: Output value


Data formats: Input, output: all data formats

Description: Depending on the data format, output data are set to the parameter value.

Application: Decoding functions, setting of output value in connection with comparing functions

Particularities: Not only the information bits are set, but all output data, e.g. 8 bits in case of SCO. Thus, also qualifiers can be set. In case of data formats INT32BS8 and FP32BS8, only the integer or floating point value is set.

For outputs with setting function, an output telegram is generated for each input tele-gram.


Conversion of one regulating step command into two single commands to different addresses.

6.5.3 Setting the cause of transmission of the output telegram - 'settc'

Function: Setting the cause of transmission to a constant value

Availability:


x x x x x

Parameter: Cause of transmission



Description: The cause of transmission is set to the parameter value.

Application: Generation of command confirmations from return info telegrams

Particularities: For outputs with setting function, an output telegram is generated for each input tel-

egram.


Command confirmation ACTTERM positive for the LED reset command, derivation from return info





M 31 60 0 0 0 160 19 31 1 128 134 160 19 Return info of LED reset

M 31 60 0 0 0 160 19 iftc 12 45 1 128 134 160 19 settc 10 ACTTERM positiv e


Schneider Electric

6.5.4 Setting data and cause of transmission - 'setcmd', 'setcon', 'settrm'

Function: Setting the output and the cause of transmission

Availability:


x x x x x

Parameter: Output value



Description: Depending on the data format, output data are set to the parameter value and cause of transmission:

setcmd - Cause of transmission = 6, 'Activation' setcon - Cause of transmission = 7, 'Activation confirmation' settrm - Cause of transmission = 10, 'Activation termination'

Through the combined setting functions the processing in the logic with 2 lines is spared.

Application: Conversion of messages into commands or command confirmations

Particularities: For outputs with setting function, an output telegram is generated for each input tel-egram.


Derivation of a regulating step command from two SPI


M 30 60 0 0 0 249 1 ifeq 1 47 1 128 0 248 57 setcmd 1 'Low er' command

M 30 60 0 0 0 249 2 ifeq 1 47 1 128 0 248 57 setcmd 2 'Higher' command


Schneider Electric

6.5.5 Setting the impulse duration in commands - 'pulse'

Function: Setting the qualifier of commands

Availability:


x x x x x

Parameter: Value for qualifier of command


Data formats: Output: SCO, DCO, RCO

Description: The impulse duration of commands is set as follows:

In the commands SCO, DCO, and RCO, the qualifier of command (QOC) is set with the range 0 – 3:

- QOC = 0 – no definition - QOC = 1 – short command duration - QOC = 2 – long command duration - QOC = 3 – persistent command

Application: Setting the impulse duration in commands



6.5.6 Setting of quality descriptors – 'setbl', 'setnt', 'setsb', 'setiv', 'setov', 'setqds', 'setca', 'setcy'

Function: Setting of quality descriptors

Availability:


x x x x x

Parameter: Value for the quality descriptor to be set


Data formats: All data formats with quality descriptors

Description: setbl - Setting of 'blocked' setnt - Setting of 'not topical' setsb - Setting of 'substituted' setiv - Setting of 'invalid' setov - Setting of 'overflow' setqds - Setting of the quality descriptor byte setca - Setting of CA (preset) in counters setcy - Setting of CY (carryover) in counters

The quality descriptors are set to the defined value.

Application: Manipulation of quality descriptors

Particularities: In contrast to the setting functions for data and cause of transmission, here the old/new comparison is used to identify changes.


C 45 60 0 0 0 242 69 pulse 1 45 1 128 134 242 69 Short command duration

C 46 60 0 0 0 242 71 pulse 2 46 1 128 134 242 71 Long command duration


Schneider Electric

6.5.7 Logical operations - 'or', 'nor', 'and', 'nand', 'iff', 'xor'

Function: Logical operation of binary signals

Availability:


x x x x x


Status: Input: ‘w‘ - transient signal, output: ‘r‘ - reset telegram

Data formats: Input: SPI, DPI, SCO, DCO, RCO; optional bit field indication, length of bit field 1, 2 bits, target bit = 0 Output: SPI, DPI

Bit field: Applicable, length of bit field 1 or 2 bits, target bit = 0

Description: Logical operation:

or - OR operation nor - NOR operation and - AND operation nand - NOT AND operation iff - Equivalence xor - Exclusive OR operation

A logical operation is characterized by the same output address, type identification and logical function for all related inputs.

Processing takes place in two steps:

1. Each input is processed through implicit format conversion or an input function (e.g. 'not'), with optional indication of a bit field. The resulting output data format is a single- or double-point information (SPI or DPI).

2. Calculation of the logical operation:

When a logical operation is calculated, internal processing is always single-pole – irrespective of the output data format SPI or DPI. This means, that in double-point signals, the states '01' and '00' are interpreted as logical '0' and the states '10' and '11' as logical '1'. The DPI output of the operation cannot assume the states '00' or '11'.

Using the input comparing functions 'cmpxx', you can control which input states are processed with logical '0' or logical '1'.

In all logical operations by default the operation-dependent calculation of quality de-scriptors is used. Thereby, the output of an OR operation will be set to logical '1' and valid if at least one input is logical '1' and valid. Similarly, the output of an AND oper-ation will be set to logical '0' and valid if at least one input is logical '0' and valid.

However, input quality descriptors can also be combined by an OR operation.

Transient signals are processed in group signals just as in single signals. Addition-ally, processing is done with negated input data. The generation of a reset telegram is also possible.

Application: Generation of multiple signals

Particularities: Inputs do not need to immediately follow each other in the data model.


Schneider Electric

Examples:

Combining of starting signals to a general starting (telecontrol lines)

Cascaded logical operations (logic)

The gates are combined via memories, so that processing is done internally within the logic. If the outputs of upstream gates are needed outside the logic, status 'm' must be removed. The output gates will still remain connected via the same device and data point address. Output telegrams will return to the logic via the ker-nel.


M 30 60 0 0 0 160 64 30 1 128 134 160 102 or Start phase A

M 30 60 0 0 0 160 65 30 1 128 134 160 102 or Start phase B

M 30 60 0 0 0 160 66 30 1 128 134 160 102 or Start phase C

M 30 60 0 0 0 160 67 30 1 128 134 160 102 or Start phase N

D DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 STAT FKT PAR ST_LN_ZI DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 GR STAT FKT PAR Meldung

I 30 64 0 0 0 1 1 30 56 0 0 0 1 1 m nand E1

I 30 64 0 0 0 1 2 30 56 0 0 0 1 1 m nand E2

I 30 64 0 0 0 1 3 not 30 56 0 0 0 1 1 m nand E3

I 30 65 0 0 0 1 4 30 56 0 0 0 1 2 m and E4

I 30 65 0 0 0 1 5 not 30 56 0 0 0 1 2 m and E5

I 30 66 0 0 0 1 6 30 56 0 0 0 1 3 or E6, A

I 30 56 0 0 0 1 1 30 56 0 0 0 1 3 or A

I 30 56 0 0 0 1 2 30 56 0 0 0 1 3 or A

&

& >1

A

E1

E2

E3

E4

E5

E6


Schneider Electric

6.5.8 Dynamic OR operation - 'dynor'

Function: OR operation with change message

Availability:


x x x x x



Data formats: Input: SPI, DPI, SCO, DCO, RCO; optional bit field indication, length of bit field 1, 2 bits, target bit = 0 Output: SPI, DPI

Bit field: Applicable, length of bit field 1 or 2 bits, target bit = 0

Description: The dynamic OR is, in principle, an OR operation with the following additional func-tion:

If the output is logical '1' and another input changes from logical '0' to logical '1', the output is first signaled with a logical '0' and then with a logical '1'.

The time tag of the 1-0 edge corresponds to the time of the event. The time tag of the successive 0-1 edge corresponds to the time of the event plus the configured duration of transient signals.

Application: Generation of special multiple signals


In combination with the 'dynor' function, no transient reset telegrams can be gener-ated (output status 'r').

Examples:

Generation of a multiple signal for a communication error with message in case of change


M 33 10 0 0 0 128 64 5 1 0 30 1 128 10 60 100 dy nor Fault P139_64

M 33 10 0 0 0 128 65 5 1 0 30 1 128 10 60 100 dy nor Fault P139_65

M 33 10 0 0 0 128 66 5 1 0 30 1 128 10 60 100 dy nor Fault P139_66

M 33 10 0 0 0 128 67 5 1 0 30 1 128 10 60 100 dy nor Fault P139_67

M 33 10 0 0 0 128 68 5 1 0 30 1 128 10 60 100 dy nor Fault P139_68

M 33 10 0 0 0 128 69 5 1 0 30 1 128 10 60 100 dy nor Fault P139_69


Schneider Electric

6.5.9 Bitstring, bitstring of 32 bits - 'bs', 'bs32'

Function: Synthesis of bitstrings

Availability:


x x x x x



Data formats: Input: all, the bit field must be specified at the input Output: function 'bs32': BS32,

function 'bs': all data formats

Bit field: Mandatory

Description: Assignment of bit field/bit field of 32 bits

The criteria for bitstring processing are the same output address and the same bit-string function for all related inputs.

In principle, processing itself is similar to logical operations, with the exception that bit fields are moved instead of combined.

The output quality descriptor is the result of the OR operation of the input quality de-scriptors.

Application: Compressing function



Starts bitstring


M 30 60 0 0 0 160 64 0 1 0 33 1 128 134 160 106 bs32 Start phase A

M 30 60 0 0 0 160 65 0 1 1 33 1 128 134 160 106 bs32 Start phase B

M 30 60 0 0 0 160 66 0 1 2 33 1 128 134 160 106 bs32 Start phase C

M 30 60 0 0 0 160 67 0 1 3 33 1 128 134 160 106 bs32 Start phase N


Schneider Electric

6.5.10 Arithmetic functions - 'sum', 'diff', 'prod', 'quot'

Function: Arithmetic operation

Availability:


x x x x x



Data formats: Input: INT16, INT32, FP32, BCR32 Output: INT16, INT32, FP32, BCR32


Description: Calculation of the arithmetic function:

sum - Sum of input values diff - Difference of input values prod - Product of input values quot - Quotient of input values

Calculation takes place internally in floating point format with double precision. If the number range of the output format is exceeded, the overflow bit or carryover bit (counters) is set.

The output quality descriptor is the result of the OR operation of the input quality de-scriptors.

Application: Arithmetic calculations of measurement and counter values


Examples:

Total power


M 36 64 0 0 0 248 89 34 1 128 134 248 200 sum Pow er 1

M 36 65 0 0 0 248 89 34 1 128 134 248 200 sum Pow er 2

M 36 66 0 0 0 248 89 34 1 128 134 248 200 sum Pow er 3


Schneider Electric

6.5.11 Threshold processing (deadband) - 'db'

Function: Threshold processing

Availability:


x x x x x

Parameter: Deadband value


Data formats: Output: INT16, INT32, FP32


Description: An output telegram is generated if the amount of change – compared to the last value transmitted – is greater than the deadband value.

Application: Attenuation of measured values




M 36 60 0 0 0 5 41 mult 1706 34 1 128 1 248 80 db 85 IA all MV

M 36 60 0 0 0 6 41 mult 1706 34 1 128 1 248 81 db 85 IB 240% NV = 4095

M 36 60 0 0 0 7 41 mult 1706 34 1 128 1 248 82 db 85 IC threshold 5% NV

M 36 60 0 0 0 5 43 mult 1706 34 1 128 1 248 83 db 85 VA-N

M 36 60 0 0 0 6 43 mult 1706 34 1 128 1 248 84 db 85 VB-N

M 36 60 0 0 0 7 43 mult 1706 34 1 128 1 248 85 db 85 VC-N


Schneider Electric

6.5.12 Deadband integrated - 'dbi'

Function: Threshold processing by integration

Availability:


x x x x x

Parameter: Deadband value




Description: If the deviation of a received measured value from the last measured value transmit-ted exceeds the deadband value, the received measured value is transmitted imme-diately, otherwise it is only updated in the memory.

Deviations of the current measured value from the last measured transmitted value are added cyclically and appropriately signed. If the amount of total changes ex-ceeds the deadband value, the measured value is transmitted and the value of total changes is set to zero.

The cycle time of the deadband integrated processing can be configured.





M 36 60 0 0 0 5 41 mult 3416 34 1 128 2 248 80 dbi 171 IA all MV

M 36 60 0 0 0 6 41 mult 3416 34 1 128 2 248 81 dbi 171 IB 120 %NV = 4095

M 36 60 0 0 0 7 41 mult 3416 34 1 128 2 248 82 dbi 171 IL3 DBI 5% NV

M 36 60 0 0 0 5 43 mult 3416 34 1 128 2 248 83 dbi 171 VA-N

M 36 60 0 0 0 6 43 mult 3416 34 1 128 2 248 84 dbi 171 VB-N

M 36 60 0 0 0 7 43 mult 3416 34 1 128 2 248 85 dbi 171 VC-N


Schneider Electric

6.5.13 Average value calculation - 'avg'

Function: Average value calculation

Availability:


x x x x x

Parameter: Calculation interval in seconds




Description: Processed measured values are not transmitted spontaneously. Instead, the current measured value is added every second. If the value changes several times within one second, the average value of those changes is used for addition.

At the end of the calculation interval, the average value is calculated by means of dividing the sum by the length of the interval.

If the average value has changed, a telegram is transmitted.




1/4 hour average value


M 36 60 0 0 0 7 43 36 1 128 3 248 80 av g 900 1/4 hour av erage v alue


Schneider Electric

6.5.14 Selecting function (switch) - 'swi'

Function: 1 out of N selection of signals via control inputs

Availability:


x x x x x

Parameter: For input functions 'sel' and 'case': input number


Data formats: Input: sel - SPI, or bit field of 1 bit length case - all data formats

deflt - all data formats

Output: The input format of the inputs 'case' or 'deflt' must be convertible into the output format through default conversion.

Bit field: Applicable, in case of 'sel', length of bit field 1 bit, target bit = 0

Description: The selection function can have the following input functions:

sel - Selection input case - Data input deflt - Default input

The data input 'case x', for which the related selection input 'sel x' is logical '1', is connected through to the output. If several selection inputs are active, the first one becomes effective according to notation.

If no selection input is active, the default input is connected through to the output. The default input can be assigned to an input telegram via the input address, or it can be initialized with a fixed value via the parameter. If this value shall be used as the default value, the input address is set to an address not used in the system (dummy address).

Data inputs are processed via default conversion, with the selection of a bit field, if applicable.

Application: Selection of busbar voltage

Particularities: If no active selection input with good quality is found, but instead an active input with set quality descriptor is found, this latter input is used. The quality descriptor of the selection input is copied into the output value.



M 30 60 0 0 0 60 1 sel 1 34 1 128 1 10 12 sw i Selection V1



M 36 64 0 0 0 242 86 case 1 34 1 128 1 10 12 sw i V1

M 36 65 0 0 0 242 86 case 2 34 1 128 1 10 12 sw i V2

M 36 66 0 0 0 242 86 case 3 34 1 128 1 10 12 sw i V3

M 34 60 0 0 0 0 255 deflt 0 34 1 128 1 10 12 sw i Default = 0


Schneider Electric

6.5.15 Flip-flop (output Q) - 'ffq'

Function: Bistable multivibrator

Availability:


x x x x x



Data formats: Inputs: SPI, DPI, SCO, DCO, RCO, length of bit field 1 bit

Output: SPI, DPI

Bit field: Applicable, length of bit field 1 bit, target bit = 0

Description: The processed information can have the following input functions:

set - Setting input res - Resetting input

dat - Data input clk - Clock input

Unnecessary inputs can be omitted.

Processing:

If the setting input = 1, the output is set to 1.

If the resetting input = 1, the output is set to 0.

If the clock input = 1, the output is set to the value of the data input.

Priority: The setting input prevails over the resetting input, and the resetting input prevails over the data input.

Quality and time tag are taken from the triggering input.

Application: Signal storage, state machines

Examples:


M 30 60 0 0 0 249 1 set 30 1 128 0 249 8 ffq Setting input

M 30 60 0 0 0 249 2 dat 30 1 128 0 249 8 ffq Clock input

M 30 60 0 0 0 249 3 clk 30 1 128 0 249 8 ffq Data input

M 30 60 0 0 0 249 4 res 30 1 128 0 249 8 ffq Resetting input


Schneider Electric

6.5.16 Interlocking functions - 'lock', 'elock'

Function: Locking of switchgear units

Availability:


- x - - -



Data formats: Inputs: cmd - DCO req - BS32 enon - SPI, DPI enoff - SPI, DPI send - SPI, DPI ('elock' only) conf - SPI, DPI ('elock' only)

Output: DCO


Description: When receiving the announcement of a switching operation (select command or re-quest for SI check), the interlocking function decides on the basis of the states of the enabling signals 'enon' or 'enoff', whether a switching command is emitted or not. The telegram exchange for switching operations with station interlocking is described in section 8.

The interlocking function processes the following input information:

cmd - Switching command from the command source enon - Enable condition for the close command, enoff - Enable condition for the open command req - Request telegram for checking the station interlocking in case of local

control send - Send telegram ('elock' only) conf - Confirmation telegram ('elock' only)

The output of the interlocking function is the switching command to the device, with the output function 'lock' or 'elock'.

The conditions for the command enabling, 'enon' and 'enoff', are created by up-stream logical operations. They are updated by process messages during runtime, so that in case of a switching operation, no further calculations are required.

For the output function 'elock', after receiving the select command, additionally, first the send telegram (input 'send') is generated and the confirmation telegram (input 'conf') is received, then the actual command procedure is started with the select command. The same procedure is executed after receiving the request for checking the station interlocking in case of local control. This procedure can include further checks before the switching operation, e.g. checks of the communication with all de-vices involved in interlocking.

Application: Locking of switching devices



Schneider Electric

Examples (station interlocking):

Default interlocking function

Advanced interlocking function

D DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 STAT FKT PAR ST_LN_ZI DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 GR STAT FKT PAR Signal

I 46 60 0 0 0 242 65 cmd 46 60 0 0 0 242 65 lock Command

I 30 57 0 0 0 0 1 enon 46 60 0 0 0 242 65 lock Enable close cmd

I 30 57 0 0 0 0 2 enoff 46 60 0 0 0 242 65 lock Enable open cmd

I 33 60 0 0 0 242 116 req 46 60 0 0 0 242 65 lock Req. SI check

D DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 STAT FKT PAR ST_LN_ZI DT DEV DPA4 DPA3 DPA2 DPA1 DPA0 GR STAT FKT PAR Signal

I 46 60 0 0 0 242 67 cmd 46 60 0 0 0 242 67 elock Command

I 30 57 0 0 0 0 3 enon 46 60 0 0 0 242 67 elock Enable close cmd

I 30 57 0 0 0 0 4 enoff 46 60 0 0 0 242 67 elock Enable open cmd

I 33 60 0 0 0 242 116 req 46 60 0 0 0 242 67 elock Req. SI check

I 30 57 0 0 0 0 5 send 46 60 0 0 0 242 67 elock Send telegram

I 30 57 0 0 0 0 6 conf 46 60 0 0 0 242 67 elock Confirmation tele


Schneider Electric

6.5.17 Invalid control - 'ivcon'

Function: Setting the signal quality 'invalid'

Availability:


x x x x x



Data formats: Input: con: SPI, bit field length 1 bit sig: all

Output: all

Bit field: Applicable, in case of 'con', length of bit field 1 bit, target bit = 0

Description : With the function 'ivcon', the quality bit 'invalid' of a signal is set, based on a control input. If the control input is active, the qualifier 'invalid' of the output signal is set. The inputs of the function are the following:

sig - Signal input con - Control input

Application: Setting of the quality 'invalid' for signals in case of a signaling voltage failure.




M 31 60 0 0 0 242 1 sig 31 1 128 0 242 1 iv con Signal input:DEV001

M 30 60 0 0 0 249 5 con 31 1 128 0 242 1 iv con Control input:M005






Schneider Electric

6.6 Status information

6.6.1 Input status information

Sta

tus Function and description

Lo

gic

SI

Lin

e

Ma

ste

r

Devic

e

w Signals reported in active state only (transient signal)

For signals marked with this status, the internal state is reset after the output telegram has been generated; for details, see section 7.6.

Note: In contrast to IEC 60870-5-103 and to the information given in device address lists, according to IEC 60870-5-104, all protection signals from the device are reported as coming and going.

x x x x x

b Initialization with quality descriptor 'substituted'

Data points marked with a 'b' in their input status are initialized with quality descriptor 'substituted' at startup. Additionally, the descriptor 'substituted' is set if in the case of transient signals (input status 'w') the state is reset internally; for details, see section 7.6..

x x x x x

n Setting and signaling with quality descriptor 'not topical'

Status 'n' can be used if the signal is to be sent with the quality descriptor 'not topical' in case of a coming communication error, and without 'not topical' in case of a going com-munication error. Typically, this applies to signals of connected devices not included in the general interrogation.

- - x - -

u Chatter suppression

The chatter suppression is used as described in section 7.7.

x x x - x

c Sending of command confirmation 'Activation confirmation'

After receiving the command, it is confirmed by the 'Activation confirmation'.

x x x x x

t Sending of command confirmation 'Activation termination'

After receiving the command, it is confirmed by the 'Activation termination'.

x x x x x

x Command procedure 'Direct execute'

At the input, the command procedure 'Direct execute' is expected.

x x x - -

s Command procedure 'Select and execute'

At the input, the command procedure 'Select and execute' is expected.

x x x - -

p Bypass

This double command is not included in the check of control uniqueness.

x x x - -

r Re-trigger

With the time functions 'ton', 'toff', 'tonoff', and 'timp', delays and impulse durations are re-triggered by further rising edges or by telegrams with active state, respectively.

x x x - x

e Enabling of timer

This status information has the effect that the timer starts without an enabling telegram.

x x x - x


Schneider Electric

6.6.2 Output status information S

tatu

s Function and description

Lo

gic

SI

Lin

e

Ma

ste

r

Devic

e

r Reset telegram for transient signals

Many network control systems cannot process transient information. Therefore, there is the possibility to transmit a telegram with reset data for transient signals.

x x x x x

c Cyclic transmission

Data points for which this status is set are reported with the configured cycle time.

- - x - -

f Force

If this status is set, for each input telegram an output telegram is generated, irrespective of whether or not there has been a change of data or quality descriptors.

x x x x x

q Quiet

If this status is set, for the data point concerned, no spontaneous output telegrams are generated.

- - x - -

m Memory

Output telegrams of a data point marked ‘m’ are returned to input processing through the internal queue. The cascading of logical operations can thus be quickly achieved.

x x - - -

b Blocked

At startup, the data point market with ‘b’ is initialized with signal/command blocking. Signals with this status are reported with the quality descriptor 'blocked'.

- - x - -

x Command procedure 'Direct execute'

At the output, the command procedure 'Direct execute' is applied; for details, see sec-

tion 7.2.2.

x x x - -

s Command procedure 'Select and execute'

At the output, the command procedure 'Select and execute' is applied; for details, see

section 7.2.2.

x x x - -

z Zero value suppression

For data points with output status 'z', output telegrams are transmitted with '0' if the value is less than the value configured at parameter 'Threshold value zero suppression'.

x x x x x

h Increasing priority

ASDUs normally transmitted via the measured value queue and marked with this status, are transmitted via the queue for binary signals instead.

- - x - -

l Decreasing priority

ASDUs normally transmitted via the queue for binary signals and marked with this sta-tus are transmitted via the measured value queue instead.

- - x - -

u Blocking of monitor direction

An output marked 'u' has the effect that in the telecontrol line concerned, the monitoring and control direction is set off-line or on-line, in analogy to IEC 60870-5-103. In case of blocking, the triggering message is the last message transmitted.

- - x - -


Schneider Electric

7 Special functions of program objects

7.1 Priority-controlled data transmission

7.1.1 Function

The following table shows the program objects into which priority-controlled data transmission is imple-mented:


- - x x -

At the IEC 60870-5-104 interface, input and output telegrams are written into queues, before they are pro-cessed and sent, respectively.

Depending on their IEC 60870-5-104 type identifiers, input and output telegrams are assigned queue priori-ties. Queue priorities are, in descending order:

1. Commands 2. Binary signals and measured values in floating point format (ASDUs 13,14, and 36) 3. Measured values in integer format (ASDUs 9, 10, 11, 12, 34 und 35)

When telegrams are read, the queue with the highest priority is queried first. The queue with the next priority is queried if the queue queried so far is empty.

Queues can work in two modes:

1. Normal mode All telegrams are saved in the queue in the order of arrival.

2. Overwrite mode At arrival of a new telegram in the queue, it is checked if the signaled data point already exists in the queue. If yes, that queue entry is overwritten. Thus, each data point exists only once in the queue.

By default, measured value queues work in overwrite mode. The other queues work in normal mode.

Queue overflow

If a queue in monitoring direction overflows, a buffer overflow message is generated and the oldest tele-grams are deleted until 20% of the queue is empty; for details, see section 10.3.4.

7.1.2 Possibilities of engineering

The priority in monitoring direction can be influenced by the output status in the data model.

Output status ‘h‘ - increasing priority

Telegrams with measured value priority are transmitted via the queue for binary signals. This status should be applied if in telecontrol lines, for instance the fault location has been specified as a low-priority ASDU 9, 10, 11, 12, 34, or 35. With status 'h', the telegram is transmitted with the priority of bi-nary signals, and measured values in the queue are prevented from being overwritten.

Output status ‘l‘ - decreasing priority

Telegrams with priority of binary signals are transmitted via the measured value queue. This status should be applied if measured operating values are transmitted as floating point values (ASDUs 13,14, or 36). Measured values are thus attenuated by overwriting in the queue and no longer hinder the transmission of binary signals.


Schneider Electric

7.2 Command processing

7.2.1 Function

The following table shows the program objects into which command processing is implemented:


x x x - -

Command processing applies to all process commands (data types 45 to 51), in IEC 60870-5-104 addition-ally to type identifications with time tag (58 to 64).

The IEC 60870-5-101 and -104 standards define two different command procedures:

• 'Direct execute'

• 'Select and execute' (or SBO - select before operate)

The system-internal default command procedure is 'Direct execute'.

The default command procedure on telecontrol lines at the IEC 60870-5-104 interface is 'Direct execute', as well. However, a parameter allows for switching to 'Select and execute'. In addition, the command proce-dure can be set internally, and for the IEC 60870-5-104 interface separately for each command, via status information ‘x‘ - 'Direct execute', and 's‘ - 'Select and execute'.

In case of switchgear control with station interlocking, double commands (data type 46) are transmitted inter-nally with the 'Select and execute' procedure.

During command processing, procedures are supervised and command confirmations are assigned by means of the originator address.

Before a command is processed, it is checked if all conditions for command execution are fulfilled. If this is not the case, a negative 'Activation confirmation' is sent to the sender. The conditions for a negative confir-mation are:

• the command does not exist in the data model,

• the maximum number of running command procedures has been exceeded,

• a command with the same address is still being processed,

• with check of control uniqueness: another double command is still being processed.

In addition, a command is rejected without confirmation if it is too old.

Command processing for telecontrol line

Processing is handled in analogy to logic / station interlocking.

A command is converted into an output command via the data model in command direction. Also, input and output commands aresent to the command processing module and a command procedure is opened. In the command procedure, command confirmations ACTCON and ACTTERM (if applicable) are supervised.

Command confirmations from the device are not included into the data model in monitoring direction. In-stead, they are converted into sender command confirmations via the command processing module. If the

Command confirmation

Engineered command

confirmation

Data model Monitoring direction

Command processing

Input command

Output command(s) to device

Command confirmation from device

Return info from device

Input command

Output command

Data model

Control direction

Return info

Device


Schneider Electric

command confirmations from the device time out, a negative command confirmation is generated after a set supervision time period.

7.2.2 Possibilities of engineering

Command processing allows the conversion of the two command procedures.

Output status ‘s‘: 'Direct execute' 'Select and execute'

In this case, first the execute command is converted into a select command. Only after the select confirma-tion has been received from the target device will the execute command be sent.

For commands from the telecontrol line in mode 'with station interlocking', the following special feature ap-plies: If for a double command, status information 's' in mode 'with station interlocking' is defined, for the command concerned is not routed to the station interlocking. It is thus possible to bypass interlocking.

Output status ‘x‘: 'Select and execute' 'Direct execute'

In this case, the select command is confirmed on the input side and only the execute command is converted and sent to the target device.

For commands from the telecontrol line in mode 'with station interlocking', the following special feature ap-plies: If for a double command, status information 'x' in mode 'with station interlocking' is defined, the com-mand is not routed to the station interlocking. It is thus possible to bypass interlocking.

Engineering command confirmations

If the recipient of commands does not send all requested command confirmations, they can be engineered. This can be done by additionally converting the command return info into a command confirmation. Such en-gineered confirmations are also processed via the command processing module.

7.3 Check of control uniqueness

The following table shows the program objects into which the check of control uniqueness is implemented:


x x x - -

Enabling this function allows to monitor whether in the program object concerned, only one double command is being processed. All other commands are rejected and a negative confirmation is transmitted. Additionally, a message 'Violation of check of control uniqueness' is generated; for details, see section 10.3.4.

The check of control uniqueness function generates an 'order running' message that remains active as long as a command is being processed. Further conditions can be included into the check of control uniqueness using an input, e.g. 'order running' messages of other telecontrol lines or connected devices.

All double commands marked by input status 'p' (bypass) are not included into the check of control unique-ness.

If switchgear units are controlled with station interlocking, it is ensured that in the device concerned only one double command at a time is executed.

7.4 Transmission in reverse direction

The following table shows the program objects into which transmission in reverse direction is implemented:


- - x x x

All 'process information in monitoring direction' (ASDUs 1–19, 21, 30-37) can be transmitted in control direc-tion, and all 'process information in control direction' (ASDUs 45-51, 58-64) can be transmitted in monitoring direction.

For transmission in reverse direction, the same process functions (logical operations, arithmetic, etc.) are available as in normal direction.

Data are managed internally in the same way as in the logic, i.e. via a virtual logical device. The telecontrol line registers the VLD to the kernel as a device. Thereby the kernel addresses commands to the VLD and


Schneider Electric

thus to the peer station via the telecontrol line. All messages in control direction are given the device address of the VLD.

M* = Messages in control direction C* = Commands in monitoring direction

In the IEC 60870-5-104 master station bus, connected devices by default are registered to the kernel as far devices. The same applies to the device interface. The device is also registered to the kernel.

In the telecontrol line, a command processing module for processing of command procedures has been im-plemented for the VLD. It realizes the same functions as the one in control direction, i.e. it converts com-mand confirmations and supervises command procedures. The conversion of command procedures 'Direct execute' to 'Select and execute' and vice versa is also possible.

System commands (general interrogation, counter read, read command, and test command) from the kernel to the VLD are also supported.

All signaling information from the VLD is transmitted to the kernel with quality descriptor 'not topical' if the link to the peer station is disturbed. When the link is re-established, a general interrogation is sent to the peer station and thus the current status (without 'not topical') is restored.

For transmission in reverse direction, a group has been implemented in the parameter subset. This allows to set the VLD address and to define whether a general interrogation is sent at re-establishing of the link.

7.5 IEC 60870-5-104 redundant transmission

IEC 60870-5-104 telecontrol lines can be set for two different application cases:

1. Operation at the station bus In this mode, a telecontrol line can communicate with one client only. Redundant transmission is not used.

2. Remote operation In this mode, redundant transmission to up to 8 clients in one redundancy group is supported. Re-dundant transmission is possible in two ways:

a) According to IEC 60870-5-104 Ed. 2 Only one link is active with data transmission enabled, all other links are passive and supervised by test telegrams. Connected clients define with 'Start data transmission', which link is active.

b) Operation of parallel links All links are simultaneously fed with data and commands are received from all links. Clients de-fine which client is active, i.e. which client is allowed to process signals and send commands.

7.6 Treatment of signals reported in active state only (transient signals)

In specific protocols, e.g. IEC 60870-5-103, some binary and analogue signals are only reported in active state. Those signals are called transient signals.

In contrast to the information given in device address lists, according to IEC 60870-5-104, all protection sig-nals from the device are reported as coming and going. However, there are signals from the system or from external devices that are reported as coming only.

Telecontrol Line

Kernel

Commands

Messages

M*

C* C*

M* Virtual logical device

Data model

control direction

Data model monitoring direction

Telecontrol

Line

object



Schneider Electric

Issues at processing

● In case of default processing, signals about processing issues are signaled only once and do not change their state thereafter.

● Some IEC 60870-5-103 protection signals are not included into the general interrogation of devices, so that they remain 'invalid' in the data model after startup.

Input status ‘w‘ – transient signal:

● With this status, the signal is internally reset after the coming message and initialized with 'valid' quality at startup.

Issues at a telecontrol line

● There is no going message at the control center. ● Transient signals are not reported with quality descriptor 'not topical' if the connection to the device is

disturbed.

Output status ‘r‘ – reset telegram

● With this status, a going message is sent after the coming message. The time difference between the messages is configurable, default setting is 0.

Input status ‘n‘ – signaling with 'not topical'

● If the connection to the device is disturbed, signals marked are reported with quality descriptor 'not topical'.

Special treatment with input status ‘b‘ - initialization with 'substituted'

● Signals marked are initialized with quality descriptor 'substituted' and the reset telegram is also re-ported with 'substituted'.

7.7 Chatter suppression

The following table shows the program objects into which chatter suppression is implemented:


x x x - x

The following figure illustrates the function:

In the data model the input status 'u' must be set for data points to activate chatter suppression.

If the number of transitions within the test interval exceeds the threshold value, then chatter suppression will be applied to the data point and the data point will be reported with quality 'blocked'. After that, no further


Schneider Electric

transitions are reported within the blocking time. When the blocking time has elapsed, transitions are counted again during the test interval.

If the number of transitions within the test interval is less than or equal to the threshold value, then chatter suppression will be reset for the data point. The data point will be reported with quality 'not blocked'. If the number of transitions exceeds the threshold value, the blocking time restarts.

The chatter suppression status is reported device-related by a single-point signal. This information is set when the first chatter suppression is applied in the device, and it is reset when the chattering of the last sig-nal ends.

7.8 Signal and command blocks in the data model

The following table shows the program objects into which signal and command blocks are implemented:


- - x - --

Blocks in the data model are set/reset through bitstring commands. These commands are confirmed with ACTCON. However, there are no data points, which could be acknowledged or queried, reflecting the status of the blocks.

The blocking command allows to select the data model (monitoring/control direction), the type of block (sig-nal/command block) and the addressing mode (individual/group block).

Thus, blocks in the data model can be set selectively for

• individual data points,

• groups of data points,

• device or ASDU addresses.

Blocks are always set in the output data model and encoded according to internal or IEC 60870-5-104 ad-dressing.

When a signal block is set, blocked data points are reported via the telecontrol line with quality descriptor 'blocked'. After that, for blocked data points, no spontaneous messages are sent anymore. However, even with a set signal block the data model is updated.

In general interrogations, the current status is reported with quality descriptor 'blocked'.

When the signal block is removed, data points are reported via the telecontrol line with the status 'not blocked'

Commands to data points with a set signal block are rejected with an ACTCON negative command confirma-tion.

Telegrams for setting and resetting blocks are described in section 10.3.4.2.

Input data model

monitoring direction

(Dev, DPAddr)

Output data model

control direction

(Dev, DPAddr)

Output data model

monitoring direction

Input data model

control direction

(ASDU, ObjAddr)

Signal blocks

Command blocks

Internal addressing Addressing acc. to IEC 60870-5-104


Schneider Electric

8 Station interlocking

8.1 Operation with station interlocking

In the device setting file, operation with station interlocking is enabled by the following parameter:

Parameters/Function parameters/Control/MAIN/SI active USER: Yes

This parameter sets the command procedure for switching devices (double command) in the device to 'Se-lect and execute' and also enables the station interlocking function on the communication module.

On the communication module, the operation mode with station interlocking can be set by starting the station interlocking program object when configuring the device in X30 Studio. In this operation mode, double com-mands are treated at the communication module as follows:

• The command procedure from the telecontrol lines to the device is set to 'Select and execute'.

• The commands are addressed on the communication module directly to the device. However, in or-der to check interlocking conditions, they are transmitted to the device via station interlocking.

8.2 Control procedures with station interlocking

8.2.1 Remote control with station interlocking

8.2.1.1 Enabling by station interlocking

Telecontrol line Station interlocking Device (CPU)

Select command, DT=46 Station interlocking check

Select command, DT=46 Bay interlocking check

ACTCON+ Select, DT=46


Req. SI check, DT=33

Execute command, DT=46 Station interlocking check

Execute command, DT=46 Bay interlocking check

ACTCON+ Exec., DT=46 ACTCON+ Exec., DT=46

Return of control state, DT=31

ACTTERM+ Sel., DT=46 ACTTERM+ Sel., DT=46

8.2.1.2 Blocking by bay interlocking 1st or 2nd check


Select/Exec. comm., DT=46 Station interlocking check

Select/Exec. command, DT=46 Bay interlocking check

ACTCON- Sel./Exec., DT=46

ACTCON- Sel./Exec., DT=46

Blocking signal BI, DT=33

8.2.1.3 Blocking by station interlocking 1st check


Select command, DT=46

Station interlocking check

ACTCON- Select, DT=46

Blocking signal SI, DT=30


Schneider Electric

8.2.1.4 Blocking by station interlocking 2nd check


Select command, DT=46 Station interlocking check

Select command, DT=46 Bay interlocking check



Req. SI check, DT=33

Execute command, DT=46

Station interlocking check

ACTCON- Execute, DT=46


Cancel command, DT=46

ACTCON+ Cancel, DT=46

8.2.2 Local control with station interlocking

8.2.2.1 Enabling by station interlocking


Local command

Bay interlocking check

Station interlocking check Req. SI check, DT=33

Execute command, DT=46


ACTCON+ Exec., DT=46

Return info of control state, DT=31

ACTTERM+ Sel., DT=46

8.2.2.2 Blocking by station interlocking


Local command


Station interlocking check Req. SI check, DT=33

Cancel command, DT=46

ACTCON+ Cancel, DT=46



Schneider Electric

8.3 System architectures with station interlocking

8.3.1 Station interlocking in central substation unit

The central substation unit can be a MiCOM S30 or an Easergy MiCOM P30 relay. In this configuration, all central functions are managed by this unit. The HMI and the telecontrol center use this unit to communicate with the devices.

The central unit also contains the interlocking logic and an interlocking function 'lock' or 'elock' for each switching device to be switched with interlocking. The interlocking logic receives the states of all switching devices and calculates the enabling signals 'enable on' ('enon') and 'enable off' ('enoff') for the interlocking functions.

A switching command sent from the HMI or the telecontrol center reaches the interlocking function and is ex-ecuted or rejected depending on the enabling signals.

In case of local control, the field unit sends a request for a station interlocking check to the corresponding interlocking function. If the operation is allowed, the station interlocking issues the switching enable by means of a switching command.

In this configuration, the command procedure 'Select and execute' must be used at the station bus for con-trolling the switchgear units with interlocking.

Gateway/central unit

HMI

Field unit 2 Field unit 1 Field unit n

Telecontrol center

lock lock lock

Interlocking logic

enon, enoff

Control state

Control state Control state

lock lock

Station bus

…


Schneider Electric

8.3.2 Station interlocking in field unit

The field units contain an interlocking function ('lock' or 'elock') for each switching device to be switched with interlocking. One field unit at the station bus contains the central station interlocking function. As an IEC 60870-5-104 client, it receives the states of all relevant switching devices. The interlocking logic calcu-lates the enabling signals 'enable on' ('enon') and 'enable off' ('enoff') and sends them to the interlocking functions in the field units.

A switching command from the HMI or the control center is sent directly to the addressed field unit, where the enable signal is checked by the respective interlocking function and the command is either rejected or executed.

In case of local control, in the field unit the request for station interlocking check is processed by the respec-tive interlocking function. If the operation is allowed, the station interlocking internally issues the switching enable by means of a switching command.

The command procedure at the station bus for controlling switchgear units with station interlocking can be set at the telecontrol lines. The command procedure required for interlocking, 'Select and execute', is only used within the field units.

Field unit with central function

HMI

Field unit 2 Field unit 1

Gateway

Telecontrol center

lock

lock

lock

Interlocking logic

enon, enoff

enon, enoff

Control state

Control state

lock

lock lock

Station bus

…


Schneider Electric

9 Checking and test functions

9.1 Permanent logging functions

Information about serious errors affecting the functionality of the software system is stored on the Ethernet board for subsequent evaluation. Those errors can lead to a system failure, which is assigned on the CPU to matrix point Operation/Cyclic measurements/Log. state signals/IEC/Comm. link faulty.

Additionally, an alarm is triggered at the CPU.

The program objects of the Ethernet board log the following information:

• Central error file The startup of the Ethernet board is documented in a central log file. Fatal errors that could lead to a program termination are also recorded into this central log file by all program objects.

• Data model log files Every program object reading a data model file writes its own log file that informs about errors oc-curred in the data model. Based on those log files, engineering errors can be identified and elimi-nated.

In addition, the following log files are written, facilitating error search in case of problems:

• Log file for control with interlocking In this log file, the station interlocking program object logs all control procedures with interlocking. Based on those log files, it is possible to determine whether the control procedure was error-free and why switching operations were rejected by the interlocking.

The following log files can be useful for error clarification by experts:

• Log file for startups of device interface In this log file, software startups of the communication module – in interaction with the CPU – are stored.

• Log file for startups of cyber security module

• Log files for telegram traffic with CPU The telegram traffic is stored in hexadecimal format in a ring memory consisting of 2 files with max. 0.5 MB capacity each.

Logging is done on the RAM disk of the Ethernet board. Please note that with each restart of the device, logs are lost.

9.2 Configurable logging functions

The program objects of the Ethernet board can log important information about their processes, so that pro-cesses can be analyzed afterwards. To this aim, program objects write a configurable number of files of con-figurable size. The file names are indexed. If the maximum number of files is reached, the index is set to 0 and the oldest file is overwritten, so that a ring memory is created.

The log files are stored at the RAM disk of the communication module. For example, for long-term record-ings, the number and size settings of the log files allow to control how much storage space is available for each program, and to avoid that information is lost if the RAM disk is full.

The log functions have only little influence on the performance of the program objects, so that they can be used in continuous operation without any problems.

For each program object, logging can be enabled or disabled via parameters of the ‘Operating test’ setting group. The following information is logged:

• Telegram traffic All telegram traffic to and from the kernel or, if applicable, via the interface to a communication server or at the communication interface to the outside (e.g. IEC 60870-5-104) is logged.

• Processing functions All information about processing functions, e.g. logic functions or command procedures, is logged.

Additionally, it is possible to set whether logging shall take place in decimal or in hexadecimal format.


Schneider Electric

10 Internal telegram interface

10.1 Telegram format and encoding

10.1.1 Introduction

Depending on the configuration, the system architecture can be very simple with only one telecontrol line, or very complex with maximum configuration. To engineer extensive communication functions, relevant ele-ments of the program objects' internal telegram interfaces are described here.

The internal telegram structure and the encodings used for type identification and cause of transmission are based on IEC 60870-5-104. Telegram elements are allocated as follows:

IEC 60870-5-104 Length Internal telegram Length

Type identification 1 Data type 2

Variable structure qualifier 1 Number of information ob-jects

1

Cause of transmission 1 Cause of transmission 1

Originator address 1 Originator address 2

Common address of ASDU 2 Device address 2

Information object address 3 Data point address 8

Time tag 7 Time tag 8

Notes:

• Internally, only single telegrams are used, i.e. the number of information objects is always 1.

• Of the 8 bytes of the data point address, 5 bytes are used.

10.1.2 Data types used

Coding Designation Data format

30 Single-point information with time tag SPI

31 Double-point information with time tag DPI

32 Step position information with time tag VTI

33 Bitstring of 32 bits with time tag BS32

34 Measured value, normalized value with time tag INT32

35 Measured value, scaled value with time tag INT32

36 Measured value, floating point value with time tag FP32

37 Integrated totals with time tag BCR32

38 Event of protection equipment with time tag DPI

70 End of initialization BS8

45 Single command with time tag SCO

46 Double command with time tag DCO

47 Regulating step command with time tag RCO

48 Set point command, normalized value with time tag

INT32BS8

49 Set point command, scaled value with time tag INT32BS8

50 Set point command, floating point value with time tag

FP32BS8

51 Bitstring of 32 bits, command with time tag BS32

100 General interrogation command with time tag BS8

101 Counter interrogation command with time tag BS8

102 Read command with time tag -

103 Synchronization command -

104 Test command with time tag BS16

Notes:

• All internal telegram types have a time tag.

• 16 bit measured values and set point values acc. to IEC 60870-5-104 are used internally with 32 bit.


Schneider Electric

10.1.3 Cause of transmission

The following table shows the causes of transmission used:

Coding Designation

1 Cyclic

2 Background scan

3 Spontaneous

4 Initialized

5 Requested

6 Activation

7 Positive activation confirmation

8 Deactivation

9 Positive deactivation confirmation

10 Positive activation termination

11 Return info caused by a remote command

12 Return info caused by a local command

20 General interrogation

38 Counter read

Notes:

• The positive/negative bit (P/N) is used according to standard.

• The test bit (T) is used according to standard.

10.1.4 Data formats

Principally, the data formats used are identical to those described in standard IEC 60870-5-101, section 7.2.6 “Information elements”. Differences are described in the following table:

Data format Designation IEC 60870-5-101

SPI Single-point information 7.2.6.1

DPI Double-point information 7.2.6.2

VTI Value with transient state indication 7.2.6.5

SCO Single command 7.2.6.15

DCO Double command 7.2.6.16

RCO Regulating step command 7.2.6.17

BS8 Bitstring of 8 bits (1)

BS16 Bitstring of 16 bits (2)

BS32 Bitstring of 32 bits 7.2.6.13

INT32 Signed integer value of 32 bits (3)

FP32 Floating point value of 32 bits 7.2.6.8

BCR32 Binary counter reading of 32 bits 7.2.6.9

INT32BS8 Integer value of 32 bits with bit field of 8 bits

BS8: 7.2.6.39

FP32BS8 Floating point value of 32 bits with bit field of 8 bits

7.2.6.8 + 7.2.6.39

Notes:

(1) - BS8 := 8BS1[1..8]<0..1> (IEC 60870-5-4 type 6) (2) - BS16 := 16BS1[1..16]<0..1> (IEC 60870-5-4 type 6) (3) - INT32 := I32[1..32]<-231..+231-1> (IEC 60870-5-4 type 2.1) (4) - In the internal telegram format, a separate byte is used for quality descriptors.


Schneider Electric

10.1.5 Quality descriptors

Quality descriptors for all data types are encoded according to IEC 60870-5-101, section 7.2.6.3:

B7 B6 B5 B4 B3 B2 B1 B0

IV NT SB BL 0 0 0 OV

IV - valid/invalid NT - topical/not topical SB - not substituted/substituted BL - not blocked/blocked OV - no overflow/overflow

10.1.6 Device addresses of program objects

The following table shows the addressing of the internal program objects:

Program object Device address

Kernel 1

Logic 5

Station interlocking 6

Device interface 15

Master station bus 1 16

Master station bus 2 17

IEC 60870-5-104 client 1 24

IEC 60870-5-104 client 2 25

Telecontrol line 1 32





IEC 60870-5-104 server 40

10.2 Telegram exchange with the device

10.2.1 Telegrams from protection part

10.2.1.1 Status

The scope of information depends on the type of protection and can be found in the address list provided for each device type. In general, all information that can be transmitted via the IEC 60870-5-103 interface is available.

During engineering with X30 Studio, all relevant status messages are offered for selection.

The internal data type used is 30 – single-point information with time tag.

10.2.1.2 Commands

In the protection part, all commands known from IEC 60870-5-103 are available. However, they are not ad-dressed via IEC 60870-5-103 function type and information number, but via the matrix point address.

Command Type Inf Data

Auto-recloser ON/OFF 015 064 Binary data: 1 – ON, 0 - OFF

Teleprotection ON/OFF 015 008

Device on-line/off-line 003 030

Reset of indications 021 010

Parameter subset 003 062 Parameter subset number 1...4

During engineering with X30 Studio, all relevant commands are offered for selection.

The internal data type used is 48 – set point command of 32 bit, normalized value with time tag


Schneider Electric

Apart from that, all matrix points marked as writable in the address list ('Type ID Write' unequal to 00) can be written with the same data type.

10.2.1.3 Measured values

The scope of available measured values depends on the device type and can be found in the address list provided for each device type. They are addressed via the matrix point address, too.

During engineering with X30 Studio, all relevant measured values are offered for selection.

The data type used is 36 – measured value, short floating point value

10.2.1.4 Energy counters

The following counters from the address list are available:

Counters Type Inf Data

MAIN: Act.energy outp.prim 005 061 Signed counter value of 31 bits

MAIN: Act.energy inp. prim 005 062

MAIN: React.en. outp. prim 005 063

MAIN: React. en. inp. prim 005 064

The data type used is 35 – measured value of 32 bits, scaled value

10.2.2 Telegrams from control part

10.2.2.1 Switchgear units

The control state of switchgear units is signaled with data type 31 – double-point information with time tag. Devices are controlled by telegrams of type 46 – double command. The following table shows the ad-dressing of switchgear units:

External device

Type Inf Message

Inf Command

DEV01 242 01 65

DEV02 242 03 67

DEV03 242 05 69

DEV04 242 07 71

DEV05 242 09 73

DEV06 242 11 75

DEV07 242 13 77

DEV08 242 15 79

DEV09 242 17 81

DEV10 242 19 83

Depending on the device type and the bay type selected, there can be less switchgear units present.

10.2.2.2 Single-point information and single commands

The following table shows the addressing of single-point information of function group SIG_1. Single-point

information is signaled with data type 30 – single-point information with time tag.

Signal Type Inf

S001 249 01

S002 249 02

S003 249 03

… … …

S040 249 40

Device types P132, P433, P435, P631, P632, P633 have max. 12 single-point signals. Device types P139, P439, and P532 have max. 64 single-point signals.


Schneider Electric

The following table shows the addressing of single commands of function group CMD_1. Single commands

are sent with data type 45 – single command.

Command Type Inf

C001 249 129

C002 249 130

C003 249 131

… … …

C026 249 154

Device types P132, P433, P435, P631, P632, P633 have max. 12 single commands. Device types P139, P439, and P532 have max. 26 single commands.

10.2.2.3 Pulse counter values

The following table shows the addressing of pulse counter values of function group Count. Counter values

are sent with data type 37 – counter value with time tag.

Counters Type Inf

Counter 1 248 1

Counter 2 248 2

Counter 3 248 3

Counter 4 248 4

10.2.2.4 Multiple signaling

Single-point information is signaled with data type 30 – single-point information with time tag. Confirma-tions of group signals are sent with data type 45 – single command.

Signal Type Inf

Group signal 1 248 65

Storing of group signal 1 248 66

Confirmation of group signal 1 248 67

Group signal 2 248 68

Storing of group signal 3 248 69

Confirmation of group signal 4 248 70

10.2.2.5 Circuit breaker trip signal

Circuit breaker trip signals are sent with data type 30 – single-point information with time tag.

Signal Type Inf

CB tripped 248 71

10.2.2.6 System information

The following table shows the addressing of system information, data type 33 – bitstring.

Signal name Type

Inf Data

Bay status 248 112 0 BS1 BS2 BS3

Type of Bay 248 113 Bay type number

Interlock violation 248 115 DCX 00 242 CMD

Request of station interlocking check 248 116 DCO 00 242 CMD


Schneider Electric

Bay status BS1

7 6 5 4 3 2 1 0

| | | | | | | | 0 1 x x x x 0 1 Signal/measured value release 0 1 x x x x 1 0 Signal/measured value block 0 1 x x 0 1 x x Command enable 0 1 x x 1 0 x x Command block 0 1 0 1 x x x x Device not blocked/faulty 0 1 1 0 x x x x Device blocked/faulty 0 1 x x x x x x Physical addressing

Bay status BS2

7 6 5 4 3 2 1 0

| | | | | | | | x x x x x x 0 1 Operation with bay interlocking x x x x x x 1 0 Operation without bay interlocking x x x x 0 1 x x Operation with station interlocking x x x x 1 0 x x Operation without station interlocking x x 0 1 x x x x Enabling of remote control x x 1 0 x x x x Blocking of remote control 0 1 x x x x x x Enabling of local control 1 0 x x x x x x Blocking of local control

Bay status BS3

7 6 5 4 3 2 1 0

| | | | | | | | 1 0 x x x x x x Command blocking because of monitoring number of

CB operations

Interlock violation, request of station interlocking check

CMD: Command information number

DCO: Double command, consisting of

S/E QU DCS

S/E: QU: DCS:

0 = execution, 1 = selection 0 = termination of switching command after position status signal 1 = short time (1s), 2 = long time (20s) 3 = persistent command 01 = OFF, 10 = ON, 00,11 = inadmissible

DCX: Like DCO, most significant bit set for indicating an interlock vi-olation

Example: DCO=02H becomes DCX=42H

The following table shows the addressing of system information, data type 30 – double-point information.

Signal name Type Inf Data

Command execution in progress 248 117 1 - command in pro-gress, 0 - command not in progress


Schneider Electric

10.2.3 Signals from the communication module to the device

10.2.3.1 Permanently assigned signals from the communication module to the device

Besides commands, also message telegrams can be sent to the device. They are assigned to matrix points in the device and are available for processing.

The following table shows the permanently assigned signals on the communication module:

Signal in device Description

Operation/Cyclic measurements/Log. state sig-

nals/IEC/Comm.link faulty

Internal malfunction of the commu-nication module, e.g. because of engineering or parameterization er-rors.


nals/IEC/Port A faulty

Fault of port A network connection


nals/IEC/Port B faulty

Fault of port B network connection

10.2.3.2 Assignable signals from the communication module to the device

The following table shows the addressing of assignable signals on the communication module:

Signal in device Type Inf

Operation/Cyclic measurements/Log. state signals/MAIN/Communication

error (1)

128 00

Operation/Cyclic measurements/Log. state signals/MAIN/SI commu.

disturbed 248 212

Operation/Cyclic measurements/Phys. state signals/VINP/Input 1

state (3) 0 1

Operation/Cyclic measurements/Phys. state signals/VINP/Input 2

state 0 2

… … … Operation/Cyclic measurements/Phys. state signals/VINP/Input 64

state 0 64

Operation/Cyclic measurements/Log. state signals/VINP/Input 1

faulty (4) 0 1

Operation/Cyclic measurements/Log. state signals/VINP/Input 2

faulty 0 2

… … … Operation/Cyclic measurements/Log. state signals/VINP/Input 64

faulty 0 64

(1) Communication error

To this matrix point, depending on the configuration, all information about the communication status should be assigned via a logical operation, e.g. an OR operation of communication errors of the engineered telecon-trol lines. See also section 10.3.3.

(2) SI communication error

To this matrix point, the communication error message of the line to the device where the station interlocking is running should be assigned. Setting 'SI communication error' has the effect that in the device, control is performed without SI and that the interlocking logic is switched to operation without SI.

(3) Virtual inputs

Via matrix points Operation/Cyclic measurements/Log. state signals/VINP/Input xx

state, any binary signals available at the communication module can be assigned for processing in the de-

vice.


Schneider Electric

(4) Virtual inputs faulty

The matrix points Operation/Cyclic measurements/Log. state signals/VINP/Input xx

faulty are not specifically assigned. They are set if in the appropriate state messages, the quality is 'not

topical' or 'invalid'.

10.2.4 Settings from the device for the communication module

10.2.4.1 Permanently assigned settings from the device for the communication module

The following table shows the permanently assigned signals from the device to the communication module:

Signal in device Description

Parameters/Config. parameters/IEC/General enable USER If 'No' is set, IEC 60870-5-104 communication is blocked by disabling the IEC 60870-5-104 server and all clients; for de-

tails, see sections 10.3.5 and

10.3.7. Operation/Cyclic measurements/Log. state sig-

nals/MAIN/Subst. interl. act.

Depending on the state, a command for station interlock-ing status ON/OFF is gener-ated; for details, see section

10.3.8.

10.2.4.2 Assignable settings from the device for the communication module

The following table shows the addressing of single-point signals with system information:

Signal name Type Inf Data

Command execution in progress 248 117 1 - command in pro-gress, 0 - command not in progress


nals/IEC/Control blocking

248 177 1 – blocking 0 – no blocking


nals/IEC/Command blocking



nals/IEC/Sig./meas.val.block



nals/IEC/Command block. EXT



nals/IEC/Sig./meas.block EXT


Blocking and activation of telecontrol lines can be engineered user-specifically. The required telegrams are described in section 10.3.

10.3 System telegrams of the communication module

10.3.1 Introduction

Program objects send and receive system telegrams for controlling and monitoring communication functions. Some of these system telegrams may be of interest to the user, since they contain important information about the state of the system and the program objects' communication interfaces. System telegrams are transmitted after a general interrogation to the respective program object and spontaneously at a change of state.


Schneider Electric

10.3.2 Telegram interface of the kernel

Signal in device DT Dev Data point address Data

Sum fault of internal program objects 30 1 17 1 - faulty, 0 - not faulty

A sum fault is set if at least 1 program object is faulty. A program object is faulty if it terminates itself e.g. be-cause of data model or parameterization errors.

The sum fault status of internal program objects is permanently assigned to matrix point Operation/Cy-

clic measurements/Log. state signals/IEC/Comm.link faulty; for details, see section

10.2.3.1.

10.3.3 Telegram interface of the device interface


SNTP/IRIG-B time synchronization faulty 30 15 FF01H 1 - faulty, 0 - not faulty

If parameter Parameters/Config. parameters/IRIGB/IRIGB/General enable USER is set to

'No', the state of the SNTP reception is signaled, otherwise the state of the IRIG-B reception is signaled.

10.3.4 Telegram interface of the IEC 60870-5-104 telecontrol line

10.3.4.1 Status signals and commands


Processing status message 33 32-36 5 See (1)

Processing status command 51 32-36 6 See (2)

Telecontrol line status message 33 32-36 8000H See (3)

Telecontrol line status command 51 32-36 8800H See (4)

Double command procedure in progress 30 32-36 11 1 - yes 0 - no

Violation of control uniqueness check 30 32-36 12 1 - yes

Telegram buffer overflow message 30 32-36 16 1 – overflow (5)

Chatter suppression signal 30 32-36 10000H + device address

1 - ON 0 - OFF

(1) Processing status message

7 6 5 4 3 2 1 0

Data byte 1 0 0 START CMD SIG

Data byte 2 - 4 0 0 0 0 0 0 0 0

SIG: Status of monitoring direction 01 = Monitoring direction off-line

10 = Monitoring direction on-line

CMD: Status of control direction 01 = Control direction off-line 10 = Control direction on-line

START: Status of startup 01 = Startup terminated 10 = Startup in progress

(2) Processing status command:

7 6 5 4 3 2 1 0

Data byte 1 0 0 0 0 CMD SIG

Data byte 2 - 4 0 0 0 0 0 0 0 0

SIG: Status command for monitoring direction 00 = No change


Schneider Electric

01 = Setting monitoring direction off-line 10 = Setting monitoring direction on-line

CMD: Status command for control direction 00 = No change

01 = Setting control direction off-line 10 = Setting control direction on-line

(3) Telecontrol line status message:

7 6 5 4 3 2 1 0

Data byte 1 0 0 STO ONL PRO

Data byte 2 0 0 0 B 0 0 S K

Data byte 3 - 4 0 0 0 0 0 0 0 0

PRO: Status projected/not projected 01 = Channel not projected 10 = Channel projected

ONL: Status on-line/off-line 01 = Channel off-line 10 = Channel on-line

STO: Status faulty/not faulty 01 = Not faulty 10 = Faulty

Faulty state of IEC 60870-5-104 telecontrol line

If a station is operated with only one IEC 60870-5-104 link, the status of the line corresponds to the status of this link. If the telecontrol system is operated redundantly, up to 8 clients per line can be connected. In that case, the status of the line is faulty if all links are faulty, and the status of the line is not faulty if at least one IEC 60870-5-104 link is operational. For details, see section 10.3.5.

Failure reason:

K = 1 - Communication server link faulty S = 1 - Static communication fault B = 1 - Fault caused by remote station permanently unready to take over

(4) Telecontrol line status command

7 6 5 4 3 2 1 0

Data byte 1 0 0 0 0 ONL PRO

Data byte 2 - 4 0 0 0 0 0 0 0 0

PRO: Setting of projected/not projected 00 = No change 01 = Setting of not projected (not used) 10 = Setting of projected (not used)

ONL: Setting of on-line/off-line 00 = No change 01 = Setting of off-line 10 = Setting of on-line

(5) Telegram buffer overflow

A telegram buffer overflow occurs if a telegram to be sent cannot be queued before sending because the queue is full. In that case, older telegrams at the head of the queue are deleted until 20% of storage is avail-able again, and the triggering message is buffered at the end of the queue.

If the message 'telegram buffer overflow' is signaled via the telecontrol line (engineering), it is buffered at the head of the queue, at the position where the telegrams were deleted. A telegram buffer overflow is only sig-naled as coming.


Schneider Electric

10.3.4.2 Commands for setting data model blocks

Commands for setting blocks in the data model are sent with data type 51 – bitstring command of 32 bits. The data point address is structured as follows:

7 6 5 4 3 2 1 0

Byte 0 (low) ASDU/device address low

Byte 1 ASDU/device address high

Byte 2 KE DM TY AD 0 0 DCO

0 Byte 3 (high) 00H

Data point address byte 2: mode

KE Identifying bit for data model blocks 0 - Not used here 1 - Data model blocking command

DM Data model identifier 0 - Data model in monitoring direction 1 - Data model in control direction

TY Type of block 0 - Signal block 1 - Command block

AD Addressing identifier of block 0 - Individual block 1 - Group block

DCO Blocking command 01 - Resetting of block 10 - Setting of block

Data are set depending on the addressing identifier (AD):

Data with addressing identifier AD = 0 - individual blocks

7 6 5 4 3 2 1 0

Data byte 0 (low) Data point/object address byte 0 (low)

Data byte 1 Data point/object address byte 1

Data byte 2 Data point/object address byte 2

Data byte 3 (high) Data point/object address byte 3 (high)

If data bytes 0 to 3 are equal to 0, the block for all data points of the addressed device / the common address of ASDU is set, respectively reset.

Data with addressing identifier AD = 1 - group blocks

7 6 5 4 3 2 1 0

Data byte 1 (low) Group low

Data byte 2 Group high

Data byte 3 Number of bits group (1 … 16)

Data byte 4 (high) Start bit group (0 … 31)

In case of group blocks, filtering occurs by a group identifier (e.g. bay number) that is encoded in a bit field in the data point or information object address.


Schneider Electric

10.3.5 Telegram interface of the IEC 60870-5-104 server


Global status signal of server 33 40 5 See (1)

Global status command to server 51 40 6 See (2)

Channel 0 status IEC104 link 0 33 40 8000H See (3)


… … … …




… … … …


… … … …



… … … …


(1) Global status signal of IEC 60870-5-104 server

7 6 5 4 3 2 1 0

Data byte 1 0 0 0 0 0 0 ONL

Data byte 2 - 4 0 0 0 0 0 0 0 0

ONL: Status on-line/off-line 01 = Server off-line 10 = Server on-line In case of off-line status, IEC 60870-5-104 communication is disabled at the network interfaces, i.e. no

links are accepted by the clients.

(2) Global status command to IEC 60870-5-104 server

7 6 5 4 3 2 1 0


Data byte 2 - 4 0 0 0 0 0 0 0 0

ONL: Status on-line/off-line 01 = Setting the server off-line 10 = Setting the server on-line

(3) Status signal of IEC 60870-5-104 link

7 6 5 4 3 2 1 0

Data byte 1 0 0 STO ONL PRO

Data byte 2 - 4 0 0 0 0 0 0 0 0

PRO: Status projected/not projected 01 = Channel not projected 10 = Channel projected

ONL: Status on-line/off-line 01 = Channel off-line 10 = Channel on-line

STO: Status faulty/not faulty 01 = Not faulty 10 = Faulty


Schneider Electric

10.3.6 Telegram interface of the IEC 60870-5-104 master station bus


Processing status message 33 10/11 5 See (1)

Processing status command 51 10/11 6 See (2)

Status signal of server link 33 10/11 8000H + server address (3)

See (4)

(1) - Data of processing status message

7 6 5 4 3 2 1 0

Data byte 1 0 0 0 0 CMD SIG

Data byte 2 - 4 0 0 0 0 0 0 0 0

SIG: Status of monitoring direction 01 = Monitoring direction off-line

10 = Monitoring direction on-line

CMD: Status of control direction 01 = Control direction off-line 10 = Control direction on-line

(2) Data of processing status command:

7 6 5 4 3 2 1 0

Data byte 1 (low) 0 0 0 0 CMD SIG

Data byte 2 - 4 (high) 0 0 0 0 0 0 0 0

SIG: Status command for monitoring direction 00 = No change

01 = Setting monitoring direction off-line 10 = Setting monitoring direction on-line

CMD: Status command for control direction 00 = No change

01 = Setting control direction off-line 10 = Setting control direction on-line

(3) Server address

The server address corresponds to the internal device address under which the server is listed by the com-munication kernel.

1. IEC 60870-5-104 master (address 16): server addresses 64 to 95 (40H-5FH) 2. IEC 60870-5-104 master (address 17): server addresses 96 to 127 (50H-6FH)

(3) Data of status signal of IEC 60870-5-104 link

7 6 5 4 3 2 1 0

Data byte 1 0 0 STO ONL ANG

Data byte 2 - 4 0 0 0 0 0 0 0 0

ANG: Status registered/not registered 01 = Not registered 10 = registered ONL: Status on-line/off-line 01 = Server off-line 10 = Server on-line STO: Status faulty/not faulty

01 = Not faulty 10 = Faulty


Schneider Electric

Failure reason:

K = 1 - Communication server link faulty S = 1 - Static communication fault B = 1 - Server permanently unready to take over

10.3.7 Telegram interface of the IEC 60870-5-104 client


Global status signal of server 33 24/25 5 See (1)

Global status command to server 51 24/25 6 See (2)

(1) Global status signal of IEC 60870-5-104 server

7 6 5 4 3 2 1 0


Data byte 2 - 4 0 0 0 0 0 0 0 0

ONL: Status on-line/off-line 01 = Server off-line 10 = Server on-line In case the status is off-line, IEC 60870-5-104 communication is disabled at the network interfaces,

i.e. no links are established to servers.

(2) Global status command to IEC 60870-5-104 server

7 6 5 4 3 2 1 0


Data byte 2 - 4 0 0 0 0 0 0 0 0

ONL: Status on-line/off-line 01 = Setting the server off-line 10 = Setting the server on-line

10.3.8 Telegram interface of the logic/station interlocking

Signal in device DT DEV Data point address Data

Status signal of station interlocking 33 6 5 See (1)

Status command to station interlocking 51 6 6 See (2)

Double command procedure in progress 30 5/6 11 1 - yes 0 - no

Violation of control uniqueness check 30 5/6 12 1 - yes

Blocking signal of station interlocking 30 6 100H + device address command

1 - ON

Signal of SI blocking cause Station interlocking

30 6 80H + blocking cause Cause of interlock violation (3)

1 – ON

Chatter suppression signal 30 5/6 10000H + device address 1 - ON 0 - OFF

(1) Status of station interlocking

7 6 5 4 3 2 1 0

Data byte 1 0 0 0 0 0 0 STA

Data byte 2...4 0 0 0 0 0 0 0 0

STA: Status of station interlocking 01 = Interlocking OFF

10 = Interlocking ON


Schneider Electric

(2) Status command to station interlocking

7 6 5 4 3 2 1 0

Data byte 1 0 0 0 0 0 0 STB

Data byte 2...4 0 0 0 0 0 0 0 0

STB: Status command to station interlocking 01 = Enabling of interlocking

10 = Enabling of interlocking

(3) Relative addresses for cause of interlock violation

0 - Switching operation not allowed 1 - Enabling signal invalid 2 - No select command before execution 3 - Command procedure still in progress 4 - Negative confirmation of selection 5 - Negative confirmation of execution 6 - Negative confirmation of cancelling 7 - Invalid command telegram 8 - Invalid command confirmation 9 - Timeout of procedure 10 - Engineering error 11 - Enabling (positive)

A cause of interlock violation is only signaled as coming.

Schneider Electric As standards, specifications and designs change from time to time, please ask for contribution 35, rue Joseph Monier – CS30323 of the information given in this publication. F - 92500 Rueil-Malmaison Cedex (France)

Tel: +33 (0)1 41 29 85 00 Fax: +33 (0)1 41 29 71 00 RCS Nanterre 954 503w Capital social 896 313 776 € Design: Schneider Electric ww.schneider-electric.com Photos: Schneider Electric Publication. P30 APPL IEC104_main 06/2018

2

018 S

chn

eid

er

Ele

ctr

ic.

All

rights

re

serv

ed.

easergy micom p30

Documents