Load Shedding Controller PML630 IEC 61850 Communication ... fileRelion® 630 series Load Shedding Controller PML630 IEC 61850 Communication Protocol Manual

Relion® 630 series

Load Shedding ControllerPML630IEC 61850 Communication Protocol Manual

Document ID: 1MRS757260Issued: 2011-11-03

Revision: BProduct version: 1.1.1

© Copyright 2011 ABB. All rights reserved

CopyrightThis document and parts thereof must not be reproduced or copied without writtenpermission from ABB, and the contents thereof must not be imparted to a thirdparty, nor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a licenseand may be used, copied, or disclosed only in accordance with the terms of suchlicense.

TrademarksABB and Relion are registered trademarks of the ABB Group. All other brand orproduct names mentioned in this document may be trademarks or registeredtrademarks of their respective holders.

WarrantyPlease inquire about the terms of warranty from your nearest ABB representative.

http://www.abb.com/substationautomation

HTTP://WWW.ABB.COM/SUBSTATIONAUTOMATION

DisclaimerThe data, examples and diagrams in this manual are included solely for the conceptor product description and are not to be deemed as a statement of guaranteedproperties. All persons responsible for applying the equipment addressed in thismanual must satisfy themselves that each intended application is suitable andacceptable, including that any applicable safety or other operational requirementsare complied with. In particular, any risks in applications where a system failure and/or product failure would create a risk for harm to property or persons (including butnot limited to personal injuries or death) shall be the sole responsibility of theperson or entity applying the equipment, and those so responsible are herebyrequested to ensure that all measures are taken to exclude or mitigate such risks.

This document has been carefully checked by ABB but deviations cannot becompletely ruled out. In case any errors are detected, the reader is kindly requestedto notify the manufacturer. Other than under explicit contractual commitments, inno event shall ABB be responsible or liable for any loss or damage resulting fromthe use of this manual or the application of the equipment.

ConformityThis product complies with the directive of the Council of the EuropeanCommunities on the approximation of the laws of the Member States relating toelectromagnetic compatibility (EMC Directive 2004/108/EC) and concerningelectrical equipment for use within specified voltage limits (Low-voltage directive2006/95/EC). This conformity is the result of tests conducted by ABB inaccordance with the product standards EN 50263 and EN 60255-26 for the EMCdirective, and with the product standards EN 60255-1 and EN 60255-27 for the lowvoltage directive. The product is designed in accordance with the internationalstandards of the IEC 60255 series.

Table of contents

Section 1 Introduction.......................................................................3This manual........................................................................................3Intended audience..............................................................................3Product documentation.......................................................................4

Product documentation set............................................................4Document revision history.............................................................5Related documentation..................................................................6

Symbols and conventions...................................................................6Symbols.........................................................................................6Manual conventions.......................................................................6Functions, codes and symbols......................................................7

Section 2 Introduction to IEC 61850.................................................9Related documentation to IEC 61850..........................................10

Section 3 Substation Configuration Language (SCL)....................13The Substation section.....................................................................14The Communication section.............................................................14The IED section................................................................................15Tool concept.....................................................................................17Engineering concept in IEC 61850-6................................................18

Section 4 Communication profile....................................................21

Section 5 Supported services.........................................................23

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

Section 7 Logical node data model................................................33Common data objects in each logical node......................................33Logical nodes for control..................................................................34

IEC61850 generic communication I/O functions DPGGIO..........34Logical node for monitoring..............................................................34

Station battery supervision SPVNZBAT......................................34IEC61850 generic communication I/O functions MVGGIO..........36IEC61850 generic communication I/O functions SPGGIO..........36

Logical node for power management...............................................37Input interface function for network circuit breaker dataNCBDCSWI.................................................................................37

Table of contents

PML630 1Communication Protocol Manual

Contingency based fast load shed function LSCACLS...............39Sheddable load trip command LSPTRC......................................49Input interface function for sheddable load data LDMMXU.........54Input interface function for network power source dataPWSMMXU.................................................................................67Output interface function for sub network data SNWRCLS.........79

Logical node for disturbance recorder function................................83Disturbance report DRRDRE.......................................................83

Load shedding power management function blocks........................84

Section 8 Glossary.........................................................................87

Table of contents

2 PML630Communication Protocol Manual

Section 1 Introduction

1.1 This manual

The communication protocol manual describes a communication protocolsupported by the IED. The manual concentrates on vendor-specific implementations.

1.2 Intended audience

This manual addresses the communication system engineer or system integratorresponsible for pre-engineering and engineering for communication setup in asubstation from an IED perspective.

The system engineer or system integrator must have a basic knowledge ofcommunication in protection and control systems and thorough knowledge of thespecific communication protocol.

1MRS757260 B Section 1Introduction


1.3 Product documentation

1.3.1 Product documentation set

Pla

nnin

g &

pur

chas

e

Eng

inee

ring

Inst

allin

g

Com

mis

sion

ing

Ope

ratio

n

Mai

nten

ance

Dec

omm

issi

onin

gde

inst

allin

g&

dis

posa

l

Application engineering

Operation manual

Installation manual

Service manual

Engineering manual

Commissioning manual

Communication protocolmanual

Technical manual

Pla

nnin

g &

pur

chas

e

Eng

inee

ring

Inst

allin

g

Com

mis

sion

ing

Ope

ratio

n

Mai

nten

ance

Dec

omm

issi

onin

gde

inst

allin

g&

dis

posa

l

Pla

nnin

g &

pur

chas

e

Eng

inee

ring

Inst

allin

g

Com

mis

sion

ing

Ope

ratio

n

Mai

nten

ance

Dec

omm

issi

onin

gde

inst

allin

g&

dis

posa

l

ApplicationApplication

Operation manualOperation manual

Installation manualInstallation manual

Service manualService manual

EngineeringEngineering

Commissioning Commissioning

Communication protocolmanualCommunication protocolmanual

Technical manualTechnical manual

engineeringengineeringguideguideguide

GUID-6D633E82-6FD1-46D4-B2EC-D93A3E2016D8 V1 EN

Figure 1: The intended use of manuals in different lifecycles

The engineering manual contains instructions on how to engineer the IED usingPCM600. The manual provides instructions on how to set up a PCM600 projectand insert IEDs to the project structure. The manual also recommends a sequencefor engineering of load shedding power management function, LHMI functions andcommunication engineering for IEC 61850.

The installation manual contains instructions on how to install the IED. Themanual provides procedures for mechanical and electrical installation. The chaptersare organized in chronological order in which the IED should be installed.

The commissioning manual contains instructions on how to commission the IEDwith the load shedding power management functions. The manual can also be usedby system engineers and maintenance personnel for assistance during the testingphase. The manual provides procedures for checking external circuitry andenergizing the IED, parameter setting and configuration. The manual describes theprocess of testing an IED in a substation that is not in service. The chapters areorganized in chronological order in which the IED should be commissioned.

Section 1 1MRS757260 BIntroduction


The application engineering guide provides information for IEC 61850 engineeringof the load shedding controller IED, protection and control IEDs and COM600Station Automation device using PCM600, IET600 and SAB600. With a practicalexample, the guide explains all the steps from system planning and engineering toapplication functionality and IED parameterization for realizing the load sheddingfunctionality using the IEDs.

The operation manual contains instructions on how to operate the IED once it hasbeen commissioned. The manual provides instructions for monitoring, controllingand setting the IED.

The service manual contains instructions on how to service and maintain the IED.The manual also provides procedures for de-energizing, de-commissioning anddisposal of the IED.

The technical manual contains application and functionality descriptions and listsfunction blocks, logic diagrams, input and output signals, setting parameters andtechnical data sorted per function. The manual can be used as a technical referenceduring the engineering phase, installation and commissioning phase, and duringnormal service.

The communication protocol manual describes a communication protocolsupported by the IED. The manual concentrates on vendor-specific implementations.

The point list manual describes the outlook and properties of the data pointsspecific to the IED. The manual should be used with the correspondingcommunication protocol manual.

The IED documentation set includes operation manual, engineeringmanual, application engineering guide, technical manual, point listmanual and IEC 61850 communication protocol manual. See the630 series documentation set for installation manual andcommissioning manual. The service manual is not available yet.

1.3.2 Document revision historyDocument revision/date Product version HistoryA/2011-05-04 1.1 First release

B/2011-11-03 1.1.1 Content updated

Download the latest documents from the ABB Web sitehttp://www.abb.com/substationautomation.



HTTP://WWW.ABB.COM/SUBSTATIONAUTOMATION

1.3.3 Related documentationProduct-specific point list manuals and other product series- and product-specificmanuals can be downloaded from the ABB web site http://www.abb.com/substationautomation .

1.4 Symbols and conventions

1.4.1 Symbols

The caution icon indicates important information or warning relatedto the concept discussed in the text. It might indicate the presenceof a hazard which could result in corruption of software or damageto equipment or property.

The information icon alerts the reader of important facts andconditions.

The tip icon indicates advice on, for example, how to design yourproject or how to use a certain function.

Although warning hazards are related to personal injury, it is necessary tounderstand that under certain operational conditions, operation of damagedequipment may result in degraded process performance leading to personal injuryor death. Therefore, comply fully with all warning and caution notices.

1.4.2 Manual conventionsConventions used in IED manuals. A particular convention may not be used in thismanual.

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

• Push button navigation in the LHMI menu structure is presented by using thepush button icons.To navigate between the options, use and .

• HMI menu paths are presented in bold.Select Main menu/Settings.

• LHMI messages are shown in Courier font.To save the changes in non-volatile memory, select Yes and press .

