Preserve the original file and capture the exact import error.
Do not begin by deleting arbitrary XML sections. Identify the parser location or rejected reference, then compare the intended communication and reporting path with live IED evidence.
Schema · references · edition · live mismatch
A rejected CID file does not automatically mean the relay is not interoperable.
First determine whether the failure is XML syntax, SCL structure, edition handling, vendor-private content, broken references or a mismatch between the file and the running IED.
- schema or namespace error during import
- unknown or unsupported edition element
- unresolved DataSet, RCB or communication reference
- vendor-private section rejected by another tool
- file imports but reporting remains silent
Diagnostic path
Separate file validity from integration usefulness.
A file can be valid XML but unsuitable for a target configurator. It can also import successfully while representing an outdated relay model or reporting assignment.
Record the parser evidence
Keep the original filename, edition, namespace, error message and reported location.
Validate critical references
Trace IED, AccessPoint, server, Logical Device, DataSet, RCB and communication references without blind deletion.
Compare with the live IED
Confirm endpoint, model, DataSet and RCB evidence currently exposed by the relay.
Create a controlled baseline
When appropriate, export only the selected reporting context and verified members required for the approved integration workflow.
Build a bounded integration baseline
Select the intended RCB, retain verified DataSet members and choose the required SCL edition instead of removing unrelated XML through trial and error.
Related guides
Check whether the file still matches the running relay.
Continue with live-model comparison or the multi-vendor integration workflow.
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.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 →