Simple Cadence measuring question.. garmin
#1
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
Simple Cadence measuring question.. garmin
So I should know this, but I don't.. simple question. Is Average Cadence as reported by a Garmin unit, based on time, or based on distance traveled?
#3
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
Right, but I'm asking about how AVERAGE cadence is calculated over a ride when reading that stat on a garmin
#4
Senior Member
Would it not be based on time?
Average Pedal Revolutions per minute, as opposed to Average Pedal Revolutions per mile.
Average Pedal Revolutions per minute, as opposed to Average Pedal Revolutions per mile.
#5
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
I ride on a flat course for 2 miles. Pedal consistently at 85rpm. Simple answer, my 2 mile ride, the average cadence was 85rpm.
OTOH.. I cycle up a 2 mile hill at 85rpm at 10mph and it takes me 12 minutes. I then coast/bomb down the same 2 mile hill at 40mph, no RPM (because I'm coasting) so it only takes me 3 minutes. Is "average cadence" then calculated as:
85rpm x 2 miles, and ZeroRPM x 2 miles = 42.5rpm, or
(85rpm x 12 minutes) + (0 x 3 minutes) = 1020rpm/15 minutes = average of 68rpm
#6
Senior Member
While I profess no direct knowledge of the Garmin Cycling system, I have to think that Cadence, being expressed as rev/min, has to be time-based.
Simple: Count all the revolutions following Start, divide by all the minutes passed since Start.
Imagine the computation required to base it on distance... 8 rpm for 7 ft, 12 for 7', 19 for 7', 27 for 7, 38 for 7, etc etc for every one revolution of the front wheel. Figure them out for every revolution, remember them all, add them up at the end of a 40 mile ride (30,000 +/- data points) and come up with an average. Not very likely!
Simple: Count all the revolutions following Start, divide by all the minutes passed since Start.
Imagine the computation required to base it on distance... 8 rpm for 7 ft, 12 for 7', 19 for 7', 27 for 7, 38 for 7, etc etc for every one revolution of the front wheel. Figure them out for every revolution, remember them all, add them up at the end of a 40 mile ride (30,000 +/- data points) and come up with an average. Not very likely!
#7
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
While I profess no direct knowledge of the Garmin Cycling system, I have to think that Cadence, being expressed as rev/min, has to be time-based.
Simple: Count all the revolutions following Start, divide by all the minutes passed since Start.
Imagine the computation required to base it on distance... 8 rpm for 7 ft, 12 for 7', 19 for 7', 27 for 7, 38 for 7, etc etc for every one revolution of the front wheel. Figure them out for every revolution, remember them all, add them up at the end of a 40 mile ride (30,000 +/- data points) and come up with an average. Not very likely!
Simple: Count all the revolutions following Start, divide by all the minutes passed since Start.
Imagine the computation required to base it on distance... 8 rpm for 7 ft, 12 for 7', 19 for 7', 27 for 7, 38 for 7, etc etc for every one revolution of the front wheel. Figure them out for every revolution, remember them all, add them up at the end of a 40 mile ride (30,000 +/- data points) and come up with an average. Not very likely!
#8
Getting older and slower!
On my Garmin 800 the average cadence is pedal strokes per minute while moving. There is a setting in tools where you can have it exclude the time you were coasting.
So it is a measure of rpm's, revolutions per minute, over the entire ride.
So it is a measure of rpm's, revolutions per minute, over the entire ride.
#9
Super Moderator
Join Date: Jul 2004
Location: Ffld Cnty Connecticut
Posts: 21,843
Bikes: Old Steelies I made, Old Cannondales
Mentioned: 12 Post(s)
Tagged: 0 Thread(s)
Quoted: 1173 Post(s)
Liked 927 Times
in
612 Posts
How is avg cadence over a ride useful ? Real-time cadence is barely even useful for a few people.
__________________
Bikes: Old steel race bikes, old Cannondale race bikes, less old Cannondale race bike, crappy old mtn bike.
FYI: https://www.bikeforums.net/forum-sugg...ad-please.html
Bikes: Old steel race bikes, old Cannondale race bikes, less old Cannondale race bike, crappy old mtn bike.
FYI: https://www.bikeforums.net/forum-sugg...ad-please.html
#10
Ride On!
Join Date: Apr 2016
Posts: 971
Bikes: Allez DSW SL Sprint | Fuji Cross
Mentioned: 6 Post(s)
Tagged: 0 Thread(s)
Quoted: 227 Post(s)
Likes: 0
Liked 3 Times
in
3 Posts
I could see real-time being useful for someone trying to get a feel for what 80 or 90 RPM feels like...but yeah, the use of average cadence over a minute -- I wouldn't find particularly useful at all.
#11
Getting older and slower!
I don't keep my eye on all the data my Garmin gives me over a ride, but analyse it after the ride. My goal is for my average cadence to be above 75 rpm's.
For me, average cadence (and power) are more importance than average speed.
For me, average cadence (and power) are more importance than average speed.
Last edited by Cychologist; 05-02-16 at 07:28 PM.
#12
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
Exactly; I'm talking about post-ride analysis. Looking back I've had comparable rides at similar average MPHs, but with more greatly differing average cadences (eg. 70 vs. 85). I was trying to get a handle on how average cadence is looked at. I'm trying to get rid of a tendency to spin up to good speed, coast down a bit, spin up again and so on, but rather instead just keep the pedals moving more often. Knowing how garmin calculates avg cadence with the first ride style is helpful.
#13
FLIR Kitten to 0.05C
Join Date: Sep 2014
Location: Lincoln, Nebraska
Posts: 5,331
Bikes: Roadie: Seven Axiom Race Ti w/Chorus 11s. CX/Adventure: Carver Gravel Grinder w/ Di2
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 2349 Post(s)
Liked 406 Times
in
254 Posts
If you're talking median pedaling average, like Stravistix shows, it is fairly useful.
Exactly; I'm talking about post-ride analysis. Looking back I've had comparable rides at similar average MPHs, but with more greatly differing average cadences (eg. 70 vs. 85). I was trying to get a handle on how average cadence is looked at. I'm trying to get rid of a tendency to spin up to good speed, coast down a bit, spin up again and so on, but rather instead just keep the pedals moving more often. Knowing how garmin calculates avg cadence with the first ride style is helpful.
Ah, the good-old pedal/coast shens.
What did it for me, was having someone or something yell at me when I stopped pedalling. Garmins these days can start chirping an alarm if your cadence drops to 0. Stravistix is also nice in the extra cadence tool info possible. The cadence avg on Garmin isn't that informative, I'm honestly not sure how it calculates its number either, even with 0-averaging turned off.
Having something like Stravistix that actually will tell you by %age exactly how much of a workout you are "cheating" yourself can be fairly motivating.
Last edited by Marcus_Ti; 05-03-16 at 05:33 AM.
#14
Senior Member
Granted, I'm no pro, but I can still use it to hone my own skills. I can compare rides and see that usually a higher cadence corresponds with a higher speed.
I find it very useful.
#15
will stop for donuts
Join Date: Jan 2014
Location: Maine
Posts: 214
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 13 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
afaik, it's average cadence based on the amount of time the cadence sensor is being triggered. So if you are coasting, that time is not factored in to your average cadence
#16
FLIR Kitten to 0.05C
Join Date: Sep 2014
Location: Lincoln, Nebraska
Posts: 5,331
Bikes: Roadie: Seven Axiom Race Ti w/Chorus 11s. CX/Adventure: Carver Gravel Grinder w/ Di2
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 2349 Post(s)
Liked 406 Times
in
254 Posts
What average Garmins display, mean/media/mode and the method to derive it is AFAIK anyone's guess.
#17
Senior Member
Join Date: Apr 2011
Location: Alpharetta, GA
Posts: 15,280
Bikes: Nashbar Road
Mentioned: 71 Post(s)
Tagged: 0 Thread(s)
Quoted: 2934 Post(s)
Liked 341 Times
in
228 Posts
I don't know.. is it just time, or time and distance? Maybe an example illustrates the question?
I ride on a flat course for 2 miles. Pedal consistently at 85rpm. Simple answer, my 2 mile ride, the average cadence was 85rpm.
OTOH.. I cycle up a 2 mile hill at 85rpm at 10mph and it takes me 12 minutes. I then coast/bomb down the same 2 mile hill at 40mph, no RPM (because I'm coasting) so it only takes me 3 minutes. Is "average cadence" then calculated as:
85rpm x 2 miles, and ZeroRPM x 2 miles = 42.5rpm, or
(85rpm x 12 minutes) + (0 x 3 minutes) = 1020rpm/15 minutes = average of 68rpm
I ride on a flat course for 2 miles. Pedal consistently at 85rpm. Simple answer, my 2 mile ride, the average cadence was 85rpm.
OTOH.. I cycle up a 2 mile hill at 85rpm at 10mph and it takes me 12 minutes. I then coast/bomb down the same 2 mile hill at 40mph, no RPM (because I'm coasting) so it only takes me 3 minutes. Is "average cadence" then calculated as:
85rpm x 2 miles, and ZeroRPM x 2 miles = 42.5rpm, or
(85rpm x 12 minutes) + (0 x 3 minutes) = 1020rpm/15 minutes = average of 68rpm
FWIW I believe from observation that the instantaneous readings for both the speed and cadence is likely calculated with a Gaussian smoothing over the past several seconds, with "zero" readings discarded. Smooths out erroneous spikes that way, better than just averaging 3-4 seconds.
Last edited by wphamilton; 05-03-16 at 07:33 AM.
#18
Senior Member
Join Date: Aug 2008
Location: South Central PA
Posts: 549
Bikes: Focus Arriba, Specialized Roubaix Expert, Bianchi Impulso Allroad
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 109 Post(s)
Liked 82 Times
in
53 Posts
(I know it's that way for 500 and 520 - I would assume the others but it can be found in the user manual).
Also from the Garmin manual:
Cadence: Revolutions of the crank arm per minute.
Cadence - Avg: Average cadence for the duration of your current ride. (So also time based)
Last edited by redcon1; 05-03-16 at 07:59 AM. Reason: Added info
#19
Senior Member
Join Date: Mar 2010
Location: Seattle, WA
Posts: 23,208
Mentioned: 89 Post(s)
Tagged: 0 Thread(s)
Quoted: 18883 Post(s)
Liked 10,646 Times
in
6,054 Posts
#20
FLIR Kitten to 0.05C
Join Date: Sep 2014
Location: Lincoln, Nebraska
Posts: 5,331
Bikes: Roadie: Seven Axiom Race Ti w/Chorus 11s. CX/Adventure: Carver Gravel Grinder w/ Di2
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Quoted: 2349 Post(s)
Liked 406 Times
in
254 Posts
Have had King hubs and Campy hubs. Never bothered me.
Did bother me once I saw real data graphs of my pedalling and how much "pedal and coast" actually is "coast and pedal a little bit". Having auto-warning of 0 cadence from a bike computer drills it in how little one actually pedals. One might *think* you are mostly pedalling and only coasting a little bit-but IRL the numbers don't lie....odds are at best pedal-and-coast results in 60%+ coasting
If you commute in MUTs or streets with lots of stoplights....very easy to condition yourself into pedal/coast, due to the constant slowing/stopping.
Did bother me once I saw real data graphs of my pedalling and how much "pedal and coast" actually is "coast and pedal a little bit". Having auto-warning of 0 cadence from a bike computer drills it in how little one actually pedals. One might *think* you are mostly pedalling and only coasting a little bit-but IRL the numbers don't lie....odds are at best pedal-and-coast results in 60%+ coasting
If you commute in MUTs or streets with lots of stoplights....very easy to condition yourself into pedal/coast, due to the constant slowing/stopping.
#21
Senior Member
Join Date: Mar 2010
Location: Seattle, WA
Posts: 23,208
Mentioned: 89 Post(s)
Tagged: 0 Thread(s)
Quoted: 18883 Post(s)
Liked 10,646 Times
in
6,054 Posts
I just exported my last ride into TCX format, queried it in SQL Server, and the average I calculate excluding zeros matches what my Garmin says exactly.
Code:
Declare @tcx xml Set @tcx = N'put the TCX data here' -- Parse the xml data into a temp table Select e.value('*:Time[1]', 'nvarchar(100)') TimeStamp, e.value('*:DistanceMeters[1]', 'decimal(10, 5)') Distance, e.value('*:Cadence[1]', 'int') Cadence, e.query('*:Extensions').query('//*:Watts[1]').value('*:Watts[1]', 'decimal(10, 5)') Power Into #x From @tcx.nodes('//*:Trackpoint') activity(e) Select Avg(Cadence) From #x Where Cadence != 0 Drop Table #x
#22
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
Interesting info everyone. Thanks. I guess it would interesting if there was a way to get raw data and analyze any way you want (ie. after the ride). For example, take a ride of a certain distance, let's say 60 miles, and then have the raw data of how many revolutions total you spun over that 60 miles, in theory you could calculate a average cadence per yard or whatnot.
I'll have to check into how I have my Garmin treating 0 rpms. I haven't found a way to change the setting in the Garmin Connect PC analysis or it's export to Zwift -- so am I correct in assuming this can only be adjusted in the actual GPS unit, and not in the software?
I'll have to check into how I have my Garmin treating 0 rpms. I haven't found a way to change the setting in the Garmin Connect PC analysis or it's export to Zwift -- so am I correct in assuming this can only be adjusted in the actual GPS unit, and not in the software?
#23
Senior Member
Join Date: Nov 2014
Location: Eugene, Oregon, USA
Posts: 27,547
Mentioned: 217 Post(s)
Tagged: 0 Thread(s)
Quoted: 18376 Post(s)
Liked 4,511 Times
in
3,353 Posts
A lot of devices will zero out zeros. So, stopping at a stop sign shouldn't impact your average speed.
Coasting while moving would be a bit different, but it would seem like adding it into your average cadence would give you bad data. Or, ideally it should be configurable. Average moving speed vs average trip speed. Average pedalling cadence vs average moving cadence vs average trip cadence??? Does standing at a stop sign while not spinning count?
I tend to pedal faster going downhill than uphill (although sometimes slowly going over the peak).
Coasting while moving would be a bit different, but it would seem like adding it into your average cadence would give you bad data. Or, ideally it should be configurable. Average moving speed vs average trip speed. Average pedalling cadence vs average moving cadence vs average trip cadence??? Does standing at a stop sign while not spinning count?
I tend to pedal faster going downhill than uphill (although sometimes slowly going over the peak).
#24
Advocatus Diaboli
Thread Starter
Join Date: Feb 2015
Location: Wherever I am
Posts: 8,636
Bikes: Merlin Cyrene, Nashbar steel CX
Mentioned: 14 Post(s)
Tagged: 1 Thread(s)
Quoted: 4733 Post(s)
Liked 1,532 Times
in
1,003 Posts
A lot of devices will zero out zeros. So, stopping at a stop sign shouldn't impact your average speed.
Coasting while moving would be a bit different, but it would seem like adding it into your average cadence would give you bad data. Or, ideally it should be configurable. Average moving speed vs average trip speed. Average pedalling cadence vs average moving cadence vs average trip cadence??? Does standing at a stop sign while not spinning count?
I tend to pedal faster going downhill than uphill (although sometimes slowly going over the peak).
Coasting while moving would be a bit different, but it would seem like adding it into your average cadence would give you bad data. Or, ideally it should be configurable. Average moving speed vs average trip speed. Average pedalling cadence vs average moving cadence vs average trip cadence??? Does standing at a stop sign while not spinning count?
I tend to pedal faster going downhill than uphill (although sometimes slowly going over the peak).
EDIT: I'm sure this is where someone tells me to get a power meter. Yeah, I know..
#25
Senior Member
Join Date: Nov 2014
Location: Eugene, Oregon, USA
Posts: 27,547
Mentioned: 217 Post(s)
Tagged: 0 Thread(s)
Quoted: 18376 Post(s)
Liked 4,511 Times
in
3,353 Posts
Do you use Strava (or a similar app), and are you able to upload power/cadence?
With Strava, you can select time or distance, and look at changes in power, speed, etc.
For Speed, I think Strava looks at both overall (in a segment) and moving (ignoring segments).
With Strava, you can select time or distance, and look at changes in power, speed, etc.
For Speed, I think Strava looks at both overall (in a segment) and moving (ignoring segments).