Routeplanning using SoC with fixed % charging and arrival SoC% to charger don't work
- Open
- Subscribe
|
L |
Lars Volker Hansen |
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.
Activity Newest / Oldest
TomTomZoe
Hi Lars
The arrival SOC setting ist a minimum setting.
The departure SOC setting is a maximum setting.
That means if you set if to 9% and 90%, the SOC at arrival will be 9% and more, the departure from the charging station will be 90% or less.
Therefore you could not configure ABRP better that you have done, and ABRP calculates the charging stop length between 9% and 90% correctly.
Your assumption is correct, if you are using live data, it’s possible that the plan is recalculated during your trip, especially if you’ve decided to drive a different route or you are going to charge way more or way less energy at a charging station than recommended through ABRP.
If you have manually adjusted the departure SoC of a charging station, ABRP will calculate with that value.
Lars Volker Hansen
Hi TomTomZoe,
Thanks for your input.
I agree that Routeplanner will calculate a route between 9% and 90% when this is the SoC settings, but:
I would like ABRP to find chargers when SoC is close to 9% and not when it around 25-32% remaining battery SoC. That will give to many charge stops and to slow charging.
That's what I'm looking for, is optimizing ABRP using the Cars SoC much better when planning. If there is 32% SoC remaining on a long route, I will just continue driving and not stop for charging at 32%, but expect that a new charger closer to 9% SoC remaining battery will be found automatically when driving ?
There are to many charging stops in a plan from Denmark to France (2000 KM) where it plan for charging with 22-32% remaining SoC, and that's not OK, especially with Live-Data from OBD2 scanner available.
TomTomZoe
Hi Lars
In general ABRP tries to find the fastest way to drive from start to destination.
So it maybe possible that using a charging station which is nearer leads to a faster arriving at the destination than using a charging station which is located in a few more kilometers. The choice pro or cons a charging station depends also on the charging power of this charging station.
There are some settings which can limit this more or less:
- „prefer and avoid“ charging networks
- planning with charging cards
Do you use one of these settings?
Maybe it will be also helpful to share a plan where this happens, so that one can have a look into it.