Continued Incorrect Ascent Readings

[sartoric]

@zvonejan said in Continued Incorrect Ascent Readings:

2 sides ( altitude, barometric changes)

actually, barometric changes (the sensor is a barometer) will be interpreted as altitude or weather changes.

For Ambit (and in the past for Spartans+S in MC) you can set in which way sensor data must be used.
Readings are 100% correct if you set this option correctly
Now on Spartans+S this option is “always” set to automatic and switches based on the other data

[zvonejan]

@sartoric said in Continued Incorrect Ascent Readings:

@zvonejan said in Continued Incorrect Ascent Readings:

Readings are 100% correct if you set this option correctly

Only on stadium with barometer mode. If you set watch to altitude or automatic mode and run trail running, there is no guarantee, that all ascent difference is from altitude (some percentage is definitelly from weather changes). Only for old suunto watches of course

[sartoric]

@zvonejan
Well, yes, if you do trail running in “alti” mode and the weather is rapidly changing too the result could be distorted

[freeheeler]

@Nick-Vlahandreas
try Dimitrios’ suggestion with the buff…
I can write books about wrong readings when the strap is too tight or when the wrist position pushes the watch against the arm e.g. during gym workouts etc

[Dimitrios Kanellopoulos]

@zvonejan no you are absolutely right. Not only for that sport of course. If I recall correct (will check that for you) the track and field mode has that set for you. Of course to have some customization (ability to select) is welcome. I wont argue.

That said, have you used the track and field mode and got asc/desc values ?

[mario_b]

@Nick-Vlahandreas what does the ascent/descent values look like in the watch? when you review the activity? do you see the same?

[Dimitrios Kanellopoulos]

@mario_b I checked it for him yes they are the same.

[mario_b]

@Dimitrios-Kanellopoulos ah ok. i think the .fit file would be nice. another test would be choosing (just for testing) running while mountain biking. if that would not count the small up’s and downs, so it would only be a problem with the calculation under the mountain biking profile/app/sport activity.

[mario_b]

@Dimitrios-Kanellopoulos looking at the jumps i think with the fit file, an fit file explorer (viewer) would show nearly 1200-1300 hm too. because this jumps are not 1 or to meters. more 4-5 meters and very often. adding them together it would result in this high number. i don’t know the track. but if there are many small hills, it would be possible.

[Dimitrios Kanellopoulos]

@mario_b I passed it to a DEM and the user is right. Those ±5-10m dips should not be there. There is something wrong with the device or the way its used .

[zvonejan]

track and field mode and got asc/desc values ?

What is track and field mode?. If you run on stadium and watch is set to barometer ( ambit series). watch will fix altitude and all changes of presure will result as weather changes. But now on s9 for example, probably watch will show some altitude changes ( but we all know, there in no altitude changes on stadium with flat surface :))

[Dimitrios Kanellopoulos]

@zvonejan activities -> running -> track

[Dimitrios Kanellopoulos]

@zvonejan but I though it was a special sport mode… now I undersatnd its a basic for running …

[ollemelin]

I have had bad ascent readings with my 9 baro since i bought it. The cut-off-point for when an ascent is not counted is way off. As both me and my wife are educated survey engineers we have actually done measurings with top end gear at the local tracks, and the 9 baro is always loosing halft of the climbed meters.

I guess its a general problem for sport watches, but it would be an easy thing for the suunto app to calculate against the terrainmodel that the route planning tool is using and calibrate the workout.

[freeheeler]

@ollemelin
I don’t trust the route planning tool in regards to total ascent. When I plan, I get predicted total ascent of around 125 to 130% of the actual total ascent.
I once checked it with S9B and A3PS. Yes S9B is a bit short on ascents but way closer to A3PS than the planned route…
despite that, I have in memory that Suunto is working on a fix

[ollemelin]

@TELE-HO Yeah, it also depends on where in the world you are, but the terrain model in suunto app is quite good where I live in sweden.

With that said, the baro-measuring works greater on longer uphills :).

Now I’m just waiting for better GPS-readings where there are trees. It’s hard to avoid them in sweden ;). But my last garmin was even worse on that.

[freeheeler]

@ollemelin
when the reliability of a map ascent is depending on the location I basically don’t trust it and rely on the baro and gps combination that might be off to some extend on bad days, but not that far off like the maps are in my region…
the following route was measured to 7.00km with my S9B and 181m ascent. I replicated the route planning just before… I ran exactly that route.

You are right for consecutive and long climbs. The watch has less or let’s say almost no issues with that… but the calculation for rolling hills is more demanding and if you search the forum, mr silentvoyager, who regrettably did a Suunto exit (I will not abbreviate that here…) had good inputs and wide discussions about that topic. @Dimitrios-Kanellopoulos is aware of that and hence Suunto, too

[mario_b]

@TELE-HO i know what you mean, but i would not care to much about meters in 10 increments. i care more of the 100s of meters.
a good example of a detail where i have to say, the elevation map is good, the trail is good, and the calculation of suunto is good. but here you can see why such calc’s are happening:

the trail is only ascending here. but the small turns return in a crossing of elevation lines. so in real the ascent is 120 up and no descent. such sings will always happen, on any rout planning platforms. but i can’t say, the did a bad job. it’s just the fact, that the calculation is only as good as the maps.

[zvonejan]

@TELE-HO

I don’t trust the route planning tool in regards to total ascent. When I plan, I get predicted total ascent of around 125 to 130% of the actual total ascent.
I once checked it with S9B and A3PS. Yes S9B is a bit short on ascents but way closer to A3PS than the planned route…
despite that, I have in memory that Suunto is working on a fix

This is not problem of Suunto :). Suunto does not have own database with altitude data. Look at the track created, it is very serrated or wavy which increase acsent a lot

[zvonejan]

route created on movescount

actual route recorded with s9b

ups it is inverted i created from end to start