|
Donald Moore |
I'm running into many cases where I want to change the calculated charge SOC % target to a higher amount. As an example I have one stop that says charge to 42% but I want it to be 100% for some specific needs. When I run the route again it goes back to 42%.
Activity Newest / Oldest
Bo_ABRP
Status changed to: Done
Bo_ABRP
We did fix a bug regarding this yesterday, so it should be working consistently for you now. Let us know otherwise!
Donald Moore
Gonna have to call you ORKIN cause you kill bugs! Everything on my side looks good. I first killed cookies. After that I created a new trip and did a bunch of SOC mods with 100% success. Finally I opened some previously created trips that had "pending" SOC changes and they "self corrected". GOOD JOB!
papymomo
Effectivement, ça a l'air de mieux fonctionner
Donald Moore
Just another example...I think this is really a significant issue that now seems prevalent in multiple plans. This is a simple route where I want to charge to 100% because I know the first top is cheap ($0.14/kWh) and there is a lack of charging options in and around Roswell NM. (I think that is because all the Alien spacecraft use them. LOL)
abetterrouteplanner.com/?plan_uuid=722d5d91-b0e9-47fe-b24b-13f3b79491c2
Katya_ABRP
Status changed to: Investigate
papymomo
J'ai remarqué la même chose, mais pas sur toute les bornes. C'est assez étrange. On peut effectivement tricher en modifiant le Soc à l'arrivée suivante.
abetterrouteplanner.com/?plan_uuid=d8e9aabb-a52b-410f-b424-decc7d475cdd
Pae exemple : je peux modifier la charge à Diges (IE Charge), mais pas à La Réserve (Ionity).
Donald Moore
Translation..."I noticed the same thing, but not on all the terminals. It's quite strange. You can actually cheat by modifying the Soc on the next arrival."
Yep...that is what I have done in some cases.
Oui... c'est ce que j'ai fait dans certains cas.
Katya_ABRP
Status changed to: User Feedback
Katya_ABRP
Hi Donald,
Please provide a link to this plan and specify at which stop you're attempting to edit the charge level.
/Katya
Donald Moore
Good morning from the US! This is not the only time I've run into this situation but the latest. It is the last Tesla charge stop at Benton Harbor where I want to make a 95-100% charge before getting to my destination after that.
abetterrouteplanner.com/?plan_uuid=0f8a5ebb-35c8-4836-a8b8-2623617e5a47
In the past I've done some work arounds such as changing the desired SOC at the following stop and played with numbers to get the desired effect. I've also cleared cookies and such on multiple occasions. BTW, this has occurred on my MacBook Air through multiple OS upgrades.
I think you have a great product and on road trips I run it side-by-side with Tesla Nav and I'm impressed on how it compares to it. Sometimes Tesla Nav suggests something slightly better for the route than ABRP and other times the other way around. Keep up the good work!
Katya_ABRP
Thank you for the link!
Agreed, this looks strange. It seemed at first as the arrival SoC would prevent a higher charge at the Sc in Benton Harbor but removing that did not correct it.
Increasing the maximum charge level did not fix it either. We'll have a closer look at this!
/Katya
Katya_ABRP
Update: It actually seems like removing the arrival SoC at the final destination, increasing the max charge AND specifying the kW of the charger in Benton Harbour did the trick. See this version of the plan; abetterrouteplanner.com/?plan_uuid=9bceb3cc-fa1a-4fe7-85dc-ac3bb6b50ea1
Looks a bit like we're losing the kW of a manually added charge stop (recognised as charger) when resetting the edits on the waypoint.
/Katya
Donald Moore
Certainly there are times to adjust the arrival SOC target. As an example, you go to a hotel with the hopes of an operational charger but find it doesn't work. You might want to pad the arrival in case you need to go to a different charger after your stay. Sometimes I want to adjust the SOC leaving a charger because while I don't "need" more that stop will be for a meal so adding charge time is just helping in planning the route. Thanks for looking into this!
Donald Moore
Certainly that seems to work but take a look at the very first stop at Santa Rosa. Try to adjust the departure SOC to 90% and see what happens. When I do that you can see the change in the stops setting but it still only calculates a 76% SOC. Additionally, the next stop at Amarillo is originally 10% at arrival and remains 10% after attempting the edit at Santa Rosa. It is like the program is ignoring the edits and sticking to its own plan. LOL Computers make fast, accurate mistakes.