630 series 1.3 IEC 61850 Protocol Implementation ... - ABB

Relion® Protection and control

630 series 1.3 IEC 61850 Protocol Implementation eXtra Information for Testing

Table of content:

1 Introduction ................................................................................................................ 2 1.1 Contents of this document.............................................................................. 2

2 Related documents .................................................................................................... 2

3 PIXIT for Association model ..................................................................................... 3

4 PIXIT for Logical device model ................................................................................. 4

5 PIXIT for Logical node model .................................................................................... 4

6 PIXIT for Server model ............................................................................................... 4

7 PIXIT for Data set model ............................................................................................ 5

8 PIXIT for Substitution model ..................................................................................... 6

9 PIXIT for Setting group control model ..................................................................... 6

10 PIXIT for Reporting model ......................................................................................... 7

11 PIXIT for Logging model ............................................................................................ 8

12 PIXIT for Generic substation events model ............................................................. 8

13 PIXIT for Control model ........................................................................................... 10

14 PIXIT for Time and time synchronization model ................................................... 13

15 PIXIT for File transfer model ................................................................................... 14

Document ID: 1MRS189727 630 series protection and control IED

Issued: 2014-06-10 IEC 61850 Protocol Implementation eXtra Information for Testing

Revision: E

2

1 Introduction

This document serves as the PIXIT document for the IEC 61850 implementation in the ABB 630 Series products.

The intention is to declare how the IEC 61850 is applied and used in the ABB 630 Series, version 1.3. The document is organized according to the IEC 61850 standard and lists the different aspects within the defined scope of this paper.

1.1 Contents of this document

Each chapter specifies the PIXIT for each applicable ACSI service model as structured in IEC 61850-10.

2 Related documents

Document Id Title

IEC 61850-5 (2003) Communication Networks and Systems in Substations – Part 5: Communication requirements for functions and device models

IEC 61850-6 (2003) Communication Networks and Systems in Substations Part 6: Configuration description language for communication in electrical substations related to IEDs

IEC 61850-7-1 (2003) Communication Networks and Systems in Substations Part 7-1: Basic communication structure for substation and feeder equipment – Principles and models

IEC 61850-7-2 (2003) Communication Networks and Systems in Substations Part 7-2: Basic communication structure for substations and feeder equipment – Abstract communication service interface (ACSI)

IEC 61850-7-3 (2003) Communication Networks and Systems in Substations Part 7-3: Basic communication structure for substation and feeder equipment – Common data classes

IEC 61850-7-4 (2003) Communication Networks and Systems in Substations Part 7-4: Basic communication structure for substation and feeder equipment – Compatible logical node classes and data classes

IEC 61850-8-1 (2003) Communication Networks and Systems in Substations Part 8-1: Specific communication service mapping (SCSM) – Mapping to MMS(ISO/IEC 9506 Part 1 and Part 2)



Revision: E

3

Document Id Title

IEC 61850-10 (2005) Communication Networks and Systems in Substations Part 10: Conformance testing

ABB 1MRS189725 630 series ver 1.3 - IEC 61850 MICS; Model Implementation conformance statement

ABB 1MRS189726 630 series ver 1.3 - IEC 61850 PICS; Protocol Implementation conformance statement

ABB 1MRS189728 630 series ver 1.3 – IEC 61850 TICS; Tissue Implementation conformance statement

3 PIXIT for Association model

Description Value / Clarification

Maximum number of clients that

can set-up an association

simultaneously

8

TCP_KEEPALIVE value 5 seconds

Lost connection detection time TCP_KEEPIDLE = 10 s TCP_KEEPCNT = 3 TCP_KEEPINIT = 10 s TCP_KEEPINTVL = 5s 10s after association start to begin sending keepalive, and 15s (3 * 5s) to detect lost connection.

Is authentication supported N

What association parameters are

necessary for successful

association

Transport selector Y

Session selector Y

Presentation selector Y

AP Title N

AE Qualifier N

If association parameters are

necessary for association,

describe the correct values e.g.

Transport selector 0001 (default)

Session selector 0001 (default)

Presentation selector 00000001 (default)

AP Title n/a

AE Qualifier n/a

What is the maximum and

minimum MMS PDU size

Max MMS PDU size 32000 bytes

Min MMS PDU size 128 bytes



Revision: E

4


What is the maximum startup time

after a power supply interrupt

2 minutes

4 PIXIT for Logical device model

Description Value / Clarification LD properties In addition to LD0, other LDs are

