Test Procedure Working Groups » IEC 61850 TPWG » Test Procedure Issues » Server

Richard to propose changes

Updated attachment based on feedback thierry; added precondition LocSta=F when supported and changed orCat from 2 to 3 for SBOes.

Richard to update per TPWG discussion:

replace DUT by XCBR and CSWI

Move "if supported" from test description to requirement condition

processed the comments: remove LLN0, move CSWI "if supported" to table A.4.2;

Richard concerned about focus on CSWI when the LocSta applies to any LN.

CSWI is common use case, perhaps state this is example use case and the test could be used in any LN.

Perhaps split to two test cases - CSWI/XCBR in separate devices and Local general test

Discuss further with Thierry.

From M.Haecker:

sCtl17
In step 1 the IED is set to <LN>.Loc=False and <LN>.LocSta=True , to allow operation from station level, not from control center level.
The control in step 2 “orCat=station” matches the operational configuration and therefore the response is positive.
The control in step 3 “orCat=remote” does not match the operational configuration and therefore the response is rejected.

No issue.

sCtl16
In the test description we state “changes the DUT to “Local”; (LLN0.Loc=True or CSWI.Loc=True) and XCBR/XSWI.Loc=True” which is unlucky.
We should have left away the last “XCBR/XSWI.Loc=True” for we execute our tests on controller level, not on process level.
If XCBR/XSWI.Loc=True , then the switchgear proxy will not accept any control via protocol. The switchgear is on manual control then.

I propose to change the test description to “Test engineer changes the DUT to “Local”; (LLN0.Loc=True or CSWI.Loc=True)”
This is a general statement, nothing to do with the discussion at hand.

a) DOns
Upon all the controls on step1 the controller will accept only orCat=1 or orCat=4, but the XCBR/XSWI proxy will reject all.
Step2 sets XCBR/XSWI proxy to “remote” i.e. acceptance of controls from CSWI basically. CSWI will accept orCat 1 and 4.
Remote controls as per step3 are to be refused, if the L/R concept is supported.
b) SBOns
As above, once XCBR/XSWI.Loc are “true”, all controls will be rejected by the proxy.
Step2 sets DUT to “remote”.
Step3 will reject local controls (MltLev is not mentioned). The stated test result is wrong for orCat 1 and 4.
Step4 sets DUT to “local” (assume XCBR/XSWI are not affected – otherwise it makes no sense).
In Step5 the DUT will not be selected for orCat 1 and 4, all other orCat will be rejected.
The local controls of step6 will be accepted.
The remote controls of step7 will be rejected.

Thierry to rewrite testcase, with significant reorganization.

Please find the test procedures, 1) split according to the control model, and 2) having additional steps for the select control model, changing CSWI.Loc from False to True after the Select succeeds.
Additionally, the test considers PIXIT entry Ct29 - i.e. are orCat 1, 4 allowed over communication or not.

I agree with the proposed changes in general. LocSta/Mltlev is tested in sCtl17. For sCtl16 we should only verify "LocSta=F or missing" and "MltLev=F or missing". According to table B.1 orCat=Station:NA and orCat=Remote:A. For orCat=Bay:PIXIT Ct29!

About SBOes expected result 9/11 it differentiate between LocSta/MltLev supported or not supported to send AddCause at SelectWithValue and Operate stage. Not sure if this is specified in the standard.

I only updated SBOes part in the 9dec

Reviewed 12/13 and decided to mark resolved.

There are differences between agreed solution from this tread and published TP1.3. In short: Proposed solution starts with Xxxx.Loc=False and then if supported forces Xxxx.Loc=True. Published TP1.3 starts with Xxxx.Loc=True and then if supported forces Xxxx.Loc=False.

As Xxxx.Loc=False is mandatory and Xxxx.Loc=True is optional, do we need to update TP1.3 to be in line with proposed solution in "Solution to redmine 5961 sCtl16 with LocSta (9dec).docx"?