Related
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

Slow GPS fix and EPO expired in fw 10.10

oBuTTuSo
Ever since I installed firmware 10.10 it takes ages for the GPS to get a lock on satellites and the watch states that EPO is expired under settings/about.
Syncing via wi-fi or GCM (iOS) does not improve the situation. Any ideas?

Edit: I use GPS only, no Galileo or GLONASS
  • 0
    Possibly not much help, but I've just deleted my EPO.bin, disconnected from GE and EPO was 'Missing'. Reconnected to GE, synched and EPO noted as Current. On the occasion I have had a slow GPS fix, powering off and on seemed to kick it into gear. Most of the time though the GPS fix has been pretty good. Currently on 10.10, 2.20 set to GPS+Galileo and no extras.
  • 0
    I swam yesterday for 52 minutes after a satellite lock, is this good for gathering info ?

    It depends on how long this satellite lock has been. more than 15/20 minutes stationary quite surely will wipe out the "expired EPO" problem.

  • 0
    Thanks OpOne, but do you have to stand still without starting activity but waiting after you clock locks gps or you can accumulate data while beeing in an activity? Maybe during a swim the GPS data is not continue but there are on and off due water immersion of the hand, so is better a run.
  • 0
    I would suspect that the best thing to do would be to keep it stationary. Back in the day when it usually took a minute or two with the older devices - 305, 310, we were in the habit of leaving them outside while we put shoes on and got ready.
  • 0
    Ok I'll will stay still with GPS… :) and report back
  • 0
    full EPO send by GPS constellation need 20 minutes of uninterrupted receiving of at least one GPS satellite (each satellite send full data of the full constellation, valid for the next 7 days, that's transmitted via the L1 radio signal), so the standing procedure starting or not an activity is the fastest and sure way. everything else could lead to longer update time (running, cycling) or not updating at all (receiving EPO during swim activity is impossible at all). looks like this is a one-shot procedure, next start will use EPO from Garmin systems.
  • 0
    For those still having the original “EPO Expired” issue, I have been having the exact same issue with both my Fenix 5 and Fenix 5+. After some messing around last night, I found that it was Garmin Express responsible for dropping an Expired EPO file on to the watch. If I closed Garmin Express completely (close on the system tray in Win 10), then deleted the EPO.bin files on the watches before ejecting from USB, the watches would initially show “EPO Missing” until after a few syncs with Garmin Connrct Mobile (GCM), at which point I got “EPO Current”. If I hooked up to Garmin Express again, the good EPO file from GCM would get overwritten by a bad EPO file from Express. So, until this is fixed, the key is to always close Express and delete the EPO.bin file before ejecting, every time you’ve hooked up the watch to your PC/Mac. Unsurpringly, my Fenix 5+ was back to it’s normal rapid GPS lock before my run this morning and the GPS track of the Run was better than my last 3 runs with the expired EPO (and yes, I did do a 30 minute static GPS soak with both watches last week, after the GPS 2.23 update). So having a curent EPO.bin file does appear to be important to getting good GPS tracks.

    Whilst the Expired EPO files is obviously a Garmin data servers/Express thing, rather than device software, I’ve reported the issue to the Fenix beta team, so hopefully they can get the appropriate people to fix the bug in the data servers.
  • 0
    For those still having the original “EPO Expired” issue, I have been having the exact same issue with both my Fenix 5 and Fenix 5+. After some messing around last night, I found that it was Garmin Express responsible for dropping an Expired EPO file on to the watch. If I closed Garmin Express completely (close on the system tray in Win 10), then deleted the EPO.bin files on the watches before ejecting from USB, the watches would initially show “EPO Missing” until after a few syncs with Garmin Connrct Mobile (GCM), at which point I got “EPO Current”. If I hooked up to Garmin Express again, the good EPO file from GCM would get overwritten by a bad EPO file from Express. So, until this is fixed, the key is to always close Express and delete the EPO.bin file before ejecting, every time you’ve hooked up the watch to your PC/Mac. Unsurpringly, my Fenix 5+ was back to it’s normal rapid GPS lock before my run this morning and the GPS track of the Run was better than my last 3 runs with the expired EPO (and yes, I did do a 30 minute static GPS soak with both watches last week, after the GPS 2.23 update). So having a curent EPO.bin file does appear to be important to getting good GPS tracks.

    Whilst the Expired EPO files is obviously a Garmin data servers/Express thing, rather than device software, I’ve reported the issue to the Fenix beta team, so hopefully they can get the appropriate people to fix the bug in the data servers.


    Thanks, that worked!
  • Former Member
    0 Former Member
    For those still having the original “EPO Expired” issue, I have been having the exact same issue with both my Fenix 5 and Fenix 5+. After some messing around last night, I found that it was Garmin Express responsible for dropping an Expired EPO file on to the watch. If I closed Garmin Express completely (close on the system tray in Win 10), then deleted the EPO.bin files on the watches before ejecting from USB, the watches would initially show “EPO Missing” until after a few syncs with Garmin Connrct Mobile (GCM), at which point I got “EPO Current”. If I hooked up to Garmin Express again, the good EPO file from GCM would get overwritten by a bad EPO file from Express. So, until this is fixed, the key is to always close Express and delete the EPO.bin file before ejecting, every time you’ve hooked up the watch to your PC/Mac. Unsurpringly, my Fenix 5+ was back to it’s normal rapid GPS lock before my run this morning and the GPS track of the Run was better than my last 3 runs with the expired EPO (and yes, I did do a 30 minute static GPS soak with both watches last week, after the GPS 2.23 update). So having a curent EPO.bin file does appear to be important to getting good GPS tracks.

    Whilst the Expired EPO files is obviously a Garmin data servers/Express thing, rather than device software, I’ve reported the issue to the Fenix beta team, so hopefully they can get the appropriate people to fix the bug in the data servers.


    Thank you, that worked for me exactly as you described! I deleted the epo.bin file, disconnected the watch from Garmin Express/USB and got EPO:Missed message. Then I synchronized the watch just via WiFi (no connection to Smartphone/GCM needed) and got current epo.bin file, EPO:Current message and GPS lock within few seconds. This works only if epo.bin is manualy deleted from the watch before synchronization via WiFi.
  • 0
    Worked fine, delete epo.bin and sync 3 times with GCM now epo ok. Many thanks