ARServerMQTT Learning
ENID

MQTT basics

MQTT turns selected relay values into subscribable data streams.

For ARServer users, MQTT is useful when relay values need to reach dashboards, middleware, historians, or IoT-style data pipelines through a broker instead of direct HMI polling.

Data platform output

What MQTT means in an ARServer workflow

MQTT uses a publish/subscribe model. ARServer publishes selected values to topics, and consumers subscribe to those topics. The broker becomes the communication hub between the gateway and dashboards or middleware.

Core terms

  • Broker: the MQTT server that receives messages and forwards them to subscribers.
  • Topic: a hierarchical name such as arserver/IED/tag/state.
  • Payload: the message body, often JSON for gateway data.
  • Subscriber: dashboard, historian, middleware, or script consuming the data.

Why topic design matters

Bad topic names make data hard to find and hard to maintain. A clear scheme should identify the gateway, IED, signal, and state type without forcing every consumer to know IEC 61850 object syntax.

Do not publish blind values: include quality, timestamp, and communication status context so dashboards do not display stale relay data as if it were live.

How ARServer fits

ARServer reads selected IEC 61850 values into a runtime cache. MQTT output can publish the current state of those selected points to a broker. This is useful for monitoring dashboards, engineering telemetry, and integration experiments.

IEC 61850 to MQTTLearn how ARServer converts relay values into useful topics and payloads.TroubleshootingCheck broker connection, topic routing, and stale data behavior.