Chargers

Q: What should I do if a charger repeatedly goes offline?
A: Common causes include network instability, outdated firmware, or communication dropouts. Check OCPP logs for Heartbeat and BootNotification events, and ensure the charger has a stable backend connection.

Q: Why does the charger show as available but doesn't start charging?
A: This can happen if the vehicle doesn’t request power or if there's a communication fault. Ask the driver to unplug and plug in again and monitori if charging starts. If you see status updates on eMabler charger logs those will indicate if transaction has started or if the status is stuck on Preparing mode it is likely a cable/car connection problem.

Q: What causes 'Faulted' status in chargers?
A: Faulted states may result from hardware issues, failed resets, or internal charger errors. Inspect the last StatusNotification and look at the description field for potentially more information about the error.

Q: How to confirm if a charger firmware is outdated?
A: Check the firmwareVersion field via the API or device dashboard. Compare it against your certified firmware list.

Q: What should I check if a charger stays offline for several hours?
A: Inspect modem connection, power supply, and signal strength. A nightly offline state often points to environmental or connectivity-related issue. With poor coverage in GSM modem connections it can take long time for stable connection to establish. Different chargers also have antennas placed differently on the hardware that can cause connectivity issues.

Q: What happens when a charger restarts—will the socket names update?
A: No, the socket name is not set by the charger, it is a metadata field in eMabler system. Therefore the socket name will not change with charger restarts.

Q: When are chargers blocked, and how can I avoid it?
A: Chargers are automatically blocked by the system in two situations:

1. Unknown charger ID:
   If a charger connects with an ID that is not recognised in eMabler, it is blocked for one hour.
   You can unblock it immediately by adding the charger through Connect or the new API, or by ensuring the charger is added to eMabler before configuring the OCPP connection.

2. Unstable connectivity:
   If a charger repeatedly reconnects due to very poor network conditions, the system temporarily blocks it for one hour.
   This allows the charger to stabilise instead of entering an infinite reconnect loop.

How to avoid chargers being blocked

• Ensure the charger has stable and reliable network connectivity.

• Add the charger in through the new API or Connect. If you have integrations using the old API, then the charger should be added to eMabler before setting the OCPP endpoint of the charger to point to eMabler OCPP.