OBD BLE Soc reading discrepancy Audi e-tron Q4
I’ve installed a vlinker mc+ module. The communication seems to work well except that the Soc value shown in the app is different from the one shown in the car. Is it a glitch?


I’ve installed a vlinker mc+ module. The communication seems to work well except that the Soc value shown in the app is different from the one shown in the car. Is it a glitch?


Log in to comment and vote
Comments3
Jun 18, 2025
PinnedHi @Alain,
The vehicle can display a different SoC in the cluster than the one we read from the BMS. While this discrepancy may be annoying to see, the BMS SoC is the more exact value, which is why we choose it for our calculations.
Alain
Jun 2, 2025
Without answer, as the reading difference seems to be always the same across the 20 to 90% range. I changed the correction factor into the Soc formula ( not the slope). Even if it approximative while using the car the Soc value of the car and in abrp are very close now. The only exception is when I charge the car. As the car stops charging at a fixed %, I don't care about ABRP at that time. I realized that other formulas might need a tweak (like the mileage) but it’s not really a deal. Unfortunately there is very little good info available about obd formulas….
My problem is solved
Alain
May 28, 2025
I continue checking this. It’s seems to be a measure configuration issue. There is continuously 2 to 3 % difference more in abrp compared to the real SOC value from the car.