communication protocol manual - abb group · 2019-03-11 · relion®670 series iec 61850 edition 1,...

— RELION® 670 SERIES

IEC 61850 Edition 1, 670 series Version 2.1 Communication protocol manual

Document ID: 1MRK 511 349-UEN Issued: March 2019

Revision: AProduct version: 2.1

© Copyright 2016 ABB. All rights reserved

This product includes software developed by the OpenSSL Project for use in the OpenSSLToolkit. (http://www.openssl.org/) This product includes cryptographic software written/developed by: Eric Young ([email protected]) and Tim Hudson ([email protected]).

Trademarks

ABB and Relion are registered trademarks of the ABB Group. All other brand or product namesmentioned in this document may be trademarks or registered trademarks of their respectiveholders.

Disclaimer

This document has been carefully checked by ABB but deviations cannot be completely ruledout. 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 orliable for any loss or damage resulting from the use of this manual or the application of theequipment.

Conformity

Table of contents

Section 1 Introduction.........................................................................................................51.1 This manual......................................................................................................................................... 51.2 Intended audience............................................................................................................................. 51.3 Product documentation................................................................................................................... 51.3.1 Product documentation set........................................................................................................ 51.3.2 Document revision history...........................................................................................................61.3.3 Related documents....................................................................................................................... 61.4 Document symbols and conventions.............................................................................................61.4.1 Symbols........................................................................................................................................... 61.4.2 Document conventions.................................................................................................................7

Section 2 Introduction to IEC 61850................................................................................. 92.1 Overview.............................................................................................................................................. 92.2 Related documentation to IEC 61850.......................................................................................... 10

Section 3 Substation Configuration description Language (SCL).............................. 113.1 The substation section....................................................................................................................123.2 The communication section...........................................................................................................123.3 The IED section................................................................................................................................. 133.4 Tool concept......................................................................................................................................153.5 Engineering concept in IEC 61850-6.............................................................................................16

Section 4 Communication profile.................................................................................... 17

Section 5 Supported services...........................................................................................19

Section 6 Data sets and control blocks...........................................................................236.1 Data sets............................................................................................................................................236.2 Report control block (URCB/BRCB)..............................................................................................236.3 GOOSE Control Blocks (GoCB)...................................................................................................... 26

Section 7 Logical node data model................................................................................. 297.1 Common data objects in each logical node............................................................................... 297.2 Logical nodes for control............................................................................................................... 307.2.1 Bay control CBAY......................................................................................................................... 307.2.1.1 Bay control QCBAY...................................................................................................................307.2.2 Switch controller CSWI............................................................................................................... 327.2.2.1 Switch controller SCSWI..........................................................................................................327.3 Logical nodes for conversion functions......................................................................................347.3.1 Integer to Boolean converter FCVB......................................................................................... 347.3.1.1 Integer to Boolean 16 conversion with logic node representation ...............................347.3.2 Boolean to integer converter FCVI...........................................................................................357.3.2.1 Boolean to integer conversion with logical node representation, 16 bit BTIGAPC.....35

Table of contents

1Communication protocol manual

7.4 Logical nodes for protection functions...................................................................................... 367.4.1 Protection trip conditioning PTRC...........................................................................................367.4.1.1 Logic for group alarm ALMCALH...........................................................................................367.4.1.2 Logic for group indication INDCALH.................................................................................... 377.4.1.3 Tripping logic common 3-phase output SMPPTRC...........................................................387.4.1.4 Logic for group warning WRNCALH..................................................................................... 397.4.2 Multipurpose analog protection GAPC...................................................................................407.4.2.1 General currrent and voltage protection CVGAPC............................................................ 407.5 System logical nodes...................................................................................................................... 477.5.1 Generic security application component................................................................................477.5.1.1 Generic security application component AGSAL............................................................... 477.5.2 Physical device information LPHD........................................................................................... 497.5.3 Logical node zero LLNO............................................................................................................. 497.5.4 Access point diagnostic for redundant Ethernet ports RCHLCCH................................... 507.5.5 Access point diagnostic for non-redundant Ethernet port SCHLCCH............................. 517.6 Logical nodes for protection related functions.........................................................................527.6.1 Disturbance recorder RDRE....................................................................................................... 527.6.1.1 Disturbance report DRPRDRE................................................................................................ 527.7 Logical nodes for generic references.......................................................................................... 537.7.1 Generic process I/O GGIO..........................................................................................................537.7.1.1 Logic rotating switch for function selection and LHMI presentation SLGAPC........... 537.7.1.2 Selector mini switch VSGAPC................................................................................................ 547.7.1.3 Generic communication function for Double Point indication DPGAPC...................... 567.7.1.4 Single point generic control 8 signals SPC8GAPC.............................................................567.7.1.5 Event counter with limit supervision L4UFCNT.................................................................597.7.1.6 IEC 61850 generic communication I/O functions SPGGIO...............................................617.7.1.7 IEC 61850 generic communication I/O functions 16 inputs SP16GGIO.........................617.7.1.8 Generic communication function for Measured Value MVGAPC.................................... 637.7.1.9 Trip matrix logic TMAGAPC....................................................................................................647.7.1.10 Elapsed time integrator with limit transgression and overflow supervision

TEIGGIO......................................................................................................................................657.8 Logical nodes for sensors and monitoring.................................................................................677.8.1 Circuit breaker monitoring SSCBR...........................................................................................677.8.1.1 SSCBR......................................................................................................................................... 677.8.2 Insulation medium supervision (gas) SIMG............................................................................ 717.8.2.1 SSIMG.......................................................................................................................................... 717.8.3 Insulation medium supervision (liquid) SIML.........................................................................737.8.4 Through fault monitoring STHR............................................................................................... 747.8.4.1 Through fault monitoring PTRSTHR ....................................................................................747.9 Logical nodes for switchgear........................................................................................................ 757.9.1 Circuit breaker XCBR...................................................................................................................757.9.1.1 Circuit breaker SXCBR............................................................................................................. 757.9.2 Switch XSWI.................................................................................................................................. 787.9.2.1 Circuit switch SXSWI................................................................................................................78

Section 8 Flexible product naming.................................................................................. 818.1 Introduction...................................................................................................................................... 81

Table of contents


8.1.1 Mapping example........................................................................................................................ 818.1.2 Mapping possibilities and requirements................................................................................82

Section 9 Glossary............................................................................................................. 85

Table of contents


Section 1 Introduction

1.1 This manualGUID-AB423A30-13C2-46AF-B7FE-A73BB425EB5F v19

1.2 Intended audienceGUID-C9B8127F-5748-4BEA-9E4F-CC762FE28A3A v10

1.3 Product documentation

1.3.1 Product documentation setGUID-3AA69EA6-F1D8-47C6-A8E6-562F29C67172 v15

IEC07000220-4-en.vsd

Plan

ning

& p

urch

ase

Engi

neer

ing

Inst

allin

g

Com

mis

sion

ing

Ope

ratio

n

Mai

nten

ance

Dec

omm

issi

onin

gD

eins

tallin

g &

disp

osal

Application manual

Operation manual

Installation manual

Engineering manual

Communication protocol manual

Cyber security deployment guideline

Technical manual

Commissioning manual

IEC07000220 V4 EN-US

Figure 1: The intended use of manuals throughout the product lifecycle

The engineering manual contains instructions on how to engineer the IEDs using the varioustools available within the PCM600 software. The manual provides instructions on how to setup a PCM600 project and insert IEDs to the project structure. The manual also recommends asequence for the engineering of protection and control functions, LHMI functions as well ascommunication engineering for IEC 60870-5-103, IEC 61850, DNP3, LON and SPA.

The installation manual contains instructions on how to install the IED. The manual providesprocedures for mechanical and electrical installation. The chapters are organized in thechronological order in which the IED should be installed.

1MRK511349-UEN A Section 1Introduction


The commissioning manual contains instructions on how to commission the IED. The manualcan also be used by system engineers and maintenance personnel for assistance during thetesting phase. The manual provides procedures for the checking of external circuitry andenergizing the IED, parameter setting and configuration as well as verifying settings bysecondary injection. The manual describes the process of testing an IED in a substation whichis not in service. The chapters are organized in the chronological order in which the IED shouldbe commissioned. The relevant procedures may be followed also during the service andmaintenance activities.

The operation manual contains instructions on how to operate the IED once it has beencommissioned. The manual provides instructions for the monitoring, controlling and setting ofthe IED. The manual also describes how to identify disturbances and how to view calculatedand measured power grid data to determine the cause of a fault.

The application manual contains application descriptions and setting guidelines sorted perfunction. The manual can be used to find out when and for what purpose a typical protectionfunction can be used. The manual can also provide assistance for calculating settings.

The technical manual contains operation principle descriptions, and lists function blocks, logicdiagrams, input and output signals, setting parameters and technical data, sorted perfunction. The manual can be used as a technical reference during the engineering phase,installation and commissioning phase, and during normal service.

The communication protocol manual describes the communication protocols supported bythe IED. The manual concentrates on the vendor-specific implementations.

The point list manual describes the outlook and properties of the data points specific to theIED. The manual should be used in conjunction with the corresponding communicationprotocol manual.

The cyber security deployment guideline describes the process for handling cyber securitywhen communicating with the IED. Certification, Authorization with role based access control,and product engineering for cyber security related events are described and sorted byfunction. The guideline can be used as a technical reference during the engineering phase,installation and commissioning phase, and during normal service.

1.3.2 Document revision historyGUID-C8027F8A-D3CB-41C1-B078-F9E59BB73A6C v2.1.1

Document revision/date History

January 2016 First Release

March 2019 Maintenance Release

1.3.3 Related documentsGUID-94E8A5CA-BE1B-45AF-81E7-5A41D34EE112 v4

1.4 Document symbols and conventions

1.4.1 SymbolsGUID-2945B229-DAB0-4F15-8A0E-B9CF0C2C7B15 v12

The electrical warning icon indicates the presence of a hazard which couldresult in electrical shock.

Section 1 1MRK511349-UEN AIntroduction


The warning icon indicates the presence of a hazard which could result inpersonal injury.

The caution hot surface icon indicates important information or warning aboutthe temperature of product surfaces.

The caution icon indicates important information or warning related to theconcept discussed in the text. It might indicate the presence of a hazard whichcould result in corruption of software or damage to equipment or property.

The information icon alerts the reader of important facts and conditions.

The tip icon indicates advice on, for example, how to design your project orhow to use a certain function.

Although warning hazards are related to personal injury, it is necessary to understand thatunder certain operational conditions, operation of damaged equipment may result indegraded process performance leading to personal injury or death. It is important that theuser fully complies with all warning and cautionary notices.

1.4.2 Document conventionsGUID-96DFAB1A-98FE-4B26-8E90-F7CEB14B1AB6 v8

• Abbreviations and acronyms in this manual are spelled out in the glossary. The glossaryalso contains definitions of important terms.

• Parameter names are shown in italics.For example, the function can be enabled and disabled with the Operation setting.

• Each function block symbol shows the available input/output signal.

• the character ^ in front of an input/output signal name indicates that the signalname may be customized using the PCM600 software.

• the character * after an input signal name indicates that the signal must beconnected to another function block in the application configuration to achieve avalid application configuration.

• Dimensions are provided both in inches and millimeters. If it is not specifically mentionedthen the dimension is in millimeters.

1MRK511349-UEN A Section 1Introduction


Section 2 Introduction to IEC 61850

2.1 OverviewGUID-66925336-B6C3-4B22-95F4-A3321B63FABB v7

The general scope of the IEC 61850 protocol standard is designed to support thecommunication of all functions being performed in the substation. Its’ main goal isinteroperability; this is the ability for IEDs from one or different manufacturers to exchangeinformation and use the information for their own functions. Moreover, the standard allows afree allocation of these functions and accepts any system philosophy, from a distributedarchitecture (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 relatedcommunication services from the communication implementation (stack).

The data model of the standard is an object-oriented one, grouping the data into the smallestpossible sets referring to the smallest possible functions to be implemented independently.These smallest possible data groups or functions are named logical nodes. The logical nodesand all data and attributes contained are named according to a standardised semantic, whichis mandatory.

This manual describes how the IEC 61850 standard is applied in the IEDs. References and briefdescriptions of the standard are also included. It is assumed that the reader has basicknowledge of the IEC 61850 standard.

The following parts of the IEC 61850 standard are of importance as they relate to this manual:

• Station Configuration description Language (SCL) is described in IEC 61850-6. The SCL isan XML based definition of how to describe the parts of a substation. This part of thestandard 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 thestandard includes a number of possible communication profiles, and how the servicesdefined 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 thecommunication facilities from client and server point of view. It includes the differentpossibilities 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 IEC 61850 implementation of the IED is described insidethe conformance documents.

• MICS, Modeling Information Conformance Statement, contains the declaration of theused logical node types.

• PICS, Protocol Information Conformance Statement, contains the details and what issupported regarding protocol facilities.

• PIXIT, Protocol Extra Information, contains additional information on how the IEC 61850 isimplemented and used.

• TICS, Tissue Information Conformance Statement, contains the supported Tissues, whichare handled in the Tissues process as defined by UCA, Utility Communication Architectureforum. The Tissues handling is found in http://www.tissue.iec61850.com.

1MRK511349-UEN A Section 2Introduction to IEC 61850


The conformance documents are unique for each product release and refer to each other. Theidentities included in the related documents refer to a specific version of the IED series.

The communication profile in IEC 61850 uses the MMS standard, which uses Ethernet andTCP/IP to handle the information transport within the substation.

The data modelling uses the concept of logical nodes to identify the published information forcommunication. The standard defines a set of logical nodes, each representing acommunication view of a process function with a number of data objects. For example, atransformer differential - or line differential protection, because the standard defines only adifferential protection. Therefore, it is possible to adapt the logical node, which is defined inthe standard, as a logical node class. The standard defines methods to describe the actuallyused logical node as a logical node type which is then based upon the logical node class. Thisallows all partners to interpret the logical node type information because the description iscompletely given in the standard. The type description of all logical nodes is part of the DataType 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 manualcontains the full description of all logical nodes available in the IEDs. The information aboutthe logical nodes and their data objects may be used to identify which signals are available forthe functions as described in the technical manual. The link to the technical manual is done inthe logical node tables by listing the signal name as given in the function block, or as seen inPCM600 or the LHMI.

2.2 Related documentation to IEC 61850GUID-906D4C7F-29FD-4922-8A8B-8A3A3E2B811E v5

Use the latest revision of the documents listed, unless stated otherwise.

Section 2 1MRK511349-UEN AIntroduction to IEC 61850


Section 3 Substation Configurationdescription Language (SCL)

SEMOD129808-4 v8

Four different types of SCL files - SCD, CID, IID, and ICD, can be exported from PCM 600.

The SCL language is based on XML. However, detailed knowledge of the XML contents is notneeded.

The SCL XML file (ICD/SCD/CID/IID) contains five sections, which are specified in IEC 61850–6clause 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, DO types, attributes and enums.

The system structure is defined by the organization of the plant structure in PCM600. Thesignal engineering and the signal routing are IET600 tasks, signal engineering regarding DS,rcb,gcb, GOOSE subscribers can be done also in PCM600. The IED needs to be configured withPCM600 before the system is configured with IET600.

The SCL engineering must be done in an SCL engineering tool. The data sets and the controlblocks are logically defined as part of the logical nodes (see IEC 61850–7–2 clause 9). The IEDalso needs a correctly configured communication section for GOOSE engineering, which canbe done in IET600 or PCM600.

The data type templates section provides the correct content description of each logical nodetype to all tools and users (clients) of the information. Each IED and vendor may have their ownlogical node type definitions included in the data type template section together with all otherlogical node types based on the standard.

1MRK511349-UEN A Section 3Substation Configuration description Language (SCL)


IEC08000178.vsd

IED Name AccessPoint Address GSEIED Name AccessPoint Address GSE

Services

AuthenticationLDevice

DAI

DOType

DAType

EnumType

SubstationVoltageLevel

BayLNode

IED LD LNIED LD LN

CommunucationSubnetwork

Connected AP

IEDAccessPoint

Server

GOOSE Control

LN0 LNDataSet DOI

DataTypeTemplates

Report Control

Inputs

DOI

SettingControl

LNodeType

DOType

DAType

EnumType

DO

DA

IED

SDO

BDAStation

Com

mun


Figure 2: IEC 61850: Principle structure of the SCL XML file

The arrows show the link between the different sections given when an IED is integrated in thesubstation structure and/or in the communication structure. All needed logical nodes of anIED are linked to the substation section by the SCL tool.

A reference to GOOSE Control Blocks (GoCB) is included in the communication section whenGoCB is configured.

3.1 The substation sectionSEMOD129763-4 v4

3.2 The communication sectionSEMOD129771-4 v3

The organization of the physical IEDs to the communication network is independent of thesubstation structure. The IEC 61850 standard defines the communication network with norelation to an existing media or protocol. The mapping to an existing media and protocol isspecified in IEC 61850–8–1.

The IEC 61850 standard describes in part 7–2 the ACSI in a media and protocol independentform. Part 8–1 specifies the mapping of this ACSI to the existing MMS.

Section 3 1MRK511349-UEN ASubstation Configuration description Language (SCL)


The communication section describes how information is routed between the IEDs andcontains 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)

en06000101.vsd

IED(server)

- Access Point (AP)- Address- GSE; GoCBs

Communication

AP

IED(server)


Communication

IED(server)


Communication

AP

IED(client)


Communication

IED(client)


Communication

Subnetwork


Figure 3: IEC 61850–6: Communication network

Additional information about the server is part of the IED.

3.3 The IED sectionSEMOD129775-4 v6

The IED section describes the complete IED as it is needed for IEC 61850 communication andsignal engineering. The data type template part of an IED may be seen as part of the IED, evenwhen separated in its own section. The IED's ICD files include the description of the logicalnodes, their data type templates and the used or supported services. The structure of the IEDsection follows the definitions made in the IEC 61850 standard.

Two basic IED types are used in system configuration.

• Station level IEDsare located on the station level and are identified as client IEDs when they read or writeinformation from or to the bay IEDs. This functionality is represented by logical nodes ofgroup “Information (I)”. These are the logical nodes (LN) = ITCI, IHMI and ITMI. Client IEDsare 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 controlblocks (BRCBs) from the server IEDs. They have to read their information about the signalsand the signal configuration from the bay IEDs. This is possible by checking all controlblocks 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 writeinformation vertically. When GOOSE messages are received, the bay level IED also has theclient role.

en06000104.vsd

AP

Subnetwork

Control

IED

CVMMXU1

SB1.LD0

Server

LPHD

SXCBR1

SCSWI1

SXSWI1

SCSWI2

SXSWI2

SCSWI3

SXSWI3

SCSWI4

SXSWI4

SCSWI5

LLN0

Mod

CBOpCap

Origin

Data

DataAttribute

Beh

Health

NamePlt

ctlValPos

Loc

OpCnt

BlkOpn

BlkCls

stVal

q

t

LogicalNode

ctlModel


Figure 4: Organization of LDs, LNs, DOs and DAs in an IED

• A server represents the communication interface to the subnetwork (Ethernet).• One or more logical device(s) (LD) are connected to a server.• A set of logical nodes belong to a LD.• The LN LLN0 is a special logical node per LD and contains for example the data sets, the

various control blocks, inputs (from GOOSE messages). In the IED series, the data setsand the control blocks shall be located to LD0.

• The LN LPHD is a special logical node per LD and contains data objects that describe thestatus of the physical device (the IED)

• Each logical node represents a function and contains a number of data objects (DO)• Each DO includes a number of data attributes (DA)

The data objects represent information signals that may be routed to station level IEDs or toother bay IEDs that are communicating via GOOSE. The signal engineering task is to select therequested signals (DOs) and link them to the client IEDs as receiver. When using a dataset forMMS, the requested signals are DOs but when creating a dataset for GOOSE messaging, DAsare used.



The number of data objects and data attributes per DO is defined by the used LN type in theIED. The content of logical node types and DO types are defined in the DTT. This also meansthat the definitions in the DTT section have to be unique within an SCD file.

3.4 Tool conceptGUID-93477EC1-9BB4-4CCE-8603-0D910BDD661B v6

The IEC 61850-6 defines a number of roles for tools. In the Relion® series, PCM600 is defined asthe 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 norelation between one section and one specific tool. The task of the IED tool is to configure allproperties for the IED, while the system tool has the task to define the place of the IED in thesystem and its communication dependencies. For example, the plant structure in PCM600results in the subsystem section in SCL regarding the subsystem structure down to the IEDlevel. The PCM600 also configures the IED section as a result of the IED configuration. InPCM600, the configuration properties for SCL are handled automatically as a result of theconfiguration, except for the receiving of GOOSE information that has a dependency with thesystem tool.

IEC 61850 engineering with PCM600, PCM600 IEC 61850 Configuration tool and IET600

PCM600:

• When an IED is instantiated, its place in the plant structure creates the correspondingstructure in the substation section in SCL. The communication facilities is also created inthe communication section.

• The functionality of the IED is configured by using ACT in PCM600. For each function, thecorresponding logical device and logical node(s) is created in the IED section togetherwith its type definition in data type template section

• The above forms the IED capabilities from a communication perspective and will then beincluded in the file exported from PCM600 as SCD, ICD, IID and CID file

PCM600: IEC 61850 Configuration tool

• Included in PCM600 is the new IEC 61850 Configuration tool which allows the user todefine data sets and control blocks for both Client Server and GOOSE communication.

• The IEC 61850 Configuration tool gives the user the possibility to make the IEC 61850engineering without export / import step.

It does NOT however allow the User to define 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

unbufffered/buffered reporting and GOOSE) and the properties for each report controlblock.



