-
I simplify my training by running the same routes throughout the year. It’s not to say I don’t add new ones, but I don’t very often.
Since this update I’d noticed that I was having to run further to clock up the same distance on any route over 1 mile long. As a result my pace has been showing up as slower, which makes all my benchmarks out of reach! While I have the perception of more speed, while achieving more Strava segment PR’s, my overall pace and times have suffered.
Today was particularly infuriating as I felt fast on an 8.20 Km hill run route that’s been a regular over the years using both Garmin’s & Suunto. I PR’d a half dozen segments, yet my average pace showed up as the slowest since 4th February 2017. What I found was that when I saved out the run, it had taken the GPS end point from hundreds of metres further back up the track. I’m guessing the GPS had been lost at that point and never recovered. I actually finished the run and saved out after running 100M further than where I’d started. Looking at the average distance on this route, Today’s run is 500 Metres shorter, a 6% error. You have to bear in mind that in 2018 all runs on this route were within 13 seconds of each other, for around 42 minutes duration.
I can’t train with these kinds of errors. I missed out on a potential 5K PB only the other day because the regular 5K running route I’ve used for years, became 4.8K according to my Suunto!
Anyone else noticed anomalies since 2.8.24? Anyone have any suggestions on a fix, except a soft reset which I’ve already done?
Thanks!
P.S. Elevation gain has also been repeatedly wrong since either the update or moving to the Suunto App. Strava can fix that, but trying to fix distance in Strava at the moment is impossible as it makes a right mess of the whole thing!
-
@Darren_M
I had a similar issue with a previous FW
https://forum.suunto.com/topic/2345/firmware-2-6-54/141Try to enable/disable GLONASS
-
@sartoric Thanks! I’ll give it a go in a moment and I’ll likely know if it’s worked by the end of the week. Nice to have some potential light at the end of the tunnel as it’s become rather pointless pushing myself to near destruction only to realise I’ve been let down by the watch and none of it counted!
-
@sartoric Oh dear, there’s a revelation! I don’t have the option to switch Glonass on! It’s greyed out, with or without GPS locked. On the image look at ‘Power Saving’ which is white writing, Glonass above isn’t, like it’s inactive, not installed! Do you agree?
-
@Darren_M
Check if GPS is enabled and the precision setting. GLONASS need “Best”Maybe precision setting is also the reason for your problem (eg. if set to OK)
-
@sartoric Ok thanks. That setting was used today. It’s an intermediate setting which I use with longer trail runs. My battery was around 45% so I enabled that setting, but the GPS setting is set to GOOD. Also, the GPS has been bad on my flat running setting mostly, which is set to BEST.
I’ve switched Glonass on and off now. I’ll report back when I’ve had time to test.
-
So, after switching Glonass on/off I ran to the Gym, then ran home after a weights session. The run there clocked 1.35 Km, yet the run back showed 1,39 Km. So a 40 metre error in less than a mile strikes me as excessive. I can see on the map where the error exists, and it appears that when I stopped and saved the run to the gym, the GPS end point takes a position tens of metres further back, and hence robbing me of distance.
Then I did a hill run the next day, with part of the route tree lined. This time Glonass enabled throughout. Same again, on an 8 Km route the GPS robbed me of 200 metres, by taking the last fix at save, 200 metres behind me. The track on the rest of the route looks very accurate, even in the tree lined section the GPS is overlaid on the track. It’s as though the GPS is going wrong right at the end of the run, when saving. Obviously this is skewing the distance and hence my average pace, which is no good to me whatsoever.
Does anyone think a full factory reset would help, or am I wasting my time? Any other suggestions?
Thanks!
PS. Just seen update 2.8.28 update available. Is this likely to fix my GPS?
-
@Darren_M said in SSWHRB losing GPS frequently since update 2.8.24:
PS. Just seen update 2.8.28 update available. Is this likely to fix my GPS?
I don’t think so, but you can try.
Consider the fact that in the last days there is an issue updating AGPS, so some slowness in getting the signal or find new satellites (so some imprecise positioning) while moving could be due to that. -
@sartoric Looks like that maintenance update fixed the issue, for now at least. Have ran once around the streets and once in the hills since. Both GPS tracks are bang on accurate. Of all the problems I’ve had with my SSWHRB, GPS has never been an issue until this time. I hope this issue will not repeat!
Thanks for the help @sartoric
-
@Darren_M
Nice to hear, but maybe the 2.8.28 FW is not the solution, but only flashing the watch is what did the trick. Maybe something was messy in your watch and this process clean it.
Btw, happy for you.
