Garmin Fenix 6 dead zone on Mt. Lady Washington
Forum rules
- This is a mountaineering forum, so please keep your posts on-topic. Posts do not all have to be related to the 14ers but should at least be mountaineering-related.
- Personal attacks and confrontational behavior will result in removal from the forum at the discretion of the administrators.
- Do not use this forum to advertise, sell photos or other products or promote a commercial website.
- Posts will be removed at the discretion of the site administrator or moderator(s), including: Troll posts, posts pushing political views or religious beliefs, and posts with the purpose of instigating conflict within the forum.
-
- Posts: 139
- Joined: 7/26/2004
- 14ers: 58
- 13ers: 59
- Trip Reports (2)
Garmin Fenix 6 dead zone on Mt. Lady Washington
The last three times that I've climbed Mt. Lady Washington my Garmin Fenix 6 has quit calculating my elevation gain at about 2,000K. The time and distance seem to function fine and match All Trails & Gaia that I also run, but for some reason elevation goes wonky. I've had my Fenix 6 for 6-7 year and used it 500+ times in Colorado, the Western US, and overseas where it's worked flawlessly, but for some reason it protests with Mt. Lady Washington. Very odd. Am I missing a update or something?
-
- Posts: 3368
- Joined: 12/5/2007
- 14ers: 58
- 13ers: 25
- Trip Reports (69)
Re: Garmin Fenix 6 dead zone on Mt. Lady Washington
Main instances when I had a GPS or GPS watch not work or throw off wonky measurements were when it wasn't calibrated properly before starting or the sky was obscured by cover or canyon walls/steep cliffs, but given your experience with it, assume thats not the case.
I've had compass measurements thrown off when ground I was on had more iron content, but not impacting altitude.
I've had compass measurements thrown off when ground I was on had more iron content, but not impacting altitude.
Re: Garmin Fenix 6 dead zone on Mt. Lady Washington
I had a lot of issues with the Garmin Fenix 6S - so much so that Garmin replaced it 3 times before eventually giving up and upgrading me to a 7S (with no further issues). I’ve since started paying attention to GPX tracks of friends with the 6 and noticed the same problem. It seems to ‘lose’ you - especially on the uphill, and not in places you’d expect, like heavily forested areas or couloirs. This would occur even on wide open slopes under clear skies. This has happened on multiple occasions to my partner who is running the 6, most recently when we did Taylor on Saturday. His elevation stopped calculating while ascending and showed about 1,000 feet less gain than mine. It eventually catches up, but he’s left with a straight line GPX track in the problem section and less mileage. Not sure if this is what you’re experiencing and no idea what causes it, but I suspect it may be a systemic issue with the 6.
-
- Posts: 139
- Joined: 7/26/2004
- 14ers: 58
- 13ers: 59
- Trip Reports (2)
Re: Garmin Fenix 6 dead zone on Mt. Lady Washington
Thank you! Your experience with the Garmin 6 sounds very similar to what happened to me. My Garmin also drops me in clear wide open areas, and only on MLW. It sounds systemic like you mentioned.Chipmunk wrote: ↑Mon May 12, 2025 10:12 pm I had a lot of issues with the Garmin Fenix 6S - so much so that Garmin replaced it 3 times before eventually giving up and upgrading me to a 7S (with no further issues). I’ve since started paying attention to GPX tracks of friends with the 6 and noticed the same problem. It seems to ‘lose’ you - especially on the uphill, and not in places you’d expect, like heavily forested areas or couloirs. This would occur even on wide open slopes under clear skies. This has happened on multiple occasions to my partner who is running the 6, most recently when we did Taylor on Saturday. His elevation stopped calculating while ascending and showed about 1,000 feet less gain than mine. It eventually catches up, but he’s left with a straight line GPX track in the problem section and less mileage. Not sure if this is what you’re experiencing and no idea what causes it, but I suspect it may be a systemic issue with the 6.