No Vo2max since update 2.14.12

[Tobi74]

@dimitrios-kanellopoulos thanks for that explanation. I did hard and soft resets, changed the battery of the heart-rate belt…. And so on.
I will do a 10k test run tomorrow. Maybe the value will appear again. I agree with you about the black box and the firstbeat plugin. It will be always a problem with third party pugs if one party is doing an adjustment .

[isazi]

@tobi74 soft resets are no issue, but every time you do a hard reset it starts from scratch and it may take a while to estimate the value again. So hard resets aren’t a way to make VO2max reappear faster, they are a way to postpone it further.

[Soylent Yellow]

@dimitrios-kanellopoulos I’ve got the same problem here with my 9 Baro. Watch hard reset itself during the firmware upgrade, and since the hardly a Vo2max reading.

I ran a HM marathon yesterday, so that’s all Zone 3/4/5 on a flat course with open view of sky and a Polar H10 HR Monitor with a new strap and fresh battery, and still zilch. No Vo2max reading at all. I am really starting to believe that 2.14.12 changed something on the data delivery to FirstBeat’s ‘Black Box’, either because the GPS signal is noisier than before, or because the HR data gets massaged or re-interpreted somewhere.

Have a look at the images below. It is quite clear when the 2.14.12 upgrade took place!

[isazi]

@soylent-yellow next firmware will fix some issues with VO2max.

[Tobi74]

update 2.14.16 is online. I have already updated. let see if it works now

[isazi]

@tobi74 I think this will be fixed in the next update, but I may be wrong.

[EzioAuditore]

@isazi You are right, still no Vo2. Out of 6 runs only my first 2 had vo2 (I got notif that the HR is not ideal on those runs for some reason ) all the rest runs no vo2.

[isazi]

@hristijan-petreski wait just a little bit more

[isazi]

This should be fixed in 2.16.26 (it has been for me for a while at least).

If any of you still has problems, please let me know.

[EzioAuditore]

@isazi Thank m8. I found a pattern when using some suunto+ functions to affect the vo2. E.q.: When strava relative effort I always had vo2 when TP I had the bug. I will try it and will give you a feedback.

[Dimitrios Kanellopoulos]

@hristijan-petreski that is interesting. Please keep me posted

[Dimitrios Kanellopoulos]

@argo320 lets continue here

• What activity do you use ?
• What S+ do you use
• What belt / OHR do you use
• Does the vo2max not get reported on the summary of the sport (after finishing the activity) ?

[EzioAuditore]

@dimitrios-kanellopoulos In my case I had:

• running (the basic/default and custom created)
  – without belt
  – belt too (HRM Pro)
  Always when choosing suunto+ with TP my vo2max was absent (in the watch after the activity was finished but also when visiting the logbook). I used also Climb/Hill and the Strava relative effort and the Vo2 was present. Will hill run tomorrow so I will be using Climb again, but on Saturday I will have long run and will try the TP data. Will report further if all is ok after this FW. Cheers.

[Argonaut330]

@dimitrios-kanellopoulos ok and thanks for your time, so:

• I mainly and only use RUNNING

• Usually i use NO S+ at all, if i go on unknown trail sometimes i use SAFE or if doing some treshold i use TrainingPeaks Running Pace (but very seldom)

• No belt, just wrist

• It doesnt get reported on the watch summary at the end and on the app VO2 tab

As said, this pattern is quite randomized, sometimes i get the VO2 either with or without the S+ functions.
Today, after the update, i went for this run to test it and i got no VO2, using Weather S+.

Let me know if anything else is needed

[Dimitrios Kanellopoulos]

Lets nail this one. Please report again with the findings after the update etc

NOTE: For OHR if the quality is bad it can not appear , but that is a different case

[Egika]

@Dimitrios-Kanellopoulos so now I do get a strange effect with the firmware of today:
I start a running activity as a test indoors, let it record for 30sec and stop it wothout actually moving (no GPS, HR 60bpm).
I get a VO2max registered of 53.1 in the summary of this activity and this value is also updated in the VO2 in the main screens.
I think this should not happen?!

[Argonaut330]

@dimitrios-kanellopoulos ok i will use for a week or so, and taking note of behaviour re VO2 recording, then will report again on this thread and take it from there. In the meantime let me know whether i need to send the logs today, grazie.

[Dimitrios Kanellopoulos]

@egika for such a small run it should show some previous calculated value. Vo2max depends on previous runs.

Also on short activities it might increase due to the little hr raise

[Egika]

@dimitrios-kanellopoulos thanks for the explanation
yes, it just increased

[Dimitrios Kanellopoulos]

So do you guys train often?
Do you get a vo2max value , and then on the next run the value is completely missing from the summary (without resetting the watch etc)