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

[sartoric]

@freeheeler not to mention that Spartans won’t get any new firmware

[Łukasz Szmigiel]

@freeheeler basically this.

The only thing that I believe might be beneficial for all of us is an “auto” mode when you go outside the watch checks which sats are available and chooses the best GNSS at the moment. But this also is prone to errors as what the watch would choose at the beginning of the workout might be bad for the rest of it. Ideally the chip would use all GNSS available and mix them in the same way mobile phones do - just use the best sats that are available at the particular moment - but that might not be possible considering that we’re talking about low power chip. I’m not even sure if it’s possible to get a location from 2 GPS sats, 1 Beidou and 1 Galileo or do you always need to have a “base” fix from 1 GNSS and then augment it with other GNSS.

And in the end - why? If there’s no fix at all - it sucks, but if there’s ~15m error for couple hundred meters - why bother?

[freeheeler]

@Łukasz-Szmigiel
my wild guess: it needs at least GPS and all the others are the whipped cream on top

[lexterm77]

Of course if choosing any option other than gps only renders track scattered, auto option would do no better than a random choice

[Egika]

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

@freeheeler basically this.

The only thing that I believe might be beneficial for all of us is an “auto” mode when you go outside the watch checks which sats are available and chooses the best GNSS at the moment.

I think this is exactly how the GPS chip in the S7 does it.
Works pretty well.

[lobo_tommy]

Can someone explain why ascents are somehow substracted with descents? My workout shows 28m ascent and 35m descent, where I can clearly see from the graph that it was way more (friend of mine with other brand watch had over three times more elevation gain on this route). 28m is just one longer uphill ride in the middle of it.

[DMytro]

@lobo_tommy non baro version?

[lobo_tommy]

@dmytro correct

[DMytro]

@lobo_tommy it’s all fine then. Alti graph is a representation of non filtered data ( threshold for non baro watches is 14m, or was it 7?) and ascend/decend values are being derived from filtering the data. So if you have two small decends roughly threshold sized - only only one might have remained after filtering. All other spikes could have been noise or not big enough altitude changes to make it towards the totals.
It’s not an issue per se, but a limitation of a device - feel free to search for ‘Altitude issues’ in the forum, it has been discussed plenty.

[lobo_tommy]

@dmytro thank you very much, that is an explanation I was looking for.

[Dimitrios Kanellopoulos]

@dmytro correct. 7 meters.