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

Baro 9 inaccuracies

Scheduled Pinned Locked Moved Suunto 9
6 Posts 4 Posters 309 Views 4 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.
  • A Offline
    adamreah
    last edited by 24 Jan 2019, 19:17

    Hi all.

    Just been for a short run with my other half. I have a Baro 9, she has a garmin forerunner (new). After having ran 2km my Baro 9 was reading 500 metres further than we had run. The wife’s garmin was spot on.

    I have had an inaccuracy issue in the past but I brushed it aside. I am now however slightly concerned that this is an issue with the watch.

    I am a climbing instructor and often take groups into remote locations, I bought the watch as an aid / backup for my work, however if it can be 500m out of kilter in a 2km distance then I am worried.

    Has anyone else had these issues? Just as a additional I was using a fenix 3 previously, which was fine and never missed a beat, it did however die releatively quickly hence the switch to suunto.

    I am now fearing I may have made a mistake. Is this something that can be remedied. I have gloss’s on and I have recently calibrated the compass

    Cheers.

    Adam.

    D 1 Reply Last reply 24 Jan 2019, 19:21 Reply Quote 0
    • D Online
      Dimitrios Kanellopoulos Community Manager @adamreah
      last edited by 24 Jan 2019, 19:21

      @adamreah try a 12s upper button reboot, sync to get the GPS optimized and retry.

      I have seen inaccuracies with S9 due to wrong caching

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

      A 1 Reply Last reply 24 Jan 2019, 19:44 Reply Quote 0
      • A Offline
        adamreah @Dimitrios Kanellopoulos
        last edited by 24 Jan 2019, 19:44

        @Dimitrios-Kanellopoulos ok. Thanks for this. I actually did this recently as the touchscreen stopped working. Is it still worth doing again?

        S 1 Reply Last reply 24 Jan 2019, 20:29 Reply Quote 0
        • S Offline
          sartoric Moderator @adamreah
          last edited by sartoric 24 Jan 2019, 20:29

          @adamreah
          Yes, to refresh GPS data

          How was the accuracy before previous reset ?

          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

          A 1 Reply Last reply 24 Jan 2019, 21:27 Reply Quote 0
          • A Offline
            Audaxjoe
            last edited by 24 Jan 2019, 21:21

            I have moved from a Fenix 3 to the 9 Baro (after a couple of buggy Fenix 5) and have found the 9 to be accurate - my better half has a Fenix 5s and I also run a Garmin Etrex 30x and all three are within a few meters of each other on a 100k bike ride. So hopefully it is a glitch.

            Suunto Vertical
            Suunto 9 BARO
            Garmin Fenix 3, 5
            Suunto Vector

            1 Reply Last reply Reply Quote 0
            • A Offline
              adamreah @sartoric
              last edited by 24 Jan 2019, 21:27

              @sartoric yeah it was accurate. I’m not really tech savvy so I don’t understand how you can get a ‘bad reset’, to then get a ‘good reset’. Still I will try it and reset the watch again.

              1 Reply Last reply Reply Quote 0
              6 out of 6
              • First post
                6/6
                Last post

              Suunto Terms | Privacy Policy

                This community forum collects and processes your personal information.
                consent.not_received