Commercial charging networks in the real-world constantly have to react and adapt to problems in the field. These may be caused by faulty communications links, unexpected driver behavior, hardware faults and firmware bugs.
Based on our experience running and managing real world commercial networks, we have built transaction improvement intelligence to improve the quality of charging services delivered by your network.
eDRV's network manages and monitors chargestations and driver transactions in near real time and intelligently takes action when needed.
There are many reasons why a chargestation unexpectedly does not start the flow of energy. These reasons range from driver failing to plug in his EV to poor data connectivity at the chargestation.
Zombie 🧟 Transactions.
If a transaction fails to start within 5 minutes, eDRV will attempt to stop the charging attempt and clean up the state of the (data) on the transaction as a protective measure.
Similar to the case above, sometimes a chargestation may miss a stop transaction message completely giving the impression that a driver is still charging when they may have driven off hours ago. This may lead to unexpected charges for the driver if this is not acted upon by the network as soon as possible.
Eternal ♾️ Transactions
If a transaction fails to stop within 6 hours, eDRV will attempt to stop the charging attempt and clean up the state of the (data) on the transaction as a protective measure.
eDRV detects when the EV is no longer taking energy from the chargestation. This is an indication of the fact that the battery is full.
EV Full Webhook
EV full charge detection triggers a webhook to your application server. Traditional use cases here for alerting the driver and requesting them to move the EV. For further details on webhooks see: Webhooks
At the start of a transaction, the network operator has no indication of how long an EV will stay on the chargestation or how much energy will be consumed.
This is a problem if at the end of a transaction your driver (customer) is unable to settle his payment. For example is his wallet does not have enough credit or his credit card has expired.
If a transaction is started using the API with a specified ceiling, eDRV's charging intelligence will ensure that the transaction does not exceed the limits set and will attempt to stop the transaction automatically.
The available limit types are:
- Energy (kWh): E.g A transaction is started via a remotestart API call with a 37kWh limit. Transaction is cut off at 36kWh by eDRVs charging intelligence.
- Time (seconds)
- Money (Currency): E.g A transaction is started via a remotestart command API call with a $20 limit. Transaction is cut off at $19 by eDRVs charging intelligence.
Updated 8 months ago