ARSAS

IEC 61850 communication validation & client testing for Windows

Discover · Monitor · Annunciate · Control · Test · Analyze COMTRADE · Export Evidence

ARSAS is a free, open-source IEC 61850 client tester for engineers working with relays and IEDs. Connect by IP, open an ICD/CID/IID/SCD file, inspect live MMS values and Reports, and collect evidence for FAT, SAT, commissioning and troubleshooting. Start with the three-step visual guide; deeper workflows are available when you need them.

Download installer · Portable single EXE · Quick Start · IO List FAT Evidence · Product website · Release notes · Roadmap

_{One persistent multi-IED shell for discovery, live values, reporting, events, alarms, guarded control, FAT, files and diagnostics.}

Latest public stable: ARSAS v1.6.42 — Windows x64, operator-tested application, published 25 October 2026. The two downloadable binaries are the exact validated public release packages. Installer · Portable single EXE · Checksums.

Engineering boundary: stable is the public application channel, not IEC 61850 conformance certification, universal vendor compatibility, physical R7/R10 qualification or lossless buffered SOE. The latest operator snapshot recorded 432 report frames with 38 continuity findings and 9 IED-advertised BufOvfl notices (not 38 proven lost events). Some test endpoints may be simulators. See the release notes and tracked qualification.

Exact source identity: v1.6.42 assets were built from 3db2ca98 with ARIEC61850 trial engine f75e323e, as recorded in bundled provenance. The main branch contains the historical 1.6.41 application baseline while the accepted v1.6.42 integration remains separately staged pending physical-qualification guards; use the release tag, not main, to inspect the exact shipped source. v1.6.40 historical field proof belongs to that older exact app/engine pair.

Start in five steps

1. Download the Windows installer for a regular workstation, or the portable EXE if you prefer a single file. Windows 10/11 x64.
2. Verify the file with Get-FileHash .\\ARSAS-Windows-x64-Setup.exe -Algorithm SHA256 and compare against the published SHA-256. Unsigned binaries can show Windows SmartScreen warnings.
3. Connect to an authorized test-network IED using Add IED → IP address → Smart Discovery, or open its ICD/CID/IID/SCD file without connecting. MMS typically uses TCP port 102.
4. Inspect and monitor the discovered IED: Reports → DataSets → Data Model → Files → Setting Groups → GOOSE. Start from the IED's configured static DataSet, then inspect live values, quality and timestamps. Avoid interpreting missing data as a successful report.
5. Test safely: perform typed Write/readback or SBO control only under an approved switching/test procedure; review SOE, GOOSE, Sampled Values, FAT evidence and COMTRADE as needed. Raw-Ethernet capture requires approved Npcap and sufficient permissions.

Full beginner Quick Start · Panduan Bahasa Indonesia · Release integrity and limitations

What's new in v1.6.42

• Complete IED Browser — Reports, DataSets, Data Model, Files, Setting Groups and GOOSE, model-backed inspection and preserved per-IED selection state.
• Control and Write you can verify — typed ctlModel Write/readback, targeted post-Write CSWI reinspection, fail-closed control admission and tested SBO Enhanced command sequences on SG7_BCU and GR_X_7SX85.
• Multi-IED monitoring — 5/5 monitoring endpoints, 183/183 initial selected values and 14/14 static RCB ingress routes observed in the operator diagnostic; report-first signal state and bounded UI updates.
• GOOSE, SNTP and SV/SMV — improved GOOSE timeline and SNTP IPv4 display, waveform viewing and first-received SV discovery without SCL/SVCB configuration.
• Modern Windows experience and COMTRADE — compact Smart IP form, cool-blue UI, responsive workspace and pinned ArdIrec analysis bridge.
• Tested distribution — 2,987/2,987 application tests passed on the release workflow; installer/portable smoke verification, SHA-256, SBOM, provenance and attestations are attached to the exact release.

Earlier milestones are retained in the historical release details and CHANGELOG, rather than mixing older product behavior into the current Quick Start.

Real ARSAS v1.6.42 product screens

Eight unedited operator PNG captures from the public v1.6.42 Windows application (25 October 2026), with full-resolution PNG links and optimized WebP previews. These screenshots show the software interface; they are not independent IEC 61850 conformance certificates or proof of lossless SOE.

Engineering view	Monitoring and analysis

The guided product demo presents each current screen with a concise engineering explanation. The guided setup dialog examples are from v1.6.40 because no newer dialog captures were supplied.

