The data being shown under My Drives has been producing incorrect distance travelled data. Today I drove to work (12.5 miles) but My Drives shows the distance as 22 miles. The journey map also seems to show me travelling directly back to my starting location. Yesterday, for the same drive it shows as having been 34 miles. I am driving a Skoda Enyaq with an OBD dongle and also Tronity as a second data source. I'm guessing that this is an issue related to the data ABRP is receiving from Tronity?
Similar thing happens sometimes with my logs.
I use ABOR to transfer the data to ABRP.
But ABRP seems to log the GPS data from AndroidAuto / my phone AND from ABOR (second logging phone).
There are very strange tracks.
Using the AA GPS data for navigation is fine.
But ONLY recording GPS data from the source that gives the latest OBD data instead of using multipe inputs would be the solution.
I think I may have gotten partly to the bottom of this. My last two or three drives have shown accurately, and I think it is because there is definite order in which to shut things down. As long as the car is at a full standstill, handbrake on, and the 'ignition' off - which in the Enyaq is achieved by unfastening my seatbelt, then the drive seems to record properly. If however I was to turn off ABRP, disconnect Bluetooth, or unplug the OBD while the car is still 'running', that is when it seems to go awry at times. Now that I know that to be the case I can happily make sure that I just follow that order all the time.
Hi Katya, I'm pretty sure that I would have had ABRP running at the same time as I actually always use it as a way to view the current charge percentage. I had a similar issue this morning. The drive logged, the travel time was correct as was the starting and finishing locations, however it is once again showing it as a 22 mile drive, when it is in fact a 12.5 mile drive. But, you are right that sometimes it seems to be completely correct, so I'm not sure if it is an issue with the app, or the car transmitting location data.
I've checked the logged drives that day and I can see that the first drive was logged inaccurately but the 2nd one was logged successfully.
As we can only log data via OBD when the ABRP app is in active use, (else no Bluetooth connection) can you recall if you did use the ABRP app actively during that drive?
Currently TRONITY states the Skoda ENYAQ is supported with the comment; "ENYAQ: Recording of charging sessions only" - thus yes, relying on TRONITY for logging driving activities would not work.