Lactate threshold activities

ovekvam 15 days ago

The latest software has this new feature:

Lactate Threshold estimates are applied automatically after training with heart rate.

But what are the requirements to get a new lactate threshold estimate? The Garmin documentation still mentions guided running exercises, but that is now removed on our watches.

I have gotten the impression that we can now get estimates by using the wrist heart rate sensor, and from activities that are not necessarily done at very high intensity, but which activity types are eligible?

My last estimate was from a guided outdoor run in august 2023. It would be nice to have a new estimate, more in line with my current shape.

0 9820003 15 days ago

might be not what you are after exactly, given all changes in soft etc. but one thing helping getting new reading (historically) was dropping max hr, chance to get new lthr was up. not sure with new soft, too scared to update from 18.xx ;)

0 RDW 14 days ago

The estimates are so inaccurate now they arent useful.

Its doing them for activities regardless of terrain, surface condition, weather or anything else.
I get 8-10bpm variation in what it detects depending on exactly what im doing, with whom and on what terrain.

0 ovekvam 14 days ago in reply to RDW

But it is all about outdoor running, no other activity types?

0 global_local 13 days ago in reply to ovekvam

Maybe it works indoors too, if you use a Stryd as a pace/distance device. But if you use a watch only, then you need a GPS signal for a pace/distance.

0 Scheddar 12 days ago

interesting, my last estimate is also from August, no way that's a coincidence

0 RM 1 day ago

I've noticed that this feature worked, at least apparently, after the update to the firmware version 20.19. Right after the first run using GPS and HR sensor from the watch, a threshold pace and HR was defined...

Nevertheless, I've after that, accomplished tens of other runs, on the same settings, and this lactate threshold was never updated! (?)

I've recently updated to 21.20, and no changes on this matter.

I've also seen the same complain on the FR965 forum...

Garmin-Sierra, any suggestion or comment about this situation?