Barometer calibration failure on 6.60

Former Member
Former Member

The barometer pressure is stuck at 83886 mbars and not moving at all...and weather is nice...

All calibration methods return a calibration failure message, it was working well on previous release !

Altimeter reading from GPS is OK and yes I have powered off/on.

Any clue?

Thanks,

Top Replies

  • Because it's a hardware issue. I had a replacement twice.

    If you had a replacement already twice, and the third watch failed too, then I would suspect some other problem. It is extrem…

All Replies

  • Former Member
    0 Former Member over 4 years ago

    had the same issue with instinct solar, send it today to service centre for warranty claim... Bought it at august 25,2020. 

  • Oh doh! I thought they solved the problem, with the modell update. I also have a solar since june.

  • Mine failed out the box yesterday.  Same thing with the barometer maxed out and calibration fails.  V11.00

  • Called Garmin; wasn't able to get the senor working and they arranged to get a replacement.

  • It is because corrupted file when updating software. You can ask garmin support to send the file to you and you can download it to your watch via PC. Mine is solved.

  • No. Already tried that. Partial solution. After calibration, it will stuck again. Because it's a hardware issue. I had a replacement twice.

  • Oh. Sorry to hear that. My garmin symptoms was that the barometer stucked on 83886, can't be calibrated, altimeter stucked on a constant value, the thermometer was blank, and when I used it in the activity mode, there's no speed data.

    Garmin support then asked me to send them the files in the watch, they analyzed them, then they sent me a .gcd file to put it in the GARMIN/REMOTE SW folder. By doing so the watch then noticed me that there is a software update available. I updated it and all the sensor functionality come back normally until now. I guess all of these errors happened when there was a software update sent from garmin connect to my watch and somehow the connection was interrupted so some of the file was corrupted, and reupdate the software can't solve this.

  • Because it's a hardware issue. I had a replacement twice.

    If you had a replacement already twice, and the third watch failed too, then I would suspect some other problem. It is extremely improbable that it could happen three times at the same person, while it never happens at thousands of other owners.

    A possible reason could be that the firmware is being repeatedly damaged while being transfered to the watch - for example if you are using a treacherous cable, or have some weird issues with the USB port - could be the hardware, like a different voltage, or spikes of tension, or many USB devices on the same computer, or using a low-quality or underpowered USB hub. It could be also the USB driver, the OS, or some software on the computer messing it up.

    Correctly it should not happen, since there should be at least some basic verification of a checksum on the watch before installing the transferred package, but we do not know whether it is really implemented, and how. I'd rather tell, it may not be the case.

    As a precaution I would try eliminating the most of the mentioned issues you can - trying to connect the watch over a new cable to a different computer than untill now, (preferable a clean new install of an OS on it), and avoiding USB hubs. Having three damaged Instincts cannot be a coincidence.

  • and avoiding USB hubs.

    I believe this is much more important than people think.  I have traced many troublesome performance anomalies back to a USB hub - ANY USB hub.

    HTH