OCPP versions at a glance

OCPP 1.6 remains widely used, while OCPP 2.0.1 and 2.1 add more detailed security, device-management and energy functions. The newest version is not automatically the best choice. The charger and its charging management system (CSMS or CPMS) must support the same version and the functions the operator intends to use.

 

What changes between the versions?

OCPP 1.6

Released in 2015, OCPP 1.6J uses JSON over WebSockets. It covers the functions needed by many operating networks, including charger status, authorisation, transactions, meter values, fault reporting, remote actions and basic smart charging. Its broad installed base makes it relevant for existing estates and CPMS integrations. It is not directly compatible with OCPP 2.x.

OCPP 2.0.1

Released in 2020, OCPP 2.0.1 introduced a different application model, so it is not backward-compatible with 1.6. It adds a structured device model, stronger security, improved transaction handling and fuller support for ISO 15118 functions such as Plug & Charge certificate management. Edition 3 became the IEC 63584 standard in 2024.

OCPP 2.1

Released in 2025, OCPP 2.1 extends 2.0.1 rather than replacing its application logic. Its additions include ISO 15118-20 support, bidirectional energy flow, distributed energy resource (DER) control, more smart-charging options and new payment and authorisation functions. These features still require support across the charger, vehicle, CPMS and wider energy system.

Which OCPP version should you choose?

For an existing network, OCPP 1.6 can remain appropriate when it covers the required operations and the installed chargers are performing well. An upgrade needs a clear use case, compatible firmware and CPMS support.

 

For new deployments, OCPP 2.0.1 is a useful procurement baseline where richer security, device management or ISO 15118 integration is required. OCPP 2.1 becomes relevant when a project genuinely needs bidirectional charging, DER control or its additional smart-charging functions. In every case, ask which functional blocks are implemented, whether the product is OCPP certified, and which charger-CPMS combinations have been tested.

How this maps to amina’s roadmap

The current amina C/C2 and amina M/M2 product pages specify local OCPP 1.6J and hardware readiness for OCPP 2.0.1. That supports current CPMS integrations while preparing the hardware for a later protocol step.

 

Hardware readiness is not the same as active OCPP 2.0.1 availability. The usable version and functions depend on the charger model, firmware, CPMS and completed integration testing. No OCPP 2.1 support claim is made here.

OCPP version questions

Can an OCPP 1.6 charger connect to an OCPP 2.0.1 CPMS?

Not through those versions directly. The CPMS would also need an OCPP 1.6 endpoint, or the charger would need compatible OCPP 2.0.1 firmware.

Does OCPP 2.1 make OCPP 2.0.1 obsolete?

No. The Open Charge Alliance continues to support both. OCPP 2.1 adds functions while preserving 2.0.1 application logic.