|Ömur Can Kayaokay|
Hello, for the route, when I constrain and use 4 as minimum charger stalls desired, I get a 13h51m route, but when I free-up the requirement to 1, I get a longer 14h30m route. Please check the routes below: abetterrouteplanner.com/?plan_uuid=f9567034-5d4b-43cd-9790-c066fca36292 abetterrouteplanner.com/?plan_uuid=56f329f2-6a9d-430a-8540-707998d2226d
And same applies to charger arrival SoC options, if I allow the ABRP to go lower down to %10 instead of %20 or higher for e.g. I get a longer route instead of shorter. Also the same with max charger SoC. If I allow it to be charged more, the ABRP does not say that "You have said that you can charge up to %100, but you don't need to, you will arrive faster if you charge less". Due to these kind of logical errors, I cannot trust ABRP fully and it makes me spend quite a bit of time to shape my route.
These kind of things happen sometimes, not always, but they do happen.
My logic is, the more you constrain, the longer it gets. More free it is to calculate, shorter it would get. Or should.
Actually, yes, it is still strange. For some reason, I am getting a longer route with 1 instead of 4 stated as minimum charging stalls.
Looking at your plans today, it seems to be behaving correctly - only requiring 1 stall made the plan faster (but obviously more risky). Do you still see the problem you describe above?