IEC 61850 Logical Nodes Explained: Complete Reference for Substation Engineers

By | April 9, 2026

Every piece of data in an IEC 61850 system lives inside a logical node. A circuit breaker position is inside XCBR. An overcurrent trip signal is inside PTOC. A voltage measurement is inside MMXU. A GOOSE control block is inside LLN0.

Logical nodes are the building blocks of the IEC 61850 data model. They represent functions — not physical devices. A single IED can contain dozens of logical nodes. A single logical node can appear in GOOSE messages, MMS reports, SCL files, and Wireshark captures.

If you do not understand logical nodes, you cannot read an SCL file, configure a GOOSE subscription, decode an MMS object reference, or troubleshoot any IEC 61850 system.

This guide covers what logical nodes are, how they are organized into groups, the most important LN classes you will encounter in substations, and how to read logical node references in practice.

1. What Is a Logical Node

A logical node is a named container for a specific function inside an IED. It groups together all the data objects related to that function.

For example, the logical node XCBR represents a circuit breaker. It contains data objects like:

  • Pos — the current position (open/closed)
  • OpCnt — operation counter
  • CBOpCap — circuit breaker operating capability
  • BlkOpn — block opening command
  • BlkCls — block closing command

The logical node does not care which physical device it runs on. XCBR could be inside an ABB relay, a Siemens relay, or a Schneider bay controller. The data model is the same everywhere — that is the whole point of IEC 61850.

2. Where Logical Nodes Sit in the Data Model Hierarchy

The IEC 61850 data model is a strict hierarchy:

IED → Access Point → Server → Logical Device → Logical Node → Data Object → Data Attribute

Example path: IED1/S1/Server/PROT/PTOC1.Op.general

LevelExampleMeaning
IEDIED1Physical device
Logical DevicePROTContainer for related LNs (e.g., protection functions)
Logical NodePTOC1Overcurrent protection, instance 1
Data ObjectOpOperate (trip output)
Data AttributegeneralGeneral trip indication (boolean)

Multiple instances of the same LN class are distinguished by an instance number: PTOC1, PTOC2, PTOC3, etc.

3. The 13 Logical Node Groups

Every logical node name starts with a letter that identifies its group. The groups are defined in IEC 61850-7-4.

GroupLetterDescriptionExamples
SystemLSystem-level LNs present in every IEDLLN0, LPHD
ProtectionPProtection functionsPTOC, PDIS, PDIF, PTOV, PTUF
SwitchgearXCircuit breakers, disconnectorsXCBR, XSWI
MeasurementMMetering and measurementMMXU, MMTR, MSQI, MHAI
ControlCSupervisory controlCSWI, CILO, CPOW
Protection-RelatedRFunctions supporting protectionRREC, RPSB, RSYN, RBRF
Automatic ControlAAutomatic control functionsARCO, ATCC, AVCO, ANCR
Sensor/MonitoringSSensors and condition monitoringSIML, SIMG, SPDC, STMP
Instrument TransformerTCT and VT modelsTCTR, TVTR
Power TransformerYTransformer and related functionsYPTR, YLTC, YPSH
Further EquipmentZOther power system equipmentZBAT, ZGEN, ZMOT, ZCAP
Interfacing/ArchivingIInterfacing and data archivingIHMI, ITCI, IARC
GenericGGeneric function referencesGGIO, GAPC, GSAL

4. System Logical Nodes (Group L)

These are mandatory in every IED. They provide system-level information.

LN ClassNamePurpose
LLN0Logical Node ZeroThe “root” LN of each logical device. Contains datasets, GOOSE control blocks, report control blocks, and log control blocks. Every logical device has exactly one LLN0.
LPHDPhysical Device InformationRepresents the physical IED hardware. Contains nameplate data, health status, power-up counter, and watchdog information. Every server has exactly one LPHD.

LLN0 is the most important LN in practice because all GOOSE and report control blocks are defined inside LLN0. When you configure a GOOSE publisher or a buffered report, you are working inside LLN0.

5. Protection Logical Nodes (Group P)

The largest group. Each LN represents one protection function.

LN ClassNameIEEE Device #Purpose
PTOCTime Overcurrent50/51Overcurrent protection (definite time and inverse time)
PIOCInstantaneous Overcurrent50Instantaneous overcurrent protection
PDISDistance Protection21Impedance-based distance protection
PDIFDifferential Protection87Current differential protection (transformer, line, bus)
PTOVTime Overvoltage59Overvoltage protection
PTUVTime Undervoltage27Undervoltage protection
PTOFTime Overfrequency81OOverfrequency protection
PTUFTime Underfrequency81UUnderfrequency protection
PTTRThermal Overload49Thermal protection
PDOPDirectional Overpower32Directional power protection
PHIZGround Detector (high impedance)87NHigh-impedance ground fault protection
PSCHProtection SchemeProtection communication scheme (permissive, blocking, etc.)
PPAMPhase Angle Measuring78Phase angle measurement for protection

Key Data Objects in Protection LNs

