Relion Protection and Control. 611 series IEC Engineering Guide

Transcription

1 Relion Protection and Control 611 series IEC 61850

2

3 Document ID: 1MRS Issued: Revision: B Product version: 2.0 Copyright 2016 ABB. All rights reserved

4 Copyright This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party, nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. Trademarks ABB and Relion are registered trademarks of the ABB Group. All other brand or product names mentioned in this document may be trademarks or registered trademarks of their respective holders. Warranty Please inquire about the terms of warranty from your nearest ABB representative.

5 Disclaimer The data, examples and diagrams in this manual are included solely for the concept or product description and are not to be deemed as a statement of guaranteed properties. All persons responsible for applying the equipment addressed in this manual must satisfy themselves that each intended application is suitable and acceptable, including that any applicable safety or other operational requirements are complied with. In particular, any risks in applications where a system failure and/or product failure would create a risk for harm to property or persons (including but not limited to personal injuries or death) shall be the sole responsibility of the person or entity applying the equipment, and those so responsible are hereby requested to ensure that all measures are taken to exclude or mitigate such risks. This product has been designed to be connected and communicate data and information via a network interface which should be connected to a secure network. It is the sole responsibility of the person or entity responsible for network administration to ensure a secure connection to the network and to take the necessary measures (such as, but not limited to, installation of firewalls, application of authentication measures, encryption of data, installation of anti virus programs, etc.) to protect the product and the network, its system and interface included, against any kind of security breaches, unauthorized access, interference, intrusion, leakage and/or theft of data or information. ABB is not liable for any such damages and/or losses. This document has been carefully checked by ABB but deviations cannot be completely ruled out. In case any errors are detected, the reader is kindly requested to notify the manufacturer. Other than under explicit contractual commitments, in no event shall ABB be responsible or liable for any loss or damage resulting from the use of this manual or the application of the equipment.

6 Conformity This product complies with the directive of the Council of the European Communities on the approximation of the laws of the Member States relating to electromagnetic compatibility (EMC Directive 2004/108/EC) and concerning electrical equipment for use within specified voltage limits (Low-voltage directive 2006/95/EC). This conformity is the result of tests conducted by ABB in accordance with the product standard EN for the EMC directive, and with the product standards EN and EN for the low voltage directive. The product is designed in accordance with the international standards of the IEC series.

7 Safety information Dangerous voltages can occur on the connectors, even though the auxiliary voltage has been disconnected. Non-observance can result in death, personal injury or substantial property damage. Only a competent electrician is allowed to carry out the electrical installation. National and local electrical safety regulations must always be followed. The frame of the protection relay has to be carefully earthed. When the plug-in unit has been detached from the case, do not touch the inside of the case. The relay case internals may contain high voltage potential and touching these may cause personal injury. The protection relay contains components which are sensitive to electrostatic discharge. Unnecessary touching of electronic components must therefore be avoided. Whenever changes are made in the protection relay, measures should be taken to avoid inadvertent tripping.

8

9 Table of contents Table of contents Section 1 Introduction...5 This manual... 5 Intended audience... 5 Product documentation...6 Product documentation set...6 Document revision history... 6 Related documentation...7 Symbols and conventions...7 Symbols...7 Document conventions...7 Section 2 IEC overview... 9 Section 3 Section 4 PCM600 tool...13 Connectivity packages...14 PCM600 and relay connectivity package version series data model...15 Product series implementation Information model...15 Vertical and horizontal communication...18 Predefined vertical communication data sets...19 Predefined horizontal communication data set...20 Vertical communication diagnostic counters Parameter setting and disturbance recorder Section 5 GOOSE Horizontal communication Configuring horizontal communication GOOSE publishing properties Configuring GOOSE with the IEC Configuration tool Defining IEDs and starting the IEC Configuration tool...25 Configuring a GOOSE publisher with the IEC Configuration tool Creating a GOOSE data set with the IEC Configuration tool Configuring a GOOSE control block with the IEC Configuration tool Configuring a GOOSE subscriber with the IEC Configuration tool series 1

10 Table of contents Configuring GOOSE inputs with the IEC Configuration tool Configuring GOOSE with IET Defining devices and exporting the SCD file for IET Creating an empty project with IET Importing the SCD file into IET Configuring a GOOSE publisher with IET Creating a GOOSE data set with IET Configuring a GOOSE control block with IET Configuring a GOOSE subscriber with IET Configuring GOOSE inputs with IET Finalizing GOOSE configuration with IET Exporting the SCL file...50 Importing the SCL file...51 Connecting GOOSE inputs to an IED application Received GOOSE message handling GOOSE supervision Background sending...55 Default value handling...56 Alarm supervision in application...56 Diagnostic counters...57 Section 6 Section 7 IEEE 1588 time synchronization and communication redundancy...61 System building High-availability seamless redundancy HSR...61 Parallel redundancy protocol PRP...62 Bay level configuration IEEE 1588 v2 parameters and status information...64 Power profile parameters Engineering verification Engineering of event reporting with PCM Managing IEC clients with the IEC Configuration tool 69 Adding new IEC clients for the IEC Configuration tool IEC Configuration tool user interface...73 Creating data sets with the IEC Configuration tool...75 Defining data set entries with the IEC Configuration tool. 76 Creating report control blocks with the IEC Configuration tool...78 Configuring RCB clients with the IEC Configuration tool Substation section configuration in the IEC Configuration tool series

11 Table of contents Section 8 Engineering of event reporting with IET Managing IEC clients with IET Adding new IEC clients for IET Attaching IEC clients to a bus with IET IET600 user interface Setting visibility of columns in grid editors...88 Substation section configuration in IET Creating data sets with IET Creating report control blocks with IET RCB client configuration with IET Configuring RCB clients semi-automatically...93 Section 9 Glossary series 3

12 4

13 1MRS B Section 1 Introduction Section 1 Introduction 1.1 This manual The engineering guide provides information for IEC engineering of the protection relays with PCM600 and IET600. The guide can be used as a technical reference during the engineering phase, installation and commissioning phase, and during normal service. For more details on tool usage, see the PCM600 documentation. 1.2 Intended audience This manual addresses the system engineers and installation and commissioning personnel. The system engineer must have a thorough knowledge of protection systems, protection equipment, protection functions and the configured functional logic in the protection relays. The installation and commissioning personnel must have basic knowledge of how to handle the electronic equipment. 611 series 5

14 Section 1 Introduction 1MRS B 1.3 Product documentation Product documentation set Planning & purchase Engineering Installation Commissioning Operation Maintenance Decommissioning, deinstallation & disposal Quick start guide Quick installation guide Brochure Product guide Operation manual Installation manual Connection diagram Engineering manual Technical manual Application manual Communication protocol manual IEC engineering guide Point list manual Cyber security deployment guideline GUID-0777AFDA-CADF-4AA9-946E-F6A856BDF75E V1 EN Figure 1: The intended use of manuals in different lifecycles Product series- and product-specific manuals can be downloaded from the ABB Web site Document revision history Document revision/date Product series version History A/ First release B/ Content updated to correspond to the product series version Download the latest documents from the ABB Web site series

15 1MRS B Section 1 Introduction Related documentation Name of the document IEC Tissues Conformance Statement (TICS) IEC Protocol Implementation extra Information (PIXIT) IEC Protocol Implementation Conformance Statement (PICS) IEC Model Implementation Conformance Statement (MICS) Document ID 1MRS MRS MRS MRS Product series- and product-specific manuals can be downloaded from the ABB Web site Symbols and conventions Symbols The caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could 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 or how to use a certain function. Although warning hazards are related to personal injury, it is necessary to understand that under certain operational conditions, operation of damaged equipment may result in degraded process performance leading to personal injury or death. Therefore, comply fully with all warning and caution notices Document conventions A particular convention may not be used in this manual. Abbreviations and acronyms are spelled out in the glossary. The glossary also contains definitions of important terms. Push button navigation in the LHMI menu structure is presented by using the push button icons. 611 series 7

16 Section 1 Introduction 1MRS B To navigate between the options, use and. Menu paths are presented in bold. Select Main menu/settings. LHMI messages are shown in Courier font. To save the changes in nonvolatile memory, select Yes and press. Parameter names are shown in italics. The function can be enabled and disabled with the Operation setting. Parameter values are indicated with quotation marks. The corresponding parameter values are "On" and "Off". Input/output messages and monitored data names are shown in Courier font. When the function starts, the START output is set to TRUE. This document assumes that the parameter setting visibility is "Advanced" series

17 1MRS B Section 2 IEC overview Section 2 IEC overview The international IEC standard defines a framework for substation communications networks and systems. The standard consists of several parts ranging from the requirements on substation automation systems to the details of a communication protocol. Its main goal is interoperability; the ability for IEDs from one or different manufacturers to exchange information and use the information for their own functions. IEC standard for communication networks and systems in substations has been out since 2005 and used successfully in ABB products. IEC standard is updated with a new version, Edition 2. Edition 2 extends to new application areas in transmission and distribution power systems and also defines a new functionality to Edition 1 functionality. This product series supports both versions of IEC 61850, Edition 1 and Edition 2. Edition 2 is a new version of IEC standard and it adds new functionality which is not supported by the Edition 1 devices. Therefore it is recommended to always use the same standard version in all devices and not to mix different versions in the same project. A major difference between the other communication protocols applied in substation automation and IEC is that the latter is not only a communication protocol, but a whole framework for specifying, engineering and operating substation automation systems. The communication part covers the connection between the IEDs and the substation clients, for example, SCADA and gateways. 611 series 9

18 Section 2 IEC overview 1MRS B GUID-43179FBC-BDC BC-81A0F886F785 V1 EN Figure 2: Structure and parts of the IEC standard The IEC standard specifies an expandable object-oriented data model and wide set of protocol services for substation automation (standard parts 7-x). The standard does not specify any protection or control functions, but specifies how the functions expose their information to a communication network. The standard supports free allocation of functions to devices. With efficient communication facilities, the functions can be located anywhere in the system, that is, an interlocking function can reside in the IED or on the station level. Additionally, the standard is open for different system implementations, that is, different integration levels and allocation of functions to different devices is supported. The standard also defines an XML description language for substation automation systems. The language facilitates efficient integration of devices into systems in an automated fashion. Additionally the standard supports a comprehensive and consistent system definition and engineering, which makes not only the devices, but also their tools and systems interoperable (standard part 6). The standard uses Ethernet and TCP/IP for communication. Since Ethernet and TCP/ IP are widely accepted and used, the application of these technologies provide a broad range of features from mainstream communication (standard parts 8-1, 9-2).Communication profiles in IEC can be divided to vertical and horizontal. The vertical profile uses MMS over TCP/IP and vertical communication Layer 2 Ethernet multicast messages. The standard separates the functionality represented by the data model and the related communication services from the communication implementation thus being open for possible new communication concepts in the future series

