VO2 and Lactate thresholds not calculating

Former Member
Former Member
I've been on each of the newest firmwares as they come out (betas included) and use the Tri chest strap (bundle). I've been running 2 or 3 times /week for the past few weeks but I haven't seen the VO2 nor Lactate thresholds calculating anywhere. Is anyone else having this problem?
  • I've been on each of the newest firmwares as they come out (betas included) and use the Tri chest strap (bundle). I've been running 2 or 3 times /week for the past few weeks but I haven't seen the VO2 nor Lactate thresholds calculating anywhere. Is anyone else having this problem?


    Are you running outside?
  • Former Member
    0 Former Member over 8 years ago
    Are you using RUN or Trail Run application?
    I had same issue.
    Mine G5 is new, I tried a run with optical HR on saturday, no VO2 calculation. I used Trail Run.
    I thaught its issue with the optical HR, so connected to strap HR Run and went out on Sunday. I used Trail Run again.
    No VO2 max calculation again.

    I remember from Fenix 3 that in the 1st versions of the firmware you had to use RUN to get calculation. But it was fixed with firmware.
    Not sure about it on F5, will go for a run with RUN today again and confirm.

    and I am on newest BETA....
  • Former Member
    0 Former Member over 8 years ago
    Yes I was using trail run
  • Former Member
    0 Former Member over 8 years ago
    Running outside every time. Trail running
  • Trail Run .... I remember from Fenix 3 that in the 1st versions of the firmware you had to use RUN to get calculation. But it was fixed with firmware.

    You have this wrong way. Trail Run did initially give VO2 and LTH. But as trail runs are at slower speeds and on uneven surfaces it did not give a true record. Those who had mixed running schedules got fed up with their values being compromised. So in later versions Trail Run profile very specifically by design do not give or modify your recorded values. I assume that is the case with the 5 series.
  • You have this wrong way. Trail Run did initially give VO2 and LTH. But as trail runs are at slower speeds and on uneven surfaces it did not give a true record. Those who had mixed running schedules got fed up with their values being compromised. So in later versions Trail Run profile very specifically by design do not give or modify your recorded values. I assume that is the case with the 5 series.


    Besides, it will only provide LTH when very hard runs.
  • Former Member
    0 Former Member over 8 years ago
    I agree that trail run has lower speeds.
    But on Fenix 3 I was running only trails, I hate flats...
    And once the firmware bug was resolved, I always got VO2 max calculations and updates using trail run. (I had a warranty replacement so it worked for calculation also)

    Will try with the run once again....
  • I agree that trail run has lower speeds.
    But on Fenix 3 I was running only trails, I hate flats...
    And once the firmware bug was resolved, I always got VO2 max calculations and updates using trail run. (I had a warranty replacement so it worked for calculation also)

    Will try with the run once again....


    If you had an updated sw on your Fenix 3 you absolutely were not getting VO2 and LTHR on the Trail Run profile.
  • Former Member
    0 Former Member over 8 years ago
    If you had an updated sw on your Fenix 3 you absolutely were not getting VO2 and LTHR on the Trail Run profile.


    First I wanted to argue as I see my VO2 max increase/decrease during last 12 months in the reports.
    But than I realized my activity named Trail Run on the watch had the Activity type Run.
    So I guess that made me think my trail runs calculated my VO2 max...

    So now on my new F5 I have Activity type Trail run - means I will never get VO2 max calculation there??
  • If you need any more convincing, have a look under the changelog notes for "Changes made from version 7.00 to 7.20" here http://www8.garmin.com/support/download_details.jsp?id=7623

    Fixed a potential issue where VO2 Max and Lactate Threshold estimates were being used incorrectly with Trail Run activities.