Suunto 7 Altitude Issues

[isazi]

@cedric13 I tried importing your file in Runalyze and play with elevation correction. Get between 800 and 1000 meters of elevation gain depending on the altitude provider I use.
So anywhere between 800 to 600 meters less than you measured.
The profile though is not too bad. I’ll see how it looks in QS.

[Mff73]

@cedric13
@isazi
I have no S7, and these issues make me wonder one thing : S7 is syncing with SuuntoApp right ?
Is there any raw data files in Android app folders, like we have for Spartans (at least) ?

For sure, we have not so many tools to fully help for all these kinds of issues

Fit file is nice, but it is Suuntocloud generated, and in this one, no ascent as well, despite the fact there is some ascent meters

[isazi]

@cedric13 this is the altitude profile in QS.

[isazi]

@isazi maybe that climb at the beginning is the error?

[Jamie BG]

@eurohiker - pointless looking at anyting within the 3m range - if I remember correctly discounts anything less than 3m. So yes you can get those weird things where you take a slightly different route and end up with 9m up and 6m down, but at same start point, as a descent wasn’t registered as the variance at the descent points was too small to measure.

I tend to find that this can occur for me, as a lot of the routes I use are reasonably flat with small short gradients, and if I do use slightly different or cirucular routes, rather than and a there and back route, yes I will get different ascent and descent values - due to what is ignored.

Saying that on the couple of higher hikes where altitude has changed by a couple of hundred meters, it has always seemed to pretty much tie in, and match back to contour lines (of course as the contour lines where 20m intervals - as long as I was within that range I am OK.

[eurohiker]

@jamie-bg the 2m was just a small scale example.
Every single activity I did doubled in altitude at the end of the hike. Even though it was stating i was at the correct altitude while at base, peak and when ever else i checked it with the contour lines.
I know it was at the correct altitude because I looked at fatmap, alltrails, gaia gps and read the altitude sign at the peaks.

I’m just stating what my “wavy” data looked like that’s all. It wasn’t my real data.

[cedric13]

@isazi thank you for your analyse.
The climb at the beginning is real, it’s very steep in my area
Maybe a smartwatch is meanly dedicated for townsman geek and not trail runner ?
For my experience S7 is more a nice gadget than a real serious sport watch. I will ask support if I can change for a S9 by example…

[freeheeler]

@cedric13
it is for sure not the successor of mountain men’s A3PS, but I consider it the best split between a smart and sportwatch.
My wife has one and she does happily with it marathon training, swimming, MTB and ski touring.

[Bulkan]

Today s7 and s9b:

[pilleus]

@bulkan said in Suunto 7 Altitude Issues:

s7 and s9b

Do you have a comparison of the absolute altitude between the two watches?

[Bulkan]

@pilleus yes,
66 vs 64,4

[isazi]

Today I did some walking hill repeats with both S9 and S7. Here the results of my comparison:

Ascent and average altitude:

Descent:

Starting altitude:

And then end altitude:

The graph:

S9 was on right wrist, S7 on left.

[freeheeler]

@isazi

[eurohiker]

@isazi

[isazi]

@eurohiker it’s totally different from your kind of results though, I never get the S7 to overshoot. In this case I believe the S9 figures the starting altitude better, therefore the gap, and being the difference less than 10 meters it’s difficult for the GPS to solve it. Unfortunately I don’t have bigger hills to do tests here

[eurohiker]

@cedric13 I’m just updating on my Suunto 7 defect.
“I have replaced your device with a replacement unit that will come with a three (3) month service warranty, which applies if the original devices warranty has expired.”

I dropped it off last Monday morning to a non DHL office (didn’t get handed over to DHL until the next day) and Suunto received it on Wednesday. It’s at the DHL office as of this morning (Monday) and will be at my door by tomorrow or wednesday.
Tip: if you have a DHL office most likely it will be a business day or 2 faster (ship/receive) due to less mail sorting/3rd party hand off.

This is Amazon level customer service. I’m extremely happy that it will be here before a big upcoming hiking and ski weekend.
TDLR: Don’t be afraid to send it in if you really think it’s defective. Its completely free and took a week from small town france to finland.

[mikulass]

Hello sorry if this is off topic…, I am experiencing following issue with S7. It is measuring somehow Descent an not Ascent …, which is 0 m in the app after the activity… and additionally when data are synchronized to Relive and Strava it shows elevation 0 m in those apps as well…(luckily Strava has some correction function for elevation so I can get some elevation there…). I’m using S7 on right hand. Link to the recent activity https://www.suunto.com/sk-sk/move/mikulasstrelecky/6047bd0e148abc47025d3e17
Could it be bug in the sw or in sensor, or any other idea? Thanks in advance. Regards.

[Aleksander H]

@mikulass guess I’m not alone. Been discussing the same issue here https://forum.suunto.com/topic/6114/totalt-ascent-descent-doesn-t-seem-to-match-elevation-graph/17?_=1615327273466

About half way down the thread I discuss having the same issue with 0m ascent. Happened 2 times so far. Both were hikes.

[isazi]

@mikulass the graph shows that there was clearly ascent. Which version of the app are you using? This does not happen to me but now there are multiple users showing this behavior.

[Aleksander H]

@isazi I’m running 4.371 on Android. That said, I have an activity which synced with quantified-self as far back as 31 january with this issue https://quantified-self.io/user/DUrrVK0qMVZO5TtAP0r6Ox2HVLD2/event/48100bfe1ddfeee6242d124cc67d4cbbff0fc13357bac4207d10f0b9d3bfb895