• Parameter names are shown in italics.

Section 1 1MRS757260 BIntroduction


The function can be enabled and disabled with the Operation setting.• The ^ character in front of an input or output signal name in the function block

symbol given for a function, indicates that the user can set an own signal namein PCM600.

• The * character after an input or output signal name in the function blocksymbol given for a function, indicates that the signal must be connected toanother function block in the application configuration to achieve a validapplication configuration.

1.4.3 Functions, codes and symbolsTable 1: Functions included in PML630

Functionality IEC 61850Control

Double point indication DPGGIO1)

Monitoring

Station battery supervision SPVNZBAT1)

Generic measured values MVGGIO1)

Single point indication SPGGIO1)

Power management

Critical circuit breaker NCBDCSWI

Contingency based fast load shed LSCACLS

Sheddable load trip LSPTRC

Busbar with sheddable load LDMMXU

Network power source PWSMMXU

Subnetwork output SNWRCLS

Disturbance recorder function

Disturbance recorder DRRDRE1)

Analog channels 1-10 (samples) A1RADR1)

Analog channel 11-20 (samples) A2RADR1)

Analog channel 21-30 (samples) A3RADR

Analog channel 31-40 (calc. val.) A4RADR

Binary channel 1-16 B1RBDR

Binary channel 17-32 B2RBDR

Binary channel 33-48 B3RBDR1)

Binary channel 49-64 B4RBDR1)

1) The function is not used by default. However, it is kept enabled in the Application Configuration toolfor instantiation in any additional user defined logic other than the features offered by the IEDConnectivity Package.



8

Section 2 Introduction to IEC 61850

The IEC 61850 protocol standard for substation enables the integration of allprotection, control, measurement and monitoring functions by one commonprotocol. It provides the means of high-speed substation applications, station wideinterlocking and other functions including load shedding, busbar protection and soon that need intercommunication between IEDs. The well-described datamodelling, the specified communication services for the most recent tasks in astation makes the standard to a key element in modern substation systems.

This manual describes how the IEC 61850 standard is applied in PML630 IED.References and brief descriptions of the IEC 61850 standard are also included. It isassumed that the reader has basic knowledge about the IEC 61850.

To understand the IEC 61850 standard and to be able to find the relatedinformation, read the following information:

• Station Configuration description Language (SCL) is described in IEC61850-6. The SCL is an XML based definition of how to describe the parts ofa substation. This part of the standard also includes the roles of different toolsas well as the engineering concepts.

• Communication profile (IEC 61850 stack) is described in IEC 61850-8-1. Thispart of the standard includes a number of possible communication profiles andhow the services defined in IEC 61850-7-2 are mapped to the communicationprofile.

• Communication services are described in IEC 61850-7-2. This part dealsmainly with the communication facilities from client and server point of view.It includes the different possibilities of communication functionality.

• Logical node data model. This is described in IEC 61850-7-3 and IEC61850-7-4.

• Conformance tests and the basis for conformance documents are handled inIEC 61850-10.

To get information and an understanding about the implemented possibilities ofIEC 61850 in the IED, see the IEC 61850 conformance documents.

• MICS, Modeling Information Conformance Statement, contains thedeclaration of the used logical node types.

• PICS, Protocol Information Conformance Statement, contains the details andwhat is supported regarding protocol facilities.

• PIXIT, Protocol Extra Information, contains additional information on how theIEC 61850 is implemented and used.

• TICS, Tissue Information Conformance Statement, contains the supportedTissues, which are handled in the Tissues process as defined by UCA, Utility

1MRS757260 B Section 2Introduction to IEC 61850


Communication Architecture forum. The Tissues handling is found in http://www.tissue.iec61850.com. The TICS for the 630 Series version 1.1 is alsoapplicable for the IED (as it is based on 630 Series version 1.1) and, hence, aseparate TICS document is not made for the IED.

The conformance documents are unique for each product release and refer to eachother; the identities included in the related documents refer to a specific version ofthe IED.

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

The data modelling uses the concept of logical nodes to identify the publishedinformation for communication. The standard defines a set of logical nodes, eachrepresenting a communication view of a process function with a number of dataobjects. The standard cannot cover all possible information that is given, forexample, by a protection function of vendor A or vendor B or for the variants of aprotection function given by the process part which is protected. For example, atransformer differential - or line differential protection, because the standarddefines only a differential protection. Therefore, it is possible to adapt the logicalnode, which is defined in the standard, as a logical node class. The standard definesmethods to describe the actual used logical node as an logical node type which isthen based upon the logical node class. This allows all partners to interpret thelogical node type information because the description is completely given in thestandard. The type description of all logical nodes is part of the Data TypeTemplate (DTT) section in the SCL description file of a station or the IED.

Beside the information about the configuration of the communication facilities, thismanual contains the full description of all logical nodes available in the IED. Theinformation about the logical nodes and their data objects may be used to identifywhich signals are available for the function as described in the technical manual.The link to the technical manual is done in the logical node tables by listing thesignal name as given in the function block, as seen in PCM600 and in LHMI.

2.1.1 Related documentation to IEC 61850Use the latest revision of the documents listed, unless stated otherwise.

Document ID Title

IEC 61850-5First edition 2003-07Ref. number: IEC 61850-5:2003(E)

Communication networks and systems insubstations -Part 5:Communication requirements for functions anddevices models

IEC 61850-6First edition 2004-03Ref. number: IEC 61850-6: 2004(E)

Communication networks and systems insubstations -Part 6:Configuration description language forcommunication in electrical substations related toIEDs

Table continues on next page

Section 2 1MRS757260 BIntroduction to IEC 61850


IEC 61850-7-1First edition 2003-07Ref. number: IEC 61850-7-1: 2003(E)

Communication networks and systems insubstations -Part 7-1:Basic communication structure for substationsand feeder equipment -Principles and models


Communication networks and systems insubstations -Part 7-2:Basic communication structure for substationsand feeder equipment -Abstract communication service interface (ACSI)


Communication networks and systems insubstations -Part 7-3:Basic communication structure for substationsand feeder equipment -Common data classes


Communication networks and systems insubstations -Part 7-4:Basic communication structure for substationsand feeder equipment -Compatible logical node classes and data classes


Communication networks and systems insubstations -Part 8-1:Specific Communication Service Mapping(SCSM) - Mappings to MMS (ISO 9506-1 andISO 9506-2) and to ISO/IEC 8802-3

IEC 61850-10First edition 2005-05Ref. number: IEC 61850-10: 2005(E)

Communication networks and systems insubstations -Part 10:Conformance testing

IEC 61850 MICS 1MRS757324 IED version 1.1- IEC 61850 MICS:Modelling Implementation ConformanceStatement

IEC 61850 PICS 1MRS757325 IED version 1.1- IEC 61850 PICS:Protocol Implementation Conformance Statement

IEC 61850 PIXIT 1MRS757326 IED version 1.1- IEC 61850 PIXIT:Protocol Implementation Extra Information

IEC 61850 TICS 1MRS189728 IED version 1.1– IEC 61850 TICSTissue Implementation Conformance Statement

1MRS757260 B Section 2Introduction to IEC 61850


12

Section 3 Substation Configuration Language (SCL)

The SCL language is based on XML. However, detailed knowledge of the XMLcontents is not needed.

The SCL XML file (ied.ICD and/or station.SCD) contains five sections, which arespecified in IEC 61850–6 clause 9.

• Header• Substation section describes the functional structure and its relation to primary

devices.• Communication section describes the connection between the IED access

points to the respective subnetwork. and includes also the properties(addresses) of the access points.

• IED section contains a description of the supported communication services,the access point(s) and the IEDs logical devices, logical nodes and their attributes.

• Data type template section contains a declaration of all types used in the SCLfile, logical nodes type, DO types, attributes and enums.

The substation section and the communication section are tasks to organize theIEDs within the substation and to establish the communication. The systemstructure is defined by the organization of the plant structure in PCM600. Thesignal engineering and the signal routing are IET600 tasks. The IED needs to beconfigured with PCM600 before the system is configured with IET600.

The IED section contains the data sets and the control blocks configured byIET600. The data sets and the control blocks are logically defined as part of thelogical nodes (see IEC 61850–7–2 clause 9). IET600 also needs a correctlyconfigured communication section for GOOSE engineering.

The data type templates section provides the correct content description of eachlogical node type to all tools and users (clients) of the information. Each IED andvendor may have their own logical node type definitions included in the data typetemplate section together with all other logical node types based on the standard.

1MRS757260 B Section 3Substation Configuration Language (SCL)


IED(server)

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

Communication

AP

IED(server)


Communication

IED(server)


Communication

AP

IED(client)


Communication

IED(client)


Communication

Subnetwork

GUID-CC043293-BBB3-4B96-A000-EA6BEFC9C460 V1 EN

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

The arrows show the link between the different sections given when an IED isintegrated in the substation structure and/or in the communication structure. Allneeded logical nodes of an IED are linked to the substation section by the SC tool.

A reference to GOOSE Control Blocks (GoCB) is included in the communicationsection when GoCB is configured.

3.1 The Substation section

The Substation description in IEC 61850–6 clause 9 describes the organization ofthe primary equipment on one side. On the other side, it includes the used logicalnodes and their relation to the primary equipment.

3.2 The Communication section

The organization of the physical IEDs to the communication network isindependent of the substation structure. The IEC 61850 standard defines thecommunication network with no relation to an existing media and protocol. Themapping to an existing media and protocol is specified in IEC 61850–8–1.