Historical screenshots (v1.6.40)

SCL model and export	COMTRADE engineering analysis

These two historical examples remain correctly version-labeled and must not be mistaken for current-release screenshots.

Why ARSAS stands out

Engineering problem	ARSAS response
Vendor CID or ICD is missing, outdated, or rejected.	Perform complete live MMS discovery and generate a schema-aware Edition 2 IID or Edition 1 ICD with companion evidence.
Reporting setup consumes the test window before values appear.	Read an immediate MMS image, prefer verified BRCB/URCB coverage, recover bounded gaps where permitted, and keep fallback acquisition visible.
A multi-IED test loses device ownership and diagnostics.	Maintain an independent association, model, monitoring state, events, files, control context, and diagnostics for every IED.
A FAT team must rebuild IO List evidence manually.	Import the approved workbook, bind exact IEC 61850 references, record ordered OFF → ON → OFF evidence, and export Excel, native PDF, or a resumable .arsas project.
GOOSE or SMV analysis requires repeated navigation and adapter selection.	Enter directly from the selected IED card, resolve the routed NIC when it is unique, and start passive capture with a safe manual fallback.
Runtime RCB slots and saved SCL identity do not line up cleanly.	Show the concrete live instances exposed by the IED while preserving the canonical logical ReportControl identity for source-backed SCL export.
Disturbance analysis feels disconnected from the IEC 61850 workflow.	Open downloaded COMTRADE records inside ARSAS and use the pinned native ArdIrec bridge for cursor, Phasor, Harmonics, and distance Locus analysis.
Integration failures become vague messages.	Preserve identity, references, DataSet membership, RCB options, protocol stage, negative response, timing, and copyable diagnostic evidence.

ARSAS shortens the path from “the IED is reachable” to “the engineer has usable, attributable evidence.” It does not turn an unsupported or ambiguous result into a false success.

One persistent engineering shell

IED Explorer and operator workspaces

Use an approved IED IP address or SCL source for Smart Discovery, signal selection, reporting and multi-IED monitoring. The Explorer keeps the selected IED context while the operator moves between live values, Sequence of Events, Alarm Annunciator, GOOSE, diagnostics, FAT and the Command Dock. Device-specific associations, models and evidence are not flattened into one ambiguous global session.

IO List FAT Workspace

Import an approved Excel workbook or open a portable .arsas project. The workspace keeps only the imported scope, binds the points to live-discovered IEC 61850 references, records ordered transition evidence, and produces customer-facing evidence output.

Once loaded, the FAT workspace remains in memory while the user visits Engineering. Returning to IO List FAT does not reopen Excel or .arsas; loading another file is an explicit replacement action.

The automatic IO List test path is read-only toward the IED. It does not issue controls. External simulation, injection, or plant operation still requires an approved procedure and safe test boundary.

IO List FAT evidence workflow

Approved IO List workbook / portable .arsas project
                        ↓
Strict schema, identity and document-control validation
                        ↓
Exact IEC 61850 and event-log reference binding
                        ↓
Trustworthy OFF baseline
                        ↓
OFF → ON evidence → ON → OFF evidence
                        ↓
PASS / REVIEW / FAIL / PENDING
                        ↓
Excel result · Native executive PDF · Portable .arsas project

A point passes only when a new ON transition and its corresponding OFF transition are captured in order. An initial ON image is not accepted as ON evidence. Quality, acquisition source, IED timestamp, ARSAS timestamp, observation sequence, and connection generation remain attached to the evidence.

Rev.3 workbook behavior

• Exact Event Log Search Reference remains the primary log-correlation field.
• Report Display Reference is used for customer-facing traceability and never replaces the live/event-log identity.
• Source state text is preserved without automatic inversion.
• Missing IED, IP, FC, data attribute, or IEC reference remains blocked instead of being guessed.
• Duplicate keys and command points remain visible as review scope.
• Automatic binary-transition FAT currently focuses on approved SDI points; analog and active-command workflows are not silently treated as equivalent tests.

Evidence outputs

• Excel result — copies the approved workbook and updates matching test rows; the source workbook is never modified in place.
• Native PDF — creates an A4 landscape AS TESTED attachment with document control, exact IEC 61850 reference, expected state, relay timestamps, result, test basis, and sign-off blocks.
• Portable .arsas — packages the workbook, project snapshot, evidence journals, exports, hashes, and handover notes for continuation on another workstation.

