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

FW v11.00 - Constantly off course for ~1 second intervals?

I upgraded to v11.00, and now when following a route I constantly get messages saying I'm off course. These last a few seconds, and then I'm back on course. Is anyone else experiencing this? Does anyone know how to fix this? This is really, really maddening.
  • I get the same - but not always. Some times I do and sometimes not. Also I've noticed that or some routes it's working fine until after I stop for coffee. When I restart (either having put the 820 to sleep or turned it off) it starts constantly report Off Course then Course Found every 5 or 10 seconds or so. It (seems) to still give directions.
    Very very annoying.

    I've been running 11.00 since it first came out. I've tried leaving the unit switched on and stationary for about 30 mins.

    Nick
  • Sounds like the same problem on the 520+. Have a read of post #10 for a solution.

    https://forums.garmin.com/forum/into...t-course-found


    Thanks Alan - I reset the device this morning before going for a ride and it worked flawlessly. No lost & found messages.

    Well mostly flawless except when it kept telling me to do a U turn after a coffee stop. After stoping the route and restarting it sorted itself out. It may have done so if I'd left it - who knows. The coffee stop was at the end of an out and back leg on the same roads.

    Anyway - I'm happy that the problems been cured.

    Why is it such a faff to reset - saving the files - reset - restore - try and persuade the device to pair with my iphone. It would be nice if there was a simple garmin express function to save - reset and restore.

    Nick
  • OT for the OP but in response to nickdodo's U-turn...I've occasionally had Edge units get confused when part of the course overlies itself, as does an entire out-and-back, lollipops, etc.. I usually will divide a course into two, an out course and a separate back course in the case of an out-and-back, or simply stop the course short of the return leg of a lollipop. The Edge will keep recording ride data after the first course navigation ends, the new one loads, and the navigation starts again.
  • Thanks Looigi,
    i usually manage it ok with a stop and restart of the course. Sometimes it just sorts itself out.
    Nick
  • and again I have to say ... MEE TOO
    but I think that 820 is too good now !?
    I think that it's belong on witch site you are creating the track and what map you use for following the road.
    Example: I create my track with ridewithgps.com and select therefore the OSM map to draw , after the download on Edge, for my ride I use the last map Europe 2018.20 , then indeed I have a lot the "off course" message , after I ride the same track but using the map I download from openfietsmap.nl "OSM Generic routable new (BEL_14 1 2019)", with any "off course" problem !?!?
    Now ... if you load the track in BaseCamp and look closely on the Map's from your GPS (not the one on the desktop) you will see that the track is not following properly the streets on Europe 2018.20 and exactly on the roads in the "Generic Map"
    So my conclusion will be that the 820 is too precisely and when you are a few meters out off the track (on the right road) he gives the message "off course"
    It is a opinion, I don't know if it is right, (I also have any trouble with a road create with MapMyRide and using the Garmin Map Europe 2018.20, I do not try with openfietsmap)
  • Noppe! A little ride today, I try all the combinations and have all the morning the message "off course"
    Like usual let's wait for a update ...
  • Just to add to the chorus, I had this problem too yesterday. Activity and route attached. The route was created in Strava and uploaded via the Strava app.
  • I experience the same problem today. In another post it is also linked to strange drop-outs in speed recording when that is based on GPS signal. Looking back in Garmin Connect it is vissible in all rides since the V11 update. Seems like a very buggy update with regards to GPS reception.
  • Same for me, I've disabled sound alarm just to avoid to become mad, but now battery last much less due to continuus wake up