Ticket Created
over 4 years ago

BOULDER-2042

Current and average cadence not updating for running activity

Hi,

A user of one of my DataFields raised this issue with me, I have subsequently observed the same thing on a different watch, different data field, different activity. 

1. I have DataFields tracking all three of Activity.Info.currentCadence, Activity.Info.averageCadence and Activity.Info.maxCadence

2. On a number of occasions (not every time, but certainly quite frequently), averageCadence and maxCadence simply stop updating

3. I have checked in the .FIT file for one of the offending activities and the file appears to be closed correctly, but nonetheless closes after storing ridiculous averageCadence and maxCadence values of "1", despite recording currentCadence correctly.

This has been observed in Fenix Sapphire 6 and Forerunner 735xt - I haven't checked any other devices. It has also been observed on at least two different DataFields that I know of.

FYI, here is an example as observed in my Dialistic DataField over the course of an 18km run. (Red is heartrate, green is speed, blue is cadence. The small circles are "maxCadence", "maxSpeed" and "maxHeartrate" respectively, the coloured wedges in outer ring are "averageCadence", "averageSpeed" and "averageHeartrate". The dial hands are "currentCadence", "currentSpeed" and "currentHeartrate".) As you can see, although average and max update correctly for speed and heartrate, the cadence remains at a nonsense value.

G

Fenix 6 Sapphire showing wrong average and max for cadence

9635560
Parents
  • over 5 years ago in reply to subra

    Hi Subra,

    No, that is not the issue!

    Current, average and max cadence are all provided effectively by Garmin FootPod, Garmin HR-Run strap, Garmin HR-Tri strap or a number of other cadence sensors. Mostly, they provide good data. Sometimes, as in now, they malfunction. There _is_ an upper limit, but pretty sure that the engineers at Garmin are a bit more advanced than allowing an integer wrapping error to reset anything > 256 to 0!

    The issue here is that the max and average values, that usually work well, are simply not being set in this instance for reasons unknown.

    (But, yes, you are right that the minimum cadence is always zero.)

    G

Comment
  • over 5 years ago in reply to subra

    Hi Subra,

    No, that is not the issue!

    Current, average and max cadence are all provided effectively by Garmin FootPod, Garmin HR-Run strap, Garmin HR-Tri strap or a number of other cadence sensors. Mostly, they provide good data. Sometimes, as in now, they malfunction. There _is_ an upper limit, but pretty sure that the engineers at Garmin are a bit more advanced than allowing an integer wrapping error to reset anything > 256 to 0!

    The issue here is that the max and average values, that usually work well, are simply not being set in this instance for reasons unknown.

    (But, yes, you are right that the minimum cadence is always zero.)

    G

Children
No Data