Instinct 2X – Cadence in Garmin Connect shows wrong value

i all,

I noticed that during a walking activity with my Garmin Instinct 2X, Garmin Connect shows an average cadence of 98 spm, which seems too high and doesn't match reality.

When I analyze the same .FIT file in tools like FitFileViewer, Interval.icu, and Strava, the cadence is shown as 60 spm, which is realistic and consistent with my older device (Forerunner 230 showed 122 spm = 61 per leg).

So the FIT file seems correct, but Garmin Connect may be misinterpreting or miscalculating the cadence value.

Has anyone else seen this?
Is it a known bug or a firmware issue?

Thanks!

  • Is it a known bug or a firmware issue?

    If you tell the FIT file shows correct data, then it does not look like a firmware bug. However, I checked some of my walks (on Instinct 3), and Garmin Connect shows the correct cadence (double of the cadence values in the FIT file), so it does not look like a bug in Garmin Connect incorrectly multiplying the data from the FIT file either, so I do not really see where the problem comes from. Perhaps, if you could post the FIT file, we could find some clues.

  • Hm, I do not know, but I see the right values in your FIT file corresponding to the values when the file is imported to Garmin Connect. Similarly as at my own walk activities.

    The following data comes from one of my recent walks with Instinct 3. The FIT file shows the Avg Cadence (single leg) of 31, and the Max Cadence of 79. Garmin Connect the shows the doubled values (for both legs) correctly as 2×31 = 62 spm, resp. 2×79 = 158 spm:

    click for image (embedding rejected)

    It looks similarly with your file as well, with the exception that there is a small deviation, likely caused by rounding or flooring the value in FitFileViewer, at the avg value: 2×45 ~= 92 spm & 2×98 = 196

    click for image (embedding rejected)

    As a conclusion, apart of the rounding/flooring issue (possibly more a problem of the FitFileViever), I do not see any discrepancy in the data.

    I do not know where you saw the 60 spm in the FIT file, since it clearly tells the avg ½ cadence of the whole session is 45 spm

  • Trying to post the images in a separate reply, sometimes it works. The first one is the screenshot of my own walk cadence data:

    And then the data of your activity:

  • thank you Trux, I saw 60 spm, when I uploaded this fit file in intervals.icu and strava.com. I dont know how they got to number 60, but Garmin shows same as your screenshot. There might be a bug, but likely somebody would already noticed that or my device is faulty. Will wait if somebody with 2X confirms that too. Thank you

  • I saw 60 spm, when I uploaded this fit file in intervals.icu and strava.com.

    Originally you wrote "When I analyze the same .FIT file in tools like FitFileViewer, Interval.icu, and Strava" and FitFileViever is what I used to look at the file too.

    If you look at the records (all individual points of the activity), when you move the cadence is indeed around 60 spm when moving, but there are also periods were you do not move (0 spm). So the moving ½ cadence is indeed somewhere around 60 spm (and that's probably what Strava shows), but when the overall average incl. the pauses is calculated, the result is 45 spm (90 spm full-cadence).

    You can see the zero cadence also on the cadence graph in Garmin Connect (the red line at the bottom):

  • So garmin platform includes 0 in cadence value, but strava and intervals.icu not? I wondered why this apply to X2 and not to FR230, but when I compared both devices, there are sections of the graph, where speed is above 0, but cadence is 0. I would expect, that when I am moving, my cadence has to be above 0. Does not it indicate something wrong with x2? Top graph is speed, bottom is cadence and red line is X2, blue line is FR230. FR230 doesnt have this drops to 0 cadence (or at least not so often)

  • I would expect, that when I am moving, my cadence has to be above 0.

    Not always. The watch may not be able to detect the cadence if the arm wearing the watch does not swing naturally. For example when you are pushing a troller or a caddy, holding on railings, ropes, trees, walls, sometimes even when you carry something in the hand, using walking poles, etc.

    It could be due to a damaged accelerometer, of course, too. You best test it by walking some distance in regular continuous pace, with arms swinging steadily and naturally. 

  • I did already three walks each 2,5hour long, wearing both watches, trying L/R hand, tight/a bit loose strap and in this particular situation, both watches were on same hand, I wore both watches on my left hand swinging my arm naturally. Thanks for your help trux.