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

LTHR Guided Test broken?

TomJones3
over 5 years ago

I have a Forerunner 945 that I have used for a few months, software version 2.5. I used the LTHR guided test a few weeks after I got the watch and it worked great, the test was not too grueling and it estimated an LTHR that confirmed what I had earlier tried with a self test (164 bpm). 

Yesterday I started the test again, completed the warmup and the first interval was targeting 175-200 bpm! Keep in mind, the watch had already detected a previous LTHR of 164. I gave it a shot, just to see what would happen. I had to run near my max HR just to stay in at the bottom of the range. After the interval ended, it started the next interval at 200-225!

I confirmed that the watch still had the 164 value for LTHR. I restarted the test and got the same initial interval.

I restarted the watch and tried again and got the same initial interval.

Obviously the test is broken, there is no way I could sustain HR at those levels and there is no historical data that would make it think so. Has anyone else seen this, or have a workaround?

  • 0 over 5 years ago in reply to f|33tStA

    I recently changed my heart rate zone from %HeartRateThreshold to %HRR and I changed my max heart rate from 192 (value of two years ago) with a recent heart rate max (180). I changed the heart rate zones for all sports and are the same in the watch and in Garminconnect, yesterday the watch detected a new heart rate max 181 in running and the watch updated only the running heart rate zones and they changed also in Garminconnect.

    The pace the watch reports the old value of the lactate threshold of june.

    Garminconnect in the graph of 6 months reports that value but only for the day that I did the test with a blue point. In the "4 weeks" and "7 days" page there are no graph but  :"you have no data for this time period"

    When I run usually I use the optical heart rate and not the chest strap, so it's normal that I don't have a threshold value in the normal runs. But the last 4 lactate threshold tests with chest strap all failed.

  • 0 over 5 years ago in reply to Mirko_Italy

    after i received my FR945 i configured the HR zones for running to %maxHR, i have done some runs, to see, if it works primary (i don't use OHR), then i decided to do a LT-Test by Garmin and it worked fine, the watch detected the LTHR and the watch asked me to accept the LTHR and of course, the watch asked me, to atapt my HR Zones too, what i accepted.

    when i looked later, i seen, the setup of my running HR Zones changed from %maxHR to %LTHR

    you could try this too?

    if yes, you could try to setup your maxHR 10bpm lower then your correct values, so the watch can easier detect a change of your HR?

  • 0 over 5 years ago in reply to f|33tStA

    I will change the zones with %max hr and I will change in Garminconnect both LTHR from 175 to 165 and max HR from 181 to 175. I will do another test with the chest strap and I will see how the watch will change these values and if it will change type of zonex from %max hr to %LTHR

  • 0 over 5 years ago in reply to f|33tStA

    Threshold test successful today after the changes described above (zones from  %HRR to %HRmax, max heart rate from 192 to 181, LTHR from 175 to 165).

    Old values were LTHR=175 pace 4:18

    New values are LTHR=162 pace 4:28

    After the run the watch asked if I wanted to accept the new LTHR heart rate value, I said yes.

    Then it asked if I wanted to change the HR zones with %LTHR, I said yes.

    The new values could be true because it's two months that I'm detraining and because now it's summer and warm (about 30°C, even if Garminconnect reports 15°C less)

    Probably the threshold is successful only if the old values are near the new values. If the difference is too big, the test fails.