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

    What's your max HR set to on the watch?

    If you have auto-detect enabled, maybe a glitch set it to a high value?

  • 0 over 5 years ago

    Yesterday I did a LTHR guided test and I followed all the steps that the watch told me to do. But at the end I had this result: "Workout ended: threshold not detected".

    The only valid test for me was with the old firmware the 19th Jun, that gave me a value of 175 and that was correct (same average value of a recent half marathon). After then I tried other 3 times, but every other test ended with the same result: "threshold not detected".

    Someone else did a valid threshold test recently with the actual firmware?

    I am now with firmware 2.72 beta.

    How often do you update the threshold value? Does it change frequently (with training and detraining) or is it quite stable?

  • 0 over 5 years ago in reply to Mirko_Italy

    it worked for me on 23.07.19 and new threshold and hr zones detected, changed from Fenix 5 to Forerunner 945 with FW 2.60 and last week 22.08.19 i have done my own Threshold pace and Fitness Test, there was again a new Lactate Threshold detection on FW 2.70.

    how looks your target HR in the activity of Lactate Threshold Test?

  • 0 over 5 years ago

    I did a test this morning and I had the No Threshold Detected result. Usually the test works flawlessly for me.

  • 0 over 5 years ago in reply to kerlaz

    but that means, it's OK because your threshold haven't increased, or?

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

    No, it means a threshold wasn't detected. OI it was unchanged it would report the threshold value still.

  • 0 over 5 years ago in reply to f|33tStA
    f|33tStA said:
    how looks your target HR in the activity of Lactate Threshold Test?

    This is how the graph looks like: in the previous step the target was 135, 149, 158, 167. In the last step  the watch asked me to run between 170 and 180 and I see that  GarminConnect i has 176 as target . I was trying to save some energy because I was expecting that the watch asked me to run another step between 180 and 190, but it terminated the workout.

    f|33tStA said:
    it's OK because your threshold haven't increased, or

    In my opinion the threshold value now could be lower than in june because it's summer and I wasn't training hard and I didn't race. So I was expecting that the watch give me a lower number than 175, or at least confirm that value. But threshold not detected it's a delusion for me, I organised the training session for this test only...

  • 0 over 5 years ago in reply to Mirko_Italy

    mhhh, could be, that the average was below the target, but not sure, have the same issue with FTP Test.my average power was to low in the last 4 minutes and the FTP Test himself failed.

    What says the menue for Lactate Threshold on your Connect App?

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

    It says actual threshold 175 (the value of the old test of June). In the last 4 weeks It says no data available. In the 12 months graph only June has a  at Red line at 175 value, then empty

  • 0 over 5 years ago in reply to Mirko_Italy

    what says your pace, better or slower? think it depends on your pace too, but i am not sure, it's mystic for me too!

    you checked your HR settings on watch and in GCM, no differenes?

    you have cycling LTHR configured too? i ask, because here i detect a problem for me:

    Cycling LTHR