SOC from Android Auto MG4 EV Urban
MG4 EV Urban Comfort Long Rang Android Auto SOC
When I try to navigate using Android Auto in ABRP, the state of charge (SOC) is passed from Android Auto to ABRP. The problem is that when the SOC is at 75%, ABRP receives a reading of 751%. Please fix this.
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments15
Samuel_ABRP
Nov 3
PinnedHey, this is fixed now. When we detect values > 100, we treat them as value / 10, so the SoC should look correct fro you. We persist that in a property, so if we detect that once, it will be used until it is deactivated again. If eventually the manufacturer fixes it, it can be toggled off again in the AA settings. Will be available in the next beta release, probably end of the week. Installing the ABRP Beta version
ABRP User #2789574
Nov 17
The problem is that when a two-digit value is reported, it's then divided by 10. Which is obviously wrong!
Samuel_ABRP
Nov 17
Hey, did you actually try it? This case is handled. Once we detect we have to divide by 10 we do that forever, until you turn it off again in settings.
ABRP User #2789574
Nov 17
Yes, I tested it. The problem is that Android Auto, for example, reports 87.6% as 876% and 87.0% as 87%. This means that ABRP experiences the following jumps: 87% -> 8% -> 86%
Samuel_ABRP
Nov 17
We either divide by 10 or not and that is persisted, so if the value drops later on, that means the vehicle sends the data wrongly (what it already does now, we just make up for it). I’m not sure we can handle both cases at the same time, if the car jumps between *10 and the actual value…
Samuel_ABRP
Nov 17
I can add another workaround, that the value is not divided by 10 for integer numbers, but that sounds pretty shaky. As its broken anyways already, i will add it, but i can’t guarantee, that it will work forever, depending on what future vehicle updates do.
ABRP User #2789574
Nov 17
Is it only necessary to divide by 10 if the data shows a percentage greater than 100%?
Samuel_ABRP
Nov 17
That will break, when you go below 10% if we just make it based on that
Samuel_ABRP
Nov 17
I had a more detailed look at this again. We cannot fix every case that goes wrong here, but at least all the cases where you start with > 10%. For cases where you start below 10% you might start with a higher value, until an update with a normal value comes in. we will then continue from that lower value. So only when you start driving below 10%, you might see issues. This is the best we can do for this case. Please also report it to MG so they can fix it.
Samuel_ABRP
Nov 3
Hey,
nice to see more cars are getting SoC in the car via AA. Unfortunately this is not a bug on our side, the car manufacturer passes the data wrongly to Android Auto. But we’ll check if we can add a workaround, to detect this, so we can handle it in a better way.
ABRP User #2789574
Nov 3
Great, thank you so much!
Mahde - ABRP
Nov 2
Hello @ABRP User #2789574,
Please share a screenshot of this error to us.
ABRP User #2789574
Nov 17
The problem is that when a two-digit value is reported, it's then divided by 10. Which is obviously wrong!
Linked to Bug soc, donnée en direct
Linked to Wrong SoC from Android Auto