ABB 650 series version 1.3 IEC PIXIT

Transcription

1 Copyright 2005 ABB. All rights reserved. ABB 650 series version 1.3 IEC PIXIT (Protocol Implementation extra Information) Summary: This document contains the additional information in how the IEC is applied and implemented in ABB 650 series products, version 1.3. The PIXIT document is one of the conformance documents stated in the IEC standard. Template version 1.0 Date: July 3, 2008, UCA International Users Group Testing Sub Committee Type des. Prep. TPTE / Heléne Andersson Doc. kind Declaration of Conformity o. of p. Appr. / Strand Martin Title 650 series version IEC Resp. dept PSTP/TPTE Approved PIXIT Part no. FILE: ABB_650_series_version_1.3_-_IEC_61850_PIXIT.doc; SAVEDATE: :29; TEMPLATE: Techn_Doc_Stand_P.dot C; SKELETO: 1MRG en -d3 1 16

2 Table of content: ABB 650 series version 1.3 IEC PIXIT Introduction Contents of this document Related documents PIXIT for Association model PIXIT for Logical device model PIXIT for Logical node model PIXIT for Server model PIXIT for Data set model PIXIT for Substitution model PIXIT for Setting group control model PIXIT for Reporting model PIXIT for Logging model PIXIT for Generic substation events model PIXIT for Control model PIXIT for Time and time synchronization model PIXIT for File transfer model Introduction This document serves as the PIXIT document for the IEC implementation in the ABB 650 series products. The intention is to declare how the IEC is applied and used in the ABB 650 series, version 1.3. The document is organized according to the IEC 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 MRG en -d3 2

3 2 Related documents Document Id IEC (2003) IEC (2003) IEC (2003) IEC (2003) IEC (2003) IEC (2003) IEC (2003) IEC (2005) ABB 1MRG ABB 1MRG ABB 1MRG Title Communication etworks and Systems in Substations Part 5: Communication requirements for functions and device models Communication etworks and Systems in Substations Part 6: Configuration description language for communication in electrical substations related to IEDs Communication etworks and Systems in Substations Part 7-1: Basic communication structure for substation and feeder equipment Principles and models Communication etworks and Systems in Substations Part 7-2: Basic communication structure for substations and feeder equipment Abstract communication service interface (ACSI) Communication etworks and Systems in Substations Part 7-3: Basic communication structure for substation and feeder equipment Common data classes Communication etworks and Systems in Substations Part 7-4: Basic communication structure for substation and feeder equipment Compatible logical node classes and data classes Communication etworks and Systems in Substations Part 8-1: Specific communication service mapping (SCSM) Mapping to MMS(ISO/IEC 9506 Part 1 and Part 2) Communication etworks and Systems in Substations Part 10: Conformance testing ABB 650 series ver IEC MICS; Model Implementation conformance statement ABB 650 series ver IEC PICS; Protocol Implementation conformance statement ABB 650 series ver IEC TICS; Tissue Implementation conformance statement 1MRG en -d3 3

4 3 PIXIT for Association model Maximum number of clients that can set-up an association simultaneously TCP_KEEPALIVE value Lost connection detection time Is authentication supported What association parameters are necessary for successful association If association parameters are necessary for association, describe the correct values e.g. What is the maximum and minimum MMS PDU size What is the maximum startup time after a power supply interrupt 8 5 seconds TCP_KEEPIDLE = 10 s TCP_KEEPCT = 3 TCP_KEEPIIT = 10 s TCP_KEEPITVL = 5s 10s after association start to begin sending keepalive, and 15s (3 * 5s) to detect lost connection. Transport selector Session selector Presentation selector AP Title AE Qualifier Transport selector Session selector 0001 (default) 0001 (default) Presentation selector (default) AP Title AE Qualifier n/a n/a Max MMS PDU size bytes Min MMS PDU size 2 minutes 1024 bytes 4 PIXIT for Logical device model LD properties In addition to LD0, other LDs are used to group Ls that belongs to a certain aggregated functionality, for example 4-stage earth fault protection. 1MRG en -d3 4

5 5 PIXIT for Logical node model LPL Health Beh Mod Included, according to definitions in ICD file. Always OK - Supported values are O, 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 Only values O 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) Which status value (ST) quality bits are supported (can be set by server) Validity: Good, Invalid, Reserved, Questionable Overflow OutofRange BadReference Oscillatory Failure OldData Inconsistent Inaccurate Source: Process Substituted Test OperatorBlocked Validity: Good, Invalid, Reserved, Questionable 1MRG en -d3 5

