IED signal selection
Inspect values, quality, logical node context, and IEC object references before publishing anything to HMI or SCADA.
Free Apache-2.0 Windows gateway
IEC 61850 MMS values routed cleanly to Modbus TCP and MQTT.
ARServer helps automation engineers inspect IEC 61850 IED data, bind selected signals to Modbus TCP, publish MQTT topics, and validate gateway behavior during HMI, SCADA, FAT/SAT, relay testing, and substation automation lab work.
IEC 61850 MMSIED acquisition
Modbus TCPHMI/SCADA map
MQTTBroker topics
What you can do
A practical bridge between relay data and tools engineers already use.
ARServer keeps the engineering path visible: select the IED signal, confirm the IEC Reference, map the output, then monitor runtime quality and stale state.
Modbus TCP output
Expose selected values as familiar status points and registers for SCADA, DCS, gateways, and FUXA dashboards.
MQTT publishing
Publish value, quality, status, and optional JSON state payloads to an external broker for modern dashboard workflows.
Workflow
Discover, select, bind, publish, validate.
The application is organized around the real engineering sequence, so the user can understand every step before a signal is exposed to another system.
Source
IEC 61850 IED
Relay, bay controller, or test model
MMS values
Gateway
ARServer
Selection, quality, mapping, acquisition, diagnostics
Modbus TCP
MQTT
HMI / SCADA
Register map
Client reads selected values from ARServer cache
Broker / Dashboard
Topic stream
Subscribers receive selected values and state
Field value
Useful gateway data is not only the value. It is the value plus quality, reference, and mapping context.
Readable references reduce mistakes. The IEC Reference stays visible so users can confirm the exact source point before exposing it to Modbus or MQTT.
Cache-based outputs are safer. HMI polling reads ARServer's cache instead of triggering direct relay reads on every Modbus request.
Fast CB is targeted. Breaker/status points can be prioritized without letting analog points block the critical refresh path.
Screenshots
A clean Windows interface for discovery, binding, and runtime monitoring.
These screens show the practical path from IED workspace to live IEC values, Modbus TCP map, and MQTT topic publishing.
Quick start
Download the portable ZIP, run ARServer, then map your first signals.
ARServer is a local Windows desktop app. It can be explored in mock mode immediately. Real IED testing uses IEC 61850 MMS runtime components supplied by the user and an optional MQTT broker when MQTT output is enabled.
- 1 Download the Windows portable ZIP from GitHub Releases.
- 2 Extract the ZIP and run ArServer.exe. The app binary is packaged as a single executable.
- 3 Use mock mode first, or add your IEC 61850 runtime components for real IED testing.
- 4 Add an IED, select signals, validate the Modbus map, configure MQTT if needed, then start runtime.
FAQ
Common questions before trying ARServer.
The project is designed to be easy to evaluate while staying honest about engineering validation and field responsibility.
Is ARServer free?
Yes. ARServer core is free and open source under Apache-2.0. There is no subscription and no license key for the ARServer core application.
Can I try it without a relay?
Yes. Mock mode lets users explore signal selection, Modbus mapping, MQTT publishing, and runtime screens before connecting to a real IED.
Is 10 ms polling guaranteed?
No. It is a scheduler target for expert bench evaluation with one/few selected points. Actual response depends on IED behavior, network latency, and selected point count.