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

[17.24] BUG - Wrist HR readout and calculations

RDW
over 1 year ago

Definitely still a bug in the wrist HR displayed during exercise.  This issue appeared with the 16.19 previous firmware.

Watch has been hard reset, user data wiped etc.

Symptoms are a run using the normal zone 2 easy HR are being logged as tempo.

The run shows never above zone 2, a perfect execution score, average HR shows bang in the middle of zone 2 and the watch logs it as Tempo instead.

Anecdotally the displayed HR seems to be 6-7 BPM lower than it should be for the pace BUT the actual training load calculation seems to use a different value NOT the one displayed to the user and on the stats.

So a Zone 2 is calculated as zone 3.  A Zone 1 is calculated as a zone 2.

There is no reason at all this run should be Tempo looking at those figures *but* the pace suggests it probably was an actual tempo HR and those figures are inaccurate (and an undercount).

Im using a LTHR% based zone (Friels recommended zones) and have been for many months without issue.  This problem started with 16.19 and persists on 17.24.


The issues are its not impossible to do a base run and  all the calculations for training load, training  balance, suggested workouts, VO2 max, race predictions etc are all going to be so inaccurate it cant be used.

  • 0 over 1 year ago

    May I ask what is your maxHR and LTHR? At a first sight your HR Zones goes a little wild.

  • 0 over 1 year ago in reply to global_local

    Max HR 189 and LTHR about (measured).

    But importantly the same settings that have worked perfectly for many months until the last 2 firmware updates.

    Ultimately an activity that is logged as in zone 2, indicated in all stats as zone 2 should be a base activity not tempo.  Which is has been until last month.

    16.19 and 17.24 changed suddenly and despite all the figures showing zone 2, its not calculating it as such.  And due to the pace i suspect its displaying an incorrectly low HR but using a different internal figure for calculations.

    The HR zones are directnly Friel's recommendations and certainly seem accurate for me based on feel (and worked fine on the calculations until the last 2 firmware)

  • 0 over 1 year ago in reply to RDW
    RDW said:
    Max HR 189 and LTHR about (measured).

    Ahm... World runners elite _can_ reach lthr about 92-94% (I have 89%) But You have measured 100%? Respect!  You definitely need a better Watch. ;)

    Jokes aside, I would say, reset your running  zones and set it up  to maxHR. Then do a guided LTHR test to get  an realistic value.

    Now your 2nd zone overlapping 2d and 3d zones together.

  • 0 over 1 year ago in reply to global_local

    That was a guided test.  4 of them over 6 months.

    And again that isnt the issue here.  The issue is what used to be zone 2 base over many hundred of activities, since the 16.19 and latest firmware update still SHOW as zone 2 but get logged as tempo.

    Its a change in behaviour that came in with a firmware change that now seems to be using 2 different HR readings - one displayed and a different for calculations.

    Prior to that, zone 2 was classed as zone 2.  Now its not despite display as if it was.

    You can now do an activity spending 100% of the time in zone 2 and it gets classed as tempo.

  • 0 over 1 year ago in reply to RDW

    I think it all depends on the incorrect frequency readings that everyone has been complaining about since 16.19