Every protection LN typically contains:

  • Op — operate (trip output): the key data object. Op.general = TRUE means the function has tripped.
  • Str — start: the function has detected a fault but not yet tripped.
  • StrVal — the measured value that caused the start.
  • Settings like SetA, SetB — setting groups for different operating conditions.

6. Switchgear Logical Nodes (Group X)

LN ClassNamePurpose
XCBRCircuit BreakerModels a circuit breaker. Contains position (Pos), operating capability, operation counter, and block commands.
XSWIDisconnector / SwitchModels disconnectors, earthing switches, and load break switches.

Key Data Objects

  • Pos — position (DPC: double point control). Values: intermediate (00), off/open (01), on/closed (10), bad state (11).
  • OpCnt — operation counter.
  • BlkOpn / BlkCls — block open / block close commands.
  • CBOpCap — circuit breaker operating capability.

XCBR is one of the most frequently referenced logical nodes. It appears in GOOSE messages (breaker position), control commands (open/close), and interlocking logic.

7. Measurement Logical Nodes (Group M)

LN ClassNamePurpose
MMXUMeasurementThree-phase electrical measurements: voltage, current, power, power factor, frequency. The most commonly used measurement LN.
MMTRMeteringEnergy metering (kWh, kVArh). Accumulates energy values over time.
MSQISequence and ImbalancePositive, negative, and zero sequence quantities. Used for unbalance monitoring.
MHAIHarmonics and InterharmonicsHarmonic analysis: individual harmonic magnitudes and THD.
MSTAMetering StatisticsStatistical analysis of measurements (min, max, average).

Key Data Objects in MMXU

  • TotW — total active power (watts)
  • TotVAr — total reactive power
  • TotVA — total apparent power
  • TotPF — total power factor
  • Hz — frequency
  • PhV — phase-to-neutral voltages (phsA, phsB, phsC)
  • A — phase currents (phsA, phsB, phsC)
  • PPV — phase-to-phase voltages

8. Control Logical Nodes (Group C)

LN ClassNamePurpose
CSWISwitch ControllerControls a switch (XCBR or XSWI). Receives open/close commands from operators or automation. One CSWI per controlled switch.
CILOInterlockingImplements interlocking logic. Prevents unsafe switching operations (e.g., opening a disconnector under load).
CPOWPoint-on-Wave SwitchingControlled switching at specific point on the voltage/current waveform to minimize transients.

CSWI is the LN that operators interact with. When a dispatcher sends an “open breaker” command from SCADA, the command goes to CSWI, which verifies interlocking (via CILO) and then sends the operate command to XCBR.

These support protection functions but are not protection functions themselves.

LN ClassNamePurpose
RRECAuto-RecloserAutomatic reclosing after a trip. Controls reclosing time, number of shots, and lockout.
RBRFBreaker FailureBreaker failure protection. If the breaker does not open within the expected time after a trip command, RBRF trips backup breakers.
RSYNSynchronism CheckChecks voltage magnitude, phase angle, and frequency before closing a breaker to synchronize two systems.
RPSBPower Swing BlockingDetects power swings and blocks distance protection from tripping during stable swings.

10. Automatic Control Logical Nodes (Group A)

LN ClassNamePurpose
ATCCTap Changer ControllerAutomatic voltage regulation via transformer tap changer.
ARCOReactive Power ControlAutomatic reactive power compensation control.
AVCOVoltage ControlAutomatic voltage regulation.
ANCRNeutral Current RegulatorControls neutral current (e.g., for Petersen coil tuning).

11. Sensor and Monitoring Logical Nodes (Group S)

LN ClassNamePurpose
SIMLInsulation Medium LevelOil level monitoring in transformers.
SIMGInsulation Medium GasDissolved gas analysis (DGA) monitoring.
STMPTemperatureTemperature measurement.
SPDCPartial DischargePartial discharge monitoring.

12. Transformer Logical Nodes (Groups T and Y)

Group T — Instrument Transformers

LN ClassNamePurpose
TCTRCurrent TransformerModels a current transformer. Used with merging units on the process bus.
TVTRVoltage TransformerModels a voltage transformer.

Group Y — Power Transformers

LN ClassNamePurpose
YPTRPower TransformerRepresents the power transformer itself.
YLTCLoad Tap ChangerModels the tap changer mechanism.
YPSHPower Shunt ReactorShunt reactor model.

13. Interfacing and Archiving Logical Nodes (Group I)

LN ClassNamePurpose
IHMIHMI InterfaceHuman-machine interface parameters.
ITCITelecontrol InterfaceInterface to telecontrol protocols (e.g., IEC 104, DNP3).
IARCArchivingData archiving and logging.

14. Generic Logical Nodes (Group G)

LN ClassNamePurpose
GGIOGeneric Process I/OGeneric digital and analog I/O points that do not fit any specific LN class. The “catch-all” LN. Used for auxiliary contacts, LEDs, binary inputs/outputs.
GAPCGeneric Automatic Process ControlGeneric PID controller or automation function.
GSALGeneric Security ApplicationSecurity-related functions per IEC 62351.

GGIO is extremely common. Whenever a device has I/O points that do not belong to a standard protection or measurement function, they go into GGIO.

