This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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 TrippyZ over 6 years ago

You need to review your HR zones.

0 Browner40 over 6 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!

I had tried soft reset, as well as turning the option off and then back on again. I have had the issue before where it stopped working after an update and cycling the option caused it to start working again. In this case nothing worked. I tried everything I could think of over the course of almost two months and nothing fixed it. I had come to the conclusion that it must be my HRM-Tri not detecting the HRV change due to age or damage... but then my new Forerunner 945 detected a new lactate threshold on the first try, with the same HRM-Tri and the same HR zones that the Fenix 5+ had.

At this point I have no idea why it wasn't detecting... but it obviously wasn't anything I was doing since the new watch had no problem detecting it.

0 JessWillis84 over 6 years ago

am having the exact same problem with my Fenix 5s sapphire. It is so completely irritating and Garmin are no help.

My latest race Training peaks detected a new threshold (obviously from my watch and HRM-tri strap) but my watch didn't load a new threshold.

0 Dr Phil over 6 years ago in reply to JessWillis84

Quite possible that Training Peaks is using a different method to derive changes to lactate threshold. Equally possible that perhaps you haven't done enough to trigger a change in the Garmin world.

Have you been in touch with Garmin?

0 nmyeti over 6 years ago in reply to TrippyZ

I think this is probably part of the issue. I got a new LTHR while running with my 5x Plus yesterday. I regularly see updated LTHR and LT pace updates when using the Run activity with my HRM-Run.