I want to understand IEC 61850
Learn why IEC 61850 uses named objects instead of register numbers, how an IED model is organized, and where MMS, Reporting, GOOSE and SCL fit.
Plain language · practical steps · engineering depth when you need it
Learn IEC 61850 by doing useful work.
You do not need to memorize every standard term before opening an IED. Start with the problem you want to solve, follow a safe ARSAS workflow, and learn the protocol concept behind each step.
BeginnerUnderstand the words and mental model without vendor jargon
PracticalFollow the same buttons and screens used in ARSAS
EngineeringKeep quality, timestamps, identity and failure boundaries visible
Field-readyTurn observations into repeatable FAT and troubleshooting evidence
Choose your starting point
What are you trying to achieve today?
Each path gives you a useful takeaway even when you do not install ARSAS yet.
I want to connect an IED
Prepare the IP address, check TCP port 102, add the device, discover its live model and read one point with value, quality and timestamp.
I need FAT or commissioning evidence
Choose an approved IO List for repeatable indication testing, or start from the IED endpoint for broader reporting, GOOSE, file and control checks.
I need to troubleshoot
Start from the symptom—connection failed, reporting silent, RCB occupied, GOOSE sequence unclear, COMTRADE missing or SCL rejected.
IEC 61850 is a shared language for substation functions and communication.
An IED exposes named functions and data—such as breaker position, current, voltage or protection status. Tools can discover these names, read their values, subscribe to changes and exchange configuration through SCL files.
ARSAS keeps the observation and its context together.
Do not look at a value alone. Keep the IED identity, object reference, quality, device timestamp, ARSAS capture time and acquisition source attached so another engineer can understand what happened.
Recommended learning path
Build confidence in small, useful steps.
Understand the IEC 61850 mental model
Learn IED, Logical Device, Logical Node, Data Object, Data Attribute and Functional Constraint using familiar substation examples.
Connect one approved IED
Verify the network route and port 102, create the device in ARSAS and complete live discovery.
Read one point correctly
Check the value together with quality, timestamp, object reference and acquisition source.
Learn how changes arrive
Understand DataSets and Reporting before treating polling, BRCB or URCB as interchangeable.
Move to project evidence
Use IO List FAT, GOOSE analysis, file retrieval, SCL comparison or guarded control according to the approved procedure.
Learning principle
Simple language does not mean weak engineering.
Every tutorial separates what you observed, what you inferred and what still needs independent verification. ARSAS guidance does not replace the IED manual, approved FAT procedure, switching authority or IEC 61850 conformance testing.
Verified stable release · ARSAS 1.6.33
Download the release-grade IEC 61850 workstation for Windows.
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 →