OCPP: the charger's link to its backend
The Open Charge Point Protocol between a charger and its operator's backend (CSMS). It never runs on the charging cable, but its log is often the first evidence in a support ticket. This page lists the messages that matter when debugging a session and how to line them up with a capture.
Role and versions
OCPP runs between the charging station and the charging station management system (CSMS, called Central System in 1.6). The charger opens a WebSocket connection to the backend and both sides send JSON messages over it: each call is answered by a result or an error. The car is never a party; OCPP sees the car only through what the charger reports.
| Version | Status | What matters for session debugging |
|---|---|---|
| OCPP 1.6J | Most widely deployed; JSON over WebSocket (the older 1.6S used SOAP) | StartTransaction and StopTransaction per session, StatusNotification with a ChargePointErrorCode |
| OCPP 2.0.1 | Current mainstream release, replacing the withdrawn 2.0 | TransactionEvent for the whole session, a device model with NotifyEvent for errors, native ISO 15118 certificate handling |
| OCPP 2.1 | Extends 2.0.1 | Bidirectional power and ISO 15118-20 support, more smart charging features |
OCPP 2.0.1 has also been published by IEC (as IEC 63584 in most references), and the release year of 2.1 is commonly given as 2025. Verify both before citing them.
Messages that matter
| Message | Versions | Why you look at it |
|---|---|---|
| BootNotification | all | Firmware version and model of the charger; a reboot during a session shows as a new BootNotification |
| StatusNotification | all | 1.6: connector status (Available, Preparing, Charging, SuspendedEV, SuspendedEVSE, Finishing, Faulted) with errorCode and vendor info. 2.0.1: connector status only, errors go to NotifyEvent |
| Authorize | all | Whether and when the identifier was accepted; in 2.0.1 it can carry ISO 15118 certificate hash data for Plug and Charge |
| StartTransaction, StopTransaction | 1.6 | Start and end of the transaction; StopTransaction carries a reason such as EVDisconnected, Local, Remote or EmergencyStop |
| TransactionEvent | 2.0.1, 2.1 | Started, Updated and Ended events with a trigger reason and, at the end, a stopped reason |
| MeterValues | all | Energy, power, current, voltage and state of charge sampled during the session |
| NotifyEvent | 2.0.1, 2.1 | Component and variable based error and state reports |
| Get15118EVCertificate | 2.0.1, 2.1 | The charger forwards the car's certificate installation or update request to the backend |
| GetCertificateStatus | 2.0.1, 2.1 | OCSP status of a certificate in the contract chain |
| SignCertificate, CertificateSigned | 2.0.1, 2.1 | The charger obtains its own SECC certificate for TLS with the car |
| NotifyEVChargingNeeds, NotifyEVChargingSchedule | 2.0.1, 2.1 | The ISO 15118 charging needs and the schedule the car chose, forwarded to the backend |
| SetChargingProfile | all | The limit or schedule the backend imposes; it ends up in the SAScheduleList or the charger's limits |
| DataTransfer | all | Vendor specific messages; 1.6 Plug and Charge implementations carry the certificate messages here |
For the 1.6 error codes and where each leads in a capture, see the ocpp16 code dictionary. EVCommunicationError is the one this tool can explain: no SLAC match, no SDP answer, a V2G timeout or a closed TCP connection.
Correlating an OCPP log with a capture
- Align the clocks first. OCPP timestamps are UTC from the charger's clock; the capture has the sniffer's clock. Pick one event visible in both, such as StatusNotification Preparing and the pilot going to state B, or the transaction start and PowerDeliveryRes Start, and compute the offset.
- Map the states: Preparing corresponds to plug in, SLAC and the session setup; Charging to the CurrentDemand or ChargingStatus loop; SuspendedEV to the car holding zero current or state B; SuspendedEVSE to the charger offering zero; Finishing to PowerDelivery Stop up to unplug.
- Match the identifier: for Autocharge the idTag or idToken is the car's MAC address, the EVCCID of SessionSetupReq; for Plug and Charge it is the eMAID from the contract certificate.
- Compare metering: MeterValues current against EVSEPresentCurrent in CurrentDemandRes; a large difference points to a meter or configuration fault.
- Read the stop reason from both ends: the StopTransaction or TransactionEvent reason against the session ending the tool reports (Timeout, EVSE stopped, EV stopped early).
An AuthorizationRes that stays Ongoing for many seconds in the capture usually has an Authorize call waiting for the backend at the same moment in the OCPP log. If the backend never answers, the car eventually gives up (TIM-02).
Other backend protocols
| Protocol | Between | Purpose |
|---|---|---|
| OCPI | CPO and eMSP | Roaming: locations, tariffs, sessions, charge detail records, token authorisation |
| OICP | CPO or eMSP and the Hubject platform | Roaming through a hub, including Plug and Charge contract data |
| OSCP | Grid or site operator and CPO | Capacity forecasts for smart charging |
| IEC 63110 | Charger and its management system | IEC protocol for managing charging and discharging infrastructure, in development |
| IEC 63119 | Roaming parties | IEC information exchange for roaming services |
The status and part structure of IEC 63110 and IEC 63119 are to be verified.
This tool reads OCPP-J logs of the charger (OCPP 1.6 and 2.0.1) and places their messages on the session timeline; it does not read the other protocols here. They matter as context: they decide whether a car was authorised and what power limit the charger offered, and the capture shows the effect.
Sources
- OCPP 1.6 edition 2, Open Charge Alliance, JSON over WebSocket
- OCPP 2.0.1, Open Charge Alliance, parts 1 to 4
- OCPP 2.1, Open Charge Alliance