Ascent/descent completly wrong
-
@sartoric and today it happened again. The Barometer Was always free from sweat and not covered with anything. Descending but then suddenly the watch added about 20 m to ascend. So after the hike more than 100 m altitude (ascent/descent) are wrong. And Not any answer from the Support. That’s really annoying!
-
@oliver-zamberger did you try cleaning the baro hole? Warm water, a soft brush.
-
@oliver-zamberger
and a link to the activity to check the graph, please… otherwise it’s just wild guessing for us
-
@freeheeler I’m thankful for any solutions/help
So here is the link
https://www.suunto.com/move/oliverzamberger/60cdf605891a7f7d02f03c1d
-
@oliver-zamberger Was the wach protected by a sleeve? In other words, could wind be a factor in this situation?
Suunto Vertical Titanium Solar
OnePlus Nord 4 -
@oliver-zamberger Here is an example from this weekend. I was wearing an S9P on my left wrist and an S9baroTi model on my right wrist. I was carrying a handheld water bottle. On my right wrist by carrying the bottle my skin was blocking the baro hole on the S9bTi. Not the jagged altitude profile AND note the altitude is 2-fold off. There are two readings for the baro as I stopped the watch a few minutes into the run as it did not connect to the smartsensor.
'
Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing
-
@surfboomerang the watch wasn’t covered by anything. So the baro sensor was always free. Also there wasn’t really any Wind… But if Wind influences the Barometer this much to deliver wrong data, why it ever integrated into the watch
Is there any possibility to deactivate the Barometer?
-
@brad_olwin i can See. It’s totally clear, that the the altitude can’t be 100% correct. But it isn’t ok, when it’s several 100 m incorrect.
And this appears to Happen most when ascending
-
@oliver-zamberger Wind does have an effect on pressure and altitude, but I don’t know to what extent.
This is data from a random windsurf session on flat water:
In the old Movescount days there was an option to select how pressure changes should be interpreted by the watch, but that option has been removed in SA unfortunately.
-
@oliver-zamberger This is the primary reason that incorrect altitude gain happens, I have had this happen due to skin (as in the example I posted) and because of wind. It is something you can learn to avoid. If you look at the profile in my post, it did not happen on the descent. I noticed the wrong ascent, knew what was causing this and kept the water bottle in my left hand on the descent.
I would argue that your incorrect data are likely due to similar issues, once you know what they are you can typically prevent it from happening.
-
@brad_olwin I ask myself: if the watch reacts this much sensitive on sweat, Wind, water etc… IT shouldn’t be used for outdoor Sports what it was made for
-
@oliver-zamberger said in Ascent/descent completly wrong:
@brad_olwin I ask myself: if the watch reacts this much sensitive on sweat, Wind, water etc… IT shouldn’t be used for outdoor Sports what it was made for
I think that your self question is a little bit biased. @Brad_Olwin and others are posting the possible causes of your issue, and it is not brand dependant, it is technology dependant. That you have had a problem, doesn’t mean that the problem is general. I never had had this issue, nor my friends using the same watch, in general S9B tend to underestimate the ascent.
BTW this watch is definitively an outdoors watch, you only need to check all the professional athletes using it.
As you have said in your previous post you didn’t have these issues before, so something have triggered it, a new way of wearing the watch, some holes of the sensor covered or blocked, using poles…If I were you I would start cleaning the baro sensor (warm water and a very soft toothbrush), then a softreset, if this doesn’t work then a reinstallation of the firmware and if eventually still doesn’t works I would contact support, the sensor can be broken too.
-
@oliver-zamberger I will add to @cosmecosta, who said it perfectly. My issue happened only because I was wearing the watch on my right wrist and had a water bottle in that hand. This has not happened when wearing on the left wrist for me. In total, I run 5-6 days per week all year. I have had this issue maybe 3-4 times since I owned the watch in 3 years.
-
@brad_olwin it happened to me twice in 2 years, and it was in days with gale strong winds. I could have avoided the issue by just wearing the watch under the jacket, but I didn’t
-
I had the same problem on the bike today. I used GPS+Glonass after a long time. But it’s true that I was wearing the watch on my right hand (to tan my left hand
)
-
@brad_olwin
uh, this info needs to be censored
regarding sensor hole coverage I fully agree, I happen to see that frequently during workouts. My luck, very very rarely when MTB, skiing or skitouring
but I have never seen a wind effect on the sensor and I went right into a hail storm with my MTB the other day. Maybe the sensor holes orientation in relation to the wind direction is crucial. -
I have noticed that my ascent seems to be drifting further away from what I know it should be. A hill that I run up that always used to top out around 350m now reads around 330ish. The ascent that’s recorded by my training partner is also starting to vary quite a bit with him now always logging quite a few more metres of elevation than myself, for whatever reason I tend to grab a few more metres along the ground so my pace always comes out looking a bit better than his. I’m using an S9B and he has a top of the line Garmin Enduro that’s a little over a month old
For sure it could be his watch that’s out, although I’m leaning towards it being mine due to the fact that his is essentially new; plus when he started noticing the variations in our vert he recalibrated his (I can’t seem to find how this is done on the S9B or whether it’s even possible to do)?
Earlier this week there was a considerable difference of 48m/157ft in less than two hours of running…
TRAINING PARTNER
MEI regularly sync to the app on both my phone and laptop and the latest updates are on so I’m a little miffed
-
@miniforklift
you can try to soak your watch over night in a glass of water, rinse it afterwards a d check how it records the alti on a hill you know well. if this doesn’t help a careful treatment with a soft toothbrush could be done.
it sounds like the sensor is collecting a bit dirt as you say it’s getting off over time -
@freeheeler said in Ascent/descent completly wrong:
@miniforklift
you can try to soak your watch over night in a glass of water, rinse it afterwards a d check how it records the alti on a hill you know well. if this doesn’t help a careful treatment with a soft toothbrush could be done.
it sounds like the sensor is collecting a bit dirt as you say it’s getting off over timeCheers, okay will do this now as I have another run with my training partner tomorrow morning. Should be similar to the one we just did so will be interesting to see if improves things. Thanks
-
i found this problem as well with trail running.
suunto app show 3638m as ascent , but when syncing this same workout to strva it show only 1083.https://www.suunto.com/en-gb/move/usaratohm/60e0784b1dc2d5647adaa446
https://www.strava.com/activities/5568664347
