Related
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

Garos
over 2 years ago

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!

  • 0 over 2 years ago

    I got several LTHR updates on beta 15.12 that synced over to Connect successfully. I haven’t had any since updating to 15.19 but I also haven’t expected any. 

    One thing I did note is that when I look at my current LTHR on the watch it says that the most recent value was a Manual Entry. Prior to 15.19 it listed the date of the most recent auto-detect and I haven’t added any manual LTHR values.

    Curious to see what happens when I get my next auto-detected LTHR. 

  • 0 over 2 years ago

    Just had a look at the .fit file for the activity that triggered the LT update with Golden Cheetah and Fit coverter. Both tools showed a detected threshold for that activity. After the workout, I saw the updated value in the performance glance on the watch. Now it is back to an old value on the watch and no sign of it in GC at all.

  • 0 over 2 years ago

    I also downloaded the garmin fit SDK and had a look at the fit file myself. The activity that triggered the LT detection has a value for LT HR and PACE stored. Browsing the developer forum these values are stored in message '140' fields 14 and 16. These give me the exact values I saw on the watch before everything got lost in translation.

  • 0 over 2 years ago in reply to nowster

    Total bandwidth for BLE is larger than ANT+. Some more info here on why devices matter

    www.muscleoxygentraining.com/.../dfa-a1-and-exercise-intensity-faq.html

  • 0 over 2 years ago in reply to andreef

    I can't believe we are back to square one with this:

    2022: LTH transfer to GC doesn't work for most users, after many months Garmin supposedly fixes it

    Jan 2023: Turns out that in the process of fixing GC synchronisation of LTH, Garmin destroyed LTH auto detection on the watch.

    Jan - May 2023: LTH auto detection on the watch does not work for several months

    May 2023: Garmin finally releases a new FW that fixes the LTH auto detection, but it turns out that GC synchronisation of LTH is borked again

    This is a parody. Silly me for getting my hopes up for the new FW after the prolongued beta phase for 15.XX. You can't fix incompetence.

  • 0 over 2 years ago in reply to rmullins08

    Hmmm, first time I hear read about that... Can't/couldn't imagine it being the case but who knows.

    Then again, I'd expect to have noticed these missed breasts in my activities...

  • 0 over 2 years ago in reply to 9610916

    Yeah can confirm this is happening. I've I modified the lactate threshold manually (46), reset my HR zones and did a guided LTH test. Shows up on my watch but not on garmin connect.

      

    Synced with garmin express and phone app. FW 15.19

    Also, the Running HR Zone based off LTH did get modified to 157, but the HR Zones themselves didn't.

  • 0 over 2 years ago

    Hello,

    being new to LT auto detection, can you please advise how it does work and what shall I do? I have updated my 955 to latest firmware and I use a HRM PRO+ strap.

    Can you please give me some indications? Thanks

  • 0 over 2 years ago in reply to dcaccount

    Make sure your max heart rate is set properly. Wear a HR strap paired to your 955. Then go run hard enough and long enough to trigger the auto detection. I was doing 8x2min yesterday and it triggered the auto-detection giving me new values post-run. 

    The watch itself also has a built-in test you can use:  "Lactate Threshold Guided Test" in the Training menu once you enter Run mode.

  • 0 over 2 years ago in reply to FlipStone

    I’m trying to find the actual research paper I saw on the subject at some point but striking out. I don’t think you would see gaps in the data, as garmin (and other devices) just smooth out the results

    twitter.com/.../1365220253219880963