0% found this document useful (0 votes)
14 views15 pages

PIXIT Protocol Implementation Guide

The document outlines the Protocol Implementation eXtra Information for Testing (PIXIT) across various models including Association, Server, Data set, Reporting, Control, and Time synchronization. It details parameters, supported features, and testing requirements for each model, along with accessibility tests and command execution validation. The information is structured to assist in the testing and implementation of IEC61850 protocols.

Uploaded by

Ahmad Golbabaei
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views15 pages

PIXIT Protocol Implementation Guide

The document outlines the Protocol Implementation eXtra Information for Testing (PIXIT) across various models including Association, Server, Data set, Reporting, Control, and Time synchronization. It details parameters, supported features, and testing requirements for each model, along with accessibility tests and command execution validation. The information is structured to assist in the testing and implementation of IEC61850 protocols.

Uploaded by

Ahmad Golbabaei
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Protocol Implementation eXtra Information for Testing

Contents
1 PIXIT for Association model .................................................................................................. 2
2 PIXIT for Server model........................................................................................................... 3
3 PIXIT for Data set model ........................................................................................................ 3
4 PIXIT for reporting ................................................................................................................. 4
5 PIXIT for control model.......................................................................................................... 5
6 PIXIT for time and time synchronisation model..................................................................... 6
7 Additional remarks .................................................................................................................. 6
8 Accessibility tests .................................................................................................................... 7
8.1 Data mapping.................................................................................................... 7
8.2 Command execution....................................................................................... 10
9 Appendix ............................................................................................................................... 12
9.1 Schematics...................................................................................................... 12

Department DBE Page 1/15 config Rev. 1


1 PIXIT for Association model
Description Value / Clarification
Maximum number of clients that can set-up an
4
association simultaneously
Lost connection detection time range (default 40 sec.
range of TCP_KEEPALIVE is 10 seconds) not configurable
Is authentication supported N
What association parameters are necessary for Transport selector Y
successful association Session selector Y
Presentation selector Y
AP Title N
AE Qualifier N
What is the maximum and minimum MMS PDU Max. MMS PDU size 32.768
size Min. MMS PDU size 2.000
What is the typical startup time after a power
40..45 sec.
supply interrupt
PSEL: 00 00 00 01
Association parameters SSEL: 00 01
TSEL: 00 01

Department DBE Page 2/15 config Rev. 1


2 PIXIT for Server model
Description Value / Clarification
Which analogue value (MX) quality bits are Validity:
supported (can be set by server) Y Good
Y 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 Validity:
supported (can be set by server) Y 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
Tested with 20
one GetDataValues request
What is the maximum number of data values in
Tested with 20
one SetDataValues request

3 PIXIT for Data set model


Description Value / Clarification
What is the maximum number of data elements
27
in one data set
How many persistent data sets can be created
Not available
by one or more clients
How many non-persistent data sets can be
Not available
created by one or more clients
How many persistent data sets can be created
0
by configuration with SCL? (response probably
(no tool available)
none, as no SCL processing tool is available)

Department DBE Page 3/15 config Rev. 1


4 PIXIT for reporting
Description Value / Clarification
The supported trigger conditions are Y integrity
Y data change
Y quality change
Y data update
Y general interrogation
The supported optional fields are Y 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
Can the server send segmented reports Y
Mechanism on second internal data change Send report immediately
notification of the same analogue data value
within buffer period (Compare IEC 61850-7-2
$[Link])
Multi client URCB approach (compare IEC All clients can access all URCBS.
61850-7-2 $14.2.1) Each client has his own instances.
What is the format of EntryID Octal string
What is the buffer size for each BRCB or how
Tested up to 1500 changes
many reports can be buffered
Pre-configured RCB attributes that cannot be name
changed online when RptEna = FALSE rptID
dataSet
confRev

Department DBE Page 4/15 config Rev. 1


