Suunto Support Australia
-
@Brad_Olwin Hi Brad,
It’s the Suunto Spartan Sports Wrist HR and my problem relates to the cumulative elevation problem that others have mentioned on here in a couple of different threads.
I predominantly use the watch for trail running and a cumulative elevation is important to me.
My question to suunto (this time) related to the ascent value I am given for a run. So for example as part of my running group I completed a 15k run. The ascent value in Movescount was 42m. However, if I tally the per lap ascent value I get 93m. The average ascent for the group was about 105m (different watches and some had barometers). I wanted to know where the 42m value comes from and how come my value isn’t 93m. I used this run specifically as I can see the value from about 10 other runners doing the same course but this happens for all my runs.
My running group uses Strava and (as discussed a lot in this forum) when I correct elevation with Strava it give a really high value, for this run I get 127m.
I am frustrated as this is my first Suunto and I was excited.
-
@MareeB If your watch does not have a barometer as I assume, the values will be imprecise and dependent on how good your GPS signals are. In the non-baro models a 7m change is required to trigger an altitude change. Unfortunately, this is the status for these watches, I have a Suunto 5 and the elevation data can be very good or poor depending on conditions. The correction in Strava is not dependent on the watch and if incorrect, it is Strava’s algorithms that are at fault. I wish I could be more helpful but without the barometer the elevation data will simply not be as precise. If you need accurate elevation data, either get an S7, S9baro or the Spartan Wrist HR Baro watch as these will provide much better elevation data.
-
@Brad_Olwin Thanks for trying Brad.
I wasn’t too worried about the Strava stuff… it just makes me look more awesome than I am! Ha ha!
With the Suunto 5 is there a per lap ascent value? Does it add up to the overall ascent?
I would be happy if the software enabled that to be my ascent value. I realise it would be more precise with the baro but my budget is not there! Within 10m would make me happy.
Thanks again. -
@MareeB I think that you will continue having issues with a non baro watch. With the S5 probably less due at its good gps reception. For what you say, 15 km with around 100 m of ascent it is quite flatish in my opinion, so it is more difficult for the watch to trigger the 7m threshold, probably with runs with more ascent you will have closer values to the others.
-
Because this is not about the Suunto App, but about a watch, I’ll move this post to the appropriate section.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@cosmecosta My problem is relating to the per lap value. This summed is what I want for my overall ascent. I used this run specifically as I have good comparison with other runners for it. This issue is happening on all my runs, even the steeper ones!
-
@isazi Thanks Isazi. It wasn’t meant to go this way… I was genuinely querying how people had found Suunto Support Australia as I’d already read through all the comments relating to my watch problem.
-
@MareeB don’t worry mate
It’s probably better here than in the app section anyway. -
@MareeB On my run today S5 on left and S7 on right. S5 was 462 feet elevation gain and S7 was 610 feet so there was ~50m difference on a 200m ascent. This is typical of the non Barometer watches I am afraid.
Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing
-
@Brad_Olwin Thanks Brad.
-
Ok so after much persistence I have an answer from the help line.
The per lap altitude is calculated using maps of the area where you are running but the overall altitude value is based solely on the data collected from the watch ie GPS alone (with the 7m buffer).
This is interesting and helpful.
I should add that there are many things I like about the watch and I feel like a big complainer when that is not the case! Thank you for everyones feedback… especially @Brad_Olwin for a two watch run!
