The racing software has a polling system, at every time interval (which varies depending on how many PM3/PM4s are configured in the racing set-up) it goes out round each PM4 and requests the current values.
Each record (as polled NOT per stroke) has Interval, PM3, Time, Meters, Current_Pace, Stroke_Rate, Heart_Rate (the interval, PM3 and HR columns are always blank). Meters are cumulative, pace and stroke rate are current values when that PM4 was polled. As soon as the cumulative distance is over the race distance the data stops.
Code: Select all
Interval,PM3,Time,Meters,Current_Pace,Stroke_Rate,Heart_Rate
,John Doe-Rower M 40+H,0.0,0,0,0,0
,,0.5,0,0,0,0
,,1.0,0,0,0,0
,,1.5,0.9,107,0,0
,,2.0,3.6,107,0,0
,,2.5,6.3,107,0,0
,,3.0,8.7,107,0,0
,,3.5,11.4,95,35,0
,,4.0,14.4,95,35,0
,,4.5,17.1,95,35,0
[... snip ...]
,,490.4,2483.7,89,38,0
,,490.9,2486.7,89,38,0
,,491.4,2489.5,89,38,0
,,491.9,2492.1,89,38,0
,,492.4,2495.2,89,38,0
,,492.9,2497.9,0,0,0
You'll see from that that it's polling at approx 0.5 sec intervals (there were ten machines configured in that race). All the clocks on the PM4s start at the same time (when
appears on the screen) and the first stroke (107 @ 1.5s which is 1:47 pace) includes the rower's reaction time. It takes a while (3.5s) before the PM4 to calculates a stroke rate (35spm). Last stroke at 492.4 seconds was 1:29 pace and 38spm that was enough to coast over the 2500m line.
Pace doesn't include tenths.