Project

General

Profile

Issues #7128

Reconfiguration of a LGOS / LSVS prefix instance number in SCT test is missing

Added by Thierry Dufaure 2 months ago. Updated 20 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
04/01/2025 (20 days late)
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
TP1.3
Updated Test Document:
Test Case ID:
new sGos25, sSvs19
Closed Reason:
Test Procedure Update
Triggering Tissue 2:
Triggering Tissue 3:

Description

During InteropTest, it was observed that - https://redmine.ucaiug.org/issues/6973
1) ICT creates supoervision LN to comply with the BAP.
2) since there was no round trip involving IID file, the SCT was not aware of the new LN instances that were added by the ICT to provide subscription supervision.
3) in a later stage, the SCT has added LNs for subscription supervision providing different naming/numbering than the ones that were added by the ICT. The ICT did not change the assignement of the subscription supervizion instances as exposed in the SCD.

It needs to be verified that after a reconfiguration of the GocbRef/MsvcbRef.setSrcRef by the SCT, that the instances in the device are matching the latest SCD configuration.
For instance with such a test: Example within SCD V1
instance 1 supervizes message 1
instance 2 supervizes message 2
instance 3 supervizes message 3

within SCD V2
instance 1 supervizes message 3
instance 2 supervizes message 1
instance 3 supervizes message 2

Files

Solution to redmine 7128 supervision instance.docx Solution to redmine 7128 supervision instance.docx 36 KB Richard Schimmel, 03/04/2025 06:22 AM
Solution to redmine 7128 supervision instance March5.docx Solution to redmine 7128 supervision instance March5.docx 37.7 KB Richard Schimmel, 03/05/2025 04:10 AM

Also available in: Atom PDF