This onboarding path is intentionally read-first. Complete the first attributable value before continuing into reporting, files, GOOSE, control or IP-to-SCL generation. Teams starting from an approved test sheet can use the separate IO List FAT path.
Choose general IEC 61850 testing for discovery and engineering workflows, or FAT / IO List Testing when the project starts from an approved ARSAS workbook or portable .arsas project.
Choose Installer or Portable ZIP, compare the downloaded file with the published SHA-256, then review the honest Authenticode status. SmartScreen may identify the current public build as an unrecognized publisher because it is unsigned.
Connect the engineering laptop only to the approved laboratory, FAT, SAT or commissioning network. Confirm addressing, routing and TCP port 102 before changing application settings. Npcap is needed for raw-Ethernet GOOSE or Sampled Values capture, not for ordinary MMS client reads.
Enter the approved IPv4 address and keep the default IEC 61850 MMS port unless the project procedure explicitly defines another endpoint. A successful TCP connection is not yet proof of a complete MMS association or service support.
Allow ARSAS to read the physical server identity, Logical Devices, Logical Nodes, Data Objects, Data Attributes, DataSets, Report Control Blocks and available type information. Treat the online model as current server evidence and SCL as configured intent.
Choose a known read-only attribute and add it to Live Values. Confirm the IED source, object reference, value, quality, timestamp and acquisition source together. Do not treat a number alone as proof that the signal is valid or timely.
ARSAS can evaluate existing BRCBs and URCBs, exact DataSet coverage and visible fallback. An occupied RCB, rejected write or incomplete DataSet should remain visible rather than being converted into a false success.
Save or copy the attributable diagnostics needed for the test record. Do not reserve an RCB, create a DataSet, write configuration or operate a control object unless the approved procedure, plant authority and independent safety checks explicitly permit it.
The current mainline provides a dedicated SDI FAT workspace. The latest stable public installer may remain an earlier version, so review release scope before field use.
Open the ARSAS workbook for a new project or open an existing portable .arsas project.
Confirm project identity, IED, TestPointId, expected states and IEC 61850 object references before starting.
Obtain a good OFF baseline, create a new ON transition, then return to OFF. Quality, IED timestamp, ARSAS timestamp, acquisition source and event order remain attached.
Seal the session, then export the Excel result copy, native PDF report or complete .arsas continuation project.
When the discovery is complete and Diagnostics has no unresolved blocking error, the same IED context can produce a bounded engineering baseline.
Do not use a signal-only project cache as if it were a complete live discovery document.
Select Edition 2 to generate IID or Edition 1 to generate ICD.
Inspect the generated SCL, JSON evidence, Markdown summary and warnings before importing anything downstream.
Test identity, communication, DataSets, RCB names, references and schema handling inside the approved FAT or SAT procedure.
A completed quick start proves that the selected endpoint, association and read path produced the displayed evidence at that time. It does not prove every service, every Logical Device, protection performance, time synchronization or IEC 61850 conformity.
Start with port 102, model discovery, reporting, RCB ownership, file service, GOOSE sequence, IO FAT continuity or SCL evidence. Preserve negative results and the exact ARSAS version in an issue report.
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 →