488 Input for Logical Nodes: Data Object bindingCreated: 23 Mar 2007 Status: In Force (green) Part: Part 7-4 (2003) Links: #489 Input for Logical Nodes: Data Object binding Page: Clause: Paragraph: Category: Issue for edition 2 of this part Issue Binding to external inputs was first discussed in tissue 216. It was agreed to extend the common logical node information with the Data Object "GenIn" (or several instances of it) composed of two optional DataAttributes: "IntAddr" and "ExtRef". This external or internal mapping could be accurate enough for some logical nodes. However, in certain cases, such as MMXU, several input references are needed to bind the logical node to process. This could be resolved with different instances of "GenIn". But, how can we know if "A.phsA" is related with "GenIn1" or "GenIn5"? It would be very useful to have a more specific way which allowed the IED tool to assign external inputs to concrete Data Objects inside the logical node. In fact, the starting point of issue 216 was to make the SCL Inputs section visible over the comunication. It has to be taken into account that "ExtRef" element could specifiy values for the doName and even the daName. Proposal Extend all CDC's with two optional attributes with FC "IN" (Inputs): "IntAddr" of type VisibleString32 (for IED internal functions)
Privacy | Contact | Disclaimer Tissue DB v. 24.11.8.1 |