19 1MRS B Section 2 IEC overview Data model (objects, sevices) 1 Client server communication GOOSE Mapping Sampled values 2 3 MMS TCP IP Ethernet link layer Real-time communication Ethernet physical layer with priority tagging (100 Mbit/s) GUID-A9FD AD-4B03-935E-BF39D48B7211 V1 EN Figure 3: Communication stacks and mapping used in IEC Abstract communication services interface (ACSI) 2 Stack interface 3 ISO/OSI stack 611 series 11

20 12

21 1MRS B Section 3 PCM600 tool Section 3 PCM600 tool Protection and Control IED Manager PCM600 offers all the necessary functionality to work throughout all stages of the protection relay life cycle. Planning Engineering Commissioning Operation and disturbance handling Functional analysis The whole substation can be controlled and different tasks and functions can be performed with the individual tool components. PCM600 can operate with many different topologies, depending on the customer needs. PCM600 is used to conduct complete engineering and configuration activities needed for the bay level protection relays. Connectivity Packages are separate software packages that provide type and version information to PCM600. Further Connectivity Packages assist the tool with communications. PCM600 uses IEC over Ethernet to communicate with bay devices. This communication allows PCM600 to configure and monitor the devices. In addition to IEC the devices have optional communications protocols and hardware to connect to station engineering tools. PCM600 provides the ability to export the configuration of the devices or an entire substation in a standard file format which enables station engineering in separate IEC System Configuration tools. A PC with PCM600 can be connected to any 611 series IED within a station by using the Ethernet connection. The connection can also be used for service and maintenance purposes. In addition, the connection is used to handle disturbance records from the protection relays. The modern-day protection relays are designed using the concept of the IEC standard. This is primarily in regards to how functions within the protection relay are modelled and how the protection relay is represented in the substation. See the IEC parameter list for the list of logical nodes available in the protection relay and observe how they follow the structure and rules as defined in part 7 of the standard. The engineering of the used communication protocols is a separate task and an addition to the engineering of protection and control functions. PCM600 can be used for different purposes throughout the protection relay life cycle. A set of special tools is available for different applications. 611 series 13

22 Section 3 PCM600 tool 1MRS B The applications can be organized into groups. Relay engineering Communication engineering Record management Device monitoring and diagnostic For more information, see PCM600 documentation. 3.1 Connectivity packages A connectivity package is a software component that consists of executable code and data which enables system tools to communicate with a protection relay. Connectivity packages are used to create configuration structures in PCM600. The latest PCM600 and connectivity packages are backward compatible with older protection relay versions. A connectivity package includes all of the data which is used to describe the protection relay, for example, it contains a list of the existing parameters, data format used, units, setting range, access rights and visibility of the parameter. In addition, it contains code which allows software packages that consume the connectivity package to properly communicate with the protection relay. It also allows for localization of text even when its read from the protection relay in a standard format such as COMTRADE. Update Manager is a tool that helps in defining the right connectivity package versions for different system products and tools. Update Manager is included with products that use connectivity packages. 3.2 PCM600 and relay connectivity package version Protection and Control IED Manager PCM600 Ver.2.7 or later REB611 Connectivity Package Ver.2.0 or later REF611 Connectivity Package Ver.2.0 or later REM611 Connectivity Package Ver.2.0 or later REU611 Connectivity Package Ver.2.0 or later Download connectivity packages from the ABB Web site or directly with the Update Manager in PCM series

23 1MRS B Section series data model Section series data model 4.1 Product series implementation The protection relays have been fully designed according to IEC This means that the functionality of the protection relay is represented in a data model in accordance with the standard and the protection relays support a wide range of the services provided by the standard. Process data: monitoring of statuses and measurements Application data: protection activation, tripping, fault recordings Disturbance records Control commands Protection settings Settings and setting groups Configuration data Diagnostics and self-supervision Fast horizontal communication between devices Time synchronization File transfer As this series of relays supports both versions of IEC 61850, Edition 1 and Edition 2, there are small differences with IEC data model depending of the used version. Generally the relay s protection and control functionality is independent of the IEC version used. Any differences between data model versions are documented. If the protection relay is ordered with no Ethernet communication interface, the front port on the device still works according to IEC All settings and configurations are changed with IEC services using PCM600 via the front Ethernet port of the LHMI. Without the rear Ethernet option, station communication is not available. 4.2 Information model The protection relay is fully modelled according to the IEC standard. The data model can include up to four logical devices where different logical nodes representing protection and control functionality are located. Depending of the selected functionality in the protection relay, different configurations have different set of logical devices and logical nodes. Data models also include full modelling and functionality of setting, setting groups and configuration according to the IEC concept. 611 series 15

24 Section series data model 1MRS B Control logical device, CTRL Disturbance recorder logical device, DR Protection logical device, LD0 All generic functionality, such as modelling of physical inputs and outputs as well as the alarming LED functionality, resides under logical device LD0. A full description of the protection relay's data model is available in the parameter list. During system engineering in the system configuration tool, do not delete or rename logical devices, logical nodes, data objects or data attributes in the IEC data model series

25 1MRS B Section series data model GUID-6DE80EB ED1-8ADF-489C01ED01C1 V1 EN Figure 4: Example of an IEC data model of a protection relay In the IEC standard, communication services are configured through a number of data structures including data sets, report control blocks, GOOSE control blocks and setting group control blocks. As these data structures pertain to the entire logical device, the standard indicates that they are to be modeled under LLN0, which is a special logical node that describes the common functionality of the logical device. All these data structures are located in logical device LD0 logical node LLN0. The full data model can be exported from PCM600 in the form of a SCL file, which is defined in part 6 of the standard. 611 series 17

26 Section series data model 1MRS B 4.3 Vertical and horizontal communication The protection relays are capable of vertical communication between the protection relay and monitoring and control systems (clients) such as PCM600 or MicroSCADA. Each protection relay can communicate to five separate clients to receive events, read or write data (an active PCM600 connection is considered to be a client). The protection relay can report data in either buffered or unbuffered mode and execute direct or select-before-operate control sequences according to the control commands sent by the client. The protection relays are also capable of horizontal or peer-to-peer communication. They can be programmed to publish (send) information to and subscribe (receive) information from other devices according to the IEC IEC standard Edition 2 increased several identification string lengths which affect communication engineering and interoperability. The table lists identification length values to be considered especially with third party tools. ABB tools generally check the length values. Table 1: Identification lengths in IEC versions Object Edition 1 length Edition 2 length Description IED name 28 (32-4) 60 (64-4) Excluding the longest LD name length of 4 characters Report control block name Without a two digit RCB instance number Data set name RptID Report Identifier GoID GOOSE Identifier Table 2: Number of control block data sets and size of data sets Control Block Maximum data sets Maximum length Description GoCB 4 80 data attributes The protection relays allow a maximum of four GOOSE control blocks, which effectively limits the protection relay to four data sets for GOOSE. The sending GOOSE data sets can have a maximum total of 80 data attributes. To minimize the messagehandling load in the receiving and sending protection relays, it is recommended to limit data attribute amount to 20 per data set. RCB 10 Edition 1: 256 data attributes Edition 2: 80 data objects The IEC configuration tool (IET600 or PCM600) allows a maximum of 10 data sets for the report control blocks series

27 1MRS B Section series data model Predefined vertical communication data sets In vertical communications, the protection relay can generate events that are automatically reported to any listening clients. These communications are configured via a series of predefined data sets and corresponding report control blocks. The data sets are used to configure what data is sent and the report control block is used to configure when data is sent. The relay connectivity package includes predefined data sets and control blocks for vertical MMS event reporting. These data sets are used in predefined reporting control blocks for five clients. The selected data in the data sets is suitable to most of the different applications and the selected default data automatically considers the used protection relay type and options. The data sets and report control blocks can be modified using the IEC Configuration tool or IET600, however, this should only be done by individuals that are extremely familiar with both the protection relays and IEC Inappropriate modifications can result in misoperation of the protection relay. StatIed generic status information of IEDs StatIo inputs, outputs, LEDs StatUrg measurement limit supervision, control feedback StatNrml protection start and trip signals, autoreclosing status StatDR digital fault recorder status MeasReg registered measurement values at faults MeasFlt measurements When function blocks are added to or removed from a relay configuration also the default data sets and the content of data sets are automatically modified to follow the IED data model. If all data does not fit into one data set, two data sets with suffixes "A" and "B" are created. The protection relays support both buffered and unbuffered event reporting. In the predefined configuration all report control blocks are configured to use buffered reporting. The benefit of buffered reporting is that it buffers events during communication breaks and thus no events are lost. Further, a single data set can only be used by one report control block and the same data set entry cannot be used in different event reporting data sets. The default values for the data sets and control blocks are suitable for most applications. The protection relay allows free renaming and editing of report control blocks and data sets. Only users who have an in-depth understanding of the protection relay and IEC should modify the default configuration. Description of data in default data sets is available in the parameter list. Vertical communication protocols, such as Modbus, rely on the data sets for event generation. Modification of the default configuration have an impact on vertical communication. 611 series 19

28 Section series data model 1MRS B It is not recommended to mix seldom updated status data (FC=ST) and frequently updated measurement data (FC=MX) in the same data set to minimize the bandwidth consumption in the network and to avoid unnecessary publishing of unchanged status data. A 611 series protection relay can have at maximum 14 configured data sets and 10 report control blocks for event handling. The maximum length for a data set is 256 data attributes. The amount of data attributes within a data object varies, however, a 611 series protection relay can have 1500 data attributes in data sets in total. The protection relay does not support defining data on data attribute level for data sets used for vertical reporting. Only data object level is allowed Predefined horizontal communication data set In horizontal communication the user normally has to engineer IEC GOOSE data sets Vertical communication diagnostic counters The IEC data model of the IEDs includes a logical node LD0.MMSLPRT1 for IEC vertical communication diagnostic. The counters are available via the HMI or PCM600 path Monitoring/Communication/MMSLPRT1. Table 3: Diagnostic data objects Data object Description Diagnostic information SucConnCnt Successful connections Number of succeeded client connection attempts FailConnCnt Failed connections Number of failed client connection attempts ConcCnt Concludes Number of session concludes TxAbtCnt Sent aborts Number of association aborts sent by server RxAbtCnt Received aborts Number of received association aborts by server TxRejCnt Sent rejects Number of sent rejects by server RxRqCnt Received request Number of received client requests FailRqCnt Failed requests Number of failed client requests SucReadCnt Reads Number of variable reads FailReadCnt Failed reads Number of failed variable reads SucWrCnt Writes Number of succeeded variable writes Table continues on next page series

