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

15.19 and lactate threshold detection

From the 15.19 change log =

"Fixes an issue that could prevent lactate threshold heart rate auto-detection from working correctly."

Finally the end of the lactate drama? Or at least one step in the good direction?

As I won't run any "around lactate threshold" session until next week, I'm looking for feedbacks :-) thanks!

  • I think this has been fixed going back several betas. When I heard that it was fixed in 15.12 I downloaded it and have been on it for a few weeks (until today when my watch updated to 15.19). I’ve received 4 LT auto-detects in that time and they all show up in Connect. 

  • Kind of unrelated question but do you need a chest strap for autodetecting LT? I know you need one for the guided tests, but I've seen contradicting info on autodetects.

  • You need a Garmin chest strap. I use the HRM Pro+ but I think some other models are compatible as well. 

  • Any ANT+ chest strap works. I have a "no name" brand and that works fine.

  • Good to know. Not sure why I thought it needed to be a Garmin strap. 

  • Has anybody tested the LT auto-detection with a Polar Verity Sense HR sensor (wearing on the upper arm)?
    My Polar sensor is connected via ANT+, but I never get an LT auto-detection. I've not tested it with the new Firmware 15.19 yet, fingers crossed...

  • While any ANT+ does work, BLE is better for LT detection is there are fewer artifacts in the HR/HRV data.

  • I also finally got a detection on 5.19. I had to lower manually set LT so that I would actually spend enough time in zone 5. However, there are two issues that I don't quite understand

    1. I swear that I pushed the accept button on the watch but now the new value is nowhere to be found.
    2. When lowering the manually set LT there was some unexpected behavior of my zones. Zones are set as percentage of LT. When I manually update the threshold then the zone percentages get changed to match my old heart rate ranges. I would expect this to keep the percentages the same so that zones would no reflect different ranges according to my new LT.

    Has anyone else seen such behavior? Just wanted some confirmation before filling bug reports.

  • With regards to point 2, I think that’s the expected behaviour.

    When you set a new LTHR, either manually or automatically, you have to go into your HR zone settings and Reset them so that the top of Z4 aligns with the new LTHR. Or at least I’ve always had to.

    It would be nice if the zones updated automatically when the LTHR changes but I guess they decided that it was preferable to require additional user intervention before changing the HR zones. 

  • Using 15.12 and 15.13, the auto-detected LT always transferred to Garmin Connect. Using 15.19, I have had 1 auto-detected LT so far and it did not transfer to Garmin Connect. Hopefully that was just a glitch and they transfer normally in the future.