ARSAS IEC 61850 workstation
Home / Compatibility evidence
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, application version, condition and public engineering record. There are currently no publicly named vendor/model entries.

Start with Quick StartSubmit compatibility evidenceBahasa Indonesia
Status vocabulary

Read the status together with its conditions.

VerifiedConditionalObservedNot testedFailed with known issue

“Verified” means repeated evidence exists for the declared service scope. It is not IEC 61850 conformance certification and does not approve every firmware, Logical Device or project configuration.

Evidence date · 2026-07

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.

ServiceStatus
MMS associationObserved
FileDirectoryVerified
File transferConditional
Live model, reporting, GOOSE, controlNot tested

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.
Directory evidenceSigned FRSMSegmented COTP
Evidence date · 2026-07

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.

ServiceStatus
MMS association and live modelObserved
Reporting evidenceConditional
Selected-RCB exportVerified
Files, GOOSE, controlNot tested

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.
RCB option evidenceApplication integrationExact export release
Machine-readable source

Evidence profiles are governed in JSON.

The public device-evidence.json registry contains the same profile IDs, service statuses, conditions and public links shown here. CI rejects unsupported status values, missing links or a named-device claim without explicit evidence metadata.

Open evidence JSON
Contribute a new profile

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.

Open compatibility formClaim governance
Verified stable release

Download ARSAS 1.6.18 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 →
Download Windows installerVerify and compare packages