Related

Inaccurate lactate threshold results continue in 21.19

trev4short
17 days ago

Beta tester here and lactate threshold detection has been incredibly inaccurate in all betas, including 21.19. This has been a known issue over the last 2-3 betas, so I'm not sure why they would release 21.19 without fixing it. My LTH jumped from 8:33 to 7:33, and then, despite a dismal 14% execution score on another threshold run, it went up further to 7:29. Now each threshold run execution score is 0% without an adjustment back down. What's the use of the beta program if they don't fix known  issues before final release?

  • 0 6 days ago
    1. I always run with HRM-Pro belt. Since November 26th, when I did a 30-minute base run with version 21.18, it hasn't detected a new threshold. Just yesterday, version 21.19 and outside with HRM-Pro, I did the Garmin-suggested workout of 15 minutes at threshold pace, plus 10 minutes of warm-up and 10 minutes of cool-down, and it still hasn't detected a new threshold. I can't understand that with a 30 min base run you have an accurate threshold meanwhile with a 15min threshold run, plus 20 min base run, you dont have a new threshold. 

    I would like to know if its possible to downgrade The firmware, I'm afraid all my new data will ruin my old ones and ruin my trainings

  • 0 6 days ago in reply to jcmadte78

    You can downgrade; nearly all versions are in the forum. But have you considered that you may not have a new threshold? 

  • 0 6 days ago in reply to RockBastard

    Thanks!

    Yes, I considered that, but before version 21.18, garmin reccomended a new threshold at least one every week, usually when i ran at threshold pace, so, one more reason to bring back again a guided lactate threshold to see if it changes or not

  • 0 6 days ago in reply to jcmadte78

    From what i saw if you don't reach your actual threshold during an activity, Garmin doesn't consider your activity a "threshold" activity.

    The problem is when your actual threshold is very high due to a wrong calculated value (it happened frequently with new firmware), is very hard to make an activity in threshold

  • 0 6 days ago in reply to jcmadte78

    It's incredible that Garmin did those big errors: we want (and every runner want...) that watch ask is we want save new MaxHR and new LTH, because is normal like this (is not it's better trow away Garmin because they are two fundamental numbers....) and we want that is possible calculate it only with belt, because without is every idiot know that beats are not true. Go back and go back quickly, before everyone change watch!