Suunto 9 baro very low elevation gain vs other brands

[Oktan]

Is there an email / link to support contact form (I looked and didnt found one), where users can complain about the elevation issue?

[Dimitrios Kanellopoulos]

@Oktan here is one place we are about 5 fieldtesters here for suunto here , and 3 debating.

[Dimitrios Kanellopoulos]

@fazel I spent some time again with your files and passed them through various services and still the ascent is reported lower from all dbs except Strava.

Try loading your ambit file to runalyze

So you can see above corrected and uncorrected.

Now I loaded both files to qs.

The altitudes are not so similar. One of the 2 had a fault probably due to some hand movement.

Take a look

You can clearly see that the ascent was missed by the s9 not due to some software but rather to different readings especially at the end that the diff is quite close to the ascent diff.

Again the algo is the same for all watches , what you experience is more of pressure sensor changes.
You ask 2 things:

1. To lower the threshold. Due to filtering out outliers this doesn’t sound right and many testers and SUUNTO don’t support it. We play on the safe side. Climbing a mountain is ok. Climbing your porch bench 2000 times and hitting everest or running on the beach facing wind and getting 2000+ ascent (I have examples) I don’t endorse personally nor from what I understand suunto.
2. To change the hw or position of the sensor ? (Not possible)
3. To change the gps chip or ad an antenna? Not possible atm.

Now, while this conversation might help someone , I will be leaving this thread for my sanity.

It’s pretty much the Nth time we look into this and actually there is no issue. I would like to spend my time with improving qs.
I cannot debate anymore on a saturated issue that has been iterated and tested from people (100+ fieldtesters) to machines that run the watches on rails. While we can argue that you want to register even 1 cm chnages as ascent Suunto and the RD team has chosen diffently and has chosen the filter and algos for each sensor that makes sense for the atheltes. Each watch from a3 to ssu to s9 has a different sensor and different sensor position with different pros and cons. For example a3 is prone to sweat while ssu is prone to wind and jackets. If you are not pleased guys and thus really bothers you to loose those 0.34 meters climbing everest or lifting your hand, I understand that but I personally don’t won’t to be bothered anymore. You can continue the debate here or anywhere else (contact support etc) but this is very very improbable to change any time soon. This might be improved at some point as a generic change for all watches and there are testers and a bigger team to validate that.

Have a happy new year , and my advice is to try to be healthy and not dictated by a tenacity. It is what it is.

Over and out from here.

And hey!!! Important:

You are doing great guys into looking into these stuff. I would do the same. I am not at all trying to stop you! Just want to be clear ️ . There is no problem adding any feedback here @fazel @Oktan etc. Please go on.

[Egika]

@Dimitrios-Kanellopoulos and that post should be made a sticky one

[Oktan]

OK. then last sentence from my side:

I’m a programmer too.
If I had in my program a constant (that its value can be argued) which fits 90% of the users, but the other 10% nagging the same issue over and over and consuming 20% of my time for explanation & proof - I would consider to let them change it (just a bit) for their own fine tuning ( and hapiness ).

[Dimitrios Kanellopoulos]

@Oktan the best would be (although not easy) to allow you to change that. Suunto cannot change it for all because then the other percentage will complain then for example.

I think that is the best solution for all. User power.

[Oktan]

I meant that 3 will be the default threshhold in the setting so the 90% will obviously wont change it, hence will not complain.
Anyways, thank you for your time, patience and all that you do for us.

[Dimitrios Kanellopoulos]

@Oktan yeah I got it pal.

[fazel]

@Dimitrios-Kanellopoulos Sorry - I thought my data was unconcerning and should have been clear. For me - this was within an acceptable range of deviation. I was relieved to be honest. You didn’t have to do all of this. I apologize for frustrating you.

[Dimitrios Kanellopoulos]

@fazel no no. It’s ok. I just wanted to explain that many times we can miss some fault etc.

To be honest if I could I would make you a tester as you did take the time Todo that great run and compare.

Actually at your data the s9 I think did a boo boo at the end as I said which I reported.

[fazel]

@Dimitrios-Kanellopoulos thank you - are you referring to the GPS track at the end?

I would love to be a tester. If that ever becomes a possibility please let me know.

[Dimitrios Kanellopoulos]

@fazel no at the elevation difference if you take a look.

[fazel]

@Dimitrios-Kanellopoulos oh wow. I see it now.

[freeheeler]

I went backcountry skiing with my friend who has well deserved and honourable inherited my A3PS. Of course the watches were not on the same arm, hence a comparison with the slightest scientific touch isn’t possible. However I would like to mention here that we went in the exactly same ascent track and his A3PS recorded around 100m less total ascent plus had issues with the track on the first few meters.

My takeaway is that S9B is not inaccurate at all.
Plus: it’s crazy good to enjoy sports without having issues like these in mind life is easier when we don’t worry

[Oktan]

@TELE-HO Can it be that his jacket blocked the barometer hole for a small period of time, and yours didnt?

[freeheeler]

@Oktan
no, not on A3PS and also not possible when I check the graph

[stromdiddily]

Interesting one for me today…S9 more than doubled the ascent/descent on my route. Green graph is a lot more jagged than the typical results.

Pouring down rain today but it was constant the whole time.

[fazel]

@stromdiddily so light green is today, dark green is a track from the same route ran in the past? I see this sort of delay with FusedAlti, @Brad_Olwin has as well.

[stromdiddily]

@fazel green is today, yellow-ish is from three months ago on the same 7 mile route. The start looks ok tbh but the green is reporting over 1k feet of climbing and the yellow is correctly showing 500ish feet.

Edit - QS feature request, ability to assign colors to merged tracks

[freeheeler]

@stromdiddily
the spike-ish graph looks like hydraulics did magic on the sensor… it’s a wild guess, but possible