P246 IEC61850 Handout

Substation Communication
P246 IEC 61850 for Power

Utility Automation
ABB Oy Distribution Automation

NAME RESP.DEPT. PREPARED
P246 IEC 61850 for Power Utility Automation FISUB/RAS 27.08.2018 P.K.
COURSE ID LANGUAGE CHECKED
P246 En
REVISION APPROVED
2.0
 ABB Oy P246 EN
Table of contents
1 General Information
2 Introduction and data model
3 Exercise 1: Data model
4 Services and GOOSE
5 Ecercise 2: GOOSE
6 Exercise 3: GOOSE testing
7 Process bus, IEEE1588 and

VLAN
8 Exercise 4: Process bus,

IEEE1588 and VLAN
9 Vertical communication
10 Exercise 5: Vertical
communication
11 Redundancy
Contents of chapter 1
1 General information
1.1 Course schedule
1.2 Notice
P246 IEC 61850 for Power Utility Automation
Course schedule
Day 1
9:00 Intro
Data model
10:15 Exercise1. Data model
10:30 Break
10:45 Services and GOOSE
11:15 Exercise 2. GOOSE
11:55 Lunch
13:00 Exercise 2. GOOSE cont.
Exercise 3. GOOSE testing
14:30 Break
14:45 Process bus, IEEE1588 and VLAN
15:15 Exercise 4: Process bus, IEEE1588 and VLAN
16:00 End of the day
Day 2
09:00 Exercise 4: Process bus, IEEE1588 and VLAN cont.
10:00 Break
10:15 Vertical communication
10:45 Exercise 5: Vertical communication
11:55 Lunch
13:00 Exercise 5: Vertical communication cont.
14:15 Break
14:30 Redundancy
16:00 End of the course
Notice
These documents have been assembled and produced for

educational purposes. The contents of your course binder will not be
updated to include future amendments.
We appreciate your comments on our course documents. On the

basis of practical experience and your feedback we can improve our
courses in the future.
The information in this document is subject to change without notice

and should not be construed as a commitment by ABB. ABB
assumes no responsibility for any errors that may appear in this
document.
This document and parts thereof must not be reproduced or copied

without ABB’s written permission, and the contents thereof must not
be imparted to a third party nor be used for any unauthorized
purpose.
Participation in a course is not only passive receiving of information

but it requires activity on your part. Our courses contain several
practical exercises. Make use of these opportunities to test and
acquire familiarity with the equipment and aids used.
As a user of our training equipment, you must read and follow

carefully the safety instructions.
In no event shall ABB be liable for direct, indirect, special, incidental

or consequential damages of any nature arising from the use of this
document, nor shall ABB be liable for incidental or consequential
damages arising from the use of any software or hardware described
in this document.
With best wishes for a rewarding course.
ABB Oy Distribution Automation

Training Team
Copyright © ABB Oy Distribution Automation

2 Introduction and data model

EVENT, DATE
IEC61850 in Substation Automation

Th1. Intro and data model
Welcome!
Is this what you expected?
Course object: IEC618500 In

Substation Communication
Course goal: Get to know, configure

and test
Course content:
– IEC61850 standard description
– GOOSE and SV configuration
– Client-Server configuration
– Redundancy and Time Sync
– Testing and troubleshooting
Course
Practicalities
• Lunch around 12
09:00 – 16.00 o’clock
• Need a break? Take
one!
• Participate
Relion® for you • Learn & share
• Ask questions
IEC61850 Intro
Situation before IEC61850
Many communication protocols:

Modbus, SPA, LON, Profibas,60870-
5-103, DNP…
Even “International” protocols have

deviations in implementation
depends of vendor
Quite difficult to build the system

using multi-vendor environment
IEC61850 Intro
Basic IEC61850 Principles
Interoperability Free configuration Long term stability

The ability of IEDs from The standard shall The standard shall be
one or several support different future proof, i.e. it must
manufacturers to philosophies and allow be able to follow the
exchange information a free allocation of progress in
and use the information functions e.g. it must communication
for the their own work equally well for technology and the
functions centralized (RTU like) or evolving system
decentralized (SCS like) requirements
systems
IEC61850 Intro
Standard benefits
Internationally accepted protocol

standard for “communication
networks and systems in
substations”
Not only a communication protocol,
so It also affects system building,
tools and configuration
The main difference to previous
communication standards is the
standardized modeling and naming
for Data
Defines a set of communication
services
IEC61850 Data model
Logical Nodes, general information
Object where standardized data for

communication are grouped in
according to their relationship to
application functions
The logical nodes may be seen also
as containers containing the data
provided by a dedicated function for
exchange (communication).
LLN0 and LPHD are special and
contains generic information about
relay
There are only LNs in the structure
that are used in application – so
data structure always depends on
application
IEC61850 Data model

Logical Nodes, naming
The name of the logical node is than PHHPTOC1

the label attached to this container
telling to what function the data CBXCBR1
belong. DARREC1
Every LN in application consist of:
– LN Prefix: vendor and application
SCHLCCH1
specific information, optional CMMXU1
– LN Class: defined in standard, is a MVGAPC2
must part of LN name. Contains 4
characters SSCBR1
– LN instance ID: application
specific, must be
First character of LN class defines
the purpose of the function
IEC61850 Data model
Logical Nodes, groups
Most common LN groups:

– P: Protection
– M: Metering and measurement
– S: Supervision and monitoring
– X: Switchgear
– R: Protection related functions
– L: System
– G: Generic
– C: Supervisory control
Full table can be found in IEC61850-7-4, c.5
IEC61850 Data model

