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

Elevation 'stuck' during run so no Ascent data Software version 17.26

erikvdg
over 1 year ago

on some runs the elevation data does not update during the run. I have autocalibrate on, but today I even calibrated the altitude just before the run to make sure. Alas, it got stuck at that altitude and therefore again no elevation data. Altimeter, GPS and barometer on the watch work fine. I have not found any obvious similarity between runs where this happens. I did NOT happen until about 2 months ago (I should check this )
Obviously irritating as I run plenty of hilly tracks

Does anyone else have this problem? 

  • 0 over 1 year ago

    New 255, software version 18.23. Second run, same problem, elevation data stuck UNTIL the very last part of the run when I briefly stopped to talk. I think this is a bug. 

    And my temperature data has disappeared. This new 255 does not log the temperature???? 

  • 0 over 1 year ago in reply to erikvdg

    Check the ABC glance, altimeter, altimeter settings, sensor mode

    Is it in "auto", "barometer only", or "altimeter only"?

    Mine is in auto and seems to do well following my elevation on hilly walks and even just going upstairs/downstairs at home with the altimeter showing on my watchface.

  • 0 over 1 year ago in reply to 6125703

    Hi, thanks for that but these settings are indeed also mine. The problem is intermittent (just like my previous 255 actually) Very first run with this one was fine, perfectly following the profile (177m total ascent on the run) second run flatlining until almost the end of the run when it suddenly picked up. GPS signal is fine here, independent Strava on my phone gives same (and correct) distance.... 

    I do suspect a calibration bug...

    I am also puzzled by the loss of temperature data. 

    The temperature sensor works but no data is displayed in Connect