S9 barometer problems

[Anssi Auvinen]

Here’s the qs link: https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/DzCcIqqv3jthDHJHh00L

[Dimitrios Kanellopoulos]

@Anssi-Auvinen then it didn’t manage to calibrate it self in time. Or calibrated incorrectly. But 1h to get a good precision is too much. Did you calibrate at start? How was the GPS conditions ?

[Brad_Olwin]

@Anssi-Auvinen You can merge the two files for the same activity, that might help for looking at the altitude. Merge the fit files for S9B and Garmin in QS, there is a button for that.

[Anssi Auvinen]

@Dimitrios-Kanellopoulos Gps conditions were fine and I have not ever calibrated it at the start.

Today again short ride Suunto 122+m, Garmin 185+m, Strava with elevation correction 196m+.

[Anssi Auvinen]

@Brad_Olwin You can clearly see even with that S9 data what is wrong. I repeated the same hill 4 times and it does not show the same elevation every time down or up. Right elevation came if I waited some minutes without moving.

[Mff73]

have you tried cleaning your baro sensor ?
too much delay in correct altitude/pressure reading may come from sensor being “blocked” by some dust or else.

You can eventually try also to downgrade firmware to previous one and see if your guess that it is FW related is true.

[Anssi Auvinen]

@Mff73 Yes, I had the watch one night in water and after that i rinsed it with running water.

[Anssi Auvinen]

Here you can see that is just working too slowly.

[Mff73]

@Anssi-Auvinen
Are you with Android SuuntoApp ?
If yes, you could also try to import the SA raw data file into QS and see GPS altitude registered by the watch. We may be able to see something different. Raw data files can be found in the phone (see this link https://forum.suunto.com/post/33052)

But if you sensor is clean, and “just” behave slowly, and if you think it is like that only since latest FW, i personnaly would have downgraded FW to be sure of this (if you are able to reproduce the phenomenon).

[Anssi Auvinen]

@Mff73 Im iOS user and I think this problem started before the latest update (I have only checked data from last couple weeks), but I can try to downgrade next week.

[Dimitrios Kanellopoulos]

@Anssi-Auvinen can I have a QS link ?

[Anssi Auvinen]

@Dimitrios-Kanellopoulos here is from this morning: https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/1WqeCPgJDXeuZsr8qH79

Another one earlier in the chat.

[Dimitrios Kanellopoulos]

@Anssi-Auvinen could you make it public ? (click on the lock icon or press share from the menu)

[Anssi Auvinen]

@Dimitrios-Kanellopoulos Now it’s public

[Dimitrios Kanellopoulos]

@Anssi-Auvinen from what I see https://www.loom.com/share/58fff68c2bd64691b06a0d8d8033352b

The flats have 2m diff. The ups 2m

The start to end have 10m (within limits)

To me it looks ok

I wonder as well how the garmin is

[Mff73]

@Dimitrios-Kanellopoulos
could it be that altitude is registered correctly, but ascent is not growing as quickly as expected ?

[Dimitrios Kanellopoulos]

@Mff73 that can be for sure…

[Anssi Auvinen]

@Dimitrios-Kanellopoulos That seems ok, but i dont think it’s right. From previously posted qs link you can see the differences better. I have also 2 rides from june and september where route was quite same, differences in the start and the end, but june ride has 300m+ more and event the september should have more. I will try to crop them in qs for matching parts.

[Dimitrios Kanellopoulos]

@Anssi-Auvinen keep me posted on the next ride. A QS link will help as always. I understand the issue and and forwarding the feedback as needed

[Anssi Auvinen]

@Dimitrios-Kanellopoulos Next ride will be a race, so there maybe i can get strava statistics from other riders.