Home / EV charger integration
EV charger integration
When a specific brand, model, and firmware must connect to the console, start with a compatibility assessment and an agreed test list.
Integration focuses on negotiation, status and session visibility, and keeping “Accepted” separate from “site action completed.” Sessions without reliable interval meters stay under review with no guessed amount.
What the assessment covers
- Protocol negotiation for OCPP 1.6, 2.0.1, and 2.1; 1.6 wins when offered together with another version.
- 2.0.1/2.1 currently cover boot, heartbeat, status, authorization, and transaction events; 2.1 has no extra exclusive features.
- Console visibility for online state, heartbeat, connectors, energy, and amount; card numbers are masked on the session screen.
- Live tests are scheduled via contact and limited to the agreed cases.
Current framework and custom needs
- This is the standard compatibility framework used to confirm protocol, status, and session visibility quickly.
- Special protocol fields, vendor logic, or site-system hooks can be reviewed together and added to the PoC scope.
- The demo cannot register live chargers; live tests and custom integration are arranged through contact.
Next step
Send brand, model, firmware, and protocol version to book a compatibility review; note any custom needs in the same message.
Contact