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

Wrong total ascent

I have recently got an Edge 520 and I am already owner of a Fenix 3 for over 2 years now.

Some time ago during a MTB tour I had to get a lift to reach one of the summit in my tour, I paused both devices so that to exclude this leg from the total distance and total ascent, but at the end of the tour the Fenix was showing the correct total climbed meter,(without cable-car ascent) while the 520 took into account also these meters with cable car, I am sure the device was paused because from the altitude graph on GC you could see a vertical line for this.

Anyone else experienced this? Is there anything I can do to avoid this?

Moreover I also noticed that in the field of % gradient, the updating of this field when facing a steep course is very slow, the Fenix already shows 9% and the 520 is still working around 1.3-1.4%.
In this case at the end of the course the total altitude is correct, so I assume it is only a software problem but anyone else seen that?

Thank you in advance for your precious help!

Top Replies

texmurphy over 7 years ago +1

Edge 520 v9.1 will add paused elevation caused by barometric pressure change (say during a cafe break while auto-paused or even at a long traffic light).

All Replies

0 karersee over 7 years ago

Up!
any clue?

0 PeterK_55 over 7 years ago

Hi,

I'm not sure about the ascent error, but I've found that the start/stop button can be very sensitive to accidental touch or spurious operation. I fitted a silicone case and haven't had any more problem with that.

I've experienced the sluggish % gradient updating when the data recording interval was set to Smart, but it behaves correctly when 1 sec recording is used, so your settings could be the reason for it.

0 karersee over 7 years ago

Thank you for your reply.
It is definitely not an accidental touch of the start button causing the problem, it is something wrong in the software!
btw, I have too the silicon cover and like it very much.
very interesting your possible solution about gradient update, I will check the setting on my device and give it a try!

0 Former Member over 7 years ago

I checked this out riding up the gondola while skiing and think it is a bug with the 520. While paused it does not accumulate elevation but when unpaused it adds the total elevation change that occurred while it was paused. I'm fairly certain the other Edge models I've had worked correctly and did not add the paused time elevation. I don't know if the 520 has always worked this way or if the bug was introduced with an update.

0 texmurphy over 7 years ago

Edge 520 v9.1 will add paused elevation caused by barometric pressure change (say during a cafe break while auto-paused or even at a long traffic light).

0 JuergMeister over 6 years ago

I have this very same issue - and I've been looking for a solution for over a year now. My friend has an Edge 1000 and he has the same issue. I used to have an Edge 305 and the issue did not occur there.
There has got to be a solution for this by now.
Does anyone have an update or a workaround for this annoying issue?