Altitude recording issue
-
-
@sartoric well… don’t know why it started from 0 when - on the other hand - the altimeter was well aware at what altitude we were
-
@sartoric
It started its recording from 0 as the graph but it states that lower point was 1400 something and the highest the peak of the mountain at 2600. So… what’s the deal?
-
if it happened only once, let it be, if it happened again or very often on your watch, I think you’d better contact suunto support
-
@giuliosq
0 belongs to x-axis and is ok as it shows duration.
how does the graph look when you zoom into it?
I have experienced that baro holes (famous topic in this forum) were blocked every now and then. this leads to increased pressure, drops in alti graph and adds more ascent meters to your total ascent, once the baro holes are free again. if you wear your watch tight this might be the reason.
if so, try to wear it a bit loser next time. -
@freeheeler or maybe too low on wrist. My friend went cycling with watch on hand and it counted almost double elevation. He had no clue why. When I gave him my bike mount, everything was ok. He was ‘pumping’ on baro holes entire time
S9P has holes on better place. But still, I thing they should be on other side - 12 o’clock. When it is raining/snowing, water can block them and you get false reading, because normally you tilt your wrist and 6 o’clock is up. Maybe I am missing something… otherwise I give this info to Suunto for free 
-
@Likarnik
Thanks you’re all being very nice. Thought it would make a sort of mix in between gps/barometer for the altitude. Like if you calculate right the altitude from point a to b why should you tell me my elevation is 1000 my more. Like, I don’t understand honestly… you all got that the altitude is correct, right? Why the elevation uphill is wrong?! -
@giuliosq can you zoom on the altitude to check if the readings are as good as they seem, or spiky? Otherwise it’s very strange. If you export the fit or gpx file and import it somewhere else, do you also get this high ascent?
-
@giuliosq
very briefly
point a to point b can be 1200m +, but in between, if recordings are wavy, each up/down will count.
not to say it is your real case.
But maybe you could zoom a little to your altitude graph and see. -
@Mff73 And just to expand a bit: this sort of scenario, when the fibrillation is excessive and doesn’t correspond to reality, causing excessive asc/dsc, is often caused by one of the below:
- Rain + wind
- Obstructed pressure sensor - either temporarily by clothing or contact with skin, or by snow; or by being dirty, rincing carefully and long can help
- Damaged pressure sensor
-
So if you climbed from 1500 to 2700 that the suunto watch recorded that is 1500 ascent.
Maybe share a link with us to analyze what happened .
Thanks a lot
-
@giuliosq
@Spree said in Altitude recording issue:@Mff73 And just to expand a bit: this sort of scenario, when the fibrillation is excessive and doesn’t correspond to reality, causing excessive asc/dsc, is often caused by one of the below:
- Rain + wind
- Obstructed pressure sensor - either temporarily by clothing or contact with skin, or by snow; or by being dirty, rincing carefully and long can help
- Damaged pressure sensor
and bad gps+baro combo
-
@Dimitrios-Kanellopoulos
So… the only things I could extract are the link to my move https://api.sports-tracker.com/apiserver/v1/workouts/export/AHoIJ7p8KEPn7s1A6X-QU8E6Jsp53iWK9YlzE8BWz3Ow82Tvkuf1jai0rP5Z_28vOg==?brand=SUUNTOAPP
And here attached the detailed climb km by km which let you understand that there are obvious drops here and there for which the ascent calculation goes nuts.
I had the watch to my wrist, no gloves, the sensor it was always free. I’m afraid here and there things like jacket and garments might have stuck it. I should wear it on the artist but in top of the jacket then.
-
@giuliosq
Have not put all the screens but here is how it goes. And then in one km it states that I climbed 1700 (I guess to justify the altitude I got to). -
@isazi
I have exported the training gps here:
https://api.sports-tracker.com/apiserver/v1/workouts/export/AHoIJ7p8KEPn7s1A6X-QU8E6Jsp53iWK9YlzE8BWz3Ow82Tvkuf1jai0rP5Z_28vOg==?brand=SUUNTOAPPOn top of this - funny enough - my watch is linked to my Wikiloc account so after each training it saves it there too. And the Wikiloc screenshot states that my ascent was correct (but I guess that’s only a calculation made afterwards, from starting point to arrival). It does not tell any climb average for example.
-
@giuliosq was this the first time it happened? If so, probably the sensor was blocked by something. If not, maybe cleaning the sensor could help (warm water, baby toothbrush, I leave it in the water for 30 minutes or one hour, turning it around sometimes, then brush it gently without sticking the brush inside and under running water).
-
@isazi
I just changed that now front eh suunto 7. So it was the very first ski test I did. I used that for running and trekking. Trekking it worked. Running it takes ages to get the gps signal and sometimes after a minute from the beginning the training app reboots. So that’s another problem too. Anyways. I bought it refurbished so I might send it in again. One other thing I noticed in comparison with the 7 I had is that the running pace on a threadmill indoor with no gps is totally wrong. The calculation made on the moving on the wrist (indoor with no gps) for the pace on the 7 was correct (identical to the one on the threadmill) on the 9 is totally wrong. Tells me I run with a 2’30” per km pace…
