micom p40 agile p341, p342, p343, p344, p345, p346...micom p40 agile p341, p342, p343, p344, p345,...

MiCOM P40 Agile P341, P342,

P343, P344, P345, P346

PIXIT

Protocol Implementation eXtra Information for Testing for the IEC 61850 Interface

Platform Hardware Version: P (P341/2) M (P343/4/5/6) Platform Software Version: 38/72 (P341) 38 (P342/3/4/5/6) Publication Reference: P34x/EN PX/Ia7

© - ALSTOM 2014. All rights reserved. Information contained in this document is indicative only. No representation or warranty is given or should be relied on that it is complete or correct or will apply to any particular project. This will depend on the technical and commercial circumstances. It is provided without liability and is subject to change without notice. Reproduction, use or disclosure to third parties, without express written authority, is strictly prohibited.

MiCOM P40 Agile P341, P342, P343, P344, P345, P346 PIXIT

CONTENTS

1 INTRODUCTION 3 1.1 Contents of this document 3

2 PIXIT FOR ASSOCIATION MODEL 4

3 PIXIT FOR SERVER MODEL 5

4 PIXIT FOR DATA SET MODEL 7

5 PIXIT FOR SUBSTITUTION MODEL 8

6 PIXIT FOR SETTING GROUP CONTROL MODEL 9

7 PIXIT FOR REPORTING MODEL 10

8 PIXIT FOR LOGGING MODEL 11

9 PIXIT FOR GENERIC SUBSTATION EVENTS MODEL 12

10 PIXIT FOR CONTROL MODEL 14

11 PIXIT FOR TIME AND TIME SYNCHRONISATION MODEL 17

12 PIXIT FOR FILE TRANSFER MODEL 18

P34x/EN PX/Ia7 1

PIXIT MiCOM P40 Agile P341, P342, P343, P344, P345, P346

2 P34x/EN PX/Ia7


1 INTRODUCTION

This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 interface. Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC 61850-10.

1.1 Contents of this document

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

P34x/EN PX/Ia7 3


2 PIXIT FOR ASSOCIATION MODEL

ID Description Value/Clarification

As1 Maximum number of clients that can set-up an association simultaneously

16

As2

TCP_KEEPALIVE value The TCP_KEEPALIVE function has been implemented according to part 8 of the IEC 61850 standards and the RFCs which the specification references. Acknowledgements received by the IED to keep-alive messages are not processed. The interval between the keep-alive messages is configurable between one (1) and twenty (20) seconds, with a setting increment of one (1) second. The default interval for TCP_KEEPALIVE messages transmitted by the relay is five (5) seconds. The TCP_KEEPALIVE messages are transmitted for a fixed period of approximately 75 seconds following the last received keep-alive response, after which time the client association will be dropped.

As3

Lost connection detection time The time-out period for aborted sockets is approximately sixty (60) seconds. For the duration of this time-out period the socket resources are unavailable for new client association requests. A total of 100 sockets are available but it should be noted that these resources are shared with other network tasks (for example SNTP time synchronization). If no sockets are available the IED will refuse new association requests from a client. Px40 devices support loss of network link detection and provide the following reporting mechanisms: • Alarm indication • Entry in the event log • No indication

As4 Is authentication supported N

As5

What association parameters are necessary for successful association

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

As6

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

As7 What is the maximum and minimum MMS PDU size

Max MMS PDU size <16,384 bytes> Min MMS PDU size <400 bytes>

As8 What is the maximum startup time after a power supply interrupt

The typical start up time of basic Ethernet services, following an interruption to the power supply is approximately 25 seconds. Full IEC 61850 services are available after an approximate start up time of 90 seconds.

4 P34x/EN PX/Ia7


3 PIXIT FOR SERVER MODEL


Sr1

Which analogue value (MX) quality bits are supported (can be set by server)

Validity: Y 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

Sr2

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

Validity: Y Good, N 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

Sr3

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

Dependant on the negotiated size of the MMS PDU and the total length of all ObjectReferences to be included within the service request. (The total length of all ObjectReferences must be less than the maximum supported MMS PDU size, taking into accounts any relevant header information).

Sr4

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

Dependant on the negotiated size of the MMS PDU and the total length of all ObjectReferences to be included within the service request. (The total length of all ObjectReferences must be less than the maximum supported MMS PDU size, taking into accounts any relevant header information.)

Sr5

Which Mode / Behaviour values are supported

On Y Blocked N Test Y Test/Blocked N Off Y

