Bug or not? Please share your ascent/descent dates

Folks, I have already started a thread because my Fenix shows completely wrong "total ascent" and "descent". In the meantime I am in contact with the support and the beta-team. Unfortunately Garmin has not considered this behavior as a bug yet. And therefore they aren´t working on this.

That´s why I want you to share your dates concerning "total ascent" and "descent" (ideally compared with other watches that measured in parallel and/or the dates which you get on Basecamp when you upload the gpx-file that the Fenix has recorded. And please add if you have Fenix 5 oder 5x because it seems that the 5x doesn´t have this bug.

I would appreciate if you join this thread because I can figure out if only my watch has a problem or if there is bug in the firmeware ...and if so this thread can/should accelerate Garmins activities.
_______________________________________
These are some of my dates:

Fenix 5: ascent 722 m, descent 584 m
Edge 500: ascent 792 m
Fenix 5-gpx-track on Basecamp: ascent 798 m, descent 780 m


Fenix 5: ascent 783 m, descent 815 m
Edge 500: ascent 890 m, descent 879 m
Fenix 5-gpx-track on Basecamp: ascent 869 m, descent 891 m


Fenix 5: ascent 716 m, descent 638 m
Fenix 5-gpx-track on Basecamp: ascent 748 m, descent 735 m


Fenix 5: ascent 513 m
Fenix 5-gpx-track on Basecamp: ascent 587 hm


Fenix 5: ascent 1347 m, descent 870 m
Edge 500: ascent 1423
Fenix 5-gpx-track on Basecamp: ascent 1402 m, descent 1383 m
  • Folks, I am respectively was in contact with both the beta and the support team. I have recorded a lot of MTB-rides with the fenix and the Edge 500. And the problem that I have described above still exists. I asked the support team if it can also be a hardware problem because it seems that I am the only one with this problem. They think that it?s a software problem and a watch replacement doesn?t make sense.

    Unfortunately I haven?t got any dates of other users. Are there no other Fenix-users that do cycling or mountainbiking with some ascent/descent? Do you all have ascent/descent dates that are correct?

    Please share your dates. If am the only one I would increase the pressure concerning watch replacement. So don?t be lazy, check your dates (starting and ending elevation ...and difference; ascent and descent ...and difference). Thank you for your help.
  • I have a new sheet with ascent-descent-comparison between Fenix 5 and Edge 500.

    Watch the weird dates of the Fenix 5 compared with the Edge 500. It is pretty resistant. Either total ascent or descent is pretty wrong on the Fenix 5 (all dates in the sheet account of course the difference of starting and ending elevation correctly).

    Folks, I will return my watch because I cannot imagine that this is software related ...as long no one else in this forum confirms that he has the same problem. Am I really the only one with this problem? PLEAS HELP !

    ciq.forums.garmin.com/.../1264526.png
  • Former Member
    0 Former Member over 7 years ago
    These are the ascent data related to my latest workouts (cycling):

    [TABLE="cellpadding: 0, cellspacing: 0"]
    [TR]
    [TD]Edge 520[/TD]
    [TD]FENIX 5[/TD]
    [/TR]
    [TR]
    [TD][/TD]
    [TD] [/TD]
    [/TR]
    [TR]
    [TD]1059[/TD]
    [TD]1057[/TD]
    [/TR]
    [TR]
    [TD]707[/TD]
    [TD]678[/TD]
    [/TR]
    [TR]
    [TD]585[/TD]
    [TD]582[/TD]
    [/TR]
    [TR]
    [TD]1277[/TD]
    [TD]1256[/TD]
    [/TR]
    [TR]
    [TD]1379[/TD]
    [TD]1357[/TD]
    [/TR]
    [TR]
    [TD]1241[/TD]
    [TD]1247[/TD]
    [/TR]
    [TR]
    [TD]660[/TD]
    [TD]671[/TD]
    [/TR]
    [TR]
    [TD]614[/TD]
    [TD]593[/TD]
    [/TR]
    [TR]
    [TD]582[/TD]
    [TD]589[/TD]
    [/TR]
    [TR]
    [TD]1034[/TD]
    [TD]1025[/TD]
    [/TR]
    [TR]
    [TD]500[/TD]
    [TD]497[/TD]
    [/TR]
    [TR]
    [TD]1540[/TD]
    [TD]1520[/TD]
    [/TR]
    [TR]
    [TD]1259[/TD]
    [TD]1266[/TD]
    [/TR]
    [TR]
    [TD]1965[/TD]
    [TD]1963[/TD]
    [/TR]
    [/TABLE]

  • Toady on a ring trail of 13,5 km i found this values on garmin connect:

    elevation gained: 594 m
    elevation lost: 659 m

    difference = 65 m



  • @vonzipper: the difference of ascent-descent has to include the difference of starting and ending elevation (which can change). Is that accounted?

    and: which firmware version?
  • These are the ascent data related to my latest workouts (cycling):



    @p.merzi: which firmware version?
  • @vonzipper: and: which firmware version?


    6.0 (d376ccb)
  • 6.0 (d376ccb)


    And have you accounted the difference of starting and ending elevation in your difference of ascent-descent? Which means for example: if you start at 100, go up to 500 (ascent should be 400) and go back to your starting point which is (on the Fenix) in the meantime at 120, descent with 380 would be correct.
  • starting elevation was 805 m
    finish elevation was 830 m

    considering that start and finish points match (it was a ring tour), fenix error was 25 mt.
    the others 65-25 = 40 meters i don’t know where do they come from.