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

Edge 520 GPS and Altimeter Accuracy

Former Member
Former Member
I have been using the 520 since September and have been patiently waiting for and installing the updates (including the latest one) in hopes that the bugs will get worked out and it will function the way it really should have out of the box.

First. GPS accuracy is horrible. Sometimes more than 100 feet off in any direction. This seems pretty insane considering that one of the big selling points on the 520 was the strava integration. 100 feet off on a segment start or finish is kind of a big deal. A good example of this would be the attached fit file and linked strava ride. While riding through Point Defiance Park I am shown to be nowhere near the road and consequently did not ride any of the 5 or so segments that I should have passed through. This ride was done on a gorgeous blue sky day during the winter where there is actually less of a tree canopy. Not that I think that should matter because I rode through this park more than a 100 times with a 510 and never had this issue. I would think that the 520 (being the newer model) would not be less accurate. Some other rides I have done through this park with the 520 actually show me in the water.

https://www.strava.com/activities/467738049

Second. The Altimeter is completely useless and often shows me riding below sea level. I know that you can correct the elevation with map data but that would require that the gps data was somewhat close to accurate. And why should I have to correct elevation data from a barometric altimeter anyway?

Is anyone else having similar issues that they have been able to correct on their own?
  • Former Member
    0 Former Member over 8 years ago
    Chronic problems with accuracy

    I've been having chronic accuracy issues with Garmin units. I've gone through 2 E500's and now on my second E520. All have been replaced by Garmin under warranty, but it's just getting ridiculous to keep having to call and complain and then get them to replace yet another unit. I've tried various settings to no avail. My riding buddies don't appear to be having the same issues...maybe I'm just cursed!

    I'm also having issues with the units dropping the heart rate after an hour or two of riding. I'm using the strap that came with the E500. I've replaced the battery and tried the current drain trick. Nothing has worked.

    Some examples of my tracking issues below. I love the form function of this little unit, but the accuracy is just horrible!







  • I have been using the 520 since September and have been patiently waiting for and installing the updates (including the latest one) in hopes that the bugs will get worked out and it will function the way it really should have out of the box.

    First. GPS accuracy is horrible. Sometimes more than 100 feet off in any direction. This seems pretty insane considering that one of the big selling points on the 520 was the strava integration. 100 feet off on a segment start or finish is kind of a big deal. A good example of this would be the attached fit file and linked strava ride. While riding through Point Defiance Park I am shown to be nowhere near the road and consequently did not ride any of the 5 or so segments that I should have passed through. This ride was done on a gorgeous blue sky day during the winter where there is actually less of a tree canopy. Not that I think that should matter because I rode through this park more than a 100 times with a 510 and never had this issue. I would think that the 520 (being the newer model) would not be less accurate. Some other rides I have done through this park with the 520 actually show me in the water.


    Just to remove one variable, which setting do you have in your activity profile for GPS? eg GPS + GLONASS or just GPS?
  • Former Member
    0 Former Member over 8 years ago
    Hi All! I`m new to Garmin community as recently bought the 520.

    I`m also struggling to get reliable gps tracking by the unit. Now it is my second unit after replacement under warranty. Mostly it is spot on (especially when sky is clear). Still there are times where 520 misses the track completely or shifts it around the corners.
    Bad weather (cloudy) and uphills with nearby trees/forest mostly affects the device. My old smartphone has never missed in such manner. Thanks to ride with friends I do have tracks from other Garmin devices and smartphones to compare at same time and conditions.

    Attaching the screenshots with issues on second unit:

    http://szosa.org/uploads/monthly_05_2016/post-13275-0-23799900-1462905282.jpg
    ^^ Cloudy and foggy morning with GPS+Glonass. Off segment completely. First unit did same thing on this uphill on cloudy sky (edge 500 did fine).

    http://szosa.org/uploads/monthly_05_2016/post-13275-0-25240400-1463168072.jpg
    ^^ light rain afternoon, GPS only after several Master Reset procedures/updates and leaving unit on for 11h to update its satellite cache.
  • I've borrowed an edge 1000 to check against the 520 for a couple of weeks. Total ascent is always very close at the end between the two, but the 520 gradient lags a lot more.

    One thing I've noticed every ride though is that when stopped both have an a gps accuracy around 10 feet, but when riding the 520 is often at 30 feet accuracy while the 1000 is still around 9-11 feet. If I stop again the 520 then comes back down to same as the 1000, eg 10 feet.

    Maybe this is why people are getting inaccurate tracks?
  • Former Member
    0 Former Member over 8 years ago
    GPS accuracy

    I've tracked the same thing on my 520. Sitting still the accuracy displayed is 10 feet. As I ride it increases to as high as 40+ feet. Not really any better than the Edge 500 I had previously. So the inclusion of Glonass seems to provide no benefit. But then again, I believe every unit I've had has been defective, including my current 520 which I will request to be replaced...yet again...
  • Former Member
    0 Former Member over 8 years ago
    GPS accuracy

    I've noticed the same thing. My 520 displays accuracy to 10 when sitting still. When I ride it increases to 40+ feet. No better than my 500. So I guess the inclusion of Glonass did nothing for accuracy. Although, I believe every unit I've had has been defective. I'll be requesting this one to be replaced as well...again...
  • Former Member
    0 Former Member over 8 years ago
    Can confirm the observed accuracy fluctuations. Enabled the accuracy data field and rode with it on main screen. Very bad cold start (1min+) to get the "gps ready" and then, next 500-600m track is way out of road. Then it increased in accurady up to 5-7meters and there the track is ok. There are part where accuracy stayed at 8-10meters and can be seen with track flowing from side to side. Used gps-only.

    https://www.strava.com/activities/578078546
  • 520 elevation jumps by 50,000 feet



    My 520 recently (few months ago) developed severe altitude sickness. It logs jumps of 25,000 to 50,000 in elevation, but otherwise logs nothing. It used to work great. Anyone else experience this? If you look at the data on strava is seems to limit the jumps to around 5200 feet.

    Trying to attach an image from garminconnect
  • Former Member
    0 Former Member over 8 years ago
    it looks like a faulty pressure sensor. You could try reinstalling the firmware but I think it is the pressure sensor. Call support.
  • I'm having exactly the same issue as GJWOLF22! Have you had any luck finding a resolution?