779   object references

Created: 30 Sep 2011

Status: In Force (green)

Part: Part 6 (2009-12; Edition 2)




Paragraph: Table 45

Category: Issue may impact interoperability of implementations of Edition 2


7-4 introduces references to other IEC 61850 objects (LD, LN, DO, DA). In table 45 the values are defined to be according to 7-2. 7-2 only defines absolute names and temporary names. However, e.g. for the GrRef of an LD hierarchy, also IED relative references are needed, as the LD hierarchy is defined per IED type, i.e. before the IED name or its LD name is known.


Introduce IED relative object references e.g. as @ldInst/lnName[.doName] with the ldInst value as defined in SCL, for use in references on the same IED as the referenced object.
Introduce also LD relative names e.g. as /lnName.doName thus referencing objects inside the same LD which contains the reference.

Discussion Created Status
The usage of IED relative object references in the form @ldInst/lnName[.doName[.attributename]](e.g. @LD0/MMXU3.PhV or @LD1/LLN0) as value for CDC ORG is introduced into the SCL language, especially for usage inside ICD files and SCD files. Any object reference values hold on configured IEDs and visible via communication must always be absolute, and use the LD name part taken from the SCL ldName option (if configured).
For symmetry of reference definitions IED internal references described with Inputs/Extref elements should use the @ as value of the iedName attribute.
20 Jan 12 In Force (green)


Privacy | Contact | Disclaimer

Tissue DB v.