P34x/EN PX/Ia7 5


6 P34x/EN PX/Ia7


<additional items> Measurement deadbands : MiCOM Px40 IEDs do not have a built in range-limit for measurements, but deadbands are specified as a percentage change based on such a range. To resolve this, each measurement provides a range configuration in the data model where a minimum and maximum value can be set. Deadbands will be configured based on a percentage change of the applied measurement range. A deadband setting of zero (0) forces the measurement to follow the instantaneous value (i.e. deadbanding is disabled). For complex measurement types supporting both magnitude and angle, the deadband will only apply to the magnitude element.

<additional items> The CDC definition BCR_PRIV includes a Data Attribute actVal whose type is

INT128, according to the Standard, whereas on MMS level it is INT64 (refer Tissue 580 and 582).


4 PIXIT FOR DATA SET MODEL


Ds1 What is the maximum number of data elements in one data set (compare ICD setting)

Not constrained by configuration parameter. Depends on available memory.

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

None

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

None

<additional items> Maximum quantity of data sets is 100.

<additional items> Dynamic data sets not supported.

P34x/EN PX/Ia7 7


5 PIXIT FOR SUBSTITUTION MODEL


Sb1 <additional items> Substitution not supported

8 P34x/EN PX/Ia7


6 PIXIT FOR SETTING GROUP CONTROL MODEL


Sg1 What is the number of supported setting groups for each logical device (compare NumSG in the SGCB)

4

Sg2 What is the effect of when and how the non-volatile storage is updated (compare IEC 61850-8-1 $16.2.4)

None. ConfirmEditSGValues not supported.

Sg3 Can multiple clients edit the same setting group

na

Sg4 What happens if the association is lost while editing a setting group

na

Sg5 Is EditSG value 0 allowed? na

Is on-line setting changes of protection elements supported?

MiCOM Px40 devices do not support on-line setting changes of protection elements over the IEC 61850 interface despite supporting multiple setting groups.

Setting Group Control Block A Setting Group Control Block (SGCB) is provided in the System/LLN0 Logical

Node instance and provides services for changing the active setting group only.

Active data attribute values The data attribute values returned over the IEC 61850 interface to requesting

clients are always taken from the active setting group of the IED.

P34x/EN PX/Ia7 9


7 PIXIT FOR REPORTING MODEL


Rp1

The supported trigger conditions are (compare PICS)

integrity Y data change Y quality change N data update N general interrogation Y

Rp2

The supported optional fields are sequence-number Y report-time-stamp Y reason-for-inclusion Y data-set-name Y data-reference Y conf-rev Y segmentation Y

Rp3 Can the server send segmented reports

Y

Rp4

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

Rp5 Multi client URCB approach (compare IEC 61850-7-2 $14.2.1)

Each URCB is visible to one client only.

Rp6 What is the format of EntryID 8 byte octet string where the upper 4 bytes relate to the current time and the

lower 4 bytes count up in increments of 1.

Rp7

What is the buffer size for each BRCB or how many reports can be buffered

The memory size allocated to each buffered Report Control Block is 50,000 bytes. Depending on full configuration, Buffered Report Control Block could store 10 DO-based reports causing Buffer Overflow, but generally far more buffered reports could be stored according to different configuration in non-worst case.

Rp8

Pre-configured RCB attributes that cannot be changed online when RptEna = FALSE (see also the ICD report settings)

DatSet (and dataset contents), ConfRev cannot be changed online. OptFlds, TrgOp, IntgPd can be changed online when RptEna = FALSE.

Rp9 May the reported data set contain: - structured data objects? - data attributes?

Y Y

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

10 milliseconds Fixed.

Rp11 Does the device support to pre-assign a RCB to a specific client in the SCL

N

<additional items> Scan cycle applies to all Data Objects and Data Attributes within the dataset

assigned to the URCB.

<additional items> Supports a quantity of sixteen (16) URCB.

<additional items> All Report Control Blocks are located within the System\LLN0 Logical Node.

<additional items> The reported data set should not contain timestamp data attributes.

10 P34x/EN PX/Ia7


8 PIXIT FOR LOGGING MODEL


Lg1 What is the default value of LogEna (Compare IEC 61850-8-1 $17.3.3.2.1, the default value should be FALSE)

Not supported

Lg2 What is the format of EntryID (Compare IEC 61850-8-1 $17.3.3.3.1)

Not supported

Lg3