The IEC 61850 standard describes in part 7–2 the ACSI in a media and protocolindependent form. Part 8–1 specifies the mapping of this ACSI to the existingMMS.

Section 3 1MRS757260 BSubstation Configuration Language (SCL)


The communication section describes how information is routed between the IEDsand contains the following parts:

• Subnetworks• IEDs connected to different subnetworks• Access points per IED to subnetworks• Address• IP address of LAN network (is exceptionally part of the address elements)• Link to GoCB message in transmission direction (extended during signal

engineering and routing)

IED(server)


Communication

AP

IED(server)


Communication

IED(server)


Communication

AP

IED(client)


Communication

IED(client)


Communication

Subnetwork

GUID-CC043293-BBB3-4B96-A000-EA6BEFC9C460 V1 EN

Figure 3: IEC 61850–6: Communication network

Additional information about the server is part of the IED.

3.3 The IED section

The IED section describes the complete IED as it is needed for IEC 61850communication and signal engineering. The data type template part of an IED maybe seen as part of the IED, even when separated in its own section. The IED's ICDfiles include the description of the logical nodes, their data type templates and theused or supported services. The structure of the IED section follows the definitionsmade 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 reador write information from or to the bay IEDs. This functionality is represented



by logical nodes of group “Information (I)”. These are the logical nodes (LN)= ITCI, IHMI and ITMI. Client IEDs are the receiver of information inmonitoring direction and sender of commands (control). These logical nodeshave no data objects. They are only used to link the report control blocks(BRCBs) from the server IEDs. They have to read their information about thesignals and the signal configuration from the bay IEDs. This is possible bychecking all control blocks for a link to it as a client.

• Bay level IEDsare located on the bay level and are identified as server IEDs when they reador write information vertically. When GOOSE messages are received, the baylevel IED also has the client role.

IED

SubnetworkAP -> S1

ServerLogical Device

LD0

LD_<n>

LS_<n>

SNW_<n>

LSC_1

PWS_1LSCLLN0

LPHD

LSCACLS

LSCCCLS1

LSCGAPC

LSCCCLS2

LSCCCLS3

LSCCCLS4

LSCRCLS

Logical Node

Mod

Beh

Health

NamPlt

Str

Op

Data Object

general

q

t

d

Data Attribute

GUID-76CB6EDD-208D-4F77-9EE6-6F3F9CA9D980 V1 EN

Figure 4: Organisation 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). Likeother ABB IEDs, even in the PML630, the data sets and the control blocksshall be located under LD0.



• The LN LPHD is a special logical node per LD and contains data objects thatdescribe the status 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 levelIEDs or to other bay IEDs that are communicating with GOOSE. The signalengineering task is to select the requested signals (DOs) and link them to the clientIEDs as receiver. The control services are not directly engineered. They areincluded in the data objects, which handle both directions the command (control)and the response (monitoring). When routing the DO in monitoring direction, thecontrol is also known by the clients.

The number of data objects and data attributes per DO is defined by the used LNtype in this IED. The content of logical node types and DO types are defined in theDTT. This also means that the definitions in the DTT section have to be uniquewith an SCD file.

3.4 Tool concept

The IEC 61850-6 defines a number of roles for tools. In the Relion® series,PCM600 is defined as IED tool, and IET600 is defined as system tool

The sections in SCL contain properties that are to be configured by these tools.There is no relation between one section and one specific tool. The task of the IEDtool is to configure all properties for the IED, while the system tool has the task todefine the place of the IED in the system and its communication dependencies. Forexample, the plant structure in PCM600 results in the subsystem section in SCLregarding the subsystem structure down to the IED level. The PCM600 alsoconfigures the IED section as a result of the IED configuration. In PCM600, theconfiguration properties for SCL are handled automatically as a result of theconfiguration, except for the receiving of GOOSE information that has adependency with the system tool.

Perform IEC 61850 engineering with PCM600 and IET600.

PCM600:



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

• The functionality of the IED is configured by using ACT in PCM600. For eachfunction, the corresponding logical device and logical node(s) is created in theIED section together with its type definition in data type template section.

• The above forms the IED capabilities from a communication perspective andwill then be included in the file exported from PCM600 as SCD, ICD or CIDfile.

IET600:

• Open a SCD file or import/merge a SCD, ICD or CID file for the particularIED(s).

• For each IED, the user defines the datasets, the control blocks for reporting(this means unbufffered/buffered reporting and GOOSE) and the properties foreach report control block.

• If client definitions (like client. ICD) are required in the system configuration,they are merged into IET600 and connected to the unbuffered/buffered reportcontrol blocks.

• For each IED, the primary/conducting equipment with their relation to theused logical nodes must be defined in the substation section.

• The resulting SCD file is exported from IET600.

PCM600:

Import the SCD file to PCM600 to receive GOOSE data. For each IED that shallreceive GOOSE information, the received data is connected to the applicationsusing SMT in PCM600.

3.5 Engineering concept in IEC 61850-6

• Top-down approach means that the system engineering tool has ICD filesavailable for each IED to be included in the system configuration. The ICDfiles may be of a template type and represent a pre-configured IED.

• Bottom-up approach means that the configurations are produced by the IEDtool, and are exported as ICD files (or SCD file) to be imported by system tools.



….IED A IED B IED Z

Client A Client B

IEDtool

Systemtool

GUID-ACC3CE26-A7F7-4B88-A6DD-9B5104A5A10F V1 EN

Figure 5: Relation between system and IED tools

Regardless of engineering approach, the idea is that the IED tool provides the CIDor ICD file for each IED. These ICD/CID files are then imported into the systemtool and merged into a SCD file, representing the complete substation or a part ofthe substation, like one for each voltage level.



20

Section 4 Communication profile

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 is been commonly used. The actual decisionis for

• 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 iscontained in part 7-2 of the standard. The mapping to the MMS for all aspects ofservices and Ethernet usage is specified in part 8-1 of IEC 61850.

Each device manufacturer, which is a partner of an IEC 61850 basedcommunication network, has to take these two specifications and adapt theirrespective product to the requirements and definitions given in the standard. Tomake this profile visible to all other partners, so they can check what they canexpect and what they have to support, the PICS document is defined. The PICScontains 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

AP

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

Subnetwork

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

Communication(MMS services part 8-1)

Communication( MMS servicespart 8-1)



GUID-5E41938B-BF64-4A80-8012-77DFF0D9D92D V1 EN

Figure 6: IEC 61850 Protocol: related standards for communication

1MRS757260 B 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-3GUID-8CA0E976-7104-4170-A92F-188D333E4C25 V1 EN

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

Out of this content, the implementation in the PML630 supports:

• GOOSE for peer to peer communication, based on IEEE802.1P (PriorityTagging) and VLAN technology

• TimeSync using SNTP• Vertical communication using MMS protocol suite with the T-profile TCP/IP

For each of the above, the resulting underlying protocols are as stated in figure4.

For more information, see the PICS and PIXIT.

Section 4 1MRS757260 BCommunication profile


Section 5 Supported services

IEC 61850-7-2 describes the services in the standard. IEC 61850-8-1 describeshow the services are applied in the communication. The conformance documentscontain the main description about the supported services in the IED.

Services that are not mentioned in this chapter or in the conformance document arenot supported.

Data setDefine data sets by the SCD description.

Create data sets under LD0/LLN0.

Report control blockFor properties about report control blocks, see PIXIT.

UnBuffered reporting as well as Buffered reporting is supported.

The relation between the parameters BufTm and IntPrd is BufTm <IntPrd. For best efficiency, the BufTm must have IntPrd as commondenominator, like n*BufTm = IntPrd, n is an arbitrary number.

Generic substation event (GOOSE)The structured GOOSE is supported. This means that the data sets can be definedwith FCDA as well as explicit attributes.

When explicit attributes are defined in the data sets, the number of such items in adata set is limited to 150.

The supported data types to be published and received using GOOSE includemeasurement, single point and double point status information together with theirquality. On reception of GOOSE message there is one valid signal available for theapplications. The valid signal represents all data in the received GOOSE telegram.Invalid means that the correct message is not received within the 1.8*maxTimeparameter for the GOOSE Control Block (as defined in IEC 61850-6). An incorrectmessage includes T=true, NeedsCom, wrong order of attributes or any discrepancyin the GOOSE message layout.

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

1MRS757260 B Section 5Supported services


ControlOf the different control sequences, the direct-with-normal-security and SBO-withenhanced security are supported (defined by the ctlModel parameter, IEC61850-7-2).

The command model can be changed for some functions by using PCM600 or PST.From communication perspective, in IEC61850 this parameter is read-only.

Check bits; interlock check and synchrocheck check, are only valid for LN typesbased upon CSWI class.

Verification of Originator Category is supported, see PIXIT.

Time and time synchronizationFor properties about time synchronization, see PIXIT and Time synchronizationdescription in the Technical manual and the Application engineering guide.

File transferSee PIXIT.

Section 5 1MRS757260 BSupported services


Section 6 Data sets and control blocks

Data setsIEC 61850 has defined Data sets and Report control blocks for signal transmissionin monitoring direction. Data sets are also used for GOOSE messages in horizontaldirection. Which data objects or single data attributes can be collected in a Data setis not specified and can be done to rules which may be defined in a project. Thefollowing figure shows a Data set where all position information of the apparatusesof a bay are put into one Data set.

The vendor of an IED can define Data sets as defaults which are part of the IEDand always available. They need to be linked to the client IEDs when more thanone client is configured. The user can delete, modify or add Data set during systemengineering.

LD0 LLN0

LD_<n>

LS_1

SNW_<n>

LSC_1

