Is there a specific VO2Max test?

Lars,

there is no particular way to turn it off, whenever the watch thinks it has enough quality data it will start estimation.

The only way to avoid the watch from estimating your Vo2max is to run without HR tracking.

Which is certainly not what you want.

Best regards
Christian

@LarsTheBear: For the Firstbeat algorithm to estimate VO[sub]2[/sub]max for running on a Garmin fitness device, it needs (i) GPS data, and (ii) HR data for the activity. My understanding is that, for indoor runs on Garmin device models that support VO[sub]2[/sub]max (e.g. using the Run Indoor activity profile on a FR230/235), the device will not perform an estimate of the metric. Furthermore, when using the trail running activity profile on the FR735XT or the FR935, VO[sub]2[/sub]max estimation is also suppressed, for the reason you gave.

I don't know if there is a suitable activity profile (or ‘app’) you can use on a VA3 for the same effect.

LarsTheBear I have the same problem. I use VA3 for soccer and was recording it as a "run" -- as a result, my average run pace was horrible but my HR was pretty high (since it's a lot of sprinting and then walking). I think my Vo2max score suffered.

I'm not sure if it helps, but last weekend I recorded my soccer game as an "outdoor walk" (so I still can see gps location, HR and overall distance which are the metrics I most want to see).
Based on what ASmugDill says above, I think I will still have same problem.

On the other hand, if the Vo2max does not count the "walks" (soccer), but only when I go for real training runs, then I should see an improvement in my vo2max score.

Otherwise, I say "this is bogus and F the vo2max!"

Thanks to those who replied. I think the situation is possibly worse than I thought, because I think the VA3 accumulates the readings it uses to estimate VO2Max over time. So if you do a mixture of track (or level) running and trail running, you're going to get a score that is sort of half-way between the two.

I guess if I really cared what my VO2Max value was, I would go someplace and have it measured, or just do the old Cooper 12-minute run test on a track. At my age, it isn't even in the top half of the list of things I'm worried about it; I'm just surprised that Garmin don't bother to explain how this stuff works, and what you need to do to get reliable values.

I'm also a little surprised that the Vivosmart 3, which is one quarter the price of the VA 3, doesn't make the same mistake -- if you want to estimate VO2Max, there's a menu item for it.

Lars,

Garmin wont explain it since the Vo2max is estimated with FirstBeat technology.

This white paper explains very detailed how it works.

https://www.firstbeat.com/app/uploads/2015/10/white_paper_VO2max_11-11-20142.pdf

Best regards
Christian

Even in the best of circumstances the Vo2Max values from any device that doesn't directly measure the gases you're expelling are estimates and are best looked at as a trend.

The fitness age thing is a bit of a gimmick. Right now it gives me a fitness age of excellent for a 21 year old and I can tell you that while I'm pretty fit for my 54 years I'm nowhere near my 21 year old self.

Hi folks,

It's worth noting that during running/walking type activities the VO2max calculation relies on 'movement speed' which can be provided either by GPS or accelerometer-based calculations. When it comes to the Vivosmart 3, this is worth noting as that particular device doesn't have an integrated GPS. The fact that the vivosmart 3 has this test option may have something to do with that.

The Firstbeat analysis is specifically and intentionally designed to be done WITHOUT any sort of special testing protocol. Rather it's designed so that you can just do your normal runs and gain regular, continuously updated insight into your cardiorespiratory fitness / aerobic capacity.
---

I don't think there is any possible way you could get anything close to a good VO2max estimate playing soccer. As you mentioned there's just way too much stopping and starting, which a) is going to be practically impossible to get consistantly reliable speed data from and b) your heart rate is going to be constantly shooting up and down in ways that mean that things will never quite match up between your HR and your work output.

Now, the good news is that your device should be capable of recognizing that the incoming speed and effort data is jumbled and therefore unreliable, and shouldn't result in a VO2max detection. That said, it is that with enough usage over time, you might be able to accidently trick the analytics engine into spitting out a VO2max figure from a soccer game... probably a bad one.
---

Fitness Age is definately a gimmick... or as we officially describe it "a relatable interpretation of VO2max." The truth is that a lot of folks are completely unfamiliar with the concept of VO2max and what it means, so a thing like "Fitness Age" simply offers a simple and easy way into the idea. The fitter you are, the younger you feel.

It's a very simple lookup that compares your current fitness level and gender with global norms. Some folks really like it and find it 'motivating' for other's it's a meh.

Lars,

Garmin wont explain it since the Vo2max is estimated with FirstBeat technology.

This white paper explains very detailed how it works.

https://www.firstbeat.com/app/uploads/2015/10/white_paper_VO2max_11-11-20142.pdf

Sure; but what irks me is that while FirstBeat is pretty open about the limitations of its method, Garmin will happily use crappy data without warning.

The FirstBeat article says:

"In order to obtain consistent results, the exercise conditions should, however, be standardized because for example running surface, wind, and high altitude may affect the moving speed."

As an example, it states that data from running on soft ground should be excluded, as should that from running steeply downhill.

It's pretty clear that the FirstBeat method is intended for running in still conditions, on firm, level ground. In addition, it is intended for running, not walking. But the VA3 will happily base a VO2Max estimate on activity that isn't remotely similar to the conditions that FirstBeat describe. I don't believe it would even be possible for the VA3 to exclude data from running on soft ground, for example, or in a stiff breeze.

Probably the FirstBeat method is reasonably accurate when used in the scenarios they tested; but the idea that you can strap on a fitness tracker and get a reliable VO2Max reading by walking your dog in the park is just ludicrous, and Garmin shouldn't be claiming that this is possible, or using such data in its estimates.

I think that the VA3 probably could be used to detect a trend in individual VO2Max over time, which I guess is what most people would be interested in. However, it can only do that if you carry out exactly the same exercise protocol every time, and that isn't possible because the unit includes data from just about every activity that has a distance and a heart rate.

The Firstbeat analysis is specifically and intentionally designed to be done WITHOUT any sort of special testing protocol. Rather it's designed so that you can just do your normal runs and gain regular, continuously updated insight into your cardiorespiratory fitness / aerobic capacity.

But FirstBeat don't claim to be able to do any of that. Specifically they state that the exercise has to be standardized to remove variable conditions. Their article could hardly be clearer about this.

"In order to obtain consistent results, the exercise conditions should, however, be standardized because for example running surface, wind, and high altitude may affect the moving speed."

Garmin are using FirstBeat's method in ways in which I don't think it was ever intended to be used.

Hi Lars,

I think you've latched on to a bit of boiler plate in the conclusion of that paper. Yes, for the absolute best results, you should always do everything under the absolute best conditions. That's Assessment 101. The rest of that particular paper maps out a sophisticated method of getting a very good estimation of your cardiorespiratory fitness level in challenging real-world conditions.

You may have misinterpreted something in the paper - apologies, they aren't always crystal clear, in the way that documents written by experts can often be - but those examples you gave "running of soft ground" and "down hill" are conditions that the analysis is designed to detect and automatically exclude from your VO2max estimate. Of course, if you are somehow always, only running downhill or on sandy beaches, then yes... you're going to eventually get some bad data thrown back at you.

Our development team spends a tremendous amount of effort working out how to identify non-representative data an exclude it from analysis. A smart algorithm is an algorithm designed to automatically select the right data to work with.

Can Garmin/Firstbeat get a good VO2max reading while your walking your dog? Well, that depends a whole lot on how you're walking your dog. ;-)

I can assure everyone that Garmin's utilization and integration of the Firstbeat physiological analytics engine is as intended.

Hope that helped a little.