Related

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

leflic
1 month 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 1 month 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 1 month 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. 

  • 0 29 days ago

    i have been telling them since some months, their engineer think the algorithms works perfectly! since the quit the manual lactate test, this new feature is a joke, even running with a chest strap with precise data is not working at all, its gives me +10bpm in lthr and maxhr, i.e. my lthr is around 157, my maxhr 173, when i have the auto-detect feature enabled, its detects a threshold of 167bpm and a maxhr of 185, no way... i dont know how its calculate this metrics, but now is useless since many months, i have disabled it and configured manually my maxhr and lthr and then the run zones, to get accurate training data

  • 0 21 days ago

    This is a known bug since many months, here same, each new auto-detect value is 10+ bpm than actual is, i reported to Garmin support, but they didnt fixed for now, they told me "The engineers sais the algorithm is fine..." there is so many customers complaining about this, and 1 year ago the algorithm was fine, looks like they hire new engineers with no idea of what they are doing...

  • 0 21 days ago in reply to Jo952

    yes, im doing the same, disabling and configuring as i know my metrics, the issue is, that many regular users dont know about their metrics or whats going on...its very rare that the issue is known since many months ago and they dont fixed it, and i feel that they dont have idea on how to...