Issues #6193

sRpN5 does not test for the case where URCBs are association based (non-indexed).

Added by IEC 61850 TPWG over 1 year ago. Updated about 1 year ago.

Due date:
01/24/2023 (about 13 months late)
Discuss in Upcoming Meeting:
Clause Reference:
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:


the goal of the test is that an URCB instance is “protected” and can’t be changed by another client. When URCBs are non-indexed (association based) such protection is evident, but there should be a test case to be sure that two clients get their own URCB instance.
This applies to both edition 2 and edition 2.1



Updated by Richard Schimmel over 1 year ago

Added solution


Updated by Thierry Dufaure over 1 year ago

I agree with the proposal of Richard.
I recommend nevertheless the wording:
when (SCL ReportControl indexed=true or SCL ReportControl indexed is not present) and response+ when SCL indexed=false


Updated by IEC 61850 TPWG about 1 year ago

  • Due date changed from 01/10/2023 to 01/24/2023
  • Assignee changed from Richard Schimmel to Thierry Dufaure

Thierry is to investigate further whether indexed="false" is allowed with only one instance.


Updated by Thierry Dufaure about 1 year ago

indexed="false" is allowed with max="1".
Propose wording:
DUT sends SetURCBValues response+ when (SCL indexed=false and max > 1), otherwise DUT sends SetURCBValues response- with data access error = temporarily-unavailable.


Updated by IEC 61850 TPWG about 1 year ago

  • Assignee changed from Thierry Dufaure to Richard Schimmel



Updated by IEC 61850 TPWG about 1 year ago

note: max is an attribute of RptEnabled


Updated by IEC 61850 TPWG about 1 year ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF