JeroenE said:
As far as I know I've got a Konnwei OBDII dongle. Of course, with all the fake stuff out there you are never really sure, I guess. Unfortunately Soul Spy stops working sometimes. It is not responsive and I need to force quit the app and restart. Other times the dongle is not responsive. Soul Spy says dicsonnecting and connecting. Usually it'll work again after a few of these cycles. Other times I need to remove the dongle and place it back before the connection works again.
Even if the connection works again it'll take some time to get new values. I mainly drive with the "Energy and Power" screen. That will start with the speed, quickly followed by the battery energy. Then usually battery SOC and the remaining range (sometimes in reverse order). It can take several minutes before the fourth value is added.
Usually I'm streaming from my phone to the car stereo. If I'm not streaming (but listening to the radio like a savage) it still happens so it doesn't seem related to each other.
Does anybody else recognises this? Is there something I can do to avoid this?
There has been more than 10 releases of the app during the past month, one of them unfortunately introduced new communication issues for the "old souls" (2014-2019). This should be fixed from BETA release 0.1.1-4284 (the same release that corrected the SOH calculation). If you still see communication issues with this or later versions, please email the soulspy.log2019XXXXXXXX.txt file to:
[email protected]. I do not have access to the old model Soul EV for testing since I upgraded my car to the e-Soul 2020, so I need these files to find out what goes wrong.
I am wondering about the freeze requiring force close. I have never experienced anything like that for the two years I have been using different versions of this app, on different phone models. If you (or anybody else) experience this again, please email the souldata log files, along with a text explaining what you were doing; what happened; the phone model; the android version; which dongle you use, and which car model, trim and model year.
JeroenE said:
Some values are weird or wrong. For example battery.heat1_temperature will show "206 C". I'm pretty sure my battery is not 206 degrees Celsius. Even if 206 would be Fahrenheit this would be far to high. I don't think I have this value in Torque. At least not in the dashes I found on this forum years ago (and which I never changed).
Erroneous values is a likely result of the communication problems (others have reported weird DTC codes, which turned out to be caused by the communication issues). When there are communication issues, data values from the car are garbled, and values are calculated based on misplaced data from the car. If this (or similar weird data) are still displayed by the latest version, email me the soulspy.log file and mention which values you see being weird.
I was assuming that the latest release (BETA 0.1.1-4479) was working perfectly on Kia Soul EV 2014-2019 using KW902. If it doesn't, I will fix it (assuming it is not caused by a problem with your OBD-dongle).