PWS_1

LSLLN0

LPHD

LSPTRC1

LSPTRC2

LSPTRC3

LSPTRC4

LSPTRC5

LSPTRC6

LSPTRC7

LSPTRC8

LSPTRC9

LSPTRC10

Tr

Tr

Tr

Tr

Tr

Tr

Tr

Tr

Tr

Tr

LD0/LLN0.GCB_SL1

LS_1/LSPTRC1.Tr, FC = ST






general

q

t

d

Data Set

LS_2

LS_3

LS_4

LS_5

LS_6

LD0/LLN0.GCB_SL2







Data Set

LD0/LLN0.GCB_SL3







Data Set

LD0/LLN0.GCB_SL4







LD0/LLN0.GCB_SL10







LD0/

LLN

0.G

CB

_SL5

LD0/

LLN

0.G

CB

_SL6

LD0/

LLN

0.G

CB

_SL7

LD0/

LLN

0.G

CB

_SL8

LD0/

LLN

0.G

CB

_SL9

Data Set Data Set

Data Sets

Data Sets

GUID-62C9029B-6DA8-4D40-9B54-28863BDB34B6 V1 EN

Figure 8: IEC 61850–7–2: Example of a Data set

General rules for Data set configuration:

1MRS757260 B Section 6Data sets and control blocks


• All data objects or their data attributes which are signals in monitoringdirection can be selected for a Data set.

• Items in a Data set is normally added by DO name + functional constraint.This means that all attributes within the DO with same functional constraintare included in the Dataset.

• 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 included in a Data set, thus defined with thecomplete attribute path. For example, the data attribute stVal of the data objectPos can be selected as a member of a Data set, because it is specified with thetrigger option data change detected (dchg).

The criteria for reporting is defined in the respective report controlblock. As the attributes have different trigger options, the mostfeasible configuration is to include attributes with same triggeroption, but it is also possible to define a number of reportingconditions for one report control block.

The description of the Data sets with name and the list of data object members(FCDAs = Functional Constraint Data Attributes) is included in the SCL file in theIED section in the Logical device subsection. As specified in IEC 61850–7–2clause 9, the Data sets are part of a Logical node. For the Relion series, the Datasets can be definded in LD0/LLN0.

6.1 Report control block (URCB/BRCB)

To be able to transmit the signals configured in a DataSet, a report control blockmust be configured to handle and specify how the events are transmitted to theclients. There are two types of report control blocks, unbuffered and buffered. Thebuffered report control block stores the events during a communication interrupt,while the unbuffered is sent upon data change and not stored during interruption.

The content of a BRCB is listed in IEC 61850-7-2 in clause 14. The BRCBcontains many attributes which are of interest to handle and secure thecommunication between the client and the server and may be set once as default ina project. Others are of application interest in the way events are handled in a project.

• Buffer time (valid only for BRCB)• This parameter describes how long the report must wait for other

expected events before it sends the report to the client. When it is knownthat additional events are generated as a follow up, it is useful to wait.For example, 500 ms for additional events stored in the report. Thisfeature reduces the number of telegrams transmitted in case of a burst ofchanges. But on the other side, it increases the overall transaction time

Section 6 1MRS757260 BData sets and control blocks


for events from IED input to presentation on HSI, which is normallydefined to be one second.

• Trigger options• The data attributes know three different trigger options (dchg, qchg,

dupd). Within the BRCB, the two other can be defined (integrity andgeneral interrogation). The attribute Trigger option is a multiple choiceand allows to mask the supported trigger options in this BRCB.

• Integrity period• When integrity is selected in the trigger option attribute, it is needed to

define an integrity period to force the transmission of all data listed inthe DataSet. This is done by the attribute Integrity period. This featurecan be used as a background cycle to ensure that the process image in allpartners is the same. Nobody is perfect and someone in the long chainfrom the contact up to the NCC may have lost an event. The backgroundcycle can repair it.

• General interrogation• A general interrogation is only done on request from a client. Not all

DataSets may contain information which is needed for a general updateof the client. For example, data with T(ransient) = TRUE are not part ofa GI. When the BRCB attribute general interrogation is set to TRUE, aGI request from the client is handled. The report handler transmits alldata defined in the Data-set with their actual values. The IEC 61850standard defines that all buffered events must be transmitted first beforethe GI is started. A running GI must be stopped and a new GI must bestarted, when a new GI 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. Thisfeature can be used to delete old events not transmitted to the client dueto stopped communication. After the link is reestablished the client candecide to clean the buffer or to receive the history.

Trigger OptionsIEC 61850 has defined in total five different TrgOp. Three of them belongs to dataattributes and marked per data attribute in the column TrgOp of the CDC tables inpart 7–3. The other two belongs to the configuration of control blocks.

• dchg = data-change• The most commonly used trigger. Whenever a process value has

changed its value either binary or a measurement a transmission is done.The standard does not define how to detect and inform the logical node.

• qchg = quality change



• Looking to the possibilities of the quality data attribute type (q) anychanges in the quality description is transmitted.

• dupd = data value update• This trigger option gives the possibility to define that a transmission

must be done on a condition which can be controlled by the application.• integrity

• This trigger forces the transmission of all process values defined in thedata set when a timer value (the integrity period) expires. It can be usedfor example to update a process signal in the background (for example,every 15 minutes).

• general interrogation• This trigger is forced by the clients (= station level IED; NCC gateway,

station HMI, ...). Normally a GI is asked for, when the client and theserver start or restart a session. When the client is able to receive theactual values and when the logical device has scanned all process valuesat least once, an image of the actual process signal status can betransmitted to the client.

Note that the possible trigger options for each attributeare included and defined in the datatype template sectionin SCL.

Link BRCB to a client LNThe BRCB has to know to whom the events shall be transmitted. This is the signalrouting engineering step. The IEC standard 61850–6 describes that this is given byincluding the LN of the client IED in the ReportBlockEnabled option.

The selected client IED with the corresponding LN, for example, ITCI is includedin the SCL structure of the Report Control description of the IED section.

The description of the BRCB with selected DataSet, configured parameters andselected IEDs is included in the SCL file in the IED section in the LN0 structurefor the LD where this LN0 belongs to.



.

IEDHSI

Client 1

IEDNCC GW 1

Client 2

IEDNCC GW m

Client 5

IED 1

Server 1

Subnetwork

ITCI2ITCI1IHSI1

LLN0 LD0/LLN0.StatUrg (for feeder status, priority and load shed inhibit status)

LD_1/MMXU1.InhLSSt, FC = ST

LD_1/MMXU1.LodPrioSt, FC = ST

LD_1/CSWI1.Pos, FC = ST




























GUID-228080DE-F70A-4E6C-AB08-F6ED10C320A3 V1 EN

Figure 9: Link BRCB to a client LN



6.2 GOOSE Control Blocks (GoCB)

Sen

d

Data-set

Rec

eive

Rec

eive

LNLN

LNLN

LN

Sen

d

Data-set

Rec

eive

Rec

eive

LNLN

LN LN

Sen

d

Data-setR

ecei

ve

Rec

eive

LN

LNLNLNLN

LN

Subnetwork

LN0

GoCB

DataSet

InputGoCBGoCB

DataSetDataSet

InputInput

Comm.GSE

LD1

Server

LN0

GoCB

DataSet

InputGoCBGoCB

DataSetDataSet

InputInput

Comm.GSE

LD1

Server

GUID-3AB50F10-A51C-4515-A936-74661339FC81 V1 EN

Figure 10: IEC 61850: Principle operation of GOOSE messages

The Generic object oriented substation event (GOOSE) class model is used todistribute input and output data values between IEDs on bay level (in horizontaldirection) through the use of multicast services. GOOSE messages bypass theserver and enable fast transmission from a publisher to one or several subscribers(receivers).

GOOSE messages are unidirectional, send only messages which request anapplication specific method to secure that the sender and the receiver of themessage operate safely. This implies that the receiver of the GOOSE messagedistributes also GOOSE messages and closes the loop for communication (request— respond on application level). The return message is not a must. It depends onthe application in which way a confirmation may be done.



The GOOSE service model of IEC 61850-7-2 provides the possibility for fast andreliable system-wide distribution of input and output data values. Thisimplementation uses a specific scheme of re-transmission to achieve theappropriate level of reliability. When a GOOSE server generates aSendGOOSEMessage request, the current data set values are encoded in a GOOSEmessage and transmitted on the multicast association. The event that causes theserver to invoke a SendGOOSE service is a local application issue as defined inIEC 61850-7-2. Each update may generate a message in order to minimizethroughput time.

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

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

eventGUID-2B4B6A9D-16F6-4D8A-804D-D964E57B580A V1 EN

Figure 11: Transmission time for events

Each message in the retransmission sequence carries a timeAllowedToLiveparameter that informs the receiver of the maximum time to wait for the next re-transmission. If a new message is not received within that time interval, thereceiver assumes that the association is lost. The specific intervals used by anyGOOSE publisher are a local issue. The timeAllowedToLive parameter informssubscribers of how long to wait. In series, (to which PML630 belongs to,), thedetection time is 1.8*timeAllowedToLive to cope with possible transmission delays.

The GOOSE message concept is used for all application functions where two ormore IEDs are involved. Typical example is the station-wide interlockingprocedure or breaker failure protection.

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



To send GOOSE messages a GoCB must be defined and a data set is needed thatcontains the data objects of single data attributes to be send.

A GOOSE message is forced to be transmitted when a trigger change is detectedfor a data attribute. All members of the data set are copied in the send buffer withtheir actual value and the message is sent. The subscribers, who knows the addressof this GOOSE message, receives the telegram. The GOOSE message includes forexample sequence number to verify that all messages are received.

