Related

Forerunner 965 - Lactate Threshold not Updating - 21.19

AJB123
1 month ago

I have a Forerunner 965 running Software Update 21.19. The last time I received a Lactate Threshold update was the 4th November despite having completed 14 runs since this date of various types / intensities (Threshold, Sprint, Easy). Prior to the 4th November my Lactate Threshold was updating regularly. I always run with a Heartrate Monitor (HRM Run). I have Auto Detection switched on for Max HR, Threshold and FTP. 

Is there another setting that I am missing?

  • 0 25 days ago in reply to global_local

    That's interesting, I always use a chest strap, so maybe it's another bug. Maybe a software update will rectify it.Thanks for the input!

  • 0 25 days ago in reply to Johnthecyclist

    I always use a chest strap, too. However, I also tried without HRM to see if I could get an updated lactate threshold estimate with the optical sensor on my FR955 wrist. But nothing changed. And this is true for every type of training (base run, recovery run, tempo run, sprint, etc.) that I do.

    Some days ago I contacted Garmin support and explained the issue. Currently waiting for help/answer from them (I'm afraid it will take a bit...).

  • 0 20 days ago in reply to 1625590

    Finally I've had a Lactate Threshold update today, using a HRM strap, during a base run. My last readings were 150bpm at 4.53 /km pace, today's update is showing as 155bpm at 4.33 /km pace.

  • 0 3 days ago

    Same issue on my 965 with latest beta FW 22.14. Absolutely no threshold updates since late Oct 2024. Was working fine before then. 

  • 0 3 days ago in reply to Bob

    So just after posting that comment, I decided to just turn all the auto detection options off, sync and then turn them all back on. I've tried this previously with no luck. Guess what, I had a lactate threshold update after today's run. Ha. Coincidence or that off/on toggle worked. I guess give it try. Let's see if it continues to work. 

  • 0 2 days ago in reply to Bob

    That's very curious Bob...

    I tried the same in the past week in three different run sessions (also tried setting a new threshold manually at the same time) but with no success.

    As you say that you had tried this before without success, I'll keep trying and trying, though I'm not very optimistic...

    On my FR955 my last automatic LT was detected on november 29th, just before the 21.19 december update!!!  Now I'm with 21.22 update installed and I'm simply getting crazy with almost not hope left. Garmin support said a new LT update will show up sooner or later...

  • 0 2 days ago

    So it took a while but I have now received 3 Lactate Threshold updates in the last 3 weeks. I did do a factory reset but I don't think this contributed. 

  • 0 2 days ago in reply to Bob
    Bob said:
    I decided to just turn all the auto detection options off, sync and then turn them all back on

    I tried this and I got an auto detection today.

    Unfortunately, I don't trust the LTHR value at all. I was typically around 148bpm (consistent with 90% of 165bpm) in the last couple of years, and suddenly 156bpm? it doesn't make sense. That would put my Max HR around 173bpm which is way too high.

    The pace kind of makes sense though, so I really don't know what to think.

  • 0 2 days ago in reply to Bob

    This might be the way to go. 
    I did a factory reset, but still no luck with an update to LT. 
    Will try the auto detection on/off option this week. Cheers :) 

  • 0 2 days ago in reply to Etupes25

    , my experience with the new algorithm has been that it occasionally incorrectly autodetects both my MaxHR and LTHR, giving higher than realistic values (just like yours). Garmin has enabled logging on my device and I've submitted them a couple of cases where this happens. Let's hope they can figure what's going on.

    Regarding LTHR pace, that's also problematic for me. It's winter now in Finland, so with all the snow and ice my pace depends on lot on where I run. I've used trail running activity to help the watch in realizing this, but when these incorrect LTHR autodetections happened, my LT pace was also off. Howeved, there's no way to fix this manually, because you can only enter manually your LT heart rate, not pace! (Luckily I have power estimation off for trail running, so that the watch doesn't try to give an incorrect running threshold power as well.)