1

Negative Time of travel


Avatar
Henning Schwartz

Hello,
I was driving today the opposite route of the bug reported here: abrp.upvoty.com/b/report-a-bug/why-does-abrp-suggest-a-charging-stop/
Again, the shortest route was interrupted by an unneccessary charging stop. At a certain point ABRP suggested to leave the charging stop out and take the direct route home. But then the estimated time of arrival seemed to be off. At the end I had a negative time left till my destination on the phone. But the estimated time in the display of my car was about right. That should have been including some charging at home (for what ever reason only one percent). A bit strange.


A

Activity Newest / Oldest

Avatar

Henning Schwartz

Same situation yesterday. I had a short travel, so no charging involved. But I had added a waypoint. After reaching that waypoint, I had the same discrepancy. I have the option activated, that there is a charging point at the destination.


Avatar

Mattias_ABRP

Status changed to: User Feedback

Avatar

Mattias_ABRP

Hey Henning, to further understand what has happened, is this correct? As you drove you accepted a faster route that did not include the not needed charger? After you did this the time on CarPlay and the phone started to differ by 25 min (as shown in pictures?). From what you wrote I understood it as the arrival time on CarPlay aka around 13.00 is the correct one and not the time around 12.30, is this right?


Avatar

Henning Schwartz

Hey Matthias,
that's correct, we did arrive at the time predicted on the car display. Only that I use Android Auto, I don't know if that makes a difference.


Avatar

Henning Schwartz

Today I had an estimated arrival time on the Android Auto Display that in the end was correct. But on the telephone itself it was 20 minutes to early, which resulted in a negative time again. I did not change anything during navigation. I created a bug report at 23:39.
The destination I used is a saved one with the option charger at this location activated.

Best,
Henning