Data attributes and data objects
Data attribute(DA) is the lowest part

in data model which actually
contains values.
Data object(DO) contains defined
set of DAs represents some function
behavior
LN contains defined set of DO
In the example:
Str is DO, represents all DA belong
to PHHPTOC1 start/pick-up
General is DA contain status of IEC61850-7-3 defines common data classes
protection start. Can be TRUE or
FALSE
t is DA and represent the last change
time
IEC61850 Data model
Functional Constraint(FC)
From an application point of view,

the data attributes are classified
according to their specific use; for
example, some attributes are used
for controlling purposes, other
attributes are used
for reporting and logging,
configuration, others indicate
measurements or setting groups,
or some identify the description of a
specific data attribute.
IEC 61850-7-2 contains list of FC
value
IEC61850 Data model

Logical device
A logical device is mainly a

composition of logical nodes and
additional services.
The grouping of logical nodes in
logical devices is based on common
features of these logical nodes.
Standard doesn’t define names and
rules for LNs allocation. So those are
vendor specific.
IEC61850 Data model
Most used Common Data Classes (CDC)
SPS = Single point status (read only 1-bit)

DPS = Double point status (read only 2-bits)
INS = Integer status (read only integer value)
ENS = Enumerated status(usually from monitored values)
ACT = Protection activation information (TRIP)
ACD = Directional protection activation information (START
SPC = Controllable single point with status (writable and
readable 1-bit)
INC = Controllable Integer with status (writable and
readable)
DPC = Controllable Double point status (writable and
readable 2-bits)
MV = Measurement value (magnitude)
CMV = Complex measurement value (magnitude and angle)
WYE = Phase-To-Ground measurement (6 x CMV objects)
DEL = Phase-To-Phase measurement (3 x CMV objects)
IEC61850 Data model

Complex view
3 Exercise 1: Data model

—
Exercise1: Data model
Task
Get to know how to find data in Point List Manual:

IEC 61850
Data model exercise
Step 1.1 Find documentation

There’re several resources and ways to find IEC61850 point list manual:
– Related product page
IEC 61850
Data model exercise

– Find on hard drive if related Connectivity package is installed. For
REF615 usually it is available in folder C:\Program Files
(x86)\ABB\Connectivity
Packages\Documentation\615_IEC\5.1.2\Documents\EN\IEC
NOTE
– Last letter represents FW version. In this example “L” is related to 5.0
FP1.
IEC 61850
Data model exercise

– Open from PCM600 if relay is on the project and documentation
package is installed
IEC 61850
Data model exercise
Step 2.1 Find address for PHHPTOC1 start

– Open Parameter List Manual
– Using CTRL+F combination search for PHHPTOC1 chapter. It won’t be
first search result and you need to find this one:
IEC 61850
Data model exercise
Step 2.2 Find address for PHHPTOC1 start

– Scroll down and find signal description Start
– Related address in IECName column represent status of PHHPTOC

start signal and it is LD0.PHHPTOC1.Str.general. Where LD0 is Logical
Device(LD), PHHPTOC1 is Data Object(DO) and general is Data
Attribute(DA). From the same table you can get that
LD0.PHHPTOC1.Str.general belongs to ST(Status) Functional
Constrain(FC).
IEC 61850
Data model exercise
Step 3.1 Find another signals

Same way as in step 2 find IEC Names for following signals and write
them down:
– CBXCBR1 Apparatus position indication
– ARCSARC1 Fault arc detected
– CCBRBRF1 Backup trip
IEC Name FC
CBXCBR1, App pos ind
ARCSARC1 Fault arc detected
CCBRBRF1 Backup trip

4 Services and GOOSE

EVENT, DATE

Th2. Services and GOOSE

Services
There are different services working with the data and files. The list of most
important:
– GOOSE: transferring messages between IEDs
– Reports: send events to clients(SCADA, RTU etc)
– Sampled values: data stream of currents and voltages
– Control: operate devices
– File transfer: transfer for parameters, configuration, DRs
– Read/Write: direct read and write values
Client-server vs spontaneous services
IEC 61850 Data Model (Objects, Services)
Sampled
Client -Server GOOSE
Values
Mapping
MMS Real time

Communication
TCP
IP
Ethernet Link Layer with VLAN and Priority tagging
Ethernet Physical Layer, 100Mb/s

GOOSE backgroud
GOOSE - Generic Object Oriented Client -

Substation Event server
Part of the international IEC 61850 Data for

GOOSE
standard for substation exchange
communication networks and

systems.
Sampled
values
GOOSE general
Horizontal communication Network

– Used to broadcast messages to control centre
MicroSCADA
peer IEDs in a substation Pro
Transmits any kind of data between Station

the IEDs. Automation
Series
COM600
Requires a station bus with Ethernet Station bus IEC 61850

technology

GOOSE benefits
Reduces wiring between IEDs

Automatically supervised connections
– Connection failures are always detected
– Data quality sent to peer IEDs along with event to enable data validation
More I/O without hardware changes or additions
Performance
Expandability
– IED retrofit installations with only small wiring changes
– New functionality can be introduced
Flexibility
– Possibility to easily add functionality afterwards
– IEDs can share unused I/O
The standard includes a concept for signal testing
GOOSE data exchange
T max Data T min T max

e.g. change e.g. e.g.
10s 2 ms 10s
The GOOSE communication link between IEDs is supervised by sending data

cyclically
When a data change is detected by an IED, the event is immediately sent to

the network multiple times to ensure reception of data
In case of a timeout, the application and the user are notified

GOOSE Performance Requirements
GOOSE response time requirements from application to application

according the standard (IEC 61850-5) are:
– Type 1A (tripping)
• Class P2/3: <3ms (P2/3 = transmission)
• Class P1: <10ms (P1 = distribution S/S)
– Type 1B (others)
• Class P2/3: <20ms
• Class P1: <100ms
ABB MV devices supporting Type1A class P2/3:
– Relion 611/615/620/630/640/
ABB MV devices supporting Type1A class P2/3:
– Relion 630, RIO600
ABB MV devices supporting Type 1B ClassP1:
– RED500(REF,REM,RET 541/543/545) with SPA_ZC400 adapter
GOOSE data transmission
NCC
Switch
Switch Switch
Control & Control & Control & Control & Control & Control & Control & Control & Control & Control &
Protection Protection Protection Protection Protection Protection Protection Protection Protection Protection
By using the system configuration tool, the user defines the logical
links between the IEDs
– Data to be sent from an IED to the station bus
– Connection of subscribed signals to an IED

GOOSE vocabulary
Message ID
Data set
Data
attributes
GCB
GOOSE data set
Data set is collection of data we are going to send. For GOOSE messages we
usually collect data from Data Attribute level, one by one. Because if we take
them from FC level, additionally we add attribute t(time), which is useless in
GOOSE

GOOSE data set, quality
Status signal must be always

followed by q(quality) attribute. If
there are several status attributes in
data set – each quality must be
inserted.
GOOSE data set, quality status
IEC61850-7-3 chapter 6 describes quality attributes

GOOSE data set, limitation
Amount of data can be sent by GOOSE depends on the product. Relion 615
may send up to 80 attributes(which means 40 real statuses, because we
always must use q attribute). And it is recommended to use 20 attributes per
data set
GOOSE control block (GCB) properties
With GCB we define GOOSE

message properties:
– APPID: 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 0000...3FFF. If several messages
within the system have same
APPID it will couse errors on
receiver IED

– MAC Address: 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-0CCD-01-00-
00...01-0C-CD-01-01-FF
– VLAN ID: 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.
Recommended values are 2...1001.
– VLAN Priority: Used in networks
supporting VLANs. The priority is
used with network switches. The
default value for GOOSE is “4” and
the value range is 0...7.

– Config revision: 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. PCM600
automatically increments value
every time you send changed GCB
to the relay. First time it will be
100, then 200 etc.
– Min Time(ms): 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.
Min time can't be changed. It is
fixed to 4ms
– Max Timer(ms): Indicates the
background "heartbeat" cycle time
in milliseconds; the default value is
“10 000 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.

Engineering steps
Sender Recipient
1. Create a data set 1. Add GOOSE receiver blocks for
2. Collect data attributes to the the incoming signals
data set 2. Connect the GOOSE receiver
3. Create the GCB blocks to the incoming signals
4. Assign data set to the GCB 3. Create logic for handling new
5. Set up GCB properties signals
6. Mark the recipient (client)
Implementation in 615 series
The common functionality of the

logical device (e.g. data sets, GCB)
must be placed under LLN0

Receiver
The signal type must match the receiver type

GOOSE Publishing
– Required data collected to Data Set which is defined in configuration tool

– GOOSE Control Block (GoCB) encodes the data (stVal and q)
– Addressing (MulticastMAC, APPID, GoID)
– Configuration Revision and IED Test state information
GoCB
Data
Grouped
Multi Dataset
cast
Data
GOOSE
GOOSE
Multi Formating
cast

GOOSE Subscribing
– GOOSE messages accepted from network according addressing

information in configuration
– Check e.g. Configuration Revision and publisher IED Test state information
– Receiver processes the data for the application
GOOSE
RX Dataset handling
Processing
Reliability
GOOSE Value Value Output Signals

Test Test • Digital
ConfRev • Analog
GOOSE Quality
RX timer
5 Exercise 2: GOOSE
—
Exercise2: GOOSE
Task
Configure GOOSE for Relion 615/620 and RIO600

Testing GOOSE messages with ITT600 and PCM600 “Work Online”
feature
GOOSE exercise
Step 0.1 Open PCM600 project

To save our time project with configurations is ready for you.
– Open PCM600 and select File -> Open/Manage Project…
– Select project with name IEC61850_GOOSE and click button Open
Project
GOOSE exercise
Step 1.1 Configure CBFP(circuit breaker failure protection) with 615 and 620
For the first task let’s assume that REF620 in incomer feeder and
REF615 is outgoing feeder. We’ll need to use REF615 CBFP backup trip
signal and send it over the GOOSE to REF620. And on REF620 assign
this signal to CB trip coil.
First, we need to configure GOOSE message on sender side.
– Open REF615 IEC61850 Configuration tool, by right clicking on
REF615 and selecting following from menu
GOOSE exercise
– In the tool click on Create new object button
GOOSE exercise
– Give a name for GOOSE data set(must starts with a letter and max
length is 27 characters). Please also note that all GOOSE must be
placed under LD0.LD0.LLN0, which is default path and, please, don’t
change it.
– Click OK
GOOSE exercise
– Double click on newly created data set
GOOSE exercise
– Append two signals to Data set entries
• LD0.CCBRBRF1.OpEx.general
• LD0.CCBRBRF1.OpEx.q
– Click OK
GOOSE exercise
– Assign GOOSE to REF620 by making a tick
After that PCM600 automatically creates GOOSE control block and now
we need to go to GOOSE Controls section to adjust GOOSE parameters
GOOSE exercise
– Select GOOSE Control Block and open Object properties window if
not opened.
– Change following parameters:

• APP ID to 101x, where x is rack
number.
• MAC Address to 01-0C-CD-01-10-1x,
where x is rack number.
• Max Time to 3000
– Save changes and close the tool
GOOSE exercise
– Open REF620 Application Configuration tool
– Insert New Application
– Name it GOOSE in Object Properties window

GOOSE exercise
– Insert GOOSERCV_BIN function block
into the configuration
– Set user defined name to inserted FB

by right-clicking on it and selecting
related command
– Change the text and press OK
GOOSE exercise
– Add new variables by right-click on FB and selecting following
command
– By the end it should looks like that:

GOOSE exercise
– Go to Protection tab
– Add REF615_CBFP[0]_OUT variable to OR gate connected to

TRPPTRC1(Master Trip 1)
GOOSE exercise
– Go to LED tab
– Make following connections(to invert input, like it is done with LED4

alarm, select input with left click and then right click on it and select
“Invert Signal”):
– Save and close Application Configuration tool

GOOSE exercise
– Open REF620 Signal Matrix tool
– Go to GOOSE tab
GOOSE exercise
– Assign incoming LD0.CCBRBRF1.OpEx.general signal to related
GOOSERCV_BIN
– Save and close to tool

GOOSE exercise
– Open REF620 Parameter Setting tool
GOOSE exercise
– Change LED3 alarm mode to Latched-S
– Save and close the tool

GOOSE exercise
– Write REF615 and REF620 configurations to relays one by one:
–
– Make sure that configurations were successfully sent to relays

GOOSE exercise
Step 2.1 Configure analog GOOSE from RIO600 to REF615

– Open RIO600 IEC61850 Configuration tool
– Double click on AnalogDs_2 data set to open entries

GOOSE exercise

– With button Del delete all entries except those, related to
RESCMMXU1 and in the end it should looks like that:
– Click OK to close window.

– Assign this DS to REF615
GOOSE exercise

– Go to GOOSE controls tab and change GOOSE control block settings
to following:
• APP ID to 102x, where x is rack number.
• MAC Address to 01-0C-CD-01-10-2x, where x is rack number.
• Max Time to 3000
– Save changes and close the tool
GOOSE exercise

– Open REF615 Application Configuration tool assign
GOOSERCV_MV(receiver for measured values) to MAPGAPC1(generic
protection)
– Assign MAPGAPC1 Operate output to LED

GOOSE exercise

– Open REF615 Signal Matrix tool and assign A.res.cVal.mag.f to
GOOSERCV_MV

GOOSE exercise

– Open REF615 Parameters Setting tool and locate MAPGAPC . Change
Start value to 5 and Operate delay time to 1000 ms

GOOSE exercise
Step 2.6 Configure analog GOOSE from RIO600 to REF615 and REF620
– Write REF615 and RIO600 configuration to IEDs from bay level
– Make sure that configurations were successfully sent to IEDs

6 Exercise 3: GOOSE testing

—
Exercise3: GOOSE testing with ITT600 SA Explorer and
Wireshark
Task
Test GOOSE configuration using ITT600 SA Explorer and Wireshark

GOOSE testing exercise
Step 1.1 Testing and troubleshooting GOOSE with Wireshark

– Open Wireshark Tool
– Double click on Ethernet adapter


– Type “goose.appid==0x101x”, where x is rack number and press Enter
After that you will see only GOOSE messages related to CBFP with
APPID = 101x
If everything is configured correctly new GOOSE message should apper
every 3 seconds, which is Max Time you set for GOOSE CB.

– Double click on any frame and check data inside
– When CBFP is not active Boolean date
should be “False”

– Open two tabs in IE and in first select REF615 simulator and in
another REF620 simulator

– Close DC1 and CB for both

– Press “Prevent CB Open” in REF615 simulator
– Add current above 1xIn in REF615 simulator to activate protection


– Check that REF620 CB is in open position
– Go to Wireshark and scroll down and locate group of messages with
almost the same time
As you can see there after the data change the status relay
automatically distribute 5 messages with very short interval and after
that continue send messages with normal Max Time interval

– You can also check data inside GOOSE message and in that case
Boolean value is “True”

– Disconnect Ethernet cable from REF615 and in time below 6 seconds
(2*MaxTime) REF620 LED4 must change color from green to red.
Step 2.1 Testing and troubleshooting GOOSE with ITT600

– Export .scd file from Substation level and give a name and save it on
hard drive.
– Open ITT600 SA Explorer

GOOSE exercise
Step 2.2 Testing and troubleshooting GOOSE

– Import previously saved *.scd
– Open Explore GOOSE tool

GOOSE exercise

– Press “Start Capture” button
– Select Ethernet adapter and press “OK”

GOOSE exercise

– Select RIO from IEDs section
– Double click on the Analog value to add messages to the plot


another REF630 simulator(in this training it is used for RIO600)

– Close DC1 and CB for REF615 and REF630

– Add voltage in REF630 simulator
– Add some currents in different phases to simulate Earth fault


– After that REF615 LED4 must be active. Make sure that “Prevent CB
open” is off
– Go to ITT600 GOOSE analyzer tool and check the plot
7 Process bus, IEEE1588 and VLAN

EVENT, DATE

Th3. Process Bus, IEEE1588, VLANs

Process bus with sampled values of currents and voltages
The relay can act as a merging unit and measure currents and voltages in the
substation and send them as Sampled Measured Values (SMV) over Ethernet.
Other relays in the substation having phase voltage-based functions can
receive the SMVs over Ethernet and use them for the following purposes:
– Instead of physically (VT or voltage sensor) measured phase voltages
– For synchro-check
Most devices on the market use IEC61850-9-2LE which is not part of standard,
but UCA Implementation Guideline for IEC 61850-9-2
The relay uses IEEE 1588 V2 Precision Time Protocol (PTP) with Power Profile
for high-accuracy time synchronization.
Benefits:
– Simplicity (reduces wiring and terminals)
– Flexibility
– Improved diagnostics
– Longer maintenance cycles
Process Bus in Relion
– ABB relays with IEC9185-9-2 support :

• Relion 615
• Relion 620
• SMU615(merging unit)
• REX640
• Relion 650
• Relion 670

Process Bus Example
Raw phase measurements sent with 4kHz sampling rate

Process Bus Example
125μs 125μs 125μs 125μs

9-2 SV Broadcasting GOOSE and MMS 9-2 SV Broadcasting GOOSE and MMS
12,8μs (1)
1 2 3 9 1 2 3 9
2nd IED. 3rd IED … 9th IED

12,8 μs = 160B*8/100Mb/s
Multicasting of sampled … 160B = 160Byte info in SV
values in 160B frame … 1Byte = 8bit
Includes 3xI, 3xU, Io, Uo … 100Mb/s = Bandwidth of Ethernet network
– In 9-2LE and 50Hz system IED has to publish SMV every 250μs, 80 times per
nominal cycle
– For 9-2LE there is bandwidth in 100Mb/s Ethernet for 19 publishers
– Margin for 60Hz and station bus traffic e.g. GOOSE -> 9 publishers
– Fulfills the needs of voltage sharing application

Process Bus configuration in PCM600, sender
Sender:
– Application Configuration tool
– IEC61850 Configuration tool

• Assign to subscriber(s)
• Keep SMV Control Block MAC Address unique within the substation
Process Bus configuration in PCM600, receiver
Receiver:
– Application Configuration tool:
• Receiving all phase voltages and residual voltage
• Receiving line voltage for synchrocheck functionality

IEEE 1588 Time Synchronization
IEEE 1588 (Precision Time Protocol – PTP)

version 2 with Power Profile time
synchronization method enabling 1 μs
high accuracy time synchronization
Required especially in process bus
applications with sampled values using
protocol IEC 61850-9-2LE
IED has a time-stamp resolution of < 4 μs
Grand Master Clock sends once per
second synchronization message to
network as multicast message
Accurate usage of IEEE 1588 requires
hardware level support from all devices in
network
Benefits
– High accuracy (1 μs)
– Reliable
– Ethernet and HSR/PRP compliant
Reliability
– Redundant clock masters
– Backup clock masters (IED level)
– Supervision
Ready for The most demanding

applications
– 1 μs = 1:1000000s
– 1 μs < 0.05⁰

Master-clock Switch as transparent clock IED
t1 t1
t2 t2
IEEE 1588**
***) Time delay in
network between

