The physical or virtual device
A protection relay, bay controller, merging unit or other IEC 61850 server.
IEC 61850 is a standardized way for substation devices to describe their functions, exchange data and share engineering information. Its biggest idea is not a cable or a packet—it is a common, meaningful model of the power-system function.
Instead of saying “read register 1024,” an IEC 61850 client can discover a named object that represents a real function—such as breaker position, phase current or protection pickup—and read its value together with quality and timestamp.
The names may look unfamiliar at first, but the hierarchy is logical once each level has a job.
A protection relay, bay controller, merging unit or other IEC 61850 server.
A grouping boundary inside the IED. One physical relay can contain several logical devices for protection, measurement or control.
A standardized functional block. For example, XCBR represents circuit-breaker information, while MMXU commonly represents measurements.
A meaningful item inside the function, such as Pos for position or A for current.
The actual value and supporting details, such as stVal, quality q and timestamp t.
An object such as XCBR.Pos can provide the state, quality and timestamp. This lets the engineer distinguish a valid fresh observation from an old, questionable or invalid value.
Two tools may display the same “1,” but only one may preserve the correct IED, object reference, quality, timestamp and acquisition path. IEC 61850 engineering is about that context as much as the value itself.
Used to associate with an IED, discover its model, read and write supported data, manage reports, transfer files and perform approved controls.
The IED sends selected changes through a DataSet and Report Control Block instead of waiting for the client to repeatedly poll every point.
Multicast messages distribute fast event states between devices, with sequence and retransmission behavior designed for dependable delivery.
High-rate streams carry sampled current and voltage values, commonly between merging units and protection or measurement functions.
XML-based Substation Configuration Language files describe devices, communication, DataSets, reports, GOOSE, Sampled Values and system intent.
Direct and Select-Before-Operate define how approved commands are prepared, checked, executed and confirmed.
Ethernet is only part of the transport. The standard also defines data meaning, services, configuration and system engineering.
SCL describes configured intent. The online IED model shows what the server currently exposes. A good workflow compares both.
An IED can answer ping while TCP port 102, association, permissions or the application service still fails.
Always read quality and timestamp before treating a displayed value as evidence.
The next tutorial shows how to prepare the network, add an IED by IP address in ARSAS, complete discovery and verify your first live value.
The current stable build includes Rev.3 IO List FAT import, an executive AS TESTED evidence report, a loaded Engineering/FAT workspace session, and direct receive-only GOOSE plus bounded SMV capture from each IED card.
Use the installer for a normal workstation, choose the portable single EXE for an approved no-install deployment, and verify the published SHA-256 before use.
What’s new, engineering boundaries and signing status →