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

Cadence

There is an inconsistency in the way cadence is displayed.

On the activities summary that lists all of my runs in a table with time, distance, average run cadence, etc, the average run cadence is showing what appears to be my real cadence divided by two. For example I have average cadences listed at 80 steps per minute.

When I examine the details of any activity, the cadence there is shown properly, at about 160 steps per minute.
  • True - Garmin are not consistent in the way they treat cadence - however I would say that the 80 figure is the correct one as more commonly cadence is defined as a complete revolution for a pair of feet. However you define it Garmin are inconsistent and show one figure on one screen and a different figure on another. My forerunner 610 shows cadence in full revolutions i.e. the 80 ish figure. Garmin really need to make it an option and apply that consistently.
  • True - Garmin are not consistent in the way they treat cadence - however I would say that the 80 figure is the correct one as more commonly cadence is defined as a complete revolution for a pair of feet. However you define it Garmin are inconsistent and show one figure on one screen and a different figure on another. My forerunner 610 shows cadence in full revolutions i.e. the 80 ish figure. Garmin really need to make it an option and apply that consistently.


    The big issue is the lack of consistency.

    On the other point, in the context of running, I more often see cadence defined as the number of foot strikes per unit time. I suppose if someone is using a foot pod then they would just be measuring the rate at which only one foot hits the ground?

    However Garmin wants to do it, they should be consistent about it.
  • Agreed they should be consistent. The most common definition of Cadence for running is the full cycle figure which has the advantage of matching with the cycling definition which is for a full revolution.
  • Are you talking about a Connect IQ app?

    In CIQ stuff I've seen inconsistencies. (writing my own app) For example, when looking at "cadence" (for a RUN activity) it's in steps per minute, but for average and max cadence, it's "revolutions" (2 steps). When I reported the difference, it seems that avg and max should be like current cadence. (in SPM)

    By multiplying avg and max by 2, the numbers I see in my app match those values as shown in Garmin Connect.
  • Same here. Any 'normal' running activity has a different way of showing runningcadence/-stride to a running work-out. Activity is ie. 180, work-out is ie. 90. This is very confusing to me.