Suunto 7 Altitude Issues

Bulkan

@aleksander-h Why are you doing a stationary test?

Aleksander H

@bulkan because I can’t leave the office

Aleksander H

10 m in 1 hour seems not to unreasonable to me. I’ll have to go for a few walks and runs, but I’m guessing things are actually good now! Which is an immense relief

Mff73

@aleksander-h
looks better, indeed

Aleksander H

@mff73 thinking about it. 10 m increase in altitude is more or less equal to the offsett I see on my SSU (I often get roughly 10 more ascent then descent despite starting and stopping at the same place). So it seems fixed!

Now all I have to do is spend the rest of the day tapping the update screen…

Aleksander H

Well. After the update I did a 15 min short lunch walk to get out of the house/office. I’m happy to say the elevation graph looked beautiful! No wonky lines, ascent where I expect it to be, descent where I expect it to be!

Thanks for all the help forum posters!

Brad_Olwin

@aleksander-h If the exercises have the exact same time the app may filter one out. Just make sure you start one 20-30sec before or after they other, then they will sync fine. I have had this happen as well.

Aleksander H

@brad_olwin said in Suunto 7 Altitude Issues:

@aleksander-h If the exercises have the exact same time the app may filter one out. Just make sure you start one 20-30sec before or after they other, then they will sync fine. I have had this happen as well.

I started them both at exactly the same time, and ended both at exactly the same time. So it is definitely no surprise if the Suunto App thought “nope, don’t need that one”.

Thanks for the tip. Hopefully though, my SSU can go back to being a reserve watch now

Mff73

@aleksander-h said in Suunto 7 Altitude Issues:

Well. After the update I did a 15 min short lunch walk to get out of the house/office. I’m happy to say the elevation graph looked beautiful! No wonky lines, ascent where I expect it to be, descent where I expect it to be!

Thanks for all the help forum posters!

Welcome (on behalf of other helpers also ) You are now officially knowledge repository of ascent/altitude issues and official next helper

Aleksander H

@mff73 I look forward to telling people they need to stick a soft toothbrush carefully into the baro hole .

I’ve picked up a few cool tricks along the way. Extracting the zip file from the android app and uploading the samples.json file to qs gave me all sorts of cool stats I didn’t know I could view!

freeheeler

@aleksander-h
Suunto takes care that we grow with our challenges

Egika

@brad_olwin is this new?
so far I have often recorded activities with both S7 and S9 and always have had duplicates in the app.
Now on Sunday it was the first time that I ended up with only 1 activity in SA after syncing the two watches.

cesareluca

Hi all,
I have the same issue with altimeter measurement jumping high and low of about 12 meters. I tested the watch with Altimeter wear os app and the readings confirm the continuous wrong measurement.
Moreover I noticed that gently squeezing the bezel or the back of the watch I systematically can change the altitude up and down.
I think that there is a hardware problem…
Someone can confirm?

Brad_Olwin

@egika No, but to be honest it seems random. I am now making sure my activities start or end 20s apart.

Brad_Olwin

@cesareluca contact support

Mff73

@cesareluca
With same problem, do you eventually try the solution a few post above ? Cleaning sensor is very first thing to do to be really sure.

cesareluca

Solved with a very soft small brush… thanks!

Kurt68

I’m slowly giving up. My S7 was at the service and the sensor is OK according to Suunto. I sent my runs to support for evaluation. No reaction for 2 months. On Thursday the run was good with only 15m deviation. Yesterday on the first flat 500m I had 53m ascent and on a lap with a 200m ascent it was 288m ascent on the S7. I’m curious whether the support will still answer.

Aleksander H

@kurt68 I assume you’ve also tried cleaning the baro hole with a soft toothbrush?

Kurt68

@aleksander-h yes but i’m trying again