OCPP connected, data missing: test the complete charging session.
Assess the technical connection between one charge point model and a backend. Transfer status, meter values and charging sessions in a traceable way.
Read the German originalConsider version and functionality together
OCPP connects charge points to a management system. The Open Charge Alliance describes different versions and testing options. Saying a device is OCPP capable does not establish which functions its specific firmware supports.
Record the charge point model, firmware, backend and required functions. Start with a traceable charging session in an authorised test environment. This provides the reference for further investigation.
Events can arrive late
An unstable connection can delay meter values or status messages. Their association must remain intact through suitable references. Do not confuse the time a message is received with the time of the event it describes.
Test an interruption during a session and the subsequent reconnection. Check whether data is delivered later, gaps remain visible and duplicate events do not create a second transaction. A green connection indicator does not answer these questions.
Distinguish software testing from operating the installation
A technical pilot shows whether the agreed message flow works. It establishes neither metrologically compliant billing nor the safety of an electrical installation. The relevant specialists must be involved for those tasks.
The handover describes tested firmware, functions and known limits. Backlogs and failures should be visible in operation. Test new charge point models and additional control functions specifically before adding them to the operational scope.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
OCPP: connect charge points to your backend · Packages