29 1MRS B Section series data model Data object Description Diagnostic information FailWrCnt Failed writes Number of failed variable writes InfRepCnt Reports Number of sent reports ActConnCnt Active connections Number of active client connections It is possible to reset the vertical diagnostics counters via Monitoring/ Communication/MMSLPRT1/Reset counters and via the IEC communication by writing TRUE to the RsCnt.Oper.ctlVal attribute under MMSLPRT1. GOOSE communication has its own diagnostic counters. See the Diagnostic counters chapter in this manual for information on diagnostic counters used in GOOSE communication. 4.4 Parameter setting and disturbance recorder The relay's protection function settings and parameters can be set and the active setting groups changed by IEC client using the standard IEC services. The disturbance recorder and load profile files in COMTRADE format are retrieved from the \COMTRADE\ and \LPD\COMTRADE\ directories by using PCM600 or any other client supporting IEC file transfer service or FTP. When setting the parameter Configuration/Communication/MMSLPRT1/Unit mode to Primary, the values sent over IEC are scaled according to the CT and VT settings. Restart the protection relay after changing the parameter. This feature is needed if the SCADA system or substation gateway does not handle scaling from nominal values. 611 series 21

30 22

31 1MRS B Section 5 GOOSE Section 5 GOOSE 5.1 Horizontal communication GOOSE is used in substation automation for fast horizontal communication between the protection relays. GOOSE can be used for direct data exchange, for example, of interlocking and blocking information between protection relays. According to the IEC standard, GOOSE uses a publisher/subscriber profile in which information is shared from one device to one or several devices by using Ethernet multicast messages. A message is an image of a sent IEC data set that is defined in the configuration. The protection relay can send any type of status or measurement data in the GOOSE messages from its IEC data model. The status data response time, that is, the time it takes for the application to handle a received GOOSE message and to send the concerned data back to the network, is below 3 ms. The response time fulfils the tightest Type 1A, Class P2/3 requirements of the standard. When the protection relay is configured to send measurements, the analog, integer or counter type data should be placed in its own data set to minimize the bandwidth consumption in the network and to avoid unnecessary publishing of unchanged status data. The triggering of analog data sending is controlled by deadband handling, zeropoint clamping and limit supervision. The horizontal communication configuration consists of the protection relays' GOOSE control block, data set and GOOSE input configuration. The result of the configuration work is a system configuration which is used for the protection relays. The used files in the workflow are IEC standard format SCL files Configuring horizontal communication Configure GOOSE by using the IEC Configuration tool in PCM600 or by using the separate IET600 tool. PCM600 interacts with IET600 by importing and exporting SCL files. 5.2 GOOSE publishing properties GOOSE data is transmitted event based and at regular intervals in 802.1Q multicast frames over the LAN. Peer devices can determine the state of the communications by listening for the transmissions. When the data values change, the data is transmitted at 611 series 23

32 Section 5 GOOSE 1MRS B an increased frequency to ensure the timeliness of its reception. The transmission then gradually tapers off to the original frequency with the new data. In GOOSE, data sending is based on data sets and GOOSE control blocks. The data set defines what device data is used in GOOSE service and sent to local Ethernet subnetwork in a GOOSE message. The GOOSE control block links the data set and its attributes to actual data. Table 4: GOOSE control block attributes GoCB attribute Multicast address Ethernet frame-specific information (802.1 Q tagging info: APPID, priority and VLAN id) GoCB name GoID Data set definition ConfRev Description A multicast addressing scheme is used when sending GOOSE messages. A multicast address can be shared by several sending devices, or it can be device specific. To keep the multicast message filtering of the devices working it is recommended to use unique multicast addresses. APPID is a GoCB-specific integer value identifying the sender GoCB and its data. The APPID must be unique for the GoCB in the system. The priority can be used according to the local network priority scheme, but normally the default value is sufficient. The VLAN group can be used when configuring the Ethernet network topology Virtual LANs for routing and filtering multicast messages. Configuration is done in managed Ethernet switches. The name of the GoCB structure seen from the IEC 61850/MMS client. Some devices use this as a unique data reference. A GOOSE control block specific string. The default value is the GoCB path in the namespace if nothing is set. It is recommended to always set a unique value in tool. Check the GOOSE Control block GoID name according to the system requirements of the receiving device. Although the protection relays use MAC address and APPID for receiving packet detection, some devices require additionally that the GOOSE control block GoID is named explicitly. Data sent in GOOSE messages to the network. ConfRev increases when the referenced data set is modified. Both the GOOSE sender and the receiver must have the same ConfRev value. This ensures that the both devices have the same configuration level in the substation configuration. ConfRev usage is done automatically by tools. If the latest system configuration is not downloaded to all required devices, the configuration revision may differ between the receiver and sender and data exchange does not work. 5.3 Configuring GOOSE with the IEC Configuration tool See detailed descriptions of the steps in corresponding chapters. 1. Add devices to a PCM600 project. 2. Engineer the GOOSE connections between the devices series

33 1MRS B Section 5 GOOSE 2.1. Define the published GOOSE data and control blocks Define the subscribing IEDs for the GOOSE data. 3. Engineer the IED applications with GOOSE inputs Defining IEDs and starting the IEC Configuration tool Use PCM600 to define the substation and the IEDs. Before starting the system engineering, configure the IED settings and logic in PCM600. For more information, see PCM600 documentation. 1. Create a PCM600 project with all the needed IEDs. If the substation includes third party IEDs requiring configuring for horizontal GOOSE communication, instantiate a generic IEC IED under the substation in the plant structure and import the SCL files (ICD/CID) holding the information on those IEDs. The third party IEDs have separate tools for creating the ICD/CID/SCD file. 2. Start the IEC Configuration tool. 611 series 25

34 Section 5 GOOSE 1MRS B GUID-BC29FDFF-0EDA-412B BCEB7EC43FF V1 EN Figure 5: Starting IEC Configuration Configuring a GOOSE publisher with the IEC Configuration tool To control the GOOSE data publishing, such as addressing, every publisher IED must have at least one data set for GOOSE data and one GOOSE control block. 1. Group the data to a data set sent to IEC station bus. 2. Define the GOOSE control block. The IED can send single binary, double binary, integer and floating point data values with a quality attribute. A quality attribute is used at the receiver side to check data validity series

35 1MRS B Section 5 GOOSE Creating a GOOSE data set with the IEC Configuration tool The sending data set is defined with the GOOSE control block. With the IEDs of this product series, the sending GOOSE data set can have a maximum of 20 data attributes to minimize the message-handling load in the receiving and sending IEDs. All data sets must be configured under the logical node LLN0 and must be provided with names unique within the IED. The IEDs allow a maximum of four GOOSE control blocks, which effectively limits the IED to four data sets for GOOSE, as there is a one-to-one correspondence between the GOOSE control blocks and GOOSE data sets. Typically, it is sufficient to define a single data set and control block for an application. However, it is recommended to use a separate data set and corresponding control block for analog values. 1. Select the target IED in the Plant Structure view. 2. Select GOOSE Communication in the drop-down box on the toolbar. GUID-4BC10E C-9E00-DF F8 V1 EN Figure 6: Selecting GOOSE communication 3. Select the Data Sets tab. 4. To add a new data set, right-click the area containing the data set names and select New. 611 series 27

36 Section 5 GOOSE 1MRS B GUID-3442CD51-442A-432F-99D1-FC5D7BEBED2F V1 EN Figure 7: Creating a new data set 5. Define the LN where the data set is to be placed (accept preselected LD0/ LLN0 ) and give the data set a unique name series

37 1MRS B Section 5 GOOSE GUID-21C1ACA E-81EA-9A5408F44F24 V1 EN Figure 8: Naming the data set A maximum of 80 data attributes can be added to IED's GOOSE data sets. Recommendation is to divide attribute amount to 20 per GOOSE data set, for maximum performance in sender/receiver. After creating the GOOSE data sets, define the data set entries (data attributes or data objects) for the data sets. After creating the GOOSE data sets, define the data set entries (data attributes or data objects) for the data sets. If quality data attributes are added to a data set, they must be located after the status value of the corresponding data object. The received GOOSE data set can contain signals on the data attribute or data object level. Data object level GOOSE entries can only be received of the following CDC types: SPS, SPC, ACD, ACT, DPS, DPC, INC, INS, ENC and ENS. Other CDC types can be connected to application only when dataset is defined in attribute level. Defining GOOSE data set entries with the IEC Configuration tool 1. Select the Data Sets tab. 2. Right-click a data set and select Details to add data attributes. 611 series 29

38 Section 5 GOOSE 1MRS B GUID-E8418EA9-A61D-4656-A31E-2192FAF5400A V1 EN Figure 9: Opening Details 3. In the Data Set Entry window, select the data attribute or data object present in the data set. Click Append selected to add the data to the end of the data set. To add a data object level entry, select it from the FC section. To add a data attribute level entry, select it from the DA section Click Insert selected to add the data above the selected row in the data set entries list. To remove a data from the data set, select the data in the data set entries pane and click Remove selected. A maximum of 80 data attributes can be added total to IED's GOOSE data sets. Recommendation is to divide attribute amount to 20 per GOOSE data se, for maximum performance in sender/receiver. GUID-4E9C55D A7E-A95E-0E808545E7DF V1 EN Figure 10: Adding data set entries series

39 1MRS B Section 5 GOOSE If a data set has quality attributes, the attributes must be located after the status value of the same data object. The data attribute entries are single data, such as stval and q. Data set entries can be also defined on data object level. Data object level GOOSE entries can only be received of the following CDC types: SPS, SPC, ACD, ACT, DPS, DPC, INC, INS, ENC and ENS. After defining the data entries for the data sets, configure the GOOSE control block properties Configuring a GOOSE control block with the IEC Configuration tool 1. Select the IED in the Plant Structure view. 2. Select the GOOSE Controls tab in the tool pane. 3. To add a new GOOSE control block, right-click the area containing the existing GOOSE control blocks and select New. 611 series 31

40 Section 5 GOOSE 1MRS B GUID-3A2BEC01-1F18-43C2-BD5D-E9207FBD049F V1 EN Figure 11: Creating a new GOOSE control block 4. Browse to LLN0 under LD0 to define where the GOOSE control block is to be placed. 5. Give a unique name to the GOOSE control block series

