We have used the live setting for departure SoC for our Tesla before. Recently even though it is connected to our Tesla account, live battery % is not updating. It always shows 90% unless we change it manually every time. We’ve logged out of Tesla in ABRP and re logged in and this did not fix the issue.
I‘ve got exactly the same problem with my connected Tesla M3 - and I can‘t even turn on live SoC at the moment … See screenshot.
Please click on the gear icon behind the car. There you will get to a detailed overview of the car data. What does it show?
Dirk, this is propably a user specific issue. In that case please use Support & Feedback from settings and use get in Contact / Contact Support (first button) and we can check the details. As the original issue is solved i will close this.
Hey Eric, checked your settings, and currently, it seems as you are not using the setting for live data for the SoC. But I assume that is because you get 90% which is the value that the system would default to if it does not get tlm (info from the car). You say the car is connected to your tesla account but from what I can see it's not currently. The last time ABRP received tlm from the car was almost a year ago. Can you test connecting it again and get back to us on how it goes and if you get any errors or similar.
I’m having same problem. It seems to be connecting to my car because “my position” is correct. But departure SoC is always 90% when live data is toggled on.
I have the same problem since two or three weeks. I'm driving an Opel Ampera-e 2018. ABRP gets OBD data from Torque Pro through Webserver Upload. Torque Pro adapter status shows regular successfull uploading of OBD data.
Although the live data status says "connected" in CarPlay and the corresponding bar icon is green (and not red), the live SOC is not used. The routing always starts (in my case) with 62% SOC, although it is configured to use live SOC. Please see screenshot.
I didn't change anything in the OBD setup for months.
The only thing that comes to mind is that about two or three weeks ago I appended the additional PIDs for the future 65kWh HV replacement battery as additional lines to the PID file at the end and then imported them into Torque Pro overwriting them. It was then possible to display the new PIDs in Torque Pro.
To rule out a possible negative impact of the additional PIDs, I completely deleted the PID configuration from Torque Pro and read in the original old PID file again. The Live SOC then worked again for one day, after that it stopped working again. Very strange.
Maybe it has something to do with the fact that ABRP App can use OBD dongles directly instead of being dependent on web server upload since some weeks?
Do you have the possibility to check my transferred data in the database and tell me where the error might be, if and what data may be missing? Or maybe only Jason-ABRP can do that? (He was able to look up my problems in the database two or three years ago)
Some minutes ago I had a closer look on the transferred data: Not only the SOC, but also both temperatures, the voltage, the current and so on are outdated, although it is connected. The time of the last update is continuously counted up, so the ABRP App seems to receive data.
I cant seem to find your account in the backend. Can you share the email you use to log in to ABRP?
Hey Thomas, I've sent this forward to Bo who hopefully will be able to find the issue.
It seems that ABRP has changed some OBD PIDs for Opel Ampera-e/Chevrolet Bolt. I've added now some more PIDs to the Webserver Upload and will test it.