Max heart rate changed in the wrong activity

Hi, 

I have automatic detection of Max Heart and FTP. Also I have two profiles: Predetermined and Cycling. I understand predetermined should be used mainly for running and any other activity and cycling for when I go on the road or the MTB.

However every time I go running my max heart rate for cycling is updated. 

As an example, I cycled five days ago and my cycling max HR went to 193 bpm for quite a few seconds. My cycling heart rate was increased to 192 bpm.

I did a run today, max HR during the run was 165bpm. At the end of the run I got a notification that my cycling heart rate was decreased.

The same happened to me a couple of weeks ago where cycling went down to 184 after running. It went up again after cycling.

Note: I use Garmin chest strap when cycling, but I only use the watch when running.

Is this a bug? I would expect that when I run the predetermined profile is updated, and only when I go on the bike the cycling profile is updated.

Cheers,
Victor

  • There is only one Max HR - it is a physiological limitation of your body, regardless what you do. That you get close to it easier while running than when cycling (or vice versa) is another topic.

    However, the Max HR is a rather stable value, not increasing with your fitness, rather only slowly decreasing with your age, so I recommend performing a Max HR test once a year, setting the Max HR value manually, and disabling the auto-detection.

  • Thanks trux!

    I tested back in April and my Max HR was 198 bpm in a lab. I might do as you say, but I wanted to test Garmin autodetect functionality and see how it works. I was surprised the way is acting and I wanted to understand whether this is expected or a bug. Perhaps someone from @Garmin can clarify this. Otherwise I'll report a bug.