Invalid power data, if export via PM5/ErgData/logbook

[roesti]

Hi everyone,
Silence reader within the last two years. I highly appreciate the valuable assistance of this community.
After almost 40 years of cycling history, my wife and I got infected by c2 virus about two years ago. We started with rowing and added the Skierg about 4 weeks ago to our fitness equipment.

Since yesterday, all the data from SkiErg and RowErg, either via direct Strava/Garmin Connect sync or via FIT-export from the logbook and import creates flawed/corrupted data.

Specifically, any power-data is complete nonsense and not usable.
If I check the Fit-files, speed is mostly at >100 km/h and power values >2000W (screenshot example attached).

This is true for both of our accounts (my wife and mine). Iphone 12 and Iphone 13 in every single activity, at least since yesterday.
In the logbook , all entries seem to be ok, including power.
Thus, those of you who don't analyse their data downstream of the logbook as we do e.g. in intervals.icu might not have realized the issue yet.

Is that a consequence of the last ErgData update from two days ago or anything else?
I already reported the problem to concept2 this morning.

Has anybody else seen the problem?
Thanks.

[Lonre]

I'm having the same problem where the FIT files have way too large power figures. Compared the exported fit files to see differences between older and now problematic ones. Strava/TrainingPeaks don't show any power values there might be sanity checks.

Equipment: PM5 and iPhone with ErgData. Noticed also that the 2.2.15 update might be the culprit.

[c2scott]

A bug was introduced in the latest release of ErgData for iOS, v2.2.15(2). The pace in the stroke data, which generates the Workout Graph and CSV is off by a factor of 10.

This is an issue that we've just become aware of. An update will be rolled out quickly but I don't know exactly when.

[johncicc]

Glad someone else is finding this error as well.
Automatically syncing my C2 workouts to training peaks was giving me TSS in the thousands, and I was wondering why.

[c2scott]

Update is published, if you are not set to auto-update then you may wish to manually update to 2.2.16(2) or higher.

[Yankeerunner]

Update is published, if you are not set to auto-update then you may wish to manually update to 2.2.16(2) or higher.

Hi Scott, I was referred to this thread by Dougie, and hope you can help.

Last Wednesday my Ergdata, which always showed the drive time in the upper right corner, stopped being active and now just shows 0.00 even as all the other functions continue to work properly.

I've seen you post about the update, and I just did a row a few minutes ago with the same problem. My Ergdata is 2.2.16(2), my PM5 shows firmware version 175, and my phone is an iPhone SE2. Can you think of anything I might try to get the drive time to be active again?

Thanks.