Ambit3 Peak elevation gain
-
@TELE-HO Okay - I did NOT adjust the altitude before. So it must be something else…the ascent was corrected when sent to Strava but I assumed Strava did that as SA still has to messed up values.
-
@fazel
what graph do you see when you upload it to QS? -
@TELE-HO here’s what I see…
-
-
@fazel
I would get in touch with customer service -
@TELE-HO thank you.
-
@fazel
not much help from my side, sorry.
Sometimes the sensor can be dirty but a graph flying higher than Everest… never seen before. -
@fazel said in Ambit3 Peak elevation gain:
@TELE-HO here’s what I see…
Run into much JFK-LAX traffic up there?
-
@Fenr1r I’m dyin’ over here…
-
@fazel that is quite a jump! Strong legs!
-
@Brad_Olwin haha. You agree - contact support?
-
@fazel make sure baro sensor holes are not clogged and weren’t. Then support.
-
correct. The baro holes on the A3P are very prone to be clogged. Or sweat etc.
-
@Dimitrios-Kanellopoulos said in Ambit3 Peak elevation gain:
Or swear etc.
I can’t curse around my Ambit? Damn, that’s restrictive.
Oops.
-
@Fenr1r lol
-
Hello, so today the same problem after skimo. The watch shows in logbook ascent 792 m and descent 1179 m. I am posting link to Strava activity (where I have corrected elevation) as I do not have my smarthpone right now with me and cannot share from Suunto app. I have synced the watch with Suuntolink. I have cleaned the baro hole. Any more ideas? Thanks.
-
I think I win.
-
@fazel Nah, you’ve just peaked.
-
@dominikbalko looks like your descent is correct and your ascent is wrong. Do you have auto-stop on? Sometimes ski touring is so slow in the uphill, that the watch pause the activity. In that time you don’t collect ascent.
-
@marcrie Yes, I have it on. You are correct, I will try it next time with off. Thank you for help.