41 1MRS B Section 5 GOOSE GUID-4057F B8A0-02A9A39DC387 V1 EN Figure 12: Naming a GOOSE control block 6. In the Data set drop-down list, select the previously created data set to link with the GCB. 611 series 33

42 Section 5 GOOSE 1MRS B GUID-400C0004-E055-4D8C-A677-E6E5B6F1D6CF V1 EN Figure 13: Data set drop-down list GUID-DC485CA5-04BE D38F72D956 V1 EN Figure 14: Data set drop-down list Data set entries in a data set linked to the GCB can be modified from the GOOSE control block tab by selecting Data Set details in the shortcut menu. 7. Edit the properties and addresses of the created GOOSE control block. Edit at least MAC Address and APP ID series

43 1MRS B Section 5 GOOSE GUID-F55622D6-1A3B-4EA8-9D4F-D0F6C229C849 V1 EN Figure 15: GOOSE control block properties Table 5: GOOSE control block properties GoCB property GoCB name Application (AppID) t(min) (ms) t(max) (ms) Table continues on next page Description GOOSE control block name. The maximum length is 28 characters. A unique GOOSE Identification string for each GoCB in the system. Recommendation is to define a device-specific value and not to use the default empty value. The maximum length is 64 characters. Indicates the maximum response time in milliseconds to data change. This time can be used by the receiver to discard messages that are too old. In principle, t(min) can vary depending on the data type, but for the IEDs, the value is always 10 ms for sent data. Indicates the background "heartbeat" cycle time in milliseconds; the default value is ms. If there are no data changes, the IED still resends the message with the heartbeat cycle to enable the receiver to detect communication losses, that is, the communication is supervised. 611 series 35

44 Section 5 GOOSE 1MRS B GoCB property Configuration Revision MAC Address App ID VLAN-ID VLAN Priority Description Contains an integer value that is sent in every GOOSE message. The integer indicates the amount of changes in the data set. The receiver checks the message for configuration mismatches. Configuration Revision cannot be manually edited in IET600. Multicast MAC address to which the specific GOOSE data is sent. The receiving IED filters the frames and starts to process them if a specific multicast address is defined in the configuration. It is recommended to have one unique multicast address per GoCB. The address range for GOOSE Multicast addresses is 01-0C- CD C-CD FF Unique HEX value application identifier for sending the GoCB within the system. It identifies the purpose of this particular data set. The value range is FFF. Used if the Ethernet switches in a station bus support VLAN. If static VLAN identifiers are defined, it also affects the switch port configuration. Value 000 indicates a non-configured VLAN and switches do not filter these messages on a port basis. This is recommended if there is no need to split the logical network. The VLAN identifier is a 3-character HEX value with range FFF. Recommended values are Used in networks supporting VLANs. The priority is used with network switches. The default value for GOOSE is 4 and the value range is With the IEDs of this product series, only t(max) is configurable, not t(min). The multicast MAC address is usually unique, and APP-ID must be unique Configuring a GOOSE subscriber with the IEC Configuration tool The IED application can receive and use single binary, double binary, integer and floating point values with attached quality information. A quality attribute is received and processed automatically Configuring GOOSE inputs with the IEC Configuration tool 1. Select the IED node from the plant structure in the Project Explorer window. 2. Click the GOOSE Controls tab in the tool pane. The rows of the GCB client editor show GCBs, the so-called senders, and the columns show the IEDs available as the GOOSE clients, the so-called receivers series

45 1MRS B Section 5 GOOSE All IEDs that are configured in the plant structure automatically appear in the clients column. 3. To add or remove clients for a GOOSE control block, click the check-box in the grid corresponding to the IEDs. When adding or removing clients, the input sections of the corresponding IEDs are updated GUID-8373FE57-645E-42E1-810D-964F29E52BDF V1 EN Figure 16: GCB client editor showing the senders and receivers 1 Publisher 2 Subscriber 1 3 Subscriber 2 In the Data Sets tab and the GOOSE Controls tab, the Clients column shows all the configured IEDs. For the IED without data sets and GCBs, however, there is no check box in the grid matrix since the IED publishes the GOOSE control block to the network. 611 series 37

46 Section 5 GOOSE 1MRS B In the Data Sets tab, the clients are mapped automatically to the corresponding data sets based on the configuration done in the GOOSE Controls pane and vice-versa. 5.4 Configuring GOOSE with IET600 See detailed descriptions of the steps in corresponding chapters. 1. Add devices to a PCM600 project. 2. Export the SCD file. 3. Import the SCD file to IET Engineer the GOOSE connections between the devices Define the published GOOSE data and control blocks Define the subscribing IEDs for the GOOSE data. 5. Export the SCD file back to PCM In PCM600, engineer the IED applications with GOOSE inputs. Before any configuration, create backups of the PCM600 and IET600 projects. For example, once an SCD file is imported into PCM600, the changes cannot be undone except by restoring the backup series

47 1MRS B Section 5 GOOSE PCM600 Create ABB devices Third party device Export Export SCD file ICD file Import Import IET600 Configure GOOSE publisher and subscriber Export SCD file Import PCM600 Configure GOOSE inputs Third party device Configure GUID F2BE-4FC3-BEFC-EA6F4BC9AAF1 V2 EN Figure 17: Horizontal communication configuration process Defining devices and exporting the SCD file for IET600 Use PCM600 to define the substation and the devices. Before starting the system engineering, configure the device in PCM600. For more information, see PCM600 documentation. 1. Create a PCM600 project with all the needed devices. 2. To export the SCD file, click the Plant Structure tab, right-click the substation node in the submenu and select Export. The file includes the whole substation configuration in SCL format for other tools. 611 series 39

48 Section 5 GOOSE 1MRS B GUID-92768C13-C DD4DA6EC0B57 V1 EN Figure 18: Exporting an SCD file from PCM Define the export options. A dialog box with several options opens. Unlike other ABB tools such as COM600S or MicroSCADA product configuration tools, IET600 does not use the private sections. Select all the check boxes but clear Export As SCL Template. GUID-220A10FD ED FCCC5E0EF6A8 V3 EN Figure 19: Export options for an SCL file 4. Click Export Creating an empty project with IET Open IET To create an empty project, click the round button on the upper-left corner of the IET600 tool. 3. Click Manage Projects series

49 1MRS B Section 5 GOOSE 4. In the Projects dialog, click New. 5. Name the project. GUID-74E0891B-22AE-4C0B-BE8E-AF85DFEBBCFC V1 EN Figure 20: Naming a project 6. To select the destination folder for the project, click Browse. 7. Click OK. After creating an empty project, import the SCD file from PCM600 to the project Importing the SCD file into IET Import the SCD file from PCM600 to the empty project. Click Import SCL File on the shortcut menu of the project object Click Import button 611 series 41

50 Section 5 GOOSE 1MRS B GUID-B7708EC E0D-49131AF7EC54 V1 EN Figure 21: Importing an SCL file 2. Locate the SCL file and click Open. If the substation includes third-party devices which need to be configured for horizontal GOOSE communication, the SCL files holding the information from those devices must be imported as well. The third-party devices have separate tools for creating the ICD/CID/ SCD file. SCD files can be imported to a project only once. If a new device needs to be later added to the configuration, it must be first created using the Create New IED function after which the Update IED function can be used to import the related CID or ICD file. Another alternative is to create a new project in IET600 and import the whole SCD file from PCM600. The existing IEC configuration including GOOSE series

51 1MRS B Section 5 GOOSE remains if the changes made in IET600 have been already imported to PCM Configuring a GOOSE publisher with IET600 To control the GOOSE data publishing, such as addressing, every publisher device must have at least one data set for GOOSE data and one GOOSE control block. 1. Group the data to a data set sent to IEC station bus. 2. Define the GOOSE control block. The protection relay can send single binary, double binary, integer and floating point data values with a quality attribute. A quality attribute is used at the receiver side to check data validity Creating a GOOSE data set with IET600 Define the sending data set used by the GOOSE control block. With the protection relays of this product series, the sending device can have a maximum of 80 data attributes in GOOSE data sets. To minimize the message-handling load in receiving and sending protection relays, the recommendation is to divide data attributes to a maximum of 20 per data set. All data sets must be configured under the logical node LLN0 and must be provided with names unique within the device. The protection relays allow a maximum of four GOOSE control blocks, which effectively limits the protection relay to four data sets for GOOSE as there is a one-to-one correspondence between the GOOSE control blocks and GOOSE data sets. Typically it is sufficient to define a single data set and control block for an application. However, it is recommended to use a separate data set and corresponding control block for analog values. 1. Select the IEDs tab in the navigation pane. 2. Click the IED node. 3. Click the Datasets tab in the editor pane. 611 series 43

52 Section 5 GOOSE 1MRS B GUID-A3DF D-4452-A0EF-9C092738D72B V1 EN Figure 22: Creating a data set in IET To add a new data set, right-click the area containing the data set names and select Insert new row the shortcut menu. 5. Define the LN where the data set is to be placed (accept preselected LD0/ LLN0 ) and give the data set a unique name series

53 1MRS B Section 5 GOOSE GUID-F3C90B9D-2B5B-40E0-9E2F-FDC71E2C554C V1 EN Figure 23: Naming a data set in IET600 After creating the GOOSE data sets, define the data attributes for the data sets. If quality data attributes are added to a data set, they must be located after the status value of the corresponding data object. The received GOOSE data set can contain signals on the data attribute or data object level. Data object level GOOSE entries can only be received of the following CDC types: SPS, SPC, ACD, ACT, DPS, DPC, INC, INS, ENC and ENS. Other CDC types can be connected to application only when dataset is defined in attribute level. Defining data entries with IET Select the Datasets tab on the editor pane. 2. Select a GOOSE data set. 3. Using the selection lists below the data set grid, select a data attribute or data object to be used. Click Append >> to add the data attribute to the end of the data set. Click Insert > to add the data attribute above the selected row in the data set entries list. A maximum of 80 data attributes can be added in total to the IED's GOOSE data sets. Recommendation is to divide the attribute amount to 20 per GOOSE data set for maximum performance in sender/receiver. 611 series 45

