This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GPS Freakout

I've been using a Forerunner 235 for 3 months. GPS accuracy has generally been OK but totally failed today. As the attached image shows, the first 100 meters was accurate then the readings went haywire. I stopped at a point I know is 1.6km -- though the watch was already up to 2km. There was a thunderstorm on the horizon. Could this have disrupted the GPS so dramatically? Is there anything I can do to reduce the possibility of this happening again? By way of background, I normally wait 4-5 mins after turning the watch on before starting to run -- normally well after the watch says GPS is ready. Setting is GPS + GLONASS. Any advice appreciated.

  • Has it happened more than once? Sometimes these things happen. The time to get excited is if it happens repeatedly. It's very difficult to suggest what, if anything, could be wrong from what is possibly a one-off occurrence.
  • Thanks Phillip. It has only happened once so far -- though I had a 610 for 4 years without it happening at all. If it does repeat, I will update. One thing I prefer with the 610 over 235 is that you can view the individual satellite connections so you can ensure there are enough before you start an activity.
  • Former Member
    0 Former Member over 8 years ago
    Same thing

    I had the same thing happen yesterday - GPS was ready and locked - after about 1.2km GPS appeared to go haywire - showed a pace of 2 min/km and distance ratcheted up to 5km (at about actual km 2). Then around half-way (8km run) the distance locked at 5.82km for the next 2km. Had one further drop-out. Bottom line 8km run showed as 7.48km, no map and information appears to be garbage. I'm wondering if this is related to a recent software update (never happened before).
  • Former Member
    0 Former Member over 8 years ago
    I've been having similar issues --- my regular runs aren't recorded accurately, and when I use the Bike activity the GPS doesn't record anything at all despite saying that it's connected. Trying a hard reset to see if that will solve it.
  • Former Member
    0 Former Member over 8 years ago
    Similar problems for me

    I did a marathon last Sunday and my mile markers were about .25 to .3 miles before the race markers. At the end it said I ran 26.56. I ran near home yesterday and it buzzed at the one mile mark well before what I know to be the actual mile mark. Probably .2 miles anyway. I was also running Runkeeper on my phone and it was off from that also. It seems only the first mile was off and then the rest were ok. Neither run had the map come up on connect.
    I see theres an update that Im downloading today. Hope this fixes it
  • Former Member
    0 Former Member over 8 years ago
    When running a race you have to keep in mind the way the course was measured and that in the first miles you will be weaving and swerving around runners leading you to run a longer distance.

    Here's a longer exlanation by DCrainmaker http://www.dcrainmaker.com/2009/03/racing-line-understanding-how-courses.html