used to group LNs that belongs to a certain ‘aggregated’ functionality, for example distance protection.

5 PIXIT for Logical node model

Description Value / Clarification LPL Included, according to definitions

in ICD file. Health Always OK Beh - Supported values are ON,

Blocked, Test, Test/Blocked and OFF. However, the Test, Test/Blocked and OFF can only be set from Local HMI or PCM 600 (IED tool) - Test/Blocked also disables reporting

Mod Only values ON and Blocked are accepted. Other values results in negative response.

6 PIXIT for Server model


Which analogue value (MX)

quality bits are supported (can be

set by server)

Validity:

Y Good,

Y Invalid,

N Reserved,

Y Questionable

Y Overflow

Y OutofRange

N BadReference

N Oscillatory



Revision: E

5


N Failure

Y OldData

N Inconsistent

N Inaccurate

Source:

Y Process

Y Substituted

Y Test

Y OperatorBlocked

Which status value (ST) quality

bits are supported (can be set by

server)

Validity:

Y Good,

Y Invalid,

N Reserved,

Y Questionable

N BadReference

N Oscillatory

N Failure

Y OldData

N Inconsistent

N Inaccurate

Source:

Y Process

Y Substituted

Y Test

Y OperatorBlocked

What is the maximum number of

data values in one

GetDataValues request

Stack does not limit the amount of the data

values. MMS PDU is the limit


data values in one SetDataValues

request

Stack does not limit the amount of the data

values. MMS PDU is the limit

7 PIXIT for Data set model



data elements in one data set

(compare ICD setting)

maxAttributes = 300

maximum FCDAs = 150

-> whatever limit is reached first.

How many persistent data sets No online creation



Revision: E

6

can be created by one or more

clients

How many non-persistent data

sets can be created by one or

more clients

No online creation

8 PIXIT for Substitution model


Substitution Substitution of value is supported. The quality can not be substituted The subID is not used.

9 PIXIT for Setting group control model


What is the number of supported

setting groups for each logical

device (compare NumSG in the

SGCB)

Maximum 4, default value = 1 Same

setting group control block is used in all

LDs.

The amount of setting groups is set in the

configuration.

What is the effect of when and

how the non-volatile storage is

updated

(compare IEC 61850-8-1 $16.2.4)

Editing of setting group is not supported

using IEC 61850

Can multiple clients edit the same

setting group


using IEC 61850

What happens if the association

is lost while editing a setting

group


using IEC 61850

Is EditSG value 0 allowed? Editing of setting group is not supported

using IEC 61850



Revision: E

7

10 PIXIT for Reporting model


The supported trigger conditions

are

(compare PICS)

integrity Y

data change Y

quality change Y (*)

data update N (*)

general interrogation Y/

The supported optional fields are sequence-number Y

report-time-stamp Y

reason-for-inclusion Y

data-set-name Y

data-reference Y

buffer-overflow Y

entryID Y

conf-rev Y

segmentation Y

Can the server send segmented

reports

Y

Mechanism on second internal

data change notification of the

same analogue data value within

buffer period (Compare IEC

61850-7-2 $14.2.2.9)

Send report immediately

Multi client URCB approach

(compare IEC 61850-7-2 $14.2.1)

Each instance URCB is visible to one client

only, (allows also multiple clients on

one/same instance or one client/instance)

What is the format of EntryID Octet string 8

What is the buffer size for each

BRCB or how many reports can

be buffered

50000 bytes for each used BRCB (max.

100 BRCB instances)

Pre-configured RCB attributes

that cannot be changed online

when RptEna = FALSE

(see also the ICD report settings)

- DatSet

- ConfRev

- SqNum

- TimeofEntry

May the reported data set

contain:

- structured data objects?

- data attributes?

- timestamp data attributes?

Y

Y

Y

What is the scan cycle for binary 5 mseconds



Revision: E

8

events?

Is this fixed, configurable

Fixed

Supported FC’s Only functional constraints MX and ST can be included in datasets for reporting

Segmentation properties 1. In buffered reports the the max_pdu_size is stored after first connection to this buffered report. 2. If the reports is released by the client and another client enabling with bigger pdu_size the report still keeps the max_pdu_size set by the first client, which was enabling first. 3. If the reports is released by the client and enabled with smaller pdu_size, buffer is purged and enabled with the smaller size.

(*) accepted by server and will be reported as data-change.

11 PIXIT for Logging model


General Logging model is not supported

12 PIXIT for Generic substation events model


What elements of a subscribed

GOOSE header are checked to

decide the message is valid and

the allData values are accepted?

If yes, describe the conditions.

Note: the VLAN tag may be

removed by a ynchron switch

and should not be checked

N source MAC address

Y destination MAC address

Y Ethertype = 0x88B8

Y gocbRef

Y timeAllowedtoLive

Y datSet

Y goID

N t

Y stNum

Y sqNum

Y test

Y confRev

N ndsCom (value is ignored)

Y numDatSetEntries

Can the test flag in the published

GOOSE be turned on / off

N

What is the behavior when the N/A



Revision: E

9


GOOSE publish configuration is

incorrect

When is a subscribed GOOSE

marked as lost?

(TAL = time allowed to live value

from the last received GOOSE

message)

Message does not arrive prior to 2*TAL,

then the message is marked as lost at the

receiver. (Time allowed to live = MaxTime

as defined in IEC 61850 part 6).

Note that erroneous GOOSE telegrams

are discarded, and valid telegrams are

supervised according to TAL.

What is the behavior when one or

more subscribed GOOSE

messages isn’t received or

syntactically incorrect (missing

GOOSE)

Is ignored. Internal data is set to invalid if time allowed to live times out.

What is the behavior when a

subscribed GOOSE message is

out-of-order

Is ignored

What is the behavior when a

subscribed GOOSE message is

duplicated

Is ignored

Does the device subscribe to

GOOSE messages with/without

the VLAN tag?

Y, with the VLAN tag

Y, without the VLAN tag

May the GOOSE data set contain:

- structured data objects?

- data attributes?

- timestamp data attributes?

Subscribed Published

Y Y

Y Y

Y (*) Y

* not used in applications

What is the slow retransmission

time?

Is it fixed or configurable?

Configured by IED tool (have to be > than

the fast retransmission time, and =<60 000

ms) Can not be set <100ms.

What is the fast retransmission

scheme?

Is it fixed or configurable?

Configured by IED tool (>1ms)

Can the Goose publish be turned

on / off by using

SetGoCBValues(GoEna)

N

Properties of updated

messages/data.

The value, quality and time is handled as

one property, e.g. if one of these changes,

there will be a data update sent for all.

Is AppId required in Goose Y



Revision: E

10


message?

How does the receving IED treat

Goose message with T = true and

needs commissioning?

The received data will be treated as

invalid.

TAL = Time Allowed to Live

13 PIXIT for Control model


What control modes are

supported

(compare PICS)

Y status-only

Y direct-with-normal-security

N sbo-with-normal-security

N direct-with-enhanced-security

Y sbo-with-enhanced-security (only for

DPC)

Is the control model fixed,

configurable and/or online

changeable?

Fixed.

Can be changed for some functions using

the PCM 600 IED tool.

Is Time activated operate

(operTm) supported

N

Is “operate-many” supported N

What is the behavior of the DUT

when the test attribute is set in

the SelectWithValue and/or

Operate request

Test mode is not supported

What are the conditions for the

time (T) attribute in the

SelectWithValue and/or Operate

request

Not supported

Is pulse configuration supported N

What is the behavior of the DUT

when the check conditions are set

Is this behavior fixed,

configurable, online changeable?

Y synchrocheck

Y interlock-check

This is only applicable for CSWI.pos,

otherwise ignored. Note also the both

conditions are checked during operate

phase. When supported, these checks can

not be configured.

What additional cause diagnosis

are supported

Y Blocked-by-switching-hierarchy

N Select-failed



Revision: E

11


Y Invalid-position

Y Position-reached

Y Parameter-change-in-execution

Y/N Step-limit

Y Blocked-by-Mode

Y Blocked-by-process

Y Blocked-by-interlocking

Y Blocked-by-synchrocheck

Y Command-already-in-execution

N Blocked-by-health

Y 1-of-n-control

Y Abortion-by-cancel

N Time-limit-over

N Abortion-by-trip

Y Object-not-selected

How to force a “test-not-ok”

respond with SelectWithValue

request?

Not supported


respond with Select request?

Not supported


respond with Operate request?

Not supported

Which origin categories are

supported?

Bay-Control, Station-Control, Remote-

Control, Automatic-Bay.

orCat is only checked for DPC and SPC

DATA’s for the logical node types

GNRLCSWI, LSHDPFRQ, OLATCC,

SPC8GGIO, VSGGIO and SLGGIO (*).

This means that the check of

