Skip to main content

Recorded speed varies wildly and energy usage way too high

Bug Reports

Since the last few weeks it seems that ABRP is recording some strange speed reading during my daily trips. In turn it seems that this is influencing the energy usage predictions, which were spot on before, but are now often more than 10% off.

When looking at the recording of one of my daily trips, I see that the speed on the highway fluctuates wildly between the 100km/h I was actually driving and around 50km/h. Also the reported usage for the trip is shown as 1042 Wh/km.

Other trips show more realistic energy usages in the 150-180 Wh/km range, but still show the jittery speed graph. There are also a few trips that simply report 0 Wh/km which also seems suspicious.

The issues with the speed seem to have started on March 14. Earlier trips show a much more consistent speed on the highway.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Michiel Visser ·
Status: Awaiting Clarification4 comments

Log in to comment and vote

Comments4

  • Katya S. changed status to Awaiting Clarification
    Team•

    May 15, 2025

    Pinned

    Hi @Michiel Visser,

    What live data methods are you using when this happens? Android Auto? OBD?

    If you’re using Android Auto live data, could you try temporarily disabling it and check if the reports become accurate again?

    You can read about how to do so here; Live Data via Android Auto

    • Michiel Visser

      •

      May 15, 2025

      I have been using OBD for live data and I have not specifically set up live data through Android Auto. However, I see that the ABRP app has permissions to access the car information so I will turn that off and check if it improves the situation.

    • Michiel Visser

      •

      May 19, 2025

      It seems that disabling the car information has fixed the problems with the speed being recorded incorrectly. However, now it seems my OBD information is also not recorded anymore. The recorded SoC is just constant for the whole trip, and power/temperature are not recorded anymore.

      During the trip it seems like the OBD connection is working correctly. I can see the SoC change while driving and the power/temperature information is also shown on my phone.

      In the recording the SoC is only updated at the end of the trip, presumably by my API data provider, which sends SoC and odometer at the end of each trip.

    • Michiel Visser

      •

      Jun 6, 2025

      @Katya Skog It seems that the OBD data recording has been fixed in one of the latest updates. I can now see the correct SoC, power and temperature information for each trip again.

      I’m still seeing some issues with the calculated energy usage for trips. Most of the time it just shows 0 Wh/km, which is incorrect. I have determined that disabling the API based data provider seems to fix the issue with the energy usage.

      My API data provider only sends a single update of the SoC and odometer at the end of a trip, approximately 5 to 10 minutes after the car has been turned off. The intention was to have correct SoC information in ABRP even after drives where ABRP was not used during the drive. Is it a bug that the energy usage gets set to zero when using the API, or am I using the API incorrectly?