lactic threshold

Former Member
Former Member
Hi,
Is there anybody for who LT auto dectect works ? As you could see on my Garmin connect's screen capture i'm superman. Of course i always run with HRM chestbelt and auto detect is on.
Any advices ?

Nobody seems to use the function :(


Fenix 5X vers 7.6 ciq.forums.garmin.com/.../1299712.png
  • Former Member
    0 Former Member over 7 years ago
    I did it by the past, it's not hard. Just stay in the green zone until you couldn't. Here the watch was unable to set a LT.
    More of a bug or hardware problem, one more. See here : https://forums.garmin.com/forum/into-sports/running/forerunner-935-aa/1297381-lactate-threshold-too-low-heart-rate
    The watch is going to return at Garmin.
  • it has something to do with the update to 7.60 , since my lactic threshold also changed to 46bpm (the exact same value as different other users) .
    The last automatic-measured value (before i updated to 7.60) was 179bpm. After the update, i got high intensity-minutes for a normal run (and 57hours of suggested resting time), after the same occured at the second rund two days later i had a look at the lactic threshold and found it @46bpm.

    I just deleted the userprofile for run, under the option-menu "heartrate" on the watch itself (i cant remember if i created this userprofile on my own or if it was already there) , changed it to many different values manually, synced, changed, synced.... now it remains at 179bpm on garmin connect mobile + online ... no matter what lactic threshold values i enter on my watch, the values in garmin connect mobile and garmin connect online do not change at all (always 179bpm) no matter if i sync via bluetooth and/or wifi . . .I am curious what will happen to the lactic value after my next runs.
  • Former Member
    0 Former Member over 7 years ago
    I called the support and they took me for an idiot. For them it is because I do not use a sensor of their brand and they do not want to take care of it under guarantee. This brand is a swindle.
  • just to say I got a lactate threshold detected last night. It was on a 935 but the software closely matches the F5. It was during a track session 'diminishing returns'. 300easy, 100hard, 200easy, 200hard, 100easy, 300effort, 400easy, 400effort. Repeat for 30 minutes.
  • Former Member
    0 Former Member over 7 years ago
    You're a lucky guy. I tried to set manually a LT value but the watch came back to 46 bpm after my last run 10,43 km 4:28/km.

    Somebody knows if it is possible to return to an older version of the OS (i'd try the 5.84 os beta version) ?.
    Here we can find all versions : http://gawisp.com/perry/fenix_D2_tactix/
  • mine looked fine 4:04/km 158bpm (max is 174)
  • problem solved (for me): i deleted the HearRate-profiles for running, swimming and cycling (as mentioned in the posting #13 above) and did a normal run but with a longer sprint at the end, to get above my lactric threshold heart rate. And everything went as expected: new lactic threshold value autodetected: save and accept as new values?:yes .
    problem solved for me. (the heart rate profiles are also there again but only running is filled with the correct new values)
  • Former Member
    0 Former Member over 7 years ago
    Ok thanks. I'll try. Did you also turn off this heart rate profiles in GC app?
  • i learned, that it can cause many problems to modify values/rates/profiles on the watch AND on GC-app/GC-online. Only change it on the watch itself and then sync two times.
    Best regards, Thomas
  • Former Member
    0 Former Member over 7 years ago
    Alléluia ! In community we trust not in GarminSupport. I followed your advice and it works! I have again a little bit low detected lactic threshold I find but I ran slowly and accelerated over the end. I hope that for my next running that will work again with a more realistic result. Thank you again jupjap and the others guys.