No Vo2max since update 2.14.12

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)

EzioAuditore

@dimitrios-kanellopoulos I run at least 3-4 times a week and do aerobics 2-3 times and then some bike (commuting).
But lately even without the bug fix (previous FW) I always had Vo2 because I was always setting suunto+ to Strava relative effort (I thought this is the reason I always have vo2).

Dimitrios Kanellopoulos

@hristijan-petreski yes that’s how it should work. I don’t see an issue here right ?

EzioAuditore

@dimitrios-kanellopoulos Yes no issue there. The issue was that everytime i choose suunto+ TrainingPeaks the Vo2 was lost. I have not been using it ever since. That’s why I said I will try again on Sunday with the new FW and TP

Dimitrios Kanellopoulos

@hristijan-petreski that’s a great indicator.

I just today used tp heart rate and had vo2max.

Please keep me posted.

Argonaut330

@dimitrios-kanellopoulos yes i train at least 5 times per week and so far, before the update, as average I got 2 VO2 per week out of 5…as you know today , after the update, no VO2 …more to follow in the next days. Ciao

EzioAuditore

@dimitrios-kanellopoulos

so just to keep you updated. Ran today with the belt and TP as suunto+ and the Vo2 is working just fine. I guess my bad OHR readings were the result of missing Vo2. Ever since I’ve been using belt all is working flawlessly. Thanks. I will try OHR on another run and if something changes will inform. Take care!