This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is metronome supposed to beep if I run with higher cadence than what's set?

Former Member
Former Member

My understanding is there's no such thing as too much cadence. If I'm currently running at 175 and want to practice for 180, if I run at 185 the metronome shouldn't beep, should it? I understand that it does beep if I go 5 below the target, but why beep if you go above? Am I missing anything?

  • I don't know about the 945, but on the 645, the metronome gives you the cadence, it doesn't beep only if your cadence is different than your goal. Mine is set on 180 steps per minute, with a beep every 4 steps, meaning I have to run left on the beep, right left right , then a new sequence starting with left on the beep. Hope this helps

  • Don't know about the 945 either, but on my old Fenix 3 there's a high alert and a low alert threshold. Is that not there on the 945 as well?

    And, the "metronome" should just be a constant beaping to maintain rhythm. I assume that what you are really talking about are the cadence alerts. Those should be possible to set up without using the metronome, which is just a help to maintain a steady cadence.

  • Former Member
    0 Former Member over 5 years ago in reply to olni65

    Thanks for your responses. The way it works on the 945 (as I experienced it) is the metronome vibrates at approx. 4-5-6 steps as Marathon.Go describes (based on some fraction calculated from the cadence I set). The problem with this is it's not matching one vibrate to 1 / 180th of a minute (i.e. 3 vibrates per second - which is what a metronome should do). It then beeps (in addition to regular Vibrate) when I run slower or faster then set cadence. It also doesn't play it on the BT headset, so while it's kind of cool to "feel" the vibrate on your wrist, when you want to "hear" the beep (if you're mis-cadencing), you can't if you listen to music on BT headset.