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

Automatic Lactate Threshold calculation is broken

sseddie
over 5 years ago

Hi,

After switching my Forerunner 645 Music (because of hardware issues) the automatic Lactate Threshold calculation does not work anymore.

I don't mean the Lactate Threshold test (I never did one, not on the new and the old Forerunner), I'm talking about the LT calculation after finishing normal running exercises. I stil get the messages that the Lactate Treshold has improved or not, this is displayed in the activity protocol details (Training Effect).

But the Lactate Treshold displayed in the Training Status widget is not being updated. It always shows the last calculated LT value from my previous Forerunner 645 with the addition "manual entry" (I've never entered the value). The Garmin Connect Mobile app also does not show any calculated LT values anymore, the LT statistic graph stops at the day where I replaced my Forerunner 645.

Does anybody has the same problems and a solution?

Bye, Stefan

  • 0 over 5 years ago

    Addition: I'm always using the Garmin heart rate chest strap and the Forerunner has the latest firmware (currently 6.20).

  • 0 over 5 years ago

    Hi,

    I observed my LT graph stoppen some time in June.  I assume it was with a FW update (5.20 to 5.70). Anyway with each FW update since 4.20 I got no improvements, but new bugs... 

  • 0 over 5 years ago in reply to bueffelmichi

    Interesting, the replacement of my FR 645 Music was also in June. So sad, the story of bugs...

  • Former Member
    0 Former Member over 5 years ago

    a few LTHR posts pop up lately Slight smile

    a few links when not already found and read...

    lactic-threshold

    jupjap said:
    problem solved (for me): i deleted the HearRate-profiles for running, swimming and cycling (as mentioned in the posting #13 above) and did a normal run but with a longer sprint at the end, to get above my lactric threshold heart rate. And everything went as expected: new lactic threshold value autodetected: save and accept as new values?:yes .
    problem solved for me. (the heart rate profiles are also there again but only running is filled with the correct new values)

    lactate-threshold-detection-issue-after-reset-factory

    mcalista said:
    There is an ongoing issue that after firmware updates, the watch can import incorrect HR information from Garmin Connect including zones, LTHR, change of zone calculation method, etc. I suspect that your factory reset has triggered the same problem.

    Set your zone method to be %LTHR in GC and perform a sync, and then do a run that is likely to result in LT detection (ie. including sustained pace below, and then above, your likely LTHR). This should restore good HR datapoints to your watch.

    the-best-hr-zones-setup-method-not-working-lt-test

    Fenix X said:
    1. Deleted all values & zones in GC app + garmin web + fenix 5 
    2. I left just Profile info +  Max HR based on 220 - age
    3. Set only one zone 4 all sports based on Max HR  (zones running + swimmind deleted)
    4. Set all detection automatic (max HR, LT , aver HR at res)
    5. done LT Test all worked perfectly!  watsch set new zones based on LT everything back to normal...

    The only srange thing is I get very Low  '''LT  154 bpm at 4:53  m/km peace ''
    ussulay i were around 168 bpm at 4:51 peace... 

    But let's move from here & see what's happen enxt... 

    happy & safe sporting

  • 0 over 5 years ago in reply to Former Member

    Thank you for this valuable summary! I will test and check     

  • 0 over 5 years ago in reply to bueffelmichi

    Thanks a lot for the answers! It seems that this problem happens when the user has multiple heartrate profiles for different sport types. In my case there's just one generic HR profile for all sport types, so I can't delete it for testing the workarounds.

    Please let us know whether this works four you.

    Bye, Stefan

  • 0 over 5 years ago in reply to sseddie

    Stefan, sorry for not replying sooner, but I wanted to observe over a frew runs what happens. I  set my profiles to "LT-based" for overall, running and cycling. I set my last known threshold (165 bpm). However, I never got a message about new zones/thresholds yet, so the data since the update are still not there for me. Maybe I have to do a few more runs.


    My next try is now to delete all profiles except the one generic HR profile and see what happens.I'll let you know...
    Oh, and maybe I need to do this:

    https://www8.garmin.com/manuals/webhelp/forerunner645/EN-US/GUID-1B0C9B93-01CD-4A0C-A30F-B815C0347159.html

    Never did this before (and got the LT values data anyway in the past). 

  • 0 over 5 years ago in reply to bueffelmichi

    Thanks for your information, would also be good to know what happens after a few more runs.

    I hope Garmin has not removed the automatic LT calculation at all with one of the last firmware upgrades. Probably most runners will never execute manual LT tests, because they're very intensive. Would be too sad...

  • 0 over 5 years ago in reply to sseddie

    The automatic Lactrate Treshold calculation works again for me, yeah Slight smile

    That's what I did:

    • I've entered a manual lactate treshold which is slightly below the last autmatic computed value (157 instead of 162 bpm).
    • I've set my HR range profiles to "LT-based" (one profile for all sport types).
    • I've done a few runs before and today an interval training. It seems to be important to have trainings where you are below and above the lactate treshold for several times.

    After the interval training I've got new computed LT values (BPM and pace) and the values look valid.

    I'm using Garmin 645 Music Firmware 6.20 and Garmin Connect App 4.22 on Android 9.0.