The concept that has to be done in case of for example a lost message is part of theapplication and not described in the standard.

A GoCB has to be defined per GOOSE-DataSet.

GOOSE messages bypass the server and send direct from the communication parton the Ethernet. This is identified for the communication in the SCLcommunication section in the GSE element, where the name of the GoCB is listedunder the ConnectedAP.

Link GoCB to an IEDThe IEDs that should receive the GOOSE message must be known and they haveto be informed in the engineering state that they receive GOOSE messages andwhich one. This is given when the external Reference, the name of the IED and themember of the data set is included in the LN0 under the structure of the LD of thereceiving IED. This part is identified as Inputs.



Section 7 Logical node data model

7.1 Common data objects in each logical node

The IEC 61850 standard describes in part 7-4, a Common Logical Node. The dataobjects contained in that LN are both mandatory and optional. The mandatory dataobjects have to be included in each LN. This clause describes the general handlingof the data objects within the series products.

The mandatory data objects as defined in IEC 61850-7-4 as part of the CommonLogical Node are Mode, Behavior, Health and NamePlate.

Mode

The operation modes ON (enabled) and BLOCKED are supported remotely by acommand or locally from the LHMI of the IED. The TEST and the TEST/BLOCKED mode can be operated locally from the LHMI or by using PCM600.

The state OFF can be set from the LHMI or by using PCM600 for the functionshaving the setting 'operation'.

Note also that for functions in other Logical devices than LD0, the Mod can onlybe controlled by communication on LLN0.

Behaviour

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

The Beh shows the actual state of the function, dependent upon the hierarchydescribed in IEC 61850-7-4, clause 6.

Health

The series products show always only the state "green" = Ok.

NamePlt

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

1MRS757260 B Section 7Logical node data model


7.2 Logical nodes for control

7.2.1 IEC61850 generic communication I/O functions DPGGIO

LN type LN prefix LN class Function block name

DPGGIO (revision 1) DP GGIO DPGGIO

Table 2: DPGGIO Logical node data (instance 0)

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

Description

Mod a_dINC Oper.ctlVal CO - - Cmd Mode parameter

Oper.origin.orCat CO - - Cmd Mode parameter

Oper.origin.orIdent CO - - Cmd Mode parameter

Oper.ctlNum CO - - Cmd Mode parameter

Oper.T CO - - Cmd Mode parameter

Oper.Test CO - - Cmd Mode parameter

Oper.Check CO - - Cmd Mode parameter

stVal ST - - Mon Mode status parameter for 61850

q ST - - Mon Mode status parameter for 61850

t ST - - Mon Mode status parameter for 61850

Beh a_dINS stVal ST - Beh Mon Behaviour parameter for 61850

q ST - Beh Mon Behaviour parameter for 61850

t ST - Beh Mon Behaviour parameter for 61850

DPCSO b_dDPC stVal ST - POSITION Mon Double point indication

q ST - POSITION Mon Double point indication

t ST - POSITION Mon Double point indication

7.3 Logical node for monitoring

7.3.1 Station battery supervision SPVNZBAT


SPVNZBAT (revision 0) SPVN ZBAT SPVNZBAT

Section 7 1MRS757260 BLogical node data model


Table 3: SPVNZBAT Logical node data


Description

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

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

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

Oper.ctlNum CO - - Cmd Mode parameter for 61850

Oper.T CO - - Cmd Mode parameter for 61850

Oper.Test CO - - Cmd Mode parameter for 61850

Oper.Check CO - - Cmd Mode parameter for 61850







BatHi a_dSPS stVal ST - ST_UHIGH Mon Start signal when battery voltageexceeds upper limit

q ST - ST_UHIGH Mon Start signal when battery voltageexceeds upper limit

t ST - ST_UHIGH Mon Start signal when battery voltageexceeds upper limit

BatLo a_dSPS stVal ST - ST_ULOW Mon Start signal when battery voltagedrops below lower limit

q ST - ST_ULOW Mon Start signal when battery voltagedrops below lower limit

t ST - ST_ULOW Mon Start signal when battery voltagedrops below lower limit

Vol b_dMV mag.f MX - U_BATT Mon Service value of the batteryterminal voltage

q MX - U_BATT Mon Service value of the batteryterminal voltage

t MX - U_BATT Mon Service value of the batteryterminal voltage

OpBatLo v1_dSPS stVal ST - AL_ULOW Mon Alarm when voltage has beenbelow lower limit for a set time

q ST - AL_ULOW Mon Alarm when voltage has beenbelow lower limit for a set time

t ST - AL_ULOW Mon Alarm when voltage has beenbelow lower limit for a set time

OpBatHi v1_dSPS stVal ST - AL_UHIGH Mon Alarm when voltage hasexceeded higher limit for a set time

q ST - AL_UHIGH Mon Alarm when voltage hasexceeded higher limit for a set time

t ST - AL_UHIGH Mon Alarm when voltage hasexceeded higher limit for a set time



7.3.2 IEC61850 generic communication I/O functions MVGGIO


MVGGIO (revision 1) MV GGIO MVGGIO

Table 4: MVGGIO Logical node data


Description











AnIn a_dMV rangeC.hhLim.f CF - MV hhLim - High High limit

rangeC.hLim.f CF - MV hLim - High limit

rangeC.lLim.f CF - MV lLim - Low limit

rangeC.llLim.f CF - MV llLim - Low Low limit

rangeC.max.f CF - MV max - Maximum value

rangeC.min.f CF - MV min - Minimum value

mag.f MX - VALUE Mon Magnitude of deadband value

subMag.f SV - - - Substituted value

range MX - RANGE Mon Range

q MX - VALUE Mon Magnitude of deadband value

t MX - VALUE Mon Magnitude of deadband 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% ofrange

7.3.3 IEC61850 generic communication I/O functions SPGGIO


SPGGIO (revision 1) SP GGIO SPGGIO



Table 5: SPGGIO Logical node data (instance 0)


Description














Ind c_dSPS stVal ST - OUT Mon Output status

q ST - OUT Mon Output status

t ST - OUT Mon Output status

7.4 Logical node for power management

7.4.1 Input interface function for network circuit breaker dataNCBDCSWI


NCBDCSWI instance 1 (revision 0) NCBD CSWI NCBDCSWI

NCBDLLN0 instance 1 (revision 0) - LLN0 NCBDCSWI

NCBDMMXU instance 1 (revision 0) NCBD MMXU NCBDCSWI

Table 6: NCBDCSWI Logical node data (instance 1)


Description




Pos b_dDPC stVal ST - CB_POS_IND Mon Critical circuit breaker positionsignal indication

q ST - CB_POS_IND Mon Critical circuit breaker positionsignal indication





Description

Pos b_dDPC t ST - CB_POS_IND Mon Critical circuit breaker positionsignal indication

Mod c_dINC stVal ST - - Mon Mode status value parameter for61850

q ST - - Mon Mode status value parameter for61850

t ST - - Mon Mode status value parameter for61850

Table 7: NCBDLLN0 Logical node data (instance 1)


Description








stVal ST - - Mon Mode status value parameter for61850






Table 8: NCBDMMXU Logical node data (instance 1)


Description











Description

TotW c_dMV mag.f MX - CRIT_CB_POW Mon Critical circuit breaker activepower

q MX - CRIT_CB_POW Mon Critical circuit breaker activepower

t MX - CRIT_CB_POW Mon Critical circuit breaker activepower

7.4.2 Contingency based fast load shed function LSCACLS


LSCACLS instance 1 (revision 0) LSC ACLS LSCACLS

LSCCCLS instance 1 (revision 0) LSC CCLS LSCACLS




LSCGAPC instance 1 (revision 0) LSC GAPC LSCACLS

LSCLLN0 instance 1 (revision 0) - LLN0 LSCACLS

LSCRCLS instance 1 (revision 0) LSC RCLS LSCACLS

Table 9: LSCACLS Logical node data (instance 1)


Description




Op b_dACT general ST T FLS_OPR Mon Load shed operate due to autofast load shedding

q ST T FLS_OPR Mon Load shed operate due to autofast load shedding

t ST T FLS_OPR Mon Load shed operate due to autofast load shedding




Str f_dACD general ST - FLS_START Mon Signal indicating fastloadshedstarted

q ST - FLS_START Mon Signal indicating fastloadshedstarted

t ST - FLS_START Mon Signal indicating fastloadshedstarted





Description

SNtw1Rs v4_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850

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

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

Oper.ctlNum CO - - Cmd Command parameter forIEC61850

Oper.T CO - - Cmd Command parameter forIEC61850

Oper.Test CO - - Cmd Command parameter forIEC61850

Oper.Check CO - - Cmd Command parameter forIEC61850






















Description

SNtw4Rs v4_dSPC Oper.ctlNum CO - - Cmd Command parameter forIEC61850




Rs v4_dSPC Oper.ctlVal CO T - Cmd Command parameter forIEC61850

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

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

Oper.ctlNum CO T - Cmd Command parameter forIEC61850

Oper.T CO T - Cmd Command parameter forIEC61850

Oper.Test CO T - Cmd Command parameter forIEC61850

Oper.Check CO T - Cmd Command parameter forIEC61850

OpCntRs v4_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850







Table 10: LSCCCLS Logical node data (instance 1)


Description









Description

Mod c_dINC q ST - - Mon Mode status value parameter for61850


ManLSCmd v4_dSPC Oper.ctlVal CO - - Cmd Command parameter forIEC61850









