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

VO2Max stuck since November 19th

MiguelSerra
over 2 years ago

Hello.

Looking at the reports I see that since November 19th that VO2Max value doesn't change not even by 1 unit. I had the same issue with my previous Edge 1030 which was solved by an update. When I bought the current 1040 I had changes on the value depending on my weekly training, but now it just stopped being updated for a long time.

Can you guys Garmin Forums solve this issue again ?!

Thanks in advance

  • 0 over 2 years ago

    I got my Fenix 7 in December 2022 and the VO2max value was estimated only while several walking activities. And since beginnig it stucks at 37 which is very likely a nonsense value (I'm doing regularly workouts and I'm typically the fastest in my family during walking, cycling etc.). 

    I fully understand that the watch requires some time and conditions to estimate the VO2max but if these are not met it shall not report some nonsense...

    Furthermore I would like to get more information how exactly this value is estimated by such watches (what sensors, what kind of processing). The help pages from Garmin are not very detailed in this aspect, unfortunately.

  • 0 over 2 years ago in reply to Garmin-Maeve

    My VO2max is suspiciously stuck since I replaced 1030 for 1040 (end of august 2022), although I still train as hard as before. My VO2max was changing constantly and reflected my performance well on 1030 (till august 2022). On the 1040 VO2max stuck on 55 no matter my training and performance was since september 5th till november 14th. Then it dropped to 53 and stayed for 1 month, then it dropped to 52 and is there for more than 1month. I guarantee that my performance and training is not impaired anyhow. 

  • 0 over 2 years ago in reply to Karis

    Exact same thing on forerunner 955 using power meter pedals..it's been reported to Garmin Cry

  • 0 over 2 years ago

    Well, today I had a VO2Max value update, so it seems to be working.
    Because of my past experience looking at this value, I was expecting a bit more fluctuation on this value...still, now I had a change.
    So let's see how it goes from now on.

  • 0 over 2 years ago in reply to MiguelSerra

    Was it due to the new firmware?

  • 0 over 2 years ago in reply to StefanScheddy

    I'm not sure. I was thinking that it can also be due to Firstbeat that might changed something in the algorithm ?!?!?! And since Garmin integrates with them, that could be a reason...