This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

what are strokes on GC?

I have noticed that on my bike rides recorded with the 830 when I look at the details on GC it indicates the number of strokes. I am assuming that is the number of turns of the pedals, but I could well be wrong. I can find no documentation that tells me how to view the strokes on the 830. So what are the strokes that GC is listing and how are they counted or calculated? Certainly the 830 could count them if you have a cadence sensor (I am assuming), but if it did so, why not have a data field to allow you to see the number? I suppose GC could also calculate an approximate stroke count based on the cadence data. I do not see this information of RWGPS but I know some information is lost in the data transfer from GC to RWGPS.

0 troutmask over 5 years ago

I get strokes from my Garmin watch when swimming. Shown on connect

Cycling cadence is shown on connect as cadence not strokes and recorded by either a cadence sensor or a crank or pedal based power metre.

0 SteveRodkey over 5 years ago in reply to troutmask

Here is an example: Strokes is listed on the lower right

0 aweatherall over 5 years ago in reply to SteveRodkey

For cycling it is the number of crank revolutions.

0 Chutin over 5 years ago in reply to aweatherall

But should it in that case not be exactly the same as "Avg Bike Cadence" times "Moving Time"? For my activities this is not the case, i.e. "Strokes" is (substantially) lower than that product ...

0 SteveRodkey over 5 years ago in reply to Chutin

That would only be the case if you were always pedaling. I know I coast a lot. Although I think there may be a setting to average cadence over total time instead of pedaling time, I have not used that.

0 Chutin over 5 years ago in reply to SteveRodkey

I see how these 2 numbers can divert: for the profile I was referring to, I have the "Cadence Averaging" set to "not include the zeros" (coasting). That leads of course to a higher "Avg Bike Cadence", and consequently to "Avg Bike Cadence" x "Moving Time" being higher than "Strokes".

If I remember correctly, the default setting was for this Cadence Averaging to include coasting, so in that case I guess "Avg Bike Cadence" x "Moving Time" should be the same as "Strokes".