OCPP versions at a glance

OCPP 1.6 is still widely used. OCPP 2.0.1 and 2.1 add more detailed security, device management and energy functions. Newer does not automatically mean better. The charger and its management system (CSMS or CPMS) must support the same version and the functions the operator actually needs.

 

What changes between the versions?

OCPP 1.6

Released in 2015, OCPP 1.6J uses JSON over WebSockets. It covers charger status, authorisation, transactions, meter values, faults, remote actions and basic smart charging. Its large installed base keeps it relevant for existing networks and CPMS integrations. It is not directly compatible with OCPP 2.x.

OCPP 2.0.1

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

OCPP 2.1

Released in January 2025, OCPP 2.1 builds on and is backward-compatible with 2.0.1. It adds ISO 15118-20 support, bidirectional charging, distributed energy resource (DER) control, more smart-charging options and new payment and authorisation functions. The charger, vehicle, CPMS and wider energy system must still support the chosen feature.

Which OCPP version should you choose?

For an existing network, OCPP 1.6 can remain the sensible choice when it covers the job and the installed chargers work well. An upgrade needs a reason, compatible firmware and CPMS support. A larger version number is not a business case.

 

For new deployments, OCPP 2.0.1 is a practical procurement baseline when richer security, device management or ISO 15118 integration is required. OCPP 2.1 matters when a project genuinely needs bidirectional charging, DER control or its added smart-charging functions. 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 leaving a route to the later protocol.

 

Hardware readiness is not active OCPP 2.0.1 support. The usable version and functions depend on the charger model, firmware, CPMS and completed integration tests. amina does not claim OCPP 2.1 support 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 also needs a 1.6 endpoint, or the charger needs compatible 2.0.1 firmware.

Does OCPP 2.1 make OCPP 2.0.1 obsolete?

No. The Open Charge Alliance supports both. OCPP 2.1 adds functions while retaining 2.0.1 compatibility.