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
Send RemoteStart/Stop, Reset and TriggerMessage — 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.
Stations and chargers
Group chargers into stations. Each charger has its own OCPP ID, OCPP version (1.6, 2.0.1 or 2.1) and security profile, so one station can mix them.
Refused, with the reason
A charger that connects with the wrong security, tries to downgrade, or does not speak the OCPP version it is set to is refused — and the reason is written to that charger's log.
Conformance test cases
The OCPP 1.6 Core suite, step by step. Every frame is also checked against the OCA JSON schema. 2.0.1 and 2.1 have suites of their own.
| Test ID | Description | Spec reference | Status |
|---|---|---|---|
TC-001 | BootNotification — required fields present | OCPP 1.6 §4.2 | Passing |
TC-002 | StatusNotification — a valid connector status | OCPP 1.6 §4.9 | Passing |
TC-003 | Authorize — idTag presented | OCPP 1.6 §4.1 | Passing |
TC-004 | StartTransaction — on a real connector (connectorId > 0) | OCPP 1.6 §4.8 | Passing |
TC-005 | MeterValues — at least two samples, at a steady cadence | OCPP 1.6 §4.7 | Passing |
TC-006 | StopTransaction — echoes the issued transactionId | OCPP 1.6 §4.10 | Passing |
Security profiles
All four OCPP Security Profiles, chosen per charger — from a 1.6 charger with no password support to TLS with a client certificate.
| Profile | Transport | Authentication |
|---|---|---|
| 0 | ws:// | No passwordFor 1.6 chargers that have no password support. |
| 1 | ws:// | Password |
| 2 | wss:// | Password, over TLS |
| 3 | wss:// | Client certificate |
Three ways to get a Profile 3 certificate
Download one from TestPilot
TestPilot issues a client certificate for the charger. Download it and install it on the charger.
Let the charger request it
The charger asks for one over OCPP — SignCertificate, answered with CertificateSigned.
Upload your own CA
Already have a certificate authority? Upload it, and chargers holding certificates it signed are accepted.
Plan limits: see pricing
How it works
Three steps, no hardware lab.
Point your charger at the CSMS
Add a station and its chargers, and pick each charger's OCPP version and security profile. Then set the charger's Central System URL to the ws:// or wss:// endpoint TestPilot shows for it. It connects inbound like it would to any CSMS.
Run the suite
TestPilot drives the charger through each step itself — TriggerMessage, RemoteStart and RemoteStop — while every OCPP message decodes in real time. Send your own commands by hand whenever you want.
Export the report
Get a pass/fail conformance report — what each step expected, what the charger actually sent — ready to share with a customer or certifier.
Test your first charger free
The free tier connects one charger on any OCPP version — no card. Want a walkthrough with your own hardware first? Bring a charger — we'll bring the CSMS.
Request a demoOr leave your email and we'll tell you when new suites ship: