Add the IED endpoint
Establish an independent MMS association and keep service failures attributable to the originating device.
IEC 61850 MMS client · live IED browser · Windows
Browse the live IEC 61850 server model directly from the IED.
ARSAS connects to an approved IEC 61850 endpoint over MMS, discovers the live model and keeps values, quality, timestamps, DataSets, Report Control Blocks, controls and diagnostics inside the same per-IED engineering session.
Live discoveryLogical Devices, Logical Nodes, Data Objects and Data Attributes
Typed valuesValue, quality, timestamp and live MMS type context
Engineering objectsDataSets, BRCBs, URCBs and control models
Per-IED stateAssociation, selections and diagnostics remain isolated
Practical workflow
From an approved IP address to searchable live evidence.
Expose useful protocol evidence without reconstructing the same context across several disconnected applications.
Discover the server model
Enumerate the logical hierarchy and live type information required for values, reports and supported controls.
Search and select signals
Filter large models and select the exact points required for FAT, SAT, commissioning or troubleshooting.
Observe attributable values
Retain quality, timestamps, recent-change evidence and the verified acquisition source.
Real application evidence
One model browser, one live-value workspace, one IED context.
Inspect current device behavior rather than relying only on a static engineering-file tree.
01Start from the device
Add the intended endpoint or open available SCL context.
02Searchable live values
Review device, quality, timestamp, source and change context together.
FAT, SAT, commissioning and protocol troubleshooting
- Confirm that the IED accepts an MMS association
- Compare live object availability with available SCL files
- Find DataSets and Report Control Blocks before reporting tests
- Inspect ctlModel before control tests
- Separate model, service and communication problems
An MMS connection is not proof of complete interoperability.
A successful association does not prove that reporting, controls, file services, GOOSE binding or every modeled object is correct. ARSAS keeps those validations explicit and does not claim conformance certification.
Move from discovery to report-based monitoring.
Inspect DataSet coverage, BRCB and URCB ownership, trigger options and fallback behavior.
Compare live behavior with SCL context.
Keep configured intent and the current device model visible together.
Verified stable release
Download ARSAS 1.6.17 for Windows.
Use the installer for a normal workstation, choose the portable ZIP for a controlled folder deployment, and verify the published SHA-256 before use.
What’s new, limitations and signing status →