OCPP DebugKit

OCPP DebugKit Studio

Studio is a native desktop debugger for OCPP charging sessions — the bench instrument of the OCPP DebugKit ecosystem. It sits between a charging station and its backend, decodes every frame live, flags protocol failures as they happen, and keeps a high-performance offline inspector for the traces you capture.

It is built in Zig on the Native SDK — native-rendered, no browser, no Electron. It starts instantly, stays small, and does the things a browser tab fundamentally cannot: open raw sockets, watch the filesystem, and run for days as a background monitor.

What it does

  • Inspect — open JSON / JSONL / bare-array traces in a virtualized timeline that stays smooth past 500k events; unpack any message, see the session it correlates into, and search or filter by action, direction, type, or severity.
  • Detect— the full OCPP 1.6J failure taxonomy (16 rules), conformant with the toolkit's reference, ranked critical to info with remediation steps.
  • Watch — a live WebSocket proxy between a charge point and its CSMS: decode frames in flight, run detection as events stream, record to the canonical trace format, and get an OS notification the moment a critical failure appears.
  • Prove — Markdown / HTML reports, semantic trace diffing, anonymize-on-export, and step-through replay.
  • Scale — native performance with no garbage collector; stream-parse traces far past what a browser tab can hold.
  • Script — the same binary is a headless CLI (inspect, report, diff, anonymize, capture, ci) for pipelines and automation.

Native, not a browser tab

Studio and the toolkit's web inspector share no code. They meet only at a conformance contract — the same trace format, the same normalized event model, and the same failure taxonomy — verified in CI on every change. A trace captured in Studio opens in the web inspector, and vice versa. See the conformance contract.

Get Studio