See IO List FAT Evidence Testing for the workbook contract, state machine, persistence model, package layout, and engineering boundaries.

Fast process-bus workflow

GOOSE from an IED card

Select IED card → GOOSE → routed NIC → passive capture → stream evidence

ARSAS resolves the Windows route to the selected IED, maps it to Npcap, and starts receive-only GOOSE capture when one adapter is proven. If adapter selection is ambiguous, ARSAS opens the workspace and asks the user to choose manually rather than guessing.

SMV from an IED card

Select IED card → SMV → routed NIC → first discovered stream
                → bounded two-cycle snapshot → values and waveform

The workflow preserves the existing stream-identity and continuity guards. smpCnt gaps, duplicates, out-of-order transitions, publisher restart, missing stream identity, or incomplete capture remain visible as review conditions. Raw lanes are not claimed as calibrated current or voltage until trusted SCL mapping and scaling are available.

Capability status

IEC 61850 area	Status	Current scope
MMS client and model discovery	Available	Association, physical identity, complete LD/LN/DO/DA hierarchy, values, quality, timestamps, DataSets, RCBs, types, and diagnostics.
IO List FAT evidence	Available	Rev.3 import, exact event-log reference, one-IED sessions, OFF → ON → OFF evidence, reconnect handling, autosave, native executive PDF, Excel result, and portable .arsas.
Workspace continuity	Available	Loaded Engineering/FAT mode switching without repetitive file dialogs; explicit replacement for another workbook or project.
Live discovery to SCL	Available	Single-IED Edition 2 IID or Edition 1 ICD from the last complete typed discovery.
RCB inspection and source-backed export	Available	Concrete live runtime instances remain visible online; source-backed export preserves canonical logical ReportControl identity and RptEnabled indexing metadata without inventing runtime slot names.
Reporting and live monitoring	Available	BRCB/URCB inspection, immediate reads, exact coverage, bounded recovery, visible polling fallback, multi-IED monitoring, and SOE.
Alarm and event operation	Available	Per-IED Alarm Annunciator with active/unacknowledged/returned state, explicit acknowledgement, and Sequence of Events carrying IED time, quality and acquisition source.
GOOSE subscriber	Available	Read-only Npcap capture, one-click IED context, APPID/VLAN/MAC, sequence, TAL, ordered payload, timeline, and model binding.
Sampled Values / SMV	Engineering preview	One-click IED context and bounded two-cycle raw waveform evidence; calibrated scaling, complete semantic mapping, synchronization proof, and sustained-performance validation remain bounded work.
IEC 61850 file transfer	Available	MMS browsing/download, segmented responses, grouped records, reconnect boundaries, duplicate handling, and detailed diagnostics.
In-process COMTRADE	Available	Pinned native ArdIrec bridge with exact and RMS time signals, synchronized cursors, Phasor, Harmonics, six-loop distance Locus, digital protection timeline, bounded display easing, and no external viewer process.
Smart Control	Available / guarded	Command Dock with live ctlModel, Direct and SBO sequences, Test/interlock/synchrocheck context, CommandTermination, timing, and mapped feedback.
Full visual SCL authoring	Planned	Complete visual project editing, communication, DataSets, control blocks, diff, and reusable project output.

See ROADMAP.md for definitions of done and explicit non-goals.

Download stable Windows packages

Package	Intended use
Windows installer	Recommended for normal use, Start Menu integration, uninstall support, and verified update workflow.
Portable single EXE	Run the self-contained single EXE without installing ARSAS or .NET on an approved workstation.
SHA-256 checksums	Verify the exact installer and portable package.
Latest tagged ARSAS release	Authoritative public release scope, assets, checksums, SBOM, provenance, and publication state.

The public Windows binaries are currently not Authenticode-signed unless the tagged release evidence states otherwise, so Windows SmartScreen may show an unrecognized-publisher warning. Verify the published SHA-256 value before use.

System requirements

• Windows 10 or Windows 11, x64.
• An isolated laboratory network or approved FAT, SAT, or commissioning boundary.
• Ethernet access to the intended IED for MMS services, normally TCP port 102.
• Npcap for raw-Ethernet GOOSE or Sampled Values capture.
• Suitable authorization, procedures, switching authority, and independent verification before active control or configuration work.

Visual Studio and an ARIEC61850 source checkout are not required for packaged use.

Engineering walkthroughs

First read-only Engineering session

