Assigning Logical Nodes to IEDs

Implementing the virtual IED links the two boxes, but the Logical Nodes inside are still unmapped: until each specification Logical Node is bound to a Logical Node in the implementing IED, signals cannot be resolved. Unmapped Logical Nodes show an open-chain icon.

image2023-6-29_16-5-11.png

Open the Mapping Dialog by double-clicking the implemented IED in the Function Specification.

image2023-6-29_15-55-21.png

The mapping dialog offers 2 mapping contexts :

  • Specification to IED : where the left column is the Logical Node from your functional specification and the right column shows which Logical node of the IED it is mapped to.

  • IED to Specification : where the left column is the Logical Node from the IED and the right column shows the Logical node from the functional specification that it is mapped to.

Use the context that seems most appropriate to you.

Click on a cell marked as not mapped. This will show you a selection dialog. By default the selection dialog will show you all the Logical Node of the same logical node class.

image2023-6-29_15-59-52.png


You can use the Show all Logical Nodes if you need to map Logical Node from different Logical Node CLASS.

Once you have created a mapping, observe that the chain icon near the Logical Node is now closed.

image2023-6-29_16-5-38.png

Furthermore the Prefix and Instance number have changed to reflect those of the IED Logical Node.


In the background STS remembers the mappings of the Logical Nodes for each different IED type. Thus the mapping can be established later just by assigning an IED with the same type without an explicit mapping step.

Automatic Mapping

Click Automatic Mapping in the dialog. STS matches Logical Nodes based on:

  • Logical Node class (CSWI, XCBR, MMXU, …)

  • Logical Node prefix

  • Logical Node instance number

image2023-6-29_16-12-59.png

Observe that the mapping is done based on the LN Class, LN prefix and LN instance. The system maps the signal to the most appropriate LN.

Automatic mapping only matches Logical Nodes of the same class. Cross-class mappings (for example mapping a specification MMXU to an IED MMTR because the IED reports metering values where the spec asked for measurement) require manual mapping.