Software update 2.13.18 for S series (S3,S5,S9)
-
@Radu-Negoescu it seems like elevation can be shown on very limited areas. I cannot find none of elevation numbers on google map 200 km around my living place.
-
I used beidou with gps on trail run today and it looks worse than on gps only. I am switching back to gps only. I am happy with it (gps only) as it now looks indistinguishable from my A3P tracks.
I had few seconds power drop to zero on Stryd wind device on one of my non stop run activities this summer and contacted Stryd Support, they quickly replied to me that is a known Suunto9b problem of dropping connections. I forgot to mention that here on forums as beer and bourbon mixed with some curated playlists of Coltain&Miles and news put on mute with caption seemed to be more interesting thing to be occupied with than ranting on forums about power drop on a power meter loosely attached to the laces of my left shoe. Fortunately, this problem seems to have gone away by itself.
-
@stromdiddily Donât know but when we have major fronts come through my elevation can change by 50-100m. As soon as I exercise FusedTrack fixes it. I donât worry too much about it. I know my house is not sinking.
Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing
-
@Brad_Olwin Totally right. I noticed that too on drastic weather changes.
But to me it doesnât make sense that the watch interprets pressure change as altitude change while it is in standby/sleep mode. It knows it isnât moving, because the display turns off.Once you keep moving it, I imagine it can be harder to distinguish pressure change is due to weather change or altitude change.
-
@surfboomerang The interesting thing for me is almost all of my storm alerts come while I am exercising. When I go back and check with a mountain weather station, I find the watch was correct, there was a huge drop in pressure that was fast. Our weather is complicated, I am at 1550m and a few km from me is a wall that varies from 3900 to 4300m. We have complicated weather patterns and wind and the weather can change over the period of a day or a couple hours. The other issue is work for me is 1700m and traveling back and forth is more problematic for elevations not being correct in the two places.
-
@Brad_Olwin issue isnât so much w the home location but I do rely on the watch face altitude when out backpacking. Useful in making sure Iâm on the right/same level as campâŚ
-
@stromdiddily The work around for this is just use the auto-calibrate feature when you are at a camp. This always restores my altitude values.
-
Do you need to take watch off wrist for auto calibration?
-
@lexterm77 No, but I think it may be faster if it is off.
-
@lexterm77 I also tried GPS only today, but I have got a worse track than yesterday with Beidou. Will try few more times.
One interesting thing I noticed though, is that it seems (in a totally non scientific way) that I get better Fusedalti without Beidou. I will also check if this is the case in the next few days.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
With Beidou my tracks are 5 meter apart, with GPS only they are half a meter apart.
One is GPS only around parking lot, it is spot on, couldnât draw better myself.
Other one is trail run with beidou, single track trail is visible on sat image but tracks are like 15 meters apart.
-
My observations with current firmware (S5) as compared to older versions:
- GPS only is universally good except in deep forests or urban canyons. Itâs as good as previously with Beidou.
- Beidou makes my tracks more âwobblyâ and in my experience is the least useful system with current firmware.
- Glonass is ok but I donât find it more useful in general everyday trainings (itâs superb in mountains though).
- Galileo - if there are enough sats available - is a monster. It struggles near dense and high buildings but in every other area itâs perfect for most of the times. I canât think of a better track precision in a running watch.
Also, âoffset locksâ happen way less often than before. It used to be a norm when changing direction (ie. 90 deg) for the track to be locked on a constant offset by 10 - 20 meters. Now it happens rarely.
It may be placebo (as everything written above ;-)) but I feel that my tempo doesnât drop as dramatically when entering wooded area. It used to drop from 6/min to 7/min only because Iâve entered the park from river embankment.
I also get an instant fix almost always.
It really is amazing.
-
Feature idea: use gnss data and route information to automatically select system with most satellites visible at that time, account for duration for completion of activity and terrain type (flat route no trees means you can catch sats at lower sky points while wooded area with lots vertical points on route means only high sky satellites are ones in direct line of sight or city routes) let algorithm decide best choice for you. Of course this would need to be done in app but with predetermined window of activity start time in lets say next 24hours would be passed onto a watch as calculated âbest choiceâ for which gps system would watch choose for each route. I can see that some satellites are barely populated at some time of the day (8) while sometimes there are 12 of them. Each hour has its advantages. These satellites (most) are moving across the sky, they are not geostationary or geosynchronous orbits. If all this is complicated an artificial horizon can be optimized for universal satellite count at lets say 20 degrees above horizon and which system has most satellites is the one being chosen
-
@lexterm77
interesting idea.
I expect that this is likely never to come, because of a crazy bad effort/benefit ratio.
I mean, how bad is it really when the track we record is 5-10m off at some points? It looks ugly on the map, yes. But most of my tracks are well within what I consider precise.
I can imagine that it would take a lot of coding and even more testing before this type of algorithm works flawlessly.Iâm happy with my tracks and if I manage to keep my baro sensor dry and clean Iâm happy with the altitude, too
living sideways
-
@freeheeler not to mention that Spartans wonât get any new firmware
-
@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?
S9PP 2.37.48
-
@Ĺukasz-Szmigiel
my wild guess: it needs at least GPS and all the others are the whipped cream on top -
Of course if choosing any option other than gps only renders track scattered, auto option would do no better than a random choice
-
@Ĺ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. -
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.
