Suunto Vertical GPS Problem?!

[GiPFELKiND]

@twekkel Workout comes --> here suuntoapp-Running-2023-05-20T05-08-21Z-track.gpx

[A Former User]

@GiPFELKiND this helps a lot. For most of the time I see a recording every 1 second, but there are some gaps… without recording timestamp or location.

Activity was about 56 minutes and moving time was 10min less, 46 min. So my guess is ‘autopause’ is enabled, which will stop recording at very low speeds (<2 km/hour) and once you move again it will pick up again. I can imagine that every (near) stop temporary the GPS fix isn’t that good (power saving?), which explains the poor track. For MTB in dense forests I would definitely recommend to disable autopause.

Does this make sense to you?

[GiPFELKiND]

@twekkel So, I’ve now looked again in the settings, and autopause is disabled. what program/software did you use to read the data so well?!

[A Former User]

@GiPFELKiND as a complete linux nerd, I used vi/bash/grep/sed/awk/gpsbabel … gpx files are just text files (and you can use any text editor), so you can lookup the timestamps and check if there are 60 for each minutes and there aren’t.

Take for example minute 05:53:xx … only 20 timestamps (and track location lat/lon) are written for that minute. I assumed that would be because of autopause. Hardware failure looks unlikely to me, but something prevents the SV to write every second like it should in ‘performance’ mode.

In low battery conditions I’ve seen tracks starting of with 1s recordings and then switching over to every 1 minutes (endurance). That is not the case here.

Not sure if very dense forest (GPS fix lost?) can cause this kind of behavior. First half of the track seems spot on, only halfway it shows this phenomena.

[Dimitrios Kanellopoulos]

@twekkel keep in mind that gps recording is not the same as polling of 1s. That means that even if the 1s frequency is used it does not mean that it will record every 1second if on second xx the quality of the signal is not acceptable.

Also keep in mind that gpx files are xml files and it’s not so well structured for data.

[A Former User]

@Dimitrios-Kanellopoulos if XML isn’t structured, what is?

Indeed a very poor GPS signal might have prevented to write accurate lat/lon. So for now I “blame it on the forest”.

[GiPFELKiND]

@twekkel

[GiPFELKiND]

@twekkel look there the beginning with good tracking is in the woods… The rest when terrible tracking open field without trees

[GiPFELKiND]

@GiPFELKiND

[GiPFELKiND]

@GiPFELKiND any questions!?

[A Former User]

@GiPFELKiND if this was a one time bad track, I wouldn’t worry about it. It can happen, although this particular example is pretty bad with so much open field.

Even with the best GPS watch out there, SV, it isn’t always perfect. If this issue persists with other activities also, I would go or a warranty claim. Upcoming firmware update (June?) might also improve the situation.

[freeheeler]

@GiPFELKiND
it would indeed be interesting to see if you can replicate this with another activity in case you have some spare time to do something similar now/soon.
I haven’t seen this kind of tracks in any watch.

[GiPFELKiND]

@twekkel

Also I analyse my track with app. And see what mystery I see… When this lines come my speed is 30 km/h NEVER NEVER… is my hand shaking when i run the problem?!

[freeheeler]

@GiPFELKiND
this for sure is not arm movement.
again: record another activity and if it is the same again -> logs.
maybe it is a one time issue and never happens again. we will only know with more samples. until then all we can do is guessing

[GiPFELKiND]

@freeheeler good morning community, today morning next run! And nothing so bad like the first run! Looks so good! Good start to you all in this new week

[zhang965]

Suunto watch generally has some spindle during the first GPS tracker, it’s kinda normal.

[ChrisA]

@GiPFELKiND that looks a lot better . Have a nice - good GPS tracking - week too!

[Dimitrios Kanellopoulos]

@twekkel exactly for that reason is bad. Sensor data are not structured on the top level entity (tree) such as the xml. They are streams, or lets say messages.

For example the limitation that XML has is that the parent entity is a trackpoint and inside that you get the sensor data. So that essentially means that if you dont have a trackpoint then you cannot have sensor data. For example inside a tunnel all points are lost

• trckpoint
  • HR
  • Speed

While on fit files for example we have messages that can contain any info and are just a timestamped payload.