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

Base runs being recorded as Tempo

Firstly, I’m running the latest version on my 965. I have:

- LTHR = 169bpm

- Max HR = 196bpm

- Zones based on %LTHR

- Auto Detect for Max HR, Threshold, FTP

just diid a 2hour base run with average HR @ 149bpm. The suggestion was 146bpm. However instead of being recorded as base effect it had been recorded as a Tempo run. I find this happening a lot. Can anyone explain why and if there is a fix please? I’ll post my graphs below for your perusal. 




If there is any other information you require that might be helpful I’m happy to provide. 

  • Make sure you go to Sport Heart Rate —> Running and enter the proper numbers with a couple changes

    Z5 = 100%

    Z4 95-100%

    Z3 = 90-95%

    Z2 = 85-90%

    Z1 = 60-85%

    You can start Z1 at 50% if you want

  • Hmmm something is not quite right. When i go into these setting this is what is preloaded:

    Z5 = >100%

    Z4 = 95-100%

    Z3 = 89-95%

    Z2 = 80-89%

    Z1 = 65-80%

    If i click on zone 1 to enter new values i get a choice in numbers from 25 to 79 (no higher). It doesn't even let me choose the 'lower' or 'upper' value. It just defaults to the selection being the 'lower' value. 

    For:

    Zone 2 I get choices 66-88

    Zone 3 I get choices: 80-94

    Zone 4 I get choices: 89-99

    Zone 5 I get choices: 96-115

  • On the watch, reset the zones. There is a bug where the zones are changed on certain events like a new HR Max detection. Sometimes, you have to switch the zones to another system, reset, switch back to your original system and reset again. This is another reason why other users are disabling HR Max detection.

    Having properly defined heart rate zones is important for you to design your workouts and to set expectations, but it is not your issue. The targets for the DSW are using % of VO2 Max, not your threshold zones. Of course, the data generated by the watch, including the LT detection data, is used to determine your VO2 max, but indirectly. In fact, if your DSW threshold targets are close to the value detected by the watch (LTHR, LT Pace or LT Power) it is a sign that the data set is pretty good.

  • Thank you. I have orders a new HRM Dual so I can get the Lactate Threshold Test to inform my data better. 

    I have done what you have instructed above. However it will still not allow me to enter in a %value of 90 for Zone 2… 

    Click here to play this video

  • Any changes are always to the lower value. Start with Z5 and work your way down to Z1. Whatever you set for Z5 will then be the upper value for Z4 and you can change the lower value for Z4. The lower value of Z4 will then be the upper value of Z3 … and so on. 

    I find it easier to make these changes on Garmin Connect. 

  • Thank you. It worked through Garmin Connect.

  • If you have it set to “Based on %LTHR” and LTHR is set to 169, your next run should show Z3 starting at 152.

  • Yes, I can confirm that is the case. 

    I note 2 is very small under the current setups: 144-151bpm is this how it should be?

  • Re: heart rate zones. I am surprised you have to enter % manually. Unless you have had some lab test done to determine LT1 and LT2, the standard % should be good enough.

    You'd get the standard % just by resetting the zones. But you don't, do you?