Project

General

Profile

Issues #6193

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

Added by IEC 61850 TPWG 2 months ago. Updated 9 days ago.

Status:
In Progress
Priority:
Normal
Due date:
01/24/2023 (9 days late)
Discuss in Upcoming Meeting:
No
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:

Description

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


Files

#1

Updated by Richard Schimmel 2 months ago

Added solution

#2

Updated by Thierry Dufaure 2 months 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

#3

Updated by IEC 61850 TPWG 23 days 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.

#4

Updated by Thierry Dufaure 22 days 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.

#5

Updated by IEC 61850 TPWG 9 days ago

  • Assignee changed from Thierry Dufaure to Richard Schimmel

Accepted.

#6

Updated by IEC 61850 TPWG 9 days ago

note: max is an attribute of RptEnabled

Also available in: Atom PDF