RER615 IEC 61850 Engineering Guide
RER615 IEC 61850 Engineering Guide
RER615 IEC 61850 Engineering Guide
Grid Automation
REC615 and RER615
IEC 61850 Engineering Guide
Document ID: 1MRS757809
Issued: 2015-03-06
Revision: B
Product version: 1.1
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.
http://www.abb.com/substationautomation
Disclaimer
The data, examples and diagrams in this manual are included solely for the concept
or product description and are not to be deemed as a statement of guaranteed
properties. All persons responsible for applying the equipment addressed in this
manual must satisfy themselves that each intended application is suitable and
acceptable, including that any applicable safety or other operational requirements
are complied with. In particular, any risks in applications where a system failure and/
or product failure would create a risk for harm to property or persons (including but
not limited to personal injuries or death) shall be the sole responsibility of the
person or entity applying the equipment, and those so responsible are hereby
requested to ensure that all measures are taken to exclude or mitigate such risks.
This 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.
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 standards EN 50263 and EN 60255-26 for the EMC
directive, and with the product standards EN 60255-1 and EN 60255-27 for the low
voltage directive. The product is designed in accordance with the international
standards of the IEC 60255 series.
Safety information
Dangerous voltages can occur on the connectors, even though the
auxiliary voltage has been disconnected.
When the plug-in unit has been detached from the case, do not
touch the inside of the case. The IED case internals may contain
high voltage potential and touching these may cause personal injury.
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 5 GOOSE..........................................................................23
Horizontal communication................................................................23
Configuring horizontal communication........................................23
GOOSE publishing properties..........................................................23
Configuring GOOSE with the IEC 61850 Configuration tool............24
Defining IEDs and starting the IEC 61850 Configuration
tool...............................................................................................25
Configuring a GOOSE publisher with the IEC 61850
Configuration tool........................................................................26
Creating a GOOSE data set with the IEC 61850
Configuration tool...................................................................26
Configuring a GOOSE control block with the IEC 61850
Configuration tool...................................................................30
Configuring a GOOSE subscriber with the IEC 61850
Configuration tool........................................................................34
Section 8 Glossary.........................................................................87
Section 1 Introduction
The engineering guide provides information for IEC 61850 engineering of the
protection IEDs with PCM600 and IET600. This guide concentrates especially on
the configuration of GOOSE communication with these tools. 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.
This manual addresses the system engineers and installation and commissioning
personnel.
Maintenance
Engineering
Planning &
Installation
Operation
purchase
Quick start guide
Quick installation guide
Brochure
Product guide
Operation manual
Installation manual
Connection diagram
Engineering manual
Technical manual
Application Engineering Guide
Communication protocol manual
IEC 61850 Engineering guide
Point list manual
GUID-7414985D-2433-46E4-B77B-CCE64F6FC8D0 V1 EN
Figure 1: The intended use of documents during the product life cycle
Product series- and product-specific manuals can be downloaded from the ABB
Website http://www.abb.com/substationautomation.
1.4.1 Symbols
The tip icon indicates advice on, for example, how to design your
project or how to use a certain function.
• Abbreviations and acronyms are spelled out in the glossary. The glossary also
contains definitions of important terms.
• The example figures illustrate the IEC display variant.
• Menu paths are presented in bold.
Select Main menu/Settings.
• LHMI messages are shown in Courier font.
REC615 and RER615 7
Engineering Guide
Section 1 1MRS757809 B
Introduction
GUID-43179FBC-BDC7-4062-95BC-81A0F886F785 V1 EN
The IEC 61850 standard specifies an expandable data model and 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 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).
However, IEC 61850 is also open for possible new communication concepts in the
future.
MMS
Real-time
communication
3 TCP
IP
Ethernet link layer
Ethernet physical layer with priority tagging (100 Mbit/s)
GUID-A9FD9579-37AD-4B03-935E-BF39D48B7211 V1 EN
Protection and Control IED Manager PCM600 offers all the necessary functionality
to work throughout all stages of the IED 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.
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 61850 over Ethernet to communicate with bay IEDs. This
communication allows PCM600 to configure and monitor the IEDs. In addition to
IEC 61850 the IEDs have optional communications protocols and hardware to
connect to station engineering tools. PCM600 provides the ability to export the
configuration of the IEDs or entire substation in a standard file format which
allows for station engineering.
A PC with PCM600 can be connected to any 615 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 IEDs.
The modern-day IEDs are designed using the concept of the IEC 61850 standard.
This is primarily in regards to how functions within the IED are modelled and how
the IED is represented in the substation. See the IEC 61850 parameter list for the
list of logical nodes available in the IED and observe how they follow the structure
and rules as defined in part 7 of the standard.
PCM600 can be used for different purposes throughout the IED life cycle. A set of
special tools is available for different applications.
A connectivity package includes all of the data which is used to describe the IED,
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 IED. It also allows for localization of text even
when its read from the IED 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.3 IET600
The Intergrated Engineering Toolbox IET600 is used to configure the IEDs for use
in IEC 61850 horizontal communication and to edit client and event reporting
properties.
IET600 acts as a system tool which is used to define and share the system-wide
IEC 61850 parameters, such as communication addresses, horizontal
communication data and its priorities and client/server (system level/IED)
connections. The actual configuration of the IED and the downloading of
configuration changes are done with PCM600.
If the IED is ordered with no Ethernet communication interface, the front port on
the device still works according to IEC 61850. All settings and configurations are
changed by using IEC 61850 via the front Ethernet port of the LHMI. Without the
Ethernet option, event reporting or peer-to-peer services cannot be used.
The IEDs have been designed around IEC 61850. This means that the functionality
of the IED is represented in a data model in accordance with the standard and the
IEDs support a range of the services provided by the standard.
• Process data: monitoring of status information, measurements
• Application data: protection activations, tripping, fault recordings
• Disturbance recorder files
• Control commands
• Protection settings
• Setting groups
• Configuration data
• Self-supervision messages
• Fast horizontal communication between devices
• Time synchronization
The IEDs are modelled in IEC 61850 using three logical devices.
Generic functionality, such as physical inputs and outputs as well as the alarming
LED functionality, resides under LD0.
GUID-04D0EA25-BAFD-49E1-AF8A-6C0A69F221F0 V1 EN
which is a special logical node that describes the common functionality of the
logical device.
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.
The IEDs are capable of vertical communication between the IED and monitoring
and control systems such as PCM600 or MicroSCADA. Each IED has four
separate clients with which a client can read or write data (an active PCM600
connection is considered to be a client). The IED can report data in either buffered
or unbuffered mode and execute control sequences. 75 events/seconds can be
continuously handled.
The IEDs are also capable of horizontal or peer-to-peer communications. They can
be programmed to publish (send) information to and subscribe (receive)
information from other devices according to the IEC 61850-8-1 and IEC 61850-9-2
LE.
Table 1: Maximum data sets and attributes for GoCB and RCB
Control block Maximum data sets Data attributes Description
GoCB 4 20 The IEDs allow a maximum of four
GOOSE control blocks, which effectively
limits the IED to four data sets for GOOSE.
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.
RCB 18 256 The IEC 61850 configuration tool (IET600
or PCM600) allow a maximum of 18 data
sets and maximum of 256 data attributes
for the report control blocks.
The IED 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 four 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 IED type and options.
The data sets and report control blocks can be modified using the IEC 61850
Configuration tool or IET600, however, this should only be done by individuals
that are extremely familiar with both the IEDs and IEC 61850. Inappropriate
modifications can result in misoperation of the IED.
If all data does not fit into one data set, two data sets with suffixes "A" and "B" are
created.
The IEDs 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 IED allows free renaming and editing of report control blocks
and data sets. Only users who have an in-depth understanding of the IED and IEC
61850 should modify the default configuration.
The IED allows free renaming and editing of report control blocks and data sets.
However, it is mandatory to keep certain signals in data sets for the IEDs, as
removing signals from data sets affects also the available events in the local HMI.
Data objects PhyHealth, PhyHealth1and PhyHealth2 from logical node
LD0.LPHD1 give indications of the IED internal or system configuration faults and
these must be available in some of the IEC 61850 data sets.
Data sets define also the status events which are available in the
LHMI event list.
The IED does not support defining data on data attribute level for
data sets used for vertical reporting. Only top-level data objects are
allowed.
The IED protection function settings and parameters can be set and the active
setting groups changed by any IEC 61850 client using the standard IEC 61850
services. The disturbance recorder and load profile files in COMTRADE format
are retrieved from the \COMTRADE\ directory by using PCM600 or any other
client supporting IEC 61850 file transfer service or FTP.
Section 5 GOOSE
The IED can send any type of status or measurement data in the GOOSE messages
from its IEC 61850 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 IED 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, zero-point clamping and limit supervision.
GOOSE data is transmitted 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 an
increased frequency to ensure the timeliness of its reception. The transmission then
gradually tappers 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 IED 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.
5.3.1 Defining IEDs and starting the IEC 61850 Configuration tool
Use PCM600 to define the substation and the IEDs. Before starting the system
engineering, configure the IED settings and logic in PCM600.
GUID-B9B41288-BB3A-491F-BA7E-C9DF36A2908F V1 EN
1. Group the data to a data set sent to IEC 61850 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.
5.3.2.1 Creating a GOOSE data set with the IEC 61850 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.
GUID-4BC10E72-1660-464C-9E00-DF40146342F8 V1 EN
GUID-C2A0D4A0-5F0C-40E5-A84C-13AF35BA09C6 V1 EN
5. Define the LN where the data set is to be placed (accept preselected “LD0/
LLN0”) and give the data set a unique name.
GUID-1EC590D1-2587-441C-8A1F-2934C10BB823 V1 EN
After creating the GOOSE data sets, define the data set entries (data attributes) for
the data sets.
Defining GOOSE data set entries with the IEC 61850 Configuration tool
GUID-E8418EA9-A61D-4656-A31E-2192FAF5400A V1 EN
3. In the Data Set Entry window, select the data attribute present 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 Remove selected.
A maximum of 20 data attributes can be added to a single GOOSE data set. If the
configured published data set is larger, it is not accepted by the IED.
GUID-62E0E852-8D5E-42E5-A669-78A9C2C873EE V1 EN
The data set entries must be single data attributes, such as stVal and
q.
After defining the data attributes for the data sets, configure the GOOSE control
block properties.
GUID-3C5E7AA0-5A13-4241-A8A7-502D9980F672 V1 EN
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.
GUID-9C901C53-92EF-46FF-A0C0-A60A2617731F V1 EN
6. In the Data set drop-down list, select the previously created data set to link
with the GCB.
GUID-DC485CA5-04BE-4047-8047-67D38F72D956 V1 EN
7. Edit the properties and addresses of the created GOOSE control block.
GUID-60BB02E4-5E31-416F-93A8-E1B77E0F7811 V1 EN
5.3.3.1 Configuring GOOSE inputs with the IEC 61850 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.
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-97E07766-DB86-4435-87CE-1CBBB57C4A80 V1 EN
Figure 15: GCB client editor showing the senders and receivers
1 Subscriber 1
2 Subscriber 2
3 Publisher
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.
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.
PCM600
Export Import
SCD
Create
file
ABB
IET600
devices
Configure GOOSE
Third party publisher and
device Export
subscriber
ICD
file Import Export
SCD file
Import
Third party
PCM600
device
Configure
GOOSE Configure
inputs
GUID-69164641-F2BE-4FC3-BEFC-EA6F4BC9AAF1 V2 EN
5.4.1 Defining IEDs and exporting the SCD file for IET600
Use PCM600 to define the substation and the IEDs. Before starting the system
engineering, configure the IED in PCM600.
GUID-DDCD8876-3E86-4405-859A-F5C06CC47DB2 V1 EN
GUID-014EC1F7-B65A-462E-9785-448AB640CB6A V1 EN
4. Click Export.
1. Open IET600.
2. To create an empty project, click the round button on the upper-left corner of
the IET600 tool.
3. Click Manage Projects.
4. In the Projects dialog, click New.
5. Name the project.
GUID-3CD5DA7F-A4FC-4D16-8008-5860BF7D01F9 V1 EN
After creating an empty project, import the SCD file from PCM600 to the project.
GUID-9F2B5FC8-1AA3-4955-999D-7850B89094AC V1 EN
The third-party IEDs have separate tools for creating the ICD/CID/
SCD file.
1. Group the data to a data set sent to IEC 61850 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.
Define the sending data set used by the GOOSE control block. With the IEDs of
this product series, the sending GOOSE data set can have at maximum 20 data
attributes to minimize the message-handling load in 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.
GUID-A25A2575-C368-4FA0-B3A3-A0119F7B4194 V1 EN
4. 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.
GUID-73606F1C-AD21-4DAC-9B35-9D2C94F07410 V1 EN
After creating the GOOSE data sets, define the data attributes for the data sets.
• 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 20 data attributes can be added to a single GOOSE data set. If
the configured published data set is larger, it is not accepted by the IED.
GUID-DBE065FB-C0C0-428A-A0A1-53F8D76C4025 V1 EN
Data set entries for vertical reporting are selected using the
data object level, and entries for GOOSE using the data
attribute level.
After defining the data attributes for the data sets, configure the GOOSE control
block properties.
1. Select the IED node on the IEDs tab in the navigation pane.
2. Select the GCB Data tab in the editor pane.
GUID-2371BB88-B680-4B2D-97BE-549B96E0DAD5 V1 EN
3. To add a new GOOSE control block, right-click the area containing the
existing GOOSE control blocks and select Insert new row.
GUID-CA85B312-AD8E-4BF0-9AFB-95171B1A4962 V1 EN
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-1F5C7FB1-7245-4678-8770-C694F6F92DB7 V1 EN
GUID-03B82AE4-9034-4ABE-8C70-895540390802 V1 EN
1. 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 IEDs available as GOOSE clients, that is, “receivers”. If
the client IED is not on the same subnetwork as the GoCB sender, it cannot
be configured as a client.
GUID-7D77C426-F847-4C7B-A8A4-852F6C9A8284 V1 EN
GUID-E55A0037-FDF2-4660-BE14-908D4AD1AAEA V1 EN
GUID-B79CE7B6-A074-491C-B34A-BC9F404F0016 V1 EN
GUID-653B6F22-8ACA-43D5-B227-2044A8BDD637 V1 EN
3. Go to the Project Explorer view and select the Plant Structure tab.
4. Right-click the project and select Import.
GUID-18929C30-EF49-4342-9B99-A6D1DBEF7A7D V1 EN
GUID-1EDEA175-63B8-4681-A067-66A797AD204C V1 EN
7. Click Import.
1. In PCM600, open Project Explorer and select the Plant Structure tab.
2. Add the GOOSERCV function block with the Application Configuration tool.
PHIPTOC_BLK
GOOSERCV_BIN PHIPTOC1
OUT BLOCK OPERATE PHIPTOC1_OPERATE
VALID ENA_MULT START PHIPTOC1_START
GUID-E9DCA896-69D8-4CAB-9E0A-766E26D4584D V1 EN
GUID-340E122B-E72E-4C70-90F5-DE15975CFFCF V1 EN
During the IED startup phase, the IED keeps the value of the
output VALID as “1” until the communication is activated.
After the communication is activated, the value of the output
VALID is updated by the value received via the communication.
If the data type does not match with the GOOSERCV function
block, the attribute cell is red.
In Signal Matrix, the received GOOSE data can be directly connected to the
IED application. The GOOSE inputs are shown on the Binary or Analog
Inputs sheets and they can be connected to the application receiver function
blocks. The columns represent publisher data and the rows represent the
possible subscriber input points.
If the data type, for example timestamp, is not supported by the IED
application, the attribute column is red. The quality attribute is automatically
incorporated in the application with the status value, and it is not seen in
Signal Matrix.
7. Save the changes made in Signal Matrix.
8. Write to the IED.
A GOOSE frame is not accepted if the Needs Commission bit is set. A frame with
the Test bit set is only accepted if the receiving IED is also in the test mode. The
Test bit is active in the sender if the IED is set to test mode.
See the technical manual for more information on the test mode.
The GOOSE frame is also not accepted if the ConfRev deviates from the one in the
configuration. These error situations can be observed in the GSEGGIO1 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 IED 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 IED is considered to be in a time-out state.
If a peer device sends the data including the quality attribute, the receiver IED
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.
If there are no GOOSE-related data changes, the IED 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 to be "fail-safe" values. For example, the IED should use an
enabled signal for interlocking and a blocking-type signal for protection.
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.
If one IED application function block input receives several signals from several
IEDs, 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 IEDs. 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.
GSEGGIO1.Alm can also be used on the application side as an input in the Signal
Matrix Tool's Binary Outputs sheet (signal GSEGGIO ALARM). For example, it is
possible to change the setting group in case one or several IEDs are disconnected
from the network.
TRUE
Dataset Error
Counter +1 Reset Receiver
Timer
Receiver Timeout
Counter +1
FALSE
TRUE Configuration
Configuration Revision
Revision
Mismatch Counter +1
Mismatch?
FALSE
FALSE
State or Sequence
Number Error Counter
+1
TRUE
Same State Number As
Previous Message?
FALSE
FALSE
Test Bit Set?
TRUE
Device In Test
Mode?
FALSE
GUID-261D823E-C0F6-44D3-AEA4-A3F3BC447107 V2 EN
FALSE
TRUE
Bad quality=
INVALID | RESERVED |QUESTIONABLE |
OVERFLOW | OUT-OF-RANGE | BAD-
Target data value is TRUE REFERENCE | OSCILLATORY | FAILURE
defaulted and quality set Quality is bad?
| INCONSISTENT | INACCURATE
to invalid.
FALSE
TRUE
TRUE
Operator blocked? Old data?
FALSE FALSE
FALSE
FALSE TRUE
Receiver in test mode? Test bit enabled?
TRUE FALSE
GUID-00279711-E690-4D18-B871-B7758AF71A74 V2 EN
The default IED SCL contains four default client definitions, “Client1”...”Client4”,
which are used by all the RCBs.PCM600 does not show these clients in the plant
structure, but the IEC 61850 Configuration tool shows the clients in the client-
server communication.
MicroSCADA and COM600 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 PCM600.
6.1.1 Adding new IEC 61850 clients for the IEC 61850
Configuration tool
Adding a new IEC 61850 client to a PCM600 project is a two-step operation. First,
a new generic IEC 61850 IED object must be created under the plant structure and
the relevant client ICD or CID file must be imported to the generic IEC 61850 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.
GUID-1191B786-944A-42A2-9C16-A6DA83DC8EED V1 EN
GUID-81C82DBA-330B-4000-A206-0C4FFBDB333F V1 EN
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.
GUID-D6C8D4FB-0E38-499D-95D8-2D21099F974F V1 EN
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.
1 2 3 4 5
9 10
GUID-611AEE28-1D17-4400-80BD-8E5054C35752 V1 EN
GUID-3D82B39F-D86C-4E99-9AB7-DC3105E6DFE6 V1 EN
GUID-FF5A846C-7D78-4D14-940D-39D1EFF4B724 V1 EN
GUID-26238804-9DF2-4C37-ADC9-65FD63E3DB1D V1 EN
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.
GUID-A87A216E-73AA-4872-8E4D-CA5A8180C92E V1 EN
After creating the GOOSE data sets, define the data set entries (data attributes) for
the data sets.
6.3.1 Defining data set entries with the IEC 61850 Configuration
tool
GUID-BAFE3D00-238E-4187-8B89-3CBF9F1A91D4 V1 EN
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.
Normally, data set entries for vertical reporting are selected using
the data object level and entries for GOOSE using the data attribute
level.
GUID-184CB65D-000A-4825-965A-406BF345C7AB V1 EN
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.
GUID-1A63962B-21A7-48DE-9A09-4BE1F7C25813 V1 EN
7. Edit the properties and options of the created report control block.
GUID-116AC0C2-FAF8-4569-B34F-4F03863156BD V1 EN
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.
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.
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 PCM600.
3. To add or remove clients for a report control block, click the check-box in the
grid, corresponding to the client and RCB.
Four clients at the maximum can be connected to a RCB.
1 2
GUID-354976C3-2B17-4C71-B271-FDBDDABB61F4 V1 EN
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 61850 Configuration tool does not support engineering of
the substation section. Instead, for example, IET600 can be used for engineering, if
needed.
When the IED configurations are changed using IET600, some preparations are
required when a project is started and the IED data model is imported to the tool
for the first time.
• The default IED SCL export from PCM600 contains four default client
definitions, “Client1”...”Client4”, which are used by all the
RCBs.MicroSCADA and COM600 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 61850 subnetwork in the Communication tab.
• Create the bus connections for the IEC 61850 clients.
GUID-083FEE42-5F0A-4923-9B7B-BF1BBC942DF8 V1 EN
4. Type the name of the client IED as it is in the file to be imported. Click OK.
GUID-52A26016-FC38-4667-B166-611041FBD3BE V1 EN
GUID-25139ACD-D2B3-4DBC-AA7D-283E7CCA4AF5 V1 EN
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-A3ED029A-C586-4086-AEAA-B51E30ADFB31 V1 EN
GUID-EA889F86-E189-4890-8308-5EB713778999 V1 EN
Figure 55: Defining bus connection properties for IEC 61850 clients
IET600 user interface is divided into sections, that is, panes for navigating and
displaying the project data.
1 2 3 4 5
GUID-BF4EEBB5-E579-4097-9EAB-8D1652C838A4 V1 EN
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.
GUID-BFF7C150-0493-4198-A881-FA68C17CD16B V1 EN
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.
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
IED. 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.
GUID-E36C02C9-E01B-4575-98AB-ED7B180DE17D V1 EN
GUID-6C0A7FE7-3C60-49AF-91D5-4BB69F6D707D V1 EN
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)
1 2 3
GUID-410C53C5-F990-4944-927D-3857E19B3AA9 V1 EN
1 Grid
2 Selection lists
3 List of data entries
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.
Data set entries for vertical reporting are selected using the data
object level, and entries for GOOSE using the data attribute level.
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.
GUID-1B103FB6-9FE2-4095-9F94-88F1F07FA284 V1 EN
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.
GUID-3CCC1EE1-6916-4A9A-9EA2-959D23282E1C V1 EN
• 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.
There are also buttons to allow semi-automatic configuration of default clients and
RCB clients.
GUID-EB4EE24C-111F-45E7-BFC4-FF6A1DB93F3F V1 EN
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
Section 8 Glossary
www.abb.com/substationautomation