OCPP DebugKit

Open-source DevTools for debugging OCPP charging sessions. Parse, analyze, and diagnose traces from a browser tab, your CI pipeline, or a native desktop instrument.

Two tools, one trace format

The OCPP DebugKit family is two independent products that share the same trace format, event model, and failure taxonomy. Use one, or both.

TypeScript · npm · CLI · browser

Toolkit

The library and CI brain.

Parse, analyze, and report OCPP traces anywhere JavaScript runs — in the browser inspector, a Node CLI, or your test suite.

  • 16 detection rules across the OCPP 1.6J failure taxonomy
  • 15 built-in scenarios with expected-failure assertions
  • Trace diffing, anonymize-on-export, CI mode, step-through replay
  • Zero-install web inspector — traces never leave your browser

Zig · Native SDK · desktop

Studio

The instrument on the bench.

A native desktop debugger that sits between a charge point and its backend, decodes every frame live, and flags protocol failures the moment they happen.

  • Live WebSocket capture between a charge point and its CSMS
  • Virtualized timeline that stays smooth past 500k events
  • OS notifications the instant a critical failure appears
  • The same binary is a headless CLI for pipelines
ToolkitStudio
LanguageTypeScriptZig
Runs inBrowser, Node, CINative desktop (macOS, Linux)
Surfacenpm library, CLI, web inspectorGUI app + headless CLI
Best forAnalysis anywhere, automation, sharingLive capture, native performance, OS integration
Installnpm install -g @ocpp-debugkit/toolkitOne-line macOS installer

Capture in one, open in the other

A trace captured in Studio opens in the toolkit's web inspector, and vice versa. The two are independent implementations checked against the same conformance contract in CI — same format, same normalized events, same failure taxonomy.

What it does

Inspect

Normalize OCPP 1.6J traces into events, sessions, and a timeline you can search and filter.

Detect

16 detection rules flag failures — failed auth, connector faults, offline stations, meter gaps, and more.

Diff

Semantic diffing of two traces to see exactly what changed between runs.

Report

Export a session analysis as a Markdown or HTML report.

Replay

Step forward and back through a session deterministically, at any speed.

Anonymize

Strip station IDs, transaction IDs, and idTags before sharing a trace.

Test

15 built-in scenarios with expected-failure assertions for the analysis engine.

Automate

Run scenario checks in CI and fail the build on regressions.

What it's not

Not a CSMSNot a simulatorNot a compliance tool

Quick Start

# Install the toolkit CLI
npm install -g @ocpp-debugkit/toolkit

# Inspect a trace
ocpp-debugkit inspect trace.json

# Generate a report
ocpp-debugkit report trace.json --output report.md

# Run a scenario
ocpp-debugkit scenario run failed-auth

Or try the web inspector — no installation required.