Connect to the intended relay
Use the existing per-IED MMS association so file operations remain attached to the correct endpoint and project context.
MMS file services · relay fault records · COMTRADE retrieval
Retrieve protection-relay fault records inside the correct IED context.
ARSAS uses IEC 61850 MMS file services to probe available directories, browse bounded paths and download disturbance-record files while preserving endpoint ownership, transfer progress and negative service evidence.
Service discoveryProbe whether the connected IED exposes usable MMS file services
Bounded browsingNavigate approved paths without uncontrolled recursive traversal
Transfer evidenceProgress, cancellation, timeout and negative responses remain visible
Record contextGroup COMTRADE-related files around the originating IED and event
Fault-record workflow
Move from a relay event to a complete downloadable record set.
Different relays can expose different directory layouts and naming conventions. ARSAS keeps discovery transparent instead of assuming that every device stores files in the same location.
Probe and browse available paths
Inspect the directories exposed by the IED with explicit boundaries, cancellation and visible service failures.
Identify the relevant disturbance record
Review filenames, timestamps and companion extensions such as CFG, DAT, HDR and INF without hiding incomplete sets.
Download and retain transfer evidence
Preserve source path, destination, progress, retry boundary and negative result details for later engineering review.
Treat a fault record as a set—not just one downloaded file.
A useful disturbance record may include configuration, sampled data, header and information companions. ARSAS provides the foundation to recognize those relationships while keeping missing or unexpected files visible.
- CFG configuration file
- DAT sampled data file
- HDR descriptive header when available
- INF or approved companion information
Negative evidence is part of the result.
An empty directory, access rejection, timeout, unsupported service or partial record set should not be presented as success. ARSAS keeps those outcomes attributable to the originating relay.
- Unsupported service remains explicit
- Timeout and cancellation remain distinguishable
- Partial downloads are not silently accepted
- Vendor-specific layouts are not treated as universal
Connected diagnostics
Keep file-service failures beside the communication evidence.
File transfer is not isolated from association state, service responses and per-IED diagnostics.
EvidenceAttributable service diagnostics
Separate association, service, relay-behavior and transfer problems instead of reducing every failure to a generic download error.
Protection and commissioning workflows
- Retrieve fault records after relay operation
- Collect disturbance evidence during FAT or SAT
- Compare record availability across multiple IEDs
- Preserve files for COMTRADE analysis tools
- Investigate missing or incomplete record sets
Downloaded files still require validation.
ARSAS does not prove that a record is complete, correctly scaled or suitable for protection analysis merely because transfer succeeded. Review the record set, time basis, channel definitions and relay configuration using approved engineering procedures.
Find the relay and its live model first.
Use the MMS client workspace to confirm endpoint identity and retain the correct IED context before browsing files.
Keep several relay sessions isolated.
Multi-IED project state helps prevent fault records and diagnostics from being mixed between devices.
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 →