Open project context
Load the available SCL and identify the intended IED, access point, DataSets, RCBs, GOOSE control blocks and addresses.
Use ARSAS to compare project SCL intent with the services and model exposed by each IED, inspect reporting and GOOSE behavior, and prepare a controlled selected-RCB baseline for SAS or gateway integration.
Interoperability problems often involve differences between configured intent, live server behavior and the expectations of the receiving SAS or gateway.
Load the available SCL and identify the intended IED, access point, DataSets, RCBs, GOOSE control blocks and addresses.
Connect to the approved endpoint and inspect the model, services, DataSets, report controls and command descriptors actually exposed.
Check RCB availability, ownership, DataSet membership, report behavior and any rejected or unsupported operations.
Verify APPID, VLAN, destination MAC, goCBRef, DataSet reference, sequence counters and ordered payload leaves.
Select the intended RCB, retain verified DataSet members and export an Edition 1 or Edition 2 SCL baseline for further engineering review.
A successful connection or export does not prove full IEC 61850 conformance, interoperability with every vendor, project correctness or acceptance by the receiving system. Final engineering review remains required.
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 →