Voters 1
1
ABRP shows wrong SoC using Tronity Live interface
- Done
 |
Kewin Stoeckigt |
Hi team. In the last few weeks I noticed that the SoC via the Tronity Live Interface doesn't update properly. Tronity has the correct SoC. When I start planning, I have the right data, but while I am driving, and lets say the car uses less battery, the SoC is not updated. In some instances I had up to a 50% difference in SoC. Again, once I stop the route guidance, I can get the new SoC.
Activity Newest / Oldest
Kewin Stoeckigt
Thanks for the info. I believe my car has version 3. I'll check to see if it works now. It worked very well until about 4 weeks ago.
Bo_ABRP
Status changed to: Done
Bo_ABRP
We found and fixed a bug yesterday when driving with ABRP without SoC refreshes from live data, which caused what you observed. Probably your Tronity connection does not update while driving, something which I think is the case for pre-3.0 firmware ID.x cars.
Kewin Stoeckigt
Hi there. Just tested it and it worked up to one point. It was fine for over 250km and a used battery charge if 79%. I was supposed to stop an charge but skipped that one as I know the next few chargers. It recalculated but then the shown SoC jumped to an arbitrary 59% even though I was down to 34%. It then never recovered. Tronity had the right %. I run version. 3. Unused abrp through android auto on a pixel 6 pro. In case that helps.
Bo_ABRP
Are you still on pre-3.0 firmware in your car?
Linda
Status changed to: Investigate