54 Section 5 GOOSE 1MRS B GUID-BE478BC1-71C0-4D50-AF3E-5A BD0 V1 EN Figure 24: Adding data set entries The possible amount of attributes that can be added to a data set and the amount of already added attributes are shown above the data set entries list. However, since IET600 cannot make a difference between the maximum data attribute count of a data set for vertical reporting and a GOOSE data set, too high a maximum value is shown for a GOOSE data set. If a data set has quality attributes, the attributes must be located after the status value of the same data object. Data set entries for vertical reporting are selected using the data object level, and entries for GOOSE using the data attribute or data object level. After installation of the connectivity package documentation add-on, a full list of the available signals with descriptions and IEC names is available in PCM600 under the Documentation menu of the IED node. The document name in PCM600 is Parameter List. After defining the data entries for the data sets, configure the GOOSE control block properties series

55 1MRS B Section 5 GOOSE Configuring a GOOSE control block with IET Select the IED node on the IEDs tab in the navigation pane. 2. Select the GCB Data tab in the editor pane. GUID-AE85F33A-01D B40557CB8469 V1 EN Figure 25: Creating a GOOSE control block 3. To add a new GOOSE control block, right-click the area containing the existing GOOSE control blocks and select Insert new row. GUID-DB202FC2-C7E5-4CB6-B BEA4652A V1 EN Figure 26: Naming a GOOSE control block 611 series 47

56 Section 5 GOOSE 1MRS B 4. Browse to LLN0 under LD0 to define where the GOOSE control block is to be placed. 5. Give a unique name to the GOOSE control block. 6. In the Attached Dataset drop-down list, select the previously created data set. After creating the GOOSE control block, edit its properties and addresses. Edit at least MAC Address and APP-ID. GUID-468D1D23-E2CE-448F-989D-55CDF8EC1AE4 V1 EN Figure 27: GOOSE control block properties To set the visibility of the GoCB columns, click the upper-left icon of the table and select or clear the check boxes in the Field Chooser dialog. GUID-083ECBF0-40B2-499A B612D29 V1 EN Figure 28: Field Chooser dialog Table 6: Selected GOOSE control block properties GoCB property GCB Application (appid) t(min) (ms) Table continues on next page Description GOOSE control block name A unique GoID for each GoCB in the system. Recommendation is to define a device-specific value and not to use the default empty value. Indicates the maximum response time in milliseconds to data change. This time can be used by the receiver to discard messages that are too old. In principle, t(min) can vary depending on the data type, but for the protection relays, the value is always 10 ms for sent data series

57 1MRS B Section 5 GOOSE GoCB property t(max) (ms) Conf.Rev. MAC Address APP-ID VLAN-ID VLAN Priority Description Indicates the background "heartbeat" cycle time in milliseconds; the default value is ms. If there are no data changes, the protection relay still resends the message with the heartbeat cycle to enable the receiver to detect communication losses, that is, the communication is supervised. Contains an integer value that is sent in every GOOSE message. The integer indicates the amount of changes in the data set. The receiver checks the message for configuration mismatches. Configuration Revision cannot be edited manually in IET600. Multicast MAC address to which the specific GOOSE data is sent. The receiving device filters the frames and starts to process them if a specific multicast address is defined in the configuration. It is recommended to have one unique multicast address per GoCB. The address range for GOOSE Multicast addresses is 01-0C- CD C-CD FF. Unique HEX value application identifier for sending the GoCB within the system. It identifies the purpose of this particular data set. The value range is FFF. Used if the Ethernet switches in a station bus support VLAN. If static VLAN identifiers are defined, it also affects the switch port configuration. Value 000 indicates a non-configured VLAN and switches do not filter these messages on a port basis. This is the recommended if there is no need to split the logical network. The VLAN identifier is a 3-character HEX value with range FFF. Recommended values are Used in networks supporting VLANs. The priority is used with network switches. The default value for GOOSE is 4 and the value range is With the protection relays of this product series, only t(max) is configurable, not t(min). Conf.Rev. cannot be manually edited. The multicast MAC address is usually unique, and APP-ID must be unique Configuring a GOOSE subscriber with IET600 The relay application can receive and use single binary, double binary, integer and floating point values with attached quality information. A quality attribute is received and processed automatically. 611 series 49

58 Section 5 GOOSE 1MRS B Configuring GOOSE inputs with IET Select the root node on the IEDs tab in the navigation pane. 2. Click the GCB Clients tab in the editor pane. The rows of the GCB client editor show GoCBs, that is, senders, and the columns show the devices available as GOOSE clients, that is, receivers. If the client device is not on the same subnetwork as the GoCB sender, it cannot be configured as a client. GUID-D619B BE5-9F26-06FE54D2A2CB V1 EN Figure 29: GCB client editor 3. To add or to delete clients, double-click the cell. Upon adding or removing clients, the corresponding input sections are updated. GUID-540DD340-BBAC-4A83-B8BA-24B8E87D13B5 V1 EN Figure 30: GOOSE inputs Finalizing GOOSE configuration with IET Exporting the SCL file 1. Export the SCL file in one of the alternative ways. Click Export SCD File on the shortcut menu of the project object Click Export button series

59 1MRS B Section 5 GOOSE GUID-CA4CD52A E-AA51-06CFDF6F7414 V1 EN Figure 31: Exporting an SCD file Importing the SCL file 2. Select the file destination and click Save. It is recommended to leave the SCD file exported from PCM600 as a backup. 1. Open PCM600 and ensure the original project is open. 2. Switch off the engineering mode. 611 series 51

60 Section 5 GOOSE 1MRS B GUID-653B6F22-8ACA-43D5-B A8BDD637 V1 EN Figure 32: Switching off the engineering mode 3. Go to the Project Explorer view and select the Plant Structure tab. 4. Right-click the project and select Import. GUID-2094D2DA-31A8-4EB DDFAEC142A2 V1 EN Figure 33: Importing an SCD file to PCM Open the SCL file exported from IET In the SCL Import Options dialog box under IED Types, select Don't import IEDs of unknown type if the GOOSE configuration does not include thirdparty devices series

61 1MRS B Section 5 GOOSE GUID-5F360E11-43BC-4853-AC45-DDAFEC6B387C V2 EN Figure 34: SCL import options in PCM Click Import. For more information, see PCM600 documentation. 5.5 Connecting GOOSE inputs to an IED application There are 20 GOOSERCV_BINs in 611 series IEDs. For 611 series application, only GOOSE binary inputs can be connected. A maximum of 20 GOOSE binary inputs can be taken into use. The application manual provides information about the details of GOOSERCV_BIN applications and related switch group functions. 1. In PCM600, open the Project Explorer and select the Plant Structure tab. 2. To open the signal matrix tool, right click the IED, and select Signal Matrix. 3. To map the input points to the receiving input data, click the cell. To expand the source field, click the edge of the field and expand it until the whole GOOSE source address is visible. 4. In Signal Matrix tool in the GOOSE sheet, the GOOSE publisher data is mapped into the corresponding GOOSERCV function block. The columns in the GOOSE sheet represent publisher data and the rows represent the possible subscriber input point. 611 series 53

62 Section 5 GOOSE 1MRS B GUID-F6C0B1A7-47E4-42B FEC V1 EN Figure 35: GOOSE sheet in Signal Matrix tool If the data type does not match with the GOOSERCV function block, the attribute cell is red. 5. Save the changes made in Signal Matrix tool. 6. Write to the IED. 5.6 Received GOOSE message handling A GOOSE frame is not accepted if the Needs Commission bit is set. When the protection relay uses IEC Edition 2, data with the Test quality bit set is accepted only if the receiving device is also in the test mode. When the relay uses IEC Edition 1, the Test field in GOOSE message is also used. For more information about GOOSE quality handling, see the corresponding flowcharts. When the protection relay uses IEC Edition 2, a GOOSE frame is not accepted if the Simulation bit is set. When the protection relay uses IEC Edition 2, the Test quality bit is active in the sender if the relay is set to test mode. When the relay uses IEC Edition 1, the Test field in GOOSE message is also set when in test mode series

63 1MRS B Section 5 GOOSE When the GOOSE sender is in test mode and the GOOSE receiver is not, in Edition 1 mode the GOOSE receiver freezes to its previous valid state, and in Edition 2 mode the data value is defaulted and the quality set to invalid. The Test bit is active in the sender if the protection relay is set to test mode. See the technical manual for more information on the test mode. The GOOSE frame is also not accepted if ConfRev deviates from the one in the configuration. These error situations can be observed in the GSELPRT1 diagnostic counters. The default GOOSE input value is 0 for all the data types. The functionality is analogous to physically wired galvanic Normally Open (NO) contacts where the disconnected signal gives value 0 of FALSE to relay application. The application must be designed to withstand the default value. This value is used when the subscribed GOOSE data is not valid, or it is not received from the network and the peer device is considered to be in a time-out state. If a peer device sends the data including the quality attribute, the receiver device input object is not updated according to the received status value if the data quality is bad, questionable or blocked. The default value is also used in this case. 5.7 GOOSE supervision Background sending To ensure reliability and availability of the application, the GOOSE communication must be supervised. Design the application so that it can handle communication losses, for example, when a peer device is not available or there are communication time-outs. If there are no GOOSE-related data changes, the protection relay resends the last GOOSE message with a heartbeat cycle to enable the receiver to detect communication losses. The heartbeat cycle is defined by modifying the MaxTime property on GOOSE control block. Every GOOSE frame has a TAL field which shows how long the frame is valid until the next heartbeat frame. Other devices may have their own TAL values. Nevertheless, all the TAL values under 1000 ms are rounded up to 1000 ms on the receiving side. If no frames are received during 2xTAL, that is, if at least two consecutive frames are lost, then the receiver considers the whole data set as invalid. The quality attribute for the entire data set is set to "bad" and the values are set to their default values. This is an important consideration when designing the application as the default values need 611 series 55

64 Section 5 GOOSE 1MRS B to be "fail-safe" values. For example, the protection relay should use an enabled signal for interlocking and a blocking-type signal for protection Default value handling The information is of point-to-point type which means that there is only one signal connected to the function block input. The default value of the GOOSE receiver blocks output (OUT) is FALSE (0) in case there is a communication error. This handling is applicable for all signal types (binary, integer, enum and floating point). In addition to the default value handling, value output signal automatically carries validity information to the application function blocks. Validity information can be used in application by adding the quality function blocks. In communication disturbance cases, GOOSE receiver blocks use default values. Application function blocks using these signals have their own handling for propagated quality information and fail-safe functionality, especially when receiving analog type of data. Exact fail-safe functionality must be checked from the function block description in the technical manual. If one relay application function block input receives several signals from several protection relays, the input value is calculated in OR or AND operation (configured in the Application Configuration tool) from several inputs. In this case, one default signal is treated as logical FALSE (0), but the other signals can keep the function block input value active. It works similarly as the traditional galvanic signal wires connected between protection relays. The advantage in the GOOSE-based signalling is that the application always detects faulty connections, which is not the case with the Normally Open (NO) type of physically wired galvanic contacts. In all cases, however, a separate alarm event is always generated by the GSELPRT1.Alm data object for IEC event clients. GSELPRT1.Alm can also be used on the application side as an input in the Signal Matrix Tool's Binary Outputs sheet (signal GSELPRT ALARM). For example, it is possible to change the setting group in case one or several protection relays are disconnected from the network Alarm supervision in application In a communication time-out situation, all the peer devices receive information about the problem. The system does not tolerate single failures or non-existing devices, for example, in service situations. Take this into account when designing an application. Disable GOOSE sending by writing false from IEC clients to the GoEna attribute under the GOOSE control block. Use this feature carefully, and for test purposes only series

