Fenix 5X Sapphire cycling max versus average cadence

Former Member over 7 years ago

I often ride indoors on my trainer where I pair my Fenix with the Garmin speed and cadence sensors along with a Wahoo Kickr Snap.

One thing I have noticed is that whenever I start pedaling from a complete stop, my Fenix cadence reading is really high for a split second---over 60000! It may even be 600000; I cannot be sure because it just flashes for a split second. Afterward it seems to record my cadence fine.

This is a particular problem since I like to ride for 10 minutes or so, come to a complete stop, calibrate my trainer, come to another complete stop, and then resume my ride. When I do that, my activity would show an average cadence higher than max cadence which is clearly nonsense. There are no noticeable spikes, however, in the cadence graph. So what gives?!

I have attached the image from a ride showing the average higher than the max cadence and the corresponding cadence graph for the entire ride.

Does anyone else have encountered this?

Thanks!
Tim ciq.forums.garmin.com/.../1344128.png ciq.forums.garmin.com/.../1344129.png

0 mcalista over 7 years ago

I don't use an indoor trainer, but would getting the pedals moving before hitting the Resume button sidestep the problem?

0 razmichael over 7 years ago

There is a note in the current beta about fixing high cadence values with some meters. So you could try that and if still broken report it up that chain. Otherwise i would suggest contacting support because, if nothing else, it should not be showing that higher average than max. This means it is ignoring the spike when it comes to the max but not the average. Does the same error occur in the watch history or just GC?

0 Former Member over 7 years ago

There is a note in the current beta about fixing high cadence values with some meters. So you could try that and if still broken report it up that chain. Otherwise i would suggest contacting support because, if nothing else, it should not be showing that higher average than max. This means it is ignoring the spike when it comes to the max but not the average. Does the same error occur in the watch history or just GC?

The watch reports the same average as GC.

I will look into the beta! Thank you!

0 Former Member over 7 years ago

Here is an update in case someone else has encountered this issue.

I have contacted Garmin Support. They told me the issue has been reported, and Garmin is looking into it.

My observation is that it is only an issue when my Wahoo Kickr Snap is connected as a power meter with my fenix 5x. There is no abnormality with the cadence reading if the Kickr Snap is not connected.