Piece Verification

[dave2013]

I was at the boathouse today and had a really good 2K time, the best I've done for 2019 (6:57.5). But at the conclusion of the piece the ErgData said "Failed to upload data. Check your software version update." I took a picture of the PM5 screen to record my times but is there a way to retrieve my metrics from the PM5? I would like to have the time shown as "verified" in my C2 log. I used to have a magnetic card that I could insert into the PM4 to record data. I think there is a USB drive that might be available to collect data from the PM5. Is it possible for me to retrieve the data from this morning's piece on the PM5?

[Citroen]

There's no direct way to get that with Ergdata.

With a USB stick (formatted with the Concept2 utility) and the Concept2 Utility (back at home) or a USB-A to USB-B printer cable and the Concept2 utility (in the boathouse) you can capture the workload data (you don't get all the stroke rate stuff but you can log it as a verified workout).

While you have the Concept2 Utility running use it to upgrade the firmware on all of your PM5s (to prevent Ergdata crashing again). That can be done with a cable or with a USB stick to carry the firmware update.

The backstop (as long as the workout hasn't been overwritten in PM5 memory) is to display the workout split detail then press grey button #4 twice to get the 16 hex digit verification code. That can be used to verify it on the Concept2 https://log.concept2.com website.

[MPx]

While you have the Concept2 Utility running use it to upgrade the firmware on all of your PM5s (to prevent Ergdata crashing again). That can be done with a cable or with a USB stick to carry the firmware update.

Good advice, but wont necessarily prevent a crash. This has happened to me three times in the last couple of months and all of my stuff is up to date. May be coincidence but the errors have occurred on the more violent sprinty pieces - intervals or the 666m for the CTC yesterday - not on longer SS type sessions.

[canglem]

This is something I'd run into as well, and via e-mail reported it. It's a known bug in the most recent iOS update for ErgData that they're planning to fix with the next release.

[dave2013]

Thank you everyone, especial Citroen for the detail instructions.