Yes, OCPP 1.6 and OCPP 2.0.1 can be used simultaneously on the same charging network when managed through UnityCharge’s Charging Management System. The system supports protocol version negotiation without requiring cloud connectivity, enabling seamless communication with chargers that support either version.
How Protocol Negotiation Works
UnityCharge’s CMS handles protocol version negotiation by initiating a handshake between the charging station and the system during connection. The system evaluates the capabilities of each charger and automatically selects the appropriate OCPP version for communication. This process occurs locally on the edge computing platform, ensuring that network outages or cloud dependency do not disrupt operations.
When a charger supports both OCPP 1.6 and 2.0.1, UnityCharge dynamically chooses the most compatible version based on the charger’s advertised capabilities and the network’s configuration. This flexibility allows operators to maintain legacy chargers while integrating newer ones without requiring a full infrastructure upgrade.
Practical Implications for CPOs
For Charge Point Operators (CPOs), this dual-version support means they can manage a mixed fleet of chargers without needing to standardize on a single protocol. It reduces operational complexity and avoids costly replacements of older hardware.
Operators can also benefit from improved uptime and reduced maintenance overhead, as the system’s offline capability ensures that protocol negotiation continues even when cloud connectivity is limited. This is especially valuable in remote or low-bandwidth locations where consistent communication is critical.
Related Reading
For more on related topics, see: OCPP 2.0.1 Tariff Configuration for CPOs.
Further reading: EV Charging Software Features | Tecell CMS (UnityCharge) – OCPP, Billing, Mobile
📣 Join our Telegram channel for EV charging technology insights and product updates.
Also find us on: LinkedIn · X · Bluesky · Mastodon · DEV.to.