Issues #5961

sCtl16 shall specify LocSta/MltLev to match with table B.1

Added by Richard Schimmel 3 months ago. Updated 26 days ago.

In Progress
Due date:
11/29/2022 (Due in 2 days)
Discuss in Upcoming Meeting:
Clause Reference:
Table B.1
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:


1) Table B.1 is very clear how a device shall respond in case for all combinations of XCBR.Loc + CSWI.Loc+ CSWI.LocSta + LLN0.MltLev and orCat=Bay/Station/Remote. sCtl16 does not specify LocSta and MltLev and as such the expected result can be wrong. For example SBOes step 3 expect response+ this requires LocSta=T! What if LocSta is not present?

2) What is the default value for LocSta when it's not present in the datamodel? I assume LocSta=False then the expected result for step 3 is wrong.

3) Because table B.1 is very specific, why do we have a PIXIT entry for SBOes step 6?

Let's discuss at TPWG



Updated by IEC 61850 TPWG about 2 months ago

  • Due date set to 10/18/2022
  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel

Richard to propose changes


Updated by Thierry Dufaure about 1 month ago

1) If LocSta is not present then the device does not make a different between remote and station operation. LocSta has been introduced to enhance the switching hierarchy by differentiating operationa originated in the station from operations orignated in the control center.

2) There is no default value for LocSta - if it is not present, operation from station and remote are treated the same - with regard to the Loc switching hierarchy.

3) Ct29 is needed, because usage of 1 (bay-control), 4 (automatic-bay) can be verified and limited by the implementaton: Local HMI (1) is done locally not over communication, Automatic bay (4) - Logic is done locally not over communication.

When XCBR/XSWI.Loc is true, then even CSWI can not operate the switching equipment. Since sCtl16 is using CSWI for switcing operation, then sCtl16 can only be performed with XCBR/XSWI.Loc = false


Updated by Richard Schimmel about 1 month ago

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


Updated by Thierry Dufaure about 1 month ago

Comments related to 5961 sCtl16 with LocSta (18oct).docx

What I don’t understand, is why are you expecting
- b3 to succeed while Xxxx.Loc = true? Select could also already fail
- d3, and d5 to succeed for orCat=remote while LocSta = false? SelectWithValue could also already fail

Actually, as soon as Xxxx.Loc = true, then Select can fail.

What happens if Xxxx.Loc = true is not achievable? The test is starting with Xxxx.Loc = true when supported, other wise with Xxxxx.Loc = false when supported.
How about starting the tests with Xxxx.Loc = false, and later: if supported set it to true.
I suppose Xxxx.Loc = false is always supported, while = true may not be.


Updated by IEC 61850 TPWG about 1 month ago

  • Due date changed from 10/18/2022 to 11/01/2022

Richard to update per TPWG discussion:

replace DUT by XCBR and CSWI

Move "if supported" from test description to requirement condition


Updated by Thierry Dufaure about 1 month ago

The test applies as soon as CSWI.Pos is availalbe AND the device implements a local remote switching hierachy.
-> CSWI.Loc is available and show the local status of the control switch.

Therefore, I recommend to remove any LLN0 cnosideratio from the test description, because CSWI.Loc vs Control(service parameter orCat) is what is currently being tested.


Updated by Richard Schimmel about 1 month ago

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


Updated by IEC 61850 TPWG 26 days ago

  • Due date changed from 11/01/2022 to 11/29/2022
  • Assignee changed from Richard Schimmel to Thierry Dufaure

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.

Also available in: Atom PDF