6 What is the maximum number of data values in one GetDataValues request What is the maximum number of data values in one SetDataValues request BadReference Oscillatory Failure OldData Inconsistent Inaccurate Source: Process Substituted Test OperatorBlocked Limited to a MMS read request (GetDataValues) containing a list of maximum 20 entries Stack does not limit the amount of the data values. MMS PDU is the limit 7 PIXIT for Data set model What is the maximum number of data elements in one data set (compare ICD setting) How many persistent data sets can be created by one or more clients How many non-persistent data sets can be created by one or more clients maxattributes = 300 maximum FCDAs = 150 -> whatever limit is reached first. o online creation o online creation 8 PIXIT for Substitution model Substitution Substitution of value is supported. The quality can not be substituted The subid is not used. 1MRG en -d3 6

7 9 PIXIT for Setting group control model What is the number of supported setting groups for each logical device (compare umsg in the SGCB) What is the effect of when and how the non-volatile storage is updated (compare IEC $16.2.4) Can multiple clients edit the same setting group What happens if the association is lost while editing a setting group Is EditSG value 0 allowed? 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. Editing of setting group is not supported using IEC Editing of setting group is not supported using IEC Editing of setting group is not supported using IEC Editing of setting group is not supported using IEC PIXIT for Reporting model The supported trigger conditions integrity are data change (compare PICS) quality change (*) data update (**) general interrogation / The supported optional fields are sequence-number report-time-stamp reason-for-inclusion data-set-name data-reference buffer-overflow entryid conf-rev segmentation Can the server send segmented reports Mechanism on second internal Send report immediately data change notification of the 1MRG en -d3 7

8 same analogue data value within buffer period (Compare IEC $ ) Multi client URCB approach (compare IEC $14.2.1) What is the format of EntryID Octet string 8 What is the buffer size for each BRCB or how many reports can be buffered Pre-configured RCB attributes that cannot be changed online when RptEna = FALSE (see also the ICD report settings) May the reported data set contain: - structured data objects? - data attributes? - timestamp data attributes? What is the scan cycle for binary events? Is this fixed, configurable Each instance URCB is visible to one client only, (allows also multiple clients on one/same instance or one client/instance) bytes for each used BRCB (max. 100 BRCB instances) - DatSet - ConfRev - Squm - TimeofEntry, see note below For the case when Data Attributes (e.g. stval, q, t) are defined on FCDA level, the time will be updated together with data & quality changes 5 mseconds 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. Handling/sending of data that is When data is blocked, the data will be sent with blocked quality blocked when quality is changed. ote also that the sending of integrity report is not prohibited by data with quality blocked. (*) accepted by server and will be reported as data-change. (**) accepted by the stack, but not used in the application. 1MRG en -d3 8

9 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. ote: the VLA tag may be removed by a ethernet switch and should not be checked Can the test flag in the published GOOSE be turned on / off What is the behavior when the 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) What is the behavior when one or more subscribed GOOSE messages isn t received or syntactically incorrect (missing GOOSE) What is the behavior when a subscribed GOOSE message is /A source MAC address destination MAC address Ethertype = 0x88B8 gocbref timeallowedtolive datset goid t stum squm test (value is ignored) confrev ndscom (value is ignored) numdatsetentries 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 part 6). ote that erroneous GOOSE telegrams are discarded, and valid telegrams are supervised according to TAL. Is ignored. Internal data is set to invalid if time allowed to live times out. Is ignored 1MRG en -d3 9

10 out-of-order What is the behavior when a subscribed GOOSE message is duplicated Does the device subscribe to GOOSE messages with/without the VLA tag? May the GOOSE data set contain: - structured data objects? - data attributes? - timestamp data attributes? What is the slow retransmission time? Is it fixed or configurable? What is the fast retransmission scheme? Is it fixed or configurable? Can the Goose publish be turned on / off by using SetGoCBValues(GoEna) Properties of updated messages/data. Is AppId required in Goose message? How does the receving IED treat Goose message with T = true and needs commissioning TAL = Time Allowed to Live Is ignored, with the VLA tag, without the VLA tag Subscribed Published (*) * not used in applications Configured by IED tool (have to be > than the fast retransmission time, and =< ms). Can not be set <100ms. Configured by IED tool (>1ms) 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. The received data will be treated as invalid. 13 PIXIT for Control model What control modes are supported (compare PICS) status-only direct-with-normal-security sbo-with-normal-security direct-with-enhanced-security sbo-with-enhanced-security (only for DPC) 1MRG en -d3 10

11 Is the control model fixed, configurable and/or online changeable? Is Time activated operate (opertm) supported Is operate-many supported What is the behavior of the DUT when the test attribute is set in the SelectWithValue and/or Operate request What are the conditions for the time (T) attribute in the SelectWithValue and/or Operate request Is pulse configuration supported What is the behavior of the DUT when the check conditions are set Is this behavior fixed, configurable, online changeable? Fixed. Can be changed for some functions using the PCM 600 IED tool. Test mode is not supported ot supported synchrocheck interlock-check This is only applicable for CSWI.pos, otherwise ignored. ote also the both conditions are checked during operate phase. When supported, these checks can not be configured. What additional cause diagnosis are supported How to force a test-not-ok respond with SelectWithValue request? Blocked-by-switching-hierarchy Select-failed Invalid-position Position-reached Parameter-change-in-execution / Step-limit Blocked-by-Mode Blocked-by-process Blocked-by-interlocking Blocked-by-synchrocheck Command-already-in-execution Blocked-by-health 1-of-n-control Abortion-by-cancel Time-limit-over Abortion-by-trip Object-not-selected ot supported 1MRG en -d3 11

12 How to force a test-not-ok respond with Select request? How to force a test-not-ok respond with Operate request? Which origin categories are supported? What happens if the orcat is not supported? Does the IED accept a selectwithvalue/operate with the same ctlval as the current status value? Does the IED accept a select/operate on the same control object from 2 different clients at the same time? Does the IED accept a select/selectwithvalue from the same client when the control object is already selected (tissue 334) Is for SBOes the internal validation performed during the SelectWithValue and/or Operate step? ot supported ot supported Bay-Control, Station-Control, Remote- Control, Automatic-Bay, Automatic-Station, Automatic-Remote. orcat is only checked for DPC and SPC DATA s for the logical node types CSWI, ATCC, SPC8GGIO, VSGGIO and SELGGIO (*). This means that the check of Local/Remote switch will only occur for these attributes. ote that the orcat is checked during the operate execution phase. DOns: Rejected for the above(*) SBOns: ot Supported DOes: ot Supported SBOes: Rejected for the above(*) Rejected means returning addcause Blocked-by-switching-hierarchy DOns: SBOns: DOes: SBOes: ot Supported ot Supported - 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. DOns: SBOns: DOes: SBOes: SBOns: SBOes: ot Supported ot Supported ot Supported The Check synchrocheck/interlock is made during Operate phase. For others, e.g. blocked, the evaluation is done during select phase. 1MRG en -d3 12

13 Can a control operation be blocked by Mod=Off or Blocked Does the IED support local / remote operation? Vendor Specific additional cause diagnosis Mod = off is not supported. Control operation is blocked in Block state () (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 ctlum - Is not checked/evaluated by the server 14 PIXIT for Time and time synchronization model What quality bits are supported Describe the behavior when the time synchronization signal/messages are lost LeapSecondsKnown ClockFailure ClockotSynchronized Time accuracy of fractions of second(*) The ABB 650 series can have 2 configured STP 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 STP servers are off-line the event timestamps get ClockFailure and ClockotSynchronized status. The time to detect error and change to 2 nd server is 2 seconds. If no backup server is defined, there is a timeout of 5 minutes. When is the time quality bit "Clock Upon start of the IED, until synchronization 1MRG en -d3 13

14 failure" set? 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 Loss of time synchronization not synchronised set? Is the timestamp of a binary event adjusted to the configured scan cycle? Does the device support time zone and daylight saving? Which attibutes of the STP Leap indicator not equal to 3 response packet are validated? Mode is equal to SERVER OriginateTimestamp is equal to value sent by the STP client as Transmit Timestamp RX/TX timestamp fields are checked for reasonableness STP version 4 (*) When the first synchronization is received the time accuracy bits will show a low value. This value will increase the more valid synchronization messages are received, as the IED synchronization accuracy improves. 15 PIXIT for File transfer model What is structure of files and directories? Is the IETF FTP protocol also implemented Directory names are separated from the file name by The maximum file name size including path (recommended 64 chars) Are directory/file name case sensitive Maximum file size /COMTRADE/<files> / or \ works for FTP transfer / for MMS ot defined ot defined, free space varies and depends on size of the configuration. ~800kB. 1MRG en -d3 14

15 Is the requested file path included in the file name of the MMS filedirectory respond? Is the wild char supported MMS es, wild card = * or *.* or empty string filedirectory request? Is it allowed that 2 client get a file at the same time? FTP authentication Remark: Delete file only works on disturbance files (drec_x.zip) and not disturbance header files (drec_xh.zip). But once the disturbance file is deleted, the IED itself will remove the disturbance header file 1MRG en -d3 15

16 REVISIO Rev. ind. Page (P) Chapt. (C) Date Dept./Init. All Created this copy from the original with doc id 1MRG Changed IED version in the document to version in the document. TPTE/ /HeAnd -d1 C9 Changed max number of setting groups from 6 to TPTE/JS -d2 C6 Changed from to, OutOfRange is supported for MX TPTE/JS -d3 C12 C14 C15 C10 The GOOSE header element TEST is changed from to (value is ignored). Added description of time accuracy bits in time quality when IED is synchronizing. Changed 2 client get a file at the same time from to. Added a descriptive remark about file deletion. Added clarification about not supported data-update trigger condition TPTC/HJ 1MRG en -d3 16