If there are multiple Log Control Blocks that specify the Journaling of the same MMS NamedVariable and TrgOps and the Event Condition (Compare IEC 61850-8-1 $17.3.3.3.2)

Not supported

Lg4 Pre-configured LCB attributes that cannot be changed online

Not supported

MiCOM Px40 devices do not support IEC 61850 logging services, hence there are no Log Control Blocks (LCB) exposed within the data model.

P34x/EN PX/Ia7 11


9 PIXIT FOR GENERIC SUBSTATION EVENTS MODEL


Go1

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 an Ethernet switch and should not be checked

N source MAC address Y destination MAC address Y Ethertype = 0x88B8 Y AppID N gocbRef Y timeAllowedtoLive Y datSet Y goID N t N stNum N sqNum Y test Y confRev Y ndsCom N numDatSetEntries

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

Y Set/reset via ‘Test Mode’ IED parameter

Go3 Does the DUT accept a configuration with a Goose control block with empty data set or too large data set?

No, the GoCB need to be removed from the configuration. GOOSE message is not published.

Go4

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

a) message does not arrive prior to TAL. TAL = (2 * (time to next message)) + (‘Minimum Cycle Time’ parameter). A ‘GOOSE IED Absent’ alarm is raised by the IED.

Go5

What is the behaviour when one or more subscribed GOOSE messages isn’t received or syntactically incorrect (missing GOOSE)

If one subscribed message is not received or is syntactically incorrect, it is ignored. (If the next message is also not received or is syntactically incorrect, the TAL will be exceeded.)

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

It is processed as if it were in order.

Go7 What is the behaviour when a subscribed GOOSE message is duplicated

It is processed as if it were in order.

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

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

Go9

May the GOOSE data set contain: - structured data objects (FCD)? - timestamp data attributes? Note: data attributes (FCDA) is mandatory

Subscribed Published Y Y Y Y

Go10 Published FCD supported common data classes/data types are

SPS, DPS, INS, ACT, ACD, BCR, MV, CMV, WYE, DEL, SEQ, SPC, DPC, INC, DPL, LPL

Go11 Subscribed FCD supported common data classes/data types are

SPS, DPS

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

1000 milliseconds with TAL = 2010 Configured by ‘Maximum Cycle Time’ parameter (‘IED Configurator’)

12 P34x/EN PX/Ia7


P34x/EN PX/Ia7 13


Go13

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

1) 0 milliseconds with TAL = 32 2) 11 milliseconds with TAL = 32 3) 11 milliseconds with TAL = 36 4) 13 milliseconds with TAL = 42 5) 16 milliseconds with TAL = 56 6) 23 milliseconds with TAL = 78 Configured by ‘Minimum Cycle Time’ and ‘Increment’ parameters (‘IED Configurator’)

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

Y

<additional items> The data received in a GOOSE message is only processed when a change in status number (stNum), taken from the GOOSE message header, is detected. No validation checks are made to ensure the data has changed inline with the stNum increment and it is accepted and processed as per the normal procedure given above. The data is transferred onto Boolean Virtual Inputs (made available in the Programmable Scheme Logic) when the data subscription parameters are met:Virtual Input state = True / On, when the received data value matches the Virtual Input’s target value in accordance with its comparison operator. Virtual Input state = False / Off, when the received data value does not match the Virtual Input’ target value in accordance with its comparison operator. The following comparison operators are supported: GOOSE data value EQUALS target value GOOSE data value IS NOT EQUAL TO target value GOOSE data value IS LESS THAN target value GOOSE data value IS GREATER THAN target value GOOSE data value is PASSED THROUGH without comparison (only applicable for binary data elements).

<additional items> The assignment of data values processed in received GOOSE messages is only transferred to Virtual Inputs if the quality of the data is acceptable. If the item being decoded is of a Common Data Class type (e.g. SPS) then an assignment to a quality value is automatically made (as it also forms part of the Common Data Class value). For basic data types, assignment to a quality value is manual. A value is classed as being bad quality if any of the quality flags, that are configured by the user in the ‘IED Configurator’, is asserted in the received quality value. If no quality flags have been configured, the value is always classed as good.

<additional items> There is also a separate ‘Publisher Present’ signal within Programmable Scheme Logic, indicating the publisher state for each Virtual Input. This, in combination with the ‘GOOSE IED Absent’ alarm, allows for GOOSE scheme problems to be easily diagnosed and dealt with automatically within scheme logic.

<additional items> Quantity of Virtual Inputs is product dependant - refer to GosGGIO1 in MICS.

<additional items> For the following conditions, a Virtual Input’s value will be forced to its configured default value: The publishing device is absent (e.g. no GOOSE messages are received). The received GOOSE message does not pass the validation criteria. The received GOOSE message has the Test flag set. The received GOOSE message has the NdsCom flag set. The default value is configured in the ‘IED Configurator’.

TAL = Time Allowed to Live


10 PIXIT FOR CONTROL MODEL


Ct1

What control modes are supported (compare PICS)

Y status-only Y direct-with-normal-security Y sbo-with-normal-security Y direct-with-enhanced-security Y sbo-with-enhanced-security

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

Configurable

Ct3 Is Time activated operate (operTm) supported

N

Ct4 Is “operate-many” supported N

Ct5

Will the DUT activate the control output when the test attribute is set in the SelectWithValue and/or Operate request (when N test procedure Ctl2 is applicable)

N

Ct6 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

Ct7 Is pulse configuration supported N

Ct8

What is the behaviour of the DUT when the check conditions are set Is this behaviour fixed, configurable, online changeable?

N synchrocheck N interlock-check DUT validates check conditions for consistency across select/operate requests.Interlocking applies to Circuit Breaker controls and causes checks to be made against associated CILO inter-locking Logical Node.

Ct9

What additional cause diagnosis are supported

Y Blocked-by-switching-hierarchy Y Select-failed Y Invalid-position Y Position-reached Y Parameter-change-in-execution N Step-limit N Blocked-by-Mode N Blocked-by-process N Blocked-by-interlocking N Blocked-by-synchrocheck Y Command-already-in-execution N Blocked-by-health Y 1-of-n-control N Abortion-by-cancel N Time-limit-over N Abortion-by-trip Y Not supported Y Object-not-selected

Ct10

How to force a “test-not-ok” respond with SelectWithValue request?

1. Send an invalid orCat value 2. Select control object twice 3. Select an operating control object 4. Send a SelectWithValue with a value the same as the current Data Objects stVal Note: This list is not exhaustive.

14 P34x/EN PX/Ia7


P34x/EN PX/Ia7 15


Ct11

How to force a “test-not-ok” respond with Select request?

1. Select more than 1 control object (fail on control uniqueness checks) 2. Select request only returns ReadResponse+ with:

The selected control object name for a successful operation.

An empty/null string for a failed select request.

Ct12

How to force a “test-not-ok” respond with Operate request?

1. Send an invalid orCat value 2. Attempt to operate an already operating control object 3. Select control object from Client A, operate same control object from

Client B. 4. For SBO/SBOw, do not select the control object prior to sending the

operate request 5. For SBO/SBOw, ensure data in operate request is different to that sent in

the select request 6. Send an operate request with a value the same as the current Data

Objects stVal Note: This list is not exhaustive.

Ct13 Which origin categories are supported?

Internally the IED supports: Process From external clients: All categories supported (the IED simply records the given category so long as it is within the valid range).

Ct14 What happens if the orCat is not supported?

IED returns AddCause ‘Not-supported’.

Ct15

Does the IED accept a SelectWithValue/Operate with the same ctlVal as the current status value?

DOns: N SBOns: N DOes: N SBOes: N AddCause = ‘Position-reached’ with MMS AccessResult = ‘object-access-denied’

Ct16

Does the IED accept a select/operate on the same control object from 2 different clients at the same time?

DOns: N SBOns: N DOes: N SBOes: N

Ct17

Does the IED accept a Select/SelectWithValue from the same client when the control object is already selected (tissue 334)

SBOns: N SBOes: N

Ct18

Is for SBOes the internal validation performed during the SelectWithValue and/or Operate step?

SelectWithValue and Operate

Ct19 Can a control operation be blocked by Mod=Off or Blocked

N

Ct20 Does the IED support local/remote operation?

Y for CB control only. The Local mode check is done on Operate only for SBO controls.

Ct21

Does the IED send an InformationReport with

LastApplError as part of the Operate response- for control with normal security?

SBOns: Y DOns: Y

<additional items> SBOns: If the client has already successfully selected the control and a second select request is issued, the IED will return a null string which indicates a Select Response. The failure to select the control does not affect its initial state (i.e. the control remains in a selected state).


16 P34x/EN PX/Ia7


