Auto-detected lactate threshold is horribly wrong
-
I’ve noticed that my stats now include lactate threshold at 145 BPM. I suspect it is a new feature introduced in the last update together with ZoneSense fields. I don’t recall seeing that before. It appeared after a run when I wore a chest strap, which I don’t normally do.
The problem is that is horribly wrong. I did a guided lactate threshold test with a Garmin watch multiple times, and it was consistently at 161-163. The one detected by Suunto is at the bottom of my zone 3, just above my aerobic threshold. I can certainly run with my HR at the upper 150s and low 160s for a long time, so my lactate threshold cannot possibly be that low.
Can anyone confirm if this is a new feature and how exactly LTHR gets calculated, and why it was detected so wrong for me?
-
@sky-runner hmmm, mine is fairly accurate. It may be due to the differences between belt and OHR. For me none of the Suunto watches provide accurate OHR, none so I wear a chest strap most of the time.
-
@sky-runner the only new feature around this after last watch firmware is that Suunto ZoneSense post activity is now native as long as a chest strap was used (it isn’t during activity unless you enable S+ ZoneSense).
So that Anaerobic HR threshold field you’re seeing, it’s coming from ZoneSense only, and if you are not familiar with ZS you’ll have a ton of questions on this value.
