Inferensys

Glossary

Logical Node (LN)

A Logical Node (LN) is the smallest functional building block in the IEC 61850 data model, representing a specific protection, control, or measurement function, such as a circuit breaker (XCBR) or distance protection (PDIS).
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
IEC 61850 DATA MODEL

What is a Logical Node (LN)?

A Logical Node (LN) is the smallest functional building block in the IEC 61850 data model, representing a specific protection, control, or measurement function within an Intelligent Electronic Device (IED).

A Logical Node (LN) is a standardized, object-oriented abstraction defined by IEC 61850 that encapsulates a single, well-defined substation automation function, such as a circuit breaker (XCBR), distance protection (PDIS), or current measurement (TCTR). Each LN groups related Data Objects (DO)—like position, mode, and health—into a self-contained module, enabling interoperability between multi-vendor Intelligent Electronic Devices (IEDs) by providing a common semantic interface regardless of the underlying hardware implementation.

LNs are instantiated within a Logical Device (LD) on a physical IED and communicate via abstract services mapped to protocols like MMS, GOOSE, or Sampled Values. The IEC 61850 standard defines over 90 logical node classes grouped by function—protection (P), control (C), metering (M), and system services (S)—allowing engineers to design Substation Automation Systems (SAS) by composing these functional blocks rather than hard-coding proprietary logic, dramatically simplifying configuration, testing, and lifecycle management.

IEC 61850 DATA MODEL

Core Characteristics of Logical Nodes

Logical Nodes are the atomic functional elements within the IEC 61850 object model, each encapsulating a specific protection, control, or measurement capability with standardized data objects and services.

01

Standardized Functional Encapsulation

Each LN represents a well-defined, self-contained function within a physical IED. The standard pre-defines the data objects and behavior for common utility functions, ensuring interoperability between devices from different manufacturers.

  • XCBR: Circuit breaker control and monitoring
  • PDIS: Distance protection element
  • MMXU: Measurement unit for currents and voltages
  • PTRC: Protection trip conditioning logic
02

Hierarchical Naming Convention

Every LN instance is uniquely identified by a structured reference path that reflects its physical location in the substation hierarchy. This path concatenates the IED name, access point, and logical device.

  • Format: IEDNameLDName/LNClassNameInstanceID
  • Example: Q1SB1PDIS1 refers to instance 1 of distance protection in bay Q1
  • Enables precise addressing for GOOSE publisher-subscriber bindings and SCADA data mapping
03

Mandatory vs. Optional Data Objects

The IEC 61850-7-4 standard defines a strict schema of mandatory (M) and optional (O) data objects within each LN class. This guarantees a baseline of functionality while allowing manufacturers to differentiate.

  • Mandatory: Mod (Mode), Beh (Behavior), Health (Health), NamPlt (Name Plate) are common to all LNs
  • Optional: Advanced diagnostic or control points specific to a vendor's implementation
  • Ensures that critical operational data is always present and uniformly accessible
04

Common Logical Node Class

All LNs inherit from a common logical node class (LLN0), which provides fundamental attributes for self-supervision and mode control. This inheritance enforces a consistent management interface across every function in the substation.

  • Mode (Mod): Controls operational state—On, Off, Test, Test/Blocked
  • Behavior (Beh): Reports the actual current functional state
  • Health (Health): Reflects internal self-diagnostic status (Ok, Warning, Alarm)
  • Name Plate (NamPlt): Provides vendor, version, and configuration metadata
05

Service Interfaces for Data Access

LNs expose their data through standardized Abstract Communication Service Interfaces (ACSI) , which are mapped to specific protocols like MMS. These services define how clients read, write, report, and log data.

  • GetDataValues/SetDataValues: Immediate read/write of data object attributes
  • Reporting: Buffered and unbuffered change-driven event reporting
  • Logging: Time-stamped historical data storage for disturbance analysis
  • GOOSE Control: Direct multicast publishing of status changes for peer-to-peer tripping
06

Logical Device Containment

LNs are grouped into Logical Devices (LDs) within a physical IED. An LD typically represents a coherent protection or control domain, such as a bay controller or a measurement unit, and always contains an LLN0 for management and an LPHD for physical device information.

  • LLN0: Manages the LD's datasets, reports, and GOOSE control blocks
  • LPHD: Maps to the physical hardware, providing nameplate and health data
  • Allows a single IED to host multiple independent functional domains, such as separate bays
LOGICAL NODE ESSENTIALS

Frequently Asked Questions

Clear answers to the most common questions about IEC 61850 Logical Nodes, the fundamental building blocks of substation automation data models.

A Logical Node (LN) is the smallest functional building block in the IEC 61850 data model, representing a specific, well-defined protection, control, measurement, or monitoring function within a substation automation system. Each LN is a named grouping of Data Objects and their associated attributes that together model a real-world power system function, such as a circuit breaker (XCBR), a distance protection element (PDIS), or a current transformer measurement (TCTR). The standard defines over 90 standardized LN classes grouped by function—protection (P), control (C), metering (M), generic (G), and more—ensuring semantic interoperability between Intelligent Electronic Devices (IEDs) from different manufacturers without requiring custom signal mapping.

IEC 61850-7-4 FUNCTIONAL DECOMPOSITION

Common Logical Node Groups and Examples

Standardized logical node groups defined by IEC 61850-7-4, each representing a category of substation functions with representative instances.

LN Group PrefixFunctional CategoryExample LNLN Class DescriptionTypical Host IED

A

Automatic Control

ATCC

Automatic tap changer control for transformer voltage regulation

Voltage Regulator Relay

C

Supervisory Control

CSWI

Switch controller handling Select Before Operate (SBO) sequences for circuit breakers and disconnectors

Bay Control Unit

G

Generic Function References

GGIO

Generic process I/O mapping binary status and analog setpoints not modeled by dedicated LNs

RTU or Gateway

I

Interfacing and Archiving

IHMI

Human-machine interface for local operator display and alarm annunciation

Station HMI

L

System Logical Nodes

LLN0

Logical node zero representing the access point and common data set for a physical IED

All IEDs

M

Metering and Measurement

MMXU

Three-phase measurement unit calculating RMS voltage, current, power, and frequency

Protection IED or Meter

P

Protection Functions

PDIS

Distance protection with multi-zone quadrilateral or mho characteristics for transmission line fault detection

Distance Protection Relay

R

Protection Related Functions

RSYN

Synchrocheck function verifying voltage, phase angle, and frequency differences before breaker closing

Bay Control or Protection IED

S

Sensors and Monitoring

SIML

Insulation medium supervision monitoring SF6 gas density, pressure, and temperature in GIS equipment

Condition Monitoring IED

T

Instrument Transformers

TCTR

Current transformer representing the physical CT ratio, accuracy class, and secondary circuit

Merging Unit

X

Switchgear

XCBR

Circuit breaker with position indication, operation counter, and trip coil supervision

Circuit Breaker IED or Bay Control Unit

Y

Power Transformers

YPTR

Power transformer monitoring winding hot-spot temperature, aging rate, and cooling system status

Transformer Monitoring IED

Z

Other Power System Equipment

ZBAT

Battery system monitoring state of charge, terminal voltage, and charge/discharge current limits

Battery Management System

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.