Description


















Description
















Description















Description

ManLSCmd v4_dSPC Oper.T CO - - Cmd Command parameter forIEC61850



Table 14: LSCGAPC Logical node data (instance 1)


Description




Op b_dACT general ST T LS_OPR Mon Loadshed oparate due tofastloadshed or slowloadshed

q ST T LS_OPR Mon Loadshed oparate due tofastloadshed or slowloadshed

t ST T LS_OPR Mon Loadshed oparate due tofastloadshed or slowloadshed




Str f_dACD general ST - LS_START Mon Signal indicating loadshed started

q ST - LS_START Mon Signal indicating loadshed started

t ST - LS_START Mon Signal indicating loadshed started

Table 15: LSCLLN0 Logical node data (instance 1)


Description














Description

Mod a_dINC t ST - - Mon Mode status value parameter for61850




Table 16: LSCRCLS Logical node data (instance 1)


Description







SNtwGen1 v1_dINS stVal ST - PS3_SN_NO Mon Sub network number ofpowersource3

q ST - PS3_SN_NO Mon Sub network number ofpowersource3

t ST - PS3_SN_NO Mon Sub network number ofpowersource3
















Description

SNtwGen5 v1_dINS t ST - PS7_SN_NO Mon Sub network number ofpowersource7




SNtwGri1 v1_dINS stVal ST - PS1_SN_NO Mon Sub network number ofpowersource1



SNtwGri2 v1_dINS stVal ST - PS2_SN_NO Mon Sub network number ofpowersource2



SNtwLBB1 v1_dINS stVal ST - BB1_SN_NO Mon Sub network number ofloadbusbar1

q ST - BB1_SN_NO Mon Sub network number ofloadbusbar1

t ST - BB1_SN_NO Mon Sub network number ofloadbusbar1
















Description

SNtwLBB5 v1_dINS t ST - BB5_SN_NO Mon Sub network number ofloadbusbar5




SNtwCB1 v1_dINS stVal ST - CB1_SN_NO Mon Sub network number of criticalbreaker1

q ST - CB1_SN_NO Mon Sub network number of criticalbreaker1

t ST - CB1_SN_NO Mon Sub network number of criticalbreaker1






















Description

SNtwCB15 v1_dINS t ST - CB15_SN_NO Mon Sub network number of criticalbreaker15




























Description

SNtwCB9 v1_dINS t ST - CB9_SN_NO Mon Sub network number of criticalbreaker9

FLSCnt v1_dINS stVal ST - FLS_CNT Mon Counter indicating number of flstriggers generated

q ST - FLS_CNT Mon Counter indicating number of flstriggers generated

t ST - FLS_CNT Mon Counter indicating number of flstriggers generated

SNtw1Act v1_dSPS stVal ST - ACTIVE_SN1 Mon Sub network1 is active

q ST - ACTIVE_SN1 Mon Sub network1 is active

t ST - ACTIVE_SN1 Mon Sub network1 is active










7.4.3 Sheddable load trip command LSPTRC


LSLLN0 instance 1 (revision 0) - LLN0 LSPTRC

LSPTRC instance 1 (revision 0) LS PTRC LSPTRC












Table 17: LSLLN0 Logical node data (instance 1)


Description














Table 18: LSPTRC Logical node data (instance 1)


Description




Tr c_dACT general ST - OPR_SL1 Mon Operate command for thesheddable load1

q ST - OPR_SL1 Mon Operate command for thesheddable load1

t ST - OPR_SL1 Mon Operate command for thesheddable load1








Description












Description












Description








Description









Description












Description











Description






Description












Description














Description












Description










7.4.4 Input interface function for sheddable load data LDMMXU


LDCSWI instance 1 (revision 1) LD CSWI LDMMXU












LDLLN0 instance 1 (revision 0) - LLN0 LDMMXU

LDMMXU instance 1 (revision 1) LD MMXU LDMMXU










Table 28: LDCSWI Logical node data (instance 1)


Description




Pos b_dDPC stVal ST - CBPOSIND_L1 Mon CB compensted signal indicationposition for Load1

q ST - CBPOSIND_L1 Mon CB compensted signal indicationposition for Load1

t ST - CBPOSIND_L1 Mon CB compensted signal indicationposition for Load1






Description








Description









Description












Description











Description






Description












Description














Description












Description












Description








Description









Description










Table 38: LDLLN0 Logical node data (instance 1)


Description













Description

Mod a_dINC q ST - - Mon Mode status value parameter for61850





Table 39: LDMMXU Logical node data (instance 1)


Description







TotW c_dMV mag.f MX - P_SHED_L1 Mon Delayed active power on thesheddable load1

q MX - P_SHED_L1 Mon Delayed active power on thesheddable load1

t MX - P_SHED_L1 Mon Delayed active power on thesheddable load1

LodPrioSt v1_dINS stVal ST - PRIO_SHD_L1 Mon Sheddable load1 priority fordisplay in COM 600

q ST - PRIO_SHD_L1 Mon Sheddable load1 priority fordisplay in COM 600

t ST - PRIO_SHD_L1 Mon Sheddable load1 priority fordisplay in COM 600

InhLSSt v1_dINS stVal ST - INBT_STS_L1 Mon Sheddable load1 inhibit status forload shedding

q ST - INBT_STS_L1 Mon Sheddable load1 inhibit status forload shedding

t ST - INBT_STS_L1 Mon Sheddable load1 inhibit status forload shedding





Description


















Description













Description

TotW c_dMV t MX - P_SHED_L2 Mon Delayed active power on thesheddable load2









Description




















Description


















Description













Description










Description




















Description













InhLSSt v1_dINS stVal ST - INBT_STS_L10 Mon Sheddable load10 inhibit statusfor load shedding

q ST - INBT_STS_L10 Mon Sheddable load10 inhibit statusfor load shedding

t ST - INBT_STS_L10 Mon Sheddable load10 inhibit statusfor load shedding



Description













Description










Description


















7.4.5 Input interface function for network power source dataPWSMMXU


PWSACLS instance 1 (revision 0) PWS ACLS PWSMMXU

PWSACLS instance 2 (revision 0) PWS ACLS PWSMMXU

PWSGCSWI instance 1 (revision 0) PWSG CSWI PWSMMXU






PWSGMMXU instance 1 (revision 0) PWSG MMXU PWSMMXU






PWSLLN0 instance 1 (revision 0) - LLN0 PWSMMXU

PWSTCSWI instance 1 (revision 0) PWST CSWI PWSMMXU

PWSTCSWI instance 2 (revision 0) PWST CSWI PWSMMXU

PWSTMMXU instance 1 (revision 2) PWST MMXU PWSMMXU

PWSTMMXU instance 2 (revision 2) PWST MMXU PWSMMXU

Table 49: PWSACLS Logical node data (instance 1)


Description

Op b_dACT general ST T SLS_OP_GRD1 Mon Latched output indicating slowload trigger for grid 1

q ST T SLS_OP_GRD1 Mon Latched output indicating slowload trigger for grid 1

t ST T SLS_OP_GRD1 Mon Latched output indicating slowload trigger for grid 1

Str f_dACD general ST - SLOW_ST_GRD1 Mon Slow load shedding start in gridtransformer 1

q ST - SLOW_ST_GRD1 Mon Slow load shedding start in gridtransformer 1

t ST - SLOW_ST_GRD1 Mon Slow load shedding start in gridtransformer 1

MaxDmdTm v1_dINS stVal ST - T_INT_GRD1 Mon time interval for demand valuecalc of grid transformer 1

q ST - T_INT_GRD1 Mon time interval for demand valuecalc of grid transformer 1





Description

MaxDmdTm v1_dINS t ST - T_INT_GRD1 Mon time interval for demand valuecalc of grid transformer 1

MaxDmdExc v1_dSPS stVal ST - MD_OPR_GRD1 Mon Max demand operated for grid 1

q ST - MD_OPR_GRD1 Mon Max demand operated for grid 1

t ST - MD_OPR_GRD1 Mon Max demand operated for grid 1

TrfOvLod v1_dSPS stVal ST - OLS_OPR_GRD1 Mon Over load shed operated for gridtransformer 1

q ST - OLS_OPR_GRD1 Mon Over load shed operated for gridtransformer 1

t ST - OLS_OPR_GRD1 Mon Over load shed operated for gridtransformer 1

MaxDmdSEn v1_dSPS stVal ST - EN_MAXD_GRD1 Mon Maximum demand sheddingenabled grid1

q ST - EN_MAXD_GRD1 Mon Maximum demand sheddingenabled grid1

t ST - EN_MAXD_GRD1 Mon Maximum demand sheddingenabled grid1

SlwLSEn v1_dSPS stVal ST - SLS_EN_GRD1 Mon Enable signal for slow load triggerfor grid transformer 1

q ST - SLS_EN_GRD1 Mon Enable signal for slow load triggerfor grid transformer 1

t ST - SLS_EN_GRD1 Mon Enable signal for slow load triggerfor grid transformer 1

MaxCurTrf v2_dMV mag.f MX - MAX_I_GRD1 Mon Maximum current of grid1

q MX - MAX_I_GRD1 Mon Maximum current of grid1

t MX - MAX_I_GRD1 Mon Maximum current of grid1

MaxDmdS v2_dMV mag.f MX - MAX_DEM_GRD1 Mon Maximum power demand for grid1

q MX - MAX_DEM_GRD1 Mon Maximum power demand for grid1

t MX - MAX_DEM_GRD1 Mon Maximum power demand for grid1

