Check Data deleted all sessions of Track Day
Posted: Thu Sep 13, 2018 7:28 am
tldr version: Sitting in pit lane near Start/Finish line corrupted a lap recording. Check database deleted all OBD2 and GPS data for all session over the whole day. No backup.
Long version:
After my last and for me most important track evening of the year, I tried to back up the evenings' data before driving home.
I would usually send myself the data, then back up the database. This time for some reason (tired), I tried to back up the database, then send myself the lap data. I pushed the icon in the Lap List that looks like the Local Backup button in the Databases screen. I now understand that this is actually the Check Database button.
It immediately, with no prompt, started checking the database. It found some corrupted data and deleted all the GPS and OBD data for the day. Multiple laps across multiple sessions. I know that there was nothing wrong with most of those laps, because I had been looking at the data and video between sessions. All that remains is the lap times and the splits.
There does not seem to be any backup made before it deleted.The most recent System backup is from the 2nd of September, and does not contain the data.
So what caused the corruption?
There was one weird 715827:42.85 lap which got recorded when we are forced to wait in the pits, which is very close to the start line. Variations in GPS position can trigger a lap when you are sitting near the start line, as I reported in the Beta testing thread "New Custom Tracks - Can't edit because recording starts" . I think this is the one that caused the error, I got a message, something like "Current lap had data problems, invalid lap.... ...please contact Author" error message (I did not screen shot it and I can't see the screen very well with my driving glasses on). Allow Low Speeds is OFF.
It does not make sense that one bad lap in a late session should corrupt multiple sessions of the whole track day?
As I was leaving the track (they close the track and we drive out over the starting lanes), HLT went into crazy mode like I reported in the beta thread - recording starting and stopping with several 715827 second laps. Again, "Allow Low Speeds" is OFF, I think GPS disturbances when stopped or moving slow near Start/Finish lines can also cause this.
Long version:
After my last and for me most important track evening of the year, I tried to back up the evenings' data before driving home.
I would usually send myself the data, then back up the database. This time for some reason (tired), I tried to back up the database, then send myself the lap data. I pushed the icon in the Lap List that looks like the Local Backup button in the Databases screen. I now understand that this is actually the Check Database button.
It immediately, with no prompt, started checking the database. It found some corrupted data and deleted all the GPS and OBD data for the day. Multiple laps across multiple sessions. I know that there was nothing wrong with most of those laps, because I had been looking at the data and video between sessions. All that remains is the lap times and the splits.
There does not seem to be any backup made before it deleted.The most recent System backup is from the 2nd of September, and does not contain the data.
So what caused the corruption?
There was one weird 715827:42.85 lap which got recorded when we are forced to wait in the pits, which is very close to the start line. Variations in GPS position can trigger a lap when you are sitting near the start line, as I reported in the Beta testing thread "New Custom Tracks - Can't edit because recording starts" . I think this is the one that caused the error, I got a message, something like "Current lap had data problems, invalid lap.... ...please contact Author" error message (I did not screen shot it and I can't see the screen very well with my driving glasses on). Allow Low Speeds is OFF.
It does not make sense that one bad lap in a late session should corrupt multiple sessions of the whole track day?
As I was leaving the track (they close the track and we drive out over the starting lanes), HLT went into crazy mode like I reported in the beta thread - recording starting and stopping with several 715827 second laps. Again, "Allow Low Speeds" is OFF, I think GPS disturbances when stopped or moving slow near Start/Finish lines can also cause this.