SOC via ODB2 is not the same as displayed on dashboard!

[lbaron]

Hi everyone.

MG5 PFR Exclusive

I just got an obd scanner - was hoping to use with ABRP.

ABRP default SOC reading is consistently 6 or 7% less than displayed on the dashboard.

Downloaded Torque to try with that, and lo and behold it also reads the same as ABRP.

So either the official dashboard reading is wrong, or the OBD reading is wrong.

Can anyone help me troubleshoot this please, it's a tad worrying.

Many thanks

 

[mg4mc]

From what I remember, there are two different SOC values available over ODB. One looks like the absolute value taking the total battery capacity including the reserved capacity at the top and bottom into the calculation. The other without those reserved values and reflects the usable SOC and matches the car value (within 1% iirc).

 

[lbaron]

From what I remember, there are two different SOC values available over ODB. One looks like the absolute value taking the total battery capacity including the reserved capacity at the top and bottom into the calculation. The other without those reserved values and reflects the usable SOC and matches the car value (within 1% iirc).

Super thanks so much, sounds very plausible. Any idea how to access the other value in Torque, or any reference to this anywhere. There's only one SOC value in the torque profile I downloaded.

 

[mg4mc]

Sorry not off the top of my head, I'd have to go out run Car Scanner again - it shows both values - and see which PID is which.

 

[lbaron]

Sorry not off the top of my head, I'd have to go out run Car Scanner again - it shows both values - and see which PID is which.

Ok no problem, I couldn't get car scanner to show anything useful. Mind sharing the settings you use to show all available info?

No worries if you can't I appreciate the steer

 

[mg4mc]

I should caveat my response by saying that it is on an MG4. I hadn't realised this post was on the MG5 forum