IEC 61850-8-1 / 9-28 min read

Worked Example: Checking a Commissioning Capture Against the Network Plan

A 10-second capture of the sample substation compared with the planned streams: a missing merging unit, a confRev mismatch, an unknown test publisher with a clashing APPID, lost GOOSE and unsynchronised samples.

Scenario

CaptureSample capture generated from the project: 40 099 frames in 10 s (SV 39 997, GOOSE 61, MMS 31, PTP 10)
Plan4 GOOSE and 2 SV streams from the VLAN & multicast table

Open SCL NetStudio ▸ Capture analyser ▸ Load sample capture.

Step-by-step calculation

Step 1: Plan check

Planned streamSeenResult
GOOSE P132_Q01/GCB_TRIP · 0001YesMatches
GOOSE P132_Q02/GCB_TRIP · 0002YesMatches
GOOSE P87T_T1/GCB_DIFF · 0003YesconfRev 2 (plan 1)
GOOSE BCU_J01/GCB_IL · 0004YesMatches
SV MU_Q01/MSVCB01 · 4001YesVLAN 0 (plan 11)
SV MU_T1/MSVCB01 · 4002NoMissing
— (not in the project)TEST_IEDLD0/LLN0$GO$gcb01 · 0001Unexpected

Step 2: GOOSE findings

P132_Q01: stNum jumped 6 → 8 — one state change was never seen. P132_Q02: no message for 3 000 ms against a TAL of 2 000 ms — subscribers would declare the stream lost — and sqNum jumped 6 → 9. TEST_IED publishes APPID 0001, the same as P132_Q01's trip, untagged and with the test flag set.

Step 3: Sampled-value findings

MU_Q01: 3 samples missing before smpCnt 2003, and smpSynch = 0 in 1 599 samples (not time synchronised). It is only priority-tagged (VLAN 0), so it is not in the planned SV VLAN 11.

Step 4: MMS

One TCP retransmission between the gateway (10.13.0.11) and P132_Q01 (port 102): packet loss or congestion on the station bus.

Result summary

CheckRequirementActualStatus
All planned streams present6 of 65 of 6 (MU_T1 missing)✗ FAIL
No unknown publishersNoneTEST_IED with APPID 0001✗ FAIL
GOOSE continuityNo lost state changes, TAL respectedstNum gap; TAL exceeded✗ FAIL
SV synchronisationsmpSynch = 20 in 1 599 samples✗ FAIL
Before energisation: find and remove the test set publishing APPID 0001, put MU_Q01 in VLAN 11, restore its time synchronisation, bring MU_T1 on line, re-load P87T_T1's CID (confRev 2 against the planned 1, or update the plan if the change is intended), and investigate the lost GOOSE messages from P132_Q01 and P132_Q02.

Key insight: A capture compared with the plan finds the problems that each device's own configuration tool cannot: missing and unknown publishers, address clashes between vendors, and devices that are configured correctly but not on the right VLAN or clock.

Try it with your own numbers

Every input in this example is editable in the live calculator — no signup needed.

Open SCL NetStudio (IEC 61850 network design) calculator →

Frequently asked questions

Where should the capture be taken?

On a mirror port or TAP that receives the multicast traffic of interest — for sampled values, on the process bus switch; for GOOSE, on the station bus. Capture for long enough to include a few state changes.

How is this different from the GOOSE & SV Capture Analyzer?

SCL NetStudio checks the capture against the network plan. The GOOSE & SV Capture Analyzer runs 86 detailed conformance checks per frame with clause references; the two complement each other.

More in IEC 61850 & Substation Automation

← Back to all worked examples