Suunto 9 Baro Endurance/Ultra Battery mode issues

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)

Łukasz Szmigiel · S9PP 2.37.48

@brad_olwin so if I get it right:

Pace gets updated once per minute or per two minutes (endurance / ultra) but eta is forcing performance mode? Why it can’t update according to 1 - 2 min refresh periods?

Brad_Olwin

@david-zunel As I stated before, I think your run is too short with too many unknowns to make conclusions regarding software issues. I will be doing some longer runs 5-6h where I can wear two S9b watches with one running Endurance and one running Performance for an adequate test. I typically do not enable auto laps but will enable for this test. I will load identical routes and see what happens. I will observe the Nav screen a few times during the run. It will be a couple of weeks for this as I am still doing SkiMo for most of my long outings as opposed to running.

David Zunel

Thanks @brad_olwin, it looks like a very good test bed!

Fenr1r

@brad_olwin said in Suunto 9 Baro Endurance/Ultra Battery mode issues:

I will be doing some longer runs 5-6h where I can wear two S9b watches with one running Endurance and one running Performance for an adequate test

I know a certain @surfboomerang is eagerly anticipating your dual S9b testing season …

surfboomerang

@fenr1r Indeed, I’m certainly interested in the test result. Funny how such a feature can cause so much confusion about the way it works vs how it should work.

As for now I have the following facts. Feel free to add or correct the list:

ultra / endurance mode can be selected for every sport mode
fusedtrack is only available for running profiles
if you navigate a route, GPS is set to performance while looking at the navigation screen. If you move away from the screen, it falls back to ultra or endurance after a while (5 min?)
if you don’t navigate a route, but have fields like ETA, ETE or distance to … fields configured in one of the screens the watch will never fall into ultra / endurance mode, but stays in performance mode
If the watch is set to ultra / endurance but operating in performance mode the sampling rate for auto laps and pace is still 1 or 2 min if I understood @David-Zunel correctly.

David Zunel

@surfboomerang

David Zunel

As I am still not able to understand the way S9b works with the laps data in different modes I made a series of tests (trail running) over the same route. Here you have:

MODE PERFORMANCE - NAVIGATOR SCREEN OFF §
https://www.suunto.com/en-be/move/davidzuelballester/60bb0e0f9859195d40b93320

MODE ENDURANCE - NAVIGATOR SCREEN ON (E-ON)
https://www.suunto.com/move/davidzuelballester/60cd9fb2852b3c080621258a

MODE ENDURANCE - NAVIGATOR SCREEN OFF (E-OFF)
https://www.suunto.com/en-be/move/davidzuelballester/6097121145cefd139a2aaa00

Looking at the maps, neither reading E-ON or E-OFF matches reading P. Whilst E-ON guidance was completely correct, the route recorded is significantly less accurate than reading P.

Looking at the total distances:

The actual distance is 13.9 kms
P recorded distance is 13.87 kms, last split ends at 13.9 Km, so is coherent.
E-ON recorded distance is 14.8 kms, last split ends at 13.3 kms (why is that?)
E-OFF recorded distance is 14.55 kms, last split ends at 14.4 kms (why is that?)

Moreover I don’t get the actual difference between split duration and split min/km. In P these readings are different although though, but in E-ON and E-OFF, these readings are far one to the other.