Related

Recurring problem regarding detected Running Lactate Treshold

live_gn
15 days ago

How is it possible that my watch (continue to) define/detect Running Lactate Threshold of BPM (170) and pace (3:54 min/km) when my MaxHR is set to 174 BPM and I know that I run 5km at apprx 4:05 min/km and 10km 4:24 min/km? I am using HRM-Pro (except during Trail Run which for me are very easy runs and Record Vo2Max is turned Off).
The Auto Detection in the Heart rate-settings for MaxHR is turned Off and Treshold is On. Vo2Max is detected to 60 and I am 58 year's W. I am not using footpod to measure pace/speed. My watch has been given these obviously wrong measurements the last months (actually longer). I was hoping that the SW update to 23.20 should give more realistic measurements, but no. Do anyone have a solution to solve this?

Top Replies

All Replies

  • 0 5 days ago

    How do you want these measurements to be true, if you have turned off automatic HRmax detection? turn it on. Then the proportion will match. Because your HRmax is probably higher than 174. Personally, in my case Garmin was wrong by 1 bpm relative to treadmill performance tests. So I think this is enough evidence that Garmin estimates do not differ much from reliable tests.

  • 0 3 days ago

    Thank you all for your thoughts. My conclusion is that there is no definitive answer, and that the Garmin logarithms are messing up the analysis data at the moment (since last year). It makes no sense that the my watch don't use the input I have entered. I had hoped that Garmin support would have stepped in, but it doesn't seem like it. Closing my question - if that's possible