S9 barometer problems
-
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.
-
@Mff73 Yes, I had the watch one night in water and after that i rinsed it with running water.
-
Here you can see that is just working too slowly.
-
@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).
-
@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.
-
@Anssi-Auvinen can I have a QS link ?
-
@Dimitrios-Kanellopoulos here is from this morning: https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/1WqeCPgJDXeuZsr8qH79
Another one earlier in the chat.
-
@Anssi-Auvinen could you make it public ? (click on the lock icon or press share from the menu)
-
@Dimitrios-Kanellopoulos Now it’s public
-
@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
-
@Dimitrios-Kanellopoulos
could it be that altitude is registered correctly, but ascent is not growing as quickly as expected ? -
@Mff73 that can be for sure…
-
@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.
-
@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
-
@Dimitrios-Kanellopoulos Next ride will be a race, so there maybe i can get strava statistics from other riders.
-
Cropped june and september rides with matching routes:
June (860+m): https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/vV5bafVvaJ9F8ujgKN3n
September (680+m): https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/vV5bafVvaJ9F8ujgKN3n
-
@Anssi-Auvinen keep in mind that Strava does it’s own thing. Also garmins etc.
What I do is parse the altitude from many DEMS to avoid particular faults from services
-
@Dimitrios-Kanellopoulos Strava shows at least same elevation gain than suunto app if you dont do elevation correction.
Here’s those 2 rides merged:
https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/dtWKtQzjB9aahYuSdJTO -
@Anssi-Auvinen I see.
Take a look
Both have identical high and low but not gain and loss. Could that be wind ? Something on how the watch is placed ?
How do you place the watch ?
-
Quite far from identical.But i have been thinking also the placement. In ride one the watch was in right hand and in ride two was attached to bike handlebar with suunto accessory.
Tested this also on tuesday ride, where I made 2 uphills with handlebar attachment and 2 uphills on a left hand. qs link
