The SoC at departure seems not to match the live SoC for my Tesla. See attached screenshots.
I checked the error with our second vehicle:
The initial Car SOC from live data is 26%. (screenshot #1)
I enter a destination (screenshot #2), the departure SOC is still correct there with 26%.
Then I press the round blue button for planning the route, and the calculated route starts with 26% SOC (screenshot #3). That't correct.
But why is there a different behaviour using different cars? Is that random?
The second car (Corsa-e) has BLE OBD connection, the first car has OBD from TorquePro.
Unfortunatley you can't add a picture by editing a existing post at Upvoty :-(.
So I deleted all and post them again in the correct order.
I just used the ABRP Website V4.2.12 (1157) to calculate a trip.
The initial Car SOC from live data is 78%. (screenshot #1)
I enter a destination (screenshot #2), the departure SOC is still correct there with 78%.
Then I press the round blue button for planning the route, and the calculated route starts with 36% SOC (screenshot #3) and therefore lets me charge in between, which would not be necessary with a departure SOC of 78%.
Can you please check this issue?
I cannot seem to find any ABRP account associated with the email address you use on here, thus I cannot check the connection for your vehicle.
However, as can be seen in the first screenshot, we haven't received data from your car for the past 49 minutes and therefore it could be outdated.
What live data option are you using for the car?