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 1 year 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 1 year ago in reply to 8151143

    Happy to provide account details/data to help expedite fixing this issue.

  • 0 over 1 year ago

    I'm 2 for 2 w/detection and updates to GC Mobile and Web. Last time, I ran 8x2min and was given new LT HR and pace at end of workout. Today was, 8x45s uphill w/values given at the end of workout. So however the estimate is calculated, it doesn't require you to go run long sustained intervals or a 5km race. That said, it appears that Garmin recently updated the chart/graph in both locations. I could be wrong, but I seem to remember it being slightly different. 

    NOTE: my max HR is manually set by me. It is not using auto-detection.

  • 0 over 1 year ago in reply to 8151143

    message to garmin-sierra: would you be so kind as to check the status of my runs so as to evaluate my LTHR? It seems to me that it doesn't work at all. furthermore, even the segments, despite being recorded on the activity, are not displayed on the watch when I start and finish the activity. Thank you.

  • 0 over 1 year ago in reply to LinAlan

    Interesting. I'm assuming you're saying that you received an auto-detected LT update and it actually sync'd with Garmin Connect and you're using 15.19 firmware on your 955? I just received an updated LT on Sunday and it still will not sync with GC...

  • 0 over 1 year ago in reply to ShawnPDX

    Yes. 15.19 on 955. LT update (HR and pace) at the end of the run. It also syncs properly. Appearing on both Garmin Connect web and iOS app. Prior to 15.19, it never updated. It has had the same values from my 935 which sync'd over when I got the 955 over a year ago.

  • 0 over 1 year ago in reply to 8151143

    I've been trying to troubleshoot this issue and tried to Wi-Fi Sync through the watch. When I do so I get: Unable to connect to Wi-Fi. Error Code 0300. Could this be related?

    Are you able to do Wi-Fi Sync?

  • 0 over 1 year ago in reply to 8151143

    After seeing your message, I gave it a try. Same error as you. Although I have WiFi enabled, I guess my 955 has been syncing over Bluetooth once in range of my phone. Someone else started a separate thread about the WiFi error 0300. You should probably go add yourself to the list.

  • 0 over 1 year ago in reply to 9610916

    This investigation has been escalated, but I don't have an update right now unfortunately. 

  • 0 over 1 year ago in reply to ShawnPDX

    This is what i see too. Updated HR on watch but not on app.

    Also the pace seems off (HR updated but not pace despite the 5km been 4/km never updated from the 5:30 it was at before, but HR updated (again only on watch)