Bad Behavior Leaving a Charging Stop

As we left a charging stop ABRP got into a loop. It presented a message about the charging stop (we were a bit behind schedule, I was driving in the parking lot and focused on driving & wanting to know which way to turn coming out of the lot, so I don’t remember exactly what the message said) — I think ABRP may have thought that I wasn’t at the charging station and was navigating away before charging or something like that.

In any case, it presented me with a warning that included an option to do something like cancel / ignore and I selected the option that seemed like it would have dismissed the warning and allowed me to proceed on the route. It didn’t, instead the warning popped up again almost instantly. I again chose the option that I thought would dismiss the warning, and again ABRP popped in right back. This continued for several iterations (which I realize is in indication that I might be insane…) until I canceled the route & replanned the trip. That cleared the loop.

I think that this happened right after updating to 6.1.0 (3491) while we were charging. I think we had navigated to the charging stop as the end point of a route. So we were starting on a new route. I don’t remember the display clearly enough to be able to say whether or not ABRP had picked up the post-charge SoC from the OBD2 dongle yet.

I’m not sure if I had the presence of mind to send a bug report in the midst of this, but if I did it would have been at about 16:15 PDT (GMT-8:00) on the 19th of July.

As I see it there are two “real” problems here (assuming that the initial behavior might be a “one off” triggered by a combination of planning a new route and starting to drive before ABRP had current position and/or SoC data from the ODB2 connection):

1. The looping, ABRP shouldn’t be repeating the same warning over and over after the warning has been dismissed. If the warning is something has to be addressed before ABRP can continue, then the warning should make that clear & indicate what needs to happen.

2. The options to respond may be unclear. But there should be a way to dismiss an alert. Even if that means that ABRP has to restart to proceed or to say “I need data to proceed, please wait”. The behavior was borderline dangerous since I needed to be attentive to my surroundings in the parking lot and I needed to know what to do when I exited the lot. It would have been better to get a pop-up that blocked the screen with a message like “waiting for ODB2 data” or “currently unable to calculate arrival SoC” with a clear “dismiss” button. Anything that didn’t have ABRP causing a repeated distraction.