Connectors & Protocols
OCPP Message Flow: From Plug-In to Stop Transaction
Follow an OCPP 1.6J session message by message: Authorize, StartTransaction, MeterValues and StopTransaction, plus how to test it and read the logs.
- Prepared by
- VULTAE Engineering Team
- Published
- Reading time
- 2 min
- Sources
- 1 references
Key takeaways
- 1An OCPP 1.6J session is a predictable sequence: the charger reports status, authorises the driver, starts a transaction, sends meter values and stops the transaction. Billing depends on the start and stop meter values.
- 2Knowing the sequence lets you read logs, test a charger against your back end and see exactly where a failed session stopped.
- 3OCPP 2.0.1 reorganises the same idea around TransactionEvent messages and a richer status model, but the stages (connect, authorise, charge, stop) are the same.

Contents
Short answer: in OCPP 1.6J a normal session runs Preparing → Authorize → StartTransaction → Charging (MeterValues) → StopTransaction → Finishing → Available. Every step is a message between the charger and the back end, so every failure leaves a trace in the log.
A session step by step
| Step | Message or status | What it means |
|---|---|---|
| 1 | StatusNotification: Preparing | The cable is connected; the charger waits for authorisation |
| 2 | Authorize | The driver identifies (RFID card, app); the back end accepts or rejects |
| 3 | StartTransaction | The session begins; the charger sends the meter start value and time |
| 4 | StatusNotification: Charging | Energy flows to the car |
| 5 | MeterValues (repeated) | Energy, power, current and sometimes voltage and temperature |
| 6 | StopTransaction | The session ends; the charger sends the meter stop value, time and reason |
| 7 | StatusNotification: Finishing, then Available | The cable is removed; the connector is ready again |
Heartbeat messages run in the background so the back end knows the charger is alive.
Reading a log
- Find the connector and time. Filter by charger ID and the session start.
- Follow the order. If StartTransaction is missing, look at Authorize and the answer to it.
- Check the answers. An Authorize reply of Blocked, Expired or Invalid explains a session that never started.
- Check meter values. Missing or jumping values break billing.
- Check the stop reason. Local, Remote, EVDisconnected, PowerLoss and similar reasons tell you who ended the session.
Common problems and where to look
| Symptom | Likely place |
|---|---|
| Card tapped, nothing happens | Authorize request or reply |
| Charger says charging, no energy | Car or charger fault; StatusNotification error code |
| Session shows 0 kWh | MeterValues or meter start/stop values |
| Session never closes | StopTransaction not sent or not acknowledged after a connection loss |
| Duplicate sessions | Transaction messages queued and resent after a reconnect |
Test it before you buy
On a sample charger, run each step against your own back end: authorise, start, let it run, stop locally, stop remotely, pull the plug and drop the network. Compare the logs with the table above. See sample testing and integration test checklist.
What changes in OCPP 2.0.1
The 2.0.1 specification replaces StartTransaction and StopTransaction with TransactionEvent messages (started, updated, ended) and uses a more detailed status model. Check how your back end handles it: see OCPP 1.6J vs 2.0.1 and the device model. The stages stay the same: connect, authorise, charge, stop.
Questions buyers ask
- Which message starts a session in OCPP 1.6J?
- StartTransaction, normally after Authorize has accepted the identifier or after a remote start. The charger sends the connector, the identifier, the meter start value and a timestamp.
- Where do the energy values come from?
- From the charger’s meter: the start value in StartTransaction, readings in MeterValues during the session and the stop value in StopTransaction. The energy of the session is the difference.
- Why does a session sometimes not start?
- Common causes are a rejected identifier, a connector in a fault or unavailable state, a lost connection, or a back end that does not respond. The log shows which message was last sent and what answer came back.
References
- [1]Open Charge Point Protocol (OCPP). Open Charge Alliance.