TmElaTrf v2_dMV mag.f MX - ETIME_GRD1 Mon Elapsed time after overloadtrigger start up from grid 1

q MX - ETIME_GRD1 Mon Elapsed time after overloadtrigger start up from grid 1

t MX - ETIME_GRD1 Mon Elapsed time after overloadtrigger start up from grid 1

TmIDMTTrf v2_dMV mag.f MX - IDMTIME_GRD1 Mon Total time after which Slow loadtrigger will be generated from grid1

q MX - IDMTIME_GRD1 Mon Total time after which Slow loadtrigger will be generated from grid1

t MX - IDMTIME_GRD1 Mon Total time after which Slow loadtrigger will be generated from grid1





Description





Oper.T CO T - Cmd Command parameter forIEC61850



Table 50: PWSACLS Logical node data (instance 2)


Description

Op b_dACT general ST T SLS_OP_GRD2 Mon Latched output indicating slowload trigger for grid 2

q ST T SLS_OP_GRD2 Mon Latched output indicating slowload trigger for grid 2

t ST T SLS_OP_GRD2 Mon Latched output indicating slowload trigger for grid 2

Str f_dACD general ST - SLOW_ST_GRD2 Mon Slow load shedding start in gridtransformer 2

q ST - SLOW_ST_GRD2 Mon Slow load shedding start in gridtransformer 2

t ST - SLOW_ST_GRD2 Mon Slow load shedding start in gridtransformer 2

MaxDmdTm v1_dINS stVal ST - T_INT_GRD2 Mon time interval for demand valuecalc of grid transformer 2

q ST - T_INT_GRD2 Mon time interval for demand valuecalc of grid transformer 2

t ST - T_INT_GRD2 Mon time interval for demand valuecalc of grid transformer 2

MaxDmdExc v1_dSPS stVal ST - MD_OPR_GRD2 Mon Max demand operated for grid 1

q ST - MD_OPR_GRD2 Mon Max demand operated for grid 1

t ST - MD_OPR_GRD2 Mon Max demand operated for grid 1

TrfOvLod v1_dSPS stVal ST - OLS_OPR_GRD2 Mon Over load shed operated for gridtransformer 2

q ST - OLS_OPR_GRD2 Mon Over load shed operated for gridtransformer 2

t ST - OLS_OPR_GRD2 Mon Over load shed operated for gridtransformer 2





Description

MaxDmdSEn v1_dSPS stVal ST - EN_MAXD_GRD2 Mon Maximum demand sheddingenabled grid2

q ST - EN_MAXD_GRD2 Mon Maximum demand sheddingenabled grid2

t ST - EN_MAXD_GRD2 Mon Maximum demand sheddingenabled grid2

SlwLSEn v1_dSPS stVal ST - SLS_EN_GRD2 Mon Enable signal for slow load triggerfor grid transformer 2

q ST - SLS_EN_GRD2 Mon Enable signal for slow load triggerfor grid transformer 2

t ST - SLS_EN_GRD2 Mon Enable signal for slow load triggerfor grid transformer 2

MaxCurTrf v2_dMV mag.f MX - MAX_I_GRD2 Mon Maximum current of grid2

q MX - MAX_I_GRD2 Mon Maximum current of grid2

t MX - MAX_I_GRD2 Mon Maximum current of grid2

MaxDmdS v2_dMV mag.f MX - MAX_DEM_GRD2 Mon Maximum power demand for grid2

q MX - MAX_DEM_GRD2 Mon Maximum power demand for grid2

t MX - MAX_DEM_GRD2 Mon Maximum power demand for grid2

TmElaTrf v2_dMV mag.f MX - ETIME_GRD2 Mon Elapsed time after overloadtrigger start up from grid 2

q MX - ETIME_GRD2 Mon Elapsed time after overloadtrigger start up from grid 2

t MX - ETIME_GRD2 Mon Elapsed time after overloadtrigger start up from grid 2

TmIDMTTrf v2_dMV mag.f MX - IDMTIME_GRD2 Mon Total time after which Slow loadtrigger will be generated from grid2

q MX - IDMTIME_GRD2 Mon Total time after which Slow loadtrigger will be generated from grid2

t MX - IDMTIME_GRD2 Mon Total time after which Slow loadtrigger will be generated from grid2









Description

Rs v4_dSPC Oper.T CO T - Cmd Command parameter forIEC61850



Table 51: PWSGCSWI Logical node data (instance 2)


Description




Pos b_dDPC stVal ST - CB_IND_GEN2 Mon Position indication of the CBconnecting generator2 to thesystem

q ST - CB_IND_GEN2 Mon Position indication of the CBconnecting generator2 to thesystem

t ST - CB_IND_GEN2 Mon Position indication of the CBconnecting generator2 to thesystem






Description











Description






Description












Description











Description






Description












Description











Description




Table 57: PWSGMMXU Logical node data (instance 6)


Description

TotW c_dMV mag.f MX - ACTPOW_GEN6 Mon Active Power on generator 6

q MX - ACTPOW_GEN6 Mon Active Power on generator 6

t MX - ACTPOW_GEN6 Mon Active Power on generator 6

GovMod v1_dINS stVal ST - GOV_MOD_GEN6 Mon Generator 6 governor mode

q ST - GOV_MOD_GEN6 Mon Generator 6 governor mode

t ST - GOV_MOD_GEN6 Mon Generator 6 governor mode

AvaW v2_dMV mag.f MX - AVA_POW_GEN6 Mon Available power from Generator 6

q MX - AVA_POW_GEN6 Mon Available power from Generator 6

t MX - AVA_POW_GEN6 Mon Available power from Generator 6



Description












Description








Description









Description












Description














Description










Table 63: PWSLLN0 Logical node data (instance 1)


Description














Table 64: PWSTCSWI Logical node data (instance 1)


Description




Pos b_dDPC stVal ST - CB_IND_GRD1 Mon Position indication of the CBconnecting grid transformer 1 tothe system





Description

Pos b_dDPC q ST - CB_IND_GRD1 Mon Position indication of the CBconnecting grid transformer 1 tothe system

t ST - CB_IND_GRD1 Mon Position indication of the CBconnecting grid transformer 1 tothe system




Table 65: PWSTCSWI Logical node data (instance 2)


Description




Pos b_dDPC stVal ST - CB_IND_GRD2 Mon Position indication of the CBconnecting grid transformer 2 tothe system

q ST - CB_IND_GRD2 Mon Position indication of the CBconnecting grid transformer 2 tothe system

t ST - CB_IND_GRD2 Mon Position indication of the CBconnecting grid transformer 2 tothe system




Table 66: PWSTMMXU Logical node data (instance 2)


Description




TotW c_dMV mag.f MX - ACTPOW_GRD2 Mon Active power on grid transformer 1

q MX - ACTPOW_GRD2 Mon Active power on grid transformer 1





Description

TotW c_dMV t MX - ACTPOW_GRD2 Mon Active power on grid transformer 1

SlwLSBlk v1_dSPS stVal ST - SLS_BLK_GRD2 Mon Slow load shed trigger block forgrid 2

q ST - SLS_BLK_GRD2 Mon Slow load shed trigger block forgrid 2

t ST - SLS_BLK_GRD2 Mon Slow load shed trigger block forgrid 2

AvaW v2_dMV mag.f MX - AVA_POW_GRD2 Mon Available power from gridtransformer 2

q MX - AVA_POW_GRD2 Mon Available power from gridtransformer 2

t MX - AVA_POW_GRD2 Mon Available power from gridtransformer 2

GriAMax v2_dMV mag.f MX - ST_IMAX_GRD2 Mon Setting above which over loadshed is initiated in grid2

q MX - ST_IMAX_GRD2 Mon Setting above which over loadshed is initiated in grid2

t MX - ST_IMAX_GRD2 Mon Setting above which over loadshed is initiated in grid2

Table 67: PWSTMMXU Logical node data (instance 1)


Description




TotW c_dMV mag.f MX - ACTPOW_GRD1 Mon Active power on grid transformer 1

q MX - ACTPOW_GRD1 Mon Active power on grid transformer 1

t MX - ACTPOW_GRD1 Mon Active power on grid transformer 1

SlwLSBlk v1_dSPS stVal ST - SLS_BLK_GRD1 Mon Slow load shed trigger block forgrid 1

q ST - SLS_BLK_GRD1 Mon Slow load shed trigger block forgrid 1

t ST - SLS_BLK_GRD1 Mon Slow load shed trigger block forgrid 1

AvaW v2_dMV mag.f MX - AVA_POW_GRD1 Mon Available power from gridtransformer 1

q MX - AVA_POW_GRD1 Mon Available power from gridtransformer 1

t MX - AVA_POW_GRD1 Mon Available power from gridtransformer 1





Description

GriAMax v2_dMV mag.f MX - ST_IMAX_GRD1 Mon Setting above which over loadshed is initiated in grid1

q MX - ST_IMAX_GRD1 Mon Setting above which over loadshed is initiated in grid1

t MX - ST_IMAX_GRD1 Mon Setting above which over loadshed is initiated in grid1

7.4.6 Output interface function for sub network data SNWRCLS


SNWARCLS instance 1 (revision 0) SNWA RCLS SNWRCLS

SNWLLN0 instance 1 (revision 0) - LLN0 SNWRCLS

SNWLRCLS instance 1 (revision 0) SNWL RCLS SNWRCLS

Table 68: SNWARCLS Logical node data (instance 1)


Description







PrioSt v1_dINS stVal ST - MAN_SHD_PRIO Mon Manual load shed Priority

q ST - MAN_SHD_PRIO Mon Manual load shed Priority

t ST - MAN_SHD_PRIO Mon Manual load shed Priority

ALodPrio1 v2_dMV mag.f MX - CUM_LOD_PR1 Mon Cumulative load priority 1

q MX - CUM_LOD_PR1 Mon Cumulative load priority 1

t MX - CUM_LOD_PR1 Mon Cumulative load priority 1













Description

ALodPrio12 v2_dMV t MX - CUM_LOD_PR12 Mon Cumulative load priority 12











































Description

ALodPrio7 v2_dMV t MX - CUM_LOD_PR7 Mon Cumulative load priority 7







Table 69: SNWLLN0 Logical node data (instance 1)


Description














Table 70: SNWLRCLS Logical node data (instance 1)


Description







NtwLSPrio v1_dINS stVal ST - SN_SHED_PRIO Mon subnetwork shed priority





Description

NtwLSPrio v1_dINS q ST - SN_SHED_PRIO Mon subnetwork shed priority

t ST - SN_SHED_PRIO Mon subnetwork shed priority

LSOpSt v1_dINS stVal ST - LS_OPR_STS Mon Load shed operator status

q ST - LS_OPR_STS Mon Load shed operator status

t ST - LS_OPR_STS Mon Load shed operator status

LSBlkSt v1_dSPS stVal ST - SN_FLS_BLK Mon Fast Load shed block

q ST - SN_FLS_BLK Mon Fast Load shed block

t ST - SN_FLS_BLK Mon Fast Load shed block

NtwSt v1_dSPS stVal ST - LS_MOD_INFO Mon Load shed enable and active

q ST - LS_MOD_INFO Mon Load shed enable and active

t ST - LS_MOD_INFO Mon Load shed enable and active

SlwLSBlkSt v1_dSPS stVal ST - SLOW_LS_BLK Mon Slow Load shed block

q ST - SLOW_LS_BLK Mon Slow Load shed block

t ST - SLOW_LS_BLK Mon Slow Load shed block

NtwLoad v2_dMV mag.f MX - SN_LOAD Mon Total load in the subnetwork

q MX - SN_LOAD Mon Total load in the subnetwork

t MX - SN_LOAD Mon Total load in the subnetwork

NtwLodInhM v2_dMV mag.f MX - LOD_INBT_OPR Mon Total inhibited Power by theoperator in the subnetwork

q MX - LOD_INBT_OPR Mon Total inhibited Power by theoperator in the subnetwork

t MX - LOD_INBT_OPR Mon Total inhibited Power by theoperator in the subnetwork

NtwLodInhS v2_dMV mag.f MX - LOD_INBT_SYS Mon Total inhibited Power by thesystem in the subnetwork

q MX - LOD_INBT_SYS Mon Total inhibited Power by thesystem in the subnetwork

t MX - LOD_INBT_SYS Mon Total inhibited Power by thesystem in the subnetwork

NtwLodMm v2_dMV mag.f MX - LOD_MISMATCH Mon Total load mismatch in thesubnetwork

q MX - LOD_MISMATCH Mon Total load mismatch in thesubnetwork

t MX - LOD_MISMATCH Mon Total load mismatch in thesubnetwork

NtwALodShd v2_dMV mag.f MX - ACTU_SHD Mon Actual Load shed

q MX - ACTU_SHD Mon Actual Load shed

t MX - ACTU_SHD Mon Actual Load shed

NtwMLodShd v2_dMV mag.f MX - MUST_SHD Mon Must be load shed

q MX - MUST_SHD Mon Must be load shed

t MX - MUST_SHD Mon Must be load shed





Description

NtwPwrBal v2_dMV mag.f MX - LOD_IMBAL Mon Load generation balance at thetime of previous load shed prioritycalculation

q MX - LOD_IMBAL Mon Load generation balance at thetime of previous load shed prioritycalculation

t MX - LOD_IMBAL Mon Load generation balance at thetime of previous load shed prioritycalculation

NtwPwrDiff v2_dMV mag.f MX - DIF_MUSTACTU Mon Difference between the must beload shed and actual load shed

q MX - DIF_MUSTACTU Mon Difference between the must beload shed and actual load shed

t MX - DIF_MUSTACTU Mon Difference between the must beload shed and actual load shed

NtwShbLod v2_dMV mag.f MX - SN_TOT_SL Mon Total amount of sheddable loadin sub network

q MX - SN_TOT_SL Mon Total amount of sheddable loadin sub network

t MX - SN_TOT_SL Mon Total amount of sheddable loadin sub network

NtwAvbPwr v2_dMV mag.f MX - SN_AVA_POW Mon Total Available power in thesubnetwork

q MX - SN_AVA_POW Mon Total Available power in thesubnetwork

t MX - SN_AVA_POW Mon Total Available power in thesubnetwork

7.5 Logical node for disturbance recorder function

7.5.1 Disturbance report DRRDRE


DRRDRE (revision 0) DR RDRE DRRDRE

Table 71: DRRDRE Logical node data


Description










Description

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








FltNum b_dINS stVal ST - Fault number Mon Disturbance fault number

q ST - Fault number Mon Disturbance fault number

t ST - Fault number Mon Disturbance fault number

MemUsed b_dINS stVal ST - Memory used Mon Memory usage (0-100%)

q ST - Memory used Mon Memory usage (0-100%)

t ST - Memory used Mon Memory usage (0-100%)

RcdMade d_dSPS stVal ST - RECMADE Mon Disturbance recording made

q ST - RECMADE Mon Disturbance recording made

t ST - RECMADE Mon Disturbance recording made

RcdStr d_dSPS stVal ST - RECSTART Mon Disturbance recording started

q ST - RECSTART Mon Disturbance recording started

t ST - RECSTART Mon Disturbance recording started

RcdClr v2_dSPS stVal ST - CLEARED Mon All disturbances in thedisturbance report cleared

q ST - CLEARED Mon All disturbances in thedisturbance report cleared

t ST - CLEARED Mon All disturbances in thedisturbance report cleared

MemUsedAlm v2_dSPS stVal ST - MEMUSED Mon More than 80% of memory used

q ST - MEMUSED Mon More than 80% of memory used

t ST - MEMUSED Mon More than 80% of memory used

7.6 Load shedding power management function blocks

The table Function block and logical device instances describes the relationshipbetween the load shedding power management function blocks and the logicaldevices in the IEC 61850 structure. Also mentioned are the maximum number ofpossible instances of the function blocks, which depend on the power networkconfiguration. These function blocks are automatically instantiated in the ACT ofPCM600 by the IED Connectivity package (Configuration Wizard feature).



Table 72: Function block and logical device instances

Function block name Maximum number ofinstances

Associated logicaldevice and instancenumber

Description

NCBDCSWI 15 NCBD_<instancenumber, based onnetwork circuit breakerindex>

For network circuitbreaker index number,see ApplicationEngineering Guide

LSCACLS 1 LSC_1 -

LSPTRC 6 LS_<1..6> Instance numberdepends on number ofload busbars

LDMMXU 6 LD_<1..6> Instance numberdepends on number ofload busbars

PWSMMXU 1 PWS_1 One instance for allpower sources

SNWRCLS 4 SNW_<1..4> Instance numberdepends on maximumnumber ofsubnetworks (numberof busbars with powersources)



86

Section 8 Glossary

ACSI Abstract communication service interfaceBeh BehaviorBRCB Report control blockCID Configured IED descriptionDA Data attributeDO Data objectEMC Electromagnetic compatibilityEthernet A standard for connecting a family of frame-based

computer networking technologies into a LANFCDA Functional constraint data attributeGI General interrogationGoCB GOOSE control blockGOOSE Generic Object-Oriented Substation EventGSE Generic substation eventHMI Human-machine interfaceICD IED capability descriptionIEC International Electrotechnical CommissionIEC 61850 International standard for substation communication and

modelingIEC 61850-8-1 A communication protocol based on the IEC 61850

standard seriesIED Intelligent electronic deviceIET600 Integrated Engineering Toolbox in PCM600IP address A set of four numbers between 0 and 255, separated by

periods. Each server connected to the Internet is assigneda unique IP address that specifies the location for the TCP/IP protocol.

ISO International Standard OrganizationLAN Local area networkLD Logical deviceLD0 Logical device zero (0)LHMI Local human-machine interface

1MRS757260 B Section 8Glossary


LLN0 Logical node zero (0)LN Logical nodeLogical device Also known as LD. Representation of a group of functions.

Each function is defined as a logical node. A physicaldevice has one or several LDs.

MICS Model implementation conformance statementMMS Manufacturing message specification; Metering

management systemNCC Network control centerPCM600 Protection and Control IED ManagerPICS Protocol implementation conformance statementPIXIT Protocol implementation extra information for testingSAB600 Substation automation builder toolSC Single commandSCD Substation configuration descriptionSCL XML-based substation description configuration language

defined by IEC 61850SMT Signal Matrix tool in PCM600SNTP Simple Network Time ProtocolTCP/IP Transmission Control Protocol/Internet ProtocolXML Extensible markup language

Section 8 1MRS757260 BGlossary


89

Contact us

ABB OyDistribution AutomationP.O. Box 699FI-65101 VAASA, FinlandPhone +358 10 22 11Fax +358 10 22 41094

www.abb.com/substationautomation

1MR

S75

7260

B©

Cop

yrig

ht 2

011

AB

B. A

ll rig

hts

rese

rved

.

Documents

Load Shedding Controller PML630 IEC 61850 Communication ... fileRelion® 630 series Load Shedding Controller PML630 IEC 61850 Communication Protocol Manual