Suunto app Forum Suunto Community Forum
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

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

    Scheduled Pinned Locked Moved Watches
    99 Posts 25 Posters 7.7k Views 27 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Brad_OlwinB Offline
      Brad_Olwin Moderator @lexterm77
      last edited by

      @lexterm77 No, but I think it may be faster if it is off.

      Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing

      1 Reply Last reply Reply Quote 1
      • isaziI Offline
        isazi Moderator @lexterm77
        last edited by isazi

        @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

        lexterm77L 1 Reply Last reply Reply Quote 1
        • lexterm77L Offline
          lexterm77 Bronze Member @isazi
          last edited by

          @isazi

          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.

          C8EB1A20-4AA8-4AA5-8988-0C1340860496.jpeg C8ABD0C1-94D1-4661-8A08-8C41988F7352.jpeg

          1 Reply Last reply Reply Quote 2
          • Łukasz SzmigielŁ Offline
            Łukasz Szmigiel
            last edited by

            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.

            S9PP 2.40.44

            1 Reply Last reply Reply Quote 5
            • lexterm77L Offline
              lexterm77 Bronze Member
              last edited by

              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 😁

              freeheelerF 1 Reply Last reply Reply Quote 3
              • freeheelerF Offline
                freeheeler @lexterm77
                last edited by

                @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

                sartoricS Łukasz SzmigielŁ 2 Replies Last reply Reply Quote 6
                • sartoricS Offline
                  sartoric Moderator @freeheeler
                  last edited by

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

                  SVTS - 2.40.38
                  SSSWHR BARO Amber - 2.8.32
                  Samsung A5 2016 - Android 7.0
                  Samsung A33 2022 - Android 14 - One UI 6.1
                  Suunto App Android 5.2.5 beta
                  Suunto App IOs 2.45.0 (19123) beta on MBP M1

                  1 Reply Last reply Reply Quote 2
                  • Łukasz SzmigielŁ Offline
                    Łukasz Szmigiel @freeheeler
                    last edited by

                    @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.40.44

                    freeheelerF EgikaE 2 Replies Last reply Reply Quote 4
                    • freeheelerF Offline
                      freeheeler @Łukasz Szmigiel
                      last edited by

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

                      living sideways

                      1 Reply Last reply Reply Quote 0
                      • lexterm77L Offline
                        lexterm77 Bronze Member
                        last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • EgikaE Offline
                          Egika Platinum Member @Łukasz Szmigiel
                          last edited by

                          @Ł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.

                          t6, S6, Elementum Terra, Ambit 3 Sapphire, Spartan Ultra Copper, Traverse Alpha, S7 Graphite LE, S9B Ambassador, S9P Granite Blue Titanium, S9PP Titanium Sand, Vertical All Black, Race Titanium Charcoal,
                          Race S All Black - TI Canary - Titanium Courtney

                          1 Reply Last reply Reply Quote 2
                          • L Offline
                            lobo_tommy
                            last edited by

                            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.
                            Suunto9_Ascent.jpg

                            DMytroD 1 Reply Last reply Reply Quote 0
                            • DMytroD Offline
                              DMytro @lobo_tommy
                              last edited by

                              @lobo_tommy non baro version?

                              L 1 Reply Last reply Reply Quote 0
                              • L Offline
                                lobo_tommy @DMytro
                                last edited by

                                @dmytro correct

                                DMytroD 1 Reply Last reply Reply Quote 0
                                • DMytroD Offline
                                  DMytro @lobo_tommy
                                  last edited by

                                  @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.

                                  L Dimitrios KanellopoulosD 2 Replies Last reply Reply Quote 1
                                  • L Offline
                                    lobo_tommy @DMytro
                                    last edited by

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

                                    1 Reply Last reply Reply Quote 1
                                    • Dimitrios KanellopoulosD Offline
                                      Dimitrios Kanellopoulos Community Manager @DMytro
                                      last edited by

                                      @dmytro correct. 7 meters.

                                      Community Manager / Admin @Suunto
                                      Creator of Quantified-Self.io
                                      youtube.com/c/dimitrioskanellopoulos
                                      https://instagram.com/dimitrioskanellopoulos
                                      https://www.strava.com/athletes/7586105

                                      1 Reply Last reply Reply Quote 1
                                      • isaziI isazi unpinned this topic on
                                      • First post
                                        Last post

                                      Suunto Terms | Privacy Policy