65 1MRS B Section 5 GOOSE Diagnostic counters The IEC data model of the protection relays includes a logical node LD0.GSELPRT1 for the GOOSE communication diagnostic. The counters are also available via the HMI or PCM600 path Monitoring/I/O Status/Communication/ GSELPRT1/Monitoring. It is possible to reset the GOOSE communication diagnostics counters via Monitoring/I/O Status/Communication/GSELPRT1/Monitoring/Reset counters and via the IEC communication by writing TRUE to the RsCnt.Oper.ctlVal attribute under GSELPRT1. Table 7: Diagnostics data objects Data object Description Diagnostics information FrRxCnt Received messages When increasing, the protection relay is receiving GOOSE messages. FrTxCnt Transmitted messages When increasing, the protection relay is sending GOOSE messages. RxStCnt Received state changes Received GOOSE messages with a new stnum value RxSeqCnt RxTestCnt Received sequence number Received frames with test bit Received GOOSE retransmissions or heartbeat cycle messages with a new sequence number Received GOOSE frames with the test flag on StWrnCnt State errors Number of notified state number jumps SeqWrnCnt Sequence errors Number of notified sequence number jumps RxTmOutC nt ConfErrCnt NdsComCnt DSErrCnt Receiver time-outs Received ConfRev mismatches Received frames with Needs Commissioning Errors in received data set Number of notified peer device time-outs When increasing, there is a mismatch between the received GOOSE frame information and the used GOOSE configuration. One peer device Indicates that its configuration is not valid or up-to-date. Received data are syntactically wrong, or there are less data in received data set than expected. Alm Receiver alarm Alarm signal value connected to the event and application logic. It is active when one peer device is in time-out. GOOSE Alarm is activated in the receiver device in certain situations. Time-out Configuration revision mismatch Error in the received data set The Needs Commissioning bit is active in the received message 611 series 57

66 Section 5 GOOSE 1MRS B Wait for GOOSE Message No Frames Received During 2xTAL FALSE GOOSE Receiver Timeout GOOSE Message Received Amount of data entries same as in previous msg? TRUE GOOSE Multicast MAC Address and APPID Match? FALSE TRUE Dataset Error Counter +1 Reset Receiver Timer Receiver Timeout Counter +1 Needs Commissioning Counter +1 TRUE Needs Commissioning? FALSE Configuration Revision Mismatch Counter +1 TRUE Configuration Revision Mismatch? FALSE Dataset Error Counter +1 TRUE Message Out of Order or Dataset Mismatch? Target Data Value Is Defaulted and Quality Set To Invalid. Alarm Is Set To TRUE TRUE State or Sequence Number Error Counter +1 FALSE FALSE State or Sequence Number Not As Expected? Same State Number As Previous Message? TRUE FALSE Frame Test or Simulation field Set? TRUE TRUE Target Data Value and Quality Are Updated Accordingly IEC Edition 2? TRUE FALSE Test Diagnostic Counter +1 Device In Test Mode? FALSE TRUE GUID C5-3B0A-4126-A430-7E0FF1FBE505 V1 EN Figure 36: Receiving GOOSE data in the protection relays series

67 1MRS B Section 5 GOOSE Status or measurand value has been received. Proceed to next data entry Value is followed by quality attribute? Target data value is updated. FALSE TRUE FALSE IEC Edition 2? FALSE Receiver in test mode? TRUE Test bit enabled? TRUE TRUE FALSE Target data value is defaulted and quality set to invalid. TRUE Quality is bad? Bad quality= INVALID RESERVED QUESTIONABLE OVERFLOW OUT-OF-RANGE BAD- REFERENCE OSCILLATORY FAILURE INCONSISTENT INACCURATE FALSE TRUE Operator blocked? TRUE Old data? FALSE FALSE Target data value is defaulted and quality is set according to q attribute. TRUE Operator blocked? FALSE Target data value is updated and quality is set according to q attribute. GUID-5A73778C-01C5-49BF F604E2343B V1 EN Figure 37: Receiving GOOSE data with quality in the protection relays 611 series 59

68 60

69 1MRS B Section 6 IEEE 1588 time synchronization and communication redundancy Section 6 IEEE 1588 time synchronization and communication redundancy 6.1 System building IEEE 1588 v2 Precision Time Protocol (PTP) according to IEEE C Power Profile and Redundant Ethernet topologies (HSR/PRP) are recommended to be used for IEC GOOSE to ensure the high accuracy time synchronization and highest availability High-availability seamless redundancy HSR HSR topology includes an HSR ring with the IEDs of this product series where IEEE 1588 v2 clock masters are connected to the ring utilizing Ethernet switches. HSR ring is presented with light blue lines and normal Ethernet connections with dark blue. Each connected node in the HSR ring must support HSR protocol to ensure smooth redundancy. Otherwise Ethernet communication is disturbed and might not work. Single attached nodes can be connected to a HSR ring with a separate redundancy box (RedBox). Use correct Ethernet connectors in the IED with HSR. IEDs with HSR support have three Ethernet connectors and redundant Ethernet ports are marked as LAN A and LAN B. The third Ethernet port without any LAN A or LAN B marking is an interlink port which is used as a redundancy box connector. 611 series 61

70 Section 6 IEEE 1588 time synchronization and communication redundancy 1MRS B Primary IEEE 1588 v2 master clock Secondary IEEE 1588 v2 master clock (optional) Managed HSR Ethernet switch IEC HSR Managed HSR Ethernet switch GUID-2E19742E-C9BE-4305-AC57-CC5FCAB654E6 V1 EN Backup 1588 master clock Figure 38: Recommended HSR reference topology with IEEE 1588 v2 The maximum number of IEDs supported in the HSR ring is 30. This is to keep the ring delay as small as possible for horizontal applications. The IED interlink port does not support IEEE 1588 v2 slave devices. HSR bandwidth is 50 Mbit/s as all messages are doubled for both directions of the ring Parallel redundancy protocol PRP PRP topology presented here is a reference system with proper switches supporting IEEE 1588 v2. This topology includes duplicated star networks which are in PRP called LAN A and LAN B. IEEE 1588 v2 clock masters are connected to the network utilizing Ethernet switches. PRP LAN A is presented with dark blue lines and LAN B with light blue. It is important in PRP not to connect LAN A and LAN B anywhere else than to end devices supporting PRP. Otherwise Ethernet communication is disturbed and might not work. All devices connected to both LAN A and LAN B must support the PRP protocol. Single attached nodes can be connected directly to LAN A or LAN B in series

71 1MRS B Section 6 IEEE 1588 time synchronization and communication redundancy which case there is no redundancy for this node or with a separate redundancy box (RedBox). Use the correct Ethernet connectors in the IED with PRP. IEDs with PRP support have three Ethernet connectors and redundant Ethernet ports are marked as LAN A and LAN B. The third Ethernet port without any LAN A or LAN B marking is an interlink port which is used as a redundancy box connector. Do not mix different PRP LANs. Ensure that the LAN A port is always connected to LAN A only and the LAN B port is connected to LAN B. The IED interlink port does not support IEEE 1588 v2 slave devices. Primary IEEE 1588 v2 master clock Secondary IEEE 1588 v2 master clock (optional) Managed Ethernet switch IEC PRP Managed Ethernet switch GUID-97160F71-CE92-413F-B090-FDF2C11918B8 V1 EN Backup IEEE 1588 v2 master clock Figure 39: Recommended PRP reference topology with IEEE 1588 v2 611 series 63

72 Section 6 IEEE 1588 time synchronization and communication redundancy 1MRS B 6.2 Bay level configuration IEEE 1588 v2 parameters and status information Time The time parameters are found via menu path Configuration/Time.. Table 8: Time parameters Parameter Value Range Synch source IEEE 1588 PTP Domain ID PTP priority 1 1) PTP priority 2 1) ) Smaller value has higher priority In IEEE 1588 v2, the PTP domain is a logical grouping of clocks that synchronize to each other using the protocol but that are not necessarily synchronized to clocks in another domain. PTP priority 1 and PTP priority 2 are used in the execution of the best master clock algorithm in which lower values take precedence. Priority 1 is the first one used to decide the clock master. Best master clock algorithm The best master clock algorithm compares data describing two clocks to determine which data describes the better clock. This algorithm is used to determine which of the described clocks in several announce messages received by the local clock port is the best clock. It is also used to determine whether a newly discovered clock is better than the local clock. The comparison algorithm is based on pair-wise comparisons of attributes with the following precedence. Priority 1 Clock class Clock accuracy Clock stability Priority 2 Clock identity: A tie-breaker based on unique identifiers Time synchronization monitoring values The time synchronization monitoring values are found via menu path Monitoring/IED status/time synchronization series

73 1MRS B Section 6 IEEE 1588 time synchronization and communication redundancy Table 9: Description Sync source Sync status Sync accuracy Time synchronization monitoring values Value IEEE 1588 master IEEE 1588 slave Up Down bits Sync accuracy indicates the synchronization accuracy in number of fractional bits. Sync accuracy can be calculated from the number of bits according to a formula. Synch _ accuracy = 2 bits seconds GUID AFCC-45F63F2FE02D V1 EN (Equation 1) Table 10: Synch accuracy values and corresponding accuracies Bits Accuracy µs 20 1 µs 19 2 µs 18 4 µs 17 8 µs ms 10 1 ms 9 2 ms 8 4 ms 7 8 ms s 0 1 s The time synchronization accuracy is rounded to the next worse accuracy, for example, if the accuracy is 2..3 ms, it is shown as 8 bits (4 ms). IEEE 1588 v2 monitoring values The IEEE 1588 v2 monitoring values are found via menu path Monitoring/IED status/time synchronization/ieee series 65

