-
-
-
Agreed not 3 %
-
I bought my girlfriend a s5 and after a fews runs i am a bit confused because the ascent recorded by the watch is about 50% of the real ascent. I use the ssu. I know s5 has no baro but at least it should record the GPS ascent which is about the same i her from the ssu. Is this a known issue?
-
Have you tried a full vertical track, without d- ?
Going from 300m to 800m should results 500d+, in S5 and also in SSU.In tracks where there are many up and down you will not have the same results because GPS device store d+ only each 7m gained, BARO device each 3m.
btw, 50% less is too much…
-
@whl_89 Same here with SSSW (no baro). Are ascend step sort? Usually in my 10-15k run with +400m always have less than +200m
Suunto: Race, S9Peak, Spartan Sport Wrist
Garmin: FR745, Edge 530
SA topics:- Guides - https://forum.suunto.com/tags/guides
-
@Saketo-Nemo i just made two runs with ups and downs but both around 50% of actual ascent. I mean i am aware of the non existing baro in s5 but this huge differences are really bad for a 300€ device
-
@suzzlo mixed ascents but shouldnt there bei an algorithm to overcome those recording gaps within those 7m?
-
just my curiosity: can you share the link of the two activity ? (also in pvt if you want)
-
@Saketo-Nemo I will upload them later
-
-
Out of curiosity, I wanted to see the altitude diference, so I imported both to QS:
S5:
SSU:
Both have similar graph shape and are in similar altitude ranges, but SSU seems a bit jagged compared to the S5 which looks smooth. Not sure which one is correct. But I’m guessing that SSU has more altitude difference because all those small spikes, also bigger drops in altitude on multiple places.
-
@Dušan-Ković If i plan this route in komoot or Suunto App altitude differences of ssu is quite correct and s5 ist about 50%. SSU works fine i think
-
@whl_89 One of my friends wants to buy S5, so I’m searching for possible problems with watch. Maybe this is one of the problems with S5. Have you tried GPS, GPS+GLONASS or GPS + GALILEO on the same route with S5?
SR
SA latest beta
Polar Verity Sense
Pixel 6 -
@whl_89 same here
-
@Dušan-Ković i would still recommend it great watch
-
@Dušan-Ković YES, there is a little problem
Run 16.6. with S5 GPS+Galileo. After 0:30 it’s very faulty:
Same route 10.6. with S3F (connected GPS):
Same days and same routs exports to Strava:
16.6.
10.6.
Start level 40…42m, highest point 50…52m would be correct!
-
@Dušan-Ković said in Suunto 5:
@whl_89 One of my friends wants to buy S5, so I’m searching for possible problems with watch. Maybe this is one of the problems with S5. Have you tried GPS, GPS+GLONASS or GPS + GALILEO on the same route with S5?
My 2 cents … if he’s some kind of mountaineer , tell him to go for a baro watch otherwise GPS only is ok.
-
-
I bought my girlfriend a s5 and after a fews runs i am a bit confused because the ascent recorded by the watch is about 50% of the real ascent. I use the ssu. I know s5 has no baro but at least it should record the GPS ascent which is about the same i her from the ssu. Is this a known issue?
I have done a lot of runs with both the S5 and S9 together, most of the time on the same arm. The S5 is always short in altitude, I mentioned this much earlier in the thread. If you care a lot about real time vertical it is not the right watch. However, I rarely see 50%, most of the time my differences are below 20%. The worst scenario for the S5 are lots of small hills as it does not record a change unless 7m. On big climbs it is much better. If you like I can post some of my SkiMo runs or runs with at least 500m altitude change. I do think that GSP+Galileo gives better altitude readings on the S5 but I have not thoroughly analyzed this yet. Third party sites (Strava, etc) will correct the altitude so in the end it isn’t that big a deal in my opinion.
I still think the S5 is a great watch and most of the time I use it for my weekday runs and just let the 3rd party apps correct the altitude. The SSU and S5 should be similar for ascent. Make sure AGPS is current and I would use GPS+Galileo.
