Incorrect values shown in Run Cadence columns on Garmin Connect's Activities page

Anyone else having issues with the permissions for that image, or is it just me?

It worked for a while but it's back to 'forbidden'. Maybe your image hoster doesn't appreciate hotlinking?

Strange. Everything else I posted in the same way still seems to show without issues.

Maybe your image hoster doesn't appreciate hotlinking?

It's Google Photos, I'm not aware of any recent change in policy, and everything else I've uploaded and posted with the same procedure in the last 40 days seems to still work in private/incognito (Safari and Chrome) browser windows without my signing in to either Google or Garmin in them.

Anyway, I've refreshed the image URL again, and it works for now when I tested it. If it stops working again, perhaps try this link: https://drive.google.com/file/d/1Qfu7bNfQKWnC9EJUWHslH4-1paYyL34BBg

I only see average cadence not maximum on the summary page but my average cadence shows the full cycle figure i.e. 90 rather than 180 - whereas in the activity details it will show 180. The summary figure is always 50% of the detail figure. I personally would rather see the full cycle figure (i.e. the 90) everywhere but I agree that garmin should be consistent but at least the figures are not wrong. I have not tried editing the max cadence field (I get occasional outliers) but I'm not sure what vale it is really - my highest cadence is always when I am descending a series of steps on a steep path not far from my house - for me average cadence is the key figure.

I only see average cadence not maximum on the summary page

The Max Run Cadence column is not included by default, but easy enough to add to the summary table on the Activites page.

but my average cadence shows the full cycle figure i.e. 90 rather than 180_…‹snip›… I personally would rather see the full cycle figure (i.e. the 90) everywhere

I'm not sure what to ‘full cycle’ refers. I normally walk/stroll at around 120‑SPM and run at around 180‑SPM, and a number below 100‑SPM just makes no sense to me.

I have not tried editing the max cadence field (I get occasional outliers) but I'm not sure what vale it is really - my highest cadence is always when I am descending a series of steps on a steep path not far from my house - for me average cadence is the key figure.

The activities I track using the Run activity profile on my FR235 always include both run and walk (usually ad‑hoc, as opposed to preset) intervals, so the Average Run Cadence figure for an activity is meaningless to me. On the other hand, the Max Run Cadence could tell me if something unusual happened, e.g. if it's less than 180 or higher than 190, then I must have had some reason for the inconsistency – in which case I'd look at overlaying the cadence chart with pace and/or elevation (and also look at the map) to see what that as for.

By full cycle I mean one full stride sequence - i.e. left and right foot - so 90 is 90 steps per minute for each foot. This used to be the more common way to quote cadence and is in line with cadence for cyclists which covers revolutions per minute. Also the Garmin footpod returns figures as 90 etc

Your explanation of why the max is useful makes sense now

Depending on the device .. you may see the number in strides / min rather than steps / min. My Forerunner 610 shows my running at about 90 on the cadence data field (strides) on the device .. yet my Vivoactive HR shows cadence in Steps/Min (ie the 180 number). They amount to the same thing.

By full cycle I mean one full stride sequence - i.e. left and right foot - so 90 is 90 steps per minute for each foot.

Thank you for the explanation. I never thought of a stride as two steps, given the dictionary definition[sup]1,2,3[/sup] of stride is typically a long step, and in Garmin Connect Mobile (under User Settings), the Stride Length is calculated as Measured Distance divided by Total Steps.

I have issue on cadence value too but i am using Edge 520. I have created a thread on this.

Did you update your device recently?

Did you update your device recently?

I updated my FR235 to firmware v4.60 when it became available. However, I don't believe that is relevant, since the cadence data for every run I've recorded with my FR235 (since firmware v3.30) exhibits the same phenomenon. It's a Garmin Connect online issue, not a device firmware issue.