15. Common Data in Every Logical Node

Every logical node (except LPHD) inherits these mandatory data objects:

Data ObjectCDCMeaning
ModINCMode control — on, off, test, test/blocked
BehINSBehaviour — reflects the current operating mode
HealthINSHealth status — ok, warning, alarm
NamPltLPLNameplate — vendor name, software revision, configuration revision

These four data objects are always present. They let you check if a logical node is active (Beh = on), healthy (Health = ok), and what mode it is running in (Mod = on vs test).

16. How to Read a Logical Node Reference

An IEC 61850 object reference follows this pattern:

LogicalDeviceName/LogicalNodeNameFunctionalConstraintFunctionalConstraint FunctionalConstraintDataObject.DataAttribute

Example

PROT/PTOC1$ST$Op.general

PartValueMeaning
Logical DevicePROTProtection logical device
Logical NodePTOC1Overcurrent protection, instance 1
Functional ConstraintSTStatus information
Data ObjectOpOperate (trip)
Data AttributegeneralGeneral trip (boolean)

Common Functional Constraints

FCMeaning
STStatus
MXMeasured values (analog)
COControl
CFConfiguration
SPSetting group (setpoints)
SGSetting group parameters

17. Logical Nodes in SCL, GOOSE, and MMS

In SCL Files

Logical nodes appear in the IED section of SCL files:

xml

<LN lnClass="PTOC" inst="1" lnType="PTOC_Type">
  <DOI name="Op">
    <DAI name="general" />
  </DOI>
</LN>

In GOOSE Messages

GOOSE datasets reference data objects inside logical nodes:

xml

<FCDA ldInst="PROT" lnClass="XCBR" lnInst="1" doName="Pos" daName="stVal" fc="ST" />

This means: “Include the status value of the Position data object from XCBR instance 1 in the PROT logical device.”

In MMS

An MMS client reads data using the full object reference:

IED1PROT/PTOC1$ST$Op → reads the trip status of overcurrent protection

18. Quick Reference: 50 Most Used Logical Nodes

LNGroupFunction
LLN0LLogical device root — datasets, GOOSE, reports
LPHDLPhysical device information
XCBRXCircuit breaker
XSWIXDisconnector / switch
CSWICSwitch controller
CILOCInterlocking
CPOWCPoint-on-wave switching
PTOCPTime overcurrent (50/51)
PIOCPInstantaneous overcurrent (50)
PDISPDistance protection (21)
PDIFPDifferential protection (87)
PTOVPTime overvoltage (59)
PTUVPTime undervoltage (27)
PTOFPTime overfrequency (81O)
PTUFPTime underfrequency (81U)
PTTRPThermal overload (49)
PDOPPDirectional overpower (32)
PHIZPHigh-impedance ground fault (87N)
PSCHPProtection scheme
PPAMPPhase angle measuring (78)
PFRCPFrequency rate of change
RRECRAuto-recloser (79)
RBRFRBreaker failure (50BF)
RSYNRSynchronism check (25)
RPSBRPower swing blocking (68)
RDRERDisturbance recorder
RADRRAnalog disturbance recorder
MMXUMThree-phase measurements
MMTRMEnergy metering
MSQIMSequence and imbalance
MHAIMHarmonics
MSTAMMetering statistics
ATCCATap changer controller
ARCOAReactive power control
AVCOAVoltage control
ANCRANeutral current regulator
TCTRTCurrent transformer
TVTRTVoltage transformer
YPTRYPower transformer
YLTCYLoad tap changer
SIMLSInsulation medium (oil) level
SIMGSInsulation medium gas (DGA)
STMPSTemperature monitoring
SPDCSPartial discharge
ZBATZBattery
ZGENZGenerator
ZMOTZMotor
GGIOGGeneric process I/O
GAPCGGeneric automatic process control
IHMIIHMI interface

Summary

Logical nodes are the language of IEC 61850. Every function in a digital substation is modeled as a logical node with standardized data objects.

The key points:

  • The first letter tells you the group: P = protection, X = switchgear, M = measurement, C = control
  • LLN0 holds all GOOSE control blocks, datasets, and report control blocks
  • XCBR and CSWI are the most referenced LNs for breaker control
  • PTOC and PDIS are the most common protection LNs
  • MMXU is the standard measurement LN for voltage, current, and power
  • GGIO is the catch-all for anything that does not fit a specific class
  • Every LN has Mod, Beh, Health, and NamPlt as mandatory data objects
  • Object references follow the pattern: LD/LNFCFCFCDO.DA

Once you know the logical node names, you can read any SCL file, any GOOSE dataset, and any MMS object reference. They are the vocabulary of IEC 61850.

Author: Zakaria El Intissar

I'm an automation and industrial computing engineer with 12 years of experience in power system automation, SCADA communication protocols, and electrical protection. I build tools and write guides for Modbus, DNP3, IEC 101/103/104, and IEC 61850 on ScadaProtocols.com to help engineers decode, analyze, and troubleshoot real industrial communication systems.

Leave a Reply

Your email address will not be published. Required fields are marked *