Ambit3 Peak elevation gain

[freeheeler]

@fazel
this definitely is a hectic example of wrong altitude recording!!
I find it crazy that this topic cumulates in the recent days… might be coincidence?!

I’ve had a conversation with @Dimitrios-Kanellopoulos because I noticed during a trial that the alti graph is drifting while I just put my watch stationary on the balcony and started an activity.
The baro sensor is sensitiv to temperature change, BUT we should not notice it as FusedAlti corrects it on the fly (and backwards afaik).
Maybe, just a first thought: is your sensor dirty or the holes clogged? Or did you manually adjust your start altitude before you started this activity?

[fazel]

@TELE-HO Does the Ambit have FusedAlti? This was recorded with an Ambit3 Peak. I didn’t think they had this feature. The crazy thing is, the first time I ran with this watch after a long period of using the 9 Baro, it performed flawlessly. But the last two times I’ve ran with the watch, both on this rails-to-trail which is flat, I’ve had elevation errors…

[freeheeler]

@fazel said in Ambit3 Peak elevation gain:

Does the Ambit have FusedAlti?

yes it does.
if you manually adjust altitude before the activity FusedAlti is deactivated and the elevation is more sensitive to mistakes due to weatherchange, temperature etc… but not to that extend IMHO

[fazel]

@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.

[freeheeler]

@fazel
what graph do you see when you upload it to QS?

[fazel]

@TELE-HO here’s what I see…

[stromdiddily]

@fazel

[freeheeler]

@fazel
I would get in touch with customer service

[fazel]

@TELE-HO thank you.

[freeheeler]

@fazel
not much help from my side, sorry.
Sometimes the sensor can be dirty but a graph flying higher than Everest… never seen before.

[Fenr1r]

@fazel said in Ambit3 Peak elevation gain:

@TELE-HO here’s what I see…

Run into much JFK-LAX traffic up there?

[fazel]

@Fenr1r I’m dyin’ over here…

[Brad_Olwin]

@fazel that is quite a jump! Strong legs!

[fazel]

@Brad_Olwin haha. You agree - contact support?

[Brad_Olwin]

@fazel make sure baro sensor holes are not clogged and weren’t. Then support.

[Dimitrios Kanellopoulos]

correct. The baro holes on the A3P are very prone to be clogged. Or sweat etc.

[Fenr1r]

@Dimitrios-Kanellopoulos said in Ambit3 Peak elevation gain:

Or swear etc.

I can’t curse around my Ambit? Damn, that’s restrictive.

Oops.

[Dimitrios Kanellopoulos]

@Fenr1r lol

[dominikbalko]

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.

https://www.strava.com/activities/4636938377

[fazel]

I think I win.