74 Section 6 IEEE 1588 time synchronization and communication redundancy 1MRS B Table 11: IEEE 1588 v2 monitoring values Description Grandmaster Identity Grandmaster time src Grandmaster accuracy Value Atomic clock GPS Terrestrial radio PTP NTP Hand set Other Internal oscil. Within a domain, grandmaster is the clock that is the ultimate source of time for clock synchronization using the PTP protocol. Grandmaster identity indicates the identity of the master clock. Grandmaster time src indicates the source of time used by the grandmaster clock. Grandmaster accuracy indicates the accuracy of the grandmaster clock Power profile parameters The IEDs' IEEE 1588 v2 time synchronization complies with the IEEE C Power Profile. For best interoperability, third party devices in the same IEEE 1588 v2 time domain network must be set according to Power Profile either via the power profile parameter or by individually setting the parameters according to Power Profile. Table 12: IEEE C Power Profile key parameters Parameter Value 1) Delay Mechanism VLAN priority Ethertype Announce period Sync period Pdelay period PTP mode P2P mandatory (default=4) 0x88f7 1 s 1 s 1 s transparent 1) Some devices use the standard notation format 2 x [s] of IEEE 1588 v2 intervals. The values in this table are in [s] format series

75 1MRS B Section 6 IEEE 1588 time synchronization and communication redundancy 6.3 Engineering verification This chapter gives a checklist of items to check and confirm during the engineering phase. The complete test specification depends on the network topology and used system components. Table 13: Time synchronization Item Description Checked Time quality Missing clock PTP priority 1 PTP priority 2 Grandmaster Observe the grandmaster accuracy (Monitoring/IED status/time synchronization/ieee 1588). The accuracy decreases slowly if the GPS antenna is removed. The IED GNRLLTMS1 WARNING signal is activated if the accuracy is not within the specified limits. Disable the clock master and check that one IED takes the clock master role. Compare priorities against the grandmaster's priority. The clock master should have smaller value (bigger priority). Same as above, but PTP priority 2 handles the selection when PTP priority 1 is the same. Can be used to set priorities to the IEDs in situation when the clock master fails. Check the grandmaster monitoring from the master configuration via the LHMI path Monitoring/IED status/time synchronization/ieee Check that all IEDs are synchronized to same PTP master. Table 14: Network Item Description Checked Max HSR loop size Maximum supported HSR loop size is 30. Consider applying different topology in case a larger system is needed. Interlink port IEEE 1588 v2 slave devices are not allowed in the interlink port. Redundancy Check the maximum delays in different network setups. 611 series 67

76 68

77 1MRS B Section 7 Engineering of event reporting with PCM600 Section 7 Engineering of event reporting with PCM Managing IEC clients with the IEC Configuration tool The default IED SCL contains five default client definitions, Client1... Client5, which are used by all the RCBs. PCM600 does not show these clients in the plant structure, but the IEC Configuration tool shows the clients in the client-server communication. MicroSCADA and COM600S clients can use the client definitions directly. If other clients need to be added to the project, import the ICD file describing the client data model to PCM Adding new IEC clients for the IEC Configuration tool Adding a new IEC client to a PCM600 project is a two-step operation. First, a new generic IEC IED object must be created under the plant structure and the relevant client ICD or CID file must be imported to the generic IEC IED. 1. Right-click a bay node in the project plant structure, point to New, then point to Generic IEC61850 IEC and select IEC61850 IED. 611 series 69

78 Section 7 Engineering of event reporting with PCM600 1MRS B GUID-12583A6B-720A-4BBB-948B-C0F7BAAEFCAB V1 EN Figure 40: Creating a generic IEC IED 2. Rename the IED object as Client_G. 3. Right-click the IED and then select Import series

79 1MRS B Section 7 Engineering of event reporting with PCM600 GUID-67C5F3BC-E800-41F1-A5ED-BC1B20241CCF V1 EN Figure 41: Selecting Import on the shortcut menu 4. Select a valid Client SCL file (ICD or CID) and click Open in the file selection dialog box. 5. Select Ignore PCM Object Type and then click Import in the SCL Import Options dialog box. 611 series 71

80 Section 7 Engineering of event reporting with PCM600 1MRS B GUID-0E26E18A-46EE-433D-956B-A051FDFA1B00 V1 EN Figure 42: Defining SCL import option 6. Start the IEC61850 Configuration tool and select Client-Server communication as engineering mode. The newly added client should be present in the Clients column along with other clients in both the Data Set tab and the Report Controls tab series

81 1MRS B Section 7 Engineering of event reporting with PCM IEC Configuration tool user interface GUID-FCABB5C3-C08E-4560-A2CD-F34B5E01CBA3 V1 EN Figure 43: IEC Configuration tool user interface 1 Engineering mode selection 2 Switch engineering mode on and off 3 Switch IEC IED naming on and off 4 Create new object 5 Selection details 6 Receiving access points 7 Mapping grid 8 Data to send/receive 9 Engineering type selection 10 Object properties 1. Engineering mode selection The communication mode can be selected from the drop-down list on the toolbar. Two modes are available: GOOSE Communication and Client-Server Communication. 2. Switching engineering mode on and off The button switches between engineering and view mode. The configuration can be edited only in the engineering mode. 611 series 73

82 Section 7 Engineering of event reporting with PCM600 1MRS B GUID-3D82B39F-D86C-4E99-9AB7-DC3105E6DFE6 V1 EN Figure 44: Engineering mode selection button When the engineering mode is enabled, SCD files from external IEC engineering tools cannot be imported into PCM Switching IEC IED naming on and off The button switches between IEC and PCM600 IED naming. 4. Create new object. The button opens a window to create a new object. The type of object depends on the currently selected engineering type. 5. Selection details The button opens the Editor window for the data currently selected in the mapping grid. The same editor can also be opened by double-clicking the data. 6. Receiving access points All IEDs that have access points capable of receiving the kind of data according to the currently selected engineering type and engineering mode are displayed as columns in the mapping grid. A check mark in a column means that the access point is receiving the data. 7. Mapping grid Mapping grid consists of check boxes for configuring what data is sent to or received by an access point. A check mark in the grid means that the data on the row is sent to the receiver in the column. 8. Data to send/receive The data available for sending/receiving in the selected engineering mode and type is displayed as rows in the mapping grid. The data is context-sensitive, with the current selection in the PCM600 plant structure. A check mark in the row means that the data is sent to or received by an access point. Double-click a data to open the data editor. 9. Engineering type selection Each engineering mode has several engineering types. Engineering type means the type of data to configure. The types can be selected by clicking the tab page on the bottom of the tool window. The available engineering types depend on the selected engineering mode. Data sets: Create, delete, modify or send data sets GOOSE controls: Create, delete, modify or send GOOSE controls Report controls: Create, delete, modify or send report controls Inputs: View inputs (external references) 10. Object properties The Object Properties window displays the properties of the currently selected data. Different data properties are edited in this window series

83 1MRS B Section 7 Engineering of event reporting with PCM Creating data sets with the IEC Configuration tool 1. Select Plant Structure in the Project Explorer window. 2. Right-click the IED node. 3. Select Client-Server Communication in the drop-down box on the toolbar. GUID-FF5A846C-7D78-4D14-940D-39D1EFF4B724 V1 EN Figure 45: Selecting Client-Server Communication 4. Select the Data Sets tab. 5. Right-click the area containing the data set names and select New to add a new data set. GUID-28F76C6F-2ACD E15-D V1 EN Figure 46: Creating a new data set 6. In the Create New Data Set dialog box, define the LN where to place the data set (accept preselected LD0/LLN0 ) and give the data set a unique name. 611 series 75

84 Section 7 Engineering of event reporting with PCM600 1MRS B GUID-F14E4515-A22B-4C29-B903-E792A199C807 V1 EN Figure 47: Naming the data set After creating the GOOSE data sets, define the data set entries (data attributes or data objects) for the data sets Defining data set entries with the IEC Configuration tool 1. Select the Data Sets tab. 2. Right-click a data set and select Details to add data attributes series

85 1MRS B Section 7 Engineering of event reporting with PCM600 GUID-059FEAC2-FBC ABC4-3B77748C5938 V1 EN Figure 48: Adding data attributes 3. In the data set entry window, select the data attribute to be contained in the data set. Click Append selected to add the data attribute to the end of the data set. Click Insert selected to add the data attribute above the selected row in the data set entries list. To remove a data attribute from the data set, select the data attribute in the data set entries pane and click Removed selected. Reporting datasets can include status and measurement type of data. Also configuration and setting values can be added to datasets in case required. Data set entries for vertical reporting are selected using the data object level, and entries for GOOSE using the data attribute or data object level. 611 series 77

86 Section 7 Engineering of event reporting with PCM600 1MRS B 7.4 Creating report control blocks with the IEC Configuration tool 1. Select the IED node in Plant Structure in Project Explorer. 2. Click the Report Controls tab. 3. Right-click the area containing the existing report control blocks and select New to add a new report control block. GUID-91955B85-A88B-4DDA-9A56-0FDB665AD730 V1 EN Figure 49: Adding a new report control block 4. Browse to LLN0 under LD0 to define where to place the report control block. 5. Give a unique name to the report control block. 6. In the drop-down list, select the previously created data set to link with the GCB series

87 1MRS B Section 7 Engineering of event reporting with PCM600 GUID-209DADC9-E621-40A4-85D3-0998C494F622 V1 EN Figure 50: Data set drop-down list 7. Edit the properties and options of the created report control block. 611 series 79

88 Section 7 Engineering of event reporting with PCM600 1MRS B GUID-FBAFEB73-38F4-4A9D-9DB7-136F8184D99B V1 EN Figure 51: Report control block properties Data set entries in a data set linked to the GCB can be modified from the GCB Control Block tab by selecting the Data Set Details in the shortcut menu series

89 1MRS B Section 7 Engineering of event reporting with PCM Configuring RCB clients with the IEC Configuration tool Add and configure the IEDs before configuring the RCB client. The potential clients and their communication configuration should be known for a successful RCB client configuration. The RCB name is limited to 14 characters or 30 charactecters (without two-digit index number) depending on which IEC version is in use. 1. In the Plant Structure, click the IED node which is RCB server. 2. Click Report Controls tab. The rows of the Report Controls window show RCBs configured for the IED. The columns of the Report Controls window show the RCB clients configured in the PCM To add or remove clients for a report control block, click the check-box in the grid, corresponding to the client and RCB. Five clients at the maximum can be connected to a RCB. 1 2 GUID-DD0A AD55-F4FD80B64E20 V1 EN Figure 52: RCB clients 1 RCBs configured for the IED 2 RCB clients 611 series 81

