Used: PID(14290004) this is the true SoC but not used by the cars UI.
Correct: PID(14290378) this is the value displayed in the cars UI.
2024-02-22 -
Activity
Newest / Oldest
Samuel_ABRP
Status changed to:
Investigate
L
Lars Volker Hansen
I have 2 Audi e-trons with same problem.
Audi e-tron 55 model 2023
Audi e-tron 55 sportsback , model 2022
Both have the same problem, that I get data via my Obdlink cx dongles, and is an ABRP premium user, but the SoC values shown in the ABRP app are different than via displayed SoC in the car display and the SoC shown in the MyAudi aop.
I hope you fix this soon, since it’s very difficult to use ABRP between Denmark and France/Italy if I can’t rely on the data un ABRP.
Thanks for the detailed info! First of all, we do not seem to have enabled OBD for the e-tron 50, have you selected a different car model to get it to work?
Second, our SOC read definition is
"soc": {
"equation": "A",
"minValue": "-5",
"maxValue": "105",
"type": "Number",
"command": "0322028C55555555",
"ecu": "765"
}
and I cannot match that to what you write above. Can you explain more?
I have selected the Audi e-tron 50 (GE) and it’s working fine (see attachment) with OBD data, besides the different SoC values in ABRP and in the car.
I got the “PID” values from Carscanner Pro, but it might be some internal values in that app. It’s also noted as “ {[01.ENG] HV Battery SoC Display}”.
But I can see that the ABRP values match the Real SoC in Carscanner and not the “displayed” value in the car. Anything I can do to help?
Activity Newest / Oldest
Samuel_ABRP
Status changed to: Investigate
Lars Volker Hansen
I have 2 Audi e-trons with same problem.
Audi e-tron 55 model 2023
Audi e-tron 55 sportsback , model 2022
Both have the same problem, that I get data via my Obdlink cx dongles, and is an ABRP premium user, but the SoC values shown in the ABRP app are different than via displayed SoC in the car display and the SoC shown in the MyAudi aop.
I hope you fix this soon, since it’s very difficult to use ABRP between Denmark and France/Italy if I can’t rely on the data un ABRP.
Best
Lars
Bo_ABRP
Status changed to: User Feedback
Bo_ABRP
Thanks for the detailed info! First of all, we do not seem to have enabled OBD for the e-tron 50, have you selected a different car model to get it to work?
Second, our SOC read definition is
"soc": {
"equation": "A",
"minValue": "-5",
"maxValue": "105",
"type": "Number",
"command": "0322028C55555555",
"ecu": "765"
}
and I cannot match that to what you write above. Can you explain more?
Thomas Baes
I have selected the Audi e-tron 50 (GE) and it’s working fine (see attachment) with OBD data, besides the different SoC values in ABRP and in the car.
I got the “PID” values from Carscanner Pro, but it might be some internal values in that app. It’s also noted as “ {[01.ENG] HV Battery SoC Display}”.
But I can see that the ABRP values match the Real SoC in Carscanner and not the “displayed” value in the car. Anything I can do to help?
Bo_ABRP
Status changed to: In progress