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

Routes drawn wrong

Yesterday and today the routes are somehow wrong. I started and ended my run from that end marker in the screenshots, but f945 marked it as end point and start point is somewhere along the route. There is really a loop at the end of the run, and it seems it only started recording the route halfway down the route. What is strange is that the distance seems more or less correct for the complete route (so just the route in the picture is missing a part). 

  • This is usually caused by that you started the activity before you got the green GPS signal. FR945 is good in using the steps and step distance to calculate the distance before you got a GPS position. My tip is to have a data screen with a map. Before you press start you can check that the watch got the correct position. I always do that since there has been a couple of occasions this year with expired CPE files that messed up the tracking completely. You would even get the green GPS signal, but the position was way off. The position was pretty ok after 5-10 minutes but still had some offset issues.

  • Yes, makes sense but during these two days that would mean it has taken 10-20 mins to acquire the GPS lock while normally (last 6 months I've had the f945) it has received the GPS lock within 10-20 secs. So wondering if this is again some wider GPS issue. Will need to test getting GPS lock later today.

  • If you start the run it will take a lot longer time to get a GPS lock. I accidently started a run without a GPS lock and everything looked fine since I got both distance and pace, but the map didn't work. I thought it was some sort of bug since all the other values worked so I just continued to run. After 40 minutes the watch got GPS lock and everything worked perfectly after that.

    I've experienced that the GPS lock takes longer time to get after software updates and change to summer/winter time. Right after those occasions I always do a restart and put the watch outside to get a first GPS lock. Sometimes it goes really fast and sometimes it takes several minutes to get the lock so I believe my routine is healthy and I never have to wait that long extra time right before my run.

  • I usually just put my watch in the window before I go for a run and let it get a fix there, then once out the fix is very quick... let it be green for a minute or so and you should be fine (I usually walk before running as a small warmup, less the 5 minutes). Never an issue.

    Examples above indeed seem like a 'original fix is wrong, started too soon' and the the offsets are ok (as in if you'd move teh track so that the startpoint is at the actual starting points it's probably perfect) so it all is a bit weird.

  • Hello Bertil, if it's taking that long to acquire satellites it might be worth your time to run through these steps. 

    • Plug the watch into a computer
    • Access the device drive
      • Connect the Garmin device to the computer 
      • Press the Windows key + E on the keyboard to open Windows Explorer/File Explorer
      • Select This PC (Windows 10 only)
      • Open the Garmin drive listed
    • Open the Garmin Folder
    • Right Click on the Remote SW folder and delete it
    • Sync with Garmin Express 

    *Note because the 945 is a music playing device these steps will only work on a Windows computer. 

  • *Note because the 945 is a music playing device these steps will only work on a Windows computer. 

    Install Android File Transfer or similar to access the Garmin  Folder and delete the Remote SW folder on MacOS

    I do wish Garmi would start including this for MacOS users.

  • Thank you all for comments, suggestions and ideas! Hearts️ Although the map version on the watch was very new (last updated ~1 month ago), there was a new version available (Europe 2020.20), and after updating that I again get very quick GPS lock. It can be that the map update process did the suggested Remote SW deletion, or something, but it works great again.