I've been used 955 for 8 monthss. I set auto detect max. Heart rate and threshold heart rate on. I got max. Hr update once in awhile but I never got threshold heart rate update I've always used coros heart rate monitor. Is there something wrong?
I've been used 955 for 8 monthss. I set auto detect max. Heart rate and threshold heart rate on. I got max. Hr update once in awhile but I never got threshold heart rate update I've always used coros heart rate monitor. Is there something wrong?
Hr update once in awhile
Max HR can be updated with sub-maximal efforts, even during "easy" runs, while...
I never got threshold heart rate update
...you would need harder efforts (threshold and above) to potentially get a LTHR and threshold pace/power update.
So if you only had mild efforts, it is very possible no LTHR was detected.
Do this to test this assumption: run as fast as possible, but keeping the pace steady, for at least 30mn (it is a field threshold test). Your LTHR will be your average HR for the last 20mn. If your pace has been steady, same thing with the pace. The key is to keep the pace as steady as possible. It might take a few trials to get the target pace right. A test is an excellent workout anyway.
The watch proposes similar threshold workouts for daily suggested workouts, but tend to be a bit short. So they might also get you an auto-detection. Anaerobic and VO2 Max workouts also give me auto-detection, but the pace value is too low in my case.
Is there something wrong?
If you have run real "threshold" runs, you should have had at least one auto-detection. If you don't, there is a chance that the auto-detected Max HR is too high: the auto-detection is looking for changes in the correlation between HR/HRV and pace in a region around 90% of Max HR. If Max HR is too high, your threshold runs might not take your HR in that zone, and the watch might not be able to identify the change in correlation in a "valid" zone.
Another possible situation is that you have an older LTHR/Pace from a previous device that has been synched to the watch (I am not sure if that synching is possible, and if it were, if it would prevent the auto-detection). But just in case, you can check on Garmin connect in reports whether there is a lactate threshold set of values.
You could try to lower your Max HR by 5 bpm and/or reset the watch to factory settings, then go run your best 5k ever. Another excellent workout that could trigger an auto-detection.
Otherwise, you will have to call Garmin Support.
My watch said my max. hr is 177. I ran 400-500km a month for several months. And I've been done all kinds of workout, including long temp, marathon pace workout. I believe my heart rate keeps in the zone many times.
including long temp, marathon pace workout
You don't mention threshold, anaerobic or VO2 max workouts. These are maximal efforts, interval-based.
Some view tempo as equivalent to threshold. As I said above, do a field threshold test and see if the watch detects your threshold.
I did all kinds of workout with different places 400/800/1km/1mile/2miles/5k/8k10k interval.
I also did a 10k all out effort last week which lasts about 40 mins. No update on lactate threshold.
I also did a 10k all out effort last week which lasts about 40 mins.
Thanks for clarifying. So yes, something is not working correctly with your set up.
DCRainmaker indicates that the Coros heart rate monitor doesn't provide R-R/HRV information.
Did you try with another HR monitor, preferably a chest strap like the polar H10 or the Garmin HRM Pro?
Right, the coros heart rate only provide heart rate info. The heart rate is quite accurate . Is that not enough for threshold heart rate?
Well, the threshold detection is based on HRV analysis. Garmin requires a chest strap for it, although this might have changed with the latest firmware on recent watches, which will now make detection work with the HR Wrist.
Apparently what is required is high quality R-R data. So I am not 100% sure that you have an issue with your HR monitor, but if you have a HRV capable chest strap this is worth trying.
You could contact Garmin support about the exact requirements for your watch and about changes in the requirements with new/upcoming firmware for your watch.
So if you only had mild efforts, it is very possible no LTHR was detected.
In fact, I was wrong here. With the latest firmware on the Epix Gen 2, I got a lactate threshold detected during a long easy base run, where my heart rate remained below Zone 3 the whole.
Unfortunately, it appears to be a poor prediction based on my previous tests (Garmin or manual). Instead of getting an LTHR around 147, I got a new LTHR at 151. The pace was 10s/mile faster than usual as well. A bit disappointed with this new feature.
Yes, it seems auto lactate threshold detection need not only heart rate but also hrv. Coros arm hr doesn't support hrv data. I also updated the latest firmware update. In the description, it said no need hrv for LTHR. Still didn't get any update yet
The new FW 21.19 allows LTHR detection with built-in OHRS only (although it is not that precise). Take a try.