Watch unusable in wind
-
@Inge-Nallsson Let me put it this way, I would rather have these 100m extra in Garmin than the current +1000m in Suunto.
Suunto measurements R and Strava data L:
-
@maszop
thats really crazy -
@GiPFELKiND Usually there are a few hundred meters extra, sometimes over 1000, but there is also such madness as in that example. I am talking about approaches in very strong winds, of course.
In stable weather everything works perfectly.
-
@maszop No you wouldnāt, because with Suunto you will know that is not correct but with Garmin you will always have doubtsā¦jokes aside, Iām not saying that you do not have issues.
Can you share the SA graph where the spikes should apear? Have you tried to send logs to see if someone at Suunto can help with it to adjust the algorithm?
-
@cosme-costa The Suunto graph:
https://i.postimg.cc/qMhcJDDr/Screenshot-20250128-114024.png -
I wrote about the same problem several months ago, on a strong windy day the total altitude reported by the Suunto App was quite overestimated:
the problem can be solved by exporting the GPX data from the SA and then import them into a smarter software that smooth out the data (for example I use Oruxmap, see details in the thread)
-
@maszop said in Watch unusable in wind:
I would rather have these 100m extra in Garmin than the current +1000m in Suunto
The +100 metres were on top of the normal Asc/Desc of ca 160 metres, so not an insignificant error.
Look, no one denies that you are having problems. But I strongly object to a blanket whitewashing of any company when trying to prove a point, and most certainly when it comes to such a finicky area as altitude.
Case in point (and another n=1 example): My FR955, bought in september 2023, is at firmware 19.18 which is two versions (soon to be three, ie 9 months) behind current stable. This because amongst the many bugs introduced by Garmin lately is one which randomly gives you Zero (0, null, zilch) altitude gain/loss during the whole activity. Flat as a pancake runsā¦ But even with this old FW version I lately - before switching to the Race S full time - experienced the Garmin āabout-to-failā sensor problem. Short, 6-7 km total, out and back runs on the most level path in my area had eg āTotal Ascent 79 m. Total Descent 66 mā whereas the true figures should read an even 20 metres.
But you wonāt find me wailing about that anywhere. 'Tis the way of penny-pinching companies, and Iāve already voted with my feet (for this training cycle).
-
@Inge-Nallsson I use Suunto, not Garmin, and I donāt care that much what Garmin does. Especially on the Suunto forum. I only see data from Garmin users and they donāt have such crazy measurements as in the case of Suunto.
The complete collapse of Suunto is fact that current the most advanced Suunto watches with an advanced barometric altimeter and many years on the market can provide much worse data than the simplest cheap phone with only GPS.
For Suunto developers, this should be embarrassing.I think that further discussion is pointless because we have been writing the same thing for years and years go by and nothing happens.
-
@maszop said in Watch unusable in wind:
I use Suunto, not Garmin, and I donāt care that much what Garmin does. Especially on the Suunto forum.
@maszop said in Watch unusable in wind:
Let me put it this way, I would rather have these 100m extra in Garmin than the current +1000m in Suunto.
@maszop said in Watch unusable in wind:
I know how the barometric altimeter works and what effect the wind and other weather conditions can have, but since all my friends with Garmin watches have more or less correct data, it means that it can be done
Iām confused.
That said, I guess weāve already reached garbage time here for a while.
No one here has ever tried to āobscureā criticism, but thereās no constructive discussion if everything other people say is just ābullshitā or āfakeā.@maszop, no one here is trying to sell anything to you, this is a Community Forum.
If youāre not okay with your Suunto watch, you can return it, sell it, or switch brand.
I mean, just find the one you enjoy and enjoy it. -
@maszop said in Watch unusable in wind:
@cosme-costa The Suunto graph:
https://i.postimg.cc/qMhcJDDr/Screenshot-20250128-114024.pngThe spikes are clearly the issue. I do believe you and it is apparent butā¦. I rarely, rarely see this with any of my watches. Can you contact me by PM? I am going to going to ask the test group. I think this issue is not common, at least for me. I may ask to collect some files.
-
@Brad_Olwin said in Watch unusable in wind:
The spikes are clearly the issue.
the algorithm that calculates all the related quantities (altitude gain, loss, etc ā¦) should include a running average to smooth out the altitude data, to eliminate the spikes if any.
Suunto Vector . Vector HR . Core . Race & Race S
-
@Stefano-M64 said in Watch unusable in wind:
@Brad_Olwin said in Watch unusable in wind:
The spikes are clearly the issue.
the algorithm that calculates all the related quantities (altitude gain, loss, etc ā¦) should include a running average to smooth out the altitude data, to eliminate the spikes if any.
if you use the search feature here, youāll find that the folks on the forum actually helped with the algo ended up in use for the S9B when it first came out. There is some pretty open dialogue about what the underlying metric actually looks like
-
@Stefano-M64 interestingly enough, the more you smooth and correct, the more you end up losing real-time metrics like pace or vertical speed
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@maszop said in Watch unusable in wind:
I think that further discussion is pointless because we have been writing the same thing for years and years go by and nothing happens.
Actually, just at the end of last year me and others provided Suunto with activity data for the same use case you have, bad weather (and wind in particular) affecting the ascent/descent calculation.
I believe it has not been prioritized because it happens to only some, and not always, and there is always something more urgent to fix. -
@isazi said in Watch unusable in wind:
@Stefano-M64 interestingly enough, the more you smooth and correct, the more you end up losing real-time metrics like pace or vertical speed
a good algorithm should be able to process raw data by eliminating noise and spurious values. Of course, that depends also on the kind of activity. For āslowā activities as walking or hiking data smoothing over 1 minute should give good results. It happens relatively often that SA gives altitude related metrics that are overestimated, only by importing the gpx data into an app (I use OruxMaps) that allow to the filter the data I get values that agree with the expected ones.
-
@isazi Improving this current algorithm is essential - current measurements are often completely useless.
Yesterdayās example:
Suunto Vertical measurements -1502m:
Strava data - 1083m:
Garmin Fenix 7 - 1157m:
Suunto data after smoothing - 1198m:
It seems that the measurements from Garmin 7 look the best.
Suunto measurements - better not to even comment on that. -
Yesterday Suunto Vertical also shone:
Suunto Vertical measurements: 3247m
Strava data: 1690m
Elevation profile in Suunto App:
Total disgrace of Suunto.
-
@maszop Could be a problem with your baro sensor?
-
@sorinus This is the third, all brand new, watch that behaves identically. 9PP and two Verticals.
-
@Brad_Olwin the other person who wrote about the pulsing is 100% correct about the issue Iām having. If you look at the elevation graph without zooming it looks kind of normal, even if you have several hundred meters extra. And the top elevation is basically correct. But what happens is you get these tiny up and downs, according to the watch, that can add a ton of elevation gain and descent as it happens so quickly
