Issues #7182
Inconsistency in sBrN10 reference to PIXIT-Rp13
Due date:
06/10/2025 (11 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
PIXIT-Rp13 is consistently utilized across all referring test cases where the RCB is pre-assigned (ResvTms = -1), with the exception of sBrN10.
Since sBrN10 exclusively involves BRCBs that are not pre-assigned, referencing Rp13 appears inconsistent.
sBrN10 addresses the scenario where ResvTms > 0 and the association is lost. Therefore, the test procedure should be updated to account for this scenario within ID Rp13 or a new PIXIT ID should be created.
Alternatives to fix PIXIT:
- Rp13: Does the server accept any client to configure/enable an RCB with:
-BRCB.ResvTms = -1, or
-URCB.Resv = T, or
-BRCB.ResvTms > 0 AND loss of association?
- Create a new PIXIT ID entry and modify sBrN10 to reference it to
Updated by IEC 61850 TPWG about 2 months ago
- Due date set to 05/27/2025
- Status changed from New to In Progress
This appears to be a missed case. Should be fixed by updating PIXIT:
Rp13: Does the server accept any client to configure/enable an RCB with:
-BRCB.ResvTms = -1, or
-URCB.Resv = T, or
-BRCB.ResvTms > 0 AND loss of association?
Updated by IEC 61850 TPWG 25 days ago
- Tracker changed from Bug to Issues
- Due date changed from 05/27/2025 to 06/10/2025
- Start date deleted (
04/23/2025)
Updated by IEC 61850 TPWG 25 days ago
- Project changed from IEC 61850 TPWG to Server
- Assignee set to Richard Schimmel
- Discuss in Upcoming Meeting set to No
- Closed Reason --Not Set--- added