Pm3 Time Bug?

[[old] ehagberg]

I did a 500m set piece. RowPro clocked my time at 1:30.5. The PM3 says it was 1:30.6. In order to have the piece verified, I had to change the time to what the PM3 logcard had registered rather than the time that RowPro uploaded to my C2 log.<br /><br />What I find strange is that it looks like this might be a PM3 bug.<br /><br />The splits recorded by both the PM3 logcard and RowPro are identical. For each 100m, here are the times:<br /><br />0:18.1<br />0:17.8<br />0:18.0<br />0:18.2<br />0:18.4<br /><br />Those add up to 1:30.5, which is what RowPro lists as the time for the piece, but the PM3 claims this is 1:30.6.<br /><br />Is this a PM3 bug, or something else?

[[old] haboustak]

That's a good find.<br /><br />It looks like a precision problem to me. The PM3 is probably using two significant digits (or more) to calculate the total of the splits and one significant digit to display the results. RowPro is probably using one significant digit for both, which causes it to underestimate the total. The more splits, the more potential for underestimation. <br /><br /><br />I know that the GET_WORKTIME command returns two digits of precision for time, but this might be something that has recently changed.

[[old] ehagberg]

Looking at the RowPro file - as the stroke data is captured - shows that the last stroke has this:<br /><br /> <Stroke><br /> <Time>90581</Time><br /> <Distance>500</Distance><br /> <Pace>0.186679229</Pace><br /> <Watts>430.3978</Watts><br /> <Cals>48.32811</Cals><br /> <SPM>43</SPM><br /> <HR>0</HR><br /> <DutyCycle>0.4</DutyCycle><br /> </Stroke><br /><br />Which would indicate 1:30.581 or 1:30.6 when rounded properly.<br /><br />I guess that RP isn't doing the right thing w/ the spilt adding... and I don't see why they'd even add the splits when they can get the right number from the last stoke of the piece.