4

SoC jumps back to start of route


Avatar
Henning Schwartz

If I leave a planned route and abrp needs to recalculate the route it does not take the last known SoC but the SoC the route has been started with. Even though it could know the actual SoC because the PSA Car Controller transmits it live.

A

Activity Newest / Oldest

Avatar

Bo_ABRP

Status changed to: In progress

Avatar

Matt_ABRP

We are still working on the fix, please bear with us. Most likely will be out in the 4.4.6


  • Avatar
  • E
E

Ewoud

Is this coming any time soon?


Avatar

Henning Schwartz

I have 4.4.6 now on Android and it seems to be fine now.


E

Ewoud

On IPhone it looks like to be working now too


Avatar

Frederico Lemos

Despite today's update, at least for iOS, which would supposedly fix some bugs and improvements, this situation remains


Avatar

Bo_ABRP

Status changed to: Investigate

Avatar

Henning Schwartz

Today again. I started on a route at quarter past ten. At that point I had a SoC auf 79%, reflected in ABRP and my Home Automation System, which gets the data from PSA Car Controller as well. The grey line is the mileage I traveled and the greenish line is my SoC. In ABRP the SoC dropped, while I was driving. It was not always the same value as the car was reporting but close enough. When I reached my final destination it jumped back to 79% even though the data received by the api were fresh (see screenshot). Shortly after my screenshot it refreshed the data again and then it matched. I get the impression that while a route is active, the data from the api is not read correctly.
Later on I took a deliberate wrong turn. After recalculating the route the SoC jumped back to the value of the start of that tour. Very strange.


  • Avatar
Avatar

Ewoud

Yes I have this one exact problem. When arriving at destination and also when recalculating after wrong turn.


Avatar

Henning Schwartz

Today I did a short toilet break without switching off the car or ending the route. ABRP didn't even recalculate the route. But the break was enough for ABRP to use the actual SoC which at that point after 2 hours drive was 20% higher then ABRP had calculated. Very unexpected.


Avatar

Henning Schwartz

Sometimes a longer stop at a traffic light is enough for ABRP to take the correct data.


Avatar

Ewoud

I also have this. Also when close to final destination the SOC jumps back to starting SOC. And its says its connected to trionity which shows the correct SOC. After 5 - 10 min when home i check ABRP app again and it shows the correct SOC again.


Avatar

Henning Schwartz

Here was the mismatch of data


Avatar

Henning Schwartz

From memory the app tells me the time it received new data, which was fairly recent but the SoC is totally wrong. At one point I had 100% even though I was driving an hour.


Avatar

Bo_ABRP

Status changed to: User Feedback

Avatar

Bo_ABRP

Are you seeing the right SoC level in ABRP at this point, only the new plan assumes initial SoC?


Avatar

Frederico Lemos

That’s right


Avatar

Linda

Status changed to: Investigate

Avatar

Frederico Lemos

Same with me. And the live data connected with TRONITY doesn’t actualize. Renault Zoe