SOFTWARE UPDATE 2.19.42 January 27, 2022

S.Pichi

@s-pichi it ok now , i do factory reset and can update now. Thanks.

MiniForklift

I was always the annoying one who had the S9B with no battery issues, used to be able to get a good couple of weeks before I needed to even think about charging

Noticed that my battery levels appeared to be dropping faster than usual so I charged it to full last night. Now, around 20hrs later it’s down to 90% and I haven’t used it at all today (no training). HR is disabled as is sleep and mobile notifications - nothing is active. 10% in less than a day without any training is definitely not right, something is off since I updated

Egika

@miniforklift as always with firmware updates: give your watch time for a full charge cycle (full to empty to fully charged), as the battery calibration needs to recalibrate itself. Then check again please.

Pavlas

I had a battery problem with the previous firmware 2.18.20
After the last update it’s good again.
But one thing happened to me on Tuesday. I went for a run. I wanted to use the Suunto Plus - Burner. As I selected the Burner, the watch froze and restarted.
After restarting, I tried again and it seems fine now (I tried it 3 times)

DMytro

@pavlas did you send logs?

Pavlas

@dmytro No. I forgot. I’m sorry.

isazi

@pavlas if it happens again (hope not), sync your watch with the app as soon as it recovers, send logs, and send me a PM with the description of what happened, the time you sent the logs, and your email. I will fill in a bug for Suunto.

@dimitrios-kanellopoulos short questions about deeper understanding ascent / descent algo during sport modes:

Ascent / descent is only counted if a certain threshold of ascent speed is reached? That means if you would run 10km with constant very low ascent ( 1m per 10km), you won’t see 1m total ascent, only maybe in absolute altitude?

I suppose absolute altitude is something completely different than ascent. Question: fusedalti has only impact in absolute altitude, not ascent? Thats why you would see weather changes in ascent but not in absolute altitude.

Pavlas

@isazi Okay, thank you!

isazi

@mountainchris said in SOFTWARE UPDATE 2.19.42 January 27, 2022:

Ascent / descent is only counted if a certain threshold of ascent speed is reached? That means if you would run 10km with constant very low ascent ( 1m per 10km), you won’t see 1m total ascent, only maybe in absolute altitude?

Yes, if you do not climb 3 meters in a short time, it does not count.

Dimitrios Kanellopoulos

@mountainchris complicated question.

Complicated answer

Yes if you do 10km with 1m ascent in each 1km it wont show 10m ascent . Your hand moves 1m . Its more complicated. But first you need to pass that threshold, have some vertical speed (accelero) and then it will count every 1m.
So if you run 1km with 3m ascent at some point and then 1m increments will count. But not forever. So if during the 2nd km there is no ascent , the 3rd km onwards even if 1m ascent , it wont count. So that threshold is reset if it sees you stopped ascenting.
The fused alti does 2 things , not in order and not only 1 time

a) If the difference of GPS based altitude to barometric altitude is big it will try to “fix” this instantly. Ie you are at 1000m but the barometer says 1m , it will correct that and all past values.
So if you are at minute 5 , lets say with a flat altitude of 1m all the time before it will correct all prev values as well to 1000m.
b) if the difference is small, and the GPS error is not helping to determine accurately the altitude it will start to correct slowly and that might count towards ascent. for example you are at 120m and the baro says 100m. The GPS error is 20m. IT wont try to correct it as the GPS altitude might be 120, 140 or 100 or what ever in 20m error. It will listen to good moements of GPS altitude and pull a bit up that barometric altitude without correcting prev values. So slowly you will see 119 , 118 and those might count to descent if you are descenting but not if not due to the threshold not being passed.

I wont go to internals but it is not an easily subject to describe.

A+B can happen many times during your workout

@dimitrios-kanellopoulos

I wont go to internals but it is not an easily subject to describe.

Thanks a lot. Yes I can somehow imagine how things are going! I startet to think about this, because I did a relative flat run on stormy weekend with continuous falling hPa (~ 5-6hPa) and I had way more ascent / descent than usually on this track. 180 vs 100 aprox. Then I started thinking…

pilleus

Suunto plus - Climb

If auto stop is activated, the Suunto plus mode “Climb” does start a new hill after a stop during an uphill.

Feature or bug?

freeheeler

@pilleus
philosophical question IMHO… it depends what type of users we are… straight forward runner athletes might prefer a new hill once they stop e.g. for refueling water… but for hiking it would make sense to keep the “old” hill when you take a short stop

Egika

@freeheeler makes sense.
But as a hiker, why would you use S+ Climb?

DMytro

@egika I can answer that: to estimate vertical speed in specific difficulty regions for a better time anticipation in the future. That’s at least what I’ve been trying to do XD

freeheeler

@dmytro
yep

Egika

@dmytro I must admit I have never used this feature. Is there any difference to the various vertical speed data fields available in sport mode customization?

DMytro

@egika it’s not for in workout, it’s for post workout.

freeheeler

@dmytro
aaah, see… that’s why I am not a member of the club you do not talk about … didn’t even notice that