...
However, the question that arises here is whether the message received by the right interface knows where to go within the IED. To address this, there are two processes that can be followed.
Later Binding:
Later binding allows you to create specific External References in the interface and automatically link them to certain functionalities in the PTOC. This setup is then exported as an ICD or IID file and used in the configuration process and system configuration tool. In the SCL file, it appears like this:
...
In later binding, you first create the External Reference and establish the link. Then, you bind to the already existing External Reference.
Message/Data Binding / ICT Binding:
In this case, the binding is not done before the system configuration but is completed afterward. First, you create a GOOSE control block, and then you create an external reference in your interface. This external reference looks a bit different:
<ExtRef iedName="..." ldInst="..." prefix/lnClass/lnInst="..." doName="..." daName="..." ServiceType="..." srcXXX="..." />
...
By tagging it, we can track exactly which plugin created the entry and ensure that the message is displayed in the correct plugin. This approach would help us manage the inconsistency more effectively.
Approaches to Address These Issues:
Here are some potential approaches to address these issues:
1. Use a Custom Attribute
Adding a custom attribute to indicate the binding type is a straightforward solution. Although it introduces a non-standard element, it can be highly effective for internal use. For example:
...
Non-standard approach, which might cause compatibility issues with third-party tools.
Requires custom tools or modifications to existing tools for validation and processing.
2. Use the descAttribute for Descriptive Information
The desc (description) attribute is part of the IEC 61850 standard and can be used to encode information about the binding type. This avoids adding non-standard attributes but still allows for clear differentiation:
...
Not as explicitly linked to binding types as a dedicated attribute.
Could be overlooked or misused for other descriptions.
(After careful consideration, it has been determined that this solution cannot be used and is not applicable to address the issue.)
3. Use the Private Tag
Using the Private tag in IEC 61850 SCL files is a viable approach for adding custom, non-standard information without violating the IEC 61850 standard. The Private element is specifically designed to allow vendors or users to include proprietary or custom data within SCL files while maintaining overall standard compliance.
...