P14x_EN_PX_Ff7

MiCOM P141, P142, P143, P144, P145

PIXIT

Feeder Management Relays

Publication Reference: P14x/EN PX/fF7

P14x/EN PX/fF7 2011. ALSTOM, the ALSTOM logo and any alternative version thereof are trademarks and service marks of ALSTOM. The other names mentioned, registered or not, are the property of their respective companies. The technical and other data contained in this document is provided for information only. Neither ALSTOM, its officers or employees accept responsibility for, or should be taken as making any representation or warranty (whether express or implied), as to the accuracy or completeness of such data or the achievement of any projected performance criteria where these are indicated. ALSTOM reserves the right to revise or change this data at any time without further notice.

GRID

MiCOM P141, P142, P143, P144, P145 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 UNBUFFERED REPORTS 10 8 PIXIT FOR REPORTING MODEL BUFFERED REPORTS 11 9 PIXIT FOR LOGGING MODEL 12 10 PIXIT FOR GENERIC SUBSTATION EVENTS MODEL 13 11 PIXIT FOR CONTROL MODEL 15 12 PIXIT FOR TIME AND TIME SYNCHRONISATION MODEL 18 13 PIXIT FOR FILE TRANSFER MODEL 19

P14x/EN PX/Ff7 1

PIXIT MiCOM P141, P142, P143, P144, P145

2 P14x/EN PX/Ff7


1 INTRODUCTION

This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 interface in P14x with Software Version 46.

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.

P14x/EN PX/Ff7 3


4 P14x/EN PX/Ff7

2 PIXIT FOR ASSOCIATION MODEL

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

16

TCP_KEEPALIVE value

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.

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.

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 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 16,384 bytes Min MMS PDU size 400 bytes

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 30 seconds.


3 PIXIT FOR SERVER MODEL

Description Value / Clarification

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

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

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 account any relevant header information.)

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 account any relevant header information.)

P14x/EN PX/Ff7 5


6 P14x/EN PX/Ff7


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.

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

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

Not constrained by configuration parameter. Depends on available memory.

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

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

Maximum quantity of data sets is 100. Dynamic data sets not supported.

P14x/EN PX/Ff7 7


5 PIXIT FOR SUBSTITUTION MODEL

Description Value / Clarification Substitution not supported

8 P14x/EN PX/Ff7


6 PIXIT FOR SETTING GROUP CONTROL MODEL

Description Value / Clarification What is the number of supported setting groups for each logical device (compare NumSG in the SGCB) 4

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.

Can multiple clients edit the same setting group na What happens if the association is lost while editing a setting group na

Is EditSG value 0 allowed? na

P14x/EN PX/Ff7 9


7 PIXIT FOR REPORTING MODEL UNBUFFERED REPORTS


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 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 URCB is visible to one client only.

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.

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

Y N N

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

10 milliseconds Fixed.

Scan cycle applies to all Data Objects and Data Attributes within the dataset assigned to the URCB. Supports a quantity of sixteen (16) URCB. All Report Control Blocks are located within the System\LLN0 Logical Node.

10 P14x/EN PX/Ff7


8 PIXIT FOR REPORTING MODEL BUFFERED REPORTS


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 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

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.

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

50,000 bytes

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.

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

Y N N

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

10 milliseconds Fixed.

Scan cycle applies to all Data Objects and Data Attributes within the dataset assigned to the BRCB. Supports a quantity of eight (8) BRCB. All Report Control Blocks are located within the System\LLN0 Logical Node.

P14x/EN PX/Ff7 11


9 PIXIT FOR LOGGING MODEL


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

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

Not supported

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

Pre-configured LCB attributes that cannot be changed online Not supported

12 P14x/EN PX/Ff7


10 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 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 N test Y confRev N ndsCom Y numDatSetEntries

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

Y Set/reset via Test Mode IED parameter

What is the behaviour when the GOOSE publish configuration is incorrect DUT will not send GOOSE

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.

What is the behaviour when one or more subscribed GOOSE messages isnt 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.)

What is the behaviour when a subscribed GOOSE message is out-of-order It is processed as if it were in order.

What is the behaviour when a subscribed GOOSE message is duplicated It is processed as if it were in order.

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

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

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

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)

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

P14x/EN PX/Ff7 13


14 P14x/EN PX/Ff7


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 Inputs 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).

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.

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.

Quantity of Virtual Inputs is product dependant refer to GosGGIO1 in MICS.

For the following conditions, a Virtual Inputs 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.


11 PIXIT FOR CONTROL MODEL


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

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

Is Time activated operate (operTm) supported N Is operate-many supported No What is the behaviour of the DUT when the test attribute is set in the SelectWithValue and/or Operate request

DUT ignores the test value and execute the command as usual

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 N

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

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

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

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.

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

Select request only returns ReadResponse+ with: The selected control object name for a successful operation An empty/null string for a failed select request

P14x/EN PX/Ff7 15


16 P14x/EN PX/Ff7


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

1. Select more than 1 control object (fail on control uniqueness checks) 2. Send an invalid orCat value 3. Attempt to operate an already operating control object 4. Select control object from Client A, operate same control object from Client B. 5. For SBO/SBOw, do not select the control object prior to sending the operate request 6. For SBO/SBOw, ensure data in operate request is different to that sent in the select request 7. Send an operate request with a value the same as the current Data Objects stVal Note: This list is not exhaustive.

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).

What happens if the orCat is not supported? IED returns AddCause Not-supported.

Does the IED accept an 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

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

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

SBOns: N SBOes: N

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

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

Does the IED support local / remote operation? Y for CB control only. The Local mode check is done on Operate only for SBO controls.

The IED will not accept a select request from the same client when the control object is already selected. This applies to both SBO control with normal security and SBO control with enhanced security. (Tissue 334)

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).


P14x/EN PX/Ff7 17


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.


12 PIXIT FOR TIME AND TIME SYNCHRONISATION MODEL


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

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.

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

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.

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 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.

18 P14x/EN PX/Ff7


13 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.

Is the IETF FTP protocol also implemented N

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).

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

Are directory/file name case sensitive Case sensitive Maximum file size Not restricted (approx 10 MB) Is the requested file path included in the file name of the MMS fileDirectory respond? N

Is the wild char supported MMS fileDirectory request?

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

Is it allowed that 2 client get a file at the same time? Y

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

P14x/EN PX/Ff7 19


20 P14x/EN PX/Ff7


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.

PXXX Product Description

GRID

Alstom Grid - ALSTOM 2011. ALSTOM, the ALSTOM logo and any alternative version thereof are trademarks and service marks of ALSTOM. The other names mentioned, registered or not, are the property of their respective companies. The technical and other data contained in this document is provided for information only. Neither ALSTOM, its officers or employees accept responsibility for, or should be taken as making any representation or warranty (whether express or implied), as to the accuracy or completeness of such data or the achievement of any projected performance criteria where these are indicated. ALSTOM reserves the right to revise or change this data at any time without further notice. Alstom Grid Worldwide Contact Centre www.alstom.com/grid/contactcentre/ Tel: +44 (0) 1785 250 070 www.alstom.com

P14x/EN PX/fF71 INTRODUCTION1.1 Contents of this document

2 PIXIT FOR ASSOCIATION MODEL3 PIXIT FOR SERVER MODEL4 PIXIT FOR DATA SET MODEL5 PIXIT FOR SUBSTITUTION MODEL6 PIXIT FOR SETTING GROUP CONTROL MODEL7 PIXIT FOR REPORTING MODEL UNBUFFERED REPORTS8 PIXIT FOR REPORTING MODEL BUFFERED REPORTS9 PIXIT FOR LOGGING MODEL10 PIXIT FOR GENERIC SUBSTATION EVENTS MODEL11 PIXIT FOR CONTROL MODEL12 PIXIT FOR TIME AND TIME SYNCHRONISATION MODEL13 PIXIT FOR FILE TRANSFER MODEL

Documents

P14x_EN_PX_Ff7