<additional items> SBOes: If the client has already successfully selected the control and a second select request is issued, the IED will return the following: SelectWithValue Response- with data access error “temporarily-unavailable” LastApplError.Error = “Operator Test Not OK” LastApplError.AddCause = “Command-already-in-execution” The failure to select the control does not affect its initial state (i.e. the control remains in a selected state). Attempts to operate an SBO control with enhanced security will only be successful if the control number in the operate request matches the control number of the successful select request.


11 PIXIT FOR TIME AND TIME SYNCHRONISATION MODEL


Tm1

What quality bits are supported? N LeapSecondsKnown N ClockFailure Y ClockNotSynchronized

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

If no configured external SNTP server responds within 5 seconds, the ‘ClockNotSynchronized’ bit will be set to 1.

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

na

Tm4

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

The ‘Clock not synchronized’ bit at power-up has a default status of not synchronized (set to 1). When the clock becomes synchronized, the bit will be reset to 0. All available time synchronization sources will affect the ‘Clock not synchronized’ bit. These time sources include SNTP and, where applicable, IRIG-B.

Tm5 Is the timestamp of a binary event adjusted to the configured scan cycle?

N

Tm6 Does the device support time zone and daylight saving?

Y

Tm7

Which attributes of the SNTP response packet are validated?

Y Leap indicator not equal to 3 Y Mode is equal to SERVER N OriginateTimestamp is equal to value sent by the SNTP client as Transmit Timestamp N RX/TX timestamp fields are checked for reasonableness Y SNTP version 4 Y other: Transmit timestamp is not null.

P34x/EN PX/Ia7 17


12 PIXIT FOR FILE TRANSFER MODEL


What is structure of files and directories?

Device Root/ COMTRADE/ dr/ dr_unextracted/ LD/ {IEDNAME}Control/ {IEDNAME}Measurements/ {IEDNAME}Protection/ {IEDNAME}Records/ {IEDNAME}System/ Files (*.cfg and *.dat) according to the COMTRADE standard, ASCII format.

Where are the COMTRADE files stored?

/COMTRADE/ and / dr_unextracted /

Ft1

Are comtrade files zipped and what files are included in each zip file?

Not zipped

Ft2 Directory names are separated from the file name by

“/” The use of “\” directory separator will return a positive result to the file transfer MMS service requests but with no data elements (directory or filenames).

Ft3 The maximum file name size including path (recommended 64 chars)

44 chars

Ft4 Are directory/file name case sensitive Case sensitive

Ft5 Maximum file size Not restricted (approx 10 MB)

Ft6 Is the requested file path included in the MMS fileDirectory respond file name?

N

Ft7

Is the wild char supported MMS fileDirectory request?

Yes, wild cards are: * *.* *.cfg and *.dat

Ft8 Is it allowed that 2 clients get a file at the same time?

Y

<additional items> Disturbance record filenames are a based around the following fixed format giving a maximum filename length of twenty eight (28) characters: yyyymmdd_HHMMSS_xxx_rNNN.* where: yyyy = The year, e.g. 2006 mm = The month, e.g. 03 (for March) dd = The day of month, e.g. 15th HH = Hours in 24hr format, e.g. 12 MM = Minutes, e.g. 59 SS = Seconds, e.g. 59 xxx = milliseconds, e.g. 999 r = A literal ‘r’ character NNN = Disturbance record number, e.g. 001 * = The file type, either cfg or dat

18 P34x/EN PX/Ia7


P34x/EN PX/Ia7 19


<additional items> If automatic extraction of Disturbance Records is required, the file operations must be performed on the ‘dr_unextracted’ directory. This directory contains disturbance records that have not been downloaded from the IED by a client. A record is classed as downloaded (or extracted) when the *.dat file has been transferred. Once extracted, disturbance records are automatically removed from this directory. However it should be noted that these records are still available from the ‘COMTRADE’ and ‘dr’ directories.

Is the IETF FTP protocol also implemented

N


20 P34x/EN PX/Ia7

PXXX Product Description

Alstom Grid

© - ALSTOM 2014. All rights reserved. Information contained in this document is indicative only. No representation or warranty is given or should be relied on that it is complete or correct or will apply to any particular project. This will depend on the technical and commercial circumstances. It is provided without liability and is subject to change without notice. Reproduction, use or disclosure to third parties, without express written authority, is strictly prohibited.

Alstom Grid Worldwide Contact Centre

www.alstom.com/grid/contactcentre/

Tel: +44 (0) 1785 250 070

www.alstom.com

micom p40 agile p341, p342, p343, p344, p345, p346...micom p40 agile p341, p342, p343, p344, p345,...

Documents