Suunto 7 Altitude Issues
-
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…
-
@Jamie-BG the ascent calc works like:
If >3m acent is done in less than 3 minutes then register it.
In order to prevent pressure drifts.
Another case can be the calibration of the start point but I doubt that
-
I have to say that the barometer/altimeter of the Suunto 7 disappoints me now and then. Yesterday for example, I did a run starting and ending at the same point 77 meters above sea level. In the workout summary the altitude profile reads 56.5 meters at the start and 82.4 meters at the end. So the end reading is not that bad, but the start is no good. And the first 300-400 meters I actually ran down (and not up!) to about 65 meters above sea level. Could it be that FusedAlti isn’t correcting the whole profile? Or is the barometer sensor of bad quality?
-
Same here. The darker one is the Suunto 7 and the lighter one from a Lezyne Mega C. The Lezyne is more or less the same as what Strava would have after the correction.
It’s a short ride of about 9 km. -
When I had my S7 it was constantly showing negative altitude numbers even though I was on a bridge.
-
@Lars-Klemmer Is it not possible to change the altitude like the Suunto 9?
-
@Eric-Verwoerd-0 not sure if you can in the watch, but the app does have an elevation offset in its settings section.
-
@Jamie-BG that setting is for activities recorded with the app, not the watch.
-
@Lars-Klemmer Just like to see if your S7 has been sent for service, and the result. My S7 is having more or less the same issue - excessive up and down recorded even on flat terrain. Today’s 1.4 hour run ended up with 393m ascent and 386m descent. When I look back history records 7 out of 10 had this issue to some extent. By the way some history records had comparisons recorded with S9 and SSWHRB, on flat terrains they recorded very minimal ascent/descent.
-
@Eric-Verwoerd-0 No, it is not possible
-
@vr2udt if a replacement unit has the same issue, maybe it’s something else?!
How are you wearing your watch? Under clothes? Left/right arm? Windy conditions?
Anything else that could affect the built in pressure sensor?
Thx -
@Egika Hi Egika, it’s not under clothes, not particularly windy, tried on both left and right wrists, same. GPS track and WHR were both good, just the ascent/descent over-counting. The altitude reading was quite off (20-30m) too, supposedly FusedAlti should kick in to adjust altitude reading after some duration of good GPS reception in the open, but didn’t happen. When comparing with either S9 or SSWHRB, wearing together with the S7, those 2 were consistently giving correct altitudes and ascent/descents. I phoned tech support today, the advice was to wait until the latest firmware is pushed to the watch, update it, then observe again.
-
@vr2udt said in Suunto 7 Altitude Issues:
@Egika Hi Egika, it’s not under clothes, not particularly windy, tried on both left and right wrists, same. GPS track and WHR were both good, just the ascent/descent over-counting. The altitude reading was quite off (20-30m) too, supposedly FusedAlti should kick in to adjust altitude reading after some duration of good GPS reception in the open, but didn’t happen. When comparing with either S9 or SSWHRB, wearing together with the S7, those 2 were consistently giving correct altitudes and ascent/descents. I phoned tech support today, the advice was to wait until the latest firmware is pushed to the watch, update it, then observe again.
Could be, that due a diferent position of the sensor holes for some reason you are blocking them during the activity?
-
I had issues. at some point. Issue was that I was showering with the watch and the little hole there was full of soap and stuff. Try cleaning it up and drying it up. Soak in water , flush under the tap water with some pressure and repeat 2-3 times.
DO NOT insert anything in the pressure hole
-
@Dimitrios-Kanellopoulos Thanks both for the suggestions, actually I have been following previous threads about the baro sensor cleaning and tried the submerge overnight in soft water with little detergent then rinse procedure. I will complete the update shortly and see if it helps.
-
@vr2udt FYI
I had a friend Damian who is a tester. He had altitude issues with 2 watches from the test builds. I sent him in the end mine (I though he was unlucky). Mine would work ok.
Then mine started to work bad. His issue in the end was that when he showered / washed hands there was always humidity stuck inside the pressure sensor. That resulted to similar charts to yours , aka “leaking pressure”.
Lets try todo this if you like.
After the cleaning and all, please do not wash, / have water contact with the watch for a few days (1-3). Observe if this imporves the situation.
-
@Dimitrios-Kanellopoulos Now I almost soak all my watches with Baro overnight to clean them before any serious activities involving heights