Suunto 7 Altitude Issues
-
@Bulkan Thanks. Signed up to Quantified Self. Thus far it hasn’t imported any of my previous activities (not sure if it trying to access data from SportsTracker or from Movescount - either way it is blank!).
The web UI for the link above is a lot cleaner in design than SportsTracker.
-
@Vinay-Menon You are welcome, here we have the creator of QS @Dimitrios-Kanellopoulos
About the import I think it works with Suunto app but not with movescount.
-
@Bulkan Thanks. I checked Quantified Self and it looks like it does not import historical data automatically. I believe the sync works from the day its setup as a service. Looking forward to using as it starts importing my runs.
-
@Vinay-Menon give it a history import there. Should be able Todo that via services.
-
@Lars-Klemmer to me it looks like pressure sensor issue. At s7 I have only seen a few.
2 options.
- Clean with water etc
- Ask for replacement
-
@Dimitrios-Kanellopoulos Thank you for your support!
-
@Lars-Klemmer you can search the forum for tips from various users on how to clean your watch with warm water.
-
@Dimitrios-Kanellopoulos Awesome! I should have clicked through the other tabs. Have kicked off the import. Many thanks.
-
@Vinay-Menon you can keep using this [1] post to talk about QS.
[1] https://forum.suunto.com/topic/3490/quantified-self-io-the-topic-for-qs-discussions/
-
@isazi Many thanks. Much appreciated.
-
@Dimitrios-Kanellopoulos A check with the aro trend app showed the correct air pressure without dropouts. the sensor works correctly. Could it be the suunto watch app?
-
Hi! Same issue here. Altitude readings total mess. Shows 10 to 20 meters when for runs on flat surface
-
@D-K very strange, try contacting support because most users, including me, have good altitude readings with the S7.
-
Just tested altitude readings of my S7 and they look terrible.
On a bridge the altitude reading says -11m and when coming back via the same bridge it’s 20m.
I don’t usually follow altitude so it’s not a big deal for me.
Does it have an effect if I had my phone with me, I mean does it in this case take readings from phone gps or something? -
Today my altitude readings from the Suunto 7 disappointed me. I was doing laps on a 400 meters running track. The altitude varied from 116 meters up to 125 meters and back down to 112 meters, all within 20 minutes.
-
@aeroild that I suppose is ok. Even gps can have this.
The question is: did it happen often ?
Pressure can chnage (the sensor) due to outside conditions or eg wind jnthe pressure hole.
If you wear the watch at the right hand perhaps due to arm swing this happened
-
To be clear. 10 meter wrong reading is very low error if it happens rarerly.
-
@Dimitrios-Kanellopoulos Last time I did laps on the track the altitude reading didn’t fluctuate this much, so I guess you are right about it not being a problem. I guess I am disappointed because the error in the readings got very visible.
-
@aeroild I understand that well friend. It could have been something that happened once ?
I know the feeling. I always look at data and get pissed if eg I get wrong distance or altitude and notice those as you do.
I am only giving some “advice” in the context of experience aka I have seen things.
-
Why do my Ascent and Descent readying not tie back to the range between my lowest and highest point. For example the lowest point is 111m, with highest 171m, however my ascent was only 49m (so how did I get to the 60m higher point?) and my descent was 66m which I can live with as is close enough to the range and suggests it is more correct than the 49m.
I also do a lot of tracks where I go in one direction then turn around and come back the exact same route. Surely in this case my ascent and descent should be the exacte same but they generally aren’t and like the above case, seldom tie back to the range…
