You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Communication Explorer aggregates control blocks with the same name.
However IEC 61850-6 Ed 2.1 only requires control blocks to be unique within each LLN0 (logical device).
This plugin should identify them using the path (typically we do this using the identity string in many OpenSCD plugins) or calculate an object reference (IEC 61850-6, Section 8.5.2) to avoid doing this.
In this screenshot, it would be tempting to think that there is one GOOSE message, named "Ctrl" which is sent:
In fact, there is three different GOOSE messages, each with a different DataSet:
Currently, the Communication Explorer aggregates control blocks with the same name.
However IEC 61850-6 Ed 2.1 only requires control blocks to be unique within each LLN0 (logical device).
This plugin should identify them using the path (typically we do this using the identity string in many OpenSCD plugins) or calculate an object reference (IEC 61850-6, Section 8.5.2) to avoid doing this.
In this screenshot, it would be tempting to think that there is one GOOSE message, named "Ctrl" which is sent:
In fact, there is three different GOOSE messages, each with a different DataSet:
Here is a test file:
XAT_Subsystem_Testing_Dup_Ctrl_Block_Name.scd.zip
This likely applies to other control blocks but I haven't looked into these further.
First reported at: transpower-nz/open-scd#29
The text was updated successfully, but these errors were encountered: