Issues #7128
Reconfiguration of a LGOS / LSVS prefix instance number in SCT test is missing
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
Updated by IEC 61850 TPWG 2 days ago
- Subject changed from Reconfiguration of aLGOS / LSVS prefix insitance number in SCT test is missing to Reconfiguration of a LGOS / LSVS prefix instance number in SCT test is missing
- Due date set to 03/04/2025
- Status changed from New to In Progress
Add a server test case to verify that when the test equipment causes a change in state of a GOOSE stream the expected LGOS reflects the change.
Reconfiguration from IID to SCD1 to IID to SCD2 is needed to exercise this issue.