Suunto 9 Baro, possible bug, auto-stop not working when stopping under bridges.
-
There is an annoying bug with the 9 Baro and the auto-stop function. While cycling, and at stops in traffic lights under bridges, although the speed drops to zero the watch keeps going in on. I thought it was just me but I confirmed it many times. Autostop works properly everywhere else but under bridges. For long stops I have to pause the recording myself, but then many times I forget to resume it after a few minutes have passed missing parts of the ride.
-
@zanxion This might be quite difficult to solve… I believe that your watch probably loses GPS signal under those bridges, right? Or perhaps it is so jumpy that it cannot really determine whether you’re moving or not…
Triggering autopause every time GPS signal is lost wouldn’t make much sense…
External bike pod might help here, but that would be an overkill solution -
@zanxion autopause depends on speed and on signal. We cannot determine a good stop if the signal is not good. Bridges can also create 0 speed if gps is lost etc
-
@Dimitrios-Kanellopoulos said in Suunto 9 Baro, possible bug, auto-stop not working when stopping under bridges.:
@zanxion autopause depends on speed and on signal. We cannot determine a good stop if the signal is not good. Bridges can also create 0 speed if gps is lost etc
My old Garmin Edge 130 cycling computer has no problems though, nor my newer Wahoo Elmnt Bolt. They both always pause when the speed reads 0 for a few seconds. It does not make any sense else like. What if you get into a tunnel and all is lost? Is it going to record a mile long at 0 speed? If this is not possible, make it so that at least the actual moving time is calculated at the end of the activity just like any other tracker/app.
— Edit —
Just a thought! Could it be that the cycling GPS computers have a build in accelerometer while 9 Baro does not? -
@inkognito said in Suunto 9 Baro, possible bug, auto-stop not working when stopping under bridges.:
@zanxion This might be quite difficult to solve… I believe that your watch probably loses GPS signal under those bridges, right? Or perhaps it is so jumpy that it cannot really determine whether you’re moving or not…
Triggering autopause every time GPS signal is lost wouldn’t make much sense…
External bike pod might help here, but that would be an overkill solutionIn my whole track there is a part I stop for about 5 minutes under a some 10 meter wide bridge. The entire ride is spot on. Stopping under that bridge for 5 minutes the watch reads 0 for five minutes. Cmon, it does not have to be that funny! Make it at least trigger a pause when things look like 0 Km for 10, or 20 seconds.
-
Yesterday I tried my son’s cheap and fairly old Garmin Forerunner 45 and it does it pretty well! Such a shame! This is something that should be addressed!