Power Grids

RTU500 series - Remote Terminal Units

IEC 61850 Client
Protocol description
Revision

Document identity: 1KGT 150 590 V013 1

Revision: Date: Changes:
0 05/2007 Base version
1 12/2009 Add description of file transfer functionality
Add description IEC 61850 server functionality
2 03/2011 Add description of functional constraint “SP”
Add information about IEC 61850 edition 2
Add description for message filtering
Add information about startup log file
3 11/2012 Update for Release 10.6
Revise document for KEMA Conformance test
Add chapter ‘Conformance Statement’
Add description for command handling
Add description for system commands
Update file transfer description
4 08/2014 Add support of functional constraint SP
Add support of transient attribute [Link]
Revise conversion of quality descriptors
Revise file transfer description for generic IEDs
Add information about NOT TOPICAL inoperable indication
New layout
5 12/2014 Describe file directory path parameter for generic IEDs
Include note about SCL2003 restriction
Add description of high communication load diagnosis message
6 06/2016 Add description of parameter "File search pattern" (PR#22596)
03/2017 Model implementation conformance statement refered to outdated
ICD substation configuration file (PR#26101)
7 08/2017 Include descriptions and conformance statements for IEC 61850 Edi-
tion 2 client
8 03/2018 Chapter System limits updated (PR#22818, #36769)
Disturbance file upload triggered by SPI (PR#33023)
New layout
9 09/2018 Updated chapter ACSI, MICS, PICS, TICS, PIXIT and SICS for IEC
61850 Edition 2 TÜV conformance test (PR#32989)

Corrected table reference in chapter 'Transfer of Disturbance Data

Files' (PR#39445)
10 12/2018 Updated chapter 'System Limits' (PR#39991)
11 03/2020 Introduced originator category for command data points (PR#44609)
10/2020 Command timeout described in chapter 'IEC 61850 Control Models'
and added chapter 'Additional Timeouts' (PBI#168393)
12 07/2021 Introduced new threshold supervision types for MFIs (PI#180244)
09/2021 Updated chapter 'System Events' (PI#181384)
Added chapter 'Setting Group Control', updated chapters 'BSO
- Bit String Output' and 'PIXIT for Setting group control mod-
el' (PI#147351)
Document identity: 1KGT 150 590 V013 1
Revision: Date: Changes:
Chapters 'Authority Control for the whole Substation' and 'IEC 61850
Control Models' updated (PI#183326)
13 12/2021 Updated chapter 'Client/Server Services' (PI#184264)
Updated chapters 'System Limits' and 'PIXIT for Association Mod-
el' (PI#183664)
06/2022 Updated chapters 'System Events' (PI#185935)
Contents

Contents

1 Introduction............................................................................................................................. 5
1.1 Preface........................................................................................................................... 5
1.2 References..................................................................................................................... 5
1.3 Conventions................................................................................................................... 6

2 Physical Layer.........................................................................................................................7

3 Link Layer................................................................................................................................9
3.1 General...........................................................................................................................9
3.2 Client/Server Services................................................................................................... 9

4 Application Layer..................................................................................................................11
4.1 Selection of protocol edition........................................................................................ 11
4.2 Logical Nodes.............................................................................................................. 11

5 Addressing............................................................................................................................ 13
5.1 IEC 61850 Object References.....................................................................................13

6 Monitoring Direction.............................................................................................................15
6.1 General.........................................................................................................................15
6.2 AMI – Analog Measured Information...........................................................................15
6.3 BSI – Bit String Information.........................................................................................17
6.4 DMI – Digital Measured Information............................................................................18
6.5 DPI – Double Point Information.................................................................................. 19
6.6 MFI – Measured Float Information.............................................................................. 20
6.7 ITI – Integrated Totals Information.............................................................................. 22
6.8 SPI – Single Point Information.................................................................................... 23
6.9 STI – Step Position Information.................................................................................. 24

7 Controlling Direction............................................................................................................ 27
7.1 ASO – Analog Setpoint Output................................................................................... 27
7.1.1 ASO – Analog Setpoint Output................................................................... 27
7.1.2 Command Authority..................................................................................... 28
7.1.3 Additional Information.................................................................................. 28
7.2 BSO – Bit String Output.............................................................................................. 29
7.2.1 BSO – Bit String Output.............................................................................. 29
7.2.2 Command Authority..................................................................................... 31
7.2.3 Additional Information.................................................................................. 31
7.3 DCO – Double Command Output............................................................................... 31
7.3.1 DCO – Double Command Output............................................................... 32
7.3.2 Command Authority..................................................................................... 32
7.3.3 Additional Information.................................................................................. 32
7.4 DSO – Digital Setpoint Output.................................................................................... 33
7.4.1 DSO – Digital Setpoint Output.................................................................... 33
7.4.2 Command Authority..................................................................................... 35
7.4.3 Additional Information.................................................................................. 35

1KGT 150 590 V013 1 I

 Contents

7.5 FSO – Floating Point Setpoint Output.........................................................................35

7.5.1 FSO – Floating Point Setpoint Output.........................................................35
7.5.2 Command Authority..................................................................................... 36
7.5.3 Additional Information.................................................................................. 36
7.6 RCO – Regulation Command Output..........................................................................36
7.6.1 RCO – Regulation Command Output..........................................................36
7.6.2 Command Authority..................................................................................... 37
7.6.3 Additional Information.................................................................................. 37
7.7 SCO – Single Command Output................................................................................. 38
7.7.1 SCO – Single Command Output.................................................................38
7.7.2 Command Authority..................................................................................... 39
7.7.3 Additional Information.................................................................................. 39

8 File transfer........................................................................................................................... 41
8.1 Transfer of Disturbance Data Files............................................................................. 41
8.2 File Transfer Configuration.......................................................................................... 42
8.3 Generic IED Type........................................................................................................ 43

9 Internal Functions.................................................................................................................47
9.1 Startup log....................................................................................................................47
9.2 Time Synchronization.................................................................................................. 47
9.3 General Interrogation................................................................................................... 47
9.4 System Events............................................................................................................. 47
9.5 System commands...................................................................................................... 49
9.5.1 Set device out of service.............................................................................49
9.6 Message Filtering.........................................................................................................49
9.7 Command Handling..................................................................................................... 50
9.7.1 IEC 61850 Control Models.......................................................................... 50
9.7.2 Qualifier of Command................................................................................. 52
9.8 IEC 61850 server functionality.................................................................................... 52
9.8.1 Logical Node Physical Health Identification................................................ 53
9.8.2 Time master supervision............................................................................. 53
9.8.3 Redundant physical communication channel supervision........................... 54
9.8.4 Authority Control for the whole Substation..................................................54
9.9 High Communication Load.......................................................................................... 55
9.10 Setting Group Control..................................................................................................55

10 Limits and Recommendations............................................................................................ 57

10.1 System Limits...............................................................................................................57
10.2 Mixed systems............................................................................................................. 57
10.3 Additional Timeouts..................................................................................................... 58

11 Conformance Statements.................................................................................................... 59
11.1 Abstract Communication Service Interface (ACSI)..................................................... 59
11.1.1 ACSI Basic Conformance Statement.......................................................... 59
11.1.2 ACSI Models Conformance Statement....................................................... 59
11.1.3 ACSI Service Conformance Statement....................................................... 61
11.1.4 Specific Communication Service Mapping (SCSM).................................... 63

II 1KGT 150 590 V013 1

Contents

11.2 Protocol Implementation Conformance Statement (PICS).......................................... 64

11.2.1 Basic Profile Conformance.......................................................................... 64
11.2.2 MMS Conformance......................................................................................65
11.3 Model Implementation Conformance Statement (MICS).............................................65
11.3.1 Common Data Class Extensions.................................................................65
11.3.2 Logical Node List.........................................................................................67
11.3.3 LN Group L: System logical nodes............................................................. 67
11.3.4 LN Group L: Logical nodes for interfacing and archiving............................ 69
11.4 Tissues Conformance Statement (TICS).....................................................................69
11.4.1 Mandatory Edition 1 IntOp Tissues............................................................. 70
11.4.2 Optional Edition 1 IntOp Tissues.................................................................72
11.4.3 Mandatory Edition 2 Tissues....................................................................... 72
11.5 Protocol Implementation extra Information for Testing (PIXIT)....................................81
11.5.1 PIXIT for Configuration................................................................................ 81
11.5.2 PIXIT for Association Model........................................................................82
11.5.3 PIXIT for Server model................................................................................82
11.5.4 PIXIT for Dataset model..............................................................................85
11.5.5 PIXIT for Substitution model....................................................................... 87
11.5.6 PIXIT for Setting group control model.........................................................87
11.5.7 PIXIT for Reporting model...........................................................................88
11.5.8 PIXIT for Logging model............................................................................. 93
11.5.9 PIXIT for Generic substation events model.................................................94
11.5.10 PIXIT for Control model...............................................................................94
11.5.11 PIXIT for Time and time synchronization model......................................... 95
11.5.12 PIXIT for File transfer model....................................................................... 96
11.5.13 PIXIT for Service Tracking model............................................................... 97
11.6 SCL Implementation Conformance Statement (SICS)................................................ 97

12 Glossary...............................................................................................................................101

1KGT 150 590 V013 1 III

 Contents

IV 1KGT 150 590 V013 1

Introduction Preface

1 Introduction

1.1 Preface
This document describes the functions of the subdevice communication interface in RTU500 series
according to IEC 61850.

1.2 References
1 IEC 61850-6:2004(E)
Communication networks and systems in substations
Part 6: Configuration description language for communication in electrical substation related to
IEDs
First edition 2004-03
2 IEC 61850-7-1:2003(E)
Communication networks and systems in substations
Part 7-1: Basic communication structure for substation and feeder equipment – Principles and
models
First edition 2003-07
3 IEC 61850-7-2:2003(E)
Communication networks and systems in substations
Part 7-2: Basic communication structure for substation and feeder equipment – Abstract
communication service interface (ACSI)
First edition 2003-05
4 IEC 61850-7-4:2003(E)
Communication networks and systems in substations
Part 7-4: Basic communication structure for substation and feeder equipment – Compatible
logical node classes and data classes
First edition 2003-05
5 IEC 61850-8-1:2004(E)
Communication networks and systems in substations
Part 8-1: Specific communication service mapping (SCSM) – Mappings to MMS (ISO9506-1 and
ISO9506-2) and to ISO/IEC 8802-3
First edition 2004-05
6 User Manual RTUtil500 Release 13 (1KGT151107)
7 RTU500 series Interfaces and Protocols Release 13 (1KGT151104)
8 RTU500 Series Function Description - Part 6: RTU500 functions (1KGT151100)
9 RTU500 Series Function Description - Part 7: Archive functions (1KGT151101)
10 IEC 61850-6:2009(E)
Communication networks and systems for power utility automation
Part 6: Configuration description language for communication in electrical substations related to
IEDs
Edition 2.0 2009-12
11 IEC 61850-7-1:2011(E)
Communication networks and systems for power utility automation
Part 7-1: Basic communication structure – Principles and models
Edition 2.0 2011-07
12 IEC 61850-7-2:2010(E)
Communication networks and systems for power utility automation
Part 7-2: Basic information and communication structure – Abstract communication service

1KGT 150 590 V013 1 5

Conventions Introduction

interface (ACSI)
Edition 2.0 2010-08
13 IEC 61850-7-4:2010(E)
Communication networks and systems for power utility automation
Part 7-4: Basic communication structure – Compatible logical node classes and data object
classes
Edition 2.0 2010-03
14 IEC 61850-8-1:2011(E)
Communication networks and systems for power utility automation
Part 8-1: Specific communication service mapping (SCSM) – Mappings to MMS (ISO 9506-1
and ISO 9506-2) and to ISO/IEC 8802-3
Edition 2.0 2011-06

1.3 Conventions
In this document function codes of data types according to IEC 61850 are marked with brackets:
<Function code>

Bold fonts with the table heading "Parameter name" are references to configuration parameters
in RTUtil500. The parameter is followed by the parameter location where to find this parameter in
RTUtil500. The first element of the parameter location defines the node in the hardware tree on the
left side (e. g. RTU, CMU, line, IED) and the second element defines selected header control tab in
the parameter window on the right side (e. g. general, interfaces, protocol).

Example:

Parameter name Default Parameter location

The tables in the next chapters include lists of the functions, options and message types supported
according to the protocol structure given in IEC 60870-5 (EPA three layer model) for

The tables in the next chapters include lists of the functions, options and message types supported
according to the protocol structure given in IEC 60870-5 (EPA three layer model) for
• the physical layer
• the link layer
• the application layer

This layered model is valid for the protocol IEC 61850.

6 1KGT 150 590 V013 1

Physical Layer

2 Physical Layer
The transmission speed in control and in monitor direction is 10 or 100 Mbit/sec.

For details see RTU500 series Interfaces and Protocols Release 12 (1KGT 150 939).

1KGT 150 590 V013 1 7

 Physical Layer

8 1KGT 150 590 V013 1

Link Layer General

3 Link Layer
3.1 General
The IEC 61850 Client provides support for Edition 1 and Edition 2 Client/Server services as
described in [5] respectively [14]. GSE management and GOOSE services are available for the
Server only. GSSE Services are not implemented.

Services like ‘Sampled Values’ described in IEC 61850-9 are not supported.

3.2 Client/Server Services

The IEC 61850 Client acts in IEC 61850 station bus as Edition 1 or Edition 2 client .

Following services as described in [3] respectively [12] are supported:

IEC 61850-7-2 model IEC 61850-7-2 service SCI support

Server GetServerDirectory
Association Associate X
Abort X
Release X
Logical Device GetLogicalDeviceDirectory
Logical Node GetLogicalNodeDirectory
GetAllDataValues
Data GetDataValues X
SetDataValues X
GetDataDirectory X
GetDataDefinition X
Data Set GetDataSetValues
SetDataSetValues
CreateDataSet
DeleteDataSet
GetDataSetDirectory X
Substitution GetDataValues
SetDataValues
Setting Group Control Block SelectActiveSG X
SelectEditSG
SetSGValues
ConfirmEditSGValues
GetSGValues
GetSGCBValues
Report Control Block Report X
GetBRCBValues X
SetBRCBValues X
GetURCBValues X
SetURCBValues X
Table 1: Supported IEC 61850-7-2 services

1KGT 150 590 V013 1 9

Client/Server Services Link Layer

IEC 61850-7-2 model IEC 61850-7-2 service SCI support

LOG Control Block GetLCBValues
SetLCBValues
GetLogStatusValues
QueryLogByTime
QueryLogAfter
GOOSE SendGOOSEMessage
GetGoReference
GetGOOSEElementNumber
GetGoCBValues
SetGoCBValues
GSSE SendGSSEMessage
GetGsReference
GetGSSEElementNumber
GetGsCBValues
SetGsCBValues
Control Select X
SelectWithValue X
Cancel X
Operate X
CommandTermination X
TimeActivatedOperate
FILE transfer GetFile X
SetFile
DeleteFile
GetFileAttributeValues X
Table 1: Supported IEC 61850-7-2 services

10 1KGT 150 590 V013 1

Application Layer Selection of protocol edition

4 Application Layer

4.1 Selection of protocol edition

The RTU500 series IEC 61850 client and server supports Edition 1 and Edition 2 of the standard.
For each RTU500 series client and server in a configuration the used protocol edition must be
defined. Due to the differences in the data model between Edition 1 and Edition 2 the selected
protocol edition cannot be changed anymore after an SCD import was done or after any data points
are configured for the client or server. So be sure to select the protocol edition first when starting a
configuration.

For details how to select the protocol edition in RTUtil500 see [6].

4.2 Logical Nodes

In IEC 61850 information is grouped according to the process needs in logical nodes. Logical nodes
consist of attributes of common data classes. Conversion of information is done on common data
class basis. This gives the possibility to support also logical nodes probably defined in the future or
for special process purposes.

Compatible logical nodes and data classes can be found in [4] respectively [13].

1KGT 150 590 V013 1 11

Logical Nodes Application Layer

12 1KGT 150 590 V013 1

Addressing IEC 61850 Object References

5 Addressing

5.1 IEC 61850 Object References

For addressing of IEC 61850 object references are used. These references are a concatenation of
the following names (see [2] respectively [11]):

LDName/[Link][&FC]

Abbreviation Name Description

LDName Logical device instance name Unique name of a logical device
LNName Logical node instance name Concatenation of

• LN Prefix
• LN name
• LN Instance number
DataName Name of common data class in logi-
cal node
DataAttribute Attribute name in common data
class
FC Functional Constraint

References can not be modified with RTUtil500. They are always synchronized from a SCD file
to the Excel Import file of RTUtil500 without modifications. The server data points with IEC 61850
objects are defined in the Excel import file only.

The complete engineering process in RTUtil500 is described in [6].

1KGT 150 590 V013 1 13

IEC 61850 Object References Addressing

14 1KGT 150 590 V013 1

Monitoring Direction General

6 Monitoring Direction
6.1 General
In monitoring direction the SCI IEC 61850 supports data transfer by data sets only. That means all
process information to receive must be part of data sets. This particularly applies to the functional
constraint SP (Set Point) that can be used in data sets only. There is no polling functionality
provided to receive set point values in monitoring direction.

The common data classes and data attributes listed in the following chapters are restricted to none
array attribute types only. The SCI IEC 61850 doesn’t support collections of values combined in an
array.

6.2 AMI – Analog Measured Information

Analog process information indicated by integer or floating point values, used as a measured value
from analog inputs.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
INC stVal ST A
ING1 setVal SP A
INS stVal ST A
MV mag.f MX A
SAV instMag.f MX A
SAV instMag.i MX A
SEQ [Link].f MX A
SEQ [Link].f MX A
SEQ [Link].f MX A
SEQ [Link].f MX A
Additional Maximum Value
Maximum Value in the external protocol to be converted to +100 % on
RTU500 series internal communication
Parameter:
Maximum Value (AMI – Protocol Sub Parameter)
[Range: - 2147483648 .. 2147483647]

Minimum Value
Minimum Value in the external protocol to be converted to -100 % on
RTU500 series internal communication.
Parameter:
Minimum Value (AMI- Protocol Sub Parameter)
[Range: -2147483648 .. 2147483647]

Threshold Supervision
Enables the threshold supervision for measured values received from the
external protocol and send on the RTU500 series internal communication.
Parameter:
Threshold Supervision (AMI – Protocol Sub Parameter)

1KGT 150 590 V013 1 15

AMI – Analog Measured Information Monitoring Direction

Threshold Supervision Type

Defines the algorithm used for the threshold supervision of measured val-
ues received from the external protocol.
Parameter:
Threshold Supervision Type (AMI – Protocol Sub Parameter)
[Selection: “Integrated Threshold Supervision” or
“Absolute Threshold Supervision”]

Threshold
Defines the threshold value used for the threshold supervision algorithm.
Parameter:
Minimum Value (AMI- Protocol Sub Parameter)
[Range: 0 .. 100%]

1 Only as part of a receiving data set

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -100% Parameter: Minimum Value
... ...
Range max. +100% Parameter: Maximum Value

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

OV Overflow [Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

16 1KGT 150 590 V013 1

Monitoring Direction BSI – Bit String Information

RTU500 series internal communication Protocol specific

[Link] == TRUE or

[Link] == TRUE
BL Blocked [Link] == TRUE
SB Substituted [Link] == substituted
NT Not Topical [Link] == TRUE
IV Invalid [Link] == invalid or
[Link] == questionable

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous -
Requested -
Interrogated -

6.3 BSI – Bit String Information

Binary process information indicated by 8, 16 or 32 bit.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
ENC1 stVal ST A
ENG1 2 setVal SP A
ENS 1 stVal ST A
INC stVal ST B
ING2 setVal SP B
INS stVal ST B
Additional None

1 Available for IEC 61850 Edition 2 client only

2 Only as part of a receiving data set
Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 Enumeration value 0
... ...
Range max. BSI8: Bit mask of 8 bit; Enumeration value 255
range ... 255
BSI16: Bit mask of 16 bit; Enumeration value 65 535
range ... 65 535
BSI32: Bit mask of 32 bit; Enumeration value 4 294 967 295
range ... 4 294 967 295

Conversion of value (Type B)

1KGT 150 590 V013 1 17

DMI – Digital Measured Information Monitoring Direction

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 0
... ...
Range max. BSI8: Bit mask of 8 bit; 255
range ... 255
BSI16: Bit mask of 16 bit; 65 535
range ... 65 535
BSI32: Bit mask of 32 bit; 4 294 967 295
range ... 4 294 967 295

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

OV Overflow [Link] == invalid

[Link] == TRUE

[Link] == TRUE
BL Blocked [Link] == questionable

[Link] == TRUE

[Link] == TRUE

(only if not invalid IV is set)

SB Substituted [Link] == substituted
NT Not Topical [Link] == questionable

[Link] == TRUE

(only if not invalid IV is set)

IV Invalid [Link] == invalid

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous -
Requested -
Interrogated -

6.4 DMI – Digital Measured Information

Binary process information indicated by 8 or 16 bit used as a measured value from digital inputs in
normalized format.

Mapping of IEC 61850 information to DMIs is by default not enabled in RTUtil500, but supported by
subdevice communication interface IEC 61850. If mapping of DMIs is required please contact ABB
for more detailed information.

18 1KGT 150 590 V013 1

Monitoring Direction DPI – Double Point Information

6.5 DPI – Double Point Information

Binary process information indicated by two bits.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
ACD dirGeneral ST A
ACD dirNeut ST B
ACD dirPhsA ST B
ACD dirPhsB ST B
ACD dirPhsC ST B
DPC stVal ST C
DPS stVal ST C
ENC 1 stVal ST D
ENG1 2 setVal SP D
ENS 1 stVal ST D
Additional None

1 Available for IEC 61850 Edition 2 client only

2 Only as part of a receiving data set
Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Intermediate Unknown
Off Forward
On Backward
Indeterminate Both

Conversion of value (Type B)

RTU500 series internal communication Protocol specific (Attribute value)

Intermediate Unknown
Off Forward
On Backward
Indeterminate -

Conversion of value (Type C)

RTU500 series internal communication Protocol specific (Attribute value)

Intermediate intermediate-state
Off Off
On On
Indeterminate bad-state

Conversion of value (Type D)

RTU500 series internal communication Protocol specific (Attribute value)1

Intermediate Enumeration value 0
Off Enumeration value 1

1KGT 150 590 V013 1 19

MFI – Measured Float Information Monitoring Direction

RTU500 series internal communication Protocol specific (Attribute value)1

On Enumeration value 2
Indeterminate Enumeration value 3

1 Shall be used only for enumerations with up to 4 values.

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

BL Blocked [Link] == TRUE
SB Substituted [Link] == substituted
NT Not Topical [Link] == TRUE
IV Invalid [Link] == invalid or
[Link] == questionable

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous -
Requested -
Interrogated -

6.6 MFI – Measured Float Information

Analog process information indicated by 32 bit used as measured value from analog inputs in float
format.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
ASG setMag.f SP A
CMV [Link].f MX A
CMV [Link].f MX A
DEL [Link].f MX A
DEL [Link].f MX A
DEL [Link].f MX A
DEL [Link].f MX A
MV mag.f MX A
SAV instMag.f MX A
SEQ [Link].f MX A
SEQ [Link].f MX A
SEQ [Link].f MX A
WYE [Link].f MX A
WYE [Link].f MX A
WYE [Link].f MX A
WYE [Link].f MX A
WYE [Link].f MX A

20 1KGT 150 590 V013 1

Monitoring Direction MFI – Measured Float Information

Additional Threshold Supervision

Enables the threshold supervision for measured values received from the
external protocol and send on the RTU500 series internal communication.
Parameter:
Threshold Supervision (MFI – Protocol Sub Parameter)

Threshold Supervision Type

Defines the algorithm used for the threshold supervision of measured val-
ues received from the external protocol.
Parameter:
Threshold Supervision Type (MFI – Protocol Sub Parameter)
[Selection: 'Integrated', 'Integrated (relative)'
'Absolute' or 'Absolute (relative)']

Threshold
Defines the threshold value used for the threshold supervision algorithm.
Parameter:
Minimum Value (MFI- Protocol Sub Parameter)
[Range: 0.0 .. 3.4028 * 1038 or 5 to 100 %]

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -3.41038 -3.41038
...
Range max. + 3.41038 + 3.41038

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

OV Overflow [Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE
BL Blocked [Link] == TRUE
SB Substituted [Link] == substituted
NT Not Topical [Link] == TRUE
IV Invalid [Link] == invalid or
[Link] == questionable

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -

1KGT 150 590 V013 1 21

ITI – Integrated Totals Information Monitoring Direction

RTU500 series internal communication Protocol specific

Cause Spontaneous -
Requested -
Interrogated -

6.7 ITI – Integrated Totals Information

Binary process information indicated by 32 bit as a countered value.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
BCR actVal ST A
BCR frVal ST A
Additional None

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -2147483648 -2147483648
... ... ...
Range max. +2147483647 +2147483647

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

SEQ Sequence number -
CY Carry [Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE
CA Adjusted -
IV Invalid [Link] == invalid or
[Link] == questionable

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous -
Requested -
Interrogated -

22 1KGT 150 590 V013 1

Monitoring Direction SPI – Single Point Information

6.8 SPI – Single Point Information

Binary process information indicated by one bit.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
ACD general ST A
ACD neut ST A
ACD phsA ST A
ACD phsB ST A
ACD phsC ST A
ACT general ST A
ACT neut ST A
ACT phsA ST A
ACT phsB ST A
ACT phsC ST A
BSC stSeld ST A
DPC stSeld ST A
ENC 1 stSeld ST A
INC stSeld ST A
ISC stSeld ST A
SPC stSeld ST A
SPC stVal ST A
SPG setVal SP A
SPS stVal ST A
Additional None

1 Available for IEC 61850 Edition 2 client only

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Off FALSE
On TRUE

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

BL Blocked [Link] == TRUE
SB Substituted [Link] == substituted
NT Not Topical [Link] == TRUE
IV Invalid [Link] == invalid or
[Link] == questionable

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -

1KGT 150 590 V013 1 23

STI – Step Position Information Monitoring Direction

RTU500 series internal communication Protocol specific

Cause Spontaneous -
Requested -
Interrogated -

6.9 STI – Step Position Information

Binary process information indicated by 8 bit.

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
BSC [Link] ST A
ISC [Link] ST A
Additional None

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -63 -63
... ...
Range max. +63 +63

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

OV Overflow [Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE or

[Link] == TRUE
BL Blocked [Link] == TRUE
SB Substituted [Link] == substituted
NT Not Topical [Link] == TRUE
IV Invalid [Link] == invalid or
[Link] == questionable
T Transient Bit [Link]

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test [Link] == TRUE
P/N Positive/negative confirmation - Irrelevant -
Cause Spontaneous -

24 1KGT 150 590 V013 1

Monitoring Direction STI – Step Position Information

RTU500 series internal communication Protocol specific

Requested -
Interrogated -

1KGT 150 590 V013 1 25

STI – Step Position Information Monitoring Direction

26 1KGT 150 590 V013 1

Controlling Direction ASO – Analog Setpoint Output

7 Controlling Direction
7.1 ASO – Analog Setpoint Output
Analog process command (16 bit signed number).

7.1.1 ASO – Analog Setpoint Output

Analog process command (16 bit signed number)

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
INC ctlVal CO A
ING stVal SP B
ASG setMag.f SP C

Conversion of value (Type A, Type B and Type C)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -100% Parameter: Minimum Value
... ...
Range max. +100% Parameter: Maximum Value

For the value types A and B the protocol specific value range is -32768 .. +32767 (16 Bit). That
means for value type A and B the scaling parameters must be limited to -32768 .. +32767 (16 Bit)
as well. Higher scaling parameters results in wrong protocol attribute values.

1KGT 150 590 V013 1 27

ASO – Analog Setpoint Output Controlling Direction

Conversion of quality descriptors (Type A)

RTU500 series internal communication Protocol specific

SE Select / Execute ACSI control service: SBO/SBOw request /
ACSI control service: Operate request

Conversion of quality descriptors (Type B and Type C)

RTU500 series internal communication Protocol specific

SE Select / Execute Not supported by protocol. Handled in SCI IEC
61850.

Conversion of cause of transmission (Type A)

RTU500 series internal communication Protocol specific

T Test ACSI control service:
Test parameter
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause Activation ACSI control service:
Select/Operate request
Activation Confirmation ACSI control service:
Operate response
Deactivation -
Deactivation Confirmation -
Activation Termination -

Conversion of cause of transmission (Type B and Type C)

RTU500 series internal communication Protocol specific

T Test Not supported by protocol.
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause All values Not supported by protocol. Handled in SCI IEC
61850.

7.1.2 Command Authority

None

7.1.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Maximum value 32767 data point - Line T61850
The parameter 'Maximum value' in the external protocol\ngets converted to +100 % within RTU internal communication.
Minimum value -32768 data point - Line T61850

28 1KGT 150 590 V013 1

Controlling Direction BSO – Bit String Output

Parameter name Default Parameter location

The parameter 'Minimum value' in the external protocol\ngets converted to -100 % within RTU internal communication.
Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.
orCat usage Derived from internal data point - Line T61850
command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

7.2 BSO – Bit String Output

Binary process command (1, 2, 8, 16, 32 bit unsigned number).

7.2.1 BSO – Bit String Output

Binary process command (1, 2, 8, 16 bit unsigned number)

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
ISC ctlVal CO A
ING setVal SP B
ASG setMag.f SP C
ENC 1 ctlVal CO D
ENG 1 setVal SP E
SGC ActSG SP F

1 Available for IEC 61850 Edition 2 client only

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 0
... ... …
63 63
… …
65471 -64
… … …
Range max. 65535 -1

Protocol specific value range is mapped to BSO8 and BSO16 in 2´s complement format.

Conversion of value (Type B)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 0
... ... …
32767 32767

1KGT 150 590 V013 1 29

BSO – Bit String Output Controlling Direction

RTU500 series internal communication Protocol specific (Attribute value)

32768 -32768
… … …
Range max. 65535 -1

Protocol specific value range is mapped to BSO16 in 2´s complement format.

Conversion of value (Type C)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 0.0
... ...
Range max. 65535 65535.0

Conversion of value (Type D)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 Enumeration value 0
... ...
Range max. 65535 Enumeration value 65535

Conversion of value (Type E)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 Enumeration value 0
... ...
Range max. 65535 Enumeration value 65535

Conversion of value (Type F)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. 0 0
... ...
Range max. 255 255

Conversion of quality descriptors (Type A and Type D)

RTU500 series internal communication Protocol specific

SE Select / Execute ACSI control service: SBO/SBOw request /
ACSI control service: Operate request

Conversion of quality descriptors (Type B, Type C, Type E and Type F)

RTU500 series internal communication Protocol specific

SE Select / Execute Not supported by protocol. Handled in SCI IEC
61850.

Conversion of cause of transmission (Type A and Type D)

30 1KGT 150 590 V013 1

Controlling Direction BSO – Bit String Output

RTU500 series internal communication Protocol specific

T Test ACSI control service:
Test parameter
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause Activation ACSI control service:
Select/Operate request
Activation Confirmation ACSI control service:
Operate response
Deactivation -
Deactivation Confirmation -
Activation Termination -

Conversion of cause of transmission (Type B, Type C, Type E and Type F)

RTU500 series internal communication Protocol specific

T Test Not supported by protocol.
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause All values Not supported by protocol. Handled in SCI IEC
61850.

7.2.2 Command Authority

None

7.2.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.
orCat usage Derived from internal data point - Line T61850
command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

7.3 DCO – Double Command Output

Binary process command (two bits).

1KGT 150 590 V013 1 31

DCO – Double Command Output Controlling Direction

7.3.1 DCO – Double Command Output

Binary process command (two bits)

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
DPC ctVal CO A

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

off FALSE
on TRUE

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

SE Select / Execute ACSI control service: SBO/SBOw request /
ACSI control service: Operate request

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test ACSI control service:
Test parameter
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause Activation ACSI control service:
Select/Operate request
Activation Confirmation ACSI control service:
Select/Operate response
Deactivation ACSI control service:
Cancel request
Deactivation Confirmation ACSI control service:
Cancel response
Activation Termination Reception of controlled attribute value

7.3.2 Command Authority

None

7.3.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Default command qualifier run interlocking, run data point - Line T61850
synchrocheck

32 1KGT 150 590 V013 1

Controlling Direction DSO – Digital Setpoint Output

Parameter name Default Parameter location

Kind of command check which should be performed.

Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.
orCat usage Derived from internal data point - Line T61850
command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

7.4 DSO – Digital Setpoint Output

Binary process command (8 or 16 bit signed number).

7.4.1 DSO – Digital Setpoint Output

Binary process command (8 or 16 bit signed number)

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
INC ctlVal CO A
ING stVal SP B
ASG setMag.f SP C

Conversion of value (Type A, Type B and Type C)

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -100% Parameter: Minimum Value
... ...
Range max. +100% Parameter: Maximum Value

For the value types A and B the protocol specific value range is -32768 .. +32767 (16 Bit). That
means for value type A and B the scaling parameters must be limited to -32768 .. +32767 (16 Bit)
as well. Higher scaling parameters results in wrong protocol attribute values.

1KGT 150 590 V013 1 33

DSO – Digital Setpoint Output Controlling Direction

Conversion of quality descriptors (Type A)

RTU500 series internal communication Protocol specific

SE Select / Execute ACSI control service: SBO/SBOw request /
ACSI control service: Operate request

Conversion of quality descriptors (Type B and Type C)

RTU500 series internal communication Protocol specific

SE Select / Execute Not supported by protocol. Handled in SCI IEC
61850.

Conversion of cause of transmission (Type A)

RTU500 series internal communication Protocol specific

T Test ACSI control service:
Test parameter
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause Activation ACSI control service:
Select/Operate request
Activation Confirmation ACSI control service:
Operate response
Deactivation -
Deactivation Confirmation -
Activation Termination -

34 1KGT 150 590 V013 1

Controlling Direction DSO – Digital Setpoint Output

Conversion of cause of transmission (Type B and Type C)

RTU500 series internal communication Protocol specific

T Test Not supported by protocol.
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause All values Not supported by protocol. Handled in SCI IEC
61850.

7.4.2 Command Authority

None

7.4.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Maximum value 32767 data point - Line T61850
The parameter 'Maximum value' in the external protocol\ngets converted to +100 % within RTU internal communication.
Minimum value -32768 data point - Line T61850
The parameter 'Minimum value' in the external protocol\ngets converted to -100 % within RTU internal communication.
Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.
orCat usage Derived from internal data point - Line T61850
command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

7.5 FSO – Floating Point Setpoint Output

Floating point process command (32 bit short floating point number)

7.5.1 FSO – Floating Point Setpoint Output

Floating point process command (32 bit short floating point number)

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
ASG setMag.f SP A

Conversion of value (Type A)

1KGT 150 590 V013 1 35

FSO – Floating Point Setpoint Output Controlling Direction

RTU500 series internal communication Protocol specific (Attribute value)

Range min. -3.41038 -3.41038
...
Range max. + 3.41038 + 3.41038

Conversion of quality descriptors (Type A)

RTU500 series internal communication Protocol specific

SE Select / Execute Not supported by protocol. Handled in SCI IEC
61850.

Conversion of cause of transmission (Type B and Type C)

RTU500 series internal communication Protocol specific

T Test Not supported by protocol.
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause All values Not supported by protocol. Handled in SCI IEC
61850.

7.5.2 Command Authority

None

7.5.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.
orCat usage Derived from internal data point - Line T61850
command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

7.6 RCO – Regulation Command Output

Regulation step command (two bits).

7.6.1 RCO – Regulation Command Output

Regulation process command (two bits)

36 1KGT 150 590 V013 1

Controlling Direction RCO – Regulation Command Output

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
BSC ctVal CO A

Conversion of value (Type A)

RTU500 series internal communication Protocol specific (Attribute value)

Lower lower
Higher higher

Conversion of quality descriptors

RTU500 series internal communication Protocol specific

SE Select / Execute ACSI control service: SBO/SBOw request /
ACSI control service: Operate request

Conversion of cause of transmission

RTU500 series internal communication Protocol specific

T Test ACSI control service:
Test parameter
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause Activation ACSI control service:
Select/Operate request
Activation Confirmation ACSI control service:
Select/Operate response
Deactivation ACSI control service:
Cancel request
Deactivation Confirmation ACSI control service:
Cancel response
Activation Termination Reception of controlled attribute value

7.6.2 Command Authority

None

7.6.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Default command qualifier run interlocking, run data point - Line T61850
synchrocheck
Kind of command check which should be performed.
Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.

1KGT 150 590 V013 1 37

SCO – Single Command Output Controlling Direction

Parameter name Default Parameter location

orCat usage Derived from internal data point - Line T61850

command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

7.7 SCO – Single Command Output

Binary process command (one bit).

7.7.1 SCO – Single Command Output

Binary process command (one bit)

Supported Common Data Attribute Name Functional Conversion of

Data Types Class Constraint Value Type
SPC ctVal CO A
SPG stVal SP B

Conversion of value (Type A and Type B)

RTU500 series internal communication Protocol specific (Attribute value)

Off FALSE
On TRUE

Conversion of quality descriptors (Type A)

RTU500 series internal communication Protocol specific

SE Select / Execute ACSI control service: SBO/SBOw request /
ACSI control service: Operate request

Conversion of quality descriptors (Type B)

RTU500 internal communication Protocol specific

SE Select / Execute Not supported by protocol. Handled in SCI IEC
61850.

Conversion of cause of transmission (Type A)

RTU500 series internal communication Protocol specific

T Test ACSI control service:
Test parameter
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause Activation ACSI control service:
Select/Operate request

38 1KGT 150 590 V013 1

Controlling Direction SCO – Single Command Output

RTU500 series internal communication Protocol specific

Activation Confirmation ACSI control service:
Select/Operate response
Deactivation ACSI control service:
Cancel request
Deactivation Confirmation ACSI control service:
Cancel response
Activation Termination Reception of controlled attribute value

Conversion of cause of transmission (Type B)

RTU500 series internal communication Protocol specific

T Test Not supported by protocol.
P/N Positive/negative confirmation ACSI control service:
response +/-
Cause All values Not supported by protocol. Handled in SCI IEC
61850.

7.7.2 Command Authority

None

7.7.3 Additional Information

Parameter name Default Parameter location

Select before operate1 enabled data point - Line T61850

If enabled: Only Two Step Commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds
Enhanced security1 disabled data point - Line T61850
In case of control with enhanced security there shall be an additional supervision of the status value by the control object.
Default command qualifier run interlocking, run data point - Line T61850
synchrocheck
Kind of command check which should be performed.
Select before operate only disabled data point - Line T61850
If enabled, only two step commands are accepted. The time between 'Select' and 'Execute' must not exceed 20 seconds.
orCat usage Derived from internal data point - Line T61850
command originator
Originator Category (orCat) of the command, which is sent to the IED.
Derived from internal command originator: 'station-control' if originated by RTU500, otherwise 'remote-control'
Remote-control: Always 'remote-control', irrespective of the internal command originator.
Station-control: Always 'station-control', irrespective of the internal command originator.

1 Defined by control model of external protocol. Not available for functional constraint SP.

1KGT 150 590 V013 1 39

SCO – Single Command Output Controlling Direction

40 1KGT 150 590 V013 1

File transfer Transfer of Disturbance Data Files

8 File transfer
8.1 Transfer of Disturbance Data Files
The IEC 61850 Client is capable to read disturbance data files from an IEC 61850 IED (IEC 61850
server) and to store them on the Compact Flash memory file system of the RTU500 series. The
user is able to access them via the internal web server. The web server is also used to transfer
these files to a workspace PC. The transmission of disturbance data files is according to [2], [3] and
[5].

The supported IEC 61850 file transfer services are:

IEC 61850-7-2 service Meaning

GetFileAttributeValues Used by a client to obtain the name and attributes of a spe-
cific file in the server’s file store.
GetFile Used by a client to transfer the contents of a file from the
server to the client.
Table 2: Supported IEC 61850-7-2 file transfer services

The IEC 61850 service attributes are mapped to the RTU500 series file attributes according
following table:

IEC 61850 attributes Meaning RTU500 series file attributes

FileName Name of the file The disturbance record number is extracted
from the file name if possible (see below for
more information)
FileSize [0..n] Size of the file Size
LastModified Time of last modification Last Modified
Table 3: Mapping of IEC 61850 file transfer attributes

The IEC 61850 Client supports file transfer with the following specific IEC 61850 IEDs:

• ABB Control and Protection devices REx615, REx630, REx650 and REx670
• ABB Busbar Protection REB500
• ABB IEC 61850 adapter SPA-ZC 400 for REJ/REU 52x, REF/REM/REU 610, REF/REMRET
541/3/5
• Disturbance recorder BEN6000
• Control and Protection devices SIEMENS Siprotec
• Control and Protection device AREVA P436

Additional to the specific IEDs the IEC 61850 Client supports a generic type with configurable
parameters. This generic type can be used for not supported IEDs. The chapter "Generic IED Type"
contains detailed information how to use the generic type.

The IEC 61850 file name is for each of the supported IEC 61850 IED different. The conversion to
the RTU500 series file name is summarized in following table.

IEC 61850 IED Meaning

ABB REx630, REx650 The disturbance record number is extracted from IEC 61850 file name.
and REx670 The resulting RTU500 series file name is “Fault xx” with xx representing
the disturbance record number.
Table 4: Conversion IEC 61850 file name to RTU500 series file name

1KGT 150 590 V013 1 41

File Transfer Configuration File transfer

IEC 61850 IED Meaning

ABB REx615 The disturbance record number is extracted from IEC 61850 file name.
The filename contains a 4 character serial number that is used as dis-
turbance record number. The resulting RTU500 series file name is
“Fault xxxx”.
ABB REB500 IEC 61850 file name doesn’t include a disturbance record number. So,
a hash value (CRC16) is calculated from the file name to get a unique
number. This ensures that together with the file date, the file number
clearly identifies a record. The resulting RTU500 series file name is
“Fault xxxxx”.
ABB SPA-ZC 400 The disturbance record is number is built from IEC 61850 file name. The
record number consists of month (first 4 Bits), day (next 5 Bits), serial
number of records at the same day (last 7 Bits). The resulting RTU500
series file name is “Fault xx” with xx representing the disturbance record
number.
BEN6000 The disturbance record number is extracted from IEC 61850 file name.
The resulting RTU500 series file name is “Fault xx” with xx representing
the disturbance record number.
SIEMENS Siprotec The disturbance record number is extracted from IEC 61850 file name.
The filename contains a 4 character serial number that is used as dis-
turbance record number. The resulting RTU500 series file name is
“Fault xxxx”.
AREVA P436 The disturbance record number is extracted from IEC 61850 file name.
The filename contains a 3 character file number that is used as distur-
bance record number. The resulting RTU500 series file name is “Fault
xxxx”.
Table 4: Conversion IEC 61850 file name to RTU500 series file name

8.2 File Transfer Configuration

The general configuration of a disturbance record file archive in the RTU500 series is described
in [7] in chapter “Disturbance Data File Archive”. To use the file transfer of an IEC 61850 IED a
file directory (FDR) with at least one file (FTR) must be configured. The IEC 61850 file transfer is
different for each supported IED. Therefore the type of IED must be set for the files and directories
in RTUtil500. As described above supported are several ABB and non ABB IEDs.

The number of directories per IEC 61850 IED depends on the IED type. The following table shows
the configuration details for the different IED types.

IEC 61850 IED Max no. of directories Name of directory

ABB REx630, REx650 1 Not relevant
and REx670
ABB REx615 1 Not relevant
ABB REB500 60 (one per bay unit) Name must be the logical device name of
the bay unit
ABB SPA-ZC 400 1 Not relevant
BEN6000 1 Name must be the logical device name
that contains disturbance files
SIEMENS Siprotec 1 Not relevant
AREVA P436 1 Not relevant
Table 5: File directory configuration for IEC 61850 IEDs

42 1KGT 150 590 V013 1

File transfer Generic IED Type

The number of files in a directory depends on the capabilities of the IEC 61850 IED. Please see
the specific IED documentation for more information. In the RTU500 series the number of files in
a directory is restricted to 15. The name of the files is created according the rules in the chapter
above.

The subdevice interface loads the newest disturbance records only. That means if one FTR is
configured the newest record is loaded, if two FTRs are configured the two newest records are
loaded and so on.

The disturbance record files in IEC 61850 are in COMTRADE format. The number of files per
disturbance record depends on the IED type (see table below).

IEC 61850 IED Meaning

ABB REx630, REx650 The disturbance record files are placed as ZIP archive on the IED.
and REx670 Each ZIP archive representing a disturbance record consists of a .DAT
(data), .CFG (configuration) and .HDR (header) file.
ABB REx615 The disturbance record files are placed as separate files on the IED.
The RTU500 series loads per disturbance record the .DAT (data) and
the .CFG (configuration) file. The files are zipped together and stored
in the RTU500 series file archive.
ABB REB500 The disturbance record files are placed as ZIP archive on the IED.
Each ZIP archive representing a disturbance record consists of a .DAT
(data), .CFG (configuration) and .HDR (header) file.
ABB SPA-ZC 400 The disturbance record files are placed as separate files on the
IED. The RTU500 series loads per disturbance record the .DAT
(data), .CFG (configuration) and .INF (information) file. The files are
zipped together and stored in the RTU500 series file archive.
BEN6000 The disturbance record files are placed as separate files on the IED.
The RTU500 series loads per disturbance record the .DAT (data) and
the .CFG (configuration) file. The files are zipped together and stored
in the RTU500 series file archive.
SIEMENS Siprotec The disturbance record files are placed as separate files on the
IED. The RTU500 series loads per disturbance record the .DAT
(data), .CFG (configuration) and .TXT (text) file. The files are zipped
together and stored in the RTU500 series file archive.
AREVA P436 The disturbance record files are placed as separate files on the IED.
The RTU500 series loads per disturbance record the .DAT (data) and
the .CFG (configuration) file. The files are zipped together and stored
in the RTU500 series file archive.
Table 6: Files per disturbance record.

For each FDR a data point of type SPI can be configured to trigger disturbance recorder directory
update.

Parameter name Default Parameter location

Disturbance recorder trigger update Disabled FDR - line T61850

If enabled, a SPI can be linked to trigger disturbance recorder directory update.

8.3 Generic IED Type

The subdevice interface supports beside the several pre-defined IEC 61850 IED types a generic
type that can be used for the disturbance file transfer of any IED. The following sections describe
the configuration and restrictions of the generic type.

1KGT 150 590 V013 1 43

Generic IED Type File transfer

To use the file transfer for the generic IED a file directory (FDR) with at least one file (FTR) must be
configured. At the file directory the IED type "Disturbance recorder - IEC61850 - Generic IED" must
be selected. With selecting the type the additional configuration parameters “File directory search
pattern”, “File directory path” and "File search pattern" became accessible at the file directory. The
first two parameters control the directory access and the third parameter controls the file selection.
The meaning of the parameters is as follows:

• File directory search pattern

This string parameter must be set to the search pattern that returns in a get directory request the
content of the disturbance record file directory.
• File directory path
This string parameter contains the file directory path information in case the generic IED doesn’t
provide the complete file name and path. Please see the specific IED documentation (PIXIT) for
more information about the search pattern and the directory path required by the IED.
• File search pattern
If this string parameter is set, the RTU500 checks whether the file name contains the defined
pattern string (case insensitive). And only files that contain the pattern string are handled as
disturbance record files. The pattern sting is a plain ASCII string that doesn't support any wild
card characters.

Depending on the reply of the IED on a get directory request the files are loaded according the
descriptions in the following table. Be sure to consider the meaning of the file directory (FDR) name
set in the RTUtil500 configuration for the file transfer.

Functionality Behavior for generic IED type

Get directory For the get directory request the configured search pattern is used.
The filenames returned by the request are checked for their extension.
In case the IED provides zipped COMTRADE files (extension .ZIP), the
files are loaded individual as they are.
In case the IED provides single COMTRADE files, the files of one
disturbance record are zipped together. The files of one disturbance
record are identified by the same file name with different extensions.
For a generic IED the COMTRADE files with the extension .DAT
(data), .CFG (configuration) and .HDR (header) are zipped together. All
other file extensions are ignored.
Directory name The configured file directory path (see above) is used to complete the
file path together with the file name provided by the IED. Be sure to
set the directory path if a generic IED doesn't provide the complete file
name. The directory path must be configured including the required
separator characters “/” or “\”.

If the generic IED provides the complete file name leave the file direc-
tory path configuration parameter empty. In this case the file name is
used as it is to access the file.
Numbers of files As for the standard IEDs each disturbance record provided by the
generic IEDs is loaded. In case a disturbance record consists of more
than one file the files are zipped together. So the number of configured
FTRs shall be set to the actual number of disturbance records to load.
Get file For generic IEDs the RTU500 tries to determine what files provided by
the IED are disturbance record files. This is done by the file ending,
that must be a COMTRADE ending (like *.dat) or a ZIP ending (*.zip).
In case the IED provides files with these endings that are no distur-
bance record files the parameter "File search pattern" can be used to
restrict the selected files (see description above).
Table 7: File transfer generic IED type

44 1KGT 150 590 V013 1

File transfer Generic IED Type

Functionality Behavior for generic IED type

According to the number FTRs configured the newest disturbance
records are loaded only. That means if one FTR is configured the
newest disturbance record is loaded, if two FTRs are configured the
two newest disturbance records are loaded and so on.
RTU560 file name It is not known whether the IED file name includes a disturbance record
number. So, a hash value (CRC16) is calculated from the file name
to get a unique number. This ensures that together with the file date,
the file number clearly identifies a disturbance record. The resulting
RTU500 series file name is “Fault xxxxx”.
Table 7: File transfer generic IED type

1KGT 150 590 V013 1 45

Generic IED Type File transfer

46 1KGT 150 590 V013 1

Internal Functions Startup log

9 Internal Functions
9.1 Startup log
During startup of the SCI IEC 61850 detailed information about the configuration and initialization
can be written to a startup log file. This file is placed on the compact flash card of a CMU and can
be downloaded via the web server. The file is written after a CMU re-start when the startup log was
enabled before in the web server. Enabling the startup log and downloading the resulting file are
found in the web server under ‘Test & Simulation -> Logging and debugging’.

9.2 Time Synchronization

Time synchronization of subordinated devices is done using SNTP time synchronization protocol.
SNTP time synchronization protocol is a general function of RTU500 series and must be configured
with RTUtil500. The configuration of SNTP is described in [8].

9.3 General Interrogation

The general interrogation to subordinated devices is part of the report control block handling
defined in IEC 61850. There is no specific general interrogation command existing.

9.4 System Events

The subdevice communication interface manages internal status messages for every device
connected to this line. These status messages are created from the subdevice communication
interface itself for every connected device.

The subdevice communication interface supports the system events summarized in the following
table:

Description of system event Shortcut

Device active #024
Device inoperable #048
Device out-of-service #049
Table 8: Supported system events

The protocol specific status information are converted to the internal system event
representation according to the table below:

Description RTU500 Protocol specific

series
internal
Device active Off Device not active
On Device active
Device inoperable Off Device connected and
PhyHealth stVal == Ok (1) or Warning (2) and
PhyHealth [Link] == good
Table 9: System event conversion

1KGT 150 590 V013 1 47

System Events Internal Functions

Description RTU500 Protocol specific

series
internal
On Device disconnected or
PhyHealth stVal == Alarm (3) or
PhyHealth [Link] != good
Device out-of-service Off Device in-service
On Device out-of-service
Table 9: System event conversion

While initialization the value of system event ‘Device is active’ (#024) is set to ON. On a running
system this system event doesn’t change anymore.

The system event 'Device inoperable' (#048) is set in dependency of the state of the subordinated
device. For a correct signalization attribute ‘PhyHealth’ of logical node LD0 must be mapped to a
DPI data point and have to be imported in RTUtil500. If no LD0 is available in synchronized SCD
file, the first found attribute 'PhyHealth' will be used for mapping of signalization. To ensure a correct
signalization in this case only one attribute 'PhyHealth' must be imported.

A subordinated device is operable if

• the device is connected and
• attribute '[Link]' is 'Ok' or 'Warning'
• attribute '[Link]’ is 'good'.

When operable the device system event 'Device inoperable' (#048) is send with value Off (0) to the
internal communication. If the state of a subordinated device changes from inoperable to operable,
all configured data points of the device are requested and sent to the internal communication.

A subordinated device is inoperable if

• the device is not connected, or
• attribute '[Link]' is 'Alarm', or
• attribute '[Link]' is not 'good'.

When inoperable the device system event 'Device inoperable' (#048) is sent with value On (1) to the
internal communication.

If the state of a subordinated device changes from operable to inoperable because the device is
no longer connected, all configured data points connected to this device are sent to the internal
communication with the actual state, marked as INVALID or NOT TOPICAL and with the time
stamp of the own RTU.

INVALID or NOT TOPICAL is set depending on the configuration parameter Information object
qualifier (see table below).

Parameter name Parameter Parameter range / Default

location Explanation
Information object qualifier (usage RTU Parameter - Mark as invalid (IV) Mark as
for disconnected subordinated invalid (IV)
devices) - Mark as not topical (NT)
Note: Also in not topical configuration are data points which have not been updated since RTU
startup marked as invalid (IV)
Table 10: Information object qualifier parameter

48 1KGT 150 590 V013 1

Internal Functions System commands

The system event 'Device out-of-service' (#049) is set to OFF during initialization. That means
the device is in-service and the SCI IEC 61850 tries to connect the device. The device can be set
out-of-service with a system command (see next chapter). In the state out-of-service an actual
connection to a device is concluded and no new connection is initiated as long as the state remains.
The device can be set back in-service with the same system command.

9.5 System commands

The behavior of subordinated devices connected to a sub-device communication interface with
protocol IEC 61850 can be modified with system single commands (SSC).

The following system single commands are supported:

SSC supported Description of SSC Address offset

X Set device out of service #001
Reset device process #002
Connect/disconnect device #003
Set redundant line 1 / 2 as preferred line #004, #005
Set redundant line 3 / 4 as preferred line #006, #007
Force global process image update, i.e. force process #012
image update of all subdevices
Request redundancy change over for the active CMU x, 1 #016 ... #031
≤ x ≤ 16
Table 11: Description of system single commands (SSC)

9.5.1 Set device out of service

The devices connected to the subdevice interface are set to in-service during initialization. During
runtime the device can be set out-of-service by operating the system single command ‘Set device
out-of-service’ with state ON. In the state out-of-service an actual connection to a device is
concluded and no new connection is initiated as long as the state remains. The device can be
set back in-service by operating the system single command with state OFF. When the device is
already in the desired state the command is confirmed negative.

Description RTU500 Protocol specific

series
internal
Set device out-of-service Off Set device in-service
On Set device out-of-service
Table 12: System command conversion

9.6 Message Filtering

The RTU500 series IEC 61850 communication engineering (data sets) is based on data object
level. That means for common data classes that include a selected (stSeld) data attribute (e.g. DPC
data class) that with each change of the stSeld attribute the value indication (e.g. stVal) is send as
well. This value indication is an unintended, spontaneous message that contains the current status
of the indication. To filter this unintended messages the following algorithm is used in the SCI IEC
61850:

1KGT 150 590 V013 1 49

Command Handling Internal Functions

Value indications in controllable common data class that contains a selected data attribute (stSeld)
are identified in the configuration. For this kind of indications a received message is checked for
value and qualifier changes. If value or qualifier is changed the message is transmitted. If value or
qualifier is not changed the message is ignored.

This is valid for all supported controllable common data classes that contains a selected (stSeld)
data attribute (see chapter 5.1 SPI- Single Point Information).

9.7 Command Handling

9.7.1 IEC 61850 Control Models

The RTU500 series IEC 61850 client supports all control models defined in standard. The mapping
functionality of the IEC 61850 control models to the commands of the RTU500 series internal
communication is shown in the table below.

RTU500 inter- IEC 61850 control model Protocol specific mapping functionality
nal command
Direct command direct-with-normal-security • The received Execute command is trans-
mitted to the device and answered by the
device.
• According to the command type a termina-
tion is created by the subdevice interface.
SBO command direct-with-normal-security • The received Select command is answered
by the subdevice interface depending on
operable state of the device.
• The received Execute command is trans-
mitted to the device and answered by the
device.
• According to the command type a termina-
tion is created by the subdevice interface.
Direct command sbo-with-normal-security • The received Execute command is trans-
mitted to the device as Select command.
In case of a positive answer the Execute
command is transmitted to the device and
answered by the device. In case of a nega-
tive answer the received Execute command
is answered negative.
• According to the command type a termina-
tion is created by the subdevice interface.
SBO command sbo-with-normal-security • The received Select command is transmitted
to the device and answered by the device.
• The received Execute command is trans-
mitted to the device and answered by the
device.
• According to the command type a termina-
tion is created by the subdevice interface.
Direct command direct-with-enhanced-security • The received Execute command is trans-
mitted to the device and answered by the
device.
Table 13: Mapping functionality of IEC 61850 control models

50 1KGT 150 590 V013 1

Internal Functions Command Handling

RTU500 inter- IEC 61850 control model Protocol specific mapping functionality
nal command
• The command termination send by the
device is transferred to the internal commu-
nication. In case the command type requires
no termination the termination is ignored.
SBO command direct-with-enhanced-security • The received Select command is answered
by the subdevice interface depending on
operable state of the device.
• The received Execute command is trans-
mitted to the device and answered by the
device.
• The command termination send by the
device is transferred to the internal commu-
nication. In case the command type requires
no termination the termination is ignored.
Direct command sbo-with-enhanced-security • The received Execute command is trans-
mitted to the device as Select command.
In case of a positive answer the Execute
command is transmitted to the device and
answered by the device. In case of a nega-
tive answer the received Execute command
is answered negative.
• The command termination send by the
device is transferred to the internal commu-
nication. In case the command type requires
no termination the termination is ignored.
SBO command sbo-with-enhanced-security • The received Select command is transmitted
to the device and answered by the device.
• The received Execute command is trans-
mitted to the device and answered by the
device.
• The command termination send by the
device is transferred to the internal commu-
nication. In case the command type requires
no termination the termination is ignored.
Table 13: Mapping functionality of IEC 61850 control models

The following remarks have to be considered for the mapping functionality above:

• In case the command in the device doesn’t support select-before-operate a Select command
send by the internal communication is answered by the subdevice interface. The Select
command is answered positive if the device is operable according to the system event ‘Device
inoperable’ (#048). If the device is inoperable the Select command is answered negative. See
chapter “System Events” for detailed information about the operable/inoperable indication.
• The IEC 61850 subdevice interface provides for each command type the parameter “Select
Before Operate Only”. If this parameter is set to YES, only select-before-operate commands are
allowed for the specific command object. In this case direct commands are confirmed negative.
The default value for this parameter is NO.
• The default value for the Command confirmation timeout is set to 25 seconds. If the IEC 61850
subdevice interface doesn't get a response from the IEC 61850 server within the defined time
span, the command is replied negative to the internal communication. This applies to all control
models described above.

1KGT 150 590 V013 1 51

Command Handling Internal Functions

Parameter name Default Parameter location

Command confirmation timeout 25 s RTU - Parameters

Maximum time until a command must be confirmed. Value range: 1 to 600 seconds.
Command operation timeout 60 s RTU - Parameters
Maximum time until a started command operation procedure is released, in case it was not completed before.
Value range: 1..660 seconds.

9.7.2 Qualifier of Command

The RTU500 series command types SCO, DCO and RCO support a mapping of the command
attribute ‘Qualifier of command’ (QU) to the IEC 61850 command data attribute ‘check’. The
attribute ‘check’ allows setting of additional command information like ‘run with interlocking’ or ‘run
with synchrocheck’.

The command parameter ‘Default command qualifier’ defines the value of the IEC 61850 'check'
data attribute in case the qualifier of command is not set to predefined value. The following values
are possible for the ‘Default command qualifier’:

• "run interlocking, run synchrocheck" or

"no interlocking, run synchrocheck" or
"run interlocking, no synchrocheck" or
"no command check"

The mapping of the ‘Qualifier of command’ to the IEC 61850 command check attribute is shown in
the table below.

Qualifier of command (QU) Command check attribute on IEC 61850 set to

0 .. 8 value of ‘Default command qualifier’
9 no interlocking, run synchrocheck
10 run interlocking, no synchrocheck
11 no interlocking, no synchrocheck
12 run interlocking, run synchrocheck
13 .. 31 value of ‘Default command qualifier’
Table 14: Mapping of IEC 61850 check attribute

9.8 IEC 61850 server functionality

The RTU500 series IEC 61850 client provides internal functionality of the RTU500 serie interfaced
as IEC 61850 server. The internal functions of the IEC 61850 subdevicecommunication interface of
the RTU500 series are:

• Logical node physical health identification

• Time master supervision
• Redundant physical communication channel supervision
• Authority control for the whole substation

The next chapters describe the provided internal RTU500 series functions in detail. For information
about the configuration aspects of the IEC 61850 server functionality see [6].

52 1KGT 150 590 V013 1

Internal Functions IEC 61850 server functionality

9.8.1 Logical Node Physical Health Identification

The physical health identification of the RTU500 series is provided in a standard data object of the
logical node LPHD. The table below shows the relation between the data object and the RTU500
series functionality.

Logical Node Data Object RTU500 series functionality

LPHD PhyHealth Operable state of the RTU500 series. Derived from the sys-
tem event “CMU operable/inoperable”. If operable Phy-
Health is set to Ok (value 1) otherwise set to Alarm (value
3).
Table 15: Relation between Logical Node and RTU500 series functionality.

To send the information about the physical health identification to clients on the station level the
RTU500 series IEC 61850 server provides the predefined data set "StatNrmlA" with the data object
"PhyHealth".

ADVICE
Please note that this only applies to LLN0 node. LPHD nodes from other logical devices are not
part of the data set.

9.8.2 Time master supervision

The time master supervision of the RTU500 series is provided in standard data objects of the logical
node LTMS. This logical node is available for Edition 2 client or server only. The table below shows
the relation between the data objects and the RTU500 series functionality.

Logical Node Data Object RTU500 series functionality

LTMS TmSyn Status of the time synchronization in the RTU500 series.
See table below for possible state values.
LTMS TmChSt1 Shows as boolean value (up/down) the status of the SNTP
time synchronization. If set ot true at least one SNTP client
in the RTU500 series is synchronized.
Table 16: Relation between Logical Node and RTU500 series functionality.

The data objects "TmSyn" represents the actual time synchronization status in the following way:

TmSyn Time synchronization status in RTU500 series

ExternalArea- The RTU500 series is not synchronized.
Clock (Value 0)
LocalAreaClock The RTU500 series is synchronized by a local time source.
(Value 1) Depending on the configuration this can be a local real time
clock or a host communication interface.
GlobalAreaClock The RTU500 series is synchronized by an SNTP server.
(Value 2)
Table 17: Indication of time synchronization status

To send the information about time master supervision to clients on the station level the RTU500
series IEC 61850 server provides the predefined data set "StatNrmlA" with the data object "TmSyn".

1KGT 150 590 V013 1 53

IEC 61850 server functionality Internal Functions

The data object for the status of the SNTP time synchronization "TmChSt1" is not part of the data
set per default. If required the data object can be added to a data set in the system configuration
outside of RTUtil500.

9.8.3 Redundant physical communication channel supervision

The redundant physical communication channel supervision of the RTU500 series is provided in
standard data objects of the logical node LCCH. This logical node is available for Edition 2 client or
server only and if PRP is configured for the Ethernet interfaces. The table below shows the relation
between the data objects and the RTU500 series functionality.

Logical Node Data Object RTU500 series functionality

LCCH ChLiv Physical channel status of redundant Ethernet interface 1.
Derived from the system event “PRP interface no. X: net-
work interface 1 link up”.
LCCH RedChLiv Physical channel status of redundant Ethernet interface 2.
Derived from the system event “PRP interface no. X: net-
work interface 2 link up”.
LCCH FerCh PRP frame error rate of redundant Ethernet interface 1.
LCCH RedFerCh PRP frame error rate of redundant Ethernet interface 2.
Table 18: Relation between Logical Node and RTU500 series functionality.

To send the information about the redundant physical communication channel supervision to
clients on the station level the RTU500 series IEC 61850 server provides the predefined data set
"StatNrmlA" with the data objects "ChLiv" and "RedChLiv".

The data objects for the PRP frame error rate "FerCh" and "RedFerCh" are not part of the data
set per default. If required the data objects can be added to a data set in the system configuration
outside of RTUtil500.

9.8.4 Authority Control for the whole Substation

The authority control of the RTU500 series is provided in standard data objects of the logical
node LLN0. The table below shows the relation between the data objects and the RTU500 series
functionality. The data object for requesting the local control authority is different for Edition 1 and
Edition 2 clients.

Logical Node Data Object RTU500 series functionality

LLN0 Loc Local control authority active. Derived from the system event
'Local control authority active/inactive'.
LLN0 RemCtlBlk Request of local control authority by client on station level
(Edition 1 only) and indication whether authority is actual granted.
LLN0 LocSta Request of local control authority by client on station level
(Edition 2 only) and indication whether authority is actual granted.
Table 19: Relation between Logical Node and RTU500 series functionality.

The data objects 'Loc' and 'RemCtlBlk' respectively 'LocSta' represents the actual control authority
in the following way:

54 1KGT 150 590 V013 1

Internal Functions High Communication Load

Loc RemCtlBlk Control authority state in RTU500 series

FALSE FALSE NCC’s on remote level have authority control. Another IEC
61850 client on station level is not allowed to control.
TRUE FALSE Authority control on station level granted to another instance
(e.g. to the HMI). Another IEC 61850 client on station level is
not allowed to control.
FALSE TRUE Not possible error state. Another IEC 61850 client on station
level is not allowed to control.
TRUE TRUE Authority control on station level granted to another IEC
61850 client. Another IEC 61850 client on station level is
allowed to control.
Table 20: Indication of control authority state

The requested and granted local control authority is reset after a timeout of 120 seconds. That
means if another IEC 61850 client has requested the local control authority successfully, the control
authority remains at this client for 120 seconds. After this time the control authority goes back to the
remote level automatically. This timeout is fixed and can be neither changed or configured.

If the IEC 61850 client wants to keep the local control authority, another request must be issued
within or after the defined timeout period. When another request is issued within the timeout period,
the timeout restarts to the full range of 120 seconds.

To send the information about authority control to clients on the station level the RTU500 series
IEC 61850 server provides the predefined data set 'StatNrmlA' with the data objects 'Loc' and
'RemCtlBlk' respectively 'LocSta'.

9.9 High Communication Load

The SCI IEC 61850 protocol implementation contains a functionality that supervises the
communication load. This functionality is driven by the incoming IEC 61850 telegrams and triggers
when many telegrams arrive in short period of time. As result the diagnosis messages “High
Communication Load” is reported and the processing in the SCI IEC 61850 is slowed down
temporarily. The processing slowdown is done to avoid blocking of other activities in the RTU560,
e.g. the PLC. The slowdown is reset if the amount of receiving telegrams goes back to normal,
resulting in the diagnosis message “Normal Communication Load”.

Triggering this functionality doesn’t mean that the SCI IEC 61850 communication is overloaded per
se. The diagnosis message is a note for the user to review the system setup. If the message occurs
very often and/or other functionalities in the RTU560 are blocked the amount of incoming telegrams
shall be reduced. This can be done for example by filtering measurement changes at the source
IEDs or by reducing the number of connected IEDs (Segmentation of IEDs on different SCI lines).

If a system works fine without any constraints the diagnosis message can be handled as
informational.

9.10 Setting Group Control

The RTU500 series IEC 61850 client supports the functionality to switch the active group of a
setting group control block (SGCB). For each SGCB found in the SCL data model of a server IED,
RTUtil500 creates a single bit string command (BSO8). This command can be used to switch the
active setting group by providing the number of the group to set, in the command value. For detailed
mapping information refer to the bit string output command in the controlling direction section.

1KGT 150 590 V013 1 55

Setting Group Control Internal Functions

During the engineering process with RTUtil500, the bit string command for the setting group
control is written to the Excel sheet of an IEC 61850 client. In the Excel sheet, the command can
be identified by the data object “SGCB” and the data attribute “ActSG”, defined for the switching
command in the standard. By completing the configuration of the command in the Excel sheet and
with RTUtil500, the command became available in the configuration file for the RTU500 firmware.

The setting group control feature doesn't comprise the reading of the actual active setting group. A
server IED supporting setting groups must include the information about the actual active setting
group in a data attribute as part of a data set. That means the information about the active group
is sent by the IED, on change in a report. Reading the actual, active setting group directly is not
supported by the client.

56 1KGT 150 590 V013 1

Limits and Recommendations System Limits

10 Limits and Recommendations

10.1 System Limits
The following table specifies the system limits of IEC 61850 Client in RTU500 series:

Description Limit
Maximum number of subdevice communication interfaces IEC 61850 per RTU 5
Maximum number of subdevice communication interfaces IEC 61850 per CMU 1
Maximum number of IEDs per RTU 120
Maximum number of IEDs per subdevice communication interface IEC 61850 644
Maximum number of process data points supported per RTU500 series 50001
Maximum number of data set entries a subdevice communication interface IEC 7000
61850 supports as client (regardless of communication type, sum across all data
sets received)
Maximum number of report control blocks (RCBs) respectively data sets per server 1000 buffered
connected to a subdevice communication interface IEC 61850 reports2

1000
unbuffered
reports2
Maximum number of entries per data set 300
Maximum number of data attribute instances (DAIs) per subdevice communication 210003
interface IEC 61850
Table 21: System limits

1 Depending on the used license.

2 Practically the limitation is the overall number of data set entries that can be handled by the
subdevice communication interface IEC 61850 (see above).
3 For a rough calculation based on the number of RTU500 data points, count 3 DAIs per
monitoring data point and 20 DAIs per command data point.
4 20 recommended
Limits of additional features of the RTU500 series are described in RTU500 Series Function
Description - Part 2: Rack mounted solutions (1KGT151096) and RTU500 Series Function
Description - Part 3: DIN rail solutions (1KGT151097).

For detailed limits on the IEC 61850 protocol implementation see chapter "Protocol Implementation
extra Information for Testing (PIXIT)".

10.2 Mixed systems

The RTU500 series can work as IEC 61850 Edition 1 or Edition 2 client or server. The used protocol
edition is defined for client and server in the configuration. In system with IEDs of one Edition only,
no restrictions apply for the RTU500 series. But in mixed systems were IEDs of Edition 1 and
Edition 2 are used together the following restrictions apply:

• For extensions of existing Edition 1 systems the RTU500 series must be configured as Edition 1
IED. The extension of Edition 1 system with Edition 2 devices is not supported.
• Mixed systems are supported for client/server communication. In mixed system the SCD file is
Edition 2 including Edition 1 data models. There is one SCD file only for mixed systems.

1KGT 150 590 V013 1 57

Additional Timeouts Limits and Recommendations

• The RTU500 series doesn’t support GOOSE communication between editions. That means the
GOOSE communication with the RTU500 series is restricted to IEDs of the same edition. The
configuration tool RTUtil500 checks this restriction and GOOSE data points from IEDs with the
wrong edition are ignored (Presenting a warning message for the user).

10.3 Additional Timeouts

Besides the timeouts defined in the Protocol Implementation extra Information for Testing (PIXIT),
the following definitions must be considered for the RTU500 IEC 61850 client.

Timeout Value Description

ACSI service 5 seconds If an IEC 61850 server doesn't reply to an ACSI service request
request within this timeout, the connection to the server is concluded.
TCP socket con- 5 seconds If an IEC 61850 server doesn't reply to a TCP/IP socket connect
nect request within this timeout, no connection to the server is estab-
lished.
Supervision mes- 15 sec- If an IEC 61850 server doesn't reply to an MMS status request
sage onds within this timeout, the connection to the server is concluded.
Table 22: Additional timeouts

58 1KGT 150 590 V013 1

Conformance Statements Abstract Communication Service Interface (ACSI)

11 Conformance Statements
11.1 Abstract Communication Service Interface
(ACSI)
The following ACSI conformance statements are used to provide an overview and details about
RTU500 series IEC 61850 client, version 12.4 :

• ASCI basic conformance statement,

• ACSI models conformance statement,
• ACSI service conformance statement

The statements specify the communication features mapped to IEC 61850-8-1 Edition 1 and Edition
2. The following tables contain a column for the RTU500 series IEC 61850 client (named “RTU500
series client”).

11.1.1 ACSI Basic Conformance Statement

The ACSI basic conformance statement for RTU500 series IEC 61850 client is defined in following
table.

Client/ Server/ RTU500

subscriber publisher series client
Client-server roles
B11 Server side - c1 -
(of TWO-PARTYAPPLICATION-ASSOCIATION)
B12 Client side c1 - YES
(of TWO-PARTYAPPLICATION-ASSOCIATION)
SCSMs supported
B21 SCSM: IEC 61850-8-1 used YES
B22 SCSM: IEC 61850-9-1 used -
B23 SCSM: IEC 61850-9-2 used -
B24 SCSM: other -
Generic substation event model (GSE)
B31 Publisher side - O -
B32 Subscriber side O - -
Transmission of sampled value model (SVC)
B41 Publisher side - O -
B42 Subscriber side O - -
c1 – shall be ‘M’ if support for LOGICAL-DEVICE model has been declared.

O – Optional

M – Mandatory
Table 23: ACSI basic conformance statement

11.1.2 ACSI Models Conformance Statement

The ACSI models conformance statement for RTU500 series IEC 61850 client is defined in
following table.

1KGT 150 590 V013 1 59

Abstract Communication Service Interface (ACSI) Conformance Statements

Client/ Server/ RTU500

subscriber publisher series client
If Server or Client side (B11/B12) supported
M1 Logical device c2 c2 YES
M2 Logical node c3 c3 YES
M3 Data c4 c4 YES
M4 Data set c5 c5 YES
M5 Substitution O O -
M6 Setting group control O O -
Reporting
M7 Buffered report control O O YES
M7-1 sequence-number YES
M7-2 report-time-stamp YES
M7-3 reason-for-inclusion YES
M7-4 data-set-name YES
M7-5 data-reference YES
M7-6 buffer-overflow YES
M7-7 entryID YES
M7-8 BufTm YES
M7-9 IntgPd YES
M7-10 GI YES
M7-11 conf-revision YES
M8 Unbuffered report control O O YES
M8-1 sequence-number YES
M8-2 report-time-stamp YES
M8-3 reason-for-inclusion YES
M8-4 data-set-name YES
M8-5 data-reference YES
M8-6 BufTm YES
M8-7 IntgPd YES
M8-8 GI YES
M8-9 conf-revision YES
Logging
M9 Log control O O -
M9-1 IntgPd -
M10 Log O O -
M11 Control M M YES
If GSE (B31/B32) is supported
M12 GOOSE O O -
M13 GSSE O O -
If SVC (B41/B42) is supported
M14 Multicast SVC O O -
M15 Unicast SVC O O -
For all IEDs
Table 24: ACSI model conformance statement

60 1KGT 150 590 V013 1

Conformance Statements Abstract Communication Service Interface (ACSI)

Client/ Server/ RTU500

subscriber publisher series client
M16 Time M M YES
M17 File Transfer O O YES
c2 – shall be ‘M’ if support for LOGICAL-NODE model has been declared.

c3 – shall be ‘M’ if support for DATA model has been declared.

c4 – shall be ‘M’ if support for DATA-SET, Substitution, Report, Log Control, or Time model has
been declared.

c5 – shall be ‘M’ if support for Report, GSE, or SV models has been declared.

O – Optional

M – Mandatory
Table 24: ACSI model conformance statement

11.1.3 ACSI Service Conformance Statement

The ACSI service conformance statement for RTU500 series IEC 61850 client is defined in
following table (depending on the statements of table "Tab. 24: ACSI model conformance
statement").

AA: Client/ Server/ RTU500

Services
TP/MC subscriber publisher series client
Server (Clause 7)
S1 GetServerDirectory TP M -
Application association (Clause 8)
S2 Associate M M YES
S3 Abort M M YES
S4 Release M M YES
Logical device (Clause 9)
S5 GetLogicalDeviceDirectory TP M M -
Logical node (Clause 10)
S6 GetLogicalNodeDirectory TP M M -
S7 GetAllDataValues TP O M -
Data (Clause 11)
S8 GetDataValues TP M M YES
S9 SetDataValues TP O O YES
S10 GetDataDirectory TP O M YES
S11 GetDataDefinition TP O M YES
Data set (Clause 12)
S12 GetDataSetValues TP O M -
S13 SetDataSetValues TP O O -
S14 CreateDataSet TP O O -
S15 DeleteDataSet TP O O -
S16 GetDataSetDirectory TP O O YES
Table 25: ACSI service conformance statement

1KGT 150 590 V013 1 61

Abstract Communication Service Interface (ACSI) Conformance Statements

AA: Client/ Server/ RTU500

Services
TP/MC subscriber publisher series client
Setting group control (Clause 16)
S18 SelectActiveSG TP O O -
S19 SelectEditSG TP O O -
S20 SetEditSGValues TP O O -
S21 ConfirmEditSGValues TP O O -
S22 GetEditSGValues TP O O -
S23 GetSGCBValues TP O O -
Reporting (Clause 17)
Buffered report control block (BRCB)
S24 Report TP c6 c6 YES
S24-1 data-change (dchg) YES
S24-2 qchg-change (qchg) YES
S24-3 data-update (dupd) YES
S25 GetBRCBValues TP c6 c6 YES
S26 SetBRCBValues TP c6 c6 YES
Unbuffered report control block (URCB)
S27 Report TP c6 c6 YES
S27-1 data-change (dchg) YES
S27-2 qchg-change (qchg) YES
S27-3 data-update (dupd) YES
S28 GetURCBValues TP c6 c6 YES
S29 SetURCBValues TP c6 c6 YES
Logging (Clause 17)
Log control block
S30 GetLCBValues TP M M -
S31 SetLCBValues TP O M -
Log
S32 QueryLogByTime TP c7 M -
S33 QueryLogAfter TP c7 M -
S34 GetLogStatusValues TP M M -
Generic substation event model (GSE)
GOOSE (Clause 18)
S35 SendGOOSEMessage MC c8 c8 -
S36 GetGoReference TP O c9 -
S37 GetGOOSEElementNumber TP O c9 -
S38 GetGoCBValues TP O O -
S39 SetGoCBValues TP O O -
GSSE (Annex C)
S40 SendGSSEMessage MC c8 c8 -
S41 GetGsReference TP O c9 -
S42 GetGSSEDataOffset TP O c9 -
S43 GetGsCBValues TP O O -
Table 25: ACSI service conformance statement

62 1KGT 150 590 V013 1

Conformance Statements Abstract Communication Service Interface (ACSI)

AA: Client/ Server/ RTU500

Services
TP/MC subscriber publisher series client
S44 SetGsCBValues TP O O -
Transmission of sampled value model (SVC) (Clause 19)
Multicast SVC
S45 SendMSVMessage MC c10 c10 -
S46 GetMSVCBValues TP O O -
S47 SetMSVCBValues TP O O -
Unicast SVC
S48 SendUSVMessage TP c10 c10 -
S49 GetUSVCBValues TP O O -
S50 SetUSVCBValues TP O O -
Control (Clause 20)
S51 Select TP M O YES
S52 SelectWithValue TP M O YES
S53 Cancel TP O O YES
S54 Operate TP M M YES
S55 Command-Termination TP M O YES
S56 TimeActivated-Operate TP O O -
File transfer (Clause 23)
S57 GetFile TP O M YES
S58 SetFile TP O O -
S59 DeleteFile TP O O -
S60 GetFileAttributeValues TP O M YES
Time (5.5)
T1 Time resolution of internal clock 10
(1 msec)
T2 Time accuracy of internal clock T1
T3 Supported TimeStamp resolution 10
(1 msec)
c6 – shall declare support for at least one (BRCB or URCB)

c7 – shall declare support for at least one (QueryLogByTime or QueryLogAfter)

c8 – shall declare support for at least one (SendGOOSEMessage or SendGSSEMessage)

c9 – shall declare support if TP association is available

c10 – shall declare support for at least one (SendMSVMessage or SendUSVMessage)

O – Optional
Table 25: ACSI service conformance statement

11.1.4 Specific Communication Service Mapping (SCSM)

See B21 table "Tab. 23: ACSI basic conformance statement" and [IEC 61850-7-2].

1KGT 150 590 V013 1 63

Protocol Implementation Conformance Statement (PICS) Conformance Statements

11.2 Protocol Implementation Conformance

Statement (PICS)
This protocol implementation conformance statement is applicable for RTU500 series IEC 61850
client, version 12.4.

11.2.1 Basic Profile Conformance

[Link] PICS for A-Profile support

The PICS for A-Profile support for RTU500 series IEC 61850 client are defined in following table.

A-Pro-
RTU500
file Profile Description Client Server
series client
shortcut
A1 Client/server A-Profile c1 c1 YES
A2 GOOSE/GSE management A-Profile c2 c2 -
A3 GSSE A-Profile c3 c3 -
A4 TimeSync A-Profile c4 c4 YES
A5 Security for client/server A-Profile o o -
A6 Security for GOOSE/GSE management A-Profile o o -
c1 Shall be ‘m’ if support for any service specified in [IEC 61850-8-1] Table 2 are declared within
the ACSI basic conformance statement (see Table 5).

c2 Shall be ‘m’ if support for any service specified in [IEC 61850-8-1] Table 6 are declared within
the ACSI basic conformance statement (see Table 5).

c3 Shall be ‘m’ if support for any service specified in [IEC 61850-8-1] Table 9 are declared within
the ACSI basic conformance statement (see Table 5).

c4 Support for at least one other A-Profile shall be declared (e.g. in A1-A3) in order to claim con-
formance to [IEC 61850-8-1].[IEC 61850-8-1].
Table 26: PICS for A-Profile support

[Link] PICS for T-Profile support

The PICS for T-Profile support for RTU500 series IEC 61850 client are defined in following table.

T-Profile RTU500
Profile Description Client Server
shortcut series client
T1 TCP/IP T-Profile c1 c1 YES
T2 OSI T-Profile c2 c2 -
T3 GOOSE/GSE T-Profile c3 c3 -
T4 GSSE T-Profile c4 c4 -
T5 TimeSync T-Profile O O YES
c1 Shall be ‘m’ if support for table 9-4 A1 is declared. Otherwise, shall be 'i'.

c2 Shall be ‘o’ if support for table 9-4 A1 is declared. Otherwise, shall be 'i'.

c3 Shall be ‘m’ if support for table 9-4 A2 is declared. Otherwise, shall be 'i'.
Table 27: PICS for T-Profile support

64 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation Conformance Statement (PICS)

T-Profile RTU500
Profile Description Client Server
shortcut series client
c4 Shall be ‘m’ if support for table 9-4 A3 is declared. Otherwise, shall be 'i'.

i – out-of-scope: The implementation of the item is not within the scope of this standard

O – Optional
Table 27: PICS for T-Profile support

11.2.2 MMS Conformance

All needed services supporting the ACSI services stated to be supported in chapter ’9.1.3 "ACSI
Service Conformance Statement" ’ are supported by the MMS stack used.

11.3 Model Implementation Conformance Statement

(MICS)
This model implementation conformance statement is applicable for RTU500 series IEC 61850
client, version 12.4.

This MICS document specifies the modelling implementations and extensions compared to IEC
61850 Edition 1 and Edition 2. For the exact details on the standardized model please compare the
ICD substation configuration files generated by RTUtil500.

• Chapter 11.3.1 describes the common data class extensions

• Chapter 11.3.2 contains the list of implemented logical nodes.
• Chapters 11.3.3 to 11.3.4 describe the implemented logical nodes.

11.3.1 Common Data Class Extensions

[Link] Supported common data classes

Following table defines the list of common data classes supported by RTU500 series IEC 61850
client.

Common data class specifications for status information

SPS Single point status
DPS Double point status
INS Integer status
ENS1 Enumerated status
ACT Protection activation information
ACD Directional protection activation information
BCR Binary counter reading
Common data class specifications for measurand information
MV Measured value
CMV Complex measured value
WYE Phase to ground related measured values of a three phase system
DEL Phase to phase related measured values of a three phase system
SEQ Sequence
Table 28: Common data classes supported by the RTU500 series IEC 61850 client

1KGT 150 590 V013 1 65

Model Implementation Conformance Statement (MICS) Conformance Statements

Common data class specifications for controlls

SPC Controllable single point
DPC Controllable double point
INC Controllable integer status
ENC 1 Controllable enumerated status
BSC Binary controlled step position information
ISC Integer controlled step position information
Common data class specifications for status settings
SPG Single point setting
ING Integer status setting
ENG 1 Enumerated status setting
Common data class specifications for analogue settings
ASG Analogue setting
Table 28: Common data classes supported by the RTU500 series IEC 61850 client

1 Support by IEC 61850 Edition 2 client only

[Link] Unsupported common data classes

Following table defines the list of common data classes not supported by RTU500 series IEC 61850
client.

Common data class specifications for status information

SEC Security violation counting
HST Histogram
VSS Visible string status
Common data class specifications for measurand information
SAV Sampled value
HMV Harmonic Value
HYE Harmonic value for WYE
HDEL Harmonic value for DEL
Common data class specifications for controlls
APC Controllable analogue set point information
BAC Binary controlled analog process value
Common data class specifications for status settings
ORG Object reference setting
TSG Time setting group
CUG Currency setting group
VSG Visible string setting
Common data class specifications for analogue settings
CURVE Setting curve
CSG Curve shape setting
Common data class specifications for description information
DPL Device name plate
LPL Logical node name plate
Table 29: Common data classes unsupported by the RTU500 series IEC 61850 client

66 1KGT 150 590 V013 1

Conformance Statements Model Implementation Conformance Statement (MICS)

CSD Curve shape description

Table 29: Common data classes unsupported by the RTU500 series IEC 61850 client

11.3.2 Logical Node List

Following table defines the list of logical nodes supported by RTU500 series IEC 61850 client.

LN Group L: System logical nodes

LPHD Physical device information
LLN0 Logical node zero
LCCH1 Physical communication channel supervision
LTMS 1 Time master supervision
LN Group I: Logical nodes for interfacing and archiving
ITCI Telecontrol interface
Table 30: Logical nodes supported by the RTU500 series IEC 61850 client

1 Supported for IEC 61850 Edition 2 client/server only

11.3.3 LN Group L: System logical nodes

[Link] LN type: LPHD

LPHD
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
PhyNam DPL Physical device name plate
PhyHealth INS Physical device health
Proxy SPS Indicates if this LN is a proxy
Table 31: Logical node type LPHD

LPHD
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
PhyNam DPL Physical device name plate
PhyHealth ENS Physical device health
Proxy SPS Indicates if this LN is a proxy
Table 32: Logical node type LPHD (Edition 2)

[Link] LN type: LLN0

LLN0
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
Table 33: Logical node type LLN0 (Edition 1)

1KGT 150 590 V013 1 67

Model Implementation Conformance Statement (MICS) Conformance Statements

LLN0
Common logical node information
Mod INC Mode
Beh INS Behaviour
Health INS Health
NamPlt LPL Name plate
Loc SPS Local operation for complete logical device
RemCtlBlk SPC Authority control for the whole substation (see chapter 8.7)
Table 33: Logical node type LLN0 (Edition 1)

LLN0
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
Common logical node information
Mod ENC Mode
Beh ENS Behaviour
Health ENS Health
NamPlt LPL Name plate
Loc SPS Local operation for complete logical device
LocSta SPC Authority control for the whole substation (see chapter 8.7)
Table 34: Logical node type LLN0 (Edition 2)

[Link] LN Type LCCH

LCCH
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
Common logical node information
Beh ENS Behaviour
ChLiv SPS Physical channel status; true, if channel receives telegrams
within a specified time interval.
RedChLiv SPS Physical channel status of redundant channel
FerCh INS Frame error rate on this channel; count of erroneous (or
missed, in case of redundancy) messages for each 1 000
messages forwarded to the application.
RedFerCh INS Frame error rate on redundant channel; count of missed
messages on this channel for each 1 000 messages for-
warded to the application.
Table 35: Logical node type LCCH (Edition 2)

68 1KGT 150 590 V013 1

Conformance Statements Model Implementation Conformance Statement (MICS)

[Link] LN type LTMS

LTMS
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
Common logical node information
Beh ENS Behaviour
TmSrc VSS Current time source
TmSyn ENS Time synchronized according to IEC 61850-9-2
TmChSt1 SPS Time channel status (up/down)
Table 36: Logical node type LTMS (Edition 2)

11.3.4 LN Group L: Logical nodes for interfacing and archiving

[Link] LN type: ITCI

ITCI
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
Common logical node information
Mod INC Mode
Beh INS Behaviour
Health INS Health
NamPlt LPL Name plate
Table 37: Logical node type ITCI (Edition 1)

ITCI
Attribute Name Attribute Type Explanation
LNName Shall be inherited from LN Class (see [IEC 61850-7-2])
Data
Common logical node information
Beh INS Behaviour
Table 38: Logical node type ITCI (Edition 2)

11.4 Tissues Conformance Statement (TICS)

This chapter contains the technical issues (tissues) conformance statement. According to the
UCA IUG QAP the tissue conformance statement is required to perform a conformance test and is
referenced on the certificate.

The tissues are grouped in mandatory interoperability tissues (IntOp tissues), optional
interoperability tissues and other tissues. The following tables are structured in the columns:

Part: Section of the IEC 61850 standard the tissue belongs to

1KGT 150 590 V013 1 69

Tissues Conformance Statement (TICS) Conformance Statements

Tissue Nr: Number of the tissue according to the database provided under http://
[Link]

Description: Short description of the tissue

Implemented: Indicates whether the tissue is implemented in the device. The meaning of the
abbreviations are
Y = Yes the tissue is implemented in the device
N = No the tissue is not implemented in the device
na = Not applicable, the tissue is not applicable for the device

The following chapters are applicable for RTU500 series IEC 61850 Edition 1 and Edition 2 client,
version 12.4.

11.4.1 Mandatory Edition 1 IntOp Tissues

During the October 2006 meeting IEC TC57 working group 10 decided that:

• green Tissues with the category “IntOp¨ are mandatory for IEC 61850 edition 1
• Tissues with the category “Ed.2¨ Tissues should not be implemented.

Below table gives an overview of the implemented Edition 1 IntOp Tissues.

Tissue Implemented
Part Description
Nr Y/na
8-1 116 GetNameList with empty response? Y

165 Improper Error Response for GetDataSetValues Y

183 GetNameList error handling Y

7-4 252 [Link] na
7-3 28 Definition of APC na

54 Point def xVal, not cVal na

55 Ineut = Ires ? na

63 mag in CDC CMV na

219 operTm in ACT na

270 WYE and DEL rms values na

1199 Allow INT32 for CDC BCR Y

7-2 30 control parameter T Y

31 Typo na

32 Typo in syntax na

35 Typo Syntax Control time na

36 Syntax parameter DSet-Ref missing na

37 Syntax GOOSE "T" type Y

39 Add DstAddr to GoCB Y

Table 39: Mandatory Edition 1 IntOp Tissues

70 1KGT 150 590 V013 1

Conformance Statements Tissues Conformance Statement (TICS)

Tissue Implemented
Part Description
Nr Y/na
40 GOOSE Message “AppID” to “GoID” Y

41 GsCB “AppID” to “GsID” na

42 SV timestamp: “EntryTime” to “TimeStamp" na

43 Control "T" semantic Y

44 AddCause - Object not sel Y

45 Missing AddCauses (neg range) na

46 Synchro check cancel Y

47 "." in LD Name? na

49 BRCB TimeOfEntry (part of #453) Y

50 LNName start with number? na

51 ARRAY [0..num] missing na

52 Ambiguity GOOSE SqNum Y

53 Add DstAddr to GsCB, SV na

151 Name constraint for control blocks etc. na

166 DataRef attribute in Log na

185 Logging - Integrity periode na

189 SV Format na

190 BRCB: EntryId and TimeOfEntry (part of #453) Y

191 BRCB: Integrity and buffering reports (part of #453) Y

234 New type CtxInt (Enums are mapped to 8 bit integer) na

275 Confusing statement on GI usage (part of #453) Y

278 EntryId not valid for a server (part of #453) Y

297 Sequence number (part of #453) Y

298 Type of SqNum (part of #453) Y

305 Reporting with BufTm=0 (part of #453) Y

322 Write Configuration attribute of BRCBs (part of #453) Y

329 Reporting and BufOvl (part of #453) Y

333 Enabling of an incomplete GoCB na

335 Clearing of Bufovfl (part of #453) Y

348 URCB class and report (part of #453) Y

349 BRCB TimeOfEntry has two definitions (part of #453) Y

Table 39: Mandatory Edition 1 IntOp Tissues

1KGT 150 590 V013 1 71

Tissues Conformance Statement (TICS) Conformance Statements

Tissue Implemented
Part Description
Nr Y/na
1281 Default for [Link] is TRUE Y
6 1 Syntax na

5 tExtensionAttributeNameEnum is restricted na

8 SIUnit enumeration for W Y

10 Base type for bitstring usage Y

17 DAI/SDI elements syntax na

169 Ordering of enum differs from 7-3 na

NOTE: Tissue 49, 190, 191, 275 and 278 are part of the optional tissue #453, all other technical
tissues in the table are mandatory if applicable.
NOTE: Editorial tissues are marked as “na”.
NOTE: Final proposal on tissue 45 is not defined yet
Table 39: Mandatory Edition 1 IntOp Tissues

11.4.2 Optional Edition 1 IntOp Tissues

After the approval of the server conformance test procedures version 2.2 the following IntOp tissues
were added or changed. It is optional to implement these tissues.

Tissue Implemented
Part Description
Nr Y/N/na
8-1 246 Control negative response (SBOns) with LastApplError N

545 Skip file directories with no files na

7-2 333 Enabling of an incomplete GoCB na

453 Combination of all reporting and logging tissues Y

6 245 Attribute RptId in SCL is optional na

526 Replace sev - Unknown by unknown na

Table 40: Optional Edition 1 IntOp Tissues

11.4.3 Mandatory Edition 2 Tissues

Below table gives an overview of the implemented Edition 2 Tissues.

Tissue Implemented
Part Description
Nr Y/na
8-1 753 Whether "GoID" and "DatSet" in GoCB are writable? na

770 GoID type mitmatch 18.1.1 and [Link].2 na

777 AddCause values na

784 Tracking of control (CTS) na

817 Fixed-length GOOSE float encoding na

Table 41: Mandatory Edition 2 Tissues

72 1KGT 150 590 V013 1

Conformance Statements Tissues Conformance Statement (TICS)

Tissue Implemented
Part Description
Nr Y/na
821 AlternateAccess in GetAllDataValues na

827 Mandatory ACSI services na

834 File dir name length 64 na

851 bType wrong for "check" in sample SCL file na

854 GetDataValues - single or multiple objects Y

935 Typing error in table 101 na

942 Wrong description of S bit in reserved word na

951 Encoding of Owner attribute na

1036 FileDirectory response na

1037 GetDataSetValues SpecWithResult Y

1040 More associate error codes Y

1041 LTS and OTS mapping na

1042 SGCB definition includes information that is not mapping na

specific
1043 na
SetEditSGValues should not detail nothing about non-
1047 volatile storage na

1058 "Currency" basictype is not mapped Y

1066 OSI-AP-Title value na

1155 UtcTime wrong referecne Y

1164 ResvTms definition should be integer in the BRCB struc- na

ture
1178 Y
DeleteDataSet response- refers to wrong clause
1181 na
Select Response+ is non-null value
1192 na
Conformance requirement for InformationReport Ambigu-
1274 na
ous
1285 Y
GoCB MinTime/MaxTime size
1287 na
GetServerDirectory(FILE) typo
1289 na
ICD file must have a communication section for 8-1 imple-
1299 mentation na

1300 COMTRADE zip file contents na

1309 typo: LLNO -> LLN0 na

1324 Missing semantics for localDetailCalling na

1336 na
Table 41: Mandatory Edition 2 Tissues

1KGT 150 590 V013 1 73

Tissues Conformance Statement (TICS) Conformance Statements

Tissue Implemented
Part Description
Nr Y/na
1361 Behavior for a ContimueAfter where the File no longer Y
exists
1441 Y
Extraneous normative reference:10608-1 and -2
1442 Y
The response- for DeleteNamedVariableList is not defined
1443 na
enhanced the mapping text for the setValues.
1453 Y
Variable length Quality encoding
1454 Y
Optonal fields in buffered reports
1462 na
Journal variableTag for ReasonCode
1495 na
Reading SE when EditSG=0

Purge buffer on write to BRCB

Reports can be generated before write(RptEna=true) is

confirmed

SNTP references to RFCs are different

GetVariableAccessAttributes error code

7-4 671 Mistake in definition of Mod & Beh Y

674 CDC of [Link] is wrong na

675 SIML LN Y

676 Same data object name used with different CDC na

677 MotStr is used with different CDC in PMMS and SOPM LN na

classes
679 na
Remove CycTrMod Enum
680 na
SI unit for [Link]
681 na
Enum PIDAlg
682 na
[Link]
683 na
Enum [Link]
685 na
Enum ParTraMod
686 Y
New annex H - enums types in XML
689 na
RREC - diagram
693 Y
Description of LTMS.TmChSt1
694 na
Data object CmdBlk
695 na
[Link]
696 na
[Link] (Status of subscription)
712 na
Table 41: Mandatory Edition 2 Tissues

74 1KGT 150 590 V013 1

Conformance Statements Tissues Conformance Statement (TICS)

Tissue Implemented
Part Description
Nr Y/na
713 Interpretation of quality operatorBlocked na

714 DO Naming of time constants in FFIL N

715 Enums for ShOpCap and SwOpCap na

716 RBDR.ChNum1 na

724 TAXD text for condition na

725 [Link] na

727 Loc in LN A-group na

734 RREC - diagram na

735 [Link] vs. [Link] na

736 [Link] and [Link] na

742 PFSign Y

743 [Link], [Link] and [Link] na

744 [Link] and [Link] na

748 LN STMP, EEHealth and EEName na

749 CBOpCap na

772 Description BndCtrChg na

773 [Link]/PwrDn shall be transient N

774 Loc, LocKey and LocSta YPSH and YLTC na

775 [Link] na

776 [Link] and OpnLim na

790 [Link]/InOv and [Link]/InOv na

800 [Link] not in table 10 na

802 Misspelling in CSYN na

808 CCGR and Harmonized control authority na

830 Presence condition of [Link] and new DOs na

831 Mode/Behaviour & Quality na

838 Setting of ConfRevNum in LGOS na

842 Testing in Beh=Blocked na

843 [Link] change type to SPS na

844 GGIO.AnOut1 move to Controls na

Table 41: Mandatory Edition 2 Tissues

1KGT 150 590 V013 1 75

Tissues Conformance Statement (TICS) Conformance Statements

Tissue Implemented
Part Description
Nr Y/na
849 [Link], [Link], [Link] DEL- na
>WYE

Presence conditions re-assessing in case of derived statis-

tical calculation

7-4 877 QVUB -settings should be optional na

879 Duplicate definition of HzChr na

902 Control Blocks in CommonLN na

908 [Link] - transient na

909 Remove [Link] and ColOpL na

912 Clarification of PwrRtg/VARtg na

920 Resetable Counter is NOT resetable na

932 Rename [Link] to [Link] na

933 Presence of [Link] and RedRxCnt Y

939 Change CDC for [Link] na

940 Clarification of feedback MX for DO with CDC APC na

967 Statistical calculation and "M" attributes na

991 LGOS: GoCBRef (as well as [Link]) should be na

mandatory
1007 na
PTRC as fault indicator - Update of description required
1044 na
TapChg in AVCO
1077 na
Rename DOnames within LTIM
1177 na
Winding ratio for TCTR and TVTR
1273 na
Behavior of DOI "Beh" due internal condition
1294 Y
Description of [Link] reg. Buchholz
1330 na
proposal in tissue 830 seems not consistent with 7-3 Ed2
1331 na
Mod, Beh and Health with q=TEST, client can't receive
1333 their states na

1456 SPS datapoint for Select is not present in LN ATCC for na

process bus
1568 na
Annex A and Mod/Beh/Health

[Link] ->transient
7-3 697 persistent command / PulseConfig na

698 Wrong case is [Link] attribute na

Table 41: Mandatory Edition 2 Tissues

76 1KGT 150 590 V013 1

Conformance Statements Tissues Conformance Statement (TICS)

Tissue Implemented
Part Description
Nr Y/na
709 Semantic of tstEna na

722 Units for 'h' and 'min' not in UnitKind enumeration. Y

814 subQ bit used na

819 APC and ASG na

832 Data attribute semantic of minVal & maxVal na

839 Use of opRcvd also in Blocked na

887 Data semantics for q and t na

919 Presence Condition for sVC na

924 Missing curve characteristics na

925 Presence of i or f attribute - Problem with writing na

926 Presence Conditions within RangeConfig na

929 condition AC_SCAV unclear na

953 missing trigger option forCSG units na

954 Data attributes with FC=CF should have trgOp=dchg na

962 instMag optional? na

968 BCR value range N

1078 CMV.t update if rangeAng changed na

1079 q and t semantic syntax errors na

1187 ldNs example value shal be 2007A na

1253 Can CDC ACT be used for 3-phase indication? Y

1387 Default value of SboClasses na

1430 opRcvd for controllable object na

1481 configRev presence condition Y

7-2 728 BRCB: could PurgeBuf be set when RptEna=TRUE? Y

778 AddCause values Y

780 What are unsupported trigger option at a control block? Y

783 TimOper Resp- ; add Authorization check na

786 AddCause values 26 and 27 are switched Y

813 TimeAccuracy choices na

820 Mandatory ACSI services (use for PICS template) Y

850 Y
Table 41: Mandatory Edition 2 Tissues

1KGT 150 590 V013 1 77

Tissues Conformance Statement (TICS) Conformance Statements

Tissue Implemented
Part Description
Nr Y/na
852 Report Value needs a corresponding index when data- na
FALSE
858 Y
Check condition type - parameter type wrong
861 na
Typo in enumeration ServiceType
869 na
dchg of ConfRev attribute
875 na
Grammer/spelling error
876 na
GenLogiclNodeClass and compatible LN Classes
943 na
GenLogiclNodeClass and SGCB, GoCB, MsvCB, UsvCB
970 na
control model change to "local" when TimeActivatedOper-
1038 ate na

1050 Wrong reference to GSSE na

1061 Loss of Info Detection After Resynch na

1062 GTS Phycomaddr definition in SCL na

1071 EntryTime wrongly appllied Y

1091 Entrytime not used in CDC na

1092 Length of DO name na

1116 The sentence "The initial value of EditSG shall be 0" in 7.2 na
1127 NewEntrTm and OldEntrTm Type in LOG Class na

1145 CONTROL service(s) parameter 'orgin' misspelled na

1154 Missing owner attribute in BTS and UTS na

1202 T – control time-stamp Y

1232 Inconistent Definition for Response Parameter Y

1242 GI not optional na

1252 EntryID needs clarification na

1283 NTS definiton na

1307 Data-Instance-ID: is 01 allowed? Y

1341 pleonasm "qchg-change" (for Ed.2) Y

1428 Segemented report with Buffer overflow na

1569 Attribute Owner is missing in GetBRCBValues services na

MTS and NTS should use svOptFlds

How to track Select service in service tracking?

7-1 828 Data model namespace revision IEC 61850-7-4:2007[A] Y
Table 41: Mandatory Edition 2 Tissues

78 1KGT 150 590 V013 1

Conformance Statements Tissues Conformance Statement (TICS)

Tissue Implemented
Part Description
Nr Y/na
874 Logical Node Class needs to be updated na

948 Enumeration (string) values format na

1060 Error in encoding in Figure F.9 na

1072 Statistical Data and Reporting na

1129 Rules for extending nameplate information na

1151 Simulated GOOSE disappears after 1st appearance na

1251 All "L" logical nodes shall be in the same LD - except for Y
gateways
1268 na
Assigment of single CDC to DOclass
1312 Y
Presence condition of lnNs and dataNs
1396 na
The use and configuration flow of LGOS and LSVS is
1491 Unclear na

CmdBlk blocks itself?

6 658 Tracking related features na

660 XML encoding header repeat na

663 FCDA element cannot "functionally constrained logical Y

node"
668 na
Autotransformer modeling
687 na
SGCB ResvTms
699 na
DO type description table
719 Y
ConfDataSet - maxAttributes definition is confusing
721 na
Log element name
731 na
quoted SCL inconsistant with annex.
752 na
Input Section/ Inputs Section
768 na
bType VisString65 is missing
779 Y
Object references
787 Y
SICS I45 inconsistency
788 na
SICS S56 from optional to mandatory
789 Y
ConfLdName as services applies to both server and client
804 na
valKind and IED versus System configuration
806 na
Max length of log name inconsistent between -6 and -7-2
807 Y
Need a way to indicate if "Owner" present in RCB
823 Y
Table 41: Mandatory Edition 2 Tissues

1KGT 150 590 V013 1 79

Tissues Conformance Statement (TICS) Conformance Statements

Tissue Implemented
Part Description
Nr Y/na
824 ValKind for structured data attributes na

825 Short addresses on structured data attributes na

845 Floating point value na

853 SGCB ResvTms na

855 SBO and ProtNs N

856 Recursive SubFunction na

857 VoltageLevel frequency and phases Y

873 Function/SubFunction for ConductingEquipment na

886 Examples for "curvPts" na

901 Missing 8-1 P-types na

936 tServices as AP or as IED element na

949 SupSubscription parameter usage is difficult na

1118 type of LN inst is ambiguous na

1147 Clarification of how tClientLN is used to enable Report na

Control Blocks
1175 na
tServices - FileHandling not consistent with -7-2
1185 na
IPv6 address lowercase only na
1195 na
Valkind value Conf for EX FC data
1208 na
Typographical Error
1284 Y
IPv6 Address format
1298 na
SCSM mapping may require a communication section in
1304 an ICD file na

1318 How to differentiate preconfigured Report Datasets and na

generated ones
1328 Y
Error in the SCL object model
1354 Y
SSD will not validate against XSD
1365 N
Limitation on the size of data type templates identifiers
1397 na
Changes to SICS Template
1398 N
Need to tighten up the XSD in regards to IEDName usage
1415 na
Subscription limitation visible in IxD file
1444 Y
originalSclVersion management in SCT
1445 Y
SICS-S110 IID import mandatory for Edition2
Table 41: Mandatory Edition 2 Tissues

80 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Tissue Implemented
Part Description
Nr Y/na
Need to support fixed and SCT controlled Datasets

ConfReportControl and a fixed ReportSettings

6 1447 Restriction on ENUMtypes in SCL Y

1450 originalSclXxx computation rules N

1451 Services section-"client" is confusing na

1457 Multiple DOI nodes with the same name. Y

NOTE: Editorial tissues are marked as “na”.
Table 41: Mandatory Edition 2 Tissues

11.5 Protocol Implementation extra Information for

Testing (PIXIT)
This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC
61850 interface in the client system: RTU500 series IEC 61850 client, version 12.4 (further referred
to as "client").

Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to
IEC 61850-10.

Each chapter specifies the PIXIT for each applicable ACSI service model as structured in IEC
61850-10and the "Conformance Test Procedures for Client System with IEC 61850-8-1 interface".

11.5.1 PIXIT for Configuration

Description Value / Clarification

Describe how the client handles nameplate con- The actual server name plate configuration revi-
figuration revision mismatches sion is read from the server during the connec-
tion establishment. The configuration revision
from the SCD file is not part of specific client
configuration file. Therefore a mismatch between
the SCD file and the actual server name plate
configuration revision is not checked by the
client.
Describe how the client handles report control The report control block configuration revision is
block configuration revision mismatches written from SCD file to the specific client con-
figuration file. During connection establishment
the client reads the report control block configu-
ration revision from the data model of the server
and compares the value with the revision from
the SCD file. In case of a mismatch an internal
minor error is generated that can be seen with a
device specific log tool. The internal minor error
has no influence on the processing of the report
control block.

The configuration revision send by the server in

an actual report is not checked by the client.
Table 42: PIXIT for configuration

1KGT 150 590 V013 1 81

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

11.5.2 PIXIT for Association Model

Description Value / Clarification

Guaranteed number of servers that can set-up 64
an association simultaneously (one association
per server)
Lost connection detection time range (default 5 seconds
range of TCP_KEEPALIVE is 1 - 20 seconds)
Lost (abort) connection retry time TCP_KEEPIDLE = 10 s

TCP_KEEPCNT = 3

TCP_KEEPINIT = 10 s

TCP_KEEPINTVL = 5s

10s after association start to begin sending keep-

alive and 15s (3 * 5s) to detect lost connection.
Is authentication supported? N
What is the maximum and minimum MMS PDU Max MMS PDU size 32000 bytes
size
Min MMS PDU size 1024 bytes
What is the typical start-up time after a power Depending on the size of the configuration a typ-
supply interrupt ical start-up time is 5 minutes (including associa-
tion to all configured servers)
How does the client behave in case of a The server is marked as offline. After a timeout
lost connection with (one of) the associated of 15 seconds the client tries to reconnect the
servers? server. The reconnect timeout is increased to 60
seconds after 3 failed connection requests. The
client never stops the reconnect retries.
Note: In case the connection to several servers
are lost at the same time the actual reconnect
timeouts can be longer.
How does the client behave when a server The server is marked as offline. After a time-
denies an Association request by the client? out of 15 seconds the client tries to connect the
server again. The connect timeout is increased
to 60 seconds after 3 failed connection requests.
The client never stops the connect retries.
Note: In case the connection to several servers
are lost at the same time the actual reconnect
timeouts can be longer.
Does the client automatically reconnect to the Y
configured servers after start-up (Automatic
start-up)?
Table 43: PIXIT for Association model

11.5.3 PIXIT for Server model

Description Value / Clarification

Maximum object identification length 129 octets: <64>/<64>
Does the client support auto-description? The client support auto-description in the means
of adaptation to minor configuration mismatches
between the SCD configuration and the actual
Table 44: PIXIT for Server model

82 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

server data model. But the client needs a com-
plete SCD configuration with all servers and
there data models included as starting point.
During the first connection establishment the
client reads parts of the actual data model of a
server and modifies (when possible) the model
from the SCD configuration according the actual
read data. The processing is then done on the
corrected data model. At any further connection
requests to a server (during the runtime of the
client) the data model is not read again. Instead
the client uses the data model read during the
first connection establishment.
Describe how to view/display data values The IEC 61850 data values are mapped to IEC
870-5-101 data values that can be viewed in the
web server provided by the device.
What analogue value (MX) quality bits are used Y Good,
in the client
Y Invalid,

N Reserved,

N Questionable

Y Overflow

Y OutofRange

Y BadReference

Y Oscillatory

Y Failure

Y OldData

Y Inconsistent

Y Inaccurate

Y Process

Y Substituted

Y Test

Y OperatorBlocked
Which status value (ST) quality bits are used in Y Good,
the client
Y Invalid,

N Reserved,

N Questionable

N BadReference

N Oscillatory
Table 44: PIXIT for Server model

1KGT 150 590 V013 1 83

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

Description Value / Clarification

N Failure

Y OldData

N Inconsistent

N Inaccurate

Y Process

Y Substituted

Y Test

Y OperatorBlocked
Describe how to view/display quality values The IEC 61850 quality bits are mapped to IEC
870-5-101 like quality attributes that can be
viewed in the web server provided by the device.
Which time quality bits are used in the client N LeapSecondsKnown

Y ClockFailure

Y ClockNotSynchronized
Describe how to view/display time quality bits The IEC 61850 time quality bit ClockNotSynchro-
nized is mapped to a time invalid attribute that
can be viewed in the web server provided by the
device.
Describe how to force a SetDataValues request Control an analogue or digital set-point that is
mapped to an IEC 61850 data object with func-
tional constraint SP.
Describe how to force GetDataValues request Control a data object with control model 'sbo-
with-normal-security'. The service 'Select' is
defined as reading of the SBO data attribute with
the ACSI GetDataValues service.
Describe how to force a GetAllDataValues The ACSI service GetAllDataValues is not sup-
request ported by the client.
Does the Client support writing blkEna values? N
Describe how the client behaves in case of: The ACSI service GetServerDirectory is not used
by the client. The client gets the logical devices
- GetServerDirectory response- of a server from the configured SCD data model
of that server. Differences between the config-
ured and the actual data model of a server are
not considered.
Describe how the client behaves in case of: The ACSI service GetLogicalDeviceDirectory is
not used by the client. The client gets the logi-
- GetLogicalDeviceDirectory response- cal node and data set information from the con-
figured SCD data model of a server. Differences
between the configured and the actual data
model of a server are not considered.
Describe how the client behaves in case of: The ACSI service GetLogicalNodeDirectory is
not used by the client. The client gets the data
- GetLogicalNodeDirectory response- set information from the configured SCD data
model of a server. Differences between the con-
Table 44: PIXIT for Server model

84 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

figured and the actual data model of a server are
not considered.
Describe how the client behaves in case of: The ACSI services GetDataDirectory / Get-
DataDefinition are used by the client to read data
- GetDataDirectory response- model information of logical nodes during con-
nection establishment. In case of a negative ser-
- GetDataDefinition response-
vice response the association to the server is
concluded. Afterwards The client tries to recon-
nect the server according the rules described in
"PIXIT for Association model".
Describe how the client behaves in case of: The ACSI service GetAllDataValues is not sup-
ported by the client.
- GetAllDataValues response-
Describe how the client behaves in case of: The ACSI service GetDataValues is used by the
client to read the actual server name plate con-
- GetDataValues response- figuration revision during connection establish-
ment. In case of a negative service response
an internal minor error is generated that can be
seen with a device specific log tool. The internal
minor error has no influence on the further con-
nection establishment.
Describe how the client behaves in case of: The ACSI service SetDataValues is used by the
client to write a data element with functional con-
- SetDataValues response- straint SP (Set Point). The origin of this write
request is a set point command from a host func-
tionality within the client (e.g. IEC 870-5-104 con-
nection to a network control center). In case of
a negative service response from the server the
set point command is confirmed negative.
Table 44: PIXIT for Server model

11.5.4 PIXIT for Dataset model

Description Value / Clarification

Describe how to force a GetDataSetValues The ACSI service GetDataSetValues is not sup-
request ported by the client.
Describe how to force a SetDataSetValues The ACSI service SetDataSetValues is not sup-
request ported by the client.
Describe how to force a DeleteDataSet request The ACSI service DeleteDataSet is not sup-
ported by the client.
Describe how the client handles following With the first connection establishment the client
dataset mismatches between the SCL and the reads the actual configuration of a dataset. This
data sets exposed via MMS: information is stored and used for the decoding
of reports containing this dataset. The datasets
(1) New dataset element read by the client are selected from the SCD
configuration of the client. Afterwards the client
(2) Missing dataset element
reads for all known dataset elements the data
(3) Dataset elements with different data type structure and type. Known dataset elements are
elements configured in the SCD (of the client)
(4) Reordered dataset members in a dataset of and mapped to an internal data objects. Dataset
a different data type elements that are not mapped to an internal data
object are not read from the server. The read
Table 45: PIXIT for Dataset model

1KGT 150 590 V013 1 85

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

Description Value / Clarification

(5) Reordered dataset members in a dataset of data structure and type are used to map received
the same data type dataset elements to internal data objects.

(1) If a server dataset contains additional (new)

elements, the elements are ignored by the client
(internally trashed). All other known elements are
processed as normal in this case.

(2) If elements are missing in a server dataset,

the internal data objects mapped to the missing
dataset elements remain invalid. All other known
elements are processed as normal in this case. If
elements are missing that are not mapped to an
internal data object nothing happens.

(3) If server dataset elements have different data

types than in the client configuration, the client
tries to map the actual data type to the internal
data object. That means the client decodes the
received dataset elements according to the data
types read from the actual server configuration
and tries to map the information to the internal
data objects. Whether the mapping is success-
ful depends on the mismatch. For example a
Boolean data type can be mapped to an integer
type but the other way round information is lost.

(4) If dataset elements are reordered in a server

dataset all known elements are processed as
normal. Unknown reordered dataset elements
are ignored. Different data types are handled as
described in (3).

(5) If dataset elements are reordered in a server

dataset all known elements are processed as
normal. Unknown reordered dataset elements
are ignored.

CAUTION: The above describe configuration

adjustments are done at the first connection
establishment only. If a server disconnects and
re-connects later the configuration of the server
is not read again. In this case the client uses
the read configuration from the first connection
establishment. If the server communication part
(e.g. datasets) is re-configured between two
connection establishments the behavior of the
client is undefined. After a server re-configu-
ration (communication part) the client must be
re-started in any case (see “PIXIT for Server
model”).
Describe how the client behaves in case of: The ACSI service GetLogicalNodeDirecto-
ry(DATA-SET) is not used by the client. The
- GetLogicalNodeDirectory(DATA-SET) client gets the data sets of a logical node from
response- the configured SCD data model of a server. Dif-
ferences between the configured data sets and
Table 45: PIXIT for Dataset model

86 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

the actual data model of a server are not consid-
ered.
Describe how the client behaves in case of: The ACSI service GetDataSetDirectory is used
by the client to read the FCDs of a data set
- GetDataSetDirectory response- during connection establishment. In case of a
negative service response the association to
the server is concluded. Afterwards The client
tries to reconnect the server according the rules
described in "PIXIT for Association model".
Maximum name length for dataset Dataset name: 32 characters (name only)

Maximum name length for dataset member Dataset member: 129 characters (whole object
including LD and FC reference)
Does the client support the creation of:
N
- persistent datasets
N
- non-persistent datasets
Describe how the client behaves in case of: The ACSI services CreateDataSet and Delete-
DataSet are not supported by the client.
- CreateDataSet response-

- DeleteDataSet response-
Describe how the client behaves when it The ACSI service SetDataSetValues is not sup-
receives a [Link]- ported by the client.
What is the maximum number of data elements 300
in one server data set the client can process?
Table 45: PIXIT for Dataset model

11.5.5 PIXIT for Substitution model

Substitution is not supported by the client.

11.5.6 PIXIT for Setting group control model

Description Value / Clarification

How can the Client be forced to send a GetLogi- The client doesn’t use a GetLogicalNodeDirec-
calNodeDirectory (SGCB) request tory (SGCB) request to get the SGCB configura-
tion. The client relies on the SCL data model of
the server used in the client configuration. So, it
is not possible to force a GetLogicalNodeDirec-
tory (SGCB) request.
Describe how to change the active setting group For each setting group control block (SGCB)
found in the SCL data model of a server, the
client provides a single bit string command. This
command can be used to switch the active set-
ting group by providing the number of the group
to set, in the command value.
Describe how to get the actual setting group val- A server supporting setting groups must include
ues the information about the actual active setting
group in a data attribute as part of a data set.
Table 46: PIXIT for Setting group control model

1KGT 150 590 V013 1 87

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

Description Value / Clarification

That means the information about the active
group is sent by the server, on change in a
report. Reading the actual, active setting group
directly is not supported by the client.
Describe how to edit setting group values Edit setting group values is not supported by the
client.
Describe how the client behaves in case of: Reading the actual SGCB values and editing set-
ting group values is not supported by the client.
• GetSGCBValues response-
• SelectEditSG response-
• SetActiveSG response-
• ConfirmEditSGValues response-
Table 46: PIXIT for Setting group control model

11.5.7 PIXIT for Reporting model

Description Value / Clarification

Does the client search for RCB in all logical In the configuration process the tool searches in
nodes? When not specify the logical nodes all logical nodes of a server for RCBs. If the RCB
is assigned to the client and at least one dataset
member is mapped to an internal data object,
the RCB is configured and enabled independent
from the logical node.
Which dynamic RCB attributes are/can be con- RptID Y
figured by the client
DataSet N

Optional fields Y

Trigger conditions Y

Buffer time Y

Integrity period Y
Does the client supports IEDs with indexed and Buffered RCB indexed Y
non-indexed report control blocks (RCB)
Buffered RCB not indexed Y

Unbuffered RCB indexed Y

Unbuffered RCB not indexed Y

The supported trigger conditions are Integrity Y

data change Y

quality change Y

data update Y

general interrogation Y
The supported optional fields are sequence-number Y

report-time-stamp Y
Table 47: PIXIT for Reporting model

88 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

reason-for-inclusion Y

data-set-name Y

data-reference Y

buffer-overflow Y

entryID Y

conf-rev Y
The minimum required optional fields are sequence-number N

report-time-stamp N

reason-for-inclusion Y

data-set-name N

data-reference N

buffer-overflow N

entryID N

conf-rev N
Does the client support segmented reports Y
Does the client support pre-assigned RCB Y

(Pre-assigning is required for the client)

Does the client support indexed RCBs Y
Does the client support reported data set con- reporting of data objects Y
taining structured data objects or data attrib-
utes? reporting of data attributes N

(Note: Unstructured data attributes are

processed by the client, but the other parts in
the device doesn't support them. Therefore the
usage of data attributes are permitted.)
Describe how the client does respond when an The client checks for each URCB whether this
URCB is already reserved by another client for: is already enabled (ACSI service GetURCB-
Values). If the URCB is already enabled the
• Indexed URCB with max>1 configured in client tries to disable the URCB by writing the
SCL (static reporting) flag “RptEna” with false. If this is successful the
• Indexed URCD with max=1 configured in client continues with the URCB setup (reading
SCL (static reporting) and writing the URCB attributes) and enables
• URCB not configured in SCL (dynamic the URCB at the end. If disabling of the URCB
reporting) fails the client concludes the connection to the
server and re-starts the connection according to
the association model.

For enabling the client tries to access the specific

URCB instance according to the configuration
in the SCD file. The URCB instance number is
derived from the position of the client within the
list of the “RptEnabled” tag. For example, if the
client is configured at the second position of the
Table 47: PIXIT for Reporting model

1KGT 150 590 V013 1 89

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

Description Value / Clarification

list the URCB instance number 2 is used when
accessing and enabling the URCB. That means:

If the “max” attribute within the “RptEnabled” tag

is greater 1 (max>1) the accessed instance num-
ber is determined from the client position in the
list.

If the “max” attribute within the “RptEnabled” tag

is 1 (max=1) the client access the instance num-
ber 1 because the client position in the list is 1
also.

In both cases, if the access with the determined

instance number fails, the client tries to access
the URCB without instance number.

Dynamic reporting is not supported by the client.

So, URCBs that are not configured in SCL are
not accessed or enabled.
Describe how the client does respond when a The client checks for each BRCB whether this
BRCB is already reserved by another client for: is already enabled (ACSI service GetURCB-
Values). If the BRCB is already enabled the
• Indexed BRCB with max>1 configured in client tries to disable the BRCB by writing the
SCL (static reporting) flag “RptEna” with false. If this is successful the
• Indexed BRCD with max=1 configured in client continues with the BRCB setup (reading
SCL (static reporting) and writing the BRCB attributes) and enables
• BRCB not configured in SCL (dynamic the BRCB at the end. If disabling of the BRCB
reporting) fails the client concludes the connection to the
server and re-starts the connection according to
the association model.

For enabling the client tries to access the specific

BRCB instance according to the configuration
in the SCD file. The BRCB instance number is
derived from the position of the client within the
list of the “RptEnabled” tag. For example, if the
client is configured at the second position of the
list the BRCB instance number 2 is used when
accessing and enabling the BRCB. That means:

If the “max” attribute within the “RptEnabled” tag

is greater 1 (max>1) the accessed instance num-
ber is determined from the client position in the
list.

If the “max” attribute within the “RptEnabled” tag

is 1 (max=1) the client access the instance num-
ber 1 because the client position in the list is 1
also.

In both cases, if the access with the determined

instance number fails, the client tries to access
the BRCB without instance number.
Table 47: PIXIT for Reporting model

90 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

Dynamic reporting is not supported by the client.
So, BRCBs that are not configured in SCL are
not accessed or enabled.
Describe how the client does respond on a Set- If the service to write the EntryID fails an internal
BRCBValues(EntryID) respond- minor error is generated that can be seen with a
device specific log tool. The internal minor error
has no influence on the processing of the report
control block.
Describe how the client does respond when a With the first connection establishment the client
report has an unknown: dataset, RptID, unex- reads the actual configuration of a dataset. This
pected number of dataset entries, and/or unex- information is stored and used for the decoding
pected data type format entries of reports containing this dataset. The datasets
read by the client are selected from the SCD
configuration of the client. That means:

• Additional datasets configured in the server

but not in the client are ignored.
• Datasets missing in the server don’t lead to
an error and the processing continues with
the next dataset.
• Different named datasets are not detected
and handled as missing datasets (continue
with next dataset).

For accessing and enabling of reports the clients

uses the RptID from the SCD configuration. That
means:

• Additional reports configured in the server but

not in the client are ignored.
• Reports missing in the server lead to a con-
clusion of the connection.
• Different named reports are not detected and
handled as missing reports (connection con-
clude).

For the handling of dataset configuration mis-

matches see “PIXIT for Dataset model”.
Describe how the client detects reporting con- Report configuration mismatches are not
figuration changes (mismatches). Does it check detected by the client (see description above).
the "configuration revision" attributes and/or During first connection establishment the actual
does it check the dataset members? Is the dataset configuration is read. This allows adap-
dataset update done online or offline? tation to dataset configuration changes (for
detailed information see “PIXIT for Dataset
model”). The adaptation to dataset changes are
done online but at the first connection establish-
ment only.

The "configuration revision" attribute is ignored.

Describe how to force the client to change the The buffer time is set to the value configured
RCB BufTm in the SCD file. By revising the SCD file and
reconfiguring the client the buffer time can be
changed.
Table 47: PIXIT for Reporting model

1KGT 150 590 V013 1 91

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

Description Value / Clarification

Does the client set server trigger option GI prior N
to first issuance of GI command?
Describe how to force the client to send the GI During each connection establishment all cor-
request rect configured RCBs are enabled by the client.
If enabling is successful GI requests are send for
the RCBs.
Describe how to force the client to enable a During each connection establishment all correct
RCB configured RCBs are enabled by the client.
Describe how the client does respond when a For accessing and enabling of reports the clients
report control block is renamed or deleted: uses the RptID from the SCD configuration
always. The client doesn't detect when an RCB
• Does it prevent reading the deleted RCB? is renamed or deleted on the server. The client
• If is reads the missing RCB, how does it tries to access the RCB and concludes the con-
handle the GetXRCBValues response-? nection as result of a negative response. After-
wards the connection is re-started according to
the association model.
Describe how the client behaves when it The buffer overflow flag is ignored by the client.
receives a report that has the buffer overflow
flag set?
Describe how to force the client to write a (valid) Connect a server and send some reports to
EntryID value. client with included EntryID. Then disconnect the
server. With the following reconnect the client
sets the last received EntryID before enabling
the report.
Describe how to force the client to purge the The client purges the report buffer of a server
report buffer. during the first connection establishment after
start-up only. At any further connection establish-
ments during the runtime of the server the report
buffer is not purged.

To force the client to purge the report buffer of a

server, reset the client and wait for the first con-
nection establishment to the server.
Describe how the client responds when it The ACSI services GetXRCBValues are used by
receives a [Link]- the client to read the attributes of report control
blocks. If reading of specific attributes fails with a
negative response an internal minor error is gen-
erated that can be seen with a device specific log
tool. The internal minor error has no influence on
the processing of the report control block.
Describe how the client responds when it The ACSI services SetXRCBValues are used by
receives a [Link]- the client to write the attributes of report control
blocks. If writing of specific attributes fails with a
negative resposne (e.g. BufTm) an internal minor
error is generated that can be seen with a device
specific log tool. In most of the cases the internal
minor error has no influence on the processing
(enabling) of the report control block.

But if the RptID cannot be written the actual

RptId from the server is taken for enabling the
report. And if the trigger options cannot be writ-
Table 47: PIXIT for Reporting model

92 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

ten at all (read back trigger options are 0) the
connection is concluded.
Describe how the client responds when it tries The client checks for each RCB whether this is
to use a RCB that is reserved by another client already enabled by another client. If the RCB
is already enabled the client tries to disable the
RCB by writing the flag “RptEna” with false. If
this is successful the client continues with the
RCB setup (reading and writing the RCB attrib-
utes) and enables the RCB at the end. If dis-
abling of the RCB fails the client concludes the
connection to the server and re-starts the con-
nection according to the association model.
Describe how the client behaves when it The client supports all optional fields (see above)
receives a report that contains optional fields but if reason-for-inclusion is missing in the report,
that are not supported by the client not changed data elements (e.g. integrity report)
are not processed.
Describe how the client behaves when it All trigger options are supported by the client.
receives a report that was caused by one or
more trigger conditions that are not supported
by the client
Describe how the client behaves when it During the connection establishment the client
encounters an RCB with a different confRev reads the report control block configuration revi-
value than expected sion from the data model of the server and com-
pares the value with the revision from the SCD
file. In case of a mismatch an internal minor error
is generated that can be seen with a device spe-
cific log tool. The internal minor error has no
influence on the processing of the report control
block.

The confRev value send in the actual report is

ignored and the report is processed according
the read data model information.
Describe how the client responds when it sets The EntryID send by the server in an actual
an EntryID value that is not recognized by the report is not checked by the client against the
server. last set EntryID.
Are there a maximum number of report control The maximum number of report control blocks
blocks that the client can enable? per server are:

- 1000 buffered reports

- 1000 unbuffered reports

(Practically the limitation is the number of data

objects that can be handled by the client)
Does the client support writing resvTms? N
Does the client support writing owner? N
Table 47: PIXIT for Reporting model

11.5.8 PIXIT for Logging model

Logging is not supported by the client.

1KGT 150 590 V013 1 93

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

11.5.9 PIXIT for Generic substation events model

GOOSE communication is not supported by the client.

11.5.10 PIXIT for Control model

Description Value / Clarification

What control modes are supported Y status-only

Y direct-with-normal-security

Y sbo-with-normal-security

Y direct-with-enhanced-security

Y sbo-with-enhanced-security
Is Time activated operate (operTm) supported N
Is “operate-many” supported N
Can the client set the test flag? Y
What check conditions can be set Y synchrocheck

Y interlock-check
Which originator categories are supported and The supported originator categories are sta-
what is the originator identification? tion-control and remote-control. The originator
identification is an internal decimal number rep-
resenting the functionality that is the origin of the
command.
Describe if and how the client sets/increments The control sequence number is set to 0 always.
the ctlNum
What does the client do when it receives a The AddCause from the LastApplicationError is
LastApplicationError and describes how to view added to the negative command response and
the additional cause? send to the originator. The AddCause can be
accessed / processed in a user application pro-
gram (PLC) only.
What does the client do when it receives a The negative command response is send to the
Select, SelectWithValue or Operate respond originator. The further processing depends on
negative? the originator (e.g. host communication protocol
or web server). In case the originator is the web
server an error message is shown.
Can the client change the control model via N
online services?
What does the client do when the ctlModel is It is not possible to configure the client when the
not initialized in the SCL? control model (ctlModel) is not initialized.
What does the client when the ctlModel in the The client uses the ctlModel configured in
SCD and in the server is different? the SCD always. If the server with a different
ctlModel responds negative to a control request
the command originator (e.g. host communi-
cation protocol or web server) gets a negative
command response. If the server with a different
ctlModel responds positive to a control request
the command is processed as normal.
Describe how the client responds when it The positive command response is send to the
receives a positive Command Termination originator. The further processing depends on
Table 48: PIXIT for Control model

94 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

the originator (e.g. host communication protocol
or web server). In case the originator is the web
server a success message is shown.
Describe how the client responds when it The negative command response is send to the
receives a negative Command Termination originator. The further processing depends on
the originator (e.g. host communication protocol
or web server). In case the originator is the web
server an error message is shown.
Describe how the client responds when it The negative command response is send to the
receives a negative Operate response originator. The further processing depends on
the originator (e.g. host communication protocol
or web server). In case the originator is the web
server an error message is shown.
Describe how the client responds when it The positive command response is send to the
receives a positive Cancel response originator. The further processing depends on
the originator (e.g. host communication protocol).
Describe how the client responds when it The negative command response is send to the
receives a negative Command Termination originator. The further processing depends on
the originator (e.g. host communication protocol).
Table 48: PIXIT for Control model

11.5.11 PIXIT for Time and time synchronization model

Description Value / Clarification

Described how to view the internal time & qual- View: The internal time and quality
ity or how to expose the timestamp and time-
stamp quality via the IEC 61850 interface (synchronized or not synchronized) can be

Viewed in the web server provided by the

Client.

Expose: The internal time is added to the Oper-

ate

Request and can be exposed there.

What time quality bits are supported Y LeapSecondsKnown

Y ClockFailure

Y ClockNotSynchronized
What is the behaviour when the time synchro- Depending on the kind of time synchronization
nization signal/messages are lost (e.g. internal real time clock, SNTP, host commu-
nication protocol) the internal time quality is set
to not synchronized:

• when the real time clock indicates a not reli-

able time
• or after a configurable time (SNTP, host com-
munication protocol.
When is the quality bit "ClockFailure" set? The time quality bit "ClockFailure” is set:

- At start-up before synchronization

Table 49: PIXIT for Time and time synchronization model

1KGT 150 590 V013 1 95

Protocol Implementation extra Information for Testing (PIXIT) Conformance Statements

- When after synchronization for a configurable

time (typical 10 minutes) no new synchronization
is received.
When is the quality bit "ClockNotSynchronized” The time quality bit "ClockNotSynchronized” is
set? set:

- At start-up before synchronization

- When after synchronization for a configurable

time (typical 10 minutes) no new synchronization
is received.
When is the quality bit "LeapSecondsKnown" The quality bit "LeapSecondsKnown" is set,
set? when the internal time gets synchronized.
Table 49: PIXIT for Time and time synchronization model

11.5.12 PIXIT for File transfer model

Description Value / Clarification

Describe when or how to force the client to After start-up and connection establishment
request GetServerDirectory(FILE) and what it the directories of all for file transfer configured
does with the responded filenames servers are read. Afterwards the directories are
requested in a time interval of 30 seconds.

The responded filenames are used to extract a

unique file number to determine whether the file
was already transferred to the client. In case no
file number is provided new files are identified
by name, size and time of last modification. New
detected files are then requested by the client.
Does the client uses a wildcard in the The used wildcard depends on the configured
GetServerDirectory(FILE) request server type. The client supports no wildcard,
wildcard = “*” and wildcard = “*.*”.
Does the client support IEDs that include the Y* path included
path in the file name in the GetServerDirecto-
ry(FILE) respond? Y* path not included
* the actual type must be configured
Does the client support IEDs that use the file Y* “/”
separator
Y* “\”

* the actual separator must be configured

(defined by IED type)
What is the maximum file name size including 255 characters
path
Can the client read a file with size 0 Y
Are directory/file name case sensitive The directory/file name is used as it is received
from the server. The extraction of the file number
from the file name (server dependent) is case
sensitive.
Maximum file size 512 Kbytes

In case the files are zipped by the client during

reading from server (server dependent) the max-
imum file size applies to the resulting ZIP file on
Table 50: PIXIT for File transfer model

96 1KGT 150 590 V013 1

Conformance Statements Protocol Implementation extra Information for Testing (PIXIT)

Description Value / Clarification

the client.
Note: If a file on the server exceeds the maxi-
mum size the client will not request any further
files from the server till the file is removed.
Describe how the client behaves in case of: The request is discarded and the processing
continues as normal. The affected server is
- GetFileAttributes response- requested again after the defined polling interval.

Note: If a file on the server can not be accessed

the client will not request any further files from
the server till the access is possible again.
Table 50: PIXIT for File transfer model

11.5.13 PIXIT for Service Tracking model

Service tracking is not supported by the client.

11.6 SCL Implementation Conformance Statement

(SICS)
This SICS is applicable for:

• Tool name: RTUtil500

• Main role: ICT
• Version: 12.4

The following tables contain mandatory and optional features of System Configuration tools and IED
configuration tools. It is up to the tool manufacturer to decide to which extent his tool fulfills one or
both roles. At least for one main role all mandatory features shall be supported.

The IED configurator features can also partly be implemented within the IED itself, if it can
be configured by an SCD or CID file. In this case the conformance statement refers to the
combination of IED and IED configurator tool. If an IED tool supports several IED types with
different engineering capabilities, then for each combination of tool and IED type a separate IED
configurator conformance statement should be given.

The features are grouped. If a group is mandatory, then at least all mandatory features of this group
shall be implemented. If a group is optional, then either all features of this group shall be missing, or
at least all mandatory ones shall be implemented.

The result of an export function can be checked in the generated SCL file. The result of an import
can be checked by tool behaviour, and at the final configured IED, by browsing through it or by its
communication behaviour.

Mandatory/ Value/
optional comments
ICD export M
I11 Fix ICD file (no adaptable export needed) GC_1 (1) NO
I12 Export of ICD file or IID file according to IED precon- GC_1 (1) YES
figuration performed by tool
Table 51: IED configurator conformance statement

1KGT 150 590 V013 1 97

SCL Implementation Conformance Statement (SICS) Conformance Statements

Mandatory/ Value/
optional comments
I13 State the data model name space (61850-7-3 sub- M YES
clause 7.2) within ICD file ([Link] value)
I14 State the data model version (61850-7-3 subclause M YES
7.8.3) and any predefined / fixed configuration values
within ICD file ([10] [Link])
I15 Version 2003 export GC_1 (2) YES
I16 Version 2007A export GC_1 (2) YES
I17 Predefined data sets O YES
I18 Predefined control blocks O YES
I19 Substation bay template with IED part O NO
I110 Communication section with default address O YES
I111 Export correct valKind value ([10] Table 46) O YES
(RO)
I112 Exports internal addresses as InRef or Input section O NO
(subclause 285H 9.3.13)
I113 Exports internal addresses in Input section with O NO
expected serviceType (subclause [10] 9.3.13)
I114 Exports in UTF-8 coding M YES
SCD import M
I21 Identify IED to be configured in SCD file by IED M YES
name
I22 Configure LD name (at least via ldInst, dependent on M YES
the IED capabilities) and IED addresses from SCD
I23 Determine communication side addresses of IED C1 YES
inputs from SCD
I24 Determine and use clock communication addresses C1 NO
from SCD
I25 Configure values of (existing) control block from C3 NO
SCD([10] 9.3)
I26 Prepare (new) control block instances according to C3 NO
SCD file
I27 Prepare / configure data sets according to SCD file C3 NO
I28 Modify predefined data sets according to SCD C3 NO
I29 Interpret client references in the control blocks of C1 YES
other IEDs to find the control block instances allo-
cated to this IED, and data sent to this IED.
I210 Set IED configuration values and parameter values O NO
as defined in SCD file
I211 Support changed (reduced capability) valKind (e.g. O NO
from Set to RO or to Conf) ([10] Table 46)
I212 Support ldName on other IEDs ([10] 9.3.4) C3 NO
I213 Interpret input signal references to source control O YES
blocks (290H 9.3.13)
I214 Imports UTF-8 coding of XML M YES
IID export after IED engineering
Table 51: IED configurator conformance statement

98 1KGT 150 590 V013 1

Conformance Statements SCL Implementation Conformance Statement (SICS)

Mandatory/ Value/
optional comments
I31 IED version and instance information: [Link]- O NO
Nam: hwRev, swRev, serNum, [Link]-
gRev
I32 Configuration values (fc=CF) O NO
I33 Setting Parameter values (fc=SP, SG) O NO
I34 SCL Header management ([10] 9.1) C3 NO
I35 Modify IED data model (add LN/Data object/LD, or O NO
remove unused LD/LN/Data object)
Tool functionality
I41 Support MustUnderstand concept ([10] 8.2) M YES
I42 Bind incoming 61850 signals to IED internal (input) C1 YES
signals
I43 Use or create IED Input section for binding incom- O YES
ing (external) signals to internal signals, to document
this binding
I44 Create CID file for IED O NO
I45 Support ldName for LD name specification C3 YES
I46 Modify LN prefixes or lnInst O YES
(Both can
be set as
wanted)
C1 - Mandatory, if the IED can receive data from other IEDs, i.e. be either client or sub-
scriber

C2 - Mandatory, if any of the other features in this table section is supported.

C3 - Mandatory, if the appropriate IED capability is claimed in PIXIT or IED capability

section.

GC_1 (n) - At least one of the elements of group n shall be available.

O - Optional; should match the IED capabilities; i.e. if an IED claims that RCBs can be
configured by SCL, then the IED tool shall support it.

M - Mandatory
Table 51: IED configurator conformance statement

1KGT 150 590 V013 1 99

SCL Implementation Conformance Statement (SICS) Conformance Statements

100 1KGT 150 590 V013 1

Glossary

12 Glossary
ACSI Abstract Communication Service Interface

AMI Analog Measured value Input

ASO Analog Setpoint command Output

BSI Bit String Input

BSO Bit String Output

CA Certificate Authority

CMU Communication and Data Processing Unit

DCO Double Command Output

DMI Digital Measured value Input (8, 16 bit)

DO Digital Output

DPI Double Point Input

DSO Digital Setpoint command Output (8, 16 bit)

FC Functional Constraint

FDR File transfer directory

FSO Floating Setpoint Command Output

FTR File transfer file

GOOSE Generic Object Oriented Substation Event

HTTPS Hypertext Transfer Protocol Secure

IEC International Electrotechnical Commission

IED Intelligent Electronic Device

ITI Integrated Totals Input

Max Maximum

MFI Analog Measured value Floating Input

Min Minimum

OSI Open Systems Interconnection Model

PC Personal Computer

PDU Protocol Data Unit

PLC Programmable Logic Control

PRP Parallel Redundancy Protocol

RCO Regulation step Command Output

RTU Remote Terminal Unit

SBO Select before Operate

1KGT 150 590 V013 1 101

 Glossary

SCD Substation Configuration Description

SCI Sub-Device Communication Interface

SCL Substation Configuration description Language

SCO Single Command Output

SCSM Specific Communication Service Mapping

SNTP Simple Network Time Protocol (according to RFC 4330)

SPI Single Point Input or Single point information

SPS Programmable Logic Control (Speicherprogrammierbare Steuerung)

SSC System Single Command

STI Step position Input

TCP/IP Transmission Control Protocol / Internet Protocol

102 1KGT 150 590 V013 1

1KGT 150 590 V013 1 103
 Note:

The specifications, data, design or other information contained in this document (the “Brochure”)
- together: the “Information” - shall only be for information purposes and shall in no respect be
binding. The Brochure does not claim to be exhaustive. Technical data in the Information are only
approximate figures. We reserve the right at any time to make technical changes or modify the
contents of this document without prior notice. The user shall be solely responsible for the use of
any application example or information described within this document. The described examples
and solutions are examples only and do not represent any comprehensive or complete solution.
The user shall determine at its sole discretion, or as the case may be, customize, program or add
value to the Hitachi Energy products including software by creating solutions for the end customer
and to assess whether and to what extent the products are suitable and need to be adjusted or
customized.

This product is designed to be connected to and to communicate information and data via a network
interface. It is the users sole responsibility to provide and continuously ensure a secure connection
between the product and users or end customers network or any other network (as the case may
be). The user shall establish and maintain any appropriate measures (such as but not limited to the
installation of firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc) to protect the product, the network, its system and the interface against
any kind of security breaches, unauthorized access, interference, intrusion, leakage and/or theft
of data or information. Hitachi Energy is not liable for any damages and/or losses related to such
security breaches, any unauthorized access, interference, intrusion, leakage and/or theft of data or
information.

Hitachi Energy shall be under no warranty whatsoever whether express or implied and assumes
no responsibility for the information contained in this document or for any errors that may appear
in this document. Hitachi Energy's liability under or in connection with this Brochure or the files
included within the Brochure, irrespective of the legal ground towards any person or entity, to which
the Brochure has been made available, in view of any damages including costs or losses shall be
excluded. In particular Hitachi Energy shall in no event be liable for any indirect, consequential or
special damages, such as – but not limited to – loss of profit, loss of production, loss of revenue,
loss of data, loss of use, loss of earnings, cost of capital or cost connected with an interruption
of business or operation, third party claims. The exclusion of liability shall not apply in the case
of intention or gross negligence. The present declaration shall be governed by and construed in
accordance with the laws of Switzerland under exclusion of its conflict of laws rules and of the
Vienna Convention on the International Sale of Goods (CISG).

Hitachi Energy reserves all rights in particular copyrights and other intellectual property rights.
Any reproduction, disclosure to third parties or utilization of its contents - in whole or in part - is not
permitted without the prior written consent of Hitachi Energy.

ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Energy company.

© 2022 Hitachi Energy.

All rights reserved.

104 1KGT 150 590 V013 1

1KGT 150 590 V013 1 105
Visit us

Hitachi Energy Germany AG

P.O. Box 42 01 30
68280 Mannheim, Germany

[Link]/rtu

1KGT 150 590 V013 1