Related

Running Lactate Threshold spiked after update 22.24

jeff.e.low
22 days ago

Has anyone else had their Running Lactate Threshold explode since updating the watch software? Did the calculation change for this in the new release?

Today my watch updated pretty much right before I went for my run, and it's now on software 22.24. I did a workout of 5 x 1km at 5k progression pace. I wore an HRM Tri for this run. When it was completed my threshold pace notified that it jumped to 182 BPM at 4:25/km. It had previously (for years) always hovered around 170 BPM and 4:50/km. Here's my chart for the last year.

  • 0 22 days ago

    Hi, the problem exists since v 21.19. There are some other threads here in the 955 and 965 section.

    I wrote a few days ago Garmin customer support again with my experiences

  • 0 22 days ago

    As Jo952 said the problem started in the autumn with v21. I had a recent lab tested threshold and quickly saw that Garmin values were becoming unrealistic. I could no longer complete my threshold runs. Eventually I ended up with injuries, so be careful. 

    Set the LT manually and do a test to get a reliable value.

  • 0 20 days ago

    This is an issue of the last firmwares, dont follow the suggestions of DSW if they are too hard, do at your pace

  • 0 20 days ago

    I don't see that. My pace dropped a bit after I stopped running due to an injury in November. After that, everything gradually returned to normal values (both for running and cycling)

  • 0 1 day ago

    Same here with the latest version. They increased my threshold by 8-9 points for no reason when whenever it detected me with the old method it was in a similar range to my stress tests. I have the maximum frequency set to manual because it has always detected it excessively high. Everything it auto detects is wrong LOL. VO2max after the last update is also very wrong.

  • 0 17 hours ago

    Mine jumped 21 today after a run! I thought I would do a guided LTH test tomorrow but it appears that has been removed from my watch! I’m getting really tired of all the issues with Garmin lately. It’s sad to say but after 15+ years I’m going to be looking to switch to a different brand Disappointed relieved

  • 0 17 hours ago

    No response from Garmin on this issue?

  • 0 15 hours ago in reply to Jwoodruff

    for me, the automatic lactate pulse detection works correctly for both running and cycling. The results I got are about the same as those previously determined using the corresponding Garmin tests. In this case, the main thing is to ensure the accuracy of the pulse and pace data. for pulse, I recommend using a chest strap. if you have a Garmin HRM pro chest strap, you should make sure that it is not used as a source of pace data.

  • 0 14 hours ago

    For me, the new LTHR auto detection produced unrealistic values in the winter (and I had to manually revert to an old value), but has now returned to producing values that are in line with my old ones. 

    I feel the new algorithm seems to be too prone to produce too high values. It may of course also depend on the kind of run, I'll try to remember to repeat the run that produced the unrealistic values earlier.

  • 0 14 hours ago

    I still experience the problem, running with a HRM Pro Plus, which is set to Pace Indoor only. The automatic detection reported a LTHR of 162 bpm and a LT Pace of 03:38/km. My autodetected MaxHR is 169. My LT should be around 03:55-04:00 based on my 10k PR (03:50/km) and my 21k PR (04:07/km). Garmis has placed logging on my device, but it´s so hard to achieve an update, with such a high auto-detected LTHR value. With the manuall test it was perfectly fine (LT Pace 03:55 and LTHR of ~155bpm). I encountered another problem, Garmin Coach is massively overestimating my capabilities (to high goals) and race time prediction say, I could run a marathon in unter 3 hours, while my marathon PR is 03h:36min. I hope, Garmin finds a solution for that problem.