How to setup auto detect heartrate and lactate treshold?

Could it be caused by the manual setting of 150 bpm as treshold? Because my treshold test did not feel really hard. The max heart rate is gave me as goal was 178. But that is not close to my max. I certainly can run with 185 for a while. I think the test wants measurements in all the zones, and my zones were defined lower than actual, because of the manual setting of 150. Does that make sense?

If so, my next test should be a bit harder, and again give me a higher lactate treshold.

Again, I trained for a marathon during a year and my 32km pace was 5.20. After having run the marathon, I gave the 955 a goal for a 10 km, but my trainings are bad. Base Base Base, at pace of 6.20. I had a sprint training once with spints of [email protected]. That is really no effort to me. In my believe the algorithm is staying behind, my vo2max is decreasing all the time, also my race predictions. I hope it turns for the better after a few weeks.

DaKo said:

think the test wants measurements in all the zones, and my zones were defined lower than actual, because of the manual setting of 150. Does that make sense?

The threshold test doesn't care about your zones. It is using a ramp system to detect certain dynamics in HR and HRV to identify the second ventilation threshold (aka "anaerobic" threshold, close to the lactate threshold).

DaKo said:

That is really no effort to me. In my believe the algorithm is staying behind, my vo2max is decreasing all the time, also my race predictions

Yeah, there is something wrong with the metrics maybe because of past training patterns or data capture issues. THis will sort itself out over a few weeks. In the mean time, you could use a Garmin Coach program for the 10k. These plans start with a benchmark run to gauge how close you are from your goals and they will be based on pace. They are also designed to be balanced, so this will help sort out the training history for all the training status metrics if you keep using a chest strap.

I just posted a question which is sort of in-line with the topic in here. I am suspecting that the old (pre-HRM strap) LTHR value which automatically got computed (and shows as manually entered for some reason) is higher than the actual value if I was to re-run the LTHR test. That, and I have never seen the values change after they were initially established automatically, and I get "--:--" for my Lactate Threashold Pace despite having a LTHR.

Anyway, I am going to re-run the LTHR Test today since I bought a HRM-Pro+ earlier this month. Based on what I read in here, is it the case that I should:
1. Set LTHR manually to something lower than what I expect the "actual" value to be, like 150 (vs. current 167)?

2. Set HR Zones back to use MaxHR (since LTHR value is artificially suppressed before test)?

Any suggestions as to why the LT Pace value is not being calculated would be helpful too.

my response in your own thread

Thank you. Yes, it makes sense that a manual LTHR value and zone boundaries would not impact the LTHR test or calculation. In my case, it sort of looks like LTHR was "stuck" at an old estimated or manually entered value from before I had the HRM strap, and which probably existed across at least 2 firmware updates. I detailed what all I did today in the thread where I had some questions about all of this.

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/337166/lactate-threshold-test-maxhr---questions-about-hr-settings/1635014#1635014

I'll re-run the LTHR test again in a couple of days to confirm this, but it is looking probable that the LTHR test is heavily influenced by whatever MaxHR value is set during it. It does sort of make sense. Since I had deliberately tweaked my MaxHR value to something low, it definitely impacted the HR targets during the test. That isn't to say that the LTHR value is wrong, but the difference between the old and new value is pretty enormous, enough so that I want to try again just for repeatability. Also, the fact that I am now getting a LT Pace value for the first time ever seems like a strong indication that there were some software issues impeding proper function.

So, I give you and update. As I let you now in an earlier post, my training intensity seems to increase. Today Garmin finally let me run a treshold run with 16 minutes @4:45/km. Have not seen that since since half of april! After the run, My treshold HR was updated from 158bpm to 161bpm, and maxHR from 192 to 193.

Finally my training intensity is going the right way (still not far enough), and I confirm the auto update of LTHR and MaxHR is working,

Happy at the moment :-)

I am in the same situation now, and also feeling more happy with the watch. It seems like it is actually working properly now that autodetect can perform its function. Not sure why it was broken, but at least it seems to be OK now!