SYMAP_IEC61850

Symap IEC61850 Implementation Specification

- Power Protection - Monitoring - Diesel Control - Power Management

SYMAP

IEC61850 Communication Interface

SYMAP SYMAP_IEC61850_rev3 - 2/29

FOR THIS DOCUMENT WE RESERVE ALL RIGHTS.

WITHOUT OUR CONSENT IN WRITING IT SHALL NOT BE REPRODUCED BY ANY MEANS NOR BE MADE ACCESSIBLE TO THIRD PARTIES. ANY VIOLATION WILL BE SUBJECT TO CRIMINAL PROSECUTION.

THE CONTENT OF THIS MANUAL IS FURNISHED FOR INFORMATIONAL USE ONLY.

THE CONTENT IS SUBJECT TO CHANGE WITHOUT NOTICE, AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY STUCKE ELEKTRONIK GMBH.

STUCKE ELEKTRONIK GMBH ASSUMES NO RESPONSIBILITY OR LIABILITY

FOR ANY ERRORS OR INACCURACIES THAT MAY APPEAR IN THIS DOCUMENTATION.

Version: 12.01.2012 File: SYMAP_IEC61850.doc IEC61850 V.1.4 Firmware:

- CU: 1.10 - MU: 1.10 - RU: 1.10 - IEC61850 1.4



Table of Contents 1 IEC61850 Model Implementation Conformance Statement (MICS) ....................... 4 1.1 Logical Nodes List ...................................................................................................... 4 1.2 Generic Logical Node Mappings ................................................................................. 5

2 Protocol Implementation Conformance Statement (PICS) .................................. 14 2.1 ASCI basic conformance statement .......................................................................... 14 2.2 ACSI models conformance statement....................................................................... 15 2.3 ACSI service conformance statement ....................................................................... 17

3 Protocol Implementation eXtra Information for Testing (PIXIT) .......................... 20 3.1 PIXIT for Association model ..................................................................................... 20 3.2 PIXIT for Server model ............................................................................................. 21 3.3 PIXIT for Data set model .......................................................................................... 22 3.4 PIXIT for Reporting model ........................................................................................ 22 3.5 PIXIT for Generic substation events model ............................................................... 23 3.6 PIXIT for Control model ............................................................................................ 25 3.7 PIXIT for Time and time synchronization model ........................................................ 27



1 IEC61850 Model Implementation Conformance Statement (MICS)

This model implementation conformance statement is applicable for Symap Y(ECG,EC,F,T,M;LD,D);BC(BC,BCG) firmware version CU1.10 and communication version 1.4.

This MICS document specifies the modelling extensions compared to IEC 61850 edition 1. For the exact details on the standardized model please compare the ICD substation configuration file: Symap.icd, version 1.4.

Chapter 1.1 contains the list of implemented logical nodes.

Chapter 1.2 specifies defined mappings of used generic logical nodes to the Symap data points.

1.1 Logical Nodes List

The following table contains the list of logical nodes implemented in the device:

L: System Logical Nodes

LPHD (Physical device information)

LLN0 (Logical node zero)

G: Logical Nodes for generic references

GGIO (Generic process I/O)

M: Logical Nodes for metering and measurement

MDIF (Differential measurements)

MMTR (Metering)

MMXN (Non phase related measurements)

MMXU (Measurement)

X: Logical Nodes for switchgear

XCBR (Circuit breaker)



1.2 Generic Logical Node Mappings

The following table contains the list of generic GGIO Data Object mappings to Symap data points. For any additional information, please refer to the Symap Service manual.

LN DO Symap Identification

GGIO1 SPCSO1 Shunt1

SPCSO2 Shunt 2

SPCSO3 Lockout

SPCSO4 SyncON

SPCSO5 Basic Binary Output Fct 1








SPCSO13 Optional Binary Output Fct 81







GGIO2 Ind10 Basic Binary Input Fct 10

Ind11 Basic Binary Input Fct 11













Ind54 Optional Binary Input Fct 54









GGIO3

Alm1 Programmable alarm status 1


























GGIO3 Alm45 Programmable alarm status 45




















GGIO4 SPCS0330 Programmable command event 330

SPCS0331 Programmable command event 331









GGIO5 AnIn1 Basic analogue input 1

AnIn2 Basic analogue input 2



GGIO6 Ind1 GOOSE subscriber information 1

Ind2 GOOSE subscriber information 2








2 Protocol Implementation Conformance Statement (PICS)

The following ACSI conformance statements are used to provide an overview and details about Symap, with firmware version 1.4 ASCI basic conformance statement,

ACSI models conformance statement,

ACSI service conformance statement

The statements specify the communication features mapped to IEC 61850-8-1.

2.1 ASCI basic conformance statement

The basic conformance statement is defined in Table A.1. Table A.1 Basic conformance statement

Client/ Subscriber

Server/ Publisher

Value/ Comments

Client-Server roles

B11 Server side (of TWO-PARTY-APPLICATION-ASSOCIATION)

Y

B12 Client side of (TWO-PARTY-APPLICATION-ASSOCIATION)

SCSMs supported

B21 SCSM: IEC 6185-8-1 used Y B22 SCSM: IEC 6185-9-1 used N B23 SCSM: IEC 6185-9-2 used N B24 SCSM: other

Generic substation event model (GSE)

B31 Publisher side N B32 Subscriber side N

Transmission of sampled value model (SVC)

B41 Publisher side N B42 Subcriber side N Y = supported N or empty = not supported



2.2 ACSI models conformance statement

The ACSI models conformance statement is defined in Table A.2. Table A.2 ACSI models conformance statement

Client/ Subscriber

Server/ Publisher

Value/ Comments

If Server or Client side (B11/12) supported

M1 Logical device Y

M2 Logical node Y M3 Data Y M4 Data set Y M5 Substitution N M6 Setting group control N Reporting M7 Buffered report control N M7-1 sequence-number N M7-2 report-time-stamp N M7-3 reason-for-inclusion N M7-4 data-set-name N M7-5 data-reference N M7-6 buffer-overflow N M7-7 entryID N M7-8 BufTim N M7-9 IntgPd N M7-10 GI N M7-11 conf-revision N M8 Unbuffered report control Y M8-1 sequence-number Y M8-2 report-time-stamp Y M8-3 reason-for-inclusion Y M8-4 data-set-name Y M8-5 data-reference Y M8-6 BufTim Y M8-7 IntgPd Y M8-8 GI Y M8-9 conf-revision Y Logging N M9 Log control N M9-1 IntgPd N M10 Log N M11 Control Y

If GSE (B31/32) is supported

M12 GOOSE Y Y M13 GSSE



Client/ Subscriber

Server/ Publisher

Value/ Comments

If SVC (41/42) is supported

M14 Multicast SVC N M15 Unicast SVC N

If Server or Client side (B11/12) supported

M16 Time Y M17 File Transfer N

Y = service is supported

N or empty = service is not supported



2.3 ACSI service conformance statement

The ACSI service conformance statement is defined in Table A.3 (depending on the statements in Table A.1).

Table A.3 ACSI service Conformance statement

Services AA: TP/MC

Client (C) Server (S) Comments

Server S1 ServerDirectory TP Y

Application association S2 Associate Y S3 Abort Y S4 Release Y

Logical device S5 LogicalDeviceDirectory TP Y

Logical node S6 LogicalNodeDirectory TP Y S7 GetAllDataValues TP Y

Data S8 GetDataValues TP Y S9 SetDataValues TP Y

S10 GetDataDirectory TP Y S11 GetDataDefinition TP Y

Data set S12 GetDataSetValues TP Y S13 SetDataSetValues TP N S14 CreateDataSet TP Y S15 DeleteDataSet TP Y S16 GetDataSetDirectory TP Y

Substitution S17 SetDataValues TP N

Setting group control S18 SelectActiveSG TP N S19 SelectEditSG TP N S20 SetSGValues TP N S21 ConfirmEditSGValues TP N S22 GetSGValues TP N S23 GetSGCBValues TP N



Services AA: TP/MC


Reporting Buffered report control block (BRCB)

S24 Report TP N S24-1 data-change (dchg) N S24-2 qchg-change (qchg) N S24-3 data-update (dupd) N

S25 GetBRCBValues TP N S26 SetBRCBValues TP N

