511269-UEN CPM PWC600I 61850 1p0
511269-UEN CPM PWC600I 61850 1p0
511269-UEN CPM PWC600I 61850 1p0
The software and hardware described in this document is furnished under a license and may
be used or disclosed only in accordance with the terms of such license.
This product includes software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/).
This product includes software provided by the jQuery Foundation (http://jquery.org/) and by
the Flot project (http://www.flotcharts.org/).
Trademarks
ABB and Relion are registered trademarks of the ABB Group. Switchsync is a trademark of the
ABB Group. All other brand or product names mentioned in this document may be trademarks
or registered trademarks of their respective holders.
Warranty
Please inquire about the terms of warranty from your nearest ABB representative.
ABB AB
Substation Automation Products
SE-721 59 Västerås
Sweden
Telephone: +46 (0) 21 32 50 00
Facsimile: +46 (0) 21 14 69 18
http://www.abb.com/substationautomation
Disclaimer
The data, examples and diagrams in this manual are included solely for the concept or product
description and are not to be deemed as a statement of guaranteed properties. All persons
responsible for applying the equipment addressed in this manual must satisfy themselves that
each intended application is suitable and acceptable, including that any applicable safety or
other operational requirements are complied with. In particular, any risks in applications where
a system failure and/or product failure would create a risk for harm to property or persons
(including but not limited to personal injuries or death) shall be the sole responsibility of the
person or entity applying the equipment, and those so responsible are hereby requested to
ensure that all measures are taken to exclude or mitigate such risks.
This document has been carefully checked by ABB but deviations cannot be completely ruled
out. In case any errors are detected, the reader is kindly requested to notify the manufacturer.
Other than under explicit contractual commitments, in no event shall ABB be responsible or
liable for any loss or damage resulting from the use of this manual or the application of the
equipment.
Conformity
This product complies with the directive of the Council of the European Communities on the
approximation of the laws of the Member States relating to electromagnetic compatibility
(EMC Directive 2004/108/EC) and concerning electrical equipment for use within specified
voltage limits (Low-voltage directive 2006/95/EC). This conformity is the result of tests
conducted by ABB in accordance with the product standard EN 60255-26 for the EMC directive,
and with the product standards EN 60255-1 and EN 60255-27 for the low voltage directive. The
product is designed in accordance with the international standards of the IEC 60255 series.
Table of contents
Table of contents
Section 1 Introduction.........................................................................................................5
1.1 This manual......................................................................................................................................... 5
1.2 Intended audience............................................................................................................................. 5
1.3 Product documentation................................................................................................................... 5
1.3.1 Product documentation set........................................................................................................ 5
1.3.1.1 Related documents.................................................................................................................... 5
1.3.2 Document revision history...........................................................................................................6
1.4 Symbols and conventions................................................................................................................ 6
1.4.1 Symbols........................................................................................................................................... 6
1.4.2 Document conventions................................................................................................................ 6
1.4.3 Functions included in Switchsync PWC600..............................................................................7
1
Communication Protocol Manual
Table of contents
2
Communication Protocol Manual
Table of contents
Section 9 Glossary..............................................................................................................81
3
Communication Protocol Manual
4
1MRK 511 269-UEN D Section 1
Introduction
Section 1 Introduction
This manual addresses the communication system engineer or system integrator responsible
for pre-engineering and engineering for communication setup in a substation from an IED
perspective.
The system engineer or system integrator must have a basic knowledge of communication in
protection and control systems and thorough knowledge of the specific communication
protocol.
The user manual provides basic instructions on how to install and use Switchsync PWC600.
The manual provides instructions for engineering, mechanical and electrical installing,
commissioning and operating, to cover the common use cases of the product.
The cyber security deployment guideline describes setting up a secure system, including
password procedures and levels of access in the system.
The technical manual contains application and functionality descriptions and lists function
blocks, logic diagrams, input and output signals, setting parameters and technical data sorted
per function. The manual can be used as a technical reference during the engineering phase,
installation and commissioning phase, and during normal service.
5
Communication Protocol Manual
Section 1 1MRK 511 269-UEN D
Introduction
1) Switchsync PWC600 1.0 is based on ABB 650 series, version 1.3. So the PIXIT and TICS from ABB 650 series,
version 1.3 are applicable for Switchsync PWC600 1.0 too.
The information icon alerts the reader of important facts and conditions.
The tip icon indicates advice on, for example, how to design your project or
how to use a certain function.
Although warning hazards are related to personal injury, it is necessary to understand that
under certain operational conditions, operation of damaged equipment may result in
degraded process performance leading to personal injury or death. It is important that the
user fully complies with all warning and cautionary notices.
• Abbreviations and acronyms in this manual are spelled out in the glossary. The glossary
also contains definitions of important terms.
• Push button navigation in the LHMI menu structure is presented by using the push button
icons.
For example, to navigate between the options, use and .
• HMI menu paths are presented in bold.
For example, select Main menu/Settings.
• LHMI messages are shown in Courier font.
For example, to save the changes in non-volatile memory, select Yes and press .
• Parameter names are shown in italics.
6
Communication Protocol Manual
1MRK 511 269-UEN D Section 1
Introduction
For example, the function can be enabled and disabled with the Operation setting.
7
Communication Protocol Manual
Section 1 1MRK 511 269-UEN D
Introduction
Table 2: Control
IEC 61850 or function name Function description
DPGGIO IEC61850 generic communication I/O functions
POS_EVAL Evaluation of position indication
VSGGIO Selector mini switch
SSCPOW Controlled switching strategy function
Table 4: Logic
IEC 61850 or function name Function description
OR Configurable logic blocks
INVERTER
PULSETIMER
GATE
XOR
LOOPDELAY
TimerSet
AND
SRMEMORY
RSMEMORY
FXDSIGN Fixed signal function block
B16I Boolean 16 to Integer conversion
B16IFCVI Boolean 16 to Integer conversion with Logic Node representation
IB16A Integer to Boolean 16 conversion
IB16FCVB Integer to Boolean 16 conversion with Logic Node representation
MINMAX Logical function to determine the minimum and maximum value
Table 5: Monitoring
IEC 61850 or function name Function description
CVMMXN Measurements
CMMXU Phase current measurement
VMMXU Phase-phase voltage measurement
CMSQI Current sequence component measurement
VMSQI Voltage sequence measurement
VNMMXU Phase-neutral voltage measurement
AISVBAS Service values presentation of the analog inputs
TM_P_P2 Service value presentation of primary analog inputs 600TRM
TM_S_P2 Service value presentation of secondary analog inputs 600TRM
MU_P_S1 Service value presentation of analog inputs Merging Unit 1
MU_P_S2 Service value presentation of analog inputs Merging Unit 2
Table continues on next page
8
Communication Protocol Manual
1MRK 511 269-UEN D Section 1
Introduction
9
Communication Protocol Manual
10
1MRK 511 269-UEN D Section 2
Introduction to IEC 61850
The general scope of the IEC 61850 protocol standard is designed to support the
communication of all functions being performed in the substation. Its’ main goal is
interoperability; this is the ability for IEDs from one or different manufacturers to exchange
information and use the information for their own functions. Moreover, the standard allows a
free allocation of these functions and accepts any system philosophy, from a distributed
architecture (for example, decentralised substation automation) to a centralised configuration
(for example, RTU based).
The standard separates the functionality represented by the data model and the related
communication services from the communication implementation (stack).
The data model of the standard is an object-oriented one, grouping the data into the smallest
possible sets referring to the smallest possible functions to be implemented independently.
These smallest possible data groups or functions are named logical nodes. The logical nodes
and all data and attributes contained are named according to a standardised semantic, which
is mandatory.
This manual describes how the IEC61850 standard is applied in Switchsync PWC600.
References and brief descriptions of the standard are also included. It is assumed that the
reader has basic knowledge of the IEC 61850 standard.
The following parts of the IEC61850 standard are of importance as they relate to this manual:
• Station Configuration description Language (SCL) is described in IEC 61850-6. The SCL is
an XML based definition of how to describe the parts of a substation. This part of the
standard also includes the roles of different tools as well as the engineering concepts.
• Communication profile (IEC 61850 stack) is described in IEC 61850-8-1. This part of the
standard includes a number of possible communication profiles, and how the services
defined in IEC 61850-7-2 are mapped to the communication profile.
• Communication services are described in IEC 61850-7-2. This part deals mainly with the
communication facilities from client and server point of view. It includes the different
possibilities of communication functionality.
• Logical node data model. This is described in IEC 61850-7-3 and IEC 61850-7-4.
• Conformance tests and the basis for conformance documents are handled in IEC
61850-10.
Detailed information regarding the IEC61850 implementation of the IED is described inside the
conformance documents.
The conformance documents are unique for each product release and refer to each other; the
identities included in the related documents refer to a specific version of the IED.
11
Communication Protocol Manual
Section 2 1MRK 511 269-UEN D
Introduction to IEC 61850
The communication profile in IEC 61850 uses the MMS standard, which uses Ethernet and
TCP/IP to handle the information transport within the substation.
The data modelling uses the concept of logical nodes to identify the published information for
communication. The standard defines a set of logical nodes, each representing a
communication view of a process function with a number of data objects. For example, a
transformer differential - or line differential protection, because the standard defines only a
differential protection. Therefore, it is possible to adapt the logical node, which is defined in
the standard, as a logical node class. The standard defines methods to describe the actually
used logical node as a logical node type which is then based upon the logical node class. This
allows all partners to interpret the logical node type information because the description is
completely given in the standard. The type description of all logical nodes is part of the Data
Type Template (DTT) section in the SCL description file of a station or the IED.
Besides the information about the configuration of the communication facilities, this manual
contains the full description of all logical nodes available in the IED. The information about the
logical nodes and their data objects may be used to identify which signals are available for the
functions as described in the technical manual. The link to the technical manual is done in the
logical node tables by listing the signal name as given in the function block, or as seen in
PCM600 or the LHMI.
Use the latest revision of the documents listed, unless stated otherwise.
Document ID Title
IEC 61850-5 Communication networks and systems in
First edition 2003-07 substations -
Ref. number: IEC 61850-5:2003(E) Part 5:
Communication requirements for functions and
devices models
IEC 61850-6 Communication networks and systems in
First edition 2004-03 substations -
Ref. number: IEC 61850-6: 2004(E) Part 6:
Configuration description language for
communication in electrical substations related to
IEDs
IEC 61850-7-1 Communication networks and systems in
First edition 2003-07 substations -
Ref. number: IEC 61850-7-1: 2003(E) Part 7-1:
Basic communication structure for substations and
feeder equipment -
Principles and models
IEC 61850-7-2 Communication networks and systems in
First edition 2003-05 substations -
Ref. number: IEC 61850-7-2: 2003(E) Part 7-2:
Basic communication structure for substations and
feeder equipment -
Abstract communication service interface (ACSI)
IEC 61850-7-3 Communication networks and systems in
First edition 2003-05 substations -
Ref. number: IEC 61850-7-3: 2003(E) Part 7-3:
Basic communication structure for substations and
feeder equipment -
Common data classes
Table continues on next page
12
Communication Protocol Manual
1MRK 511 269-UEN D Section 2
Introduction to IEC 61850
1) Since Switchsync PWC600 version 1.0 is based on ABB IED 650 series version 1.3, the PIXIT and TICS of ABB
IED 650 version 1.3 are applicable to this product also. The PICS of ABB IED 650 series version 1.3 was
modified to include additional implementation information on handling of sampled values data, which is a
feature available only in Switchsync PWC600.
13
Communication Protocol Manual
14
1MRK 511 269-UEN D Section 3
Substation Configuration description Language (SCL)
Three different types of SCL files - SCD, CID and ICD, can be exported from PCM600.
The SCL language is based on XML. However, detailed knowledge of the XML contents is not
needed.
The SCL XML file (ICD/SCD/CID) contains five sections, which are specified in IEC 61850-6
clause 9.
• Header
• Substation section describes the functional structure and its relation to primary devices.
• Communication section describes the connection between the IED access points to the
respective subnetwork. and includes also the properties (addresses) of the access points.
• IED section contains a description of the supported communication services, the access
point(s) and the IEDs logical devices, logical nodes and their attributes.
• Data type template section contains a declaration of all types used in the SCL file, logical
nodes type, data object types, attributes and enums.
The system structure is defined by the organization of the plant structure in PCM600. The
signal engineering and the signal routing are IET600 tasks. The IED needs to be configured
with PCM600 before the system is configured with IET600.
The IED section contains the logical node types included in the respective IED configuration
and the data sets and the control blocks configured by IET600. The data sets and the control
blocks are logically defined as part of the logical nodes (see IEC 61850-7-2 clause 9). IET600
also needs a correctly configured communication section for GOOSE engineering.
The data type templates section provides the correct content description of each logical node
type to all tools and users (clients) of the information. Each IED and vendor may have their own
logical node type definitions included in the data type template section together with all other
logical node types based on the standard.
15
Communication Protocol Manual
Section 3 1MRK 511 269-UEN D
Substation Configuration description Language (SCL)
Substation
VoltageLevel
Station
Bay
LNode
IED LD LN
IED LD LN
Communucation
Commun
Subnetwork
Connected AP
IED Name AccessPoint Address GSE
IED Name AccessPoint Address GSE
IED
Services AccessPoint
Server
Authentication
LDevice
LN0 LN
DataSet DOI
DAI
Report Control
GOOSE Control
Inputs
DOI
IED
SettingControl
DataTypeTemplates
LNodeType
DO
DOType
DOType
DA SDO
DAType
DAType
BDA
EnumType
EnumType
IEC08000178.vsd
D0E801T201305151541 V1 EN-US
A reference to GOOSE Control Blocks (GoCB) is included in the communication section when
GoCB is configured.
The substation description in IEC 61850-6 clause 9 describes the arrangement of the primary
equipment. In addition, it also includes a list of the applied logical nodes and the relation of
those logical nodes to the primary equipment.
16
Communication Protocol Manual
1MRK 511 269-UEN D Section 3
Substation Configuration description Language (SCL)
The organization of the physical IEDs to the communication network is independent of the
substation structure. The IEC 61850 standard defines the communication network with no
relation to an existing media or protocol. The mapping to an existing media and protocol is
specified in IEC 61850-8-1.
The IEC 61850 standard describes in part 7-2 the ACSI in a media and protocol independent
form. Part 8-1 specifies the mapping of this ACSI to the existing MMS.
The communication section describes how information is routed between the IEDs and
contains the following parts:
• Subnetworks
• IEDs connected to different subnetworks
• Access points per IED to subnetworks
• Address
• IP address of LAN network (is exceptionally part of the address elements)
• Link to GoCB message in transmission direction (extended during signal engineering and
routing)
IED IED
(client) (client)
- Access Point (AP) - Access Point (AP)
- Address - Address
- GSE; GoCBs - GSE; GoCBs
Communication Communication
Subnetwork AP
AP
en06000101.vsd
D0E771T201305151541 V1 EN-US
The IED section describes the complete IED as it is needed for IEC 61850 communication and
signal engineering. The data type template part of an IED may be seen as part of the IED, even
when separated in its own section. The IED's ICD files include the description of the logical
nodes, their data type templates and the used or supported services. The structure of the IED
section follows the definitions made in the IEC 61850 standard.
17
Communication Protocol Manual
Section 3 1MRK 511 269-UEN D
Substation Configuration description Language (SCL)
• Station level IEDs are located on the station level and are identified as client IEDs when
they read or write information from or to the bay IEDs. This functionality is represented by
logical nodes of group “Information (I)”. These are the logical nodes (LN) = ITCI, IHMI and
ITMI. Client IEDs are the receiver of information in monitoring direction and sender of
commands (control). These logical nodes have no data objects. They are only used to link
the report control blocks (BRCBs and URCBs) from the server IEDs. They have to read their
information about the signals and the signal configuration from the bay IEDs. This is
possible by checking all control blocks for a link to it as a client.
• Bay level IEDs are located on the bay level and are identified as server IEDs when they read
or write information vertically. When GOOSE messages are received, the bay level IED also
has the client role.
Subnetwork
AP
Server IED
SB1.SS_1
Logical
Node
LLN0
LPHD Data
SSXCBR1 Mod
SSXCBR2 Beh
SSXCBR3 Health
Data
SSCPOW1 NamePlt Attribute
Pos stVal
Loc q
OpCnt t
BlkOpn ctlModel
BlkCls
CBOpCap
POWCap
D0E773T201305151541 V1 EN-US
The data objects represent information signals that may be routed to station level IEDs or to
other bay IEDs that are communicating via GOOSE. The signal engineering task is to select the
requested signals (DOs) and link them to the client IEDs as receiver. When using a dataset for
MMS, the requested signals are DOs but when creating a dataset for GOOSE messaging, DAs
18
Communication Protocol Manual
1MRK 511 269-UEN D Section 3
Substation Configuration description Language (SCL)
are used. The control services are not directly engineered. They are included in the data
objects, which handle both the command (control) and the response (monitoring). When
assigning the DOs in monitoring direction, the control is understood by the clients.
The number of data objects and data attributes per DO is defined by the used LN type in the
IED. The content of logical node types and DO types are defined in the DTT. This also means
that the definitions in the DTT section have to be unique within an SCD file.
IEC 61850-6 defines a number of roles for tools. In the Relion® series, PCM600 is defined as the
IED tool, and IET600 is defined as the system engineering tool.
The sections in SCL contain properties that are to be configured by these tools. There is no
relation between one section and one specific tool. The task of the IED tool is to configure all
properties for the IED, while the system tool has the task to define the place of the IED in the
system and its communication dependencies. For example, the plant structure in PCM600
results in the subsystem section in SCL regarding the subsystem structure down to the IED
level. PCM600 also configures the IED section as a result of the IED configuration. In PCM600,
the configuration properties for SCL are handled automatically as a result of the configuration,
except for the receiving of GOOSE information that has a dependency with the system tool.
The IEC 61850 Configuration tool in PCM600 does not include functionality
for defining the substation part.
IET600
• Open a SCD file or import/merge a SCD, ICD or CID file for the particular IED(s).
• For each IED, the user defines the datasets, the control blocks for reporting (this means
unbuffered/buffered reporting and GOOSE) and the properties for each report control
block.
19
Communication Protocol Manual
Section 3 1MRK 511 269-UEN D
Substation Configuration description Language (SCL)
• If client definitions (like client. ICD) are required in the system configuration, they are
merged into IET600 and connected to the unbuffered/buffered report control blocks.
• Logical nodes, which are not related to the conducting equipment, must be included in the
bay level in the substation section.
• The resulting SCD file is exported from IET600.
PCM600
Define the inputs for the client in IET600 and cross-reference the signals in SMT. Import the
SCD file to PCM600 to receive GOOSE data. For each IED that shall receive GOOSE information,
the received data is connected to the applications using SMT in PCM600.
If input signals are not defined for clients in IET600, they will not be visible in
SMT.
• Top-down approach means that the system engineering tool has ICD files available for
each IED to be included in the system configuration. The ICD files may be of the template
type and represent a pre-configured IED.
• Bottom-up approach means that the configurations are produced by the IED tool, and are
exported as CID files (or SCD file) to be imported into the system tools.
Client A Client B
System
tool
IEC09000151-1-en.vsd
D0E805T201305151541 V1 EN-US
20
Communication Protocol Manual
1MRK 511 269-UEN D Section 3
Substation Configuration description Language (SCL)
Regardless of the engineering approach, the idea is that the IED tool provides the CID or ICD
file for each IED. These ICD/CID files are then imported into the system tool and merged into a
SCD file, representing the complete substation or a part of the substation, like one for each
voltage level.
21
Communication Protocol Manual
22
1MRK 511 269-UEN D Section 4
Communication profile
The IEC 61850 standard describes its requested services in ACSI, which is contained in part 7-2
of the standard. The mapping to the MMS for all aspects of services and Ethernet usage is
specified in part 8-1 of IEC 61850.
Each device manufacturer, which is a partner of an IEC 61850 based communication network,
has to take these two specifications and adapt their respective product to the requirements
and definitions given in the standard. To make this profile visible to all other partners, so they
can check what they can expect and what they have to support, the PICS document is defined.
The PICS contains in a table based form the capabilities of a product or product family.
IED (client)
(61850 services; part 7-2)
AP
Subnetwork
Communication Communication
(MMS services; part 8-1) (MMS services; part 8-1)
IEC08000179.vsd
D0E803T201305151541 V1 EN-US
23
Communication Protocol Manual
Section 4 1MRK 511 269-UEN D
Communication profile
Generic
Object Generic
Sampled Core Substation
Oriented
Values Time ACSI Status
Substation
(Multicast) Sync Services Event
Event
TimeSync
SV GOOSE (SNTP) MMS Protocol Suite GSSE
IEC09000153-1-en.vsd
D0E808T201305151541 V1 EN-US
• GOOSE
• TimeSync using SNTP
• The peer-to-peer/vertical communication using MMS protocol suite with the T-profile
TCP/IP
• Sampled values according to IEC61850-9-2 (LE)
For each of the above, the resulting underlying protocols as stated in Figure 6.
24
Communication Protocol Manual
1MRK 511 269-UEN D Section 5
Supported services
IEC 61850-7-2 describes the services in the standard. IEC 61850-8-1 describes how the services
are applied in the communication. The conformance documents contain the description of the
supported services in the IED.
Services that are not mentioned in this chapter or in the conformance document are not
supported by the IED.
Data set
Define data sets by the SCD description.
The maximum number of data sets (DS) in an IED is 100. The maximum number
of data objects (DO) in a data set for MMS is 100. The maximum data attributes
(DA) in a data set for GOOSE is 150.
Substitution
Substitution is supported for the respective DATA, according to IEC 61850-7-4, that have the
substitution attributes defined.
There is only one setting group control block, which is located in LD0/LLN0 (Logical Device/
Logical Node 0).
Change or edit of setting values as well as reading of setting values is neither supported nor
visible in IEC 61850.
Note that the actual number of used setting groups is defined by the
parameter MaxNoSetGRP in the function SETGRPS, which is configured in PST
in PCM600. PWC600 1.0 supports only a single setting group.
Note that the parameters BufTm and IntPrd shall have the relation BufTm <
IntPrd. For best efficiency, the BufTm should have IntPrd as common
denominator, for example: n*BufTm = IntPrd, n is an arbitrary number.
25
Communication Protocol Manual
Section 5 1MRK 511 269-UEN D
Supported services
The supported data types to be published and received over GOOSE are binary values, double
point values, integer values and measured values, together with their quality. One signal is
available inside the application to validate the reception of a GOOSE message. Invalid means
that the correct message is not received within the 1.8*maxTime parameter for the GOOSE
Control Block (as defined in IEC 61850-6). An incorrect message includes T=true, NeedsCom,
wrong order of attributes or any discrepancy in the GOOSE message layout.
Note that the data sets that are used or referred to by GOOSE control blocks
can only include a data attribute once. In other words, there may not be the
same data attribute in more than one data set.
When publishing a measured value, the user must take care of which measured value data
attributes are added to a data set. If the measured value is event-handled (like in the case of
MMXU functions), then one can add that value directly to the data set. If the value is not event-
handled, (like in the case of Synchrocheck function), it is recommended to connect the value
desired to be published to a MVGGIO function block (in ACT) and then use the measured value
given by the MVGGIO.
Example of functions that have event-handled measured values (can be added directly to the
data set).
• CVMMXN - Measurements
• CMMXU - Phase current measurement
• VMMXU - Phase-phase voltage measurement
• CMSQI - Current sequence component measurement
• VMSQI - Voltage sequence measurement
• VNMMXU - Phase-neutral voltage measurement
Generic function blocks are provided to make available to the 61850 bus signals that are not
defined inside any of the available function blocks. Example of such functions include:
Sampled values
The IEC 61850-9-2 process bus communication protocol enables an IED to receive streams of
measured values of primary voltage and current in digital format. These sampled values are
broadcast by devices known as merging units (MUs).
Each sampled values' stream has a unique identification (SvID) and contains the data from four
voltage measuring points and four current measuring points. Switchsync PWC600 can receive
sampled values' streams from up to four logical MUs, that is, up to 32 measuring points.
26
Communication Protocol Manual
1MRK 511 269-UEN D Section 6
Data sets and control blocks
IEC 61850 has defined data sets and report control blocks to transmit signals for monitoring
purposes. Data sets are also used for GOOSE messages in horizontal communication among
IEDs. The project defines the data objects or single data attributes that should be collected in
a data set. The following figure shows a data set where all position information of the
apparatuses of a bay are put into one data set.
The vendor of an IED can define data sets as defaults that are part of the IED and always
available.
LD0
DATA-SET
LLN0 LD0/LLN0.StatUrg
LD0/ACBMSCBR3.Mechhealth FC=ST
ACBMSCBR2 Mechhealth
ACBMSCBR3 Mechhealth
stVal
t
D0E792T201305151541 V1 EN-US
• All data objects or their data attributes can be selected for a data set.
• Only those data attributes of a data object can/will be selected which have the same
function constraint (FC).
• Data objects with different FC can be selected for a data set. For example, DOs with FC =
ST and DOs with FC=MX can be member in one data set.
• A single data attribute can be selected when it is specified with a trigger option. For
example, the data attribute stVal of the data object Pos can be selected as a member of a
data set, because it is specified with the trigger option data change detected (dchg).
The description of the data sets with name and the list of data object members (FCDAs) is
included in the SCL file in the IED section in the Logical device subsection. As specified in IEC
61850-7-2 clause 9, the data sets are part of a logical node. They are most likely included in the
LLN0.
To be able to transmit the signals configured in a DataSet, a report control block must be
configured to handle and specify how the events are transmitted to the clients. There are two
types of report control blocks; unbuffered and buffered. The buffered report control block
27
Communication Protocol Manual
Section 6 1MRK 511 269-UEN D
Data sets and control blocks
stores the events during a communication interrupt, while the unbuffered is sent upon data
change and not stored during interruption.
The content of a BRCB is listed in IEC 61850-7-2 in clause 14. The BRCB contains many
attributes which are of interest to handle and secure the communication between the client
and the server and may be set once as default in a project. Others are of application interest in
the way events are handled in a project.
Trigger Options
IEC 61850 has defined in total five different TrgOp. Three of them belonging to data attributes
and marked per data attribute in the column TrgOp of the CDC tables in part 7–3. The other
two belonging to the configuration of control blocks.
• dchg = data-change
• Whenever a process value has changed its value either binary or a measurement a
transmission is done.
• qchg = quality change
• Looking to the possibilities of the quality data attribute type (q), any changes in the
quality description will be transmitted.
• dupd = data value update
28
Communication Protocol Manual
1MRK 511 269-UEN D Section 6
Data sets and control blocks
• This trigger option give the possibility to define that a transmission should be done
on a condition which can be controlled by the application.
• integrity
• This trigger forces the transmission of all process values defined in the data set
when a timer value (the integrity period) expires.
• general interrogation
• This trigger is forced by the clients (= station level IED; NCC gateway, station
HMI, ...). Normally a GI is asked for, when the client and the server start or restart a
session. When the client is able to receive the actual values and when the logical
device has scanned all process values at least once, an image of the actual process
signal status can be transmitted to the client.
Note that the possible trigger options for each attribute are included
and defined in the datatype template section in SCL.
The selected client IED with the corresponding LN, for example, ITCI is included in the SCL
structure of the Report Control description of the IED section.
The description of the BRCB with selected DataSet, configured parameters and selected IEDs
is included in the SCL file in the IED section in the LN0 structure for the LD where this LN0
belongs to.
Subnetwork
Server 1 LLN0
DATA-SET
LD0/LLN0.StatUrg
IED 1
LD0/ACBMSCBR1.Mechhealth FC=ST
LD0/ACBMSCBR2.Mechhealth FC=ST
LD0/ACBMSCBR3.Mechhealth FC=ST
D0E776T201305151541 V2 EN-US
29
Communication Protocol Manual
Section 6 1MRK 511 269-UEN D
Data sets and control blocks
The Generic Object Oriented Substation Event (GOOSE) class model is used to distribute input
and output data values between IEDs on bay level (in horizontal direction) through the use of
multicast services. GOOSE messages enable fast transmission from a publisher to one or
several subscribers (receivers).
The GOOSE service model of IEC 61850-7-2 provides the possibility for fast and reliable
system-wide distribution of input and output data values. This implementation uses a specific
scheme of re-transmission to achieve the appropriate level of reliability. When a GOOSE server
generates a SendGOOSEMessage request, the current data set values are encoded in a GOOSE
message and transmitted on the multicast association. The event that causes the server to
invoke a SendGOOSE service is a local application issue as defined in IEC 61850-7-2. Each
update may generate a message in order to minimize throughput time.
Additional reliability is achieved by re-transmitting the same data (with gradually increasing
SqNum and retransmission time).
Time of transmission
T0 (T0) T1 T1 T2 T3 T0
event
IEC09000152-1-en.vsd
D0E817T201305151541 V1 EN-US
The GOOSE message concept is used for all application functions where two or more IEDs are
involved. Typical example is the station-wide interlocking procedure or breaker failure
protection.
Figure 10 shows the GOOSE concept for three IEDs which interchange GOOSE messages
between each other.
30
Communication Protocol Manual
1MRK 511 269-UEN D Section 6
Data sets and control blocks
Receive
Receive
Receive
Receive
Receive
Receive
Send
Send
Send
Data-set Data-set Data-set
LN LN LN
LN LN
LN
LN LN LN
LN
LN LN LN LN LN
Subnetwork
Comm. Comm.
GSE GSE
Server Server
LD0 LD0
GoCB
GoCB
GoCB Input
Input
Input GoCB
GoCB
GoCB Input
Input
Input
DataSet
DataSet
DataSet DataSet
DataSet
DataSet
LN0 LN0
en06000109.vsd
D0E795T201305151541 V1 EN-US
A GOOSE message is forced to be transmitted when a trigger change is detected for a data
attribute. All members of the data set are copied in the send buffer with their actual value and
the message is sent. The subscribers, who know the address of this GOOSE message, receive
the telegram. The GOOSE message includes a sequence number to verify that all messages are
received.
31
Communication Protocol Manual
32
1MRK 511 269-UEN D Section 7
Logical node data model
The data model used by IEC 61850 is based on logical nodes containing a set of data objects.
The data model is defined in the standards.
The standard describes only classes of logical nodes and data objects on one side and
common data classes for the data object attributes. The elements in these classes are defined
as:
• Mandatory (M)
• Optional (O)
• Conditional optional (Cxxx)
• In addition, IEC 61850 states rules for adding vendor-specific definitions to the standard,
in order to cope with extra functionality.
The possible description of the data model according to the standard allows to adapt a logical
node of a LN class to that what the product is supporting or using for this LN. This definition
of what parts of a class is used in the actual product and possible addition is called a type,
according to IEC 61850-6. There are LN types based upon LN classes. The LN type attributes
are called Data Objects (or DATA) and are selected from DO types, based upon respective CDC.
This allows all partners in the IEC 61850 project who need this LN to understand the LN in all
details for the communication part.
The IEC 61850 standard does not describe the functionality and way of operation. Each
supplier has to describe this separately. ABB has described the function blocks that represent
a logical node and all other function blocks in the technical manuals. This chapter in the
communication protocol manual has two purposes:
• Describe the Logical Node types and their data object attribute types.
• Make the link to the description of the function block.
The IEC 61850 standard describes in part 7-4, a Common Logical Node. It contains both
mandatory and optional data objects. The mandatory data objects have to be included in each
LN. This clause describes the general handling of the data objects within the IED.
The mandatory data objects as defined in IEC 61850-7-4 as part of the Common Logical Node
are Mode, Behavior, Health and NamePlate.
Mode (Mod)
The operation modes ON (enabled) and BLOCKED are supported remotely by a command or
locally from the LHMI of the IED. The TEST and the TEST/BLOCKED mode can be operated
locally from the LHMI or by using PCM600.
33
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
The state OFF can be set from the LHMI or by using PCM600 for the functions having the
setting operation.
Note also that for functions in other Logical devices than LD0, Mod can only be controlled by
communication on LLN0.
Behaviour (Beh)
The operational mode as given by the Mode control is shown in the data object Beh with the
priority rules as described for Beh in clause 6 of IEC 61850-7-4.
The Beh shows the actual state of the function, dependent upon the hierarchy described in IEC
61850-7-4, clause 6.
Health
The name of the logical node and its relation to namespace definition are shown in the data
object NamPlt as specified for the SCL structure.
Health and NamPlt data objects are not shown in the Logical node data tables.
34
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
35
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
36
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
37
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
38
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E559T201305151541 v1
39
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
D0E527T201305151541 v1
40
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E710T201305151541 v1
41
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
42
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E716T201305151541 v1
43
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
44
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
45
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
D0E698T201305151541 v1
46
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E699T201305151541 v1
47
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
D0E617T201305151541 v1
48
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E722T201305151541 v1
49
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
50
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E711T201305151541 v1
51
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
D0E717T201305151541 v1
52
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
53
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
54
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
55
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
D0E620T201305151541 v1
56
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E629T201305151541 v1
57
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
58
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E631T201305151541 v1
59
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
60
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E624T201305151541 v1
61
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
62
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
D0E630T201305151541 v1
63
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
64
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
65
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
66
Communication Protocol Manual
1MRK 511 269-UEN D Section 7
Logical node data model
67
Communication Protocol Manual
Section 7 1MRK 511 269-UEN D
Logical node data model
68
Communication Protocol Manual
1MRK 511 269-UEN D Section 8
IEC 61850 communication engineering
The IED function blocks have a design based on the demands and advantages of the IEC 61850
standard. This means that there is a strict relation between the function blocks and the logical
node types. This relation is automatically handled by the PCM600 tools.
See Figure 11 for a principle view of the IEC 61850 logical node concept in the IED.
FBs
FBs
GOOSE interf.
GOOSE GOOSE
GOOSE
Receive Receive
LN Receive
LN
GOOSE
GOOSE
Send GOOSE
Send Send
FB
FBs application
with function
monitoring
Communication handler
Command / IN / OUT interface AF part
only LN
FB
application
function
FBs
LN
with Event
part
monitoring
handler
and
commands
FB
application
function Event
queue
LN
part
IEC08000364-2-en.vsd
IEC08000364 V2 EN-US
69
Communication Protocol Manual
Section 8 1MRK 511 269-UEN D
IEC 61850 communication engineering
Receive
Receive
Receive
Receive
Receive
Receive
Send
Send
Send
Data-set Data-set Data-set
LN LN LN
LN LN
LN
LN LN LN
LN
LN LN LN LN LN
The IEC 61850 standard defines SCL-file types in the sequence of engineering. These files have
a different definition, which is explained in IEC 61850–6. Three of these file types are used in
the engineering process for an IED.
To engineer the IEC 61850 protocol interface for the IED, the following additional manuals or
knowledge of their contents is required.
• Knowledge of the IEC 61850 engineering process as described in the IEC 61850 standard.
• The IEC 61850 conformance documents for the IED to be engineered.
70
Communication Protocol Manual
1MRK 511 269-UEN D Section 8
IEC 61850 communication engineering
The IEC 61850 standard defines the complete part needed for information communication in a
substation. This can be split into the following parts:
For more details please refer to the IEC 61850 standards. In the following description it is
assumed that PCM600 together with Integrated Engineering Tool (IET600) is used as system
configuration tool.
A short form of a typical sequence is shown in Figure 13 when a complete station is exported
as a SCD file.
1. Export SCL files from PCM600. In the scenario in Figure 13 it is a SCD file. Other SCL file
types are possible to export.
2. Configure horizontal and vertical communication in the IET600 station configuration tool.
3. Import SCL files to PCM600 project. In the scenario in Figure 13 it is the updated SCD file.
IET600 2
create project
import SCD file
SCD file configure data sets SCD file
configure Report CBs
configure GOOSE CBs
export SCD file
PCM600 1 PCM600 3
IEC11000264-3-en.vsdx
IEC11000264 V3 EN-US
The pre-condition for exporting SCL files from PCM600 is that all IEDs included in the project
are configured. The hardware interface, for example the IP address, must be selected and
configured. Station communication has to be activated in the IED, that is, the IEC 61850-8-1
setting Operation must be set to On.
71
Communication Protocol Manual
Section 8 1MRK 511 269-UEN D
IEC 61850 communication engineering
IEC08000415 V3 EN-US
IEC09000627-2-en.vsd
IEC09000627 V2 EN-US
Procedure for selecting the export type when an IED is selected in the plant structure:
72
Communication Protocol Manual
1MRK 511 269-UEN D Section 8
IEC 61850 communication engineering
1. Right-click on the IED in the plant structure and select Export to open the Export window.
2. Select the type of file to export from the Save as type drop down list (see Figure 16):
• Configured IED Description (*.cid) for the IEC 61850 structure as needed for the IED
at runtime.
• IED Capability Description (*.icd) for the IEC 61850 structure.
IEC08000416-3-en.vsdx
IEC08000416 V3 EN-US
IEC08000418-2-en.vsd
IEC08000418 V2 EN-US
If only GOOSE communication between ABB IEDs will be used in a project, this can be
engineered directly in PCM600. This requires that the essential configuration of all involved
IEDs is completed, in particular the function blocks for GOOSE communication.
IEC 61850 configuration engineering mode must be enabled in order to use this functionality.
However, the choice of doing the communication engineering within PCM600 will restrict
further SCD file imports from IEC 61850 system configuration tools.
73
Communication Protocol Manual
Section 8 1MRK 511 269-UEN D
IEC 61850 communication engineering
1. In the plant structure, select the substation, voltage level, or bay, within which all involved
IEDs are located.
2. Invoke the IEC 61850 Configuration tool, either from the context menu (right-click on the
selected element) or from the main menu under Tools.
3. In the dropdown selector on the toolbar, select engineering mode GOOSE
Communication.
4. Click GOOSE Controls tab to display the possible communication paths. These are
determined by the functions configured in the IEDs. Potential publishers including
available data types are shown on the left of the matrix and potential subscribers on the
top, where each IED is identified by its Technical Key. See Figure 18.
IEC19000267 V1 EN-US
74
Communication Protocol Manual
1MRK 511 269-UEN D Section 8
IEC 61850 communication engineering
IEC19000266 V1 EN-US
IEC19000265 V1 EN-US
75
Communication Protocol Manual
Section 8 1MRK 511 269-UEN D
IEC 61850 communication engineering
IEC19000269 V1 EN-US
Figure 21: Mapping received GOOSE controls to function blocks in the IED
5. Click Save button to save the signal mapping.
6. Close Signal Matrix tool.
7. Write the entire configuration to the IED, see section Writing IEC 61850 communication
configuration to an IED.
For IEC 61850 engineering, a separate system configuration tool may be needed with PCM600
(for example, when using other than ABB IEDs).
76
Communication Protocol Manual
1MRK 511 269-UEN D Section 8
IEC 61850 communication engineering
All data sets, report control blocks and GOOSE control blocks must be
located at LD0/LLN0. There are limitations regarding the maximum
number of data sets, number of entries in a data set and the number of
report control blocks that can be used.
3. Add and/or reconfigure data sets. The configured IED includes a number of predefined
data sets, but it is possible to add additional data sets and/or reconfigure default data
sets according to the requirements.
4. Configure report control blocks for each data set used in vertical communication. Pre-
configured IEDs include predefined report control blocks which can be reconfigured. If
additional control blocks are needed, it is possible to add them according to
requirements.
The vertical client must belong to the same sub-network as the IEDs.
Please see the IET600 user manual for additional information about vertical
and horizontal station communication engineering.
All data sets, report control blocks and GOOSE control blocks must be
located at LD0/LLN0. There are limitations regarding the maximum
number of data sets, number of entries in a data set and the number of
report control blocks that can be used.
3. Create a GOOSE data set for the sending IED. Define the content of the data set according
to the requirements.
The data set for GOOSE contains signals on the data attribute or FCDA
levels. The latter is also known as structured GOOSE.
77
Communication Protocol Manual
Section 8 1MRK 511 269-UEN D
IEC 61850 communication engineering
Data for one signal can only be included in one GOOSE data set. The data
set for GOOSE cannot be empty.
4. Create a GOOSE control block and connect it to the GOOSE data set. Check parameters
for GOOSE control block, for eaxample MinTime and MaxTime, and update as required.
5. Connect the GOOSE control block to receiving IEDs that subscribe GOOSE data.
6. Export the SCD file.
IEC09000631 V3 EN-US
4.1. Select Ignore Substation Section to ignore the sub-station section in the SCD file
during import.
4.2. Select Don't import IEDs ... to disable the import of unknown IED types (for example
third-party IEDs).
4.3. Select Replace unknown ... to replace unknown IED types with IED type “Generic IEC
61850 IED”. Use this option if you need to import third-party IEDs into PCM600.
4.4. Select Ignore PCM Object Type if the IED type is modified outside PCM600.
4.5. Click Import.
5. Configure how to receive data from sending IEDs:
5.1. In SMT, configure connections between signals the server is sending and the GOOSE
receive function blocks.
78
Communication Protocol Manual
1MRK 511 269-UEN D Section 8
IEC 61850 communication engineering
IEC09000631 V3 EN-US
79
Communication Protocol Manual
Section 8 1MRK 511 269-UEN D
IEC 61850 communication engineering
After changing any aspect of IEC 61850 communication the updated configuration needs to be
written to the IED. This is done through a full Write to IED... from the context menu or the
Tools menu.
During the write process, the user is asked to update the communication configuration:
IEC09000729-2-en.vsd
IEC09000729 V2 EN-US
80
Communication Protocol Manual
1MRK 511 269-UEN D Section 9
Glossary
Section 9 Glossary
D0E688T201305141612 v5
Names of function blocks, IEC 61850 logical nodes, data objects, data
attributes etc. are not listed here. Refer to the respective section of this
document or to the relevant part of the standard.
AC Alternating current
ACT Application configuration tool within PCM600
ACSI Abstract communication service interface, as defined in IEC 61850-7-2
A/D converter Analog-to-digital converter
AI Analog input
ANSI American National Standards Institute
AP Access point for digital communication
AR Autoreclosing
AWG American Wire Gauge standard
BI Binary input
BIO Binary input/output module
BO Binary output
BRCB Buffered report control block
BS British Standards
CAN Controller Area Network. ISO standard (ISO 11898) for serial
communication
CB Circuit breaker
CCITT Consultative Committee for International Telegraph and Telephony. A
United Nations-sponsored standards body within the International
Telecommunications Union.
CCVT Capacitive Coupled Voltage Transformer
CDC Common data class
CID Configured IED description file as per IEC 61850-6
Class C Protection Current Transformer class as per IEEE/ ANSI
CMT Communication Management tool in PCM600
CO cycle Close-open cycle
COM Communication module
COMTRADE Standard format according to IEC 60255-24
CPU Central processing unit
CRC Cyclic redundancy check
CSV Comma-separated values
CT Current transformer
CVT Capacitive voltage transformer
81
Communication Protocol Manual
Section 9 1MRK 511 269-UEN D
Glossary
DA Data attribute
DARPA Defense Advanced Research Projects Agency (The US developer of the
TCP/IP protocol etc.)
DC Direct current
DHCP Dynamic Host Configuration Protocol
DI Digital input
DNP Distributed Network Protocol as per IEEE Std 1815-2012
DO Data object
DR Disturbance recorder
DRAM Dynamic random access memory
DSP Digital signal processor
DTT Data type template section in the SCL description file of a station or IED
DVD Digital versatile disc
EHV Extra high voltage
EIA Electronic Industries Association
EMC Electromagnetic compatibility
EMI Electromagnetic interference
EN European standard
ESD Electrostatic discharge
FC Function constraint
GDE Graphical display editor within PCM600
GIS Gas-insulated switchgear
GoCB GOOSE control block
GOOSE Generic object-oriented substation event
GPS Global positioning system
GSAL Generic security application
GSE Generic substation event
HMI Human-machine interface
HSAR High speed autoreclosing
HTTPS Hypertext transfer protocol secure
HV High-voltage
HVDC High-voltage direct current
HW Hardware
ICD IED capability description file as per IEC 61850-6
IEC International Electrical Committee
IEC 60044-6 IEC Standard, Instrument transformers – Part 6: Requirements for
protective current transformers for transient performance
IEC 61850 Substation automation communication standard
IEC 61850-8-1 Communication protocol standard for station bus
IEC 61850-9-2(LE) Communication protocol standard for sampled values
IEEE Institute of Electrical and Electronics Engineers
82
Communication Protocol Manual
1MRK 511 269-UEN D Section 9
Glossary
IEEE 802.12 A network technology standard that provides 100 Mbits/s on twisted-pair
or optical fiber cable
IEEE 1686 Standard for Substation Intelligent Electronic Devices (IEDs) Cyber
Security Capabilities
IED Intelligent electronic device
Instance When several occurrences of the same function are available in the IED,
they are referred to as instances of that function. One instance of a
function is identical to another of the same kind but has a different
number in the IED user interfaces. The word "instance" is sometimes
defined as an item of information that is representative of a type. In the
same way an instance of a function in the IED is representative of a type of
function.
IP 1. Internet protocol. The network layer for the TCP/IP protocol suite widely
used on Ethernet networks. IP is a connectionless, best-effort packet-
switching protocol. It provides packet routing, fragmentation and
reassembly through the data link layer.
2. Ingression protection, according to IEC standard
IP 20 Ingression protection, according to IEC standard, level 20
IP 40 Ingression protection, according to IEC standard, level 40
IP 54 Ingression protection, according to IEC standard, level 54
IRF Internal failure signal
IRIG-B InterRange Instrumentation Group Time code format B, standard 200
ITU International Telecommunications Union
LAN Local area network
LCD Liquid crystal display
LD Logical device in IEC 61850
LED Light-emitting diode
LHMI Local human-machine interface
LN Logical node in IEC 61850
MCB Miniature circuit breaker
MICS Model implementation conformance statement, for IEC 61850
MMS Manufacturing Message Specification
MU Merging unit
MVB Multifunction vehicle bus. Standardized serial bus originally developed for
use in trains.
NC Normally closed auxiliary contact
NCC National Control Centre
NCIT Non-conventional instrument transformer
NO Normally open auxiliary contact
OCO cycle Open-close-open cycle
PC Personal computer
PCM Pulse code modulation
PCM600 Protection and control IED manager
PICS Protocol implementation conformance statement, for IEC 61850
PIO Precision input/output module
83
Communication Protocol Manual
Section 9 1MRK 511 269-UEN D
Glossary
PIXIT Protocol implementation extra information for testing, for IEC 61850
PoW Point on wave
PPS, 1PPS One pulse per second, time synchronization interface
Process bus Bus or LAN used at the process level, that is, in near proximity to the
measured and/or controlled components
PSM Power supply module
PST Parameter setting tool within PCM600
PT ratio Potential transformer or voltage transformer ratio
PWC Point-on-wave controller
RBAC Role-based access control (role-based security)
RISC Reduced instruction set computer
RJ-45 Registered jack 45, commonly used as plug connector for electrical
Ethernet
RMS value Root mean square value
RS422 A balanced serial interface for the transmission of digital data in point-to-
point connections
RS485 Serial link according to EIA standard RS485
RTC Real-time clock
RTU Remote terminal unit
Rx Receive line
SA Substation Automation
SBO Select-before-operate
SCADA Supervision, control and data acquisition
SCD System configuration description file as per IEC 61850-6
SCL System configuration language in IEC 61850
SCS Station control system
SCT System configuration tool according to standard IEC 61850
SMT Signal matrix tool within PCM600
SMS Station monitoring system
SNTP Simple network time protocol – is used to synchronize computer clocks on
local area networks. This reduces the requirement to have accurate
hardware clocks in every embedded system in a network. Each embedded
node can instead synchronize with a remote clock, providing the required
accuracy.
SPO Single-pole operated (circuit breaker), i.e. one drive for each pole.
SST Switchsync Setting Tool within PCM600
Starpoint Neutral point of transformer or generator
SVC Static VAr compensation
SW Software
TC Trip coil
TCS Trip circuit supervision
TCP Transmission control protocol. The most common transport layer protocol
used on Ethernet and the Internet.
84
Communication Protocol Manual
1MRK 511 269-UEN D Section 9
Glossary
85
Communication Protocol Manual
86
87
ABB AB
Substation Automation Products
SE-721 59 Västerås, Sweden
Phone +46 (0) 21 32 50 00
Scan this QR code to visit our website
www.abb.com/substationautomation
1MRK 511 269-UEN