State number
A new published state is normally associated with a state-number change. Confirm that the ordered payload or relevant status also changed as expected.
stNum · sqNum · TAL · retransmission
GOOSE sequence values explain whether the publisher changed state or retransmitted the same state.
Interpret sequence evidence together with goCBRef, DataSet, APPID, VLAN, source MAC, TAL and payload. One counter alone is not enough to identify the stream.
Sequence number
Retransmissions of the current state normally advance sequence evidence. Gaps, resets or unexpected patterns require context from capture continuity and publisher restart behavior.
Diagnostic path
Supervise the whole stream identity.
First prove that consecutive frames belong to the same publisher and control block. Then examine state, sequence, retransmission interval and TAL behavior.
Bind the stream identity
Use source and destination MAC, APPID, VLAN, goCBRef and DataSet reference.
Track state transitions
Compare stNum with the ordered allData payload and the expected process event.
Track retransmission
Inspect sqNum progression and frame timing while the state remains unchanged.
Supervise TAL and capture gaps
Separate a publisher that exceeded its advertised lifetime from a local capture interruption or interface problem.
Observe sequence and payload together
ARSAS keeps stream identity, flags, TAL, counters and ordered payload visible in one GOOSE session.
A counter reset is not automatically a device fault.
Publisher restart, configuration activation or capture discontinuity can change the observed pattern. Correlate the timing with device and project events.
A healthy sequence does not prove correct semantics.
The stream can be timely and internally consistent while the DataSet order, scaling or subscriber mapping is wrong.
Related pages
Continue with GOOSE workflow evidence.
Review the analyzer capability and multi-vendor integration path.
Use the evidence to narrow the cause—not to claim conformance.
ARSAS can expose live model, report, GOOSE, file, control and diagnostic evidence. Final conclusions still depend on the approved project design, vendor documentation, test procedure, network access and independent verification.
Written and reviewed by Ari Sulistiono.
Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.
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 →