Suunto 9 different ascension depending of sport mode
Good day all,
Anyone else have a big difference in elevation gain depending of the sport mode they use to track their activity?
According to my watch, for the same trail, if I use the trail running mode I will get around 7m of ascension gain on my small run. If I do the same trail with the snowshoe mode, I get around 20m of ascension gain.
Considering that this small loop is less than 5km and really flat I think the trail mode is more accurate but if I compare to my running partner (who use a Garmin) we will have an approximate 150-200m of difference on elevation gain on our long runs (around 30k) and this was also tested on an official race, same course, same distance, same day.
A little background, I have a Suunto 9, most recent update. I have tried both GPS + GLONAS & GPS + GALILEO. All my runs are done with the Performance mode selected for battery life/ GPS. I’m in North America (CAN, Ottawa).
Please advise, I love my Suunto but having that much of a difference in elevation gain accuracy is concerning. (for the US people out there, 200m = approximately 650 ft.)
Thanks (sorry english is not my first language)
welcome to the community.
you apparently have a non baro S9, right?
the ascent calculation on non barometric devices is not very precise.
there are some discussions ongoing already, you will find them with the search function or checkout these 2 links:
Thanks! This is correct I have a non baro S9.
I understand that the accuracy is approximately 7m difference between the Baro and non Baro model. That I can live with but having a difference using the same watch in different mode, is what concerns me.
I would like not to have to change to a S9B not even a year after getting my S9.
Consider that, since your watch rely on GPS data for altitude evaluation, bad signals can affect measurement.
To be sure that the issue is due to the sport mode, you should have 2 watches recording the same activity (at the same time) using 2 different sport modes … of course, easier said than done
Do you have always the same results ?
I understand that the accuracy is approximately 7m
In fact 7m is the non baro threshold to recognize altitude modification
For baro watches the threshold is 3m
To answer your question, yes I do always get the same results. So in a way, my watch is really consistent by sport mode but not between sport mode (default sport mode by the way).
Btw, 7m recorded for a flat run is normal, right ? even 20m for the same run could be considered as correct (with a non baro device).
Btw2, you can’t calculate that if for 5km those two modes have such a difference, thus for 30km it will be mutliplicated. You may just be in the GPS altitude mesurement precision (non precision).
Btw3, strange that you say it is consistent each time you change sport mode, such a difference happen : either no luck the “bad” gps days are always during snow mode, or something behind it.
Have you ever try to do the same day, the same loop twice, switching from one mode to another and see ?
If you sync with SA, and have an Android phone, you can import the raw files to QS and we may see all raw data to check GPS accurency during your activities.
I’d like to ask you about huge different between ascent and descent on my couple exercise. Today I ran on almost the same rout and I had absolutely strange data if I compare it to other similar rout.
This is that wrong route:
And here is normal one:
And here another normal with almost the same route
@tomahawk5000 was a storm approaching? Otherwise it was probably something on your sensor, like a sleeve, generating the pressure changes. I think @TELE-HO is the expert in this field
@isazi thanks for your reply.
No storm, anything different Vs other trains was that I didn’t use polar h7 to HR measure and I had watch on the inside of the wrist but I change it somewhere in the middle of training but wrong ascent was from the beginning
the alti graph in your first link looks quite jumpy compared to the others.
I have experienced weird total ascent when the skin covers the sensor venting holes. If it happens once or twice it could be easily already around 20-30m or more.
I saw a much more detailed graph in quantified-self.io. If you upload your wrong recording to QS, you will see unusual spikes and and how much they spike up and down.
would be interesting to see a screenshot of this graph
here’s a graph of one of my recent home TRX workouts.
@TELE-HO thank you very much for your help. Please find below link to this wrong exercise:
and below correct one if needed (it’s almost the same track):
Different between those tracks is only that I used Polar H7 HR monitor on correct track and I had watch on the inside of the wrist on wrong track (I saw that once I use Polar H7 then I have much lower HR bpm which is in my opiniom better)
ps below is link to different track which I did today on bike:
the first link shows a smooth alti graph and after a short time it starts becoming spiky, also your bike ride has a downspike that might not be there on the real topography.
I don’t think it is related to the HR belt. If there is a relation then it is the way you wear the watch when you measure with OHR on your wrist.
Next time you do an activity, try to observe if you cover the baro sensor.
And just in case to exclude another potential failure cause: soak your watch over night in water and carefully rinse the baro sensor then.
This helped some athletes already to get their weird measurements fixed
Thank you so much for help. I’ll put my watch into the water for all night just in case (hope it will not broke my watch)