5 PIXIT for control model
Description Value / Clarification
What control modes are supported Y status-only
Y direct-with-normal-security
N sbo-with-normal-security
N direct-with-enhanced-security
N sbo-with-enhanced-security
Is Time activated operate (operTm) supported N
What is the behavior of the DUT when the test
attribute is set in the SelectWithValue and/or Not available
Operate request
What are the conditions for the time (T)
attribute in the SelectWithValue and/or Operate Not available
request
Is “operate-many” supported N
Is pulse configuration supported N
N synchrocheck
What check conditions are supported
N interlock-check
What service error types are supported Y instance-not-available
N instance-in-use
N access-violation
N access-not-allowed-in-current-state
N parameter-value-inappropriate
N parameter-value-inconsistent
N class-not-supported
N instance-locked-by-other-client
N control-must-be-selected
Y type-conflict
N failed-due-to-communications
N constraint failed-due-to-server-constraint
What additional cause diagnosis are supported N blocked-by-switching-hierarchy
N select-failed
N invalid-position
N position-reached
N parameter-change-in-execution
N step-limit
N blocked-by-Mode
N blocked-by-process
N blocked-by-interlocking
N blocked-by-synchrocheck
N command-already-in-execution
N blocked-by-health
N 1-of-n-control
N abortion-by-cancel
N time-limit-over
N abortion-by-trip
How to force a “test-not-ok” respond with
Not applicable
SelectWithValue request?
How to force a “test-not-ok” respond with
Always accepted
Operate request?
Which origin categories are supported? What
Ignored
happens if the orCat is not supported?
ctlVal == stVal Accepted
behaviour if Test is set in Operate Ignored

Department DBE Page 5/15 config Rev. 1


6 PIXIT for time and time synchronisation model
Description Value / Clarification
What quality bits are supported Y LeapSecondsKnown
N ClockFailure
Y ClockNotSynchronized
What is the behavior when the time ‘ClockNotSynchronized’ will be set within five
synchronization signal/messages are lost minutes.
Time stamp accuracy Better than 30 ms
When is the quality bit "Clock failure" set? Not available
When is the quality bit "Clock not On startup and less than seven minutes after
synchronised” set? broken SNTP-sync-link.

7 Additional remarks
Description Value / Clarification
If there are several TAPCONs in a project, they Can be done by setting the IEDs name in the
must have different LD names (MMS domain device via external tool or setting via display input.
names). This means that e.g. the IED name Restart of device is needed.
has to be changed. How can this be done?
How can the actual ICD file be obtained? Via ftp access.
[Link]
How to change the actual ip-settings? Via external software or via display. Ip-address
change is done immediately after entering.

Department DBE Page 6/15 config Rev. 1


8 Accessibility tests

8.1 Data mapping


All parameter changes have to be mapped to the IEC61850.
In
table 1 and 2 all data is listed that should be checked.

Department DBE Page 7/15 config Rev. 1


ATCC

IEC61850 name parameter I/O front panel forced by


Loc - - + remote key
TapChg - + + higher/lower command via binary inputs, SCADA or front panel
CAN bus;
ParOp + - - second device is needed
manual/auto inputs (IO);
LTCBlk - + + hand/auto keys
manual/auto inputs (IO);
Auto - + + hand/auto keys
CtlV - + - see manual;3.3 Description of the display
LodA - + - see manual, 3.3 Description of the display
BndCtr + - - see manual, 7.2 Regulating Parameters
BndWid + - - see manual, 7.2 Regulating Parameters
CtlDlTmms + - - see manual, 7.2 Regulating Parameters
LDCR + - - see manual, [Link] Line-Drop Compensation
LDCX + - - see manual, [Link] Line-Drop Compensation
BlkLV + - - see manual, 7.2.2 Limit values
LimLodA + - - see manual, 7.2.2 Limit values
LDC - - - only accessable via IEC61850
TmDlChr + - - see manual, 7 Parametering
LDCZ + - - see manual, [Link] Line-Drop Compensation
TapBlkR + - - max. Tap pos
TapBlkL + - - min. Tap pos
CirCur + - - CAN bus; second device is needed
Master + - - CAN bus; second device is needed
Follower + - - CAN bus; second device is needed
SICmd1 - - - only accessable via IEC61850
SICmd2 - - - only accessable via IEC61850
SICmd3 - - - only accessable via IEC61850
VoltLvl1 + + + IO X1:33 or SCADA
VoltLvl2 + + + IO X1:16 or SCADA
VoltLvl3 + + + IO X1:17 or SCADA
OverV + - - increasing measured voltage
UnderV + - - lowering measured voltage
OverC + - - increasing measured current
MotDrv - + - IO X1:28
UInd1 - - - see manual, 7.4.2 Status
UInd2 - - - see manual, 7.4.2 Status
UInd3 - - - see manual, 7.4.2 Status
UInd4 - - - see manual, 7.4.2 Status
FuncMon - + - 15 min. after startup and measured voltage 0V
ParErr - - + can not be forced under normal conditions

