Well, the firmware update did nothing to help solve the PM5 problems. But it sure did change the symptoms. Now, while I am rowing, at random points, the PM5 will throw an error, but it will keep working and talking to painsled. I can push continue, and everything will be fine for a while, and then it will repeat. The time between errors can be just a couple of strokes, or as long as 10 minutes.
I checked the batteries, and they claim to be at 96%, which makes sense since I replaced them last week when this problem started.
I guess it is time to contact Concept2. For now, I think I will swap out the monitor to a PM3 that I have lying around. I’ll see if that works better with a USB cable than the PM5 works via BT.
The session was uneventful. I really like the 4×12′ session. It’s a quick session and the 1:59 pace put me right on the edge of my aerobic HR zone, and a bit over at the end.
On the chart, you can see when I got the screens because it caused the blips in the pace. By my count I had 18 interruptions due to error screens
Workout Summary - media/20171225-2205320o.csv --|Total|-Total-|--Avg--|-Avg-|Avg-|-Avg-|-Max-|-Avg --|Dist-|-Time--|-Pace--|-Pwr-|SPM-|-HR--|-HR--|-DPS --|12912|54:00.0|02:05.5|198.3|21.7|146.2|162.0|11.0 W-|12108|48:00.0|01:58.9|208.1|21.9|146.2|162.0|11.5 R-|00808|06:00.0|03:42.9|079.4|18.9|141.8|162.0|09.0 Workout Details #-|SDist|-Split-|-SPace-|-Pwr-|SPM-|AvgHR|MaxHR|DPS- 00|03033|12:00.0|01:58.7|207.6|21.9|134.9|145.0|11.6 01|03027|12:00.0|01:58.9|209.1|21.8|144.8|154.0|11.6 02|03025|12:00.0|01:59.0|207.3|21.9|149.9|158.0|11.5 03|03023|12:00.0|01:59.1|208.2|21.9|155.3|162.0|11.5
I’ll be starting off with my new training paces today, based on the recent testing.
- Cat VI: 2:03 – 2:08
- Cat V: 1:58 – 2:02
- Cat IV: 1:52
- Cat III: 1:48
- Cat II: 1:45
Today’s session: 10 x 500m / 2′ Cat V pace.
2 thoughts on “Merry Christmas: 4 x 12′ / 1’30””
That’s not good. When did the symptoms start? Did something change In your configuration around that time?
I am really lazy updating firmware on PM5 or NK SpeedCoach. These devices are not connected to the internet so if it works, I won’t touch it
I’ve recently used PainSled (on Android) as a test, and on the next workout using ErgData I got the same errors as you did. I reset the batteries and it was Ok after that. Since I never seen those errors before or since using PainSled, I suspect it may be to do with how that app communicates with the PM5. ErgData has been improved and is now stable, but there are still bugs.
LikeLiked by 1 person