ANYONE CAN HELP ME WITH METERS CLIMBED???
-
a few days ago, i publish a similar problem… my suunto 9 have problems with the acumulated meters climbed. it works with gps because its the model without baro.
in the other publication i explained that the acumultaed meters was wrong, comparing with anoteher suunto baro, and garmin fenix 5.
today, i have a problem that is not the first or second time.
yesterday night i sincronise with pc my suunto. i have all the latest versions of firmware and suuntolink. today i start looking for gps and cardio, and when it was ok, i wait 5 minuts for take a best signal, like the suunto support tell me…i start the run move, and my street was downhill direction, but the gps give 12 meters of climbing, and i was running downhill!! i have this problem more than 5 o 6 times, and i dont understand…in suunto support tell me all the correct things for the good work, and i know this, but doing all this things, not works well.
i do 2 times a full reset with suunto link.
what can i do? this is the move of today, the first km its wrong because i go downhill and have meters climbed.http://www.movescount.com/es/moves/move303957649
but in strava, the first km its correct…why suunto its having this mistake,and strava give the good value??
if i cant solucionate this, im thinking make a change to garmin 5
thank for your time and your answers
-
@Carles-Merin
It seems that even you do all things right, your first minutes are quite strange : 32km/h, Ascent instead descent.
Looks GPS was not good enough at the beginning.
Why? No idea. -
The reason Strava shows correct elevation profile and elevation gain is that for non-baro devices it ignores altitude data from the uploaded FIT file and instead uses its own elevation database.
In contrast, Movescount uses GPS elevation from the watch in this case, which is known to be fairly inaccurate. If you care about accurate elevation you should have gotten a baro model.
