Related

cadence

iba55
1 month ago

Hi friends,

I have a problem with the 955 (my main watch) and it is that it does not calculate the average cadence correctly when walking or hiking, 
when running the error is much smaller. 
The reason is that sometimes the cadence stays at zero, then I have confirmed this in the cadence graph in Garmin Connect. 
The average must add the zeros and the amount is reduced. 
I have confirmed this common Garmin problem with the Fenix ​​7X, 255, Enduro 3 and 955 comparing them with the Suunto Race S and the Coro Pace Pro. 
The difference is approximately: Garmin 120 steps per minute (wrong) and the other watches 128 (correct). 
Why does it add the zeros in the average without stopping walking and what is the solution?
Thank you in advance

Top Replies

All Replies

  • 0 1 month ago

    The formatting of your message means I have to scroll that monospaced text block back and forth horizontally to read the whole message. Please don't do that.

    This will be purely a design decision to calculate the average based on total time rather than just the time where there was movement.

    Perhaps you could turn on auto-pause so the watch stops recording when you stop moving?

  • 0 1 month ago in reply to nowster
    nowster said:
    The formatting of your message means I have to scroll that monospaced text block back and forth horizontally to read the whole message. Please don't do that.

    I think this might be an unintentional result of copying text from something like Google translate. (That's just my guess because I've seen it more than once, and most of the time, the text has either obviously been a translation and/or OP mentioned that it was.)

  • 0 1 month ago in reply to FlowState

    Yes, i am sorry, it is Google tranlator issue.

  • 0 1 month ago in reply to nowster

    Thank you. No, I don't use Auto-Pause.

    I have tried it on several Garmin models and I get the same incorrect average on all of them. Friends of mine have same problem (5 people): Cadence Average counts Zeroes

  • 0 1 month ago in reply to iba55
    iba55 said:
    I have tried it on several Garmin models and I get the same incorrect average on all of them. Friends of mine have same problem (5 people): Cadence Average counts Zeroes

    Given that Garmin probably won't change this behaviour [or make it an option, like it does for power averaging in cycling activities], I have an imperfect solution using a 3rd-party Connect IQ data field that I made.

    [1/3]

    [sorry for splitting this reply into 3 parts, the forum won't let me post it otherwise]

  • 0 1 month ago in reply to FlowState

    1) Download AppBuilder 5 from the Connect IQ store [it's like Excel for your watch]

    [2/3]

  • 0 1 month ago in reply to FlowState

    2) Use the following settings

    - Label: CADENCE [non-0] [or whatever you want]

    - Formula:

    For activity average: 

    avg(nonzero(cadence))

    For lap average:

    lapavg(nonzero(cadence))

    - Data format: Auto

    - Record Data to FIT File: enable this option if you want the value to be recorded to the activity file and displayed in Connect

    3) Add the AppBuilder 5 data field to your activity

    [3/3]

  • 0 1 month ago in reply to iba55
    iba55 said:
    Yes, i am sorry, it is Google tranlator issue.

    For anyone who's interested, the problem with weirdly formatted text happens if you manually copy text from Google Translate, by:

    - selecting the text

    - pressing CTRL/CMD-C, or right-clicking and selecting Copy..

    The solution is to press the copy-to-clipboard button instead. This will avoid the formatting seen in the original post.