End of GPS trace missing
-
@Mff73 I checked the file samples.json from the suunto app. And in this file, the last sample has the timestamp of the ending track. Also the distance for this sample is valid.
There is also no problem with the app. It seems the watch has stoppt recording the track!
Except the summary values, showed on the display, are recorded until the end.
I would expect a warning from a (not cheap) watch, when the memory goes out! -
@Peter-Tönz
Not nice
-
@Mff73 I use always the best GPS Quality (no data are better than unusable data
) and therefore, every one second a trackpoint is stored.
Is it possible to use the best possible GPS quality but onls every 10 seconds or so?
Thats enough for such long adventures and extends the possible ‘track-time’ by the factor 10!
(I mean that option was available for the Ambit 3 Baro) -
@Peter-Tönz
I recall GPS was the only system available of all GNSS systems with Ambit and battery life “best, good, ok” was controlled by sample rate 1sec, 5sec or 60sec.
I have recently tried ultra mode and was very surprised about precision. honestly never tried it before. maybe give this a try? … don’t wait until the next Eiger Ultraby the way: congrats to all you Eiger Ultra runners! awesome effort! I admire your running capabilities!!
living sideways
-
@freeheeler all GNSS modes in 9PP and Vertical have a 1s fix except for tour mode, which won’t be useful for a run.
-
@freeheeler On Ambit, there were settings to configure recording rate and recording interval on movescount
It would be good if Suunto can provide us with a table with an estimation of max recording time depending on the different battery mode.By the way, I don’t have the complete GPS trace on suuntoapp, but during the Eiger race, the watch was perfect. Data were accurate, the navigation was perfect, battery was awesome.
-
@Cédric-Dodrimont said in End of GPS trace missing:
It would be good if Suunto can provide us with a table with an estimation of max recording time depending on the different battery mode.
Exactly. It is awesome to have a battery life this long, but there should be guidelines regarding other limitations. Or alternatively Suunto to fix the implementation so that ultra long activities can be handled in the watch and in SA.
-
@BrunoH this is a must, especially because this is their mainly selling point (and tbh only thing that stands out).
-
@zhang965 I see you receive some downvotes. I don’t want to enter any personal here, even I had similar experience regarding crashing of my new vertical. As I’m coming from IT/technical environment I know that if something didn’t happened to me it does not mean it can not happened to somebody else. I learned, that even developers and testers did perfect job, it is still possible that some user will find workflow when it fails or simply does not work. Probably it would be enough just to update attitude here. …and fix bugs as soon as possible.
-
People at Suunto are aware of this discussion, and there is an ongoing investigation.
-
@dombo said in End of GPS trace missing:
@zhang965 I see you receive some downvotes. I don’t want to enter any personal here, even I had similar experience regarding crashing of my new vertical. As I’m coming from IT/technical environment I know that if something didn’t happened to me it does not mean it can not happened to somebody else. I learned, that even developers and testers did perfect job, it is still possible that some user will find workflow when it fails or simply does not work. Probably it would be enough just to update attitude here. …and fix bugs as soon as possible.
Dear Dombo,
It’s totally fine to get downvotes, we have many many elephants in the room, and… welcome to suunto community forum!
-
P Peter Tönz referenced this topic on
-
@Cédric-Dodrimont ok. I understand why i had this kind of problem on a 100 miles (more than 40h). Now it seens resolved with last update.
-
@Antoine I heard about issues to sync long runs… A collegue of mine runs the Swisspeaks 360 last september and recorded the full 360km and 111 hours in one track.
After that he couln’t sync it with the app!I plan to run for almost two weeks next summer. I will test some long tracks before the big event and will see wether I can track it in one piece (or split it up like with the Sunnto 9 Baro)
-
@Peter-Tönz i have also “big event” next summer. Keep us informed after long run if the problem is solved. Thanks !
-
Solved with last update, some people already used it to run a 100 miles.
-
@isazi I’ve repeatedly experienced something similar on the watch itself (with the latest firmware): For instance, today I did a 15k / 7h hours loop (non-stop tracking including breaks, i.e., without auto-pause) and initially I could see my previous track on the map just fine. But when returning to the origin, the initial part of the track was missing on the watch. This means that it would have been impossible to navigate back to the origin, which really is a total no-go to me (what can I use the watch for in an emergency if it cannot even guide me back?). Has anyone experienced this, too (and / or knows solutions to this issue)?
-
@Peter-Tönz @Antoine As @isazi stated this issue is fixed.
-
@wesk2a this is another issue from the one described here (i.e. the watch was not recording the full track). In your case the map does not show the track from the beginning of the activity, that is also very annoying but different. How long ago did it happen to you? Did you send logs?
-
@isazi Hi isazi, yes it’s somewhat different from the issue described above, my issue only affects the display of the track on the watch. Shall I open a new thread for this?
Note that the full track is actually recorded and shown correctly in the app after sync. But in map view on the watch the initial part of the track is not displayed after a while. This happened to me just this weekend and multiple times before. I haven’t sent any logs yet (how / where would I do this?). Again, nothing is missing from the track in the app, so I guess it’s just a displaying bug / issue.
-
@wesk2a I know about the problem you have, I believe it is also fixed in testing firmware already (the one that will be released next) but just to be safe, can you open a new thread and if it happens again to you send me a private message as soon as possible after the event? So I can help you send logs to Suunto and open a bug with them, to have this checked.
