Related
Options

Pool swimming: Time data is just *weird* beyond description!

8287926
2 months ago

I really don't know how to put this into words so I'll rely on screen grabs.

In this first image from a while back, the time data on the x-axis makes sense. 8 mins 20, 25 mins, 41mins 40 etc. I can easily map where I was in my lap swimming against how long I'd been going.

Recently, though, my data is seriously screwy. The x-axis data now makes no sense at all in terms of its hours/minutes/seconds display. If anyone has come across this and knows what causes it and fixes it, I'd love to know!

  • 0 2 months ago

    There are couple of similar cases reported on the forum. I do not know what causes the corrupted data, but I do know that trimming slightly the activity fixes it. You may want to send the corrupted FIT file of the activity to the Support for investigation.

  • 0 1 month ago in reply to trux

    Thanks, I'll look into doing that!

  • 0 1 month ago

    As far as I can tell, this intermittently occurs when using auto rest. It's not always predictable, but happens sometimes and sometimes not.

    I haven't determined exactly what causes it, though the watch logging erroneous extra laps seems to be a common factor. It's definitely indicative of some sort of uint64 overflow - maybe something to do with the watch taking the difference between the activity start and end times causes a wraparound below 0 on an unsigned int?

    Try turning off auto rest and see if that helps.