Lactate threshold not updating

I've been using my Fenix 5 since march 2018. Initially, the lactate threshold speed was updating regularly, until a few of months ago. I've been running a lot more than usual the last months, and he 10k prediction is updating OK, from 45 min to 39 min, which sounds about right. But the lactate threshold speed is stuck at 5:06 min/km, and I know that is too high. It’s been like that since 27^th of March. The lactate threshold pulse is also stuck at the same value (163), but that may be correct, I don’t know.

I’ve set the Physiological Metrics to automatic and tried to manually lower the max pulse from 193 to 183, but nothing changes.

Do I have to perform a guided lactate threshold test to make it update? I seems

(I am 49 yrs, VO2 54)

0 mcalista over 6 years ago

You have to generate sufficient data during a run both below and above your LTHR for the watch to be able to identify the inflection point in Heart Rate Variability that is associated with LT.

The guided LTHR test is designed to generate sufficient data, but the watch will generate LTHR during any run IF there is sufficient data in the right categories. A series of over-threshold intervals will normally work well. Or just do your normal run, and finish the last 500m at an over-threshold pace.

0 TrippyZ over 6 years ago

Have you done any Z3>Z4>Z5 runs? Using HRM strap?

0 mehmetozturk over 6 years ago

As I red this, I ran the 10th km fast(4:30/km) and get an LTH update!

0 torrei126 over 6 years ago in reply to mehmetozturk

Maybe I can try that? Thanks.

0 tickerguy over 6 years ago in reply to torrei126

Yeah as noted if you're not doing a "guided test" the workout has to be long enough and hard enough to cross over the threshold and the data received has to be sufficient on both sides to calculate it. You also have to have a chest strap on -- the optical reader isn't precise enough.