Just upgraded to 5x Plus Ti DLC, elevation seems off

Former Member
Former Member
I just got my 5x DLC Ti (had a 5x previously) and completed a couple group rides with it and a wahoo bolt. The elevation nunbers are normally a little off from my 5x and wahoo, but not drastically.

With the new one on a 40 mile ride my elevation is lower than all of my riding group by over 600ft?? I calibrated the altimeter and barometer just a couple days back, but that should not matter because it's just calculating the increase and decrease regardless if starting figure, right?

So far, really loving this watch, Garmin pay and music are incredible!

??????
  • I just got my 5x DLC Ti (had a 5x previously) and completed a couple group rides with it and a wahoo bolt. The elevation nunbers are normally a little off from my 5x and wahoo, but not drastically.

    With the new one on a 40 mile ride my elevation is lower than all of my riding group by over 600ft?? I calibrated the altimeter and barometer just a couple days back, but that should not matter because it's just calculating the increase and decrease regardless if starting figure, right?

    So far, really loving this watch, Garmin pay and music are incredible!

    ??????


    Have you tried latest beta?
  • Former Member
    0 Former Member over 6 years ago
    Have you tried latest beta?


    No sir. This is the only problem I have found that is impacting me currently, and after running Beta on my 1030 Edge and Fenix 5x (Org) I decided on this one to just wait for release code. I did read through the beta notes after your response and am hopeful that the 4.0 release will resolve the issue I am seeing. Have a great day!
  • I did about 30 skydives wuth the 5x Plus and the altimeter readings have been desastrous. Using the Jumpmaster app as an altitude indicator would have killed me every single time. On the way up (in an unpressurized aircraft/inside pressure the same as outside pressure) the watch lost about 600m on the climb to 1000m. After that, it tracked the climb correctly (having this 600m offset). After the jump under open canopy at 700m, the watch still showed 2000+ m and on the ground still was at 1500m. Comparrison was made with 4 barometric altimeters (1 analog, 3 digital) who all showed the same. (Even my old Fenix 3 worked fine in this regard).
    This failure will also have an effect on the O2 readings as they are linked to altitude and as such, this feature was also totally worthless.

    After a couple of emails, I received an RMA from Garmin and send them the watch for exchange.
    Next skydiving will happen in September with hopefully better outcome.

    (Kindly refrain from telling me about different settings for altimeter vs barometer ot thing like "not made for skydiving"/only for experienced skydivers, ... -- I'm a pilot and a skydiver with 2000+ jumps bith military and civil -- I know how these things should work and tested with all logical and illogical settings)
  • I did about 30 skydives wuth the 5x Plus and the altimeter readings have been desastrous.


    Which software version were you on? Any production software on the Fenix 5+ series earlier than ver 4.20 contained the same elevation ‘over-smoothing’ bug that the Fenix 5 series and Forerunner 935 did until very recently (Fixed on Fenix 5 ver 10.00 and 935 ver 10.10). The easiest way to describe the bug is with a picture. The plot attached is a MTB ride I did with a friend last Friday (17 August); his watch was on the older 935 series sw 9.70 with the bug and my Fenix 5+ on sw 4.20 containing the bug fix. There is approximately 160m offset as the 935 was not calibrated at the start (my 5+ has the correct altitudes), but it’s the shape of the graph that’s important. My 5+ is picking up all the ups and downs in granular detail, whereas the 935 is considerably over-smoothing the ascent/descents and was also under reporting total ascent/descent. My 5+ used to have similarly over-smoothed elevation plots until one of the recent beta releases contained a fix (that is now in production 4.20). I can only imagine this over-smoothing bug is amplified to an even greater error with the rapid ascent to descent involved with sky diving. Whilst Garmin have replaced your hardware, it’s likely it is the software that was causing the issue.ciq.forums.garmin.com/.../1391997.jpg
  • Which software version were you on? ...... Whilst Garmin have replaced your hardware, it’s likely it is the software that was causing the issue.


    The jumps where prior to ver 4.2. From the beginning I assumed it to be a SW bug but Garmin insisted on, "that it can't be a SW bug" and as such offered to replace the unit. So the next jumps will be on the then latest SW with a new watch. Depending on my willingness to do more tests, I might switch the SW version between jumps to see, if/when the issue (if SW linked) got resolved. This is, of course, if it has been resolved for the rapid changes occuring in skydiving. Let's hope for the best. I'll keep you posted.

  • UPDATE: 21 jumps done with 4.65 BETA and the altimeter readings are finally OK. Both on ascent in the plane and descent while freefalling/under canopy the watch matches the altitude of my comparisson devices (1 analog, 3 digital altimeters. All based on barometric pressure).
    Watch "lacks" behind about 20/30 m but this can be due to my other digital ones might have a faster update rate. Yet, this is unimportand as I'm "working" with the thousand and hundret digits, not the tens.
    On the ground it is alwys back to 0. Just on 2 jumps, after stopping the activity, altimeter value on the activity page dropped to about "-180m". It remained however at "0" in the calibration section. I couldn't reliably repeat this behaviour - so not sure the reason behind.
    Yet again, for me, watch is now reliable for jumping (and no - it is not and will never be the only device I rely on).