TestPilot
Validate a charger against the protocol in minutes
Point a charging station at the CSMS over wss:// and prove it works — a live OCPP log, operator commands, and an exportable pass/fail report.
Why TestPilot?
Everything you need to prove OCPP conformance. Nothing you don't.
No bench, no lab
Point a charger at a wss:// URL and start validating. No power supply, no test rig — just the protocol.
Every frame decoded
CALL / CALLRESULT / CALLERROR parsed live and laid out in a structured, color-coded log as they arrive.
Operator commands
Trigger RemoteStart/Stop, Reset, ChangeConfiguration and more — and watch exactly how the charger responds.
Shareable report
Export a pass/fail conformance report you can hand to a customer or a certifier — status is always icon + word.
Conformance test cases
OCPP 1.6 Core Profile — a sample of the checks in the current suite.
| Test ID | Description | Spec reference | Status |
|---|---|---|---|
TC-001 | BootNotification — valid payload | OCPP 1.6 §4.2 | Passing |
TC-002 | BootNotification — missing required fields | OCPP 1.6 §4.2 | Passing |
TC-003 | Heartbeat — interval compliance | OCPP 1.6 §4.6 | Passing |
TC-004 | StartTransaction — idTag validation | OCPP 1.6 §5.2 | Passing |
TC-005 | StopTransaction — reason codes | OCPP 1.6 §5.3 | Passing |
TC-006 | StatusNotification — all connectorStatus values | OCPP 1.6 §4.10 | Passing |
How it works
Three steps, no hardware lab.
Point your charger at the CSMS
Set the charger's Central System URL to your TestPilot wss:// endpoint. It connects inbound like it would to any CSMS.
Drive the session
Watch every OCPP message decode in real time, and send operator commands — RemoteStart/Stop, Reset, ChangeConfiguration.
Export the report
Get a pass/fail conformance report mapped to the spec — ready to share with a customer or certifier.
Be among the first
We're working with a handful of charger teams to validate TestPilot against real hardware. Bring a charger — we'll bring the CSMS.
Request a demo