Unbuffered report control block (URCB)

S27 Report TP Y S27-1 data-change (dchg) Y S27-2 qchg-change (qchg) Y S27-3 data-update (dupd) Y

S28 GetURCBValues TP Y S29 SetURCBValues TP Y

Logging Log control block

S30 GetLCBValues TP N S31 SetLCBValues TP N

Log

S32 QueryLogByTime TP N S33 QueryLogByEntry TP N S34 GetLogStatusValues TP N

Generic substation event model (GSE) GOOSE-CONTROL-BLOCK

S35 SendGOOSEMessage MC Y S36 GetReference TP N S37 GetGOOSEElementNumber TP N S38 GetGoCBValues TP Y S39 SetGoCBValues TP N

GSSE-CONTROL-BLOCK

S40 SendGSSEMessage MC N S41 GetReference TP N S42 GetGSSEElementNumber TP N S43 GetGsCBValues TP N S44 SetGsCBValues TP N N

Transmission of sampled value model (SVC) Multicast SVC

S45 SendMSVMessage MC N S46 GetMSVCBValues TP N S47 SetMSVCBValues TP N

Unicast SVC

S48 SendUSVMessage TP N S49 GetUSVCBValues TP N



Services AA: TP/MC


S50 SetUSVCBValues TP N

Control S51 Select N S52 SelectWithValue TP N S53 Cancel TP N S54 Operate TP Y S55 Command-

Termination TP N

S56 TimeActivated-Operate TP N

File transfer S57 GetFile TP N S58 SetFile TP N S59 DeleteFile TP N S60 GetFileAttributeValues TP N

Time

T1 Time resolution of internal clock 7 nearest negative power of 2 in seconds

T2 Time accuracy of internal clock 10 T0

T1

T2

T3

T4

T5

T3 Supported TimeStamp resolution - 10 nearest negative power of 2 in seconds



3 Protocol Implementation eXtra Information for Testing (PIXIT)

This section specifies the protocol implementation extra information for testing (PIXIT) of Symap IEC 61850 implementation. Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC 61850-10. Each chapter specifies the PIXIT for each applicable ACSI service model as structured in IEC 61850-10.

3.1 PIXIT for Association model

Description Value / Clarification Maximum number of clients that can set-up an association simultaneously

4

TCP_KEEPALIVE value 10 Lost connection detection time 15 seconds Is authentication supported N What association parameters are necessary for successful association

Transport selector N Session selector N Presentation selector N AP Title N AE Qualifier N

If association parameters are necessary for association, describe the correct values e.g.

Transport selector 0001 Session selector 0001 Presentation selector 00000001 AP Title na AE Qualifier na

What is the maximum and minimum MMS PDU size

Max MMS PDU size 10000 Min MMS PDU size 10000

What is the maximum startup time after a power supply interrupt

5 seconds



3.2 PIXIT for Server model

Description Value / Clarification Which analogue value (MX) quality bits are supported (can be set by server)

Validity: N Good, N Invalid, N Reserved, N Questionable N Overflow N OutofRange N BadReference N Oscillatory N Failure N OldData N Inconsistent N Inaccurate Source: N Process N Substituted N Test N OperatorBlocked

Which status value (ST) quality bits are supported (can be set by server)

Validity: N Good, Y Invalid, N Reserved, N Questionable N BadReference N Oscillatory N Failure N OldData N Inconsistent N Inaccurate Source: N Process N Substituted N Test N OperatorBlocked

What is the maximum number of data values in one GetDataValues request

15



3.3 PIXIT for Data set model

Description Value / Clarification What is the maximum number of data elements in one data set (compare ICD setting)

49

How many persistent data sets can be created by one or more clients

20

How many non-persistent data sets can be created by one or more clients

20

3.4 PIXIT for Reporting model

Description Value / Clarification The supported trigger conditions are (compare PICS)

integrity Y data change Y quality change N 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 N entryID N conf-rev Y segmentation Y

Can the server send segmented reports N Mechanism on second internal data change notification of the same analogue data value within buffer period

Send report immediately

Multi client URCB approach Each URCB is visible to all clients May the reported data set contain: - structured data objects? - data attributes? - timestamp data attributes?

Y

