S9B crash during navigation.
-
Can you explain what chnages with the correct versions of the tests ? Thanks
-
Hi , the changes is not use Suunto Plus Climb and the GPS+QZSS+GLONASS to GPS+QZSS+BEIDU , but I don’t know if is a problem to use POI with external platform https://www.plotaroute.com that’s hangs or a problem with Suunto Plus Climb or GPS+QZSS+GLONASS
-
@Dimitrios-Kanellopoulos OK watch crashed again today and I managed to send the log. It was sent at 10.57 UK time.
Few similarities to last time:
location was similar.
It was the second waypoint
And I was using the 2nd best GPS performance - I hardly ever use this mode, I normally have it on best, could this cause an issue?After crash I rebooted the watch, loaded the GPX with top tracking and had no further issues.
This time I was following the route the correct way around but had left the route for around 3km, and it crashed just after joining back on the route.
-
@Audaxjoe said in S9B crash during navigation.:
And I was using the 2nd best GPS performance
Isn’t navigation always in “best” GPS mode? No matter what GPS mode you select?
-
@surfboomerang meaning if you’re on the nav screen? Think yes
-
@Audaxjoe the GPS sampling frequency does not cause a crash for me and I use endurance mode frequently. When on the route screen if a route is loaded or breadcrumb screen the watch will switch to best GPS fix while on those screens and then revert to the set frequency when on other screens
-
@Brad_Olwin I have no idea what caused the crash, just that the watch has crashed twice since last software update. I am not sure which screen I was on when it crashed either, just that navigation was on following a route with POI on it.
I have had the watch two years and it has never faltered before.
-
@Audaxjoe probably not your case, but does it happen always in tgr same area? I remember a user, maybe a year ago or so, having a watch crash all the time he/she approached a military base.
-
@isazi nowhere near any military base but was in a similar location. Been out today with no issues. Maybe the log will shed light on it.
-
I had this happen to me today, after it rebooted after 8km I set up the run exactly the same and ran the remaining 14km with no problem, first part had lots of missing data like ascent and decent. I was using Suunto Plus Climb and following a previously created route.
-
@Audaxjoe did you use climb ?
-
@Dimitrios-Kanellopoulos I used climb on both runs, first one crashed second was fine. Going to try it again today see what happens, I am thinking as someone suggested it could be to do with a route I was following maybe?!
-
@Mark-Hooper yes that is correct. I am just interested to make sure if it needs both to be on to crash. I personally cannot reproduce this
-
@Dimitrios-Kanellopoulos it seems random because I set up the second run immediately after the crash while I was out on the road using the exact same settings, route and using S+ Climb.
-
@Mark-Hooper please next time also try to send the logs via the Suuntolink and mark the time and ID that it will be passed back.
If possible after your workout so that the logs are not overwritten.
-
@Dimitrios-Kanellopoulos I will, thanks for helping out
-
@Dimitrios-Kanellopoulos no, I have never used climb.
I use the watch a lot, and navigate with waypoints normally for bike rides around 200k, shorter ones I know where I am going so don’t normally use a route and the atch is perfect.
Just these two walks one reversing a track and crashed at second waypoint, the other following it as plotted at second waypoint, the waypoints were around a 2km from each other. The only other thing I can think of that I had done different to normal was not use the top GPS tracking.
I’ll try and plot another route to the same spot and see if I can reproduce it.
After the Crash on Saturday, I think around 6km into a 42 km walk, after I restarted the watch it navigated perfectly for the remaining distance, and I did leave then return to the route a few times with no issue. This time I used top GPS tracking which was why I mentioned it. By the sounds of it a total coinsidence but both crashes were using the second tier tracking.