PM5 Inaccurate Log Times
Posted: February 23rd, 2022, 11:00 am
I noticed some significant time discrepancies between my Concept2 Online Logbook (mostly updated via USB and Concept2 Utility) and Strava. This is a problem for me because I use multiple sources for Apple Health. When the times are inaccurate, it cannot distinguish duplicate entries, so it appears as though I've worked out for twice the time.
As one example, yesterday I started a session at 9:36 AM and ended at 10:06 AM. The Strava integration shows this session at 10:17 AM. I checked the time on my PM5. It was running only 6 minutes fast, so I corrected that, but it doesn't account for the 41 min discrepancy in start times. It would still be inaccurate even if Strava used the end time (even with the 6 minutes that would be 10:12 AM).
I went back to the Concept2 Utility to look at the times directly on the USB and it's also inaccurate, so it appears the issue is with how the PM5 records the session time (at least to a USB). Yes, I know about the ErgData app, but until the PM5 allows for multiple Bluetooth connections, that's not a good solution. This problem could exist regardless of how the session data is transferred to the Concept2 online logbook (e.g. USB or ErgData).
Has anyone else noticed this and/or discovered a fix?
As one example, yesterday I started a session at 9:36 AM and ended at 10:06 AM. The Strava integration shows this session at 10:17 AM. I checked the time on my PM5. It was running only 6 minutes fast, so I corrected that, but it doesn't account for the 41 min discrepancy in start times. It would still be inaccurate even if Strava used the end time (even with the 6 minutes that would be 10:12 AM).
I went back to the Concept2 Utility to look at the times directly on the USB and it's also inaccurate, so it appears the issue is with how the PM5 records the session time (at least to a USB). Yes, I know about the ErgData app, but until the PM5 allows for multiple Bluetooth connections, that's not a good solution. This problem could exist regardless of how the session data is transferred to the Concept2 online logbook (e.g. USB or ErgData).
Has anyone else noticed this and/or discovered a fix?