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

Still no VO2MAX after a month

I now have the 945 for a month, and till this moment it did not once ''calculate' my Vo2Max (using the watch leds not an external heart rate band).


I understand it can take up to 4 weeks... I have been running 2-3 times a week, which includes runs at more then 70% of my max heart rate for at least 10 min. (as Garmin states is needed).

Do you have the same problem ?; and did you find a way to get it working... as all other nice new features of the 945 are based upon the Vo2Max value!

  • I believe Fredderic is correct.

    Individual zone settings should not affect the FirstBeat algorithms.

    MaxHR setting on the other hand will have a major impact, with probably also resting HR value, and possibly LTHR value. Those are metrics that are either right or wrong, but zones are more a matter of personal taste and I can't imagine FirstBeat to base their algorithms on that. That would be a major flaw.

  • I’m sure the way the heart rate zones are incorrectly setup is the reason the VO2max score is still absent. If only the topic starter would adjust his heart rate zones to normal values and try that setup for a few days.....

  • of course they will affect it, if the watch "thinks" the user has never got out of zone 1 heart rate zone, it will never perform a Vo2 max calculation as it thinks the user isn't working hard enough.

  • I believe the FirstBeat algorithms does not care about zones.

    It cares about intensity as %HRmax.

  • So I think the ultimate takeaway here is that you are not doing any of the normal "gotchas" that would keep your VO2max from calculating. From everything I have seen and experienced, you SHOULD be getting a calculation. 

    The next step, for me,  would be a hard reset of the watch. If you call in to Garmin Support that will be the first thing they have you try. It might have worked itself into a weird corner or have a setting somewhere that is incorrect and a hard reset will potentially fix any of those issues. If you do a hard reset and still don't get a reading in a week or 2, then it is probably something physically wrong with the watch.

  • As a next step I decided to ‘reset’ the heartrate zones to the Garmin default values/percentages based on max heartrate value... so now I guess I have to wait about 2 weeks again.

    Below a run I did today whith those new values.... I want to thank you all for your suggestions and advise!

  • Firstbeat will not care about user defined zones, there are many different ways to setup your zones, there is no standard meaning what Z1 or Z5 means. Firstbeat will use things like max pulse or lactate threshold pulse (which might be user input or calculated, not sure) to calculate their own "heart rate ranges" and work their numbers on the workouts.

    Obviously its not open source, but using user supplied heart rate zones and trying to give these any meaning would be a pretty stupid move, I am very confident they would not do that :).

  • I found some more information on this (and I agree with the HR zones assumption of you, taking user settings would be stupid) and by this white paper ( https://assets.firstbeat.com/firstbeat/uploads/2015/10/FFW609US05-171.pdf ) I would think that it's important to have activities with "useful" data to get some "Training Effect" which can be classified and interpreted then  like described here a bit: https://assets.firstbeat.com/firstbeat/uploads/2017/06/white_paper_VO2max_30.6.2017.pdf ,Page 4

    So maybe it's the workout pattern? Interesting stuff, by the way ;-)

  • See to it that age, weight, gender and activity level is set. Those are needed for calculations.