S9 barometer problems
-
@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
-
@Anssi-Auvinen if you wear the watch on your write wrist, the baro sensor is facing toward the headwind. I can imagine this is causing such issue.
-
@halajos There was no error when watch was in the wrist, it’s now when it is in the handlebar. And I write with my left hand, so I do not wear it in the write wrist
-
@Anssi-Auvinen said in S9 barometer problems:
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
For sure this is a difference no doubt. I meant thought that the high is ok. (and the low).
In regards to wind / hand placement
2 potential probs.
- As noted headwind (even if it doesnt exist)
- Left hand can block the sensor if you push / lean on the bike.
To wipe out completely outside / wind factors imo the best apporach is either the bar or just in a pocket (if you want to be really picky) .
In regards to this:
-
@Dimitrios-Kanellopoulos The “old” data with riding in the right hand just seems more accurate so I don’t think the placement is the problem.
Barometer just is just not sensetive enough anymore and is not reacting quick changes of altitude. And theres lots of those when gravel riding here in countryside.
But is the cause that watch is broken or still barometer is too dirty even after cleaning? Or is the problem in the updated software?
-
@Anssi-Auvinen said in S9 barometer problems:
Or is the problem in the updated software?
The only thing I know is that in the last update we literaly din’t change anything for Alti or GPS
-
@Dimitrios-Kanellopoulos And if I remember the earlier update was in earlier in the spring.
-
@Anssi-Auvinen correct.
