My car suddenly showed 3552% battery SoC. I unlinked & relinked the obd connector & it's still erroring.
2022 Mini Cooper SE, veepeak obdcheck ble+ on a pixel 4a5g.
I tried disconnecting the reader & reconnecting it, toggled Bluetooth on & off, toggled the car on & off. But every time I connect it the app has a "connected, but bad telemetry data" error, & the SoC is well over 3550%.
I just checked and we did not modify anything related to OBD commands here. So there is one thing you can do to help us. Please get into the car and connect to it, so you see the wrong value. Then go to settings and scroll down to support & feedback, select the first option which is either contact or give feedback. It should ask you to upload usage data from the app, click yes so it will attach the latest OBD responses you got from the car. Then open the report with your mail client, for example gmail and it should prefill the mail with some text. Send that mail to email@example.com and I'll check your data.
Thanks - but when I went to try connecting, the obd reader would not connect to the car at all. Then it wouldn't connect to the phone via Bluetooth, so I ended up resetting all Bluetooth connections, pairing (took maybe 10 tries), connecting, then deleting the saved vehicle in ABRP, creating a new one, & connecting the reader (which took another 5 or 6 tries). It would establish a bt connection but not connect, or connect without getting all telemetry values. Finally it did connect successfully & the correct SoC was reported - of course it's not calibrated anymore.
Unfortunately I was in the middle of a trip when I first noticed this, & the actual SoC was not enough to get to my destination, but the app thought there was plenty - 3000% of 114 miles is enough to get anywhere without stopping to charge. I'm glad I wasn't blindly relying on ABRP navigation or that would have been trouble! If it happens again I'll be sure to pull right over & send a bug report.
This keeps happening, & now I can no longer connect my odb device. The debug uuid is above. Hope this can get figured out! My phone keeps shutting down from overheating when the app is used for more than 30 minutes!
The overheating issue should be gone since 4.2.6. What can still happen though is that the phone get's really hot from inductive charging and wireless AA. Although this combination looks really nice together, it causes a lot of heat on the phone, even without ABRP running. So with navigation apps together this will heat up the phone quite a bit. What is your setup for running AA?
We will check the OBD logs soon.
Just checked your data, looks like we get some timeouts on the can bus for some commands during connection. However i can also see data and it always looks like reasonable data, for example soc 80%...
As the veepeak is not a fully supported device by us (according to the list of tested devices from www.iternio.com/abrp-obd ), i would advise to try another dongle, for example the Maclean MCE200 is pretty cheap in Europe.
It could be that the data inconsistencies come from the dongle too: We also had reports from other dongles, that did not filter the responses from the can bus correctly which resulted in a total mess of the data.
As we do not list the Veepeak and we do not have one for testing i can not offer you any workaround so far, but would propose to try any of the other dongles. I use the MCE200 and the USCI-2000 and both work flawlessly even on 6h trips.
I once had a Veepeak dongle myself, the cheap blue BT only version für 10$. It worked most of the times, but reset every now and then and i had to replug it to get it to work again. This is the reason we test some dongles ourself if they work as expected and recommend them to the users. We can and will not offer extended support for other dongles, unless it makes sense for us (for example if we get some for testing and we think they are of good enough quality).
My car does not have Android auto, & my phone does not have wireless charging - in fact, it's on a vent mount so there's air conditioning blowing directly on it most of the time, but that doesn't cool it down enough to prevent overheating.
In that case please go to settings, scroll down to map settings and select ABRP map as map type and let me know if that helps. If the phone however even gets hot when the AC is on, then i think there is something wrong with your phone. The air vents should cool down the phone so much, that it can't heat up, even when the phone is under full load. I did that a few times too, to cool it down when it was getting hot from the sun. However my phone never got so hot that it shut down during a drive.
Btw which App Version do you use? With 4.2.6 i think we introduced a new version that drastically improves performance. So earlier versions heated up some phones more, but if you are on latest version this should be fixed. Latest is 4.2.8.
I've got 4.2.8, & the phone overheated again today even with the ABRP map setting. It was in the low 70s inside the car & out, & the phone wasn't even plugged into the USB port.
This happened about 20 minutes on a highway (65mph).
Could you please open a separate issue for the temperature problem? It's hard to keep the overview if multiple issues are mixed into one.
Did you try another OBD dongle yet, to see if it improves the situation?