OCPP (Open Charge Point Protocol)

Q: What causes a 'Connector already in use' error?
A: This happens when the backend believes a session is active. Check for missed StopTransaction messages and ensure the connector is idle.

Q: Why does the charger reject RemoteStartTransaction?
A: Ensure the connector is not reserved or faulted. The charger must be in Available state and the vehicle must be ready.

Q: Can chargers support multiple charging profiles?
A: Yes. You can set different profiles with stack levels for site limits and smart charging use cases.

Q: How can I confirm Remote Start capabilities?
A: If remote start works via the UI, the charger supports remote start for other flows (e.g., ad-hoc or Express) as well.

Q: What causes 'Timeout' errors in transaction logs?
A: These usually arise from delayed backend responses or slow charger reactions. Inspect round-trip message logs and retry logic in OCPP sessions.

Q: What does StatusNotification with status Preparing mean?
A: It indicates the charger is waiting for the vehicle to initiate charging after successful authorization. This is common right before energy flow starts.

Q: How do I ensure the charger is pointing to the correct OCPP endpoint?
A: Verify the charger's configuration (locally or via backend provisioning) includes the correct OCPP server URL provided by eMabler.