I have had issues with the elevation readings all summer long. I consistently am missing at least 50%(and usually more) of my total elevation gain while cycling or mountain biking. I usually end up enabling the Elevation Correction. I have been in contact with support. On the first call, they told me to upgrade to the beta software and clean the sensor. I did both, and it still read erroneously. On the next call, I was instructed to default it back to factory settings and try again. After doing this, repairing all my sensors, etc, the elevation gain was still off by at least 50%. On the next call, they agreed to replace it under warranty. I recieved the new device, set it up, and it is doing the EXACT SAME THING. I now believe there is a software bug with 9.20. Does anyone else experience this? I can't believe I am the only one who has this issue, on 2 completely separate devices. Anyone from Garmin Support on here that can address this? This is a 600 dollar device and I believe it should work correctly. I hate having to use the USGS tables for elevation as they are highly inaccurate when mountain biking.
Another hike yesterday where my older VA3 was failing miserably again worked properly. Very slight error between start and stop elevation that can be chalked up to when the GPS dinged "ready" after I already started. Hill peaks were correct also, where the VA3 would be smoothed off with a great deal of error. I can only assume the bug in the Fenix series is the same as the one in the VA3 since I have not owned the F5S long enough to have the bug in it.
Comparing a elevation plot from my F1 (pretty much perfect) to an elevation plot from my F5X (pretty much rubbish) for 12 laps on exactly the same chair lift I have come to the conclusion that the F5X is only usefull as a fishing sinker. refer attached pictures.ciq.forums.garmin.com/.../1387077.jpg
Comparing a elevation plot from my F1 (pretty much perfect) to an elevation plot from my F5X (pretty much rubbish) for 12 laps on exactly the same chair lift I have come to the conclusion that the F5X is only usefull as a fishing sinker. refer attached pictures.
Thanks interesting comparaison indeed! Just one question Wander_ What was the firmware version on your F5X at the time of this comparaison? 9.2 or 10.5x? Thank you for your return.
ps: i also just read that for elevation it might help to lock the barometer in altimeter mode, in the barometer option, under wacth mode > Altimeter , rather than being by default in auto, cause he will try to understan if changes in pressure occur cause of a storm coming or because you gain in altitude. This can mess up the elevation. So if you dont care about weather storm alert, put in on OFF and lock the barometer watch mode on altimeter.
Comparing a elevation plot from my F1 (pretty much perfect) to an elevation plot from my F5X (pretty much rubbish) for 12 laps on exactly the same chair lift I have come to the conclusion that the F5X is only usefull as a fishing sinker. refer attached pictures.
Yeah, that is pretty bad. Please do try the 10.0 update or the Beta version if you haven't yet. It is working very well with me, and I am quite pleased.
i wonder why so many people are reporting, that the elevation problem is fixed with beta 10.51!? for me it is the same useless joke as before. i can't believe that garmin releases so much trash and is not able to fix at least the basic things why one bought a fenix.
yesterday i did a small mountain bike tour - here are the results for the elevation gain:
fenix 5: 201 m garmin connect online with correction: 316 m trainerroad: 358 m runtastic: 343 m
the fenix is so way off, that i simply can't believe it.
i wonder why so many people are reporting, that the elevation problem is fixed with beta 10.51!? for me it is the same useless joke as before. i can't believe that garmin releases so much trash and is not able to fix at least the basic things why one bought a fenix.
yesterday i did a small mountain bike tour - here are the results for the elevation gain:
fenix 5: 201 m garmin connect online with correction: 316 m trainerroad: 358 m runtastic: 343 m
the fenix is so way off, that i simply can't believe it.
Mine has been working pretty good since updating. I have done a few mtb rides, and couple road rides. yesterday I showed approx 2300' elevation. When I corrected, it showed 2600'. I am attributing the 300' error to be associated with temperature change as it got about 20F warmer from the start of my ride to the end. This is in stark contrast to when I did not have the update, I was missing AT LEAST 50% of my elevation. I assume my elevation would have shown about 1300' if I did not have the update. Sucks that it is not working for you. Have you tried manually calibrating prior to the start of the activity?
To add to my last post, It was stated that Garmin recommends recalibrating every hour. That is not always possible, especially if one is participating in a race. We cannot be expected to stop, recalibrate, and continue riding. I would like to see an enhancement where the watch would recalibrate itself automatically while in an activity, every hour. For the price of this watch, I do not think that would be too much to ask for. My longest activity this year was 12 hours and I cannot imagine having to recalibrate 12 times just so I can see accurate data. This should not be difficult, as the watch could get a quick snapshot of the GPS, barometric pressure etc. and base the calibration on those #'s.
Bandit, I would check again the version on your device software again. I am having excellent results that closely follow map elevations. However, I am doing relatively slower hikes vs. Fast rides. ????
because i do not trust the "auto calibration" i always do a manual calibration before i start the activity. first i calibrate manually and then i wait a little while after the gps fix was successful.
and yes, i am sure that i have the beta 10.51 installed (incl. all the other files like gps 2.2). perhaps the elevation is better when hiking. garmin seems to concentrate on walking activities these days. perhaps this is the only way to sort out all their big software problems and fix them step by step with trial and error.
That is really far off. I don't understand how a watch that touts itself for outdoor adventure could have these sorts of fundamental navigation issues for some folks. I will finally get my but onto my bike this weekend and take a ride around the block. My "block" is a relative nightmare for old farts like me:
Hopefully I don't drop dead. I have not had the luxury of time with a busy family this summer to ride much. It is part of the reason I got this darned device, to motivate me to get out.
