6b-iec61850 - protection schemes

9/26-27/2007

2007 PTUG Meeting, Philadelphia, PA, USA 1

Testing IEC61850 - Enabled Protection S h U i F6150 P S tSchemes Using F6150 Power System Simulators

Jun VerzosaDoble Engineering Company

Doble International Protection Testing Users Group Conference24-28 September 2007Philadelphia, PA, USA

Topic Covered

Brief Introduction to IEC61850 Doble IEC61850 GSE configurator Doble IEC61850 GSE configurator Testing IEC61850-enabled IEDs using

Doble F6150 test systems Configuring IEDs for IEC61850

9/26-27/2007


What Is IEC 61850? International Standard More than a Protocol

A Framework for Substation Automation A Framework for Substation Automation

SubstationLAN

Network

HMI

Borrowed from

Siemens

What Is IEC 61850?IEC 61850 is more than a protocol, its a frameworks for substation automation.

n B

ay

Leve

lSt

atio

nLe

vel HMI

Station Bus

Process Bus (sampled analog

values)Conventional CTs and VTs

Proc

ess

Leve

l

)CTs and VTs with hard wiring are used today

Borrowed from

Siemens

9/26-27/2007


What Is IEC 61850?

The core idea is a description language,The core idea is a description language, that completely describes the data structure and functionality of a substation information system in a standardized manner.

What Is IEC 61850?This standardized language can be understood by devices from different manufacturers ensuring one of the key goals of IEC 61850, Multi-Vendor Inter-Operability.

IEC 61850

y g , p y

Borrowed from

Siemens

9/26-27/2007


Defining DevicesPhysical Devices breakdown into Logical Nodes

PTOC

RREC

XCBR CSWI

Circuit BreakerIndication & Control

Auto Reclosing

Time Over Current

CB1

IED1XCBR

XSWI

MMXU

MMTR Metering

CSWI

CSWI

Borrowed from

Siemens

Measurement Unit

Disconnect SwitchIndication & Control

Indication & Control

Defining DevicesLogical Nodes are grouped inside a Logical Device

PTOC

RREC

IED1Logical Device

The description of the logical device

CB1

IED1XCBR

XSWI

MMXU

MMTR

CSWI

CSWI

(i.e. the IED) is what you will find in

a device description file. (called

ICD)

Borrowed from

Siemens

9/26-27/2007


Accessing DataThink Windows Explorer

PTOC (Time Over Current LN )RREC (Autorecloser LN )

+

+

IED1 IED1IED1/XCBR

RREC (Autorecloser LN )XCBR (Switchgear Circuit Breaker)CSWI (Control - Circuit Breaker)XSWI (Switchgear Disconnect)CSWI (Control - Disconnect)MMXU (Measurement Unit)MMTR (Metering)

+

+

+

+

+

+

+

Borrowed from

Siemens

Accessing DataTree view

PTOCRREC

+

+

IED1/XCBRIED1 IED1/XCBR.Pos

Mode (Mode)Beh (Behavior )Health (Health)Name (Name plate)Loc (Local operation)EEHealth (External equipment)EEName (External equipment name plate)

+

+

+

+

+

+

+

XCBRRREC+

-

OperCnt (Operation counter)Pos (Switch position)BlkOpen (Block opening)BlkClos (Block closing)ChMotEna (Charger motor enabled)CBOpCap (Circuit breaker operating capability)POWCap (Point On Wave switching capability)

+

+

+

+

+

+

+Borrowed from

Siemens

9/26-27/2007


Accessing DataTree view

PTOCRREC

+

+

IED1/XCBR.PosIED1 IED1/XCBR.Pos.stVal

Mode (Mode)Beh (Behavior )Health (Health)Name (Name plate)Loc (Local operation)EEHealth (External equipment)EEName (External equipment name plate)

+

+

+

+

+

+

+

XCBRRREC+

-

OperCnt (Operation counter)Pos (Switch position)

+

-ctlValstValpulseConfigoperTimqmore

intermediate-state (0)off (1)on (2)bad-state (3)

Borrowed from

Siemens

Data Communication using IEC61850Think in terms of Logical Groupings

DN

P 3.