t3
 t3 
t4 t4
all active
Delay measurement
components has to
be compensated
Sync telegram
August 27, 2018 Slide 10

Boundary clock
The transmission time (latency) in routers and
switches has a measurable effect on the
precision of the time transmission. To correct
such inaccuracies, PTP defines what are known
as boundary clocks.
In a network segment, a boundary clock is the

reference time source (master clock) to which
the subordinate slave clocks synchronize.
Typically routers and switches take on the role
of a boundary clock.
The boundary clock in turn obtains the time

from a higher-level reference time source
(Grandmaster).

The “Best Master Clock” algorithm evaluates the following criteria:

– "Priority 1“
– "Class“
– "Clock Accuracy“
– "Clock Variance“
– "Priority 2"
First the algorithm evaluates priority 1 of the participating devices. The device with the smallest
value for priority 1 becomes the reference time source (Grandmaster). If the value is the same for
multiple devices, the algorithm uses the next criterion and if this is also the same, it uses again the
next criterion.
If all values are the same for multiple devices, the smallest value in the "Clock Identifier" field defines
which device becomes the reference time source (Grandmaster).
The device offers you the option in the settings of the boundary clock to individually define the
values for "Priority 1" and "Priority 2". This allows you to control which device will be the reference
time source (Grandmaster) in the network.
Network Segregation, VLANs example
VLAN ID = 1, MMS to COM600
VLAN ID = 100, GOOSE between all IEDs
VLAN ID = 200, Process Bus
INC OUT OUT OUT BC BR OUT OUT OUT INC

