S9 barometer problems

[Anssi Auvinen]

@cosmecosta Yes, I will contact support again. I don’t know have you read the whore thread, but seems that may barometer is not sensitive as it used to be. It used to give more meter but now it cannot react as fast as it used to do.

[cosme.costa]

@Anssi-Auvinen said in S9 barometer problems:

@cosmecosta Yes, I will contact support again. I don’t know have you read the whore thread, but seems that may barometer is not sensitive as it used to be. It used to give more meter but now it cannot react as fast as it used to do.

Yes I read all the thread. But, did you try the hard reset, reflashing the firmware? Maybe you save some days without the watch.

[Anssi Auvinen]

@cosmecosta Yes, I have done the hard reset last week.

[fazel]

@Anssi-Auvinen My ride yesterday.

Plotaroute: 4199 ft
Garmin 830: 4075 ft
Suunto 9 Baro (mounted on handlebars): 2993 ft

I’ve let it sit in warm water twice in the last couple of months. I’ve had issues on the bike since I got the watch. I assumed it had to do with me wearing it on my right hand in previous rides as the barometer opening would face into the wind, potentially affecting the measurements. I also assumed it was fixed. I haven’t rode with the watch in a long time but yesterday’s ride seems to suggest it’s still an issue - even with the watch mounted perpendicular to the bike’s movement. I shared this data with Suunto back in 2018 but never heard back.

https://docs.google.com/spreadsheets/d/1llLMEgMqTu6i0fUzrCg5AOTV45ZKkcDlKtj-24kGihI/edit?usp=sharing

[freeheeler]

@fazel
do you have this issue again or still?
did you hear about the fridge test? despite that, it looks something is wrong…
but could you please also share the alti profile of the watch and how it should look like?

[Dimitrios Kanellopoulos]

@fazel do you have 2 fit files for me ?

One from.the suunto
One from.the Garmin ?

[fazel]

@Dimitrios-Kanellopoulos Sure - PM or post here?

[Dimitrios Kanellopoulos]

@fazel as you please

[fazel]

@Dimitrios-Kanellopoulos K - here you go.

Suunto.fit Gramin.fit

Hadn’t thought about loading them into DC Rainmaker’s Analyzer tool. This is what I see (blue is Suunto). They track well, Suunto is just consistently low.

[Dimitrios Kanellopoulos]

@fazel said in S9 barometer problems:

2993 ft

nothing is wrong here.

Edge counts ascent even with ±1m bumps and affected by wind if it has a baro.
Suunto 9 counts every ±3m

Here are the charts

Stats if I use 1m resolution for counting ascent

Stats if I use 2-3m resoltuion / filter for counting ascent

Using Runanalyze to check the elevation data

I see as I said above that the 3m filtering is working the best. Take a good look below.

Now lets see what other Digital Elevation Databases say

Corrected to RaceEvelation service much much less ascent!

Using STRM and other services for correcting the data:

Take a good look please at the report. I did spend time todo this.

My conclusion:

Your Garmin records ascent every little bump that you take, more over it’s less realistic and out of coordination from most Digital Elevation services I used.
Most of those services are aligned with your S9 baro as you can see.

So your garmin overregisters ascent. Take this with a grain of salt but I live in NL. If I apply the same philosophy at some flats I ll be ascenting like 100+ meters that is not realistic. -+1m changes should not be reported as they do not really contribute to any effort the user should take into account for his performance lever nor data wise. That is counting noise basically.

[fazel]

@Dimitrios-Kanellopoulos Thank you for the time to put this together. I will read it over when I get to work

[Dimitrios Kanellopoulos]

@fazel a thing you can test your self.

Upload a ride to Runanalyze. There you can play with this (see screenshots)

[isazi]

@Dimitrios-Kanellopoulos said in S9 barometer problems:

So your garmin overregisters ascent. Take this with a grain of salt but I live in NL. If I apply the same philosophy at some flats I ll be ascenting like 100+ meters that is not realistic. -+1m changes should not be reported as they do not really contribute to any effort the user should take into account for his performance lever nor data wise. That is counting noise basically.

I wrote something similar just days ago
And yes, my Edge registers hundreds of meters of ascent in Amsterdam, that gladly Runalyze fixes on its own.