Routeplanning using SoC with fixed % charging and arrival SoC% to charger don't work

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/report-a-bug/routeplanning-using-soc-with-fixed-charging-and-arrival-soc-to-charger-dont-work/
β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”
I have an Audi eTron and uses OBD2 scanner for live-data, which works great, but when I'm planning a route from e.g., Denmark to France I set my charging level in the car to 90% SoC when charging and don't change that during the trip due to time used at charger.
I also have set SoC arrival at charger to 9% in the app.
When I'm planning a new route the ABRP app or website don't use these informations to maker a route where I always start at 90% from each charger, and then direct me to a charger where estimation is close to 9% SoC at arrival.
Each charging point shows an arrival SoC from 9-34% and each Charging SoC when leaving shows from 70-100%

Isn't it possible to make a plan where a fixed SoC e.g., 90% when charging is used and where it only searches for chargers around the arrival at charger % (in my case 9%) is used, and then of course a higher % at arrival at charger if no desired charger from my list is in the area - hence - charge earlier at route.

I can adjust manually for each charger today, but then it recalculates the route for every change, but not to a better result.
Since I use live data via OBD2 reader, I expect that the live data is used (SoC) and a plan is adjusted on the go if needed, but using the arrival at charger and depart from charger SoC % ?
Is there a way to do it that I haven't found in the app/Apple Caplay, or is it an error in the ABRP app ?
It's to time consuming today, and the result of the route plan isn't good at all for a long route.

Where does this happen?
-
ABRP version number (found at bottom of settings menu)
-

Please authenticate to join the conversation.

Upvoters
Status

Rejected

Board

πŸ› Bug Reports

Date

Almost 2 years ago

Author

Lars Volker Hansen

Subscribe to post

Get notified by email when there are changes.