Software update 2.13.18 for S series (S3,S5,S9)

[Łukasz Szmigiel]

@Dimitrios-Kanellopoulos good to know. I’ll keep an eye on it though. I have a feeling that my pace is related to GNSS quality (on flat runs of course). Typically it’s between 15 and 30 seconds slower when signal is bad compared to good days.

But it may as well be my feeling and confirmation bias. Or my form is linked to GNSS quality on that particular day

Anyway, I had an amazing track accuracy yesterday with Galileo and had a nearly constant pace that didn’t drift as much as usual (typically when entering park or other area with dense vegetation it drops significantly) which got me thinking how much is pace related to GNSS signal quality.

[Fenr1r]

@Łukasz-Szmigiel said in Software update 2.13.18 for S series (S3,S5,S9):

Or my form is linked to GNSS quality on that particular day

Clearly you, in particular, need to watch out for those times when Galileo is in conjunction with Beidou while GPS is in retrograde. Have your geo-location read. It’s a side biz for the nerdier astrologers.

[Łukasz Szmigiel]

@Fenr1r will have to keep that in mind, good point. Right after I check my tarot before my next run that is!

[Dimitrios Kanellopoulos]

@Łukasz-Szmigiel without wanting to mitigate an issue an advice I give to all my running friends:

Do your self a favor and buy a stryd. Suunto, Garmin, COROS , that will help you with the pace no matter what brand name you are using.

[A Former User]

@Dimitrios-Kanellopoulos hehe, that’s funny as recently I was considering buying a Styd for my runs, just to rule out occasional distance problems due bad GPS signal.

[Bulkan]

@Dimitrios-Kanellopoulos said in Software update 2.13.18 for S series (S3,S5,S9):

@Łukasz-Szmigiel without wanting to mitigate an issue an advice I give to all my running friends:

Do your self a favor and buy a stryd. Suunto, Garmin, COROS , that will help you with the pace no matter what brand name you are using.

Best advice ever and deep a bit into the knowledge of running with power. If you run into a tunnel you will get instapace… Stryd is very reliable.

[Łukasz Szmigiel]

@Dimitrios-Kanellopoulos I run for fun, good health and mood (and mud too, when weather permits, if you know what I mean). The pace is not an issue for me nor does it distract me in any way. Especially now when I’m still struggling with marathon-related injuries and I have no need for speed.

Just curious if there’s any significant relationship between what watch gets from GNSS and the pace it computes. That’s it

Stryd is interesting (numbers, numbers, hehe) but I’d rather get a new pair of shoes when the need arises (or a new backpack, etc.). I find it quite pricey for what it does for 100% amateur use.

[Dimitrios Kanellopoulos]

@Łukasz-Szmigiel roger

[Rob33]

@Dimitrios-Kanellopoulos the gain in autonomy (duration) is known? it concerns other systems but not GPS?
the gain is not canceled by more frequent points registration?

[Dimitrios Kanellopoulos]

@Rob33

There are 2 things for you to consider.

• Sampling rate aka how often you ask for GNSS updates (your location)
• Recording rate aka how often you record those GNSS points.

The recording rate changed, the sampling rate was always 1s

[Rob33]

@Dimitrios-Kanellopoulos OK. the recording frequency rate does not affect the autonomy.

“the sampling rate was always 1s”: it makes sense but then how do you gain autonomy ? (simple curiosity )

or is the improvement more about precision?
or both?

[Dimitrios Kanellopoulos]

@Rob33

Best: 1s Sampling rate
Endurance: 1 minute sampling rate
Ultra: 5 minute sampling rate

[Rob33]

@Dimitrios-Kanellopoulos I know.
I was talking about the gain announced a few comments above? (New GPS firmware from sony that improves many things including power consumption for other GNSS systems than GPS)

[Dimitrios Kanellopoulos]

@Rob33 I suppose the maths that the chip does are simplified and other techniques. Complicated subject. Includes SNR etc.

[Łukasz Szmigiel]

@Dimitrios-Kanellopoulos you mentioned that new GPS firmware improves power consumption with other GNSS than GPS. Shouldn’t it be reflected in estimation on activity start screen? Or simply those gains in power are reflected in better accuracy? Or are they internal and not reported by battery time estimation?

Having my watch at 85% I get 20h estimated time with GPS only and GPS plus Beidou and 14h with GLONASS and Galileo which is identical as with previous firmware.

[markytarky]

@Łukasz-Szmigiel true, I just tried the same, full battery 24h best performance on GPS only, 18h best performance GPS +Galileo

[Brad_Olwin]

@Łukasz-Szmigiel @markytarky When I test the battery life, I typically do this on a run or ski that is at least 4-6h, longer if I can. The watch will provide an estimate but it is just an estimate. Moreover, if you are needing sufficient battery for long endurance events does it really matter which satellite system is used? Or how precise your track is? Under long events Endurance mode will only get a GPS fix every minute and FusedTrack will fill in the details so why not use GPS only? There are improvements with power consumption but what you are asking simply does not make that much sense.

[Rob33]

@Brad_Olwin The idea is, I believe, to be able to do ultra trail (up to 24 -26 hours) while still using the Best 1s mode

[markytarky]

@Brad_Olwin thanks, I got your point. I think we both were referring to this sentence: New GPS firmware from sony that improves many things including power consumption for other GNSS systems than GPS. So kind of common sense is telling us most probably it will increase the estimate while using the GPS with another system. Thank you again.

[Dimitrios Kanellopoulos]

We didn’t bump up those numbers as the improvement might be 1-2h (or more).

Changing the estimates can create complexity , from people who read the specs but still don’t have the update etc.

Better be on the safe side.