Process Bus detailed guideline
There are detailed information for Process Bus configuration for Relion615
and Relion620 IEC61850 Engineering Guide
8 Exercise 4: Process bus, IEEE1588 and VLAN

—
Exercise4: Process bus, IEEE1588 and VLAN
Task
Configure Process Bus between REF615 and REF620

Configure IEEE1588 on switch and IEDs
Configure VLANs
Process bus, IEEE1588 and VLAN
Step 1.1 Configure Process Bus from REF615 to REF620

– Open REF615 Application Configuration tool
– Add SMSENDER function on Communication tab


– Open REF615 IEC61850 Configuration tool
– Open Process Bus Communication section
– Assign Process Bus data set to REF620


– Go to Sampled Values Controls tab
– Change properties to following:

• MAC Address: 01-0C-CD-04-10-3x, where x is rack number
• VLAN ID to 2


– Open REF620 Application Configuration tool and make following logic
on Communication tab
– Assign ULTVTR1_ALARM and ULTVTR1_WARNING variables to LEDs


– Open REF615 Parameter Setting tool, locate Time settings and
change Synch source parameter to IEEE1588

– Repeat that step for REF620

– Write REF615 and REF620 configurations to relays one by one:
–
– Make sure that configurations were successfully sent to relays

Step 2.1 Configuring Ethernet switch

