Related

MaxHR gets adjusted with new LTHR, even if maxHR auto-detection is disabled

leflic
12 days ago

Whenever a new running LTHR is detected on my FR955, the running specific maxHR is adapted too, even if maxHR detection is disabled. It only affects the running specific values, not the general ones.

E.g. during my last run, it detected a LTHR that was 5 bpm higher than before andei adapted the maxHR to a value 5bpm higher than before.

This drastically changes my DSW, e.g. it's impossible to get into the vo2max range. Also, the maxHR is 10bpm higher than I think rt should be.

Is this normal or a bug? What can I do?

FW 22.24

  • 0 11 days ago

    Same problem here. It's definitely a serious bug. The problem exists since v21.19. I'm regularly chatting with Garmin Customer Support about this topic. Even with the HRM Pro Plus the watch extremely overestimates my capabilities. Btw if I manually chance MaxHr to 170bpm and LTHR to 159bpm, DSW still suggests me to do a Base Run @ 151 bpm and a Threshold Run at 162 bpm. That's strange and extremely annoying. My LT Pace should be around 03min:55sec, according to Garmins definition of a LT Pace and it auto detected a Pace of 03min:37sec,which is too fast and unrealistic.

    EDIT: Please report your oberservations with faulty LTHR and LT Pace to the Garmin customer support. They need data to investigate.

  • 0 8 days ago

    The same thing has happened to me too. Right in the middle of a training plan. I turned off the auto detect and updated my zones. It adjusted all the runs based on my input.