Issues #640
sMdl6 indicates that indexed = FALSE and RptEnabled max > 1 is prohibited, but for association specific URCBs max can be >1
Status:
Closed
Priority:
Normal
Assignee:
-
Due date:
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
8-1
Triggering Tissue:
Final Decision:
non-indexed URCB with max>1 are allowed
Initial Test Document:
Updated Test Document:
Test Case ID:
sMdl6
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:
Description
In the new test procedures, test case sMdl6 indicates the case where indexed = FALSE and RptEnabled max > 1 is prohibited, but I don’t see that in the standard.
In the case of association specific URCBs, having max=1 doesn’t indicate that each client has their own copy of the URCB available.
For an implementation that allows 7 clients where each can access one and only one copy of the URCB, RptEnabled max=7. According to Table 24 in -6, max is the number…which are instantiated at configuration time. We create 7 at configuration time, but they are not indexed. When a client connects it can enable its own copy.
Files