Y

Y, will/will not be included in a dchg report

What is the scan cycle for binary events? Is this fixed, configurable

10 ms Fixed



3.5 PIXIT for Generic substation events model

Description Value / Clarification 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 ethernet switch and should not be checked

N source MAC address Y destination MAC address Y Ethertype = 0x88B8 N gocbRef, NULL gocbRef is

considered an error N timeAllowedtoLive N datSet N goID N t Y stNum N sqNum Y test Y confRev Y ndsCom N numDatSetEntries;

numDataSetEntries=0 is considered an error

Can the test flag in the published GOOSE be turned on / off

N

What is the behavior when a GOOSE message with test flag set is received?

The message will be ignored

What is the behavior when the GOOSE publish configuration is incorrect

DUT keeps GoEna=F

When is a subscribed GOOSE marked as lost? (TAL = time allowed to live value from the last received GOOSE message)

message does not arrive by 2x TAL

What is the behavior when one or more subscribed GOOSE messages isnt received or syntactically incorrect (missing GOOSE)

Quality flags of corresponding DOs are set to invalid

What is the behavior when a subscribed GOOSE message is out-of-order

Out-of-order message will be ignored

What is the behavior when a subscribed GOOSE message is duplicated

The duplicate message is ignored

Does the device subscribe to GOOSE messages with/without the VLAN tag?

Y, with the VLAN tag Y, without the VLAN tag



Description Value / Clarification May the GOOSE data set contain: - structured data objects? - data attributes? - timestamp data attributes?

Subscribed Published N N Y Y N N

What is the slow retransmission time? Is it fixed or configurable?

5000 mseconds with TAL = 10000 Fixed

What is the fast retransmission scheme? Is it fixed or configurable?

1) 2 mseconds with TAL = 4 2) 4 mseconds with TAL = 24 3) 16 mseconds with TAL = 9968 4) 5000 mseconds with TAL = 10000 Retransmission scheme is fixed

Can the Goose publish be turned on / off by using SetGoCBValues(GoEna)

Y

TAL = Time Allowed to Live



3.6 PIXIT for Control model

Description Value / Clarification 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 N sbo-with-enhanced-security

Is the control model fixed, configurable and/or online changeable?

FIXED

Is Time activated operate (operTm) supported

NO

Is operate-many supported NO What is the behavior of the DUT when the test attribute is set in the selectwithvalue and/or operate request

n/a

What are the conditions for the time (T) attribute in the SelectWithValue and/or Operate request

DUT ignores the time value and execute the command as usual

Is pulse configuration supported NO What is the behavior of the DUT when the check conditions are set Is this behavior fixed, configurable, online changeable?

N synchrocheck N interlock-check Fixed

What additional cause diagnosis are supported

No additional cause is sent

How to force a test-not-ok response with Operate request?

DOns: n/a SBOns: n/a DOes: n/a SBOes: n/a

Which origin categories are supported? 2 What happens if the orCat is not supported?

DOns: execute as usual SBOns: n/a DOes: n/a SBOes: n/a

Does the IED accept an selectwithvalue/operate with the same ctlVal as the current status value?

DOns: Y SBOns: n/a DOes: n/a SBOes: n/a

Does the IED accept a select/operate on the same control object from 2 different

DOns: Y SBOns: n/a



Description Value / Clarification clients at the same time? DOes: n/a

SBOes: n/a Can a control operation be blocked by Mod=Off or Blocked

N

Does the IED support local / remote operation?

N



3.7 PIXIT for Time and time synchronization model

Description Value / Clarification What quality bits are supported? N LeapSecondsKnown

N ClockFailure Y ClockNotSynchronized

Describe the behavior of the IED when the time synchronization signal/messages are lost

TimeStamp Quality set to ClockNotSynchronized

When is the time quality bit "Clock failure" set?

N/A

When is the time quality bit "Clock not synchronised set?

If no SNTP response is received within 2 seconds after request

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 Y 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 3 and/or 4 N other (describe)


SYMAP SYMAP_IEC61850_rev3 - 29/29 Stucke Elektronik GmbH Merkurring 26 22143 Hamburg Germany

http://www.stuckegmbh.de

Documents

SYMAP_IEC61850