90 Section 7 Engineering of event reporting with PCM600 1MRS B The clients are added or removed automatically to the corresponding data sets in the Data Sets tab. Date sets are based on the configuration done in the Reports Controls tab and vice-versa. 7.6 Substation section configuration in the IEC Configuration tool The substation topology consists of the substation, voltage level and bay nodes. The bay nodes include also the conducting (primary) equipment, which corresponds to the switches, that is, the circuit breakers, disconnectors, and earth switch, of the configured IED. In addition to the substation topology configuration, logical nodes of the IEDs are mapped to proper objects, for example, to support the automatic bay configuration via SCL files in the SCADA system. At the moment, the IEC Configuration tool does not support engineering of the substation section. Instead, for example, IET600 can be used for engineering, if needed series

91 1MRS B Section 8 Engineering of event reporting with IET600 Section 8 Engineering of event reporting with IET Managing IEC clients with IET600 When the relay configurations are changed using IET600, some preparations are required when a project is started and the protection relay's data model is imported to the tool for the first time. The default IED SCL export from PCM600 contains five default client definitions, Client1... Client5, which are used by all the RCBs.MicroSCADA and COM600S clients can use the client definitions directly. If other clients need to be added to the IET600 project, import the ICD file describing the client data model to the project and attach the file to the same IEC subnetwork in the Communication tab. Create the bus connections for the IEC clients Adding new IEC clients for IET600 Adding a new IEC client to an IET600 project is a two-step operation. The client must be first created using the Create New IED function, after which the Update IED function can be used to import the related ICD or CID file. 1. To create an IED, click the IEDs tab in the navigation pane. 2. Click the root node in the IED tree. 3. Right-click the node and click Create New IED. 611 series 83

92 Section 8 Engineering of event reporting with IET600 1MRS B GUID-E18A928E-0D13-42D7-A059-DCA14EC77F90 V1 EN Figure 53: Creating a new IED 4. Type the name of the client IED as it is in the file to be imported. Click OK. GUID-5128D370-B2A5-4CF3-91B6-AC2516CFF722 V1 EN Figure 54: Naming the new IED 5. Right-click the created IED and click Update IED series

93 1MRS B Section 8 Engineering of event reporting with IET600 GUID-A21BDBCF-243C-49A3-ADC1-4950D15C8FA0 V1 EN Figure 55: Choosing a SCD file for updating the IED 6. Select any valid SCL file that is SCD, ICD, CID or IID, and click Open from the file selection dialog box. IET600 automatically matches IEDs with the same name in IET600 and in the file. 7. To import the IED from the file, click OK. GUID-1BAF3BC2-A2BF FC4-2AB5D132F98F V1 EN Figure 56: Updating the IED The procedure used in configuring IEC clients can be used to create or update any IED, also several IEDs at the same time. 611 series 85

94 Section 8 Engineering of event reporting with IET600 1MRS B Attaching IEC clients to a bus with IET Click the Communication tab in the navigation pane. 2. Click the Subnetworks tab in the editor pane. 3. In the Subnetworks grid, select the bus from the Subnetwork list to attach the IEC client to the bus. An alternative way is to drag the client in the Communication tab to the correct subnetwork. GUID-22634FE7-E4F7-45C5-A02C-1FF4206D9C4B V1 EN Figure 57: Defining bus connection properties for IEC clients By default, the IEDs' bus connections are ready-made when the configuration work is started and need not to be set separately. After the client bus connections are created, the event clients appear in the RCB Clients tab. 8.2 IET600 user interface IET600 user interface is divided into sections, that is, panes for navigating and displaying the project data series

95 1MRS B Section 8 Engineering of event reporting with IET GUID-5CDBAF7B-2F3B-4115-B60C-D92520D254D6 V1 EN Figure 58: IET600 user interface 1 Menu on the top of the user interface 2 Navigation pane for context-oriented navigation and filtering the various editors 3 Properties pane for detailed properties of the selected element in the navigation pane 4 Editors for detailed design and engineering of the substation, IEDs and IEC communication 5 Logging and messaging (output) pane The navigation pane provides context-oriented navigation of the editors. It has three tabs, which correspond to three different context views. Substation Full substation topology and primary equipment nodes IEDs IED nodes and corresponding functionality Communication Subnetworks and connected IED access points The editor pane is the main working area of the IET600 user interface. It is organized to various tabs for detailed substation design and engineering. The visible tabs depend on the node type selected in the navigation pane. Available editor tabs depend on the selected node type, not on the selected navigation tab. Choose any available context view to do the needed engineering tasks. 611 series 87

96 Section 8 Engineering of event reporting with IET600 1MRS B Choose upper or lower level in the structure to see the data of single, many or all IEDs at the same time in the editor pane Setting visibility of columns in grid editors Most editors are implemented as tables. These grid editors provide features like setting column visibility, filtering, sorting, automatic data filling, copying and pasting, finding and replacing and exporting to Excel. Most tables include columns which are hidden by default. GUID-98B5E599-F56E-4C78-AA58-29A77342B76F V1 EN Figure 59: Setting column visibility in a grid editor 1. To set the visibility of the columns, click the upper-left icon of the table. 2. Select or clear the check boxes from the Field Chooser dialog box. 8.3 Substation section configuration in IET600 Substation topology consists of the substation, voltage level and bay nodes. Bay nodes include also the conducting (primary) equipment, which corresponds to the switches, that is, the circuit breakers, disconnectors, earth switch, of the configured protection relay. Substation topology is initially built by importing the SCD file from PCM600. The SLD editor is a graphical editor for the configuration of the substation section in IET600. It provides tools to draw the primary equipment and the interconnection between the equipment in the bay series

97 1MRS B Section 8 Engineering of event reporting with IET600 SLD in the protection relay is configured using the Graphical Display Editor of PCM600, not in IET600 GUID-16825D5B-89B6-4F62-969F-2EF494AF87E3 V1 EN Figure 60: SLD Editor 8.4 Creating data sets with IET600 Data sets are created or modified using the Dataset editor, which consists of three parts. Grid for existing data sets (data set creating, deleting and renaming) Selection lists for adding new entries to a selected data set List of data set entries for selected data set (viewing, deleting) 611 series 89

98 Section 8 Engineering of event reporting with IET600 1MRS B GUID-2FDBE5B4-B18A-44CE-80BE-A32F148A63DB V1 EN Figure 61: Data set editor 1 Grid 2 Selection lists 3 List of data entries 1. Select an IED node in the IEDs navigation pane. 2. Click the Datasets tab in the editor pane. 3. Right-click the area containing data set names and select Insert new row. 4. Define the LN where the data set is to be placed (preselected LD0/LLN0 is recommended) and the name for the new data set. 5. Click Append>> to add data items to the end of the data set or click Insert> to add data items above the selected row in the data set entries list. Reporting datasets can include status and measurement type of data. Also configuration and setting values can be added to datasets in case required. Above the data set entries list is shown how many attributes it is possible to add to the data set and how many are already added. Select a proper FC (functional constraint) value for the data attributes to be added to a data set. If none is selected, that is (all) is shown on the list, it is not possible to add attributes to the data set series

99 1MRS B Section 8 Engineering of event reporting with IET600 Data set entries for vertical reporting are selected using the data object level, and entries for GOOSE using the data attribute or data object level. 8.5 Creating report control blocks with IET600 Configuration properties, such as the attached data set and the buffering and triggering options of the RCBs are are defined in the RCB editor. A predefined RCB configuration of a preconfigured IED is a proposed default configuration which can be adapted according to the requirements. 1. Click an IED node in the IEDs navigation pane. 2. Click the RCB Data tab in the editor pane. 3. Right-click the area containing RCB names and select Insert new row. 4. Define the LN where the RCB is to be placed (preselected LD0/LLN0 is recommended) and the name for the new RCB. Use the field chooser to show or hide the properties. For example, the SeqNum, Entry ID and Reason Code options (set by default in the IED) are hidden by default. GUID-135E2E06-244A-4A67-AA84-A02F8D1C0649 V1 EN Figure 62: RCB editor Conf.Rev cannot be manually edited. IET600 updates it automatically to the next multiple of 100 when the configuration changes. Deleting an RCB does not totally remove it from IET600. Instead, its status is set to Deleted and it is not exported to SCL files. Removing a data set automatically puts the related RCB to the Deleted state. An RCB cannot be renamed. To rename an RCB, delete it and create a new RCB with a new name. 611 series 91

100 Section 8 Engineering of event reporting with IET600 1MRS B The RCB name is limited to 14 characters or 30 charactecters (without two-digit index number) depending on which IEC version is in use. 8.6 RCB client configuration with IET600 To succeed with an RCB client configuration, the potential clients and their communication configuration should be known. Therefore, the IEDs must be added and configured to the subnetwork before configuring the RCB client. The rows of the RCB client editor show IEDs and RCBs and the columns show the available client IEDs. If a client IED is not on the same subnetwork as a server IED or RCB, it cannot be configured as a client. GUID-B32499EC-0FB3-42A5-9B3B-33B61DFCD20A V1 EN Figure 63: RCB client editor Different keys can be used when editing the cells. PLUS SIGN (+), asterisk (*) or X to add an additional client to the existing ones Numbers to change the client sequence or add clients MINUS SIGN (-), SPACEBAR or DELETE to delete existing clients Double-clicking with the mouse to add or delete clients RCB client editor supports both manual and semi-automatic client configuration series

101 1MRS B Section 8 Engineering of event reporting with IET Configuring RCB clients semi-automatically On the right in the RCB client editor there are option buttons to choose whether to show IEDs (for defining default clients) or RCBs or both together. There are also buttons to allow semi-automatic configuration of default clients and RCB clients. GUID-EB4EE24C-111F-45E7-BFC4-FF6A1DB93F3F V1 EN Figure 64: Semi-automatic configuring of RCB clients 1. Configure the default clients which are used by the rule-based RCB generation to automatically configure RCB clients. Use buttons on the RCB client editor. Clear All removes all default clients Configure Empty fills out only default clients for those IEDs that have no clients configured yet Configure All deletes all existing default clients and fills them out afterwards 2. Configure the RCBs clients. The default clients must be configured before configuring RCB clients otherwise the automatic RCB client configuration does not work. Use buttons on the RCB client editor. Clear All removes all RCB clients Configure Empty copies the default client configuration of this IED to its RCBs (only for those RCBs that have no clients configured yet) Configure All deletes the existing RCB clients and copies the default client configuration of this IED to its RCBs IET600 updates the Enabled Clients configuration value of the RCBs automatically based on the configuration made in the RCB client editor. In addition, IET600 always reserves one extra engineering 611 series 93