Ergdata + PM3: Strokes are skipped in logged data

Topics relating to online racing and training with 3rd party software.
Post Reply
Allan Olesen
2k Poster
Posts: 374
Joined: April 27th, 2018, 6:40 am

Ergdata + PM3: Strokes are skipped in logged data

Post by Allan Olesen » February 2nd, 2019, 8:04 am

I have a PM3 (first model, with newest firmware for that model), connected via cable to an Android phone running Ergdata. I have noticed that when doing short intervals, the max. watts which I saw on the PM3 screen, are not to be found when I look at the recorded data afterwards.

In this workout it became especially apparent:
https://log.concept2.com/profile/1181099/log/36824331

At 20, 25 and 30 minutes, I did a 15 second interval at approx. 350 watt, equal to 1:40 pace, and a stroke rate around 36 SPM. The recorded heart rate supports that something happened here. But when looking at the pace graph, there is not even a small spike at 25 minutes. The fastest recorded pace around 25:00 was 2:17, not 1:40.

When I download the stroke data as a CSV file, it seems like I did one long stroke (no. 459) which lasted for 17 seconds from 25:02 to 25:19. During those 17 seconds I travelled 82 meter, which is equal to an average pace of 1:44. But the recorded pace for that stroke is 2:24, and the power is only 117 watt. And even though my stroke took 17 seconds, my stroke rate is unchanged at 20 SPM.

Number Time (seconds) Distance (meters) Pace (seconds) Watts Cal/Hr Stroke Rate Heart Rate
456 1497 4918 148 108 671 20 117
457 1499 4928 146 112 687 21 116
458 1502 4936 137 136 768 24 117
459 1519 5018 144 117 703 20 145
460 1523 5027 150 104 656 20 143
461 1525 5037 153 98 636 20 141
462 1528 5046 151 102 649 20 139

Anyone else having similar problems? Is my old PM3 simply too slow to transmit all stroke data when my stroke rate goes this high?

Post Reply