-
and just noticed that the exported link displays my highest point of 948m as ascent…
living sideways
-
@TELE-HO I haven’t seen those spikes with my old a3p either. Only with my s9 baro.
-
@surfboomerang should be. Wait for end Oct
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos That would be great! Thanks!
-
@solid_dd
it’s like a good wine, it takes time but then it’s great
-
@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.
-
@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… -
@TELE-HO I dont look at the link data. As @fejker mentioned this is pretty much an old issue.
With the link you provide I open the activity with the Suunto app
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
@Dimitrios-Kanellopoulos
and within SA it is correct I assume
-
@TELE-HO yes correct
-
@Dimitrios-Kanellopoulos Just a small update/test after the latest firmware update:
I exported the FIT files of two moves from Runalyze and used GPXSee to analyze the fit files. The tool has 2 ways to calculate the speed: “By distance/time” or “Recorded by device”
Unfortunately the speed with GPS only didn’t improved very much after the latest firmware update if I calculate the speed by distance/time:
If I calculate the speed by “Recorded by device” it started to look a bit better:
The move with GPS+GLONASS however looks much cleaner if the speed is recorded by distance/time. Especially the second half
Is this because of a better/stronger signal if I combine GPS+GLONASS?
So it looks like the firmware update solved the speed wobble a little bit, but not quite like the Ambit 3 Peak. The speed spikes are also visible on the watch screen during the move, so it isn’t only the FIT file.