– Open AFS View-CT 3.0 tool
– Type Ethernet switch IP(can be found from the sticker on it) and
press Enter

– Write credentials:
• User Name: admin
• Login: abbadmin
– Click OK
– After that click Login

There is no IEEE1588 GPS in the classroom, so switch will take role of
Master Clock.
– Locate Time settings for PTP

– Switch Operation On and select PTP mode to v2-boundary-clock
– Click Set button


– Select Boundary Clock settings and change Priority 1 to 1
– Click Set

– Go to Switching -> VLAN -> Configuration

– Press Create button
– Type 2 and click OK


– Assign ports 4,5 and which are REF615, REF620 and PC ports to
VLANID 2. Use T option, which means Tag
– Click Set
Step 3.1 Testing

– Check that Time Sync is OK. Go to Local HMI settings menu, than go
inside Monitoring -> IED status -> Time Synchronization:
• Synch source must be IEEE 1588 slave
• Synch status must be Up
Step 3.2 Testing

– Export scd file from PCM600 and import it to ITT600.
– Open Explore SV tool
– Select Ethernet adapter and press Start capturing button

Step 3.2 Testing

another REF620 simulator
Step 3.3 Testing

– In REF615 simulator add some voltage and check in REF620
measurements Voltage is the same
– Add some current in REF615 simulator
– Open ITT600 Explore SV tool and check that Currents and Voltages
are the same (note, that in the tool Voltages values are Ph-Ground,
but in IED measurements menu are Ph-Ph)
– Change REF620 cable from 5 to another port.
– Check from REF620 LEDs that GOOSE is still OK, but SV are missing. It
is because another port is not a part of VLAN “2”
9 Vertical communication
EVENT, DATE