Local/Remote switch will only occur for

these attributes.

What happens if the orCat is not

supported?

DOns: Rejected for the above(*)

SBOns: Not Supported

DOes: Not Supported

SBOes: Rejected for the above(*)

Rejected means returning addCause

Blocked-by-switching-hierarchy

Does the IED accept a

selectwithvalue/operate with the

same ctlVal as the current status

value?

DOns: Y


DOes: Not Supported

SBOes: Y



Revision: E

12


- The “position reached” is generated as a cmdTerm. This addCause is not responded for select nor operate.

- For CSWI.pos; To change a 1,1 or 0,0 position requires additionally a interlock bypass, i.e. no interlock check.


select/operate on the same

control object from 2 different

clients at the same time?

DOns: N


DOes: Not Supported

SBOes: N


select/selectwithvalue from the

same client when the control

object is already selected (tissue

334)


SBOes: N

Is for SBOes the internal

validation performed during the

SelectWithValue and/or Operate

step?

The Check synchrocheck/interlock is made

during Operate phase. For others, e.g.

blocked, the evaluation is done during

select phase.

Can a control operation be

blocked by Mod=Off or Blocked

Mod = off is not supported.

Control operation is blocked in Block state

(Y)

Does the IED support local /

remote operation?

Y

Vendor Specific additional cause

diagnosis

(note: all these addCauses have negative value)

- 23 blockedForCommand

- 24 blocked-for-open-command

- 25 blocked-for-close-command

- 30 longOperationTime

- 31 switch-not-start-moving

- 32 persistent-intermediate-state

- 33 switch-returned-to-initial-position

- 34 switch-in-bad-state

- 35 not-expected-final-position

Handling of cancel - Cancel is only accepted in select phase - Cancel is accepted from other clients

(different from the client making a select)

Handling of ctlNum - Is not checked/evaluated by the server



Revision: E

13

14 PIXIT for Time and time synchronization model


What quality bits are supported N LeapSecondsKnown

Y ClockFailure

Y ClockNotSynchronized

Describe the behavior when the

time synchronization

signal/messages are lost

The ABB 630 Series can have 2 configured SNTP Servers. If the first fails, the second is taken into use. There is an automatic switch ‘back’ if an erroneous one comes operable. If all SNTP servers are off-line the event timestamps get ClockFailure and ClockNotSynchronized status. The time to detect error and change to 2nd server is 2 seconds. If no backup server is defined, there is a

timeout of 5 minutes.

When is the time quality bit “Clock

failure” set?

Upon start of the IED, until synchronization is received. As the time system is self-adjusted, the clock failure is set when the estimated deviation exceeds a certain value. Due to the good internal accuracy, this deviation occurs in the order of > 30 days.

When is the time quality bit “Clock

not ynchronized” set?

Loss of time synchronization

Is the timestamp of a binary event

adjusted to the configured scan

cycle?

N

Does the device support time

zone and daylight saving?

Y

Which attibutes of the SNTP

response packet are validated?

Y Leap indicator not equal to 3

N Mode is equal to SERVER

Y OriginateTimestamp is equal to

value sent by the SNTP client as

Transmit Timestamp

Y RX/TX timestamp fields are

checked for reasonableness

Y SNTP version 4



Revision: E

14

15 PIXIT for File transfer model


What is structure of files and

directories?

/COMTRADE/<files>

Is the IETF FTP protocol also

implemented

Y

Directory names are separated

from the file name by

“/” or “\” works for FTP transfer

“/” for MMS

The maximum file name size

including path (recommended 64

chars)

Not defined

Are directory/file name case

sensitive

N

Maximum file size Not defined, free space varies and

depends on size of the configuration.

~800kB.

Is the requested file path included

in the file name of the MMS

fileDirectory respond?

Y

Is the wild char supported MMS

fileDirectory request?

Yes, wild card = * or *.* or empty string

Is it allowed that 2 client get a file

at the same time?

N

FTP authentication Y

Contact us

1MR

S189

727

E ©

Cop

yrig

ht 2

014

ABB.

All

right

s re

serv

ed.

ABB Oy Medium Voltage Products Distribution Automation P.O. Box 699 FI-65101 VAASA, Finland Phone +358 10 22 11 Fax +358 10 22 41094

www.abb.com/substationautomation

630 series 1.3 IEC 61850 Protocol Implementation ... - ABB

Documents

Transcript of 630 series 1.3 IEC 61850 Protocol Implementation ... - ABB