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 showing as 90 rather than 180

As the title says, my cadence is showing as around 90 rather than around 180 for a bit less than half the time of a running activity in Garmin Connect (web or iOS app), meaning that the average cadence, which should be around 180, is being calculated as much lower than it should be (around 145). Here's a typical example:

https://connect.garmin.com/modern/activity/2885952909

Has anyone else experienced this?
Is the watch faulty?
How is cadence measured anyway?
  • Cadence is measured by analysing accelerations measured by the watch's built-in accelerometer, and those accelerations are indirectly caused by the swings of your arms. That is unless you use an external footpod. So either your watch is faulty, or you do something weird with your arms while running.
  • Hmm, I don't think I do anything weird with my arms, but next run I will consciously make sure my arms are swinging normally and check the results. Thanks.
  • Then I'd suspect a faulty accelerometer in your watch. You might want to try a hard reset before contacting support.
  • This could be a temporary issue in GC. It has happened to me a few times when analysing my runs but it goes away. I presume is relates to the activity rendering and they forget to double the numbers,
  • Did you have a look at his activity? Cadence reading at about 180 spm is interweaved with readings at about 90 spm. Doesn't look like a Garmin Connect rendering issue to me. Doubling the numbers would cause his cadence to be in the 180-360 range, which again doesn't make sense.
  • I've checked back through my activities and everything was fine up until about 10 days ago, e.g. nothing wrong with this one:

    https://connect.garmin.com/modern/activity/2745033304

    Then, about 10 days ago, the interweaving of ~90 spm data points started. It coincided with a period of interval runs so it's hard to tell exactly when it started, but all the normal runs since then have the problem.

    I'll try a hard reset before my next run...
  • Mine is doing the same thing since the FW upgrade to 5.20. I did a hard reset and the first run after that does seem better but I did not reinstall any data fields or watch faces yet