Wrong reference consumption
For about a year, ABRP worked perfectly. I haven’t checked in the past few months, but I think the reference consumption was usually above 90% at all speeds, and ABRP would typically predict my arrival state of charge within 1%. A few days ago, I entered a route and saw that it was completely off-it suggested significantly more stops and charging. I checked and saw that the reference consumption was set to 384 Wh/km, which is unrealistic; I think it used to be around 210 Wh/km. I checked the settings and everything looked fine, so I reset the consumption and did a short trip today. I averaged 110 km/h on the highway (sometimes a bit faster, but the average was about 110 km/h), and when I got into the city, the average speed dropped. The car showed 15.9 kWh/100 km, although I think it was about 18.7 kWh/100 km just on the highway. ABRP again somehow calculated 291 Wh/km.
If I calculate manually, 92% - 13% = 79%. 79% x 0.42 = 33.18 kWh / 184 km = 180 Wh/km.
What can I do, besides disabling automatic settings and manually entering the consumption?
The car is an Opel Mokka-e, 2024, nominally 46,3 kWh net (50 kWh gross), but after one year CarScanner shows it has 42,* kWh. For connecting, I use OBD LE, although the app shows it’s connected to Enode (with occasional interruptions, which is why I switched to OBD LE), and now I see it’s also connected to Android Auto, which I don’t think I noticed before.
I was thinking of deleting the car and adding it again, but I don’t see how that could be the cause since the car is set up manually anyway.
Acc ID: 316639
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments10
Linda ABRP
Apr 30, 2025
Hi
I can see that the reference consumption says 190 now. Does that change when you are in the car and start driving?
You can try to unlink the OBD the next time you drive and see what happens with the reference consumption. Also if you don’t allow Android auto to give you live data and see if that’s where the problem is. Maybe one of these give you the wrong reference consumption?
ABRP User #316639
Apr 30, 2025
Now it shows 190 because I reset the consumption again (190Wh is the default for Opel Mokka-e). I was planning a trip, but with a reference consumption of 291, it gives the wrong suggestions.
I can unlink and re-link the OBD, but OBD it’s important to me because without OBD the data is received only from Enode, which can have a delay. Someone mentioned above, in his case delay is 3 hours, which makes ABRP completely useless (or any other app, like e-routes).
ABRP thinks you have 48% battery and sends you to a charger 150 km away, but in reality you’ve only got 13%, because the car didn’t send SOC data to Enode, and therefore Enode didn’t forward it to ABRP.
OBD is connected directly and sends data even without an internet connection.
ABRP User #316639
Apr 30, 2025
Is it possible to have "two" ABRP sessions running at the same time? For example, if it's open on Android Auto, then you close the app on your phone and open it again? It seems like it's counting twice.
Tonight I tested it in city driving, and so far everything seems fine. Tomorrow I'll try again on a short trip.
ABRP User #316639
May 1, 2025
Today I tried again and the problem has reappeared. The reference consumption is 240Wh, but the car shows 120Wh, it's calculating double again.
I don't know if it's because of Android Auto (14.3.151744), even though I reset the consumption again, drove a few kilometers, and then it was fine. It's as if it's adding up consumption from multiple sensors, although I don't know which ones or if anything can be adjusted there. I'll uninstall Android Auto and reconnect it.
ABRP User #316639
May 4, 2025
I uninstalled and reinstalled Android Auto (this time only stable, not the beta version), but it still shows higher consumption. After that, I tried driving without using Android Auto - just running ABRP directly on the phone (connected to OBD LE). Technically, that shouldn't make a difference since AA is essentially just screen mirroring, but strangely enough, that seems to be the issue.
I haven’t tested it on a longer route yet (only about 40 km so far), so I’ll see once I drive a bit more. But it appears that when I use ABRP only on the phone, without Android Auto, it shows the correct reference consumption.
Linda ABRP
May 5, 2025
Live data with SoC from AA is new so that might have to be fixed from them. Right now it’s only some car models that can have SoC from AA so hopefully this will develop and improve.
ABRP User #316639
May 5, 2025
Can I disable receiving SoC via Android Auto? In ABRP, I can see connections to OBD LE and Enode, but I don’t see any link to Android Auto, so I can’t disconnect it.
Because it's definitely an issue with Android Auto (or at least I’m 99% sure). I tested it today on my usual route, but without Android Auto (I disconnected it). There was a strong headwind today, and consumption was higher than usual, but ABRP still calculated only 174 Wh/km (without AA). Last time, without any headwind, but connected to AA, ABRP calculated 374 Wh/km and 291 Wh/km. In the meantime, I noticed that my mobile app updated to version 6.0.0 (3363) Beta, and I also updated Android Auto to 14.3.651804 (but I didn’t use it).
Using ABRP through Android Auto is more convenient for me than using it on the phone. The car's screen is much larger than the phone's.
Linda ABRP
May 5, 2025
Yes you can disable it. You have given the permission to read the SoC so you need to take that back. You can see how to do it here
https://abrp.featurebase.app/en/help/articles/6787947-live-data-via-android-auto
We have also seen it here in our test cars that SoC from AA does not work with other live data options.
ABRP User #316639
May 5, 2025
Great, thanks! Btw, just out of curiosity, where does AA get the SoC data from?
In other words, if I unlink Enode and remove OBD BLE, would the SoC data from AA work correctly with ABRP in that case? Although I don't see how AA would get SoC data in that case (without OBD or connection to Stellantis server). Because I just thinking of buying another OBD dongle and a splitter for CarScanner, just like Bjorn Nyland does.
Linda ABRP
May 6, 2025
If you don’t use Enode and an OBD and AA have permission to read SoC you get it that way. It’s not possible to use a splitter with an OBD with our app. The OBD can’t be connected to anything else when you use it with ABRP.