Which OCPP Versions Does TrendPower Support?

Choosing EV charging software begins with a practical question: will it communicate with the chargers you already own and the models you plan to install next? The protocol version matters, but so do charger firmware, enabled features and commissioning results.

OCPP support at a glance

OCPP is the communication protocol between a charge point and a charging station management system (CSMS). It enables common operational messages across hardware and software from different suppliers. It does not, by itself, guarantee that every charger implements every optional function in the same way.

When does OCPP 1.6J make sense?

OCPP 1.6J remains a practical choice when an operator has an installed fleet that already communicates reliably with its backend. A migration need not begin with replacing those chargers. TrendPower can review their connection settings and required workflows, then test whether the TrendPower CPMS receives the correct status, authorization, transaction and meter data.

For a new installation, ask the hardware supplier which features are actually implemented. “OCPP 1.6 compatible” does not tell you whether the charger supports the charging profiles, offline authorization or security extensions your business needs.

When should an operator consider OCPP 2.0.1?

OCPP 2.0.1 is worth evaluating for new networks that require more structured device management, stronger security workflows or detailed charger diagnostics. It also provides a framework for features associated with smart charging and ISO 15118 integration. That framework is not a promise that Plug & Charge works on every OCPP 2.0.1 charger; the vehicle, charger, certificates and other parties in the service chain must also support it.

The Open Charge Alliance distinguishes mandatory Core functions from optional OCPP 2.0.1 certification profiles, including Smart Charging and ISO 15118 Support. This is why TrendPower asks customers to specify the function they need, not just the version number. For a deeper technical comparison, read TrendPower's OCPP 1.6 vs OCPP 2.0.1 guide.

Can TrendPower manage a mixed OCPP 1.6J and 2.0.1 network?

That is a common project requirement. An operator may have OCPP 1.6J chargers at existing sites while specifying OCPP 2.0.1 for a new rollout. TrendPower's platform can be scoped to bring compatible chargers into one operating environment for monitoring, sessions and commercial workflows.

The operator experience can be unified, but the hardware capabilities are not automatically identical. For example, a remote command or diagnostic field available on one 2.0.1 charger may be absent from an older 1.6J model. TrendPower should map features by charger model so staff know which functions are available at each site.

How TrendPower approaches charger compatibility

TrendPower's published solution PDF describes its OCPP 1.6/2.0.1 compatibility and a platform built for charger management, user applications and operations. In a real project, the useful proof is a test with the exact equipment and workflows the operator intends to deploy.

1. Identify the hardware. Share charger manufacturer, model, firmware version, OCPP endpoint configuration and the supplier's supported-feature documentation.
2. Define the operating journey. Include RFID or app authorization, remote start and stop, session data, pricing, payment and any site-host reporting.
3. Test essential messages. Confirm boot, status changes, authorization, transaction start and end, meter values, fault reports and recovery after disconnection.
4. Test optional functions separately. Smart charging, reservations, firmware updates, certificates and Plug & Charge-related workflows require explicit verification where applicable.
5. Run a pilot. Validate real driver sessions, failed payments, network outages and operator response before adding the rest of the charger fleet.

TrendPower's Hongxinda overseas OCPP platform project illustrates how charger connectivity sits alongside local language and payment integration. It is a project example, rather than evidence that every charger model supports every optional OCPP function.

What about OCPP 2.1 and formal certification?

The Open Charge Alliance lists OCPP 2.1 as a newer protocol version. TrendPower's solution PDF identifies compatibility with OCPP 1.6 and 2.0.1, so customers should not assume 2.1 support or infer it from a 2.0.1 integration. If your tender calls for OCPP 2.1, provide the precise feature and interface requirements for a separate technical review.

Likewise, protocol compatibility is different from OCA certification. An OCA certificate relates to a particular product, protocol version and tested profiles. If certification is mandatory for your charger or management system, ask for the exact certificate and check the Open Charge Alliance's certification records.

What should you send TrendPower for an OCPP assessment?

A useful first message contains the charger models and quantities; firmware and OCPP versions; current backend or migration requirements; country of deployment; must-have functions; expected payment methods; and the pilot launch date. If possible, attach your charger's Protocol Implementation Conformance Statement (PICS), test reports or sample OCPP logs. These details help TrendPower distinguish standard configuration from integration work that needs a separate scope.

Reference: TrendPower EV Charging Solution PDF; Open Charge Alliance protocol overview.