Related
Options

VO2max and Training status not updating since 9.33

Petorrr
over 2 years ago

Hi all, anybody encountered this problem already? I checked back in Garmin Connect, last VO2max update was in a run on 28-Aug with SW version Epix Gen2 8.37. After the software update to 9.33 none of my runs recorded a VO2max data point anymore. And I mean, it doesn’t show any point (also not the same value, just none) in the history graph, it just stops on 28-Aug. Also on the watch in the VO2max screen it shows last update 28-Aug. I ran at least an 11K, a 6K and 2 faster 5K’s definitely meeting the criteria for VO2max calculations (outdoor GPS, >70% of maxHR etc). Due to the No Data on VO2max it can’t show a Training Status in the widgets, so it’s showing No Status….. Seems to be a SW update problem as all the following runs were done with the 9.33 version after the update, this can’t be a coincidence. Is there a solution, or has anybody encountered the same problem?

  • 0 over 2 years ago in reply to Etupes25

    Absolutely! All my runs since the last SW update meet these criteria. 5Ks, 10Ks with GPS, runs at least 30 mins or longer with recorded heart rate and in the >70% heart rate zones.
    I really hate doing a factory reset, as you will need to have to install everything again, watchfaces, parameter settings, data screens, widgets, the apps order etc. This is really a mess Garmin has created in this version, not to mention even the battery drain problem.
    BTW: Also Instinct 2 and Fenix users report the VO2max problem, so I guess this is a more generic software module bug they use cross-platforms

  • 0 over 2 years ago in reply to Petorrr

    Contact Garmin support. They will request access to your account and check you sync logs. This is what I did when I noticed issues with daily suggestions. They had some back end sync issues that they have been working on. My issue has disappeared, but maybe there are other issues.

  • 0 over 2 years ago in reply to Etupes25

    I may have found something. Was just analyzing the FIT files of the runs that were still OK, and the runs after the SW update. There is one major difference with the ones that don't generate VO2max..... they seem to use my Cycling (!) heartrate settings and zones. I am also using an Edge530 for my racebike, therefore have different sports and different zones. After the update to 9.33 all my FIT files suddenly use the wrong maxHR etc, so it seems. 

    Fit file that generated last VO2max:

    max_heart_rate,threshold_heart_rate,hr_calc_type,pwr_calc_type
    192,0,percent_max_hr,percent_ftp

    All Running FIT files after the SW update to 9.33 have FTP settings which come from cycling.......:

    functional_threshold_power,max_heart_rate,threshold_heart_rate,hr_calc_type,pwr_calc_type
    200,185,0,percent_max_hr,percent_ftp


    I will delete the Sports (incl Cycling) profiles except for the default one from my watch and go again to see if this changes the behavior. I suspect the new SW version messes up with these profiles with a wrong index or so, and has running now set to the wrong cycling maxHR and zones profile.

    I guess Garmin engineering should then look into this when this solves my problem, because then many more that use multiple profiles may encounter this problem.

  • 0 over 2 years ago in reply to Petorrr

    Maybe... Remember that 9.33 introduces power for running, so it is possible you just see a placeholder value in your running fit files. The difference of HR Max is noticeable, so yeah, correcting this is valuable.

    Looks like Garmin is still sorting out sync issues.

  • 0 over 2 years ago in reply to Etupes25

    Ok didn’t know that, so that could also explain the difference in the Fit files…….

  • 0 over 2 years ago

    I have the same issue with bike rides. Training status has been fine up until this update. Since the update I get no status. I’ve done three rides this week. All with power meters. No status showing. It says I need to do at least one ride with VO2 tracking but all three should have been suitable (they have been until this update). I assume this is a bug. 

  • 0 over 2 years ago in reply to Tim

    Sounds like exactly the same as my problem but then for the cycling VO2max…… If you search on the forum there are more people having this similar problem, but not many. Maybe it is a specific setting in our watches that with the newer version disables the VO2max calculation. Anyway I upgraded this morning to the Alpha 9.35 and did a normal 10K run, meeting all VO2max criteria. Still no new value…… So I posted this as a bug on the Beta testers forum to the Garmin developers. I am very sure now this is a bug somewhere in the platform software as also Instinct 2 and Fenix 7 users report similar problems. 

  • 0 over 2 years ago

    Same problem occurring with the Fenix7. Like others here, all runs meet criteria for VO2max calculations and all attempts to rectify unsuccessful. Following this thread with interest! 

  • 0 over 2 years ago in reply to scottyd99999

    Thanks for your reply Scotty. We’re not alone, there are more of us having this problem! Instinct, Fenix, Epix users, all the same problems. Hopefully Garmin will fix this in the next version.