Th4. Vertical communication, SCL and COM600

Vertical communication, IEC61850-7-2 definition
Reporting and logging meets a number of crucial requirements for event-

driven information exchange. The data transfer models described in this
clause provide mechanisms for transferring data values caused by well-
defined conditions from a logical node to one client or storing the data in a
server's log for future querying.
In contrast to high bandwidth and time-consuming fast reading (polling)
devices for extraordinary event occurrences, the reporting provides
immediate transmission of events.
Reporting is controlled by constraints.
The main characteristics of reporting and logging are:

– timely reports serve as an indication to clients (optionally keeping
sequence-of-events to the client),
– logging of events for later retrieval (sequence-of-events stored in server),
– the impact on network bandwidth is minimized,
– sending reports only when required (controlled by several attributes),
– low-frequency integrity scan and client-initiated general interrogation.

Reporting provides mechanisms to report packed values of instances of a

data object immediately or after some buffer time.
Reporting and logging as well as the basic services of the data model provide
flexible data retrieval schemas, for example:
– change-of-state notification of clients: immediate reports,
– sequence-of-events: keeping reports in sequence or storing and querying
sequences of log entries,
– polling data objects at any time: GetDataValues and GetDataSetValues.

Vertical communication, PCM600 configuration
PCM600 automatically creates Data Sets with all entries and devide them to
several Data Sets.
If standard configuration is used, Report already assigned to Clients, if
configuration is done from scratch, those should be connected to Clients
manually
Content inside DSs can be changed, but do it carefully, because if some entry
is not in DSs – event in event log will not be shown as well.
Same data set entry cannot be used in different reporting data sets.

There are parameters for Report CB on Report

Controls tab
Most of the values are OK by default

Main parameters are:
– Buffer time – max buffer time
– Buffered – if Yes, buffered. If No – Unbuffered
– Cycle Time – how often report is sending when
Cycle triggering option is set to Yes
– Triggering option – define when report should
be send
Vertical communication, buffered/unbuffered reports
There are two classes of report control blocks defined, each with a slightly
different behaviour:
– buffered-report-control-block (BRCB) – internal events (caused by trigger
options data-change, quality-change, and data-update) issue immediate
sending of reports or buffer the events (to some practical limit) for
transmission, such that values of data object are not lost due to transport
flow control constraints or loss of connection. BRCB provides the sequence-
of-events (SOE) functionality;
– unbuffered-report-control-block (URCB) – internal events (caused by
trigger options data-change, quality-change, and data-update) issue
immediate sending of reports on a “best efforts” basis. If no association
exists, or if the transport data flow is not fast enough to support it, events
may be lost.

Vertical communication, control model
The control model provides a specific way to change the state of internal and
external processes by a client. The control model can only be applied to data
object instances of a Controllable common data class (CDC) and whose
ctlModel DataAttribute is not set to “statusonly”. Such data objects will be
referred to as "control objects".
The control model defines the following services:
– Select (Sel) / SelectWithValue (SelVal);
– Cancel;
– Operate (Oper) / TimeActivatedOperate (TimOper) /
TimeActivatedOperateTermination(TimOperTermination);
– CommandTermination (CmdTerm).
SCL structure, control model
The control model provides a specific way to change the state of internal and
external processes by a client. The control model can only be applied to data
object instances of a Controllable common data class (CDC) and whose
ctlModel DataAttribute is not set to “statusonly”. Such data objects will be
referred to as "control objects".
The control model defines the following services:
– Select (Sel) / SelectWithValue (SelVal);
– Cancel;
– Operate (Oper) / TimeActivatedOperate (TimOper) /
TimeActivatedOperateTermination(TimOperTermination);
– CommandTermination (CmdTerm).

