Why You’re Getting Flat Lines and Missing Subscriber Data
The root cause is that IEC 61850 drivers (both GOOSE and SV) require a hardware target to function — they do not work on localhost.
This is explicitly documented in the internal KB:
“The drivers configured in the IO interfaces do not work on a localhost, only on a target.”
The IEC61850_SAS model relies on both GOOSE and SV communication between IEDs. When you run on localhost:
SV subscribers receive zero → the relay’s current input (from CT1_BT via SV) stays at 0, producing the flat green line you see on the BT_PU Overcurrent Relay Current panel
SV subscriber waveforms are absent → the publisher outputs from the power system model, but the subscriber driver is not active, so only publisher data appears on the SV Data tab
GOOSE subscribers receive nothing → all downstream protection logic (breaker failure, reverse blocking) doesn’t trigger
Do You Need the OP5650XG?
Yes, you need your OP5650XG (or another OPAL-RT hardware target) to reproduce the helpfile results for this model. The IEC 61850 drivers are real-time communication protocol drivers that run on the target’s network interfaces and cannot be emulated on a Windows host PC.
There is one partial exception: for SV-only testing, the
[Quick testing guide] IEC61850 Sampled Values mentions using the internal loopback interface (lo) on the target. But the IEC61850_SAS model uses both GOOSE and SV, so a full target is required.
Correct Workflow to Reproduce the Helpfile Results
Step 1 — Open the Model
Open IEC61850_SAS.ecf from the Protection examples category in HYPERSIM 2022.1.
Step 2 — Verify I/O Interface Configuration
Go to HYPERSIM tab → I/O Interface
Confirm the IEC 61850 interface has:
GOOSE publishers: BreakerFailureBT, ProtectionBT
GOOSE subscribers: subscriptions at IncA_PUBCU and IncB_PUBCU
SV publisher: IOP_K_BT_MU (from CT1_BT current transformer)
SV subscriber: to BT_PU relay inputs
Verify the Ethernet Adapter matches an actual network interface on your OP5650XG (typically eth1 — make sure it’s not connected to your corporate network to avoid flooding)
In General settings, confirm “Enable all SV and GOOSE services by default” is checked
Step 3 — Execute Load Flow
Open Network → Load Flow
Set frequency to 60 Hz
Click “Execute load flow”
Alternatively, enable “Perform load flow when simulation starts” in Simulation Settings
Step 4 — Set Scenario Parameters
Choose one of the two scenarios:
Scenario
Scen_Sel
Op_Mod
Behavior
Breaker Failure
1
2
CB_BT fails to open → CB_INCB opens
Reverse Blocking
2
1
CB_BT opens → CB_INCA stays closed (blocked)
Step 5 — Run on Target (OP5650XG)
Connect to your OP5650XG as the simulation target in HYPERSIM
Do NOT use localhost — select the target in the simulator settings
Start the simulation
Step 6 — Open ScopeView
Open the template IEC61850_SAS.svt
Click Sync and Trig buttons to synchronize with the fault trigger at 0.2 seconds
Press Play for signal acquisition
Step 7 — Verify Results
BT_Relay_Fault tab: You should see current waveforms from the SV subscriber, relay Q output going to 1 at 0.25 s, fault status, and CB_BT command
SV Data tab: Both publisher and subscriber waveforms should appear for all phases
GOOSE tabs: stNum, sqNum should match between publisher and subscriber, State = 1
Quick Troubleshooting Checklist
Simulation running on target (not localhost)
Load flow executed before or at simulation start
Ethernet adapter in I/O Interface matches a valid interface on the target
IEC 61850 services enabled by default in General settings
Check .simout log for driver start confirmation — look for messages like IEC 61850: X core(s) reserved for the driver thread
ScopeView Sync and Trig enabled for fault capture
