End of GPS trace missing

[zhang965]

@Cédric-Dodrimont said in End of GPS trace missing:

@zhang965 Here it seems we have the same issue on S9B and Vertical.

Peter-Tönz My Eiger teammate had a S9B, and the recording stopped just before Grosse Scheideg.

But it stopped earlier on the Vertical than the S9B, next time I will use my S9B

Yep, guess what, the person in my screenshot tested S9 as well.

Did you try with your ambit2?

[Cédric Dodrimont]

@zhang965 I had exactly the same issue in 2016 with my ambit during UTMB TDS.

I can understand there’s a limit for recording activities, but I would like to have an estimation on the activity duration we can record, or at least a warning telling me it’s time to stop the activity, sync the watch and start a new one.

[Cédric Dodrimont]

@Łukasz-Szmigiel The exported fit file is 3,8MB

[stromdiddily]

@Cédric-Dodrimont if the watches (all three of them) are showing correct stats (distance, time, elevation, etc) seems more like an issue with the app doesn’t it?

[Cédric Dodrimont]

@stromdiddily Maybe yes.
Or the watches stopped recording GPS data at some point, but no info on the maximum time we can record data with the watch.

[isazi]

@Cédric-Dodrimont rule of thumb is at least the battery duration, so a S9B in performance mode could have problem recording an 80 hours activity, but the Vertical should be able to do that.

[A Former User]

@Cédric-Dodrimont said in End of GPS trace missing:

@zhang965 I had exactly the same issue in 2016 with my ambit during UTMB TDS.

I can understand there’s a limit for recording activities, but I would like to have an estimation on the activity duration we can record, or at least a warning telling me it’s time to stop the activity, sync the watch and start a new one.

Sorry to hijack, but I don’t understand how can that be done, from this table the log capacity of the ambit 3 is always bigger than battery life
watchuseek:

Or it when it doesn’t have the capacity to delete old activities when the log of current one is getting bigger?

[Mff73]

@André-Faria
maybe with charging during activity

[Cédric Dodrimont]

@isazi Thanks for your feedback, anything I can do to analyze what happened ?
The Vertical was configured in performance mode with OHR turned on. Recording stopped after 50 hours.

[Mff73]

@Cédric-Dodrimont
Did you export the fit file for this activity and checked it (for example with https://www.fitfileviewer.com/ ) and see if, by any chance, exported activity contains full track points (meaning data are well stored somewhere at Suunto, but not fully displayed in app) ?

If you have an Android phone, and will little geek skills ( instructions here ) you can try to find the raw data file for this activity, and be able also to check if, data send by watch to app, at that time, was complete.

[Peter Tönz]

@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!

[Mff73]

@Peter-Tönz
Not nice

[Peter Tönz]

@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)

[freeheeler]

@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 Ultra

by the way: congrats to all you Eiger Ultra runners! awesome effort! I admire your running capabilities!!

[Łukasz Szmigiel]

@freeheeler all GNSS modes in 9PP and Vertical have a 1s fix except for tour mode, which won’t be useful for a run.

[Cédric Dodrimont]

@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.

[BrunoH]

@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.

[Likarnik]

@BrunoH this is a must, especially because this is their mainly selling point (and tbh only thing that stands out).

[dombo]

@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.

[isazi]

People at Suunto are aware of this discussion, and there is an ongoing investigation.