Related
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

Max Heart Rate Updated Without Meeting the "New" Max Heart Rate During the Activity [FR255, bug]

Tom Hale
over 1 year ago


I just did a run with an avg HR of 149 and max of 161.  At the end I was told a new max HR of 192 was detected, and this synced to Garmin Connect.

Run details can be found here.  I'm running firmware 13.21.

 this bug is analogous to the same one reported on the 955.  I'm in Australia.  You have permission to email and view/access my Garmin Connect account.

  • 0 over 1 year ago in reply to ovekvam

    I am not sure what you mean by the above.

    First of all its a %. which means that the absolute value of the zone should change if the underlying value changes. But not the percentage in the settings. It makes no sense to change the % as that would result in a double change (e.g. increase the absolute value as well as the percentage).

    Second, my setting for HR zone basis, as mentioned in my post, is set to %LTHR. So even if the MaxHR value changes, I would expect the neither the absolute zone values nor the %-es for the range to change.

  • 0 over 1 year ago in reply to Abász

    What I mean is that when the ratio between max HR and lactate threshold HR changes, it makes sense to change the zones.. My zones are based on max HR, and shown as a percentage of max HR, so they (the percentages) never change.

  • 0 over 1 year ago in reply to ovekvam

    But then what would be the purpose of setting the zones based on LTHR if it changes based on Max HR?

    If I want it to change based on MaxHR then I would set the basis on %MAXHR

  • 0 over 1 year ago in reply to Abász

    I am no expert here, but it seems sensible to me that the pecentages stay constant if you base the zones on maximum HR. And if the LTHR changes relative to the maximum HR, the zone percentages would have to change as well if they are based on LTHR.