I've got an edge520 since Xmas (updated at 10.0 version of firmware) and I think there is an issue with altitude because the device (with both with GPS and GPS+Glonass) shows an altitude of 50-60 m less than real...
When you set a starting altitude (or when you start from a location saved in your device) what do you see on garmin connect or strava as starting altitude? The one you set or something about +/- 10m?
I usually set my altitude at 261m but every time my edge shows me 261 but the recorded is 252 or 266 ore other values... It seems that barometric sensor doesn't read starting altitude properly...
This is definitely my last Garmin unit... Fortunately the competition is providing some nice alternatives.
I'm on 12.10 and like many others I have huge problems with grade and altitude. As soon as there's some tree coverage the grade resets to 0%. It is beyond my comprehension why they changed the setup from barometric reading to GPS for the grade. VAM is working correctly and without issues.
The icing on the cake is that for today's ride all altitudes are 300m low in Garmin Connect even though they showed correctly on the 520...
All of this worked perfectly well until firmware 9.
This is definitely my last Garmin unit... Fortunately the competition is providing some nice alternatives.
I'm on 12.10 and like many others I have huge problems with grade and altitude. As soon as there's some tree coverage the grade resets to 0%. It is beyond my comprehension why they changed the setup from barometric reading to GPS for the grade. VAM is working correctly and without issues.
The icing on the cake is that for today's ride all altitudes are 300m low in Garmin Connect even though they showed correctly on the 520...
All of this worked perfectly well until firmware 9.
Sad really...
Hi
I had some bad results on recorded altitude data with 10, 11, 11.10 FW...from 12.10 on everything seems ok (I mean recorded data by barometric sensor) and now starting altitude on GC is what I set. What I see wrong is what it's displayed on screen (GPS related). Anyway, I can offset altitude on your fit file if you want...
that's because Edge 25 and Samsung are GPS based while edge 520 has barometric altimeter. The correct profile is the one recorded by edge 520
In January I purchased a 520 as a temporary computer before moving to some other brand. I have noticed that the total elevation gained during a ride with 520 is much lower than with my already retired 510. The difference is over 30 %. The difference is not weather related: I know that the elevation of 510/520 is not reliable during heavy rain, for example.
In January I purchased a 520 as a temporary computer before moving to some other brand. I have noticed that the total elevation gained during a ride with 520 is much lower than with my already retired 510. The difference is over 30 %. The difference is not weather related: I know that the elevation of 510/520 is not reliable during heavy rain, for example.
Do you know if the old 510 was also GPS based?
don't forget that total elevation is not based on total sum of positive variation recorded during a ride but is something adjusted by an algorithm (for example the device sum up only variations of +/- 1m or something similar). If you could open a .fit file recorded by your devices you'll be able to understand what I mean...
In January I purchased a 520 as a temporary computer before moving to some other brand. I have noticed that the total elevation gained during a ride with 520 is much lower than with my already retired 510. The difference is over 30 %. The difference is not weather related: I know that the elevation of 510/520 is not reliable during heavy rain, for example.
I go on group rides in the Sierra Nevadas, ranging from 1000 feet to 15,000 feet of climbing. There are a lot of devices: - 500 (barometric altimeter) - 510 (barometric altimeter) - 520 (barometric altimeter) - 800 (barometric altimeter) - 810 (barometric altimeter) - 1000 (barometric altimeter) - iPhone Strava app (GPS) - Android Strava app (GPS)
When comparing my climbing against other riders, I see some variation, typically 5-10% but it can be as large as 20-25% between highest and lowest. My 520 generally agrees with RideWithGPS on my iPhone, and with other cyclists using various devices. When I have large difference versus other riders, it is always on a Northern California winter morning when the ride starts in mid to upper 30 degrees, and ends with temps in 50s. At least with my 520, it is generally accurate except in the winter when there is a wide temperature range during the ride. I have a friend with a 1000 that is rock steady, and another friend with 1000 that consistently is 10-20% below other devices on the same ride.
