Report a Bug

I have an Audi e-tron 55 Quattro 2023 model and an Audi e-tron 55 Sportsback Quattro 2022 model , and uses ABRP Premium together with an OBDlink CX BLE for live data which is supported in the ABRP app.

I use the latest version of the ABRP app - 4.7.5 (2633)

There is a big difference in the SoC shown in the ABRP app compared to the correct SoC shown in the car as well as in the Car Scanner Pro app. The Car Scanner Pro app shows in real time a lot of data-points from the car.
Most things works fine, but since the SoC used in ABRP is wrong it results in the car running out of electricity while driving whilst the ABRP app still shows that the SoC is sufficient to reach a charger.

The gross battery level in an Audi e-tron 55 Quattro is 95 KwH (Brutto) , but the useable part of the battery for driving is only 86 KwH (Netto), so it makes a big difference which level you use, and I believe that you Read/use the 95kwH instead of the correct 86 KwH, and that have a big impact in calculations and consumption.

As you can see in the attached fotos:
MyAudi app shows e.g. 3% 14 kilometres left in the battery.
Car Scanner Pro shows that the Battery SoC Display is 3.5% (the correct useable battery level), but Battery Charge level, Battery SoC and SoC true all shows 11% which isn't the useable amount of battery but the total gross volume of the Battery.

The MyAudi-app shows the same SoC and remaining kilometres as the actual display in the Audi car.

I have attached photos from 3 different battery levels, so you can investigate, since ABRP is reading and using the wrong data-point.

Please fix the problem, so you read and use the correct data-point (Battery SoC Display - 3.5%)

I believe that your data model should be correct when you calculate the route if the SoC level was correctly read and used, but since the SoC read is incorrect and used in the ABRP app everything goes wrong, when the battery is low. It's almost 8-9% different, and the consumption is due to that also wrong.
That results in that when a route plan is calculated, too many charging stops are used, since the consumption in the car is mis-calculated.
Right now I have to set the arrival SoC to charger to 15-20% to avoid the car running out of electricity, which again leads to too many charging stops when making a plan, hence - travel time will also be much longer than in real life.

I know that there is another bug report from another user, but I tried to give you more data, so you can see the problem.

In my case I would have been out of electricity with many % / kilometers if I wasn't aware of the bug (wrong read data-point) in the ABRP app.

I look forward for an update with a fix and please reach out if you need more information or data from me.

Lars