Wrapper/Logical Node Instance
IEC 61850 IN MICOM IEDS
IEC 61850 is implemented by use of a separate Ethernet card. This Ethernet card manages the majority of the
IEC 61850 implementation and data transfer to avoid any impact on the performance of the protection functions.
To communicate with an IEC 61850 IED on Ethernet, it is necessary only to know its IP address. This can then be
configured into either:
An IEC 61850 client (or master), for example a bay computer (MiCOM C264)
An MMS browser, with which the full data model can be retrieved from the IED, without any prior knowledge
of the IED
The IEC 61850 compatible interface standard provides capability for the following:
Read access to measurements
Refresh of all measurements at the rate of once per second.
Generation of non-buffered reports on change of status or measurement
SNTP time synchronization over an Ethernet link. (This is used to synchronize the IED's internal real time
GOOSE peer-to-peer communication
Disturbance record extraction by file transfer. The record is extracted as an ASCII format COMTRADE file
Controls (Direct and Select Before Operate)
Setting changes are not supported in the current IEC 61850 implementation. Currently these setting changes are carried out
using the settings application software.
IEC 61850 DATA MODEL IMPLEMENTATION
The data model naming adopted in the IEDs has been standardised for consistency. Therefore the Logical Nodes
are allocated to one of the five Logical Devices, as appropriate.
The data model is described in the Model Implementation Conformance Statement (MICS) document, which is
available as a separate document.
IEC 61850 COMMUNICATION SERVICES IMPLEMENTATION
The IEC 61850 communication services which are implemented in the IEDs are described in the Protocol
Implementation Conformance Statement (PICS) document, which is available as a separate document.
Identifies the major functional areas within the IEC 61850 data model. Either 3 or 6 characters are
used as a prefix to define the functional group (wrapper) while the actual functionality is identified by
a 4 character Logical Node name suffixed by an instance number.
For example, XCBR1 (circuit breaker), MMXU1 (measurements), FrqPTOF2 (overfrequency protection,
This next layer is used to identify the type of data you will be presented with. For example, Pos
(position) of Logical Node type XCBR.
This is the actual data (measurement value, status, description, etc.). For example, stVal (status value)
indicating actual position of circuit breaker for Data Object type Pos of Logical Node type XCBR.
Chapter 18 - Communications