IEC 61850 basics

IEC 61850 is the relay model, not just a communication port.

For ARServer users, IEC 61850 is the source side: the relay or IED exposes named electrical objects with values, quality, and timestamp context. ARServer reads selected points and republishes them to systems that need simpler interfaces.

Source protocol

What you need to understand before reading relay data

IEC 61850 is widely used in substation automation because it describes equipment behavior using a structured model. Instead of treating the relay as a flat list of numbers, it organizes data into logical devices, logical nodes, data objects, and data attributes.

Core terms

  • IED: the relay, bay controller, meter, or intelligent electronic device that exposes data.
  • Logical node: a functional block such as XCBR for circuit breaker, PTOC for overcurrent protection, or MMXU for measurements.
  • Data object: a named object inside the logical node, such as Pos, Op, or A.
  • Data attribute: the actual readable attribute, such as stVal, q, or t.
  • Function constraint: a grouping such as status, measurement, control, configuration, or description.

Why MMS matters

In ARServer’s normal workflow, the IED is read through IEC 61850 MMS over TCP. MMS gives access to named object references instead of only numeric addresses. That is powerful, but it is not always convenient for HMI and SCADA tools that expect Modbus registers or simple tags.

Why SCL files help

SCL files such as ICD, CID, IID, and SCD describe the IED engineering model. When they are available, they help users plan object references, datasets, and expected signals before connecting to the live device.

Field rule: do not map every IEC 61850 point. Start with breaker position, protection start/trip, alarms, mode/status, and key measurements. Validate the value, quality, and timestamp before giving it to HMI or SCADA.

How ARServer fits

ARServer uses IEC 61850 as the source of truth, then keeps a controlled runtime cache. From that cache, it publishes selected values to Modbus TCP and MQTT while keeping quality and timestamp context visible for engineering review.