0 (to

EM

S/SC

AD

A

61850LAN

IED 1 Data

67 TOC Pick-up

CB1 is Closed

I Phase A is 200A

V Phase A is 26.3kV

Protection Data

Switchgear Data

Measurement DataCB1

IED1

Borrowed from

Siemens

9/26-27/2007


Data Communication using IEC61850

DN

P 3.

0 (to

EM

S/SC

AD

A HMI LinkageCB pos = IED1/XCBR.Pos.stVal

67 TOC PU = IED1/PTOC.Start.general

IED 1 Data 61850 Messages

Ia = IED1/MMXU.A.phsA.mag

Va = IED1/MMXU.V.phsA.mag

67 TOC Pick-up

CB1 is Closed

I Phase A is 200A

V Phase A is 26.3kV

IED1/XCBR.Pos.stVal (CB pos)

IED1/PTOC.Start.general (67 TOC PU)

IED1/MMXU.A.phsA.mag (Ia)

IED1/MMXU.V.phsA.mag (Va)CB1

IED1

Borrowed from

Siemens

Logical Groupings Devices, nodes, classes and data

Physical Device(network address)

9/26-27/2007


Logical Groupings Devices, nodes, classes and data

LN2(PDIS)

LN1(XCBR)

Pos Op

gen. qstVal q

Logical Device( )

Logical Node(1 to n)

Data Class

Data

Physical Device - server(network address)

Logical Device(IED1)

Physical Device

(1 to n)

Borrowed from

Siemens

Logical node groups

L System LN (2) P Protection (28) R Protection related (10)

M Metering and measurement (8) S Sensor and monitoring (4)

X S it h (2) R Protection related (10) C Control (5) G Generic (3) I Interfacing and archiving (4) A Automatic control (4)

X Switchgear (2) T Instrument transformers (2) Y Power transformers (4) Z Further power system

equipment (15)

Examples: Logical node classes PTOC: Time overcurrent prot. PDIF: Differential protection RBRF: Breaker failure XCBR: Circuit breaker

GGIO: Generic logical node CSWI: Switch controller MMXU: Measurement unit YPTR: Power transformer

9/26-27/2007


Logical NodesThere are 86 Logical Node Classes

Logical Node Groups Group Desig-nator

Number

System Logical Nodes L 2

PDIR Directional elementPDIS Distance protection PSCH Protection SchemePVPH Volts per Hz relayPTUV U d ltProtection functions P 27

Protection related functions R 10Supervisory control C 4Generic References G 3Interfacing and Archiving I 4Automatic Control A 4Metering and Measurement M 7Switchgear X 2

MMXU Measuring (Measuring unit)MMTR MeteringMDIF Differential Measurementsmore

PTUV UndervoltagePDOP Directional over powermore

Switchgear X 2Instrument Transformer T 2Power Transformer Y 4Further power system equipment Z 14Sensors S 3

XCBR Circuit BreakerXSWI Circuit Switch

Unicast vs. Broadcast vs. Multicast

Unicast packets are sent from host to host. The communication is from a single host to another single host. There is one device transmitting a message destined for one reciever

Multicast is a special protocol for use with IP. Multicast enables a single device to

Broadcast is when a single device is transmitting a message to all other devicesin a given address range. This broadcast could reach all hosts on the subnet, allsubnets, or all hosts on all subnets. Broadcast packets have the host (and/orsubnet) portion of the address set to all ones. By design, most modern routerswill block IP broadcast traffic and restrict it to the local subnet.

for one reciever.

communicate with a specific set of hosts, not defined by any standard IP addressand mask combination. This allows for communication that resembles aconference call. Anyone from anywhere can join the conference, and everyone atthe conference hears what the speaker has to say. The speaker's message isn'tbroadcasted everywhere, but only to those in the conference call itself. A specialset of addresses is used for multicast communication.

9/26-27/2007


Logical Node Names

Example for distance LN class PDIS (distance element):

Z1GPDIS1Z1GPDIS1

Logical Node Class Name (fixed)

LN Suffix (free, usually the Instance #)

LN Name Prefix (free, application specific)

Logical Node Class Name (fixed)

Maximum length of LN name = 13 characters

DataThere are 355 Data Classes

Data Classes Number

System information 13Samples of Data Classes

System information 13Physical device information

11

Measurements 66Metered values 14Controllable Data 36Status information 85

Str Starting of a logical node like TOC1 startOp Operation of a logical node like Zn3PDISTr Trip activationPos Switch positionLoc Local operation BlkZn Blocking of correleated PDIS zoneBlkCls Block closing of a Sw or CB

A - Phase to ground amps for Phases 1, 2, and 3Settings 130

355

ase to g ou d a ps o ases , , a d 3Ang - Angle between phase voltage and currentMore..

9/26-27/2007


Examples of Data items:

Z1GPDIS1.Op.General

Data items

[Boolean]Z1GPDIS1.Op.General

Z1GPDIS1.Op.q

[Boolean]

[Quality]

D t tt ib t [t ]Logical node

Data object name

Data attributes and [types]name

M3PGGIO5.Ind08.stVal

Data items - examples

[Boolean]

LP1PSCH1.ProTx.stVal

LP1PTRC1.Tr.General

Bay1XCBR2.Pos.stVal

B 1XCBR2 P

[Boolean]

[Coded Enum]

[Q li ]

[Boolean]

Bay1XCBR2.Pos.q [Quality]

9/26-27/2007


Some Common Data Attribute Types Used in Protection Boolean [ True (1) or False (0) ]

Bit t i [ 0100001000100000 ]

Data Attribute Types

Quality Bitstring [e.g., 0100001000100000 ]

Enum Value

Bit Pairs

Usual Meaning (ex. for CB)

0 0 0 Transition1 0 1 False or Open

Coded Enum (or bit pair)

2 1 0 True or Closed3 1 1 Invalid

[e.g., G-00000000-P-00 ] as seen in Doble Configurator

Quality (special type of bitstring:13 bits)

BayA1/Q0XCBR1.Pos.ctlVal

Addressing a Data item

Data Object Name (fixed)Attribute Name (fixed)

l d lLogical Node Name Suffix (free)

Logical Device Name (free)Logical Node Name Prefix (free)

Logical Node Class (fixed)(free)

9/26-27/2007


3rd Party Tools

IEC 61850 Messaging

Data is communicated between IEDs using Messages called Generic Substation Events ( GSE )

Each message can contain many data items

IEDs publish GSE messages using multicasting to the substation communication network

Other IEDs subscribe to or receive some messages. gIEDs that do not subscribe to the message do not receive it.

9/26-27/2007


IEC 61850 Message Types GSE (Generic Substation Event)

GSSE (generic substation status event) A fixed format only supporting BitPair (or Coded

Enum) data type Backwards compatible with UCA2 GOOSE

UCA2 GOOSE is often confused with IEC61850 GOOSE

GOOSE (generic object-oriented substation event) Much more flexible Much more flexible Multiple messages can be sent from one IED Multiple data attribute types (Boolean, BitString,

Coded Enum, Integer, floating, etc)

IEC 61850 GOOSE message

Fast data exchange method Used for Protection and ControlUsed for Protection and Control Messages are published by multicasting on the

network IEDs subscribe to selected multicast messages Heartbeat messages are sent periodically (60s, 10s,

1s, etc.) under normal conditions When an event occurs, messages are sent multiple

times.

9/26-27/2007


OSM-

Central device withtime synchronization

opticaloptical

IEC 61850 GOOSE MessagingExample

IEC61850 station

optical FibreOSMswitch Cat 5 Cat 5 electricalelectrical

GOOSE MessageGOOSE MessageOCOC--Feed2Feed25050--1 picked up1 picked up OCOC F d3F d3

OC-Feed4ANSI> l k 0 2

Rapid Spanning Tree determines where the ring is logically open

outgoing feedersincomingfeeder

OC-Feed1

OC-Feed2

OC-Feed3OC-Feed4

ggANSIANSI5050--1 picked up1 picked upIEC I> picked upIEC I> picked up

OCOC--Feed1Feed15050--1 picked up1 picked up-- F1F1

p pp pF2F2 OCOC--Feed3Feed35050--1 picked up1 picked up

-- F3F3

>Block 50-2IEC>I>> Block

outgoing feederBorrowed from

Siemens

Voltage and CurrentSignals

Demo on GOOSE message

F6150 Test system

GOOSE Message: Trip

GOOSE Message: Position

VoltagesSignals

1. Simulated faultIED 1

BREAKER

IED 2

ProtectionFunction

Autoreclose / SynchFunctions

2. Trip generated

3. CB New Position

4. Reclose command

GOOSE Message: Reclose

4. Reclose command

5. CB New Position IEC61850 NETWORKS

9/26-27/2007


IEC61850 Documents

Basic principles Part 1

Glossary Part 2

General Requirements Part 3

System and project management Part 4

Communication requirements Part 5

Substation Automation System Configuration Part 6

Basic Communication Structure Part 7

M iPart 9

Sampled Measured ValuesPart 8

Conformance testing Part 10

Mapping to Ethernet

Mapping to MMS and Ethernet

IEC61850 Primary Parts

Part 6-1: Substation Configuration Language (SCL)

Part 7-2: Abstract Communications Service Interface (ACSI) and base types ( CS ) a d base types

Part 7-3: Common Data Classes (CDC)

Part 7-4: Logical Nodes

Part 8-1: Specific Communications Service Mappings (SCSM) - MMS & Ethernet

Part 9-2: SCSM - Sampled Values over Ethernet

10 1 C f Part 10-1: Conformance Testing

9/26-27/2007


Substation Configuration Language SCL (Part 6-1)

Description language for communication in electrical substations related to the IEDs

ICD: IED Capability Description. Description of items supported by an IED.

CID: Configured IED Description. Configuration for a specific IED.

File Types

SCD: Substation Configuration Description. Description of the substation configuration.

SSD: System Specification Description. Description of the system equipment connections.

Parts of A GOOSE Message

Message Header GOOSE Control Reference, GOOSE ID (formerly called App

ID), Dataset Reference (Dataset Name), Revision Number, etc. Multicast MAC Address, VLAN ID, VLAN Priority, App ID

Number

Dataset Items (that belong to a user-defined dataset) Status information, Quality, etc.-----------------------------------------------------------------------

Item no. & details (logical device, logical node, data object)( g , g , j ) Data type - Boolean, Coded Enum (or Bit Pair), Bit String,

Quality ( a special 13-bit string), etc. Value

9/26-27/2007


GOOSE Examples

GOOSE Examples

9/26-27/2007


What is Required in Using F6150 for Testing IEC61850 IEDs ?

F6150 CPU2 with Option F6080 (IEC 61850 messaging support)Option F6080 (IEC 61850 messaging support) Firmware Version 4.25 or later

ProTesT 2.06 or F6TesT 2.17 or later versions Doble IEC 61850 GSE Configurator

OSI LLC Driver for Ethernet (needs to be installed i t )in computer)

Network Switch and cables

Testing IEC61850 IEDs using F6150

Conventional Protection Scheme

TRIP

TT RcvTT Send

52a

52b

9/26-27/2007



Conventional => IEC61850

TRIP

TT RcvTT Send

TRIP 52a 52b

52a

52b


IEC 61850 Implementation

TRIP 52a 52b

9/26-27/2007



Testing with F6150 Power System Simulator

TRIP 52a 52b

Test this IED Simulate the others


Get Configuration Data of IEDs

TRIP 52a 52b

9/26-27/2007



Configure F6150 Instrument for GSE Testing

TRIP 52a 52b


Configure F6150 Instrument for GSE Testing

TRIP 52a 52b

9/26-27/2007



Disconnect Other IEDs to be Simulated

TRIP 52a 52b


Perform Test Using GSE Status Events

Prepare test plansPrepare test plans

Run Tests

9/26-27/2007



Perform Test Using GSE Status Events

Prepare test plansPrepare test plans

Run Tests

SCL Files LaptopImport

ProTesT Available mapped Data items

Discover Messages

9/26-27/2007


SCL Files LaptopImport

ProTesT or

F6TesT

Available mapped

Data items

Discover Messages

Doble IEC61850 GSE Configurator

Supports GOOSE & GSSE

9/26-27/2007


Testing IEDs Set for IEC61850

1. Get IED Configuration Data (IEDs are assumed to be already configured)

2. Configure F6150 Instrument to be able to Receive and Send GSE Messages

Inputs: GN1 GN32 (up to 128 in future) Outputs: GP1 GP32

3. Use GNx and GPx in F6TesT or ProTesT modules or macros.

How do we configure F6150 f GSE i ?for GSE messaging?

9/26-27/2007



Supports GOOSE & GSSE


Configures the F6150 Power System Simulator for GSE MessageSimulator for GSE Message

Subscription (Input or Reception) andPublishing (Output or Transmission)

9/26-27/2007



Define GSE Messages and their Dataset items (payload) - (Discover messages, import SCL files, or

ll t th )manually create them)

Select Dataset items from messages that will be used for testing and

Assign data items to F6150 Inputs andOutputs; define True and False values

Download the Data Items and I/O mappingsDownload the Data Items and I/O mappings to the F6150 - (Configure the instrument)

Observe Live Data Status while testing

Defining GOOSE Messages for Testing with Doble F6150

3 Ways using Doble IEC61850 GSE ConfiguratorConfigurator

Manually Create Messages Discover Messages from IEDs that are

connected to the Network Import from SCL Files (*.ICD, *.CID, *.SCD)Import from SCL Files ( .ICD, .CID, .SCD)

Messages can be manually edited

9/26-27/2007



Manually Create Messages

Click [+] icon

Click GOOSE button



Fill in required qGOOSE Message header information

9/26-27/2007




Add dataset items

Click [+] icon

Enter Item Label Select Data Type and Normal Value

Add more dataset items

TRIP


Discover Messages from IEDs

Click buttonClick button

Wait for Messages to Appear(This will take a few seconds to 2 minutes)

9/26-27/2007



Discover Messages from IEDs

Select a message by clickingDataset items will appear below


Discover Messages from IEDs (dataset items)

Trip A

Trip B

Trip C

Refer to a List of Messages and Dataset Items

Need to identify items.Enter meaningful anduser-friendly labels

9/26-27/2007



Import SCL Files

Select more files as needed

Double click an SCL file or Select and click Open button


Import SCL Files

Imported Messages

Dataset items

9/26-27/2007



Import SCL Files Dataset item details from SCL file

BFI CB1

Trip CB1

CB1 CSw Pos

Enter more user-friendly labels based on SCL details and other available

info; you can use copy, paste, edit.

Select Messages & Dataset Items

Select Message

Check boxes to

select

9/26-27/2007


Assign Selected Dataset items to F6150 Inputs (GNx)

Select an Item

ClickSelected Items are displayed

After Click selected item is added below

GN1 automatically assigned; you can change (GN1 to GN32) Select Compare Sign and Value to compare to.

Select More Messages & Items

9/26-27/2007


Assign Selected Dataset items to F6150 Inputs (GNx)

Select and Add more Dataset Items for F6150 GSE Inputs

Assign Selected Dataset items to F6150 Outputs (GPx)

Select Item Click

GP1 and GP2 automatically assigned; you can change (GP1

to GP32)

Check and Edit True and False Values. F6150 will use these values for simulating output messages.

9/26-27/2007


Download Test Configuration (GNx & GPx) toF6150

Configure and Verify Communication with the Instrument

Go back to the GSE Configuration tab and click

Instrument Confirms Successful Download

Viewing Live Data

Check here to select entire dataset for

viewing

Check here to view only

selected items

Values Update during testingduring testing

9/26-27/2007


Live Data Demo

Using ProTesT or F6TesT with GSE C fi tGSE Configurator

Saving Messages and Test Configuration Files

Substation MessagesFile (*.GSX). Saves

All listed messages All dataset items. User-given Names Ticked checkboxes

Test Configuration File(*.GCX) Saves all substation message

and dataset items; plus Saves mapping of dataset

items for Inputs (GNx) and Outputs (GPx) in F6150

Files can be prepared off line in the office At the substation, the Configuration Files can be

used directly for Download to F6150

Ticked checkboxes Outputs (GPx) in F6150

9/26-27/2007


File Types in GSE Configurator

IEC 61850 SCL Files (ICD, CID, SCD) Are Imported by the GSE Configurator resulting in listing of Messages and th i d t t ittheir dataset items.

DOBLE Files Substation Messages File (*.GSX) contains a list of

available messages and dataset items. Test Configuration File(*.GCX) contains messages

and selected dataset items that are used by the F6150and selected dataset items that are used by the F6150 for inputs (GNx) and outputs (GPx)

Testing IEC61850 Relays or IEDs

9/26-27/2007


Test Setup

Network Switch

Wired Logic I/O?

Can still use wires if needed.

Voltages Currents

GE UR Relay SEL 421 Relay

Testing with F6150 test set l d fi dalready configured

for GSE message subscription and publishing.

9/26-27/2007


ProTesT ZPLBOI

Select Logic Input

ProTesT ZPLBOI

9/26-27/2007


F6150 Digital Inputs (F6TesT)

1 Enter User friendly name1. Enter User-friendly name like TTSend

2. Select GSE Output No.

F6150 Digital Outputs (F6TesT)

1. Enter User-friendly name like CB1.52a

2. Select GSE Output No.

9/26-27/2007


F6TesT Z-Characteristic Testing

Select Input Signal. Corresponding GN number

appears on the right.

Z-Characteristic Testing

9/26-27/2007


State Simulation

Select State Transition Trigger if Needed

State Simulation (Timers & Inputs)

Select Timer Stop Input SignalSense Condition = G appearsAssociated GN input no. appears

9/26-27/2007


State Simulation (Digital Outputs)

Overcurrent Testing

Select Test Triggers / Inputs

9/26-27/2007



Step 1. Discover or Import GOOSE Messages, select data items for use as inputs and outputs; or Open the relevant Saved CFG file

From IED2

- TT Rcv

Open the relevant Saved CFG file

From IED1

- TT Send

- TRIP

From Merging Unit

- CB1_52a

- CB1_52b


Step 2. Connect F6150 (if not yet connected)

Step 3. Configure F6150 for GOOSE I/O messages = Download CFG

Step 4. Disconnect th IED if d d

Step 5. Perform Tests

other IEDs, if needed

9/26-27/2007


Testing IEC61850 Using F6TesT

Define Inputs:

GOOSEGOOSE Subscriptions

Define Outputs:

You can copy names from the GSE Configurator and paste into these tables.

GOOSE Simulations

State Simulation Test SSIMUL1. Pre-fault


1. Pre fault

2. AN Fault

3. AN Fault and TT Rcv goes high

4. Relay Trips => transition to CB TrippingTripping

5. CB is fully Open

6. Post-fault and TT Rcv resets

9/26-27/2007



SelectSelect transition

input


GOOSE Simulations (Logic Outputs)

GPx numbers and User-given names are listed. Check items that will be simulated and specify true/false

conditions on the right.

9/26-27/2007



Timers and GOOSE Subscriptions (Logic Inputs)

Select from user-given names or input numbers like GN1, GN2,GN3,,LN1, LN2, LN3 Sense condition and input number will be displayed

After running the test the results are number will be displayedshown.

Testing IEC61850 Using ProTesT

Timers and GOOSE Subscriptions (Logic Inputs)

Select GNx It is suggested that GNs and their Select GNx Logic Input

ggmeaning be listed in the Timer name or the relay notebook tab for reference; (especially if there are many inputs to choose from)

9/26-27/2007



Select transition

input


GOOSE Simulations (Logic Outputs)

Select GPx Logic Input

9/26-27/2007


Testing IEC61850 IEDs

Selecting GSE Logic Inputs in OTHER Test Macros / Modules

ProTesT

Select GNx Logic Input

ProTesT

Testing IEC61850 IEDs

Selecting GSE Logic Inputs in OTHER Test Macros / Modules

ProTesT F6TesT

Select GNx Logic Input

ProTesT F6TesT

Select Trigger Name Logic Input is

Displayed

9/26-27/2007


Overcurrent Testing

Select Test Triggers / Inputs

Using IEC61850 GSE Configurator

Issues when Discovering and Selecting Messages and Dataset Items

Several datasets can come from a single IED Datasets that you want uses generic GGIO Each dataset can have many items; up to 32, 64, or

more The identity of the dataset item is not known by

looking at the messages; one has to get it from the IED using other software or refer to a prepared list.

9/26-27/2007


How to identify items in a GSE message

Use Software from relay manufacturer Refer to a prepared list of messages and theirRefer to a prepared list of messages and their

dataset items Use 3rd Party Tools (this may not yield complete inftomation)

SISCO AX-S4 MMS KEMA UNICA

th others

Example on How to Identify the Elements Mapped to Dataset Items

This means that Dataset message withmessage with

GooseAppID= OC Tripshas dataset items

Item1 = PHASE TOC1 OP

Item2 = IOC1 OP

Item3 = TOC1 OP

9/26-27/2007



How to Alleviate the Selection Problem (1) During discovery phase, connect only the

IEDs that are of interest, if possible. Select only the the datasets and dataset items

that are relevant for the test plans. Assign meaningful user-given Labels or to the

dataset items of interest. Save it as a Sub (.gsx file) (Sub applies to a whole substation,

a bay, or a single IED. It is possible to delete messages and save a smaller subset. ) You may create several groups of subs.


How to Alleviate the Selection Problem (2) Open the desired saved Sub. For each set of Test Plans define a smaller set

of Inputs and Outputs. Check only data items that are going to be

used. Select and define GSE InputsSelect and define GSE Inputs Select and define GSE Outputs

Save it as a CFG (test configuration file .gcx), using a meaningful filename for easy identification later.

9/26-27/2007


Configuring IEDs for IEC61850

GOOSE Publishing GOOSE Subscription GOOSE Subscription

Configuring IEDs or IEC61850

GOOSE Configuration Tools Software from IED vendors

May be part of IED Setting software or may be a separate software

May not fully support IEDs from other vendors .

Third Party System Configuration Software Third Party System Configuration Software Supports IEDs from All Vendors

9/26-27/2007


SEL - Creating IED GOOSE Message for Publishing (Transmit)

Define DatasetsS l t l t t i l d it i Select elements to include as items in the dataset

SEL - Defining Dataset in IEDs

Specific Logical Nodes Generic Logical Nodes - GGIO

9/26-27/2007


SEL - Defining Dataset in IEDs

AcSELerator Architect

In AcSELerator Quickset software


Define GOOSE Message Select Dataset (payload) to be Select Dataset (payload) to be

transmitted with the message.

9/26-27/2007



IED Name =SEL_421_1

As seen by Doble GSE Configurator

SEL - IED Configuration for GOOSE Subscription (Receive)

drag item

9/26-27/2007


SEL - IED Configuration for GOOSE Subscription (Receive)

In AcSELerator Quickset, map PT1 Rx to CCIN001

GE UR Relay

Supports Both GSSE & GOOSEGSSE & GOOSE

9/26-27/2007


GE Relay GOOSE Setup(Network & Server Configuration)

GE Relay GOOSE Setup(Messages Sent)

Dataset Name = Goose2

GoCBRef = GERly1XfmerProt/LLN0.GO.gcb02

Goose App ID

9/26-27/2007


GE Relay GOOSE Setup(Messages Received)

GOOSE Subscription Configurationfor Remote device CB1

Purpose: Receive CB1 Status values for . 52a, 52b, CB Ready

C GOOSRemote IED CB1 GOOSE message was previously defined for publishing as:

Goose App ID = CB1 52a.q GGIO1.Ind1.q

52a.StVal GGIO1.Ind1. StVal

52b q GGIO1 Ind2 q 52b.q GGIO1.Ind2.q

52b.StVal GGIO1.Ind2. StVal

CB Ready.q GGIO1.Ind3.q

CB Ready.StVal GGIO1.Ind3.StVal

9/26-27/2007


GOOSE Subscription Configurationfor Remote device CB1

Rx msg = GooseIn1

Goose AppID = CB1

Item 1: CB1_52a.q

Item 2: CB1_52b.StVal

Item 3: CB1_52b.q

Item 4: CB1_52.StVal

Item 5: CB1 Ready.q

Item 5: CB1 Ready.StVal

Remote Device m

GGIO1.Ind1.q

GGIO1.Ind1.StVa

GGIO1.Ind2.q

GGIO1.Ind2.SVa

GGIO1.Ind.3.q

GGIO1.Ind3.StVa

Remote device transmits Goose Output using GGIO1; This Local device receives Goose Input uses GGIO3

System Configuration Tools

Support IEDs from multiple vendors Import ICD and/or CID files from multiple IEDs Map Goose subscriptions (input) in an IED to

receive information from other IEDs Create a SCD file for the complete substation

and/or create CID files for individual IEDs Siemens DIGSI 4 ABB Kalki ASE

9/26-27/2007


SEL 421 GOOSE Performance

GE UR Relay GOOSE Performance

D t t 1 2 (Dataset 1: < 2 ms (high speed)

Datasets 2 to 8: < 100 ms

9/26-27/2007


6b-iec61850 - protection schemes

Documents

ptug meeting

description language

key goals of iec

todayborrowed fromsiemens926

icdborrowed fromsiemens926

standardized language

substation information

p yborrowed fromsiemens926