488   Input for Logical Nodes: Data Object binding

Created: 23 Mar 2007

Status: In Force (green)

Part: Part 7-4 (2003)

Links: #489 Input for Logical Nodes: Data Object binding




Category: Issue for edition 2 of this part


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.


Extend all CDC's with two optional attributes with FC "IN" (Inputs): "IntAddr" of type VisibleString32 (for IED internal functions)
"ExtRef" of type ObjectReference (for other IED's objects).

Discussion Created Status
Time for voting is over 24 Jun 08 In Force (green)
Solution will be included in editon 2. 14 Feb 08 Ballot Period
Solution from Quebec: include in to CDC ORG an attribute called "purp" (Purpose). 13 Sep 07 Discussion (red)
Proposal of WG10 / Editor Meeting in Seoul:
the InRef1 or InRef2 data shall have the following information that can be retrieved from that data:
(1) an ARRAY of External references; each of these references uniquely identifies one data that is connected to this input. I.e., it is possible to connect multiple data to one "input"
(2) an internal reference. The semantic of the internal reference is not standardised today. It could be a name of a data object from an output (e.g. EEHealth) or from a controllable data (e.g. BlckRec) or a non standardised designation (Init)
(3) a description attribute
For the rest there is no agreeement yet. Possible information can be:
(x) an ARRAY of quality (to be able to read that the receiving device has the data available)
(x) an ARRAY of the data received on the inputs
--> further discussion is required
21 Apr 07 Discussion (red)
Regarding #tissue 489 and the solution in Seoul this tissue will be reopend. 19 Apr 07 Discussion (red)
This tissue belongs to part 7-3 and will be commented under #489. 26 Mar 07 Not Applicable


Privacy | Contact | Disclaimer

Tissue DB v.