Process Bus Insight is a receive-only IEC 61850 Process Bus analyzer for Windows. This guide explains the recommended Inno Setup installation (or optional portable ZIP) and a safe observation workflow.
Recommended setup:
- Windows 10 or Windows 11 x64.
- A physical Ethernet adapter connected to a TAP, mirror port, or isolated test network.
- Npcap installed with normal raw packet capture support.
- Local admin rights if your Windows/Npcap policy requires elevated capture access.
Avoid these adapters for serious timing interpretation:
- Loopback adapters.
- Wi-Fi / Wi-Fi Direct.
- Hyper-V, VMware, VPN, or virtual bridge adapters.
- Unverified USB Ethernet adapters when timing evidence matters.
- Download latest stable Windows installer (.exe) directly, or use the landing page which discovers newer stable releases automatically.
- Verify the installer against the official SHA256SUMS.txt.
- Close any prior running instance and run the Inno Setup installer. It installs into
C:\Program Files\Process Bus Insightby default, creating a Start Menu shortcut and optional desktop shortcut. - For an upgrade, run the newer installer without uninstalling first; the stable application identity retains the previous install directory. Re-running the same installer can repair files.
- The optional portable ZIP can still be extracted manually to
C:\Tools\ProcessBusInsightwhen appropriate.
Launch Process Bus Insight from the Start Menu, or run ProcessBusInsight.exe from the installed folder. Quick Start.pdf, User Manual.pdf, and Install and Update.md are available offline in the same folder; shortcuts to both PDFs are in the Start Menu.
The application is self-contained. Npcap is installed separately for live capture, never silently by this installer. If Npcap cannot load, the application shows Npcap unavailable — capture disabled and will not fabricate a capture-capable Ethernet adapter.
- Select the physical Ethernet adapter connected to the Process Bus traffic.
- Start capture.
- Confirm traffic appears in the event log.
- Review SV stream discovery.
- Review GOOSE publishers and event changes.
- Review PTP timing context if present.
- Load SCL when available and compare expected-vs-observed objects.
- Copy evidence only after confirming adapter and capture-path confidence.
For a useful FAT/SAT troubleshooting screenshot or copied finding, include:
- Selected adapter raw device name.
- SV stream APPID, svID, VLAN, source MAC, and stream status.
- GOOSE publisher/control block and stNum/sqNum state when relevant.
- PTP transport/domain/grandmaster context when relevant.
- Missing sample / sequence / arrival timing status.
- Timing confidence label and timestamp source wording.
- Expected SCL fields and observed fields when SCL is loaded.
Arrival timing shown by the app is based on host/Npcap software timestamps. Treat it as screening evidence. Do not use it as certification-grade jitter proof unless the capture path is validated with hardware timestamping, TAP, or trusted timing equipment.