Browse first, then download a bounded record set.
Confirm that the MMS association supports file services, enumerate the permitted directory, identify related CFG, DAT, HDR or INF files, and retain the original names and originating IED context.
MMS file service · directories · record sets
COMTRADE retrieval starts by proving the relay's file-service path.
The relay may expose disturbance records through vendor-specific directories and naming patterns. Successful transfer of one file does not prove the complete record set is present.
- file service is unsupported or rejected
- root directory opens but expected records are absent
- download starts then times out or closes
- CFG is present but DAT is missing
- files are transferred but belong to a different event
Diagnostic path
Treat directory and transfer results as separate evidence.
File-service availability, directory content, file size, transfer completion and record-set consistency are different checks. Preserve each result rather than reducing everything to “download failed.”
Confirm the selected IED session
Use the correct endpoint and association so files cannot be attributed to the wrong relay.
Probe file-service support
Record unsupported, access-denied and directory-not-found outcomes separately.
Browse within a bounded path
Retain exact names, timestamps and available size information before selecting files.
Validate the record set
Group matching base names and verify that the expected configuration and data components were downloaded completely.
Timeout is not the same as unsupported service.
A timeout can indicate network interruption, server behavior, large transfer duration or session closure. Keep the last confirmed offset or progress evidence when available.
Downloaded is not the same as usable.
Open the files with an approved COMTRADE viewer and verify channel definitions, sample rates, timestamps and event identity before using the record as project evidence.
Related pages
Use the dedicated file-transfer workflow.
Review current ARSAS file-service scope and the commissioning use case.
Use the evidence to narrow the cause—not to claim conformance.
ARSAS can expose live model, report, GOOSE, file, control and diagnostic evidence. Final conclusions still depend on the approved project design, vendor documentation, test procedure, network access and independent verification.
Written and reviewed by Ari Sulistiono.
Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.
Verified stable release
Download ARSAS 1.6.18 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 →