Related
Options

Running cadence shown as half of steps/min after 19.20 update

FahadUsman
over 3 years ago

I have Fenix 6s Pro, and recently (most likely after 19.20 update) I have noticed that during running acitvities the watch shows cadence as half of what it usually shows. For example it shows 85 instead of usual 170. However after completing the activity, it shows correct cadence in garmin connect app. I have noticed this both with and without the HRM chest strap. Did anyone else also notice something similar?

  • 0 over 3 years ago

    The currentCadence used to show SPM for running activities but now shows half the values (but only even numbers, so it doesn't show 90.5 for example) as mentioned in this thread. Just confirmed it with my own data field. This have changed in the last software versions.

    The .FIT file have 2 cadence values. The first is cadence (in rpm) and the second is fractional_cadence (in rpm). So these two values must be summed and then multiplied with two to get the SPM. These two values in the .FIT file have always (what I've seen) been half the values of the SPM so the .FIT file hasn't changed.

    Screenshot from the .FIT file:

  • 0 over 3 years ago in reply to jim_m_58

    Thank you for the Vivoactive 4 change log information you provided. Even though the VA4 is on the Fitness side, the example will help to get the bug resolved on the outdoor side for the Fenix 6 series.

    We are looking for anyone willing to provide examples of the 50% of cadence issue. Please highlight my name and send me a Private Message. Thank you!

  • 0 over 3 years ago in reply to Garmin - Chris

    Count me in with the 50% cadence issue...

  • 0 over 3 years ago

    This issue seems to have been fixed in version 19.74 BETA. 

  • +1 over 3 years ago

    For those that have installed the Beta v19.74 or v19.75, all reports thus far have been the 50% cadence issue is resolved for those using a Cadence data field downloaded from Connect IQ to their watch.

    Once the official software is released, the issue should be 100% resolved for everyone.

  • 0 over 3 years ago 

    var mySettings = System.getDeviceSettings();
var version = mySettings.monkeyVersion;
var firmwareVersion =  mySettings.firmwareVersion;
if (firmwareVersion[0] == 19 && firmwareVersion[1] == 20) {
  if (version[0] == 3 && version[1] == 2 && version[2] == 6) {
      return info.currentCadence * 2;
  }
}
return info.currentCadence;

    As this issue is resolved in the comming firmware update, I added an if-clause to judge the firmware version.