Connectors & Protocols
OCPP 1.6J vs 2.0.1: Differences and What to Ask a Hardware Supplier
The practical differences between OCPP 1.6J and 2.0.1 — security, device model, smart charging, ISO 15118 — and what to ask a charger supplier.
- Prepared by
- VULTAE Engineering Team
- Published
- Reading time
- 3 min
- Sources
- 3 references
Key takeaways
- 1OCPP is the open protocol between a charger and its management software. 1.6J is still the most widely deployed version; 2.0.1 adds built-in security profiles, a richer device model, better smart charging and support for ISO 15118 Plug & Charge.
- 2OCPP 2.0.1 was adopted by the IEC as IEC 63584, and OCPP 2.1 (2025) adds bidirectional charging and energy-management features on top of it.
- 3The version on the datasheet is not enough: ask which feature profiles or functional blocks are implemented, which security profile is supported, and which back ends the firmware has been tested with.
- 4Choose 2.0.1 for new public networks and where security or Plug & Charge matter; 1.6J remains a practical choice where your back end does not support 2.0.1 yet. Chargers that support both give you room to move.
Contents
Short answer: OCPP is the open language between a charger and its management software. 1.6J is still the most widely deployed version and works well for many networks. 2.0.1 adds security profiles with certificates, a richer device model, better smart charging, a cleaner transaction model and ISO 15118 Plug & Charge support; it was adopted by the IEC as IEC 63584. The two are not compatible, so charger and back end must match. Ask suppliers which parts of the protocol they implement and which back ends they have tested with.
Side by side
| Topic | OCPP 1.6J | OCPP 2.0.1 |
|---|---|---|
| Status | Widely deployed since 2015–2016 | Current mainstream version; IEC 63584 |
| Transport | JSON over WebSocket (the “J”) | JSON over WebSocket |
| Security | Added later through a separate security whitepaper | Built-in security profiles: basic auth, TLS, TLS with client certificates; certificate management |
| Configuration and monitoring | Fixed list of configuration keys | Device model: components and variables, flexible monitoring and reporting |
| Transactions | Start and stop messages | Unified TransactionEvent with clearer states |
| Smart charging | Charging profiles | Improved profiles, external limits, integration with energy management |
| Plug & Charge | Not native | Messages for ISO 15118 certificate handling |
| Display messages | Limited | Messages to show on the charger screen, e.g. prices |
| Firmware updates | Basic | Secure firmware update with signatures |
OCPP 2.1 (published by the IEC as IEC 63584-210:2025) builds on 2.0.1 and remains compatible with it, adding bidirectional charging, distributed-energy control and more payment options.
When to choose which
| Situation | Practical choice |
|---|---|
| New public network, security requirements, Plug & Charge plans | 2.0.1 |
| Existing back end that only runs 1.6J | 1.6J now; chargers that can switch to 2.0.1 later |
| Home and small-business chargers on an app | Either; the app provider decides |
| Large fleet or utility projects with cybersecurity rules | 2.0.1 with TLS and client certificates — see cybersecurity requirements |
What to ask a hardware supplier
- Version: 1.6J, 2.0.1 or both? Can the charger be switched between them by configuration or firmware?
- Scope: which feature profiles (1.6J) or functional blocks (2.0.1) are implemented — smart charging, local authorisation list, firmware management, reservation, display messages?
- Security: which security profile? How are certificates installed and renewed?
- Certification: has the firmware been certified by the Open Charge Alliance, or tested at plugfests?
- Interoperability: which back ends has this firmware been tested with?
- Error reporting: how detailed are status notifications and error codes?
- Updates: how long will the firmware be maintained, and how are updates delivered?
Then test a sample on your own back end before ordering in volume — see what to test on samples.
OCPP is one link in the chain
OCPP connects charger and back end. Other protocols connect the back end to roaming partners (OCPI, OICP) and the car to the charger (ISO 15118, DIN 70121) — see OCPP vs OCPI vs OICP and ISO 15118 and Plug & Charge.
VULTAE chargers and OCPP
Our networked AC and DC chargers support OCPP 1.6J and OCPP 2.0.1 over Ethernet, Wi-Fi or 4G and work with third-party back ends. Tell us your platform and we will confirm the firmware version and features tested with it — see charge point management software.
Questions buyers ask
- What is the main difference between OCPP 1.6J and 2.0.1?
- OCPP 2.0.1 adds defined security profiles with certificate management, a flexible device model for configuring and monitoring chargers, improved smart charging, a unified transaction model and messages for ISO 15118 Plug & Charge. It is not backwards compatible with 1.6, so charger and back end must both support it.
- Is OCPP 2.0.1 better than 1.6J?
- Technically, yes — especially for security, diagnostics and Plug & Charge. In practice the best version is the one your charger and back end both implement well and have tested together. Many networks still run 1.6J successfully.
- Should I wait for OCPP 2.1?
- Not for most projects. OCPP 2.1 builds on 2.0.1 and is backwards compatible with it, adding bidirectional charging and distributed-energy control. A charger with solid 2.0.1 support is a good basis today.
- How do I check a supplier’s OCPP support?
- Ask for the OCPP version and the supported feature profiles or functional blocks, the security profile, any Open Charge Alliance certification, and a list of back ends the firmware has been tested with. Then test a sample with your own back end.
References
- [1]Open Charge Point Protocol (OCPP). Open Charge Alliance.
- [2]OCPP 2.1 Edition 1 officially published by IEC as IEC 63584-210:2025. Open Charge Alliance.
- [3]Open Charge Point Protocol. Wikipedia.