Configuration language SCL
Substation Configuration
description Language (SCL)
– Describes all information
exchanged in a substation
communication network
– Configuration tools translate the
IED capabilities to-from SCL
– Enables information exchange
between the IED configuration
tools from different manufacturers
– Secures backwards the
compatibility between different
versions of IEDs and IED
configuration tools
– XML-based
SCL file types
.SSD file: System Specification Description

– For data exchange from a system specification tool to the system
configuration tool
– Describes the single line diagram of the substation and the required Logical
Nodes
.SCD file: Substation Configuration Description (PCM600)

– For data exchange from the system configuration tool to IED configuration
tools
– Describes the complete substation configuration
– This file contains all IEDs, a communication configuration section and a
substation description section

SCL file types
.ICD file: IED Capability Description

– For data exchange from the IED configuration tool to the system
configuration tool
– All capabilities and functionality of the IED:
• logical devices, logical nodes
• data sets
• control blocks
.CID file: Configured IED Description

– For data exchange from the IED configuration tool to the IED
– Describes instantiated, configured IED within a project
– The communication section contains the current address of the IED
SCL SLD section
SLD section describe relation between SLD elements and data structure.
There is no tool in PCM600 to configure it. Can be done in IET 600 or in
Communication tool editor(e.g. SAB600 for COM600)
COM600
General
Key points
The COM600 product is an all-in-one
unit that functions as:
– Communication gateway
– Real-time and historical data
management unit
– Web Human Machine Interface
(WebHMI)
– Automation controller
COM600
Concept
The COM600
uses process
information and
device data,
acquired over
Ethernet or serial
communication
protocol
interfaces to
execute specific
substation
functions and
applications.
COM600
General
Hardware
COM600 is based on ruggedized
mechanics without rotating parts
Well adapted for harsh environments
All connectors and ports are located
on the front panel of the unit
COM600 fulfills the RoHS directive
which restricts the use of certain
hazardous substances in electrical
and electronic equipment
COM600
Engineering
SAB600
Based on the IEC 61850 standard

and PCM600 (ABB’s common tool
for new and existing ABB
protection IEDs)
IED-specific connectivity packages
enable easy integration and use of
COM600 with ABB protection and
control IEDs
– A connectivity package includes
descriptions of the data and
signals available in the IED
– The descriptions are used to
automatically configure the
master communication in the
COM600 gateway
Connection to COM600 using
LAN/WAN
COM600
Software features
Web-browser based HMI Data historian Communication gateway
IEC61131-3 based Logic processor GOOSE Analyzer Tool (GAT) Special extra
- GOOSE
- Analytics
- FDIR
COM600
Features
Communication gateway
Provides gateway functions
for mapping signals
between protection and
control IEDs in industrial or
utility substations and
higher-level systems.
Gathers data from
protection and control IEDs
and from process devices
using different
communication protocols.
COM600
Features
Web HMI functionality
Single Line Diagram (SLD) with

dynamic busbar coloring
Breaker control (opening and
closing of circuit breakers)
Management of alarms and events
Visualization of measurements
(current, voltage, power etc.)
Disturbance/oscilographic record
upload
from IEDs
Parameter setting for IEDs
System supervision, including IEDs
and communication buses and links
Access and user management for
secured authorized access to IEDs
Required for using the Data
historian
10 Ecxercise 5: Vertical communication

—
Exercise5: Vertical communication
Task
Set communication between REF615/620 and COM600

Adjust SLD
Test signals flow with ITT600
Vertical communication
Step 1.1 Test with ITT600

– Open PCM600 IEC 61850 Engineering Tool from Substation level
– Open Client-Server communication
– Check that all DS belong to REF615 and REF620 are assigned to

clients

– Close the IEC61850 Enginireeng tool
– Export scd file
– Open ITT600 and Import scd file there
– Run REF615 simulator
– In ITT600 locate REF615 -> LD0 and connect as Client 1

– Close the IEC61850 Enginireeng tool
– Export scd file
– Open ITT600 and Import scd file there
– Run REF615 simulator
– In ITT600 locate REF615 -> LD0 and connect as Client 1

– You have to get this message
– Click OK to close it

– Open Process Events tab
– You’ll see there a lot of messages, because when you connect client to
IED first time, relay send all data in Data set
– Clear the view by clicking on Clear List button

– After that close the CB in REF615 simulator
– Check Process Events list. There should be only values that changed
the status

– Change REF615 Control mode to Remote with R/L button on local HMI
– Select CBCSWI1 from the tree and right click on it
– Click Open Command Dialog


– Click Open Switch and confirm by clicking OK

– Exit dialog

– Check that CB is in Open position
Step 2.1 COM600 configuration

– Open SAB600 tool
– Create New Project and name it
– Right click on the top element and create new Gateway


– Write COM600 IP address in properties

– Create new IEC61850 OPC server under the Gateway

– Right click on it and select SCL import
– Select File and open scd you exported from PCM600 before

– Click several time Next and finally press Import

– Open Substation Structure tab
– Expand Q02 bay (which is REF620)
You can see there that Only Q0(CB) has some connections to SLD

– Right click on Q02 and select Data Connection

– First select Q1 and on the left column and DCSWSWI1 from the right
column and press Left arrow

– After that it should be like that

– Same way assign DCSXSWI2 to Q2 and ESSXSWI to Q9

It is done according to the REF620 configuration in PCM600

– Click OK to close Data Connection

– Open Q01 SLD editor
– Move green dot to the right place


– Delete upper dot and line

– Add Outfeeder element

– Click on Direct link and connect Outfeeder to the line

– Click Apply
– Close Editor

– Open Q02 SLD editor and delete all the lines and dots, but not
elements. Arrange elements like that

– Add blue and green dots from Connctions menu as shown on the
picture

– With direct link connect all the elements

– Select Infeed element and right click on it to open Configure Powered
Rules

– Make a rule, that line is considered to be powered when current is
greater than 0 and Apply

– Click Apply to save changes in SLD editor
– Close editor

– Right click on J1 (voltage level) element and create new BusBar

– Open BusBar SLD editor

– Add Busbar start and Busbar end elements
– Click Apply and close the editor


– Open J1 SLD editor

– Arrange elements like on the picture

– Right click on REF615 first and select Connect to Basbar

– Click Connect
– Repeat the same with REF620


– It should look like on the picture. Click Apply to save changes and
close the tool

– Go to Communication tab and right click on Gateway and select
Management

– Go to Communication tab and right click on Gateway and select
Management

– Click Update & reload configuration.

– Open IE and type COM600 IP
– Use following gredentials
• User: COM600
• Password: Training600
– Open REF615 and REF620 simulators
– Check COM600 SLD
11 Redundancy
EVENT, DATE

Th4. Vertical communication, SCL and COM600

Redundancy
Relion 615/620 support 3 types of redundancy topologies:

– RSTP ring topology (requires managed switch, because there no settings for
RSTP on relay side)
– HSR ring (switch is not needs)
– PRP (two separate networks with two managed switches)
With “zero” switchover time (seamless)
– PRP (Parallel Redundancy Protocol)
IEC 62439-3 Clause 4
– HSR (High-availability Seamless Redundancy)
IEC 62439-3 Clause 5
PRP/HSR is a patent of ABB Corporate Research
ABB has assured the IEC to provide licenses throughout the world free of
charge or under reasonable terms
Ring with embedded switches
RSTP
HMI GW
Station to Network
Computer Contr.Center
Protection Protection Protection Protection Portection

& Control & Control & Control & Control & Control
IED IED IED IED IED

PRP: IEC 62439
Sender HMI GW
Station to network
computer control center
HSR:
Communication Telegram A Telegram B
in both ring
directions!
Second telegram
discarded – no
switchover time!
Protection Protection Protection Protection Protection Protection

& & & & & &
Control Control Control Control Control Control
IED IED IED IED IED IED
Receiver
HSR node operation
Sender Receiver
Applications Applications
Upper layers
publisher/ transport layer publisher/ transport layer
Link layer subscriber network layer subscriber network layer
interface
Link send discard send discard
duplicate duplicate duplicate duplicate 7
redundancy
entity (LRE)
Switching logic 3
1 2
(SL)
4
6 5
Ports
A B A B
Transceivers
CCW CCW
CW CW
Send: the LRE sends each frame to send simultaneously over port A and port B (1), (2).
Forward: the switching logic resend frames from one port over the other port (3),(4) except own frames (5),(6)
Receive: the LRE receives both frames, keeps the first frame and discards the duplicate (7).

PRP: IEC 62439
PRP: Connection to Sender HMI GW

two independent Station to network
computer control center
communication
networks!
Telegram B
Second telegram
discarded – no Telegram A Communication
switchover time! system 2
Switch Switch
Communication
system 1
Protection Control Protection Control Protection Control

IED IED IED IED IED IED
Sender

P246 IEC61850 Handout

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

P246 IEC61850 Handout

Uploaded by

Copyright:

Available Formats

Substation Communication

P246 IEC 61850 for Power

ABB Oy Distribution Automation

2 Introduction and data model

3 Exercise 1: Data model

4 Services and GOOSE

6 Exercise 3: GOOSE testing

7 Process bus, IEEE1588 and

8 Exercise 4: Process bus,

These documents have been assembled and produced for

We appreciate your comments on our course documents. On the

The information in this document is subject to change without notice

This document and parts thereof must not be reproduced or copied

Participation in a course is not only passive receiving of information

As a user of our training equipment, you must read and follow

In no event shall ABB be liable for direct, indirect, special, incidental

With best wishes for a rewarding course.

ABB Oy Distribution Automation

Copyright © ABB Oy Distribution Automation

2 Introduction and data model

IEC61850 in Substation Automation

Course object: IEC618500 In

Course goal: Get to know, configure

Many communication protocols:

Even “International” protocols have

Quite difficult to build the system

Interoperability Free configuration Long term stability

Internationally accepted protocol

Object where standardized data for

IEC61850 Data model

The name of the logical node is than PHHPTOC1

Most common LN groups:

Full table can be found in IEC61850-7-4, c.5

IEC61850 Data model

Data attribute(DA) is the lowest part

From an application point of view,

IEC61850 Data model

A logical device is mainly a

SPS = Single point status (read only 1-bit)

IEC61850 Data model

3 Exercise 1: Data model

Get to know how to find data in Point List Manual:

Step 1.1 Find documentation

Step 1.2 Find documentation

Step 1.3 Find documentation

Step 2.1 Find address for PHHPTOC1 start

Step 2.2 Find address for PHHPTOC1 start

– Related address in IECName column represent status of PHHPTOC

Step 3.1 Find another signals

CBXCBR1, App pos ind

ARCSARC1 Fault arc detected

CCBRBRF1 Backup trip

4 Services and GOOSE

IEC61850 in Substation Automation

IEC61850 in Substation Automation

IEC 61850 Data Model (Objects, Services)

MMS Real time

IEC61850 in Substation Automation

GOOSE - Generic Object Oriented Client -

Part of the international IEC 61850 Data for

communication networks and

Horizontal communication Network

Transmits any kind of data between Station