VO2max don't change
-
@Adamhert Progress widget and scroll down (you should have run though a couple of times to get performance info - dependant on your HR zones too).
-
@EzioAuditore thanks!
-
I am experiencing kind of strange behaviour of vo2max value. It changes but not the way I expected
last Saturday I did some interval run and got 55,2. Yesterday I did another interval run and got 54,7. This is the first time ever I got decreased value after an interval training ( which was quite intense - 5.30 min x 3 with 3.45 min/km as an average pace )Suunto Spartan Ultra, Suunto 7 Ti, Suunto Vertical Ti Solar
-
@rooldaa perhaps your HR was higher than last time?
Watch: Suunto Vertical Ti
Blog: isazi's home
-
-
@BrunoH I couldn’t stop my self laughing
Good one! -
@BrunoH The truth is that out of the 3 watches I have, I only get Vo2 on the Race. But this and the Ocean I use the most and the Ocean (if same as previous FW) needs me to run without the HR Belt to give me reading and I do not run without Belt. The Vertical I have ran 3,4 times and as much hikes without any Vo2 so far.
-
@isazi slightly higher, yes. But training was slightly harder as well. I just have a feeling that algorithms have changed compared for instance to last year. I run quicker this season and focusing more on high intensity running but getting lower values. I don’t know
-
Hello,
New pro peak, latest software installed, several runs no vo2 max, no fitness level.
Support says to send it back for a check, but it looks like the software has a problem. Have any improvements been made recently? -
I have the same problem. VO2 max estimate stopped after the last update in my Suunto 9 peak pro. The app shows clearly the date it stopped and its been several moths since the watch sais its needed to record at least an outdoor run to estimate. I’ve run hundreds…
I dont know if Suunto is working on this, as I see its a common problem for many users. -
It is still working here but I had a back injury and didn’t go running or biking from Nov - Mar. but Vo2max stayed at 44,8 so I guess as there was no new measurement it just stayed there. Now it gets new data from running and it changes.
