Suunto 9 Baro Endurance/Ultra Battery mode issues

[David Zunel]

Hi @brad_olwin and thanks for your answer,

That I can understand and I didn’t expect the GPS to work differently however what surprises me is that in Endurance / Ultra mode FusedTrack is able to interpolate positions and gives you a quite precise navigator reading, which is great because you don’t miss a turn. Now, assuming that the watch is able to give you this good approximate reading, it would be really easy to fill the data gap from the GPS (1/2 minutes) and give you a decent approximation in auto lapping and therefore in the total distance.

I’ve been looking for detailed technical info on how FusedTrack works but I didn’t get much. Do you (or anyone) has more detail about it?

[Dimitrios Kanellopoulos]

@david-zunel keep in mind, if you use the navigation screen the mode will switch to GPS best.
Then after 5mins of exiting that screen it will switch back to endurance etc.

[David Zunel]

Hi @dimitrios-kanellopoulos and thanks for your answer,

Now I don’t get it, because in these tests I run almost 100% of the time using the navigation screen, so It means I’m using GPS best (I don’t perceive a worse performance in the battery though, I would have run out of battery according to the watch pre-run estimation) so autolap should be accurate. Am I missing something here?

[Łukasz Szmigiel]

@dimitrios-kanellopoulos will S9 turn off navigation screen automatically after 5 minutes when using 1 min / 2 min battery modes to conserve the battery or does the user need to do it manually?

[isazi]

@łukasz-szmigiel you need to leave the screen.

[Łukasz Szmigiel]

@isazi so in principle, you can set the watch to Ultra but if you’re going to stick to navigation screen 100% of time, it’ll be on Performance 100% of time, correct?

[Dimitrios Kanellopoulos]

@łukasz-szmigiel correct

[Dimitrios Kanellopoulos]

@david-zunel now I dont as well… Do you have a link for me ?

[Fenr1r]

@łukasz-szmigiel

you can set the watch to Ultra but if you’re going to stick to navigation screen 100% of time, it’ll be on Performance 100% of time, correct?

And if you have ETE/ETA and/or Distance to WP/POI/End data fields enabled, regardless of whether you have a route (or POI[?]) loaded and which screen you’re on.

From the man himself.

[Dimitrios Kanellopoulos]

@fenr1r he didn’t say that, I I think the ETA fields will make it to best only if a route is loaded

[Fenr1r]

@dimitrios-kanellopoulos Did you follow those links?

[Dimitrios Kanellopoulos]

@fenr1r yes

[Fenr1r]

@dimitrios-kanellopoulos My apologies (& to @Brad_Olwin), he didn’t say “regardless” but he didn’t say “only”, either. And isn’t the result the same? BEST will be applied without a route loaded? That was the experience that started the thread, no?

Alternatively, is it just ETA? Or ETE, Distance to (WP/POI/End) and ETA?

[David Zunel]

Dear @dimitrios-kanellopoulos,

here you can access the latest activity where I experimented this behaviour.
https://www.suunto.com/move/davidzuelballester/608484c3a8ea142553edb692

It’s an almost flat, circular route, along both banks of Saar river. From the link you can see that the registered distance was 18.47 Kms while the actual one is 17.15 Kms. Now, looking at the graphs I’m realising the the total distance reported there is the real one (just moving the cursor till the end of the graph), 17.15 Kms. Moreover looking at the splits (1 Km), it looks like they are somehow modified. Duration and pace don’t match, pace looks right to me.

And now, in the attached picture, you see the recording in the watch, when you can see that readings where probably taken only at the 1 min sample rate (endurance mode).

FYI. I had the route loaded and I was following the route (not necessarily looking at it all the time)

[Dimitrios Kanellopoulos]

@david-zunel only the last part is with wrong data right (regarding pace etc) ?

In most of the run from what I see the endurance mode was used

[Brad_Olwin]

@david-zunel The other issue is a 1.5 h run is quite short to get an idea of battery life for the extended battery modes. A 5-6h run would provide a much better idea based on consumption.

[Łukasz Szmigiel]

@dimitrios-kanellopoulos so, let’s say you’re running 100+ km ultra race and have S9 set on Endurance or Ultra and have route loaded and there’s also ETA field on base screen. Will the FusedTrack engage correctly and stay engaged or will watch default to Performance?

[Brad_Olwin]

@łukasz-szmigiel I believe will default to Performance, I avoid any ETE/ETA fields for waypoints or for finish on my Custom Ultra Sport modes. The Altitude Route Profile will not cause the GPS switch, only the route profile page. I typically only use the Altitude Profile. My comments are vaiid for when a route is loaded. Otherwise, it makes no sense to have ETE or ETA fields on the screens.

[David Zunel]

Hi @dimitrios-kanellopoulos,

in the screenshot (watch reading) you laps 2 to 6 are wrong then 9,10,11, 17 and 18 for sure all of them are wrong, so I assume all readings have some kind of error, and that GPS sampling interval was at least 1min.

If you look at the move (link), 1 km splits pace seems to be ok though ( I don’t understand the difference in duration neither)

[David Zunel]

Hi @brad_olwin. Yes probably you are right, but I remember this run quite well. When I started the battery was showing 6% and the time at performance mode said 1h, I switched to endurance resulting in 2h. The battery estimation might not have been accurate but the watch reading indicated clearly GPS accuracy GOOD. I presumed that Fusedtrack did its part so I could follow the navigation but according to @Dimitrios-Kanellopoulos if I was using the navigation screen then GPS was set at BEST.

So,unless there is something I don’t understand or I am missing, I see 2 options:

1/ GPS was actually back at BEST because I selected the navigation screen. Then my good navigation reading was provided by the GPS sampling at 1 second, BUT, autolap failed and total distance did so. Software problem here. (good news : battery stood)

2/ GPS was stuck at GOOD (software problem here?) and Fusedtrack did its job to provide with the good navigation reading. Autolap degraded, and so did the total distance. This could be easily fixed in real-time or at least at the end of the race (the shared link seems to have done it)