Android Auto * (Anode + OBD) = Double Consumption
Does ABRP still report double consumption if Anode and an OBD are connected, but you also give the ABRP mobile app permission to read vehicle data through Android Auto?
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments4
Linda ABRP
Jul 21
Hi
No should not get double consumption. I don’t know which of your cars you refer to but if you click at Live data you can see which connection provides with which data. I think we mostly get SoC from Android auto.
ABRP User #316639
Jul 22
Hello,
I have three data sources linked: a BLE OBD + Enode + Android Auto. With all three enabled about a year ago the app calculated a calibrated reference consumption of around 400 Wh/km for Opel Mokka-e, which is clearly unrealistic. The real value should be around 190-210 Wh/km.
I disabled sharing from Android Auto and after that everything worked correctly. I’ve now enabled Android Auto again to check whether this issue has been fixed in the meantime, but I’m currently getting a CRC of around 250 Wh/km, so I’m not sure the problem has actually been resolved.
Linda ABRP
Jul 27
I have sent this to my colleagues so they can look at it. I will get back to you.
ABRP User #316639
Jul 28
Thanks. I just checked and I see that the reference consumption has dropped to 249 Wh/km. That's still quite high, but what surprises me is that it's actually decreasing. Before it only ever went up. It might turn out that 249 Wh/km is actually a realistic for the Opel Mokka Electric. :)
I'm thinking of resetting the reference consumption in the app and disabling the Android Auto connection with ABRP, so it only receives data from the OBD and Enode. That way I can see whether the reference consumption changes. I think it will, to somewhere around 190-210 Wh/km.