Suunto 9 Highly inaccurate speed readings

[surfboomerang]

Little status update:
Suunto support requested to return the watch for investigation.

Lets see if they can find something…

[surfboomerang]

Watch is replaced by Suunto support. Just got my new one.
My first run looks promising. No real spikes like I had before. I’ll test high speed sports soon to see if my issue is really resolved.

[surfboomerang]

@Dimitrios-Kanellopoulos The new version of the app looks great btw!!

Is it possible that the suunto 9 doesn’t record all the fields you have in the app? (like battery level, GPS satellite status etc…).
Because I selected those settings in my profile settings, but the data was not available in the graph.

[Dimitrios Kanellopoulos]

@surfboomerang those fields are recroding just not exported. You need the SML files and I still dont have support for those. However I will add as it’s at least the last feature I ll push for now.

Regarding my data that have those fields that is because we use another tool internal to extract those data

[surfboomerang]

Bringing an old topic back to life after firmware update 2.8.28…

@Dimitrios-Kanellopoulos and @dirty-hippie
Unfortunately the speed spikes are still not correctly filtered for my case. I did two testruns today. One with GPS only and the other one with GPS+GALILEO.

I was driving a steady 57km/h during this run

Below are the results:

GPS Only

GPS+GALILEO

[Dimitrios Kanellopoulos]

@surfboomerang Ok. Thanks for this.

I will have to escalate this. I would like to know how much this can happen in other modes.

Btw what sport mode do you use? PErhaps there is different bahaviour per sport mode?

[surfboomerang]

@Dimitrios-Kanellopoulos This time I used the sports mode “Other”, but I have seen this behaviour also with “Windsurfing”.

I checked a move that I did yesterday. I selected the profile “Running” and had GALILEO on.

So it looks like it happens on all sport modes, but the spikes (and dips) are greater for sports with higher speeds

[Dimitrios Kanellopoulos]

@surfboomerang what files are you reading ?

[surfboomerang]

@Dimitrios-Kanellopoulos The files above are GPX exports from Runalyze.

[Dimitrios Kanellopoulos]

@surfboomerang I would prefer to look at the fit file.

Do you have some SA link for me of the files with these issues ?

[surfboomerang]

@Dimitrios-Kanellopoulos I sent you the links in a pm

[surfboomerang]

<Frustration mode>

Can someone tell me if this issue is resolved in the upcoming firmware update?
I did a windsurf session today on a rainy day and I had GPS+Galileo on. The picture below shows a segment of a track that is almost 100 km like this.
As you can see it is a horrible recording of speed!!!

</Frustration mode>

[freeheeler]

@surfboomerang
I just compared my recordings from a3p to s9b within SA… s9b indeed gives a spikier graph… strange!

a3p: https://app.suunto.com/move/skiingone/5d836edd58e211b5ae86859e

s9b:
https://app.suunto.com/move/skiingone/5d921b3c58e2111193c1ec1c

[freeheeler]

and just noticed that the exported link displays my highest point of 948m as ascent…

[surfboomerang]

@TELE-HO I haven’t seen those spikes with my old a3p either. Only with my s9 baro.

[Dimitrios Kanellopoulos]

@surfboomerang should be. Wait for end Oct

[surfboomerang]

@Dimitrios-Kanellopoulos That would be great! Thanks!

[freeheeler]

@solid_dd
it’s like a good wine, it takes time but then it’s great

[fejker]

@TELE-HO said in Suunto 9 Highly inaccurate speed readings:

and just noticed that the exported link displays my highest point of 948m as ascent…

It has been like this since I can remember and I have reported this many times and nothing has happened since at least January 2019 … and I bet you all my tech gear that it has been like this longer than that. Here we are nine months later and still nothing.

[freeheeler]

@fejker
I’m glad it’s on the export file only that I actually don’t need… it’s correct for Strava…
the pain is: when @Dimitrios-Kanellopoulos wants to see our files and asks for the shared link… he does not see what we see…
I noticed the wrong total ascent but more mistakes could be hidden anywhere…