K |
Kurt Ziegler |
On a route with combined CSS and L2 charging stops, the total charge time is reported incorrectly. It's adding the CSS times but not the L2.
abetterrouteplanner.com/?plan_uuid=d78831da-0207-4107-ae12-4f49171cf2b5
Activity Newest / Oldest
Mattias_ABRP
Status changed to: Done
Mattias_ABRP
Hey Kurt,
your charging at City of Caldwell is what we call a destination charger, all Level 2 chargers are. The charging on such a charger is slow and more or less we are counting on you adding into your plan to be able to do something else in the same time, aka it's a destination, and thus is not counted to the charging time or the total time of the plan as it's to some extent not part of the plan but something you do outside of it. I hope this makes sense to you and my description was decently clear. We are looking into making this clearer.
Kurt Ziegler
Thanks for the prompt and thorough explanation!
Note that with the current state of charging in this part of the world, an L2 charger can enable much better routes. And particularly with vehicles like the Bolt that have relatively slow DCFC rates, the time spent at the L2 charger can be significantly less than the time spent at fast chargers. So while I understand your rationale for the current behavior, it doesn't make much sense for a lot of trips in Idaho. Here's a variation on the route that demonstrates what I'm talking about.
abetterrouteplanner.com/?plan_uuid=d782e990-e751-4a42-9fcc-8f1f06f73e94
FWIW here's how I'd expect it to work: Don't exclude the time based on the charger type, but rather on whether the user has selected "Add a stop around this waypoint" for the charger location. If selected, exclude the time in the rollup. If unselected, include it.
Thanks again for the prompt response and an excellent product.
Mattias_ABRP
Hey Kurt,
I like your suggestion I will add it as a suggestion for future work. We have already added an explanation to the times when we exclude the L2 time so you will notice it easier in the future.