1. Install ARSAS or run the portable single EXE, then verify SHA-256.
2. Confirm the approved network path and TCP port 102.
3. Choose Add IED by IP address.
4. Complete live discovery.
5. Select a small known set of read-only points.
6. Verify IED ownership, value, quality, timestamp, and acquisition source.
7. Enter GOOSE, SMV, files, SCL, or control only after the read path is understood.

First IO List FAT session

1. Open IO List FAT and import the approved workbook or .arsas project.
2. Review blocked, duplicate, command, and unsupported rows.
3. Select one imported IED and start connection/preparation.
4. Obtain a trustworthy OFF baseline.
5. Operate the approved external test source OFF → ON → OFF.
6. Review live evidence and event-log correlation.
7. Stop/seal the session and export Excel, native PDF, or .arsas.
8. Move to Engineering and back to FAT without reopening the loaded project.

See the bilingual Quick Start, IO List FAT guide, Guided Demo, FAQ, and Troubleshooting Guides.

Architecture

┌────────────────────────────────────────────────────────────────────────────┐
│                                   ARSAS                                    │
│ Engineering Workspace ⇄ Loaded IO List FAT Workspace                     │
│ Explorer · Monitor · SOE · GOOSE · SMV · Files · SCL · Control          │
│ Project state · Excel/PDF evidence · .arsas packaging · diagnostics      │
└────────────────────────────────────┬───────────────────────────────────────┘
                                     │ typed application services
┌────────────────────────────────────▼───────────────────────────────────────┐
│                                ARIEC61850                                  │
│ MMS · Reporting · GOOSE · SMV · File Services · SCL · Control            │
│ Transport · Type System · Schema Profiles · Diagnostics · Validation      │
└───────────────────────────┬──────────────────────┬─────────────────────────┘
                            │ TCP/102              │ Ethernet process bus
                       Approved IEDs          Approved capture network

Protocol parsing, transport behavior, typed contracts, schema profiles, SCL conversion/export, and reusable validation belong in ARIEC61850. ARSAS owns the Windows workflow, project state, visualization, diagnostics, IO List test coordination, Excel/PDF evidence, and engineer-facing packaging. The in-process COMTRADE workspace uses the separately pinned ArdIrec native bridge for disturbance-record parsing and analysis.

Detailed notes: Architecture · IO List FAT Evidence · COMTRADE integration · SCL export · Engine compatibility

Build from source

Requirements: Windows 10/11, .NET 8 SDK, Visual Studio 2022 or the .NET CLI, a compatible ARIEC61850 source checkout, and Npcap for process-bus testing.

Recommended layout:

D:\Git\
├─ ARIEC61850\
└─ arsas\

git clone https://github.com/masarray/ARIEC61850.git
git clone https://github.com/masarray/arsas.git
cd arsas
dotnet restore .\ArIED61850Tester.csproj
dotnet build .\ArIED61850Tester.csproj -c Release

Safety, privacy, and evidence boundaries

IEC 61850 control, report configuration, temporary DataSet creation, file access, and other active operations can affect IED resources or equipment state. Use them only inside an approved boundary with suitable isolation, authority, procedures, and independent verification.

GOOSE and Sampled Values capture is receive-only in ARSAS, but station/process-bus traffic still requires an approved adapter, network boundary, and data-handling policy.

Do not publish credentials, private endpoints, customer identity, confidential IO Lists, SCL, relay settings, packet captures, disturbance records, or .arsas evidence projects. Sanitize evidence before opening a public issue.

ARSAS is not an IEC 61850 conformance certificate, functional-safety certification, cybersecurity approval, calibrated injection system, automatic switching authority, or substitute for an approved FAT/SAT/commissioning procedure.

Documentation and support

• Product website
• Quick Start
• IO List FAT Evidence
• Compatibility evidence
• Guides
• Documentation hub
• Support guide
• Security policy

Contributing and license

Focused, reproducible, independently authored contributions are welcome. Read CONTRIBUTING.md, the independent implementation and provenance policy, the clean-room and interoperability policy, CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md, and NOTICE.md.

The community edition is licensed under GNU GPL v3.0 or later. See LICENSE. A separate commercial license is available for proprietary integration, OEM/white-label distribution, warranty, maintenance, priority support, training, and project-specific development; see COMMERCIAL-LICENSE.md.

---

ARSAS
From an approved IED endpoint or IO List to trustworthy IEC 61850 evidence and reusable project output.