Data sets (DS) are generated automatically in PCM600. Report controlblocks (RCBs) are not generated automatically in PCM600.

• If client definitions (like client. ICD) are required in the system configuration, they aremerged 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 thebay 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 theSCD 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.To be able to importscd-file to PCM600 61850 engineering in PCM must be set to disabled.

If input signals are not defined for clients in IET600, they will not be visible inSMT. Inputs (GOOSE clients) can also be defined in PCM600.

3.5 Engineering concept in IEC 61850-6GUID-FFE87459-FBC1-4D85-A6B3-7BD6F576ECE4 v3

• Top-down approach means that the system engineering tool has ICD files available foreach IED to be included in the system configuration. The ICD files may be of the templatetype and represent a pre-configured IED.

….IED A IED B IED Z

Client A Client B

IEDtool

Systemtool

IEC09000151-1-en.vsdIEC09000151 V1 EN-US

Figure 5: Relation between system and IED tools



Section 4 Communication profile

GUID-25495333-A2B7-44A7-908D-68EC06694AD5 v6

The IEC 61850 standard is conceptually written to be independent of an existingcommunication media and message transmission concept. Out of this, a specificcommunication profile is decided and has been commonly used. The profile contains:

• Ethernet as the media• TCP/IP• ISO session and presentation layer• MMS (Manufacturing Message Specification (ISO 9506-1 and ISO 9506-2)

The IEC 61850 standard describes its requested services in ACSI, which is contained in part 7-2of the standard. The mapping to the MMS for all aspects of services and Ethernet usage isspecified 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 requirementsand definitions given in the standard. To make this profile visible to all other partners, so theycan 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 possibility of a product or product family.

IED (server)(61850 services; part 7-2)

Communication(MMS services; part 8-1)

- Access Point (AP) / Address- GSE

IEC08000179.vsd

AP

IED (client)(61850 services; part 7-2)

Subnetwork

IED (server)(61850 services part; 7-2)






Figure 6: IEC 61850 Protocol: related standards for communication

1MRK511349-UEN A Section 4Communication profile


SV GOOSE TimeSync(SNTP) MMS Protocol Suite GSSE

TCP/IPT-Profile

ISO COT-Profile

ISO/IEC 8802-2 LLC

GSSET-ProfileUDP/IP

ISO/IEC 8802-3 Ethertype

SampledValues(Multicast)

GenericObjectOrientedSubstationEvent

TimeSync

CoreACSIServices

GenericSubstationStatusEvent

ISO/IEC 8802-3


Figure 7: Overview of functionality and profiles according to IEC 61850-8-1

Out of this content, the implementation supports:

• Sampled values according to 9-2LE• GOOSE• TimeSync using SNTP• The peer-to-peer/vertical communication using MMS protocol suite with the T-profile

TCP/IP

For each of the above, the resulting underlying protocols as stated in Figure 7.

See the PICS and PIXIT for more information.

Section 4 1MRK511349-UEN ACommunication profile


Section 5 Supported services

GUID-E08C91D7-A59B-478B-B39A-26E786591E2A v7

IEC 61850-7-2 describes the services in the standard. IEC 61850-8-1 describes how the servicesare applied in the communication. The conformance documents contain the description of thesupported services in the IED.

Services that are not mentioned in this chapter or in the conformance document are notsupported by the IED.

Data set

Define data sets by the SCD description.

Create data sets under LD0/LLN0.

For more information on data sets, see the PIXIT-related documents.

Substitution

Substitution is supported for the respective DATA, according to IEC 61850-7-4, that have thesubstitution attributes defined.

Setting group control block

There is only one setting group control block, which is located in LD0/LLN0 (Logical Device0/Logical Node 0).

The Setting range is expressed in the minVal and maxVal data attributes (DAs) in each settingdata object (DO). When writing settings a check will be done to compare the new value withthe minVal and maxVal attributes, when applicable (this depends on the data type and if theminVal and maxVal are mapped). So if the minVal and maxVal is not mapped, all values in therange of the data type will be accepted. If the written value is outside the range, Object-Value-Invalid will be returned to the client.

Note that the actual number of used setting groups is defined by theparameter MaxNoSetGRP in the function SETGRPS, which is configured in PSTin PCM600. But six setting groups is the maximum and it cannot be exceeded.

Setting parameter values via IEC 61850 Edition 2

Some parameters values can be set over IEC 61850 Edition 2 communication, provided that theparameter Enable61850Setting has been set to Enabled in Main menu/Configuration/Communication/Station communication/IEC61850–8–1/IEC61850–8–1:1/EnableSettings byPCM600 or in the LHMI.

1MRK511349-UEN A Section 5Supported services



Figure 8: Enabling parameter setting via IEC 61850

Setting parameter values over the communication link doesn't require anyauthorization if Enable61850Setting has been set to Enabled.

Write to parameters with functional constraint (FC) = SP

• Issue: write to parameter

Writes to parameters where (FC) = SP should not be done while there is anongoing setting group edit session.

Write to parameters with functional constraint FC = SE

• Issue: write to SelectEditSG(n). (n) is the setting group• Issue: write to one or several parameters• Issue: write to ConfirmEditSG (CnfEdit=TRUE)

If a second SelectEditSG(n) is issued where n differs from the actual, anysetting changes are discarded and a new edit session is started.

Cancellation of an ongoing edit session. there are two ways to cancel an ongoing editsession:

Section 5 1MRK511349-UEN ASupported services


• Issue: write to ConfirmEditSG (CnfEdit=FALSE)

or

• Issue: write to SelectEditSG(0)

Reading values where FC = SP

• Issue: read from parameter

Report control block

For properties about report control blocks, see PIXIT.

UnBuffered reporting as well as Buffered reporting is supported.

Generic object oriented substation event (GOOSE)

The structured GOOSE is supported. This means that the data sets can be defined with FCDAas well as explicit attributes.

Note that the data sets that are used or referred to by GOOSE control blockscan only include a data attribute once. In other words, there may not be thesame data attribute in more than one data set.

When publishing a measured value, the user must take care of which measured value dataattributes are added to a data set. If the measured value is event-handled (like in the case ofMMXU 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 valuedesired to be published to a MVGAPC function block (in ACT) and then use the measured valuegiven by the MVGAPC.

Example of functions that have event-handled measured values (can be added directly to thedata 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• MVGAPC - IEC 61850 generic communication I/ O functions

Generic function blocks are provided to make available to the 61850 bus signals that are notdefined inside any of the available function blocks. Example of such functions include:

• SPGAPC - IEC 61850 generic communication I/ O functions• DPGAPC - IEC 61850 generic communication I/ O functions• MVGAPC - IEC 61850 generic communication I/ O functions

Control

Of the different control sequences, the ‘direct-with-normal-security’ and ‘SBO-with-enhanced’security are supported (defined by the ctlModel parameter, IEC 61850-7-2).

1MRK511349-UEN A Section 5Supported services


Check bits; interlock check and synchrocheck check, are only valid for LN types based uponCSWI class.

Verification of Originator Category is supported, see also PIXIT.

Section 5 1MRK511349-UEN ASupported services


Section 6 Data sets and control blocks

6.1 Data setsSEMOD129786-5 v7

IEC 61850 has defined data sets and report control blocks to transmit signals for monitoringpurposes. Data sets are also used for GOOSE messages in horizontal communication amongIEDs. The project defines the data objects or single data attributes that should be collected ina data set. Figure 9 shows a data set where all position information of the apparatuses of abay are put into one data set.

PCM600 will generate default data sets, based on the current ACT configuration. The defaultdata sets can be modified or removed in the engineering tools. No RCBs are createdautomatically by PCM600. However, the configured IEDs are delivered with RCBs for all defaultthe data sets.

Figure 9: IEC 61850–7–2: Example of a data set for MMS

General rules for data set configuration:

• 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 adata 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 isincluded in the SCL file in the IED section in the Logical device subsection. As specified in IEC61850–7–2 clause 9, the data sets are part of a logical node. They are most likely included in theLLN0.

6.2 Report control block (URCB/BRCB)SEMOD129786-17 v5

To be able to transmit the signals configured in a DataSet, a report control block must beconfigured to handle and specify how the events are transmitted to the clients. There are twotypes of report control blocks; unbuffered and buffered. The buffered report control blockstores the events during a communication interrupt, while the unbuffered is sent upon datachange and not stored during interruption.

The content of a BRCB is listed in IEC 61850-7-2 in clause 14. The BRCB contains manyattributes which are of interest to handle and secure the communication between the clientand the server and may be set once as default in a project. Others are of application interest inthe way events are handled in a project.

• Buffer time (valid only for BRCB)

• This parameter describes how long the report should wait for other expected eventsbefore it sends the report to the client. When it is known, that additional events aregenerated as a follow up, it is useful to wait, for example, 500 ms for additionalevents stored in the report. This feature reduces the number of telegramstransmitted in case of a burst of changes. Parameter IEC61850BufTimEnable

1MRK511349-UEN A Section 6Data sets and control blocks


enables/disables the buffer time. For more information, refer section IEC 61850-8-1communication protocol in Technical manual.

• Trigger options

• The data attributes know three different trigger options (dchg, qchg, dupd). Withinthe BRCB, the two other can be defined (integrity and general interrogation). Theattribute Trigger option is a multiple choice and allows to mask the supportedtrigger options in this BRCB.

• Integrity period

• When integrity is selected in the trigger option attribute, it is needed to define anintegrity period to force the transmission of all data listed in the DataSet. This isdone by the attribute Integrity period. This feature can be used as a backgroundcycle to ensure that the process image in all partners is the same.

• General interrogation

• A general interrogation is only done on request from a client. Not all Data-sets maycontain information which is needed for a general update of the client. For exampledata with T(ransient) = TRUE are not part of a GI. When the BRCB attribute generalinterrogation is set to TRUE a GI request from the client will be handled. The reporthandler will transmit all data defined in the Data-set with their actual values. The IEC61850 standard defines that all buffered events shall be transmitted first before theGI is started. A running GI shall be stopped and a new GI shall be started, when a newGI request is received while a GI is running.

• Purge buffer (valid only for BRCB)

• This BRCB attribute can be used by a client to clean the event buffer from old events.The events are discarded on request of the client. This feature can be used to deleteold events not transmitted to the client due to stopped communication. After thelink is reestablished the client can decide to clean the buffer or to receive the history.

Trigger Options

IEC 61850 has defined in total five different TrgOp. Three of them belonging to data attributesand marked per data attribute in the column TrgOp of the CDC tables in part 7–3. The othertwo belonging to the configuration of control blocks.

• dchg = data-change

• Whenever a process value has changed its value either binary or a measurement atransmission is done.

• qchg = quality change

• Looking to the possibilities of the quality data attribute type (q) any changes in thequality description will be transmitted.

• dupd = data value update

• This trigger option give the possibility to define that a transmission should be doneon a condition which can be controlled by the application.

• integrity

• This trigger forces the transmission of all process values defined in the data setwhen a timer value (the integrity period) expires.

• general interrogation

• This trigger is forced by the clients (= station level IED; NCC gateway, stationHMI, ...). Normally a GI is asked for, when the client and the server start or restart asession. When the client is able to receive the actual values and when the logicaldevice has scanned all process values at least once, an image of the actual processsignal status can be transmitted to the client.

Section 6 1MRK511349-UEN AData sets and control blocks


Note that the possible trigger options for each attribute are includedand defined in the datatype template section in SCL.

Link BRCB to a client LN

The BRCB has to know to whom the events shall be transmitted. This is the signal routingengineering step. The IEC standard 61850–6 describes that this is given by including the LN ofthe client IED in the ReportBlockEnabled option.

The selected client IED with the corresponding LN, for example, ITCI is included in the SCLstructure of the Report Control description of the IED section.

The description of the BRCB with selected DataSet, configured parameters and selected IEDsis included in the SCL file in the IED section in the LN0 structure for the LD where this LN0belongs to.



6.3 GOOSE Control Blocks (GoCB)SEMOD129786-83 v6

en06000109.vsd

Send

Data-set

Rec

eive

Rec

eive

LN

LN

LNLN

LN

Send

Data-set

Rec

eive

Rec

eive

LNLN

LN LN

Send

Data-set

Rec

eive

Rec

eive

LN

LNLN

LNLN

LN

Subnetwork

LN0

GoCB

DataSet

InputGoCBGoCB

DataSetDataSet

InputInput

Comm.GSE

LD0

Server

LN0

GoCB

DataSet

InputGoCBGoCB

DataSetDataSet

InputInput

Comm.GSE

LD0

Server


Figure 10: IEC 61850: Principle operation of GOOSE messages

The Generic Object Oriented Substation Event (GOOSE) class model is used to distribute inputand output data values between IEDs on bay level (in horizontal direction) through the use ofmulticast services. GOOSE messages enable fast transmission from a publisher to one orseveral subscribers (receivers).

The GOOSE service model of IEC 61850-7-2 provides the possibility for fast and reliablesystem-wide distribution of input and output data values. This implementation uses a specificscheme of re-transmission to achieve the appropriate level of reliability. When a GOOSE servergenerates a SendGOOSEMessage request, the current data set values are encoded in a GOOSEmessage and transmitted on the multicast association. The event that causes the server toinvoke a SendGOOSE service is a local application issue as defined in IEC 61850-7-2. Eachupdate may generate a message in order to minimize throughput time.

Additional reliability is achieved by re-transmitting the same data (with gradually increasingSqNum and retransmission time).

Section 6 1MRK511349-UEN AData sets and control blocks


T0 retransmission in stable conditions (no event for a long time)

(T0) retransmission in stable conditions may be shortened by an event

T1 shortest retransmission time after the event

T2, T3 retransmission times until achieving the stable conditions time

Time of transmission

T0 (T0) T1 T1 T2 T3 T0

eventIEC09000152-1-en.vsd


Figure 11: Transmission time for events

Each message in the retransmission sequence carries a timeAllowedToLive parameter thatinforms the receiver of the maximum time to wait for the next re-transmission. If a newmessage is not received within that time interval, the receiver assumes that the association islost. The specific intervals used by any GOOSE publisher are a local issue. ThetimeAllowedtoLive parameter informs subscribers of how long to wait.

The GOOSE message concept is used for all application functions where two or more IEDs areinvolved. Typical example is the station-wide interlocking procedure or breaker failureprotection.

Figure 10 shows the GOOSE concept for three IEDs which interchange GOOSE messagesbetween each other.

To send GOOSE messages a GoCB must be defined and a data set is needed that contains thedata objects of single data attributes to be sent.

A GOOSE message is forced to be transmitted when a trigger change is detected for a dataattribute. All members of the data set are copied in the send buffer with their actual value andthe message is sent. The subscribers, who knows the address of this GOOSE message,receives the telegram. The GOOSE message includes a sequence number to verify that allmessages are received.



Section 7 Logical node data model

GUID-EFBB8957-ABA9-4B25-B1CC-630B892A3FC7 v3

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.

• IEC 61850-7-4 Compatible logical node classes and data classes• IEC 61850-7-3 Common data classes

The standard describes only classes of logical nodes and data objects on one side andcommon data classes for the data object attributes. Also here it is given has the elements inthese classes are defined as:

• Mandatory (M)• Optional (O)• Conditional optional (Cxxx)• In addition, the 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 logicalnode of a LN class to that what the product is supporting or using for this LN. This definitionof 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 attributesare called Data Objects (or DATA) and are in of DO types, base upon respective CDC class. Thisallows all partners in the IEC 61850 project who need this LN to understand the LN in all detailsfor the communication part.

The IEC 61850 standard does not describe the functionality and way of operation. Eachsupplier has to describe this separately. ABB has described their function blocks thatrepresent a logical node and all other function blocks in the technical manuals. This chapter inthe 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.

7.1 Common data objects in each logical nodeGUID-8400E43A-6199-4539-BB74-CAC865C85508 v3

The IEC 61850 standard describes in part 7-5, a Common Logical Node. The data objectscontained in that LN are both mandatory and optional. The mandatory data objects have to beincluded in each LN. This clause describes the general handling of the data objects in the IEDs.

The mandatory data objects as defined in IEC 61850-7-4 as part of the Common Logical Nodeare Mode, Behavior, Health and NamePlate.

Mode

The operation modes ON (enabled) and BLOCKED are supported remotely by a command orlocally from the LHMI of the IED.

If the setting “RemoteModControl” is set to “Off” (default), all remote writes toMod will be rejected.

Behaviour

1MRK511349-UEN A Section 7Logical node data model


The operational mode as given by the Mode control is shown in the data object Beh accordingto priority rules described for Beh in clause 6 of IEC 61850-7-4.

The Beh shows the actual state of the function depending on the hierarchy described in clause6 of IEC 61850-7-4.

It is possible that the behavior is influenced also by other sources independent from the Mod,for example Insertion of the test handle, loss of SV, IED configuration tool (PCM600), or LHMI.

In case the setting “operation” of a function is set to Off from the LHMI or PCM600, the Behwill be set to Off independent of the value of the Mod.

The state Off can be set from the LHMI or the PCM600 for the functions having the setting“operation”.

Health

Health will reflect the current status of the IED HW and configuration. Possible values are: OK,Warning, and Alarm.

Health indicates OK, Warning, or Alarm, depending on the IED status.

NamePlt

The name of the logical node and its relation to namespace definition are shown in the dataobject NamePlt as specified for the SCL structure.

7.2 Logical nodes for control

7.2.1 Bay control CBAY

7.2.1.1 Bay control QCBAYGUID-2BD411B4-2371-4B97-8D8D-DB632B15BC85 v1

PID-4086-LOGICALNODEDATA v3

QCBAY (revision 1) Q CBAY

Table 1:

Mod a_dINC Oper.ctlVal CO - Mod Cmd Mode parameter for 61850

Oper.origin.orCat CO - Mod Cmd Mode parameter for 61850

Oper.origin.orIdent CO - Mod Cmd Mode parameter for 61850

Oper.ctlNum CO - Mod Cmd Mode parameter for 61850

Oper.T CO - Mod Cmd Mode parameter for 61850

Oper.Test CO - Mod Cmd Mode parameter for 61850

Oper.Check CO - Mod Cmd Mode parameter for 61850

stVal ST - - Mon Mode status value parameterfor 61850

q ST - - Mon Quality: Mode status valueparameter for 61850

t ST - - Mon Timestamp: Mode status valueparameter for 61850

Table continues on next page

Section 7 1MRK511349-UEN ALogical node data model


Beh a_dINS stVal ST - Beh Mon Behaviour parameter for 61850

q ST - Beh Mon Quality: Behaviour parameterfor 61850

t ST - Beh Mon Timestamp: Behaviourparameter for 61850

LocSwPos v1_dINS stVal ST - - Mon Position of the Local/Remoteswitch

q ST - - Mon Quality: Position of the Local/Remote switch

t ST - - Mon Timestamp: Position of theLocal/Remote switch

SrcOpPrm v1_dINS stVal ST - PSTO Mon Value for the operator placeallocation

q ST - PSTO Mon Quality: Value for the operatorplace allocation

t ST - PSTO Mon Timestamp: Value for theoperator place allocation

BlkCmd v1_dSPC Oper.ctlVal CO - - Cmd Special block command valueused for blockCommand

Oper.origin.orCat CO - - Cmd Special block command valueused for blockCommand

Oper.origin.orIdent CO - - Cmd Special block command valueused for blockCommand

Oper.ctlNum CO - - Cmd Special block command valueused for blockCommand

Oper.T CO - - Cmd Special block command valueused for blockCommand

Oper.Test CO - - Cmd Special block command valueused for blockCommand

Oper.Check CO - - Cmd Special block command valueused for blockCommand

stVal ST - CMD_BLKD Mon Function is blocked forcommands

q ST - CMD_BLKD Mon Quality: Function is blocked forcommands

t ST - CMD_BLKD Mon Timestamp: Function isblocked for commands

BlkUpd v1_dSPC Oper.ctlVal CO - - Cmd Special block command valueused for blockUpdate

Oper.origin.orCat CO - - Cmd Special block command valueused for blockUpdate

Oper.origin.orIdent CO - - Cmd Special block command valueused for blockUpdate

Oper.ctlNum CO - - Cmd Special block command valueused for blockUpdate

Oper.T CO - - Cmd Special block command valueused for blockUpdate

Oper.Test CO - - Cmd Special block command valueused for blockUpdate

Oper.Check CO - - Cmd Special block command valueused for blockUpdate

stVal ST - UPD_BLKD Mon Update of position is blocked




BlkUpd v1_dSPC q ST - UPD_BLKD Mon Quality: Update of position is

blocked

t ST - UPD_BLKD Mon Timestamp: Update of positionis blocked

BlkMeas v1_dSPS stVal ST - - Mon Update of measurand isblocked

q ST - - Mon Quality: Update of measurandis blocked

t ST - - Mon Timestamp: Update ofmeasurand is blocked

Loc v1_dSPS stVal ST - LOC Mon Local operation allowed

q ST - LOC Mon Quality: Local operationallowed

t ST - LOC Mon Timestamp: Local operationallowed

Rem v1_dSPS stVal ST - REM Mon Remote operation allowed

q ST - REM Mon Quality: Remote operationallowed

t ST - REM Mon Timestamp: Remote operationallowed

7.2.2 Switch controller CSWI

7.2.2.1 Switch controller SCSWIGUID-4F40A4BA-6781-41BF-8389-D8EFD791D005 v1


SCSWI (revision 1) S CSWI

Table 2:

Pos a_dDPC Cancel.ctlVal CO - - Cmd Command parameter forIEC61850

Cancel.origin.orCat CO - - Cmd Command parameter forIEC61850

Oper.ctlVal CO - - Cmd Command parameter forIEC61850

Oper.origin.orCat CO - - Cmd Command parameter forIEC61850

SBOw.ctlVal CO - - Cmd Command parameter forIEC61850

SBOw.origin.orCat CO - - Cmd Command parameter forIEC61850

SBOw.origin.orIdent CO - - Cmd Command parameter forIEC61850

Oper.origin.orIdent CO - - Cmd Command parameter forIEC61850

Cancel.origin.orIdent CO - - Cmd Command parameter forIEC61850




Pos a_dDPC Cancel.ctlNum CO - - Cmd Command parameter for

IEC61850

Oper.ctlNum CO - - Cmd Command parameter forIEC61850

SBOw.ctlNum CO - - Cmd Command parameter forIEC61850

SBOw.T CO - - Cmd Command parameter forIEC61850

Cancel.T CO - - Cmd Command parameter forIEC61850

Oper.T CO - - Cmd Command parameter forIEC61850

Oper.Test CO - - Cmd Command parameter forIEC61850

Cancel.Test CO - - Cmd Command parameter forIEC61850

SBOw.Test CO - - Cmd Command parameter forIEC61850

Oper.Check CO - - Cmd Command parameter forIEC61850

SBOw.Check CO - - Cmd Command parameter forIEC61850

stVal ST - POSITION Mon Position indication

q ST - POSITION Mon Quality: Position indication

t ST - POSITION Mon Timestamp: Position indication

stSeld ST - SELECTED Mon Select conditions are fulfilled

subEna SV - - - Substitute enable

subVal SV - - - Substituted double positionvalue

ctlModel CF - CtlModel - Specifies control model type

















OpCls b_dACT general ST T EXE_CL Mon Execute command for closedirection

q ST T EXE_CL Mon Quality: Execute command forclose direction

t ST T EXE_CL Mon Timestamp: Execute commandfor close direction

OpOpn b_dACT general ST T EXE_OP Mon Execute command for opendirection

q ST T EXE_OP Mon Quality: Execute command foropen direction

t ST T EXE_OP Mon Timestamp: Execute commandfor open direction

BlkCmd v1_dSPC Oper.ctlVal CO - - Cmd Special block command value

Oper.origin.orCat CO - - Cmd Special block command value

Oper.origin.orIdent CO - - Cmd Special block command value

Oper.ctlNum CO - - Cmd Special block command value

Oper.T CO - - Cmd Special block command value

Oper.Test CO - - Cmd Special block command value

Oper.Check CO - - Cmd Special block command value

stVal ST - CMD_BLK Mon Commands are blocked

q ST - CMD_BLK Mon Quality: Commands are blocked

t ST - CMD_BLK Mon Timestamp: Commands areblocked

7.3 Logical nodes for conversion functions

7.3.1 Integer to Boolean converter FCVB

7.3.1.1 Integer to Boolean 16 conversion with logic node representationSEMOD158419-1 v3


IB16FCVB (revision 0) IB16 FCVB

Table 3:

Mod a_dINC Oper.ctlVal CO - Mod Cmd Mode parameter

Oper.origin.orCat CO - Mod Cmd Mode parameter

Oper.origin.orIdent CO - Mod Cmd Mode parameter

Oper.ctlNum CO - Mod Cmd Mode parameter

Oper.T CO - Mod Cmd Mode parameter

Oper.Test CO - Mod Cmd Mode parameter

Oper.Check CO - Mod Cmd Mode parameter




Mod a_dINC stVal ST - - Mon Mode status parameter for

61850

q ST - - Mon Quality: Mode status parameterfor 61850

t ST - - Mon Timestamp: Mode statusparameter for 61850




ISCSO b_dINC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







stVal ST - - Mon Integer to be converted to bitpattern OUT1 to OUT16

q ST - - Mon Quality: Integer to be convertedto bit pattern OUT1 to OUT16

t ST - - Mon Timestamp: Integer to beconverted to bit pattern OUT1to OUT16

ctlModel CF - - - Used by CH

7.3.2 Boolean to integer converter FCVI

7.3.2.1 Boolean to integer conversion with logical node representation, 16 bitBTIGAPC

SEMOD175753-1 v4


LN type LN prefix LN class Function block name

B16IFCVI (revision 0) B16I FCVI BTIGAPC



Table 4: BTIGAPC Logical node data

DO name DO type DA name FC T Signal Mon/Cmd

Description








stVal ST - - Mon Mode status parameter for61850



Beh a_dINS stVal ST - Beh Mon Behaviour parameter

q ST - Beh Mon Quality: Behaviour parameter

t ST - Beh Mon Timestamp: Behaviourparameter

OutInt b_dINS stVal ST - OUT Mon Output value

q ST - OUT Mon Quality: Output value

t ST - OUT Mon Timestamp: Output value

7.4 Logical nodes for protection functions

7.4.1 Protection trip conditioning PTRC

7.4.1.1 Logic for group alarm ALMCALHPID-6510-LOGICALNODEDATA v1


ALMCALH (revision 1) ALM CALH ALMCALH

Table 5: ALMCALH Logical node data


Description












Description

Mod a_dINC stVal ST - - Mon Mode status parameter for61850






GrAlm a_dSPS stVal ST - ALARM Mon OR function betweeen inputs 1to 16

q ST - ALARM Mon Quality: OR function betweeeninputs 1 to 16

t ST - ALARM Mon Timestamp: OR functionbetweeen inputs 1 to 16

7.4.1.2 Logic for group indication INDCALHPID-6511-LOGICALNODEDATA v1


INDCALH (revision 1) IND CALH INDCALH

Table 6: INDCALH Logical node data


Description


















Description

GrAlm a_dSPS stVal ST - IND Mon OR function betweeen inputs 1to 16

q ST - IND Mon Quality: OR function betweeeninputs 1 to 16

t ST - IND Mon Timestamp: OR functionbetweeen inputs 1 to 16

7.4.1.3 Tripping logic common 3-phase output SMPPTRCGUID-B56D86A1-47D9-4B45-A90B-B622C3AE5D2D v2



SMPPTRC (revision 3) SMP PTRC SMPPTRC

Table 7: SMPPTRC Logical node data


Description

Str a_dACD general ST - START Mon Common start signal

dirGeneral ST - - Mon Common direction signal

phsA ST - STL1 Mon Start signal from phase L1

dirPhsA ST - - Mon Direction signal from phase L1

phsB ST - STL2 Mon Start signal from phase L2

dirPhsB ST - - Mon Direction signal from phase L2

phsC ST - STL3 Mon Start signal from phase L3

dirPhsC ST - - Mon Direction signal from phase L3

q ST - START Mon Quality: Common start signal

t ST - START Mon Timestamp: Common startsignal

Op a_dACT general ST - TRIP Mon General trip output signal

phsA ST - TRL1 Mon Trip signal from phase L1

phsB ST - TRL2 Mon Trip signal from phase L2

phsC ST - TRL3 Mon Trip signal from phase L3

q ST - TRIP Mon Quality: General trip outputsignal

t ST - TRIP Mon Timestamp: General trip outputsignal












Description

Mod a_dINC stVal ST - - Mon Mode status parameter for61850






LORs v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







SPTr v1_dSPS stVal ST - TR1P Mon Tripping single-pole

q ST - TR1P Mon Quality: Tripping single-pole

t ST - TR1P Mon Timestamp: Tripping single-pole

TwoPTr v1_dSPS stVal ST - TR2P Mon Tripping two-pole

q ST - TR2P Mon Quality: Tripping two-pole

t ST - TR2P Mon Timestamp: Tripping two-pole

TPTr v1_dSPS stVal ST - TR3P Mon Tripping three-pole

q ST - TR3P Mon Quality: Tripping three-pole

t ST - TR3P Mon Timestamp: Tripping three-pole

ClsLO v1_dSPS stVal ST - CLLKOUT Mon Circuit breaker lockout output(set until reset)

q ST - CLLKOUT Mon Quality: Circuit breaker lockoutoutput (set until reset)

t ST - CLLKOUT Mon Timestamp: Circuit breakerlockout output (set until reset)

7.4.1.4 Logic for group warning WRNCALHPID-6512-LOGICALNODEDATA v1


WRNCALH (revision 1) WRN CALH WRNCALH



Table 8: WRNCALH Logical node data


Description














GrAlm a_dSPS stVal ST - WARNING Mon OR function betweeen inputs 1to 16

q ST - WARNING Mon Quality: OR function betweeeninputs 1 to 16

t ST - WARNING Mon Timestamp: OR functionbetweeen inputs 1 to 16

7.4.2 Multipurpose analog protection GAPC

7.4.2.1 General currrent and voltage protection CVGAPCPID-3857-LOGICALNODEDATA v1

GF2LLN0 instance 1 (revision 0) - LLN0

GF2MMXN instance 1 (revision 3) GF2 MMXN

GF2PHAR instance 1 (revision 2) GF2 PHAR

GF2PTOV instance 1 (revision 2) GF2 PTOV

GF2PTOV instance 2 (revision 2) GF2 PTOV

GF2PTUC instance 1 (revision 2) GF2 PTUC

GF2PTUC instance 2 (revision 2) GF2 PTUC

GF2PTUV instance 1 (revision 2) GF2 PTUV

GF2PTUV instance 2 (revision 2) GF2 PTUV

GF2PVOC instance 1 (revision 2) GF2 PVOC

GF2PVOC instance 2 (revision 2) GF2 PVOC

PH1PTRC instance 1 (revision 3) PH1 PTRC



Table 9:

Mod aINC Oper.ctlVal CO - Mod Cmd Mode parameter










Beh aINS stVal ST - Beh Mon Behaviour parameter for 61850



IvdCrv v1SPS stVal ST - - Mon Error signal from overcurrentfunctions

q ST - - Mon Quality: Error signal fromovercurrent functions

t ST - - Mon Timestamp: Error signal fromovercurrent functions

UnVBehMem v1SPS stVal ST - Mon Low voltage for directionalpolarization

q ST - Mon Quality: Low voltage fordirectional polarization

t ST - Mon Timestamp: Low voltage fordirectional polarization

Table 10:

Beh aINS stVal ST - Beh Mon Behaviour parameter for 61850



Amp bMV mag.f MX - CURRENT Mon Measured current value

q MX - CURRENT Mon Quality: Measured current value

t MX - CURRENT Mon Timestamp: Measured currentvalue

Vol bMV mag.f MX - VOLTAGE Mon Measured voltage value

q MX - VOLTAGE Mon Quality: Measured voltage value

t MX - VOLTAGE Mon Timestamp: Measured voltagevalue




Mod cINC stVal ST - - Mon Mode status parameter for61850



AmpPwrFact v2MV mag.f MX - ICOSFI Mon Measured current multipliedwith cos (Phi)

q MX - ICOSFI Mon Quality: Measured currentmultiplied with cos (Phi)

t MX - ICOSFI Mon Timestamp: Measured currentmultiplied with cos (Phi)

VolAmpAng v2MV mag.f MX - Mon Angle between voltage andcurrent

q MX - Mon Quality: Angle between voltageand current

t MX - Mon Timestamp: Angle betweenvoltage and current

Table 11:




Str b_dACD general ST - BLK2ND Mon Block from second harmonicdetection

q ST - BLK2ND Mon Quality: Block from secondharmonic detection

t ST - BLK2ND Mon Timestamp: Block from secondharmonic detection

Mod c_dINC stVal ST - - Mon Mode status parameter for61850



Table 12:




Str b_dACD general ST - Mon Start signal from overvoltagefunction OV1




Str b_dACD q ST - Mon Quality: Start signal from

overvoltage function OV1

t ST - Mon Timestamp: Start signal fromovervoltage function OV1

Op b_dACT general ST T TROV1 Mon Trip signal from overvoltagefunction OV1

q ST T TROV1 Mon Quality: Trip signal fromovervoltage function OV1

t ST T TROV1 Mon Timestamp: Trip signal fromovervoltage function OV1




Table 13:




Str b_dACD general ST - Mon Start signal from overvoltagefunction OV2

q ST - Mon Quality: Start signal fromovervoltage function OV2

t ST - Mon Timestamp: Start signal fromovervoltage function OV2

Op b_dACT general ST T TROV2 Mon Trip signal from overvoltagefunction OV2

q ST T TROV2 Mon Quality: Trip signal fromovervoltage function OV2

t ST T TROV2 Mon Timestamp: Trip signal fromovervoltage function OV2






Table 14:




Str b_dACD general ST - Mon Start signal from undercurrentfunction UC2

q ST - Mon Quality: Start signal fromundercurrent function UC2

t ST - Mon Timestamp: Start signal fromundercurrent function UC2

Op b_dACT general ST T TRUC2 Mon Trip signal from undercurrentfunction UC2

q ST T TRUC2 Mon Quality: Trip signal fromundercurrent function UC2

t ST T TRUC2 Mon Timestamp: Trip signal fromundercurrent function UC2




Table 15:




Str b_dACD general ST - Mon Start signal from undercurrentfunction UC1

q ST - Mon Quality: Start signal fromundercurrent function UC1

t ST - Mon Timestamp: Start signal fromundercurrent function UC1

Op b_dACT general ST T TRUC1 Mon Trip signal from undercurrentfunction UC1

q ST T TRUC1 Mon Quality: Trip signal fromundercurrent function UC1

t ST T TRUC1 Mon Timestamp: Trip signal fromundercurrent function UC1






Table 16:




Str b_dACD general ST - Mon Start signal from undervoltagefunction UV1

q ST - Mon Quality: Start signal fromundervoltage function UV1

t ST - Mon Timestamp: Start signal fromundervoltage function UV1

Op b_dACT general ST T TRUV1 Mon Trip signal from undervoltagefunction UV1

q ST T TRUV1 Mon Quality: Trip signal fromundervoltage function UV1

t ST T TRUV1 Mon Timestamp: Trip signal fromundervoltage function UV1




Table 17:




Str b_dACD general ST - Mon Start signal from undervoltagefunction UV2

q ST - Mon Quality: Start signal fromundervoltage function UV2

t ST - Mon Timestamp: Start signal fromundervoltage function UV2

Op b_dACT general ST T TRUV2 Mon Trip signal from undervoltagefunction UV2

q ST T TRUV2 Mon Quality: Trip signal fromundervoltage function UV2

t ST T TRUV2 Mon Timestamp: Trip signal fromundervoltage function UV2






Table 18:




Str b_dACD general ST - Mon Start signal from overcurrentfunction OC2

dirGeneral ST - DIROC2 Mon Directional mode of OC2(nondir, forward,reverse)

q ST - Mon Quality: Start signal fromovercurrent function OC2

t ST - Mon Timestamp: Start signal fromovercurrent function OC2

Op b_dACT general ST T TROC2 Mon Trip signal from overcurrentfunction OC2

q ST T TROC2 Mon Quality: Trip signal fromovercurrent function OC2

t ST T TROC2 Mon Timestamp: Trip signal fromovercurrent function OC2




IvdCrv v1_dSPS stVal ST - - Mon Error signal from overcurrentfunction OC2

q ST - - Mon Quality: Error signal fromovercurrent function OC2

t ST - - Mon Timestamp: Error signal fromovercurrent function OC2

Table 19:




Str b_dACD general ST - Mon Start signal from overcurrentfunction OC1

dirGeneral ST - DIROC1 Mon Directional mode of OC1(nondir, forward,reverse)

q ST - Mon Quality: Start signal fromovercurrent function OC1

t ST - Mon Timestamp: Start signal fromovercurrent function OC1

Op b_dACT general ST T TROC1 Mon Trip signal from overcurrentfunction OC1




Op b_dACT q ST T TROC1 Mon Quality: Trip signal from

overcurrent function OC1

t ST T TROC1 Mon Timestamp: Trip signal fromovercurrent function OC1




IvdCrv v1_dSPS stVal ST - - Mon Error signal from overcurrentfunction OC1

q ST - - Mon Quality: Error signal fromovercurrent function OC1

t ST - - Mon Timestamp: Error signal fromovercurrent function OC1

Table 20:




Str b_dACD general ST - Mon General start signal

q ST - Mon Quality: General start signal

t ST - Mon Timestamp: General startsignal

Op b_dACT general ST - TRIP Mon General trip signal

q ST - TRIP Mon Quality: General trip signal

t ST - TRIP Mon Timestamp: General trip signal




7.5 System logical nodes

7.5.1 Generic security application component

7.5.1.1 Generic security application component AGSALPID-7016-LOGICALNODEDATA v2


AGSAL instance 1 (revision 2) A GSAL AGSAL

SECLLN0 instance 1 (revision 1) - LLN0 AGSAL



Table 21: AGSAL Logical node data (instance 1)


Description




AcsCtlFail a_dSEC cnt ST - - Mon Mapping tag

t ST - - Mon Timestamp: Mapping tag

AuthFail a_dSEC cnt ST - - Mon Mapping tag


Ina a_dSEC cnt ST - - Mon Mapping tag


SvcViol a_dSEC cnt ST - - Mon Mapping tag


Mod c_dINC stVal ST - - Mon Mode status value parameterfor 61850



OpCntRs f_dINC Oper.ctlVal CO - - Cmd Mapping tag

Oper.origin.orCat CO - - Cmd Mapping tag

Oper.origin.orIdent CO - - Cmd Mapping tag

Oper.ctlNum CO - - Cmd Mapping tag

Oper.T CO - - Cmd Mapping tag

Oper.Test CO - - Cmd Mapping tag

Oper.Check CO - - Cmd Mapping tag

stVal ST - - Mon Mapping tag

q ST - - Mon Quality: Mapping tag


NumCntRs o_dINS stVal ST - - Mon Mapping tag

q ST - - Mon Quality: Mapping tag


Table 22: AGSAL Logical node data (instance 1)


Description








Description

Mod c_dINC stVal ST - - Mon Mode status value parameterfor 61850



7.5.2 Physical device information LPHDPID-4023-LOGICALNODEDATA v3

LPHD (revision 6) - LPHD

Table 23:

PhyNam b_dDPL swRev DC - - - Firmware version

serNum DC - - - Serial Number

model DC - - - IEDModel for IEC61850

PhyHealth n_dINS stVal ST - PhyHealth Mon Physical health

q ST - PhyHealth Mon Quality: Physical health

t ST - PhyHealth Mon Timestamp: Physical health

7.5.3 Logical node zero LLNOPID-5185-LOGICALNODEDATA v1

LLN0 (revision 2) - LLN0

Table 24:















Beh a_dINS q ST - Beh Mon Quality: Behaviour parameter

for 61850


NamPlt ln0_dLPL swRev DC - - - Firmware version

Health n_dINS stVal ST - - Mon Physical health

q ST - - Mon Quality: Physical health

t ST - - Mon Timestamp: Physical health

7.5.4 Access point diagnostic for redundant Ethernet portsRCHLCCH



RCHLCCH (revision 1) RCH LCCH RCHLCCH

Table 25: RCHLCCH Logical node data


Description














ChLiv a_dSPS stVal ST - LinkAUp Mon Channel A link status

q ST - LinkAUp Mon Quality: Channel A link status

t ST - LinkAUp Mon Timestamp: Channel A linkstatus

RedChLiv a_dSPS stVal ST - LinkBUp Mon Channel B link status

q ST - LinkBUp Mon Quality: Channel B link status

t ST - LinkBUp Mon Timestamp: Channel B linkstatus





Description

FerCh b_dINS stVal ST - ErrorRateA Mon Channel A redundancy errorrate

q ST - ErrorRateA Mon Quality: Channel A redundancyerror rate

t ST - ErrorRateA Mon Timestamp: Channel Aredundancy error rate

RedFerCh b_dINS stVal ST - ErrorRateB Mon Channel B redundancy errorrate

q ST - ErrorRateB Mon Quality: Channel B redundancyerror rate

t ST - ErrorRateB Mon Timestamp: Channel Bredundancy error rate

7.5.5 Access point diagnostic for non-redundant Ethernet portSCHLCCH



SCHLCCH (revision 1) SCH LCCH SCHLCCH

Table 26: SCHLCCH Logical node data


Description














ChLiv a_dSPS stVal ST - LINKUP Mon Access point link status

q ST - LINKUP Mon Quality: Access point linkstatus

t ST - LINKUP Mon Timestamp: Access point linkstatus



7.6 Logical nodes for protection related functions

7.6.1 Disturbance recorder RDRE

7.6.1.1 Disturbance report DRPRDREGUID-0B12001D-5AD2-451B-8AFE-0920B947F5C1 v1


DRPRDRE (revision 0) DRP RDRE

Table 27:








stVal ST - ModeSt Mon Mode status parameter for61850

q ST - ModeSt Mon Quality: Mode status parameterfor 61850

t ST - ModeSt Mon Timestamp: Mode statusparameter for 61850




RcdMade a_dSPS stVal ST - RECMADE Mon Disturbance recording made

q ST - RECMADE Mon Quality: Disturbance recordingmade

t ST - RECMADE Mon Timestamp: Disturbancerecording made

FltNum b_dINS stVal ST - FaultNumber Mon Disturbance fault number

q ST - FaultNumber Mon Quality: Disturbance faultnumber

t ST - FaultNumber Mon Timestamp: Disturbance faultnumber



7.7 Logical nodes for generic references

7.7.1 Generic process I/O GGIO

7.7.1.1 Logic rotating switch for function selection and LHMI presentationSLGAPC

SEMOD114936-1 v4



SLGGIO (revision 7) SL GGIO SLGAPC

Table 28: SLGAPC Logical node data


Description














IntIn b_dINS stVal ST - SWPOSN Mon Switch position (integer)

q ST - SWPOSN Mon Quality: Switch position(integer)

t ST - SWPOSN Mon Timestamp: Switch position(integer)

SwPosC1 v5_dISC Oper.ctlVal CO - - Cmd Command parameter forIEC61850


valWTr.posVal ST - - Mon Position








Description

SwPosC1 v5_dISC Oper.Test CO - - Cmd Command parameter forIEC61850


q ST - - Mon Quality: Position

t ST - - Mon Timestamp: Position

ctlModel CF - - - Control model type for jumpcmd

sboTimeout CF - - - Maximum time between selectand execute signals for jumpcmd

sboClass CF - - - Select for many used for jumpcmd

SPCCO v6_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







ctlModel CF - - - Control model type for stepcmd

sboTimeout CF - - - Maximum time between selectand execute signals for stepcmd

sboClass CF - - - Select for many used for stepcmd

7.7.1.2 Selector mini switch VSGAPCSEMOD158754-1 v3


VSGGIO (revision 1) VS GGIO

Table 29:








Mod a_dINC Oper.T CO - Mod Cmd Mode parameter









DPCSO d_dDPC Cancel.ctlVal CO - - Cmd Command parameter forIEC61850

Cancel.origin.orCat CO - - Cmd Command parameter forIEC61850

Oper.ctlVal CO - - Cmd Command parameter forIEC61850


SBOw.ctlVal CO - - Cmd Command parameter forIEC61850

SBOw.origin.orCat CO - - Cmd Command parameter forIEC61850

SBOw.origin.orIdent CO - - Cmd Command parameter forIEC61850


Cancel.origin.orIdent CO - - Cmd Command parameter forIEC61850

Cancel.ctlNum CO - - Cmd Command parameter forIEC61850


SBOw.ctlNum CO - - Cmd Command parameter forIEC61850

SBOw.T CO - - Cmd Command parameter forIEC61850

Cancel.T CO - - Cmd Command parameter forIEC61850



Cancel.Test CO - - Cmd Command parameter forIEC61850

SBOw.Test CO - - Cmd Command parameter forIEC61850





DPCSO d_dDPC SBOw.Check CO - - Cmd Command parameter for

IEC61850

stVal ST - POSITION Mon Position indication, integer

q ST - POSITION Mon Quality: Position indication,integer

t ST - POSITION Mon Timestamp: Positionindication, integer

stSeld ST - - Mon Select conditions are fulfilled

ctlModel CF - CtlModel - Specifies the type for controlmodel according to IEC 61850

7.7.1.3 Generic communication function for Double Point indication DPGAPCSEMOD55384-1 v4


DPGGIO (revision 0) DP GGIO

Table 30:











Beh aINS stVal ST - Beh Mon Behaviour parameter



DPCSO bDPC stVal ST - POSITION Mon Double point indication

q ST - POSITION Mon Quality: Double point indication

t ST - POSITION Mon Timestamp: Double pointindication

7.7.1.4 Single point generic control 8 signals SPC8GAPCSEMOD176448-1 v3


SPC8GGIO (revision 2) SPC8 GGIO



Table 31:














SPCSO1 d_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850


















SPCSO3 d_dSPC Oper.origin.orCat CO - - Cmd Command parameter for

IEC61850





























SPCSO6 d_dSPC Oper.Check CO - - Cmd Command parameter for

IEC61850















7.7.1.5 Event counter with limit supervision L4UFCNTGUID-C7139F45-E03E-440A-85FD-2102B6470688 v1


L4UFCNT (revision 0) L4U FCNT

Table 32:

CntRs a_dBCR actVal ST - VALUE Mon Counted value

q ST - VALUE Mon Quality: Counted value

t ST - VALUE Mon Timestamp: Counted value









Mod a_dINC Oper.Test CO - Mod Cmd Mode parameter for 61850








RsCnt v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







Lim1 v1_dSPS stVal ST - LIMIT1 Mon Counted value is larger than orequal to CounterLimit1

q ST - LIMIT1 Mon Quality: Counted value is largerthan or equal to CounterLimit1

t ST - LIMIT1 Mon Timestamp: Counted value islarger than or equal toCounterLimit1













7.7.1.6 IEC 61850 generic communication I/O functions SPGGIOGUID-900EC450-B37E-4578-ADAA-901CB8CC497D v2


SPGGIO (revision 1) SP GGIO

Table 33:














Ind c_dSPS stVal ST - OUT Mon Output status

q ST - OUT Mon Quality: Output status

t ST - OUT Mon Timestamp: Output status

7.7.1.7 IEC 61850 generic communication I/O functions 16 inputs SP16GGIOGUID-E6D85EF8-3DA5-4814-9337-24DB15B76BF5 v2


SP16GGIO (revision 2) SP16 GGIO



Table 34:














Ind c_dSPS stVal ST - OUT1 Mon Output 1 status

q ST - OUT1 Mon Quality: Output 1 status

t ST - OUT1 Mon Timestamp: Output 1 status

Ind2 c_dSPS stVal ST - OUT2 Mon Output 2 status

























Ind9 c_dSPS q ST - OUT9 Mon Quality: Output 9 status























GrInd v1_dSPS stVal ST - OUTOR Mon Output status logic OR gate forinput 1 to 16

q ST - OUTOR Mon Quality: Output status logic ORgate for input 1 to 16

t ST - OUTOR Mon Timestamp: Output statuslogic OR gate for input 1 to 16

7.7.1.8 Generic communication function for Measured Value MVGAPCSEMOD55402-1 v3


MVGGIO (revision 1) MV GGIO

Table 35:









Mod a_dINC Oper.Test CO - Mod Cmd Mode parameter








AnIn a_dMV rangeC.hhLim.f CF - MV hhLim - High High limit multiplied withthe base prefix (multiplicationfactor)

rangeC.hLim.f CF - MV hLim - High limit multiplied with thebase prefix (multiplicationfactor)

rangeC.lLim.f CF - MV lLim - Low limit multiplied with thebase prefix (multiplicationfactor)

rangeC.llLim.f CF - MV llLim - Low Low limit multiplied withthe base prefix (multiplicationfactor)

rangeC.max.f CF - MV max - Maximum value multiplied withthe base prefix (multiplicationfactor)

rangeC.min.f CF - MV min - Minimum value multiplied withthe base prefix (multiplicationfactor)

mag.f MX - VALUE Mon Magnitude of deadband value

subMag.f SV - - - Substituted value

range MX - RANGE Mon Range

q MX - VALUE Mon Quality: Magnitude ofdeadband value

t MX - VALUE Mon Timestamp: Magnitude ofdeadband value

subEna SV - - - Enable substitution

db CF - MV db - Cycl: Report interval (s), Db: In% of range, Int Db: In %s

zeroDb CF - MV zeroDb - Zero point clamping in 0,001%of range

7.7.1.9 Trip matrix logic TMAGAPCIP15121-1 v4


TMAGGIO (revision 0) TMA GGIO



Table 36:











Beh aINS stVal ST - Beh Mon Behaviour parameter



Out1 v1SPS stVal ST - OUTPUT1 Mon OR function betweeen inputs 1to 16

q ST - OUTPUT1 Mon Quality: OR function betweeeninputs 1 to 16

t ST - OUTPUT1 Mon Timestamp: OR functionbetweeen inputs 1 to 16

Out2 v1SPS stVal ST - OUTPUT2 Mon OR function between inputs 17to 32

q ST - OUTPUT2 Mon Quality: OR function betweeninputs 17 to 32

t ST - OUTPUT2 Mon Timestamp: OR functionbetween inputs 17 to 32

Out3 v1SPS stVal ST - OUTPUT3 Mon OR function between inputs 1to 32

q ST - OUTPUT3 Mon Quality: OR function betweeninputs 1 to 32

t ST - OUTPUT3 Mon Timestamp: OR functionbetween inputs 1 to 32

7.7.1.10 Elapsed time integrator with limit transgression and overflowsupervision TEIGGIO

GUID-9DD4C562-D0D7-4BFB-B9E0-D016675EB772 v1


TEIGGIO (revision 0) TEI GGIO



Table 37:














Alm a_dSPS stVal ST - ALARM Mon Indicator of the integrated timehas reached the alarm limit

q ST - ALARM Mon Quality: Indicator of theintegrated time has reachedthe alarm limit

t ST - ALARM Mon Timestamp: Indicator of theintegrated time has reachedthe alarm limit

RsAccTms v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







Wrn v1_dSPS stVal ST - WARNING Mon Indicator of the integrated timehas reached the warning limit

q ST - WARNING Mon Quality: Indicator of theintegrated time has reachedthe warning limit

t ST - WARNING Mon Timestamp: Indicator of theintegrated time has reachedthe warning limit




AccTms v2_dMV mag.f MX - ACCTIME Mon Integrated elapsed time inseconds

q MX - ACCTIME Mon Quality: Integrated elapsedtime in seconds

t MX - ACCTIME Mon Timestamp: Integrated elapsedtime in seconds

7.8 Logical nodes for sensors and monitoring

7.8.1 Circuit breaker monitoring SSCBR

7.8.1.1 SSCBRGUID-30A59448-3B80-4298-965D-19E28BB0BBD8 v3


SSCBR (revision 3) S SCBR

Table 38:














InaTmdCnt v1_dINS stVal ST - INADAYS Mon The number of days CB hasbeen inactive

q ST - INADAYS Mon Quality: The number of days CBhas been inactive

t ST - INADAYS Mon Timestamp: The number ofdays CB has been inactive

RmnLif v1_dINS stVal ST - CBLIFEPH Mon CB Remaining life of respectivephase

q ST - CBLIFEPH Mon Quality: CB Remaining life ofrespective phase




RmnLif v1_dINS t ST - CBLIFEPH Mon Timestamp: CB Remaining life

of respective phase

RsAccAPwr v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







RsCBWear v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







RsTrvTm v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







RsSprChaTm v1_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







RsSprChaTm v1_dSPC Oper.T CO - - Cmd Command parameter for

IEC61850



OpnAlm v1_dSPS stVal ST - TRVTOPAL Mon CB open travel time exceededset value

q ST - TRVTOPAL Mon Quality: CB open travel timeexceeded set value

t ST - TRVTOPAL Mon Timestamp: CB open traveltime exceeded set value

ClsAlm v1_dSPS stVal ST - TRVTCLAL Mon CB close travel time exceededset value

q ST - TRVTCLAL Mon Quality: CB close travel timeexceeded set value

t ST - TRVTCLAL Mon Timestamp: CB close traveltime exceeded set value

OpNumAlm v1_dSPS stVal ST - OPERALM Mon Number of CB operationsexceeds alarm limit

q ST - OPERALM Mon Quality: Number of CBoperations exceeds alarm limit

t ST - OPERALM Mon Timestamp: Number of CBoperations exceeds alarm limit

OpNumLO v1_dSPS stVal ST - OPERLO Mon Number of CB operationsexceeds lockout limit

q ST - OPERLO Mon Quality: Number of CBoperations exceeds lockoutlimit

t ST - OPERLO Mon Timestamp: Number of CBoperations exceeds lockoutlimit

APwrAlm v1_dSPS stVal ST - IPOWALPH Mon Accum I^CurrExponent integrover CB open travel timeexceeds alarm limit

q ST - IPOWALPH Mon Quality: Accum I^CurrExponentintegr over CB open travel timeexceeds alarm limit

t ST - IPOWALPH Mon Timestamp: AccumI^CurrExponent integr over CBopen travel time exceeds alarmlimit

APwrLO v1_dSPS stVal ST - IPOWLOPH Mon Accum I^CurrExponent integrover CB open travel timeexceeds lockout limit

q ST - IPOWLOPH Mon Quality: Accum I^CurrExponentintegr over CB open travel timeexceeds lockout limit

t ST - IPOWLOPH Mon Timestamp: AccumI^CurrExponent integr over CBopen travel time exceedslockout limit

LonTmAlm v1_dSPS stVal ST - MONALM Mon CB 'not operated for long time'alarm




LonTmAlm v1_dSPS q ST - MONALM Mon Quality: CB 'not operated for

long time' alarm

t ST - MONALM Mon Timestamp: CB 'not operatedfor long time' alarm

SprChaAlm v1_dSPS stVal ST - SPCHALM Mon Spring charging time hascrossed the set value

q ST - SPCHALM Mon Quality: Spring charging timehas crossed the set value

t ST - SPCHALM Mon Timestamp: Spring chargingtime has crossed the set value

PosOpn v1_dSPS stVal ST - OPENPOS Mon CB is in open position

q ST - OPENPOS Mon Quality: CB is in open position

t ST - OPENPOS Mon Timestamp: CB is in openposition

PosIvd v1_dSPS stVal ST - INVDPOS Mon CB is in Invalid Position

q ST - INVDPOS Mon Quality: CB is in Invalid Position

t ST - INVDPOS Mon Timestamp: CB is in InvalidPosition

PosCls v1_dSPS stVal ST - CLOSEPOS Mon CB is in closed position

q ST - CLOSEPOS Mon Quality: CB is in closed position

t ST - CLOSEPOS Mon Timestamp: CB is in closedposition

CBLifAlm v1_dSPS stVal ST - CBLIFEAL Mon Remaining life of CB reduced toLife alarm level

q ST - CBLIFEAL Mon Quality: Remaining life of CBreduced to Life alarm level

t ST - CBLIFEAL Mon Timestamp: Remaining life ofCB reduced to Life alarm level

PresLO v1_dSPS stVal ST - GPRESLO Mon Pressure below lockout level

q ST - GPRESLO Mon Quality: Pressure below lockoutlevel

t ST - GPRESLO Mon Timestamp: Pressure belowlockout level

ColOpn v1_dSPS stVal ST - TRCMD Mon Open command issued to CB

q ST - TRCMD Mon Quality: Open command issuedto CB

t ST - TRCMD Mon Timestamp: Open commandissued to CB

TmmsCls v2_dMV mag.f MX - TTRVCL Mon Travel time of the CB duringclosing operation

q MX - TTRVCL Mon Quality: Travel time of the CBduring closing operation

t MX - TTRVCL Mon Timestamp: Travel time of theCB during closing operation

TmmsOpn v2_dMV mag.f MX - TTRVOP Mon Travel time of the CB duringopening operation

q MX - TTRVOP Mon Quality: Travel time of the CBduring opening operation

t MX - TTRVOP Mon Timestamp: Travel time of theCB during opening operation




TmsSprCha v2_dMV mag.f MX - SPCHT Mon The charging time of the CBspring

q MX - SPCHT Mon Quality: The charging time ofthe CB spring

t MX - SPCHT Mon Timestamp: The charging timeof the CB spring

AccAPwr v2_dMV mag.f MX - IPOWPH Mon Accumulated I^CurrExponentintegrated over CB open traveltime

q MX - IPOWPH Mon Quality: AccumulatedI^CurrExponent integrated overCB open travel time

t MX - IPOWPH Mon Timestamp: AccumulatedI^CurrExponent integrated overCB open travel time

PresAlm v3_dSPS stVal ST - GPRESALM Mon Pressure below alarm level

q ST - GPRESALM Mon Quality: Pressure below alarmlevel

t ST - GPRESALM Mon Timestamp: Pressure belowalarm level

OpCnt v5_dINS stVal ST - NOOPER Mon Number of CB operation cycle

q ST - NOOPER Mon Quality: Number of CBoperation cycle

t ST - NOOPER Mon Timestamp: Number of CBoperation cycle

7.8.2 Insulation medium supervision (gas) SIMG

7.8.2.1 SSIMGGUID-358AD8F8-AE06-4AEA-9969-46E5299D5B4B v3


SSIMG (revision 0) S SIMG

Table 39:













Mod a_dINC t ST - - Mon Timestamp: Mode status

parameter for 61850




InsAlm a_dSPS stVal ST - PRES_LO Mon Pressure below lockout level

q ST - PRES_LO Mon Quality: Pressure below lockoutlevel

t ST - PRES_LO Mon Timestamp: Pressure belowlockout level

PresAlm a_dSPS stVal ST - PRES_ALM Mon Pressure below alarm level

q ST - PRES_ALM Mon Quality: Pressure below alarmlevel

t ST - PRES_ALM Mon Timestamp: Pressure belowalarm level

TmpAlm a_dSPS stVal ST - TEMP_ALM Mon Temperature above alarm level

q ST - TEMP_ALM Mon Quality: Temperature abovealarm level

t ST - TEMP_ALM Mon Timestamp: Temperatureabove alarm level

Pres b_dMV mag.f MX - PRESSURE Mon Pressure service value

q MX - PRESSURE Mon Quality: Pressure service value

t MX - PRESSURE Mon Timestamp: Pressure servicevalue

Tmp b_dMV mag.f MX - TEMP Mon Temperature of the insulationmedium

q MX - TEMP Mon Quality: Temperature of theinsulation medium

t MX - TEMP Mon Timestamp: Temperature ofthe insulation medium








TmpLO v1_dSPS stVal ST - TEMP_LO Mon Temperature above lockoutlevel

q ST - TEMP_LO Mon Quality: Temperature abovelockout level

t ST - TEMP_LO Mon Timestamp: Temperatureabove lockout level



7.8.3 Insulation medium supervision (liquid) SIMLGUID-37669E94-4830-4C96-8A67-09600F847F23 v3PID-3706-LOGICALNODEDATA v3

SSIML (revision 0) S SIML

Table 40:














InsAlm a_dSPS stVal ST - LVL_LO Mon Level below lockout level

q ST - LVL_LO Mon Quality: Level below lockoutlevel

t ST - LVL_LO Mon Timestamp: Level belowlockout level

PresAlm a_dSPS stVal ST - LVL_ALM Mon Level below alarm level

q ST - LVL_ALM Mon Quality: Level below alarm level

t ST - LVL_ALM Mon Timestamp: Level below alarmlevel

TmpAlm a_dSPS stVal ST - TEMP_ALM Mon Temperature above alarm level

q ST - TEMP_ALM Mon Quality: Temperature abovealarm level

t ST - TEMP_ALM Mon Timestamp: Temperatureabove alarm level

Pres b_dMV mag.f MX - LEVEL Mon Level service value

q MX - LEVEL Mon Quality: Level service value

t MX - LEVEL Mon Timestamp: Level service value

Tmp b_dMV mag.f MX - TEMP Mon Temperature of the insulationmedium

q MX - TEMP Mon Quality: Temperature of theinsulation medium




Tmp b_dMV t MX - TEMP Mon Timestamp: Temperature of

the insulation medium








TmpLo v1_dSPS stVal ST - TEMP_LO Mon Temperature above lockoutlevel

q ST - TEMP_LO Mon Quality: Temperature abovelockout level

t ST - TEMP_LO Mon Timestamp: Temperatureabove lockout level

7.8.4 Through fault monitoring STHR

7.8.4.1 Through fault monitoring PTRSTHRGUID-7AE60CB5-3CD5-4FE2-8D54-664AA78DD2DE v1


PTRSTHR (revision 0) PTR STHR

Table 41:















Beh a_dINS q ST - Beh Mon Quality: Behaviour parameter

for 61850


GenAlm a_dSPS stVal ST - ALARM Mon General fault detection alarm

q ST - ALARM Mon Quality: General fault detectionalarm

t ST - ALARM Mon Timestamp: General faultdetection alarm

GenCmAlm a_dSPS stVal ST - CMLI2TALM Mon General cumulative fault (I^2)talarm

q ST - CMLI2TALM Mon Quality: General cumulativefault (I^2)t alarm

t ST - CMLI2TALM Mon Timestamp: General cumulativefault (I^2)t alarm

GenEvtAlm a_dSPS stVal ST - I2TALM Mon General fault (I^2)t alarm for anevent

q ST - I2TALM Mon Quality: General fault (I^2)talarm for an event

t ST - I2TALM Mon Timestamp: General fault (I^2)talarm for an event

RpRdy a_dSPS stVal ST - REPMADE Mon Report is ready for file transfer

q ST - REPMADE Mon Quality: Report is ready for filetransfer

t ST - REPMADE Mon Timestamp: Report is ready forfile transfer

FltCnt b_dINS stVal ST - TFCNT Mon Overall number of faultsdetected since last reset

q ST - TFCNT Mon Quality: Overall number offaults detected since last reset

t ST - TFCNT Mon Timestamp: Overall number offaults detected since last reset

7.9 Logical nodes for switchgear

7.9.1 Circuit breaker XCBR

7.9.1.1 Circuit breaker SXCBRGUID-C865CD66-9B2F-4D40-9BC0-BCA7DE7A3D8E v1


SXCBR (revision 1) S XCBR



Table 42:














BlkCls a_dSPC Oper.ctlVal CO - - Cmd Special block command value







stVal ST - CL_BLKD Mon Indication that the function isblocked for close commands

q ST - CL_BLKD Mon Quality: Indication that thefunction is blocked for closecommands

t ST - CL_BLKD Mon Timestamp: Indication that thefunction is blocked for closecommands

BlkOpn a_dSPC Oper.ctlVal CO - - Cmd Special block command value







stVal ST - OP_BLKD Mon Indication that the function isblocked for open commands

q ST - OP_BLKD Mon Quality: Indication that thefunction is blocked for opencommands




BlkOpn a_dSPC t ST - OP_BLKD Mon Timestamp: Indication that the

function is blocked for opencommands

Loc a_dSPS stVal ST - - Mon Indication that the function isin local mode (process level)

q ST - - Mon Quality: Indication that thefunction is in local mode(process level)

t ST - - Mon Timestamp: Indication that thefunction is in local mode(process level)

OpCnt b_dINS stVal ST - CNT_VAL Mon Operation counter value

q ST - CNT_VAL Mon Quality: Operation countervalue

t ST - CNT_VAL Mon Timestamp: Operation countervalue

Pos c_dDPC stVal ST - POSITION Mon Apparatus position indication

q ST - POSITION Mon Quality: Apparatus positionindication

t ST - POSITION Mon Timestamp: Apparatus positionindication



CBOpCap h_dINS stVal ST - CBOPCAP Mon Breaker operating capability 1 =None, 2 = O, 3 = CO, 4 = OCO, 5= COCO, 6+ = More

q ST - CBOPCAP Mon Quality: Breaker operatingcapability 1 = None, 2 = O, 3 =CO, 4 = OCO, 5 = COCO, 6+ =More

t ST - CBOPCAP Mon Timestamp: Breaker operatingcapability 1 = None, 2 = O, 3 =CO, 4 = OCO, 5 = COCO, 6+ =More

BlkUpd v1_dSPC Oper.ctlVal CO - - Cmd Special block command value







stVal ST - UPD_BLKD Mon Update of position indication isblocked

q ST - UPD_BLKD Mon Quality: Update of positionindication is blocked

t ST - UPD_BLKD Mon Timestamp: Update of positionindication is blocked



7.9.2 Switch XSWI

7.9.2.1 Circuit switch SXSWIGUID-A7AEBCA2-89FD-4F6E-A3B8-57E6A16035C9 v1


SXSWI (revision 1) S XSWI

Table 43:














BlkCls a_dSPC Oper.ctlVal CO - - Cmd Special block command value







stVal ST - CL_BLKD Mon Indication that the function isblocked for close commands

q ST - CL_BLKD Mon Quality: Indication that thefunction is blocked for closecommands

t ST - CL_BLKD Mon Timestamp: Indication that thefunction is blocked for closecommands

BlkOpn a_dSPC Oper.ctlVal CO - - Cmd Special block command value







BlkOpn a_dSPC Oper.T CO - - Cmd Special block command value



stVal ST - OP_BLKD Mon Indication that the function isblocked for open commands

q ST - OP_BLKD Mon Quality: Indication that thefunction is blocked for opencommands

t ST - OP_BLKD Mon Timestamp: Indication that thefunction is blocked for opencommands

Loc a_dSPS stVal ST - - Mon Indication that the function isin local mode (process level)

q ST - - Mon Quality: Indication that thefunction is in local mode(process level)

t ST - - Mon Timestamp: Indication that thefunction is in local mode(process level)

OpCnt b_dINS stVal ST - CNT_VAL Mon Operation counter value

q ST - CNT_VAL Mon Quality: Operation countervalue

t ST - CNT_VAL Mon Timestamp: Operation countervalue

Pos c_dDPC stVal ST - POSITION Mon Apparatus position indication

q ST - POSITION Mon Quality: Apparatus positionindication

t ST - POSITION Mon Timestamp: Apparatus positionindication



SwOpCap f_dINS stVal ST - SWOPCAP Mon Switch operating capability 1 =None, 2 = O, 3 = C, 4 = O and C

q ST - SWOPCAP Mon Quality: Switch operatingcapability 1 = None, 2 = O, 3 = C,4 = O and C

t ST - SWOPCAP Mon Timestamp: Switch operatingcapability 1 = None, 2 = O, 3 = C,4 = O and C

SwTyp g_dINS stVal ST - - Mon 1=LoadBreak,2=Disconnector,3=EarthSw,4=HighSpeedEarthSw

q ST - - Mon Quality:1=LoadBreak,2=Disconnector,3=EarthSw,4=HighSpeedEarthSw

t ST - - Mon Timestamp:1=LoadBreak,2=Disconnector,3=EarthSw,4=HighSpeedEarthSw

BlkUpd v1_dSPC Oper.ctlVal CO - - Cmd Special block command value





BlkUpd v1_dSPC Oper.origin.orIdent CO - - Cmd Special block command value





stVal ST - UPD_BLKD Mon Update of position indication isblocked

q ST - UPD_BLKD Mon Quality: Update of positionindication is blocked

t ST - UPD_BLKD Mon Timestamp: Update of positionindication is blocked



Section 8 Flexible product naming

8.1 IntroductionGUID-98BC22A7-8EFF-4CD0-829E-FBB5D8FD8024 v2

The Flexible product naming tool in PCM600 allows the customer to use an IED-vendorindependent 61850 model of the IED. This customer model will be exposed in all IEC 61850communication, but all other aspects of the IED will remain unchanged (for example, names onthe local HMI and names in the tools).

This offers significant flexibility to adapt the IED to the customers system and standardsolution.

Benefits:

• IEDs uses the customer model for communication.• Customer specific naming convention for communication can be used.• Other IEDs and station level equipment can be defined from the customer specific

communication model.• Error tracing of communication can be the same between different installations.

8.1.1 Mapping exampleGUID-DD7F097C-1D72-4BA2-8684-61B54EF0D00C v1

FunctionA

Non-affected function views IED 61850 model Customer 61850 modelFPN mapping

FunctionB

LHMI view

PCM view

... view

LD

APTOC

BPTOC

LD

L1PTOC

L2PTOC

LD

LD

IEC15000502-2-en.vsdx


Figure 12: L1PTOC in the customer model mapped to BPTOC in the IED model andL2PTOC mapped to APTOC

Mapping shown in Figure 12 results to mapping shown in Figure 13.

1MRK511349-UEN A Section 8Flexible product naming


FunctionA

Non-affected function views

FunctionB

LHMI view

PCM view

... view

LD

L1PTOC

L2PTOC

LD

LD

Customer 61850 model

IEC15000503-2-en.vsdx


Figure 13: L1PTOC mapped to FunctionB and L2PTOC mapped to FunctionA

8.1.2 Mapping possibilities and requirementsGUID-AA4E0570-D874-4B82-84A5-729644C67626 v1

The mapping between the IED model and the customer model provides a set of possibilitiesbut also include some requirements.

The mapping is possible at several levels in the structure:

• Logical Node level (LN to LN)• Data Object level (DO to DO)• Data Attribute level (DA to DA).

Custom logical device name (LDName) can be used for addressing.

When the mapping is performed there are some requirements that must be fulfilled betweenthe IED model and the customer model:

• One attribute in the customer model can only be mapped to one attribute in the IEDmodel.

• However one attribute in the IED model can be mapped to several attributes in thecustomer model.

• The functional constraint (FC) of the data attributes must match.• The basic type of the data attributes must match.• Trigger options of the data attributes must match.• The version of the IEC 61850 standard must match.• Number of data sets must not exceed the maximum number of data sets that the IED

supports.

There are also some consequences that must be thought about when doing the mapping forexample,

Section 8 1MRK511349-UEN AFlexible product naming


• If two DOs in one LN in the customer model are mapped to DOs in different LNs in the IEDmodel the DOs in the customer model might be inconsistent with respect to quality in thecase of different operational states of the IED Functions.

• When several LNs in the customer model are mapped to one function in the IED, the Modof the function will affect all the customer LNs

Several other use cases like this exist. By understanding the concept of mapping from IEDfunctions and IED model to customer model, these cases can be foreseen.

1MRK511349-UEN A Section 8Flexible product naming


Section 9 Glossary

M14893-1 v18

AC Alternating current

ACC Actual channel

ACT Application configuration tool within PCM600

A/D converter Analog-to-digital converter

ADBS Amplitude deadband supervision

ADM Analog digital conversion module, with time synchronization

AI Analog input

ANSI American National Standards Institute

AR Autoreclosing

ASCT Auxiliary summation current transformer

ASD Adaptive signal detection

ASDU Application service data unit

AWG American Wire Gauge standard

BBP Busbar protection

BFOC/2,5 Bayonet fiber optic connector

BFP Breaker failure protection

BI Binary input

BIM Binary input module

BOM Binary output module

BOS Binary outputs status

BR External bistable relay

BS British Standards

BSR Binary signal transfer function, receiver blocks

BST Binary signal transfer function, transmit blocks

C37.94 IEEE/ANSI protocol used when sending binary signals between IEDs

CAN Controller Area Network. ISO standard (ISO 11898) for serialcommunication

CB Circuit breaker

CBM Combined backplane module

CCITT Consultative Committee for International Telegraph and Telephony. AUnited Nations-sponsored standards body within the InternationalTelecommunications Union.

CCM CAN carrier module

CCVT Capacitive Coupled Voltage Transformer

Class C Protection Current Transformer class as per IEEE/ ANSI

CMPPS Combined megapulses per second

CMT Communication Management tool in PCM600

1MRK511349-UEN A Section 9Glossary


CO cycle Close-open cycle

Codirectional Way of transmitting G.703 over a balanced line. Involves two twistedpairs making it possible to transmit information in both directions

COM Command

COMTRADE Standard Common Format for Transient Data Exchange format forDisturbance recorder according to IEEE/ANSI C37.111, 1999 / IEC60255-24

Contra-directional Way of transmitting G.703 over a balanced line. Involves four twistedpairs, two of which are used for transmitting data in both directionsand two for transmitting clock signals

COT Cause of transmission

CPU Central processing unit

CR Carrier receive

CRC Cyclic redundancy check

CROB Control relay output block

CS Carrier send

CT Current transformer

CU Communication unit

CVT or CCVT Capacitive voltage transformer

DAR Delayed autoreclosing

DARPA Defense Advanced Research Projects Agency (The US developer of theTCP/IP protocol etc.)

DBDL Dead bus dead line

DBLL Dead bus live line

DC Direct current

DFC Data flow control

DFT Discrete Fourier transform

DHCP Dynamic Host Configuration Protocol

DIP-switch Small switch mounted on a printed circuit board

DI Digital input

DLLB Dead line live bus

DNP Distributed Network Protocol as per IEEE Std 1815-2012

DR Disturbance recorder

DRAM Dynamic random access memory

DRH Disturbance report handler

DSP Digital signal processor

DTT Direct transfer trip scheme

ECT Ethernet configuration tool

EHV network Extra high voltage network

EIA Electronic Industries Association

EMC Electromagnetic compatibility

EMF Electromotive force

Section 9 1MRK511349-UEN AGlossary


EMI Electromagnetic interference

EnFP End fault protection

EPA Enhanced performance architecture

ESD Electrostatic discharge

F-SMA Type of optical fiber connector

FAN Fault number

FCB Flow control bit; Frame count bit

FOX 20 Modular 20 channel telecommunication system for speech, data andprotection signals

FOX 512/515 Access multiplexer

FOX 6Plus Compact time-division multiplexer for the transmission of up to sevenduplex channels of digital data over optical fibers

FPN Flexible product naming

FTP File Transfer Protocol

FUN Function type

G.703 Electrical and functional description for digital lines used by localtelephone companies. Can be transported over balanced andunbalanced lines

GCM Communication interface module with carrier of GPS receiver module

GDE Graphical display editor within PCM600

GI General interrogation command

GIS Gas-insulated switchgear

GOOSE Generic object-oriented substation event

GPS Global positioning system

GSAL Generic security application

GSE Generic substation event

HDLC protocol High-level data link control, protocol based on the HDLC standard

HFBR connector type Plastic fiber connector

HLV circuit Hazardous Live Voltage according to IEC60255-27

HMI Human-machine interface

HSAR High speed autoreclosing

HSR High-availability Seamless Redundancy

HV High-voltage

HVDC High-voltage direct current

IDBS Integrating deadband supervision

IEC International Electrical Committee

IEC 60044-6 IEC Standard, Instrument transformers – Part 6: Requirements forprotective current transformers for transient performance

IEC 60870-5-103 Communication standard for protection equipment. A serial master/slave protocol for point-to-point communication

IEC 61850 Substation automation communication standard

IEC 61850–8–1 Communication protocol standard



IEEE Institute of Electrical and Electronics Engineers

IEEE 802.12 A network technology standard that provides 100 Mbits/s on twisted-pair or optical fiber cable

IEEE P1386.1 PCI Mezzanine Card (PMC) standard for local bus modules. Referencesthe CMC (IEEE P1386, also known as Common Mezzanine Card)standard for the mechanics and the PCI specifications from the PCI SIG(Special Interest Group) for the electrical EMF (Electromotive force).

IEEE 1686 Standard for Substation Intelligent Electronic Devices (IEDs) CyberSecurity Capabilities

IED Intelligent electronic device

IET600 Integrated engineering tool

I-GIS Intelligent gas-insulated switchgear

IOM Binary input/output module

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 afunction is identical to another of the same kind but has a differentnumber in the IED user interfaces. The word "instance" is sometimesdefined as an item of information that is representative of a type. Inthe same way an instance of a function in the IED is representative of atype of function.

IP 1. Internet protocol. The network layer for the TCP/IP protocol suitewidely used on Ethernet networks. IP is a connectionless, best-effortpacket-switching protocol. It provides packet routing, fragmentationand reassembly through the data link layer.2. Ingression protection, according to IEC 60529

IP 20 Ingression protection, according to IEC 60529, level



IRF Internal failure signal

IRIG-B: InterRange Instrumentation Group Time code format B, standard 200

ITU International Telecommunications Union

LAN Local area network

LIB 520 High-voltage software module

LCD Liquid crystal display

LDCM Line data communication module

LDD Local detection device

LNT LON network tool

LON Local operating network

MCB Miniature circuit breaker

MCM Mezzanine carrier module

MPM Main processing module

MVAL Value of measurement

MVB Multifunction vehicle bus. Standardized serial bus originally developedfor use in trains.

NCC National Control Centre

NOF Number of grid faults



NUM Numerical module

OCO cycle Open-close-open cycle

OCP Overcurrent protection

OLTC On-load tap changer

OTEV Disturbance data recording initiated by other event than start/pick-up

OV Overvoltage

Overreach A term used to describe how the relay behaves during a fault condition.For example, a distance relay is overreaching when the impedancepresented to it is smaller than the apparent impedance to the faultapplied to the balance point, that is, the set reach. The relay “sees” thefault but perhaps it should not have seen it.

PCI Peripheral component interconnect, a local data bus

PCM Pulse code modulation

PCM600 Protection and control IED manager

PC-MIP Mezzanine card standard

PELV circuit Protected Extra-Low Voltage circuit type according to IEC60255-27

PMC PCI Mezzanine card

POR Permissive overreach

POTT Permissive overreach transfer trip

Process bus Bus or LAN used at the process level, that is, in near proximity to themeasured and/or controlled components

PRP Parallel redundancy protocol

PSM Power supply module

PST Parameter setting tool within PCM600

PTP Precision time protocol

PT ratio Potential transformer or voltage transformer ratio

PUTT Permissive underreach transfer trip

RASC Synchrocheck relay, COMBIFLEX

RCA Relay characteristic angle

RISC Reduced instruction set computer

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

SA Substation Automation

SBO Select-before-operate

SC Switch or push button to close

SCL Short circuit location

SCS Station control system

SCADA Supervision, control and data acquisition



SCT System configuration tool according to standard IEC 61850

SDU Service data unit

SELV circuit Safety Extra-Low Voltage circuit type according to IEC60255-27

SFP Small form-factor pluggable (abbreviation)Optical Ethernet port (explanation)

SLM Serial communication module.

SMA connector Subminiature version A, A threaded connector with constantimpedance.

SMT Signal matrix tool within PCM600

SMS Station monitoring system

SNTP Simple network time protocol – is used to synchronize computer clockson local area networks. This reduces the requirement to have accuratehardware clocks in every embedded system in a network. Eachembedded node can instead synchronize with a remote clock,providing the required accuracy.

SOF Status of fault

SPA Strömberg Protection Acquisition (SPA), a serial master/slave protocolfor point-to-point and ring communication.

SRY Switch for CB ready condition

ST Switch or push button to trip

Starpoint point of transformer or generator

SVC Static VAr compensation

TC Trip coil

TCS Trip circuit supervision

TCP Transmission control protocol. The most common transport layerprotocol used on Ethernet and the Internet.

TCP/IP Transmission control protocol over Internet Protocol. The de factostandard Ethernet protocols incorporated into 4.2BSD Unix. TCP/IPwas developed by DARPA for Internet working and encompasses bothnetwork layer and transport layer protocols. While TCP and IP specifytwo protocols at specific protocol layers, TCP/IP is often used to referto the entire US Department of Defense protocol suite based uponthese, including Telnet, FTP, UDP and RDP.

TEF Time delayed -fault protection function

TLS Transport Layer Security

TM Transmit (disturbance data)

TNC connector Threaded Neill-Concelman, a threaded constant impedance version of aBNC connector

TP Trip (recorded fault)

TPZ, TPY, TPX, TPS Current transformer class according to IEC

TRM Transformer Module. This module transforms currents and voltagestaken from the process into levels suitable for further signalprocessing.

TYP Type identification

UMT User management tool



Underreach A term used to describe how the relay behaves during a fault condition.For example, a distance relay is underreaching when the impedancepresented to it is greater than the apparent impedance to the faultapplied to the balance point, that is, the set reach. The relay does not“see” the fault but perhaps it should have seen it. See also Overreach.

UTC Coordinated Universal Time. A coordinated time scale, maintained bythe Bureau International des Poids et Mesures (BIPM), which forms thebasis of a coordinated dissemination of standard frequencies and timesignals. UTC is derived from International Atomic Time (TAI) by theaddition of a whole number of "leap seconds" to synchronize it withUniversal Time 1 (UT1), thus allowing for the eccentricity of the Earth'sorbit, the rotational axis tilt (23.5 degrees), but still showing the Earth'sirregular rotation, on which UT1 is based. The Coordinated UniversalTime is expressed using a 24-hour clock, and uses the Gregoriancalendar. It is used for aeroplane and ship navigation, where it is alsosometimes known by the military name, "Zulu time." "Zulu" in thephonetic alphabet stands for "Z", which stands for longitude zero.

UV Undervoltage

WEI Weak end infeed logic

VT Voltage transformer

3IO Three times zero-sequence current.



Scan this QR code to visit our website

1MR

K51

134

9-U

EN

communication protocol manual - abb group · 2019-03-11 · relion®670 series iec 61850 edition 1,...

Documents