• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 70 replies
  • Answers 1 answer
  • Subscribers 25 subscribers
  • Views 16834 views
  • Users 0 members are here
Options
Related
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

Altimeter negative spiking after 17.50 upgrade, causing gigantic errors

serjmac
over 2 years ago

After the latest 17.50 firmware upgrade, my Instinct seems to gone totally useless in regards to the altimetry.

Until now, it was more or less usable, as a lot of people had reported, it usually record more positive climb that should (maybe between 10% to 20% excess).

But now look at the altimetry record. Those negative continuous spiking caused that about a 890 meters total climb, the device recorded 6600 meters total climb !! That is so insanely wrong.

I have done this route several times, never happened before.

Device was calibrated prior to start, the start altimeter is right at about 1050 meters.

Does anybody know why the barometer has gone this wrong?

But

  • 0 over 2 years ago in reply to 4857931

    thank you! i installed 15.81 and now the altimeter works correctly. you made my isntinct finally usable, great!

  • 0 over 2 years ago in reply to bandit_74

    We have to help each other. Regards

  • 0 over 2 years ago in reply to Garmin - Chris

    Thanks for the reply, Chris.

    I understand that you are a client-facing rep and have little direct control over software development.

    As for Express handling updates differently than Connect, well, please pass along that consistency is a Hallmark of good design. I've noticed several areas where the two apps are different. Perhaps the developers can streamline future efforts by trueing up the API. (I've 20+ years in software dev.)

    I see another from another user that 17.51 is generally available. I'll install that version to test whether the issue is resolved.

    Thanks for your help, apologies for being salty yesterday.

    Mark

  • 0 over 2 years ago

    Good afternoon,

    If you are one of our users who are frequently seeing the altimeter issues noted in this post, please go to the link below to install our latest beta aimed to address this specifically. We would appreciate your feedback on the post below as well.

    https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/instinct/305282/instinct---18-01-public-release-candidate 

  • 0 over 2 years ago in reply to Luke_ODQA

    Nope. Better than 17.50, on par with 16.00.

    I looked back through old activities. April 25 was the last time I had the expected elevation gain. Instinct was on 16.50; prior to that the elevation was unpredictable.

    The numbers are better when I apply Elevation Corrections.

  • 0 over 2 years ago in reply to Luke_ODQA

    Good morning  Luke,

    18.01 is not fixing at all.

    I'm at 350mt where I live. I run calibration and it sets at 347 but after 5 seconds is 1230mt and stays there.

    same as in 17.5, I'm going back to v13.

  • 0 over 2 years ago in reply to Luke_ODQA

    If it helps I will add that I cannot do manual calibration (like in 17.5).
    I am at 350 mt and the altimeter measures 1200.
    if i try manual calibration at 350 it tells me it is not possible because it is out of sensor range.
    instead, if i do the gps calibration it reads 347 and sets it.
    after about 5 seconds it goes up around 1100/1300 and stays there.
    with earlier versions, ie v15 or 16, manual calibration on the other hand works smoothly, like gps calibration, and once set they are maintained.

  • 0 over 2 years ago

    I have this exact same problem. In fact it the reason why I am here--I came here to find out why my altimeter has become essentially nonfunctional. I will run along an almost flat trail  (with maybe a total gain of 100 feet over 5 miles) and the watch is telling me I have gained 5,000 feet. Garmin, please fix this ASAP!

  • 0 over 2 years ago

    How can we roll back the firmware to the version just prior to the defective 17.50?  Or maybe what I should be asking is, why won't Garmin just issue an automatic "update" the rolls back its defective 17.50 to the last functioning version until they have a new version that actually works?  Or is that too much to ask?  To me it would seem the easiest way to fix this, especially for the thousands of users who are less tech savy than the few who will come here and try to figure it out on their own.   The defective 17.50 was mistakenly automatically rolled out to everyone--so until there is a better version that has been confirmed to fix, it would make sense to me to roll it back. And maybe for Garmin to be more careful in vetting firmware before it rolls out new versions.

    BTW, I am one of those "less tech savy" users. I don't normally hang out here, and came across the forum only after spending a lot of time trying to troubleshoot and google up some kind of solution. I didn't update to defective 17.50--this was thrust upon us by Garmin via an automatic "update" and so manually changing firmware versions is not something I am familiar with. But until Garmin fixs this, that does seem to be the only solution. So what is the easiest way to do this? (Apologies if someone already posted this and I missed it.)