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

Elevation since latest update

Is anyone having trouble with elevation readings since the latest software (or chipset) update? Up to version 3.20 everything looked good, but since then (not sure which of the recent updates might have contributed... a few close together) my total ascent and descent are 50-75% more than the true value. 

  • Same, here, did a run today, usually i'm at 130 meter above the sea at my start point and during the run it can goes to 120meter max. But run stats say altitude min -34 and max - 3 ?

    When I turn on the watch the morning or during the days the altimeter can take + 10 or - 10 meter easely.

  • Former Member
    0 Former Member over 4 years ago

    The Sony chipset doesn't have anything to do with it unless you select calibrate using GPS.  This is from Garmin's Support website:

    • Use GPS - This mode will determine your elevation through GPS triangulation. Elevation calibrated through GPS is accurate to +/-400 feet. 

    As you can see, this isn't very accurate at all.  Your best bet is manually calibrate the altimeter to the correct elevation and calibrate the barometer to the correct pressure at the start of your activity.  Then select your barometer watch mode that best fits your situation:

    Watch Mode

    Sets the sensor used in watch mode. The Auto option uses both the altimeter and barometer according to your movement. You can use the Altimeter option when your activity involves changes in altitude, or the Barometer option when your activity does not involve changes in altitude.

    Your previous readings may have been better due to better GPS reception or your current EPO file may need to be updated.  Try what I mentioned above if you haven't done so in the past and I'm certain you'll have more accurate results.  I hope this helps.

  • I recall there being this issue with previous watches (935, ex) after certain updates, which were corrected with subsequent updates, and so while I agree the chipset itself isn’t the issue, something has absolutely changed through the recent spate of updates to the watch. I know it’s correctable having seen this before, but just wanted to make sure this was brought to awareness. I believe it’ll be corrected. Good to see I’m not the only one. 

  • And to make sure I’m clear about the issue I’m having, it’s the accrual of elevation ascent / descent where I’m having the troubles, not the starting elevation value. At the end of runs that would have, say, 100m of elevation gain and loss, I’m getting 150-200 suddenly. Strava corrects it to the right value, the values I used to get prior to the latest updates, and I’ve worn a second watch which corroborates the old sums and Strava’s figures.