GOOSE
Sanitized capture showing publisher identity, GoID/AppID, stNum/sqNum, TAL, payload order and expected DataSet mapping; include negative or missing-frame findings.
Status · conditions · evidence date · public record
Compatibility is a service-level evidence claim—not a vendor logo.
ARSAS publishes only bounded evidence that can be tied to a protocol behavior, the application version when documented (or an explicit unknown), its conditions and a public engineering record. There are currently no publicly named vendor/model entries.
Status vocabulary
Read the status together with its conditions.
VerifiedConditionalObservedNot testedFailed with known issue
“Verified” describes the declared historical service scope; the ARSAS version used for these field captures is not publicly recorded. It is not IEC 61850 conformance certification and does not approve every firmware, Logical Device or project configuration.
Interoperability evidence matrix
See exactly which IEC 61850 services have public evidence—and which do not.
This is not a vendor scorecard. Each cell reports only the bounded public evidence in device-evidence.json. “Not tested” means no public test evidence is claimed; “Not declared” means that profile does not publish a status for that service.
Historical evidence · July 2026. Current published stable: v1.6.42. The ARSAS version used for these field captures is not publicly recorded, and a retest on v1.6.42 is not documented. The matrix does not claim current-stable interoperability.
| Service | Profile A · File service | Profile B · RCB / SCL |
|---|---|---|
| MMS association | Observed | Observed |
| Live model discovery | Not tested | Observed |
| Reporting | Not tested | Conditional |
| FileDirectory | Verified | Not tested |
| File transfer | Conditional | Not tested |
| GOOSE | Not tested | Not tested |
| Control | Not tested | Not tested |
| Selected RCB export | Not declared | Verified |
How to read this: one successful service does not imply another service works, and no row certifies IEC 61850 conformance. Open the profile below to see the exact conditions and public engineering records behind each status.
Evidence → exact release
Release identity and field-test evidence are different records.
The release is verifiable as a package; interoperability requires a separate service-specific field result.
Current stable package: v1.6.42 · tag v1.6.42 · source commit 3db2ca98d144ab4b456e8dc1db9af18ad7a948f2. Inspect the exact release or verify SHA-256 and package provenance. Package/CI evidence does not prove a device test.
Profile A · July 2026: file-service history, tested ARSAS version not publicly recorded; conditions and engineering trail. Not associated with the current stable by inference.
Profile B · July 2026: RCB/SCL history, tested ARSAS version not publicly recorded; conditions and engineering trail. Not associated with the current stable by inference.
v1.6.42 operator application FAT (25 October 2026): 5/5 monitoring endpoints, 183/183 initial values and 14/14 static RCB ingress paths observed; selected ctlModel Write/readback and SBO Enhanced checks were successful on the tested targets. The later operator report capture recorded 432 frames, 38 continuity findings and 9 IED-reported BufOvfl notices. This is scoped operator application evidence, not an accepted independent release-specific physical interoperability record, not evidence of 38 lost events, and not proof of lossless SOE. See release notes.
Accepted, publicly linked release-specific field-test records: 0. No retest on v1.6.42 is publicly documented in the registry. This describes publication coverage, not a device or software failure. Future reviewed records must identify the exact version, tag, source commit, service, actual date, outcome, conditions, sanitized public evidence and review PR. Inspect the release-test ledger and review requirements.
Evidence gaps · next capture
What is missing from these two published profiles?
GOOSE and Control are marked Not tested in both profiles. This is a gap in public field evidence, not a claim that ARSAS lacks either capability. A service omitted from one profile remains Not declared, not Not tested.
Control
Approved non-energized test showing ctlModel, Direct/SBO sequence, service and CommandTermination results, rejection/AddCause and independently checked process feedback.
Recheck on v1.6.42
For any service, provide the exact stable tag and ARSAS version; test date and anonymized IED model/firmware or disclosure boundary; positive and negative service result with sanitized diagnostics and acquisition conditions. Historical engineering records do not substitute for a new field test.
Contribute a bounded result: state the actual test date, release version, evidence type and service conditions. Preserve negative results; remove sensitive identifiers. Submit service evidence → The matrix above remains the source for profile-specific Not tested and Not declared statuses.
Anonymized field profile A — MMS file-service transport
Vendor, model, installation and firmware are not published. The public evidence concerns protocol behavior, not product endorsement.
Field evidence: 2026-07. ARSAS version at capture: Not publicly recorded. Retest on v1.6.42: Not documented. Updating this page or registry is not a field retest.
| Service | Status |
|---|---|
| MMS association | Observed |
| FileDirectory | Verified |
| File transfer | Conditional |
| Live model, reporting, GOOSE, control | Not tested |
Service → public engineering trail: MMS association / FileDirectory · PR #36; File transfer · signed FRSM, rooted paths, COTP reassembly. These are engineering records, not published raw field captures or new stable-release tests.
Conditions
- Nested FileDirectory entries and rooted file paths were observed.
- FileOpen could return a signed Integer32 FRSM, including negative values.
- Large FileRead responses required segmented COTP reassembly.
- Transfer success does not prove record completeness or COMTRADE scaling.
Anonymized field profile B — RCB and SCL export evidence
Vendor, model, installation and firmware are not published. Evidence remains read-only until an approved export action is requested.
Field evidence: 2026-07. ARSAS version at capture: Not publicly recorded. Retest on v1.6.42: Not documented. Updating this page or registry is not a field retest.
| Service | Status |
|---|---|
| MMS association and live model | Observed |
| Reporting evidence | Conditional |
| Selected-RCB export | Verified |
| Files, GOOSE, control | Not tested |
Service → public engineering trail: MMS association / live model / read-only RCB options · PR #36; selected-RCB export · PR #79. RCB option evidence does not establish live report delivery; these links are not raw field captures or new stable-release tests.
Conditions
- Live RCB names, TriggerOptions, OptionalFields, BufTm and IntgPd were preserved.
- Selected-RCB export retained the exact live MMS RCB identity.
- Exported SCL remains an engineering baseline requiring independent validation.
- No runtime RCB reservation or write is implied by this profile.
Evidence profiles are governed in JSON.
The public device-evidence.json registry contains the same profile IDs, service statuses, historical dates, explicit version/retest unknowns, service-level engineering records and conditions shown here. CI rejects unsupported status values, missing links or a named-device claim without explicit evidence metadata.
Report the service behavior—not only the brand.
Provide the ARSAS version, operating system, service under test, sanitized diagnostics, firmware when disclosure is allowed and a reproducible result. Confidential identifiers and credentials must be removed.
Submit → maintainer review → registry PR: a GitHub issue is a report, not verified field evidence. A reviewer checks privacy, exact version/date, expected versus observed results and service conditions; only a separate reviewed registry PR can change this matrix. Planned tests and engineering history alone do not establish a new physical retest.
Verified stable · ARSAS 1.6.42
Ready for an approved Windows workstation?
Installer and portable packages share the same application scope. Verify the published SHA-256 and review the release boundary before field use.
Release notes, limitations and signing status →