PM5 erg data frozen at 'Workout Active' post workout completion

[Ciliconblade]

Hi all,

Wondered if I could have some advice. I have a PM5, latest software.

Quite consistently when I row a 100M sprint while connected to my Erg Data, when I complete the row, the workout doesn't get properly recorded. Instead the screen seems to be stuck on 'Workout Active', it's semi frozen but I can still click and change the different displays but I can't reset it or press menu to get out of the main screen on the PM5 either.

The row is not recorded at all, nor is there a workout code stored in the PM5 so I can't verify it. I am doing the British virtual race later so hopefully this bug doesn't carry to that too.

Wondered what I should do? I've reset it before but it didn't solve the issue.

Many thanks,

Johnny

[Carl Watts]

Did you try a full factory reset on the PM5 ? Its not the same as just pressing the reset button on its own.

Normally I have relied on RowPro to automatically setup my splits but since moving to the Dual PM monitor set-up I now have independent control over the splits with ErgData on one PM5 and the PM3 running RowPro.

When I decided to do a 1 minute a few weeks ago I was very surprised that you cannot set-up decent splits in the PM5 for like 10 or 20 seconds, your stuck with a single 1 minute split which is pretty much useless. Its also horrible in your LogBook entry, you could even have 5 second splits as the PM5 is capable of producing up to 50 splits for your row.

Emailed Concept 2 weeks ago to change it but as its been like this since probably 2003, don't expect it to change in a hurry. Perhaps if enough people can be bothered to e-mail Concept 2 they will change it for at least the 1 minute as this is a rankable time.

Are you using the latest version of ErgData ? from memory it doesn't update itself, you need to check for updates manually. Also you have not stated Android or iOS, there are no issues with Android version 1.98 with PM5 Firmware version V168.

I have stayed away from V169, it gave me all sorts of problems using Bluetooth and I had to roll back to V168 which is flawless.