The OCPP Integration Problems We See Most Often

For many EV charging projects, getting the hardware installed is the easy part. The real work often starts when the chargers need to connect to the customer’s own OCPP backend.

We have worked on projects where the charger could power a vehicle normally, but the platform showed the wrong connector status. In other cases, the backend accepted the charging data but calculated the wrong amount. We have also seen chargers appear offline even though the site still had internet access, and Remote Start commands that were accepted without the vehicle ever beginning to charge. None of these situations are unusual.

OCPP gives chargers and backend platforms a common language, but that does not mean every system behaves the same way.

Below are the OCPP issues we come across most often and how our engineering team usually approaches them.

Immersion Liquid Cool EV Charger 2

Charging Works, but the Billing Is Wrong

The vehicle connects, charging starts, power is delivered, and the session appears to finish normally. But the backend may show zero energy, the wrong kWh value, or an incorrect charge amount.

When this happens, we do not start by replacing meters, charging modules, or other hardware. We start with the OCPP transaction.

The first messages we normally review are:

  • StartTransaction
  • MeterValues
  • StopTransaction

That is why a billing problem cannot be diagnosed by looking at the charger alone.

The useful question is:

What did the charger send, what did the server receive, and what did the platform do with that data?

The Connector Status Does Not Match What Is Happening at the Charger

Another common complaint is that the connector status shown on the OCPP platform does not match the physical charger.

The driver may have already unplugged the cable, but the backend still shows Preparing, Charging, or Finishing.

Sometimes the session has ended, but the connector never returns to Available.

For OCPP 1.6J, these cases are often related to StatusNotification.

A normal session may move through a sequence such as:

Available → Preparing → Charging → Finishing → Available

Real installations are not always this clean.

A network drop can occur at the wrong moment. A status message can be delayed. An abnormal stop can also leave the connector in a state that neither side handles correctly.

We compare the time when the cable was connected, when authorization was completed, when charging actually started, when power stopped, when the cable was removed, and which StatusNotification messages were exchanged during that period.

RemoteStartTransaction Is Accepted, but the Vehicle Does Not Charge

This causes a lot of confusion during OCPP commissioning. The charger replies Accepted. But nothing happens at the vehicle.

It does not mean the full charging process has already been completed.

The charger still needs to verify several conditions, including the connector state, vehicle connection, authorization, cable locking, internal faults, and power module readiness.

So when Remote Start is accepted but charging does not begin, we do not stop at the OCPP message.

We continue into the charger system log and, if necessary, the vehicle communication log.

This is one of the reasons OCPP troubleshooting requires more than protocol knowledge. The backend may be working correctly while the actual charging process is being blocked somewhere else.

The Charger Keeps Going Offline

In many overseas projects, what initially looks like an OCPP problem turns out to be a network problem.

That is why we always recommend testing network stability as part of commissioning rather than waiting for repeated offline alarms after the chargers are already in service.

Both Systems Support OCPP 1.6J. Why Is There Still a Compatibility Issue?

We hear this question often. The charger supports OCPP 1.6J. So why is additional integration work needed? Because the protocol standard is only part of the system

For that reason, we consider OCPP compatibility testing part of the project, not an optional extra.

Before a large shipment, we normally recommend testing at least:

  • BootNotification
  • Heartbeat
  • StatusNotification
  • Authorize
  • StartTransaction
  • StopTransaction
  • MeterValues
  • RemoteStartTransaction
  • RemoteStopTransaction
  • Network reconnection
  • Charger reboot
  • Fault reporting
  • Charging Profile
  • Firmware update

For DC fast charging projects, real vehicle testing is also valuable because the backend is only one part of the charging chain.

How We Troubleshoot OCPP Problems

We normally compare three sources:

  • the OCPP backend log
  • the charger system log
  • what actually happened between the charger and vehicle

Then we follow one charging session from start to finish.

  • When was the vehicle connected?
  • When did authorization happen?
  • When was the remote command received?
  • When did the charger start delivering current?
  • Were MeterValues reported correctly?
  • When did the session stop?
  • Was StopTransaction sent?
  • Did the connector return to Available?

OCPP Integration Support From the Charger Manufacturer

For us, supplying an EV charger does not end with hardware delivery.

When customers connect our chargers to their own OCPP backend, our engineering team can support OCPP 1.6J integration, backend compatibility testing, Remote Start and Remote Stop troubleshooting, connector status analysis, MeterValues verification, billing-related data checks, and charger offline investigation.

For customers planning a larger rollout, we strongly recommend completing OCPP integration testing before mass deployment.

Update cookies preferences
WhatsApp

Get a Quick Quote!

x

    Get a Quick Quote!

    x