NO GOOD DATA ASCENT (AND DESCENT)

[Matteo Zambenedetti]

Re: GPS altitude meter
Hi everyone, I have a 9 Baro and a problem with measuring the ascent (and descent). The difference with the real one is around 15%, what is the solution?

[freeheeler]

@matteo-zambenedetti
could be several reasons… it’s in-depth discussed in here already
check if the graph recorded has unrealistic spikes (down and up again). if so: the baro holes were covered.
other reasons could be dirty sensor, manual calibration before the activity or wind gusts during stormy weather.
we’ll find out if you share the graph or the link to your activity with us

[isazi]

@matteo-zambenedetti we need to look at the route before anyone can answer

[Matteo Zambenedetti]

@isazi I try to senso It. Hiking_2022-06-19T02_32_03.fit

[isazi]

@matteo-zambenedetti also, does it measure more or less than you expect?

[Matteo Zambenedetti]

@isazi much more. In this track the real ascent is about 1500 MT, 9 Baro says about 3000 MT…this morning, real about 500, 9 Baro about 650

[freeheeler]

@matteo-zambenedetti
and the graph doesn’t match the topographie of the recorded track if I’m not completely wrong. but it doesn’t exactly look like the sensor was covered.
did you calibrate the altitude manually just before the activity?

[Matteo Zambenedetti]

@freeheeler yes, both times. Do I have to reset It?

[freeheeler]

@matteo-zambenedetti
no… next time: don’t touch it if alti is completely wrong, just start your activity. FusedAlti will calibrate it for you and will do it also throughout the activity when it compares to gps alti and detects it’s shifting

[Matteo Zambenedetti]

@freeheeler OK I will do. A question: Does Fusedalti start automatically when I start my Activity?

[isazi]

@matteo-zambenedetti yes, during the first 15 minutes.

[Matteo Zambenedetti]

Good morning everyone,
I return to the subject to post some files to better explain my problem.
First of all, I don’t understand why SUUNTO does not provide software for pc but only apps for android (or mac) …
So, this is the screenshot of my hike according to the data of my 9 Baro and the app Suunto in my phone

ASCENT 3168MT!!! UNREALISTIC!!!

and this is the screenshot of the same track but downloaded on Openrunner software

ASCENT 1368MT!!! REALISTIC!!!

and this is the track.gpssuuntoapp-Hiking-2022-06-19T00-32-03Z-track.gpx

can anyone help me to understand and solve the problem?
what is the exact procedure to follow before starting a hike or a bike ride?

I apologize if I can’t answer right away but I’m working and I don’t have much time

[A Former User]

@matteo-zambenedetti what is the problem?
If you start higher than 1800m, and climb till 3200…at least roughly: 3200-1800=1400.
You have some other climbs on the graph, but also, you start higher than1800, so I can’t understand where is the issue.

[cosme.costa]

@matteo-zambenedetti Can you also share the ascent graph in the Suunto phone app?

[Matteo Zambenedetti]

the problem that openrunnere says I climbed 1368 meters (correct) while summarized says that I climbed 3168 meters (wrong)

[Matteo Zambenedetti]

the .gps track that posted before cannot be opened?

[cosme.costa]

@matteo-zambenedetti I understand that the watch says the same than the Suunto app, am I right?

I want to see if the ascent graph from the watch has spikes, so it means that for some reason the baro sensor has been blocked (skin, jacket, wind,…) and for that reason you have higher ascent than expected.

[Matteo Zambenedetti]

@cosme-costa I understand what you mean. I therefore report the profile of my excursion: you will notice that there are no peaks.
However, if there were, Openrunner would have had to show me the same rise as Suunto. My problem is why was my 9 baro wrong?

[freeheeler]

@matteo-zambenedetti
because of several small spikes that I can already see without zooming in… maybe the other platform filters it by default? Strava filters by request

[Matteo Zambenedetti]

@freeheeler Does your 9b the same?