Select the approved adapter
Choose the interface connected to the intended station or process-bus segment. Raw Ethernet capture requires Npcap.
Read-only GOOSE inspection · stream supervision · model binding
Turn IEC 61850 GOOSE traffic into attributable engineering evidence.
ARSAS captures GOOSE through an approved network interface and presents stream identity, sequence behavior, retransmission, Time Allowed to Live, flags, payload order and available model context without transmitting GOOSE frames.
Stream identityAPPID, VLAN, destination MAC, goCBRef and DataSet reference
SequencestNum, sqNum, retransmission rhythm and state-change evidence
SupervisionTAL, Test, ndsCom and visible stream health
PayloadOrdered allData values with SCL or live-model binding context
Diagnostic workflow
Find whether the problem is traffic, sequence, configuration or interpretation.
A packet list alone is not enough. ARSAS keeps stream-level evidence together so engineers can distinguish absent traffic from stale sequence, incorrect network identity, payload mismatch or incomplete engineering context.
Identify each publisher stream
Group frames using APPID, destination MAC, VLAN, goCBRef and DataSet evidence instead of treating all GOOSE traffic as one list.
Inspect state and sequence
Observe stNum changes, sqNum progression, retransmission behavior and TAL before deciding whether the publisher is healthy.
Bind payload to engineering meaning
Compare ordered allData leaves with available SCL or live-model context and keep uncertainty visible when mapping is incomplete.
Real application screenshot
Inspect stream details without losing the wider IED context.
The GOOSE workspace is part of the same project environment used for MMS, SCL, reporting and diagnostics.
GOOSEStream supervision and payload inspection
Review publisher identity, APPID, VLAN, sequence, retransmission, TAL, flags, ordered payload and available model binding evidence.
What ARSAS helps an engineer verify
- Is the expected publisher visible on the selected interface?
- Does stNum change when the source state changes?
- Does sqNum progress with plausible retransmission behavior?
- Is TAL being refreshed before expiry?
- Do APPID, VLAN, MAC, goCBRef and DataSet match the intended design?
- Can ordered payload leaves be mapped to available engineering context?
Capture evidence is not a protection-system acceptance result.
ARSAS does not transmit GOOSE, prove end-to-end trip performance or certify network design. Protection logic, timing, redundancy, subscriber behavior and final scheme acceptance still require approved procedures and independent test evidence.
Use SCL to explain the intended stream.
Compare observed publisher identity and payload order with the available configured model.
Keep communication diagnostics attributable.
Use independent IED sessions and diagnostics to avoid mixing MMS, GOOSE and device-specific problems.
Verified stable release
Download ARSAS 1.6.17 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 →