table 1: „ATCC1 data list for change test“

Department DBE Page 8/15 config Rev. 1


YLTC

IEC61850 name parameter I/O front panel forced by


no direct access;
Health - - - status 'OK', 'warning' and 'error' are treated due to TAPGUARD240
status
not visible via display;
OpCnt - + - every successfull step change has to be counted (*1)
TapChg - + - BCD inputs (UC1)
BCD inputs (UC1);
EndPosR - + - Limits can be set via parameter (*2)
BCD inputs (UC1);
EndPosL - + - Limits can be set via parameter (*2)
MotDrv - + - IO X1:28
SigGRE - - - no direct access
SigYel - - - no direct access
SigRED - - - no direct access
USigYEL - - - no direct access
USigRED - - - no direct access
AbrPrts - - - no direct access
OilExCl - - - no direct access
AbsWPt - - - no direct access
OilSamp - - - no direct access
OnSTmIntv - - - no direct access

table 2: "YLTC1 data list for change test"

*1) A successful tap position change has to be forced by setting input “Motor drive” hi, changing
BCD inputs (only one tap position difference is allowed!) and finally setting input “Motor drive”
lo.
*2) Values can be changed by parameter settings. [MENU] -> Parameter -> Limit values -> page 24
and 25

Department DBE Page 9/15 config Rev. 1


8.2 Command execution
In order to test the command execution via IEC61850 all of the listed data points have to be validated.

ATCC

IEC61850 name parameter I/O front panel description


outputs "LOWER" "RAISE" (IO);
TapChg - + + LED 'higher' or 'lower'
output "PARALLEL ON";
ParOp - + + LED 'parallel'
outputs "MANUAL" "AUTO" (IO);
LTCBlk - + + LED "MANUAL" or "AUTO"
BndCtr + - + see manual, 7.2 Regulating Parameters
BndWid + - + see manual, 7.2 Regulating Parameters
CtlDlTmms + - + see manual, 7.2 Regulating Parameters
LDCR + - + see manual, [Link] Line-Drop Compensation
LDCX + - + see manual, [Link] Line-Drop Compensation
BlkLV + - + see manual, 7.2.2 Limit values
LimLodA + - + see manual, 7.2.2 Limit values
LDC + - + only accessable via IEC61850
TmDlChr + - + see manual, 7 Parametering
LDCZ + - + see manual, [Link] Line-Drop Compensation
readable via IEC 61850;
CirCur + - - visible via parametersetting:
[MENU]->Configuration->Parallel Control-><page 00>
readable via IEC 61850;
Master + - - visible via parametersetting:
[MENU]->Configuration->Parallel Control-><page 00>
readable via IEC 61850;
Follower + - - visible via parametersetting:
[MENU]->Configuration->Parallel Control-><page 00>
readable via IEC 61850;
SICmd1 - - - customer specific implementation
readable via IEC 61850;
SICmd2 - - - customer specific implementation
readable via IEC 61850;
SICmd3 - - - customer specific implementation
VoltLvl1 + + + accessable via IEC61850 or binary inputs (user setting)
VoltLvl2 + + + accessable via IEC61850 or binary inputs
VoltLvl3 + + + accessable via IEC61850 or binary inputs

table 3: "ATCC list for access test"

Department DBE Page 10/15 config Rev. 1


YLTC
There are no possibilities to force an action.

Department DBE Page 11/15 config Rev. 1


9 Appendix

9.1 Schematics

figure 1: on site view

Department DBE Page 12/15 config Rev. 1


figure 2: wiring plan 1

Department DBE Page 13/15 config Rev. 1


figure 3: wiring plan 2

Department DBE Page 14/15 config Rev. 1


figure 4: wiring plan 3

Department DBE Page 15/15 config Rev. 1

You might also like