Lactate Threshold not auto detecting since March

Has anyone else had an issue with the Lactate Threshold not being detected? My fitness level has greatly improved and I feel like my threshold numbers are no longer accurate. My last threshold was detected March 14th and even though I have done several races and threshold runs that "should" have updated my numbers since then I have not gotten one.

I have tried turning off the option and turning it back on(I have had that fix it in previous watches) and have done a soft reset several times. I have been on several different Betas and now v7.10 in that time.

I just purposely did a building threshold run today that definitely should have detected a new threshold. At the previously detected threshold HR, my pace was about 1min/mile faster and it still didn't trigger. I'm using an HRM-Tri and was running on a flat, paved surface with very little wind. I've attached a screenshot of the pace graph with HR overlaid. I can't see any reason for it to have not triggered unless I didn't hit my threshold at any point in the run... which seems highly unlikely since I had a slow built from 9:00 min/mile and 143bpm to a 7:30 min/mile and 173bpm. My current last measured LTHR was 8:35 min/mile and 164bpm. ciq.forums.garmin.com/.../1478238.jpg

Top Replies

All Replies

0 JanH over 6 years ago

Hm. Mine never auto-detected it. I did a dedicated Lactate threshold test once and then it got some values... But might be because I never did a training before from which it could have calculated it.

0 TrippyZ over 6 years ago

I suggest you follow the on device LT test. I get a 'new LT detected' roughly every two weeks.

0 Browner40 over 6 years ago

I have never gotten the guided test to successfully detect a threshold. Across three different watches and over the course of three years the guided test has never worked to detect a threshold for me.

I used to get an update when I did a hard steady effort, or a negative split 5k like I did above. But since March, I have not gotten an update from either the guided test or any hard efforts... even though my VO2max and fitness level have definitely gone up. Even if the value is the same it should have still detected it.

TrippyZ when was the last LT detected for you? If you go on your performance widget and scroll through to the Lactate threshold screen it should give you a date. What SW version were you on? Are you using GPS, GPS + Glonass, or GPS + Galileo?

0 cichykot over 6 years ago

It's not a true. Did me new threshold three days ago. With HMR belt of course.

0 Browner40 over 6 years ago

cichykot it is true, for me. I'm just trying to narrow down why it is true. What software version are you on? What was your GPS setting at? I think I changed my GPS setting from GPS only to GPS+ Galileo around that time and now I'm wondering if that had anything to do with it.

0 cichykot over 6 years ago

I'v had 6.71 beta, another thing that he has not detected anything for a long time, and how he detected it was 4, 27 / km where I actually have some 4; 10 hahah
ps
GPS doesn't matter I'v have a Stryd.

0 TrippyZ over 6 years ago

When was the last LT detected for you? If you go on your performance widget and scroll through to the Lactate threshold screen it should give you a date. What SW version were you on? Are you using GPS, GPS + Glonass, or GPS + Galileo?

Two days ago. I am using Fenix 5 version 13 and always Galileo. I am keep my HR zones bang up to date.

0 Browner40 over 5 years ago

Just as an update.... since no-one else seemed to be having this problem. I did another threshold detection run today with my new Forerunner 945 and it detected my lactate threshold pace and heart rate with no issues. Not sure what state I got my F5+ into that made it stop detecting, but the new Forerunner is not having the issue at all. Maybe a factory reset would have fixed it, but I guess now we will never know.

0 rugby4all over 5 years ago

Soft reset (hold the power button for ~ 20s or so and then restart the watch) did it for me after I noticed no lactate threshold update for over a week...
Hope it works for you too!

0 Mathias.Bjorklund over 5 years ago

Mine doesn't auto detect either. Stopped roughly one year ago. (It was then an fenix 5, now a 5S+)
I believe that it has got some setting related to HR incorrect somewhere, maybe internally which is not even shown in the GUI.
I had the feature since it first apperared in fenix3 and then it worked flawlessly.

When I try to do the guided test it uses very strange HR zones and force me to do running in 4 minutes above 164 beats/minute. I cannot during interval training reach those targets, especially not for 4 minutes. My LTHR is around 150-155 @ 4.10 pace. Yes, the Max HR is set correctly which I can reach during race when running for a long time with high intensity (176)
When the guided tests worked in the beginning i should run for 3 minutes @158 BPM, which I can reach.
Of course I use a real HR belt, and not the random-generator on the watch.