Altimeter Calibration Issue
-
I’d add a firmware version to this, but it’s been present through the last 3 updates so…here we go.
At seeming random cause and timing, the altimeter will refuse to let me calibrate it. I know my home elevation down to sub-foot accuracy (long story, son of a surveyor
), so I calibrate the watch if I ever notice it too off, because I use the barometer readings for weather forecasting constantly. At random times, the Run will revert back to its erroneous reading seconds after calibrating…and will continue to do so until I either record a GNSS based activity, or restart the watch.What’s odd is the altimeter isn’t stuck (locked on a elevation reading), its just offset and I can’t calibrate that. If I change in elevation when its doing that (which is NOT all the time), it will track the change correctly, just not give the right actual reading. What I can’t figure out is what causes it—it’s started this immediately after tracking an activity sometimes, started it overnight while I’m asleep, started it after washing the watch, and sometimes randomly after none of these things. And it’s persisted intermittently through 3 firmware versions, and a hard reset…
-
Update for Firmware 3.25.18–the issue is still there. For specifics this time, it occurred after an outdoor activity (walk in this case, which I rarely record) and is locked at an elevation EXACTLY 25 feet above my actual elevation.
-
@JebClydeNC
25 feet is not that much, and probably well in the expected tolerancy of fusedalti calibration. GNSS elevation is not perfect.
Activities are processing fusedalti calibration and might explain your behaviour.
