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

645 Altimeter short changing my stats....

After have an old Garmin VivoActive 1 for a long long time I decided to upgrade to the 645M. I love it! However one of the things I was most excited about was finally having a barometric altimeter. I find in general that Strava's recalculation it does on watches that do not have a barometric altimeter (like the VivoActive 1) tends to show less altitude than what you actually did. I'm a stats junkie and I wanted a more accurate reading of my elevation profile from mountain bike rides.

So this is where I was excited to be moving to the 645M...well the excitement did not last long. I find the barometric altimeter to be even less accurate than GPS calculated elevation. The altimeter on the 645M shows me getting even less elevation change over a ride...and I know for a fact after using it a few months that the watch consistently short me on what I actually did. Not by just a little bit either, it's not even close to accurate. A local trail ride that I know has a total ascent of about 1100 feet shows as 750 feet on my 645M. That's pretty disappointing. Anyone else notice this with the 645M? It's really the only issue I have with the watch but for me personally it's a HUGE issue.

  • Sawtooth has not been an big issue for me. Last time was in marathon race in first one and half kilometer. Don't know why it happened during thousands of runners started the race.

    The manual GPS calibration works if automatic fails. If manual calibrate don't work, just try it again.

    The problem is that the elevation is mostly 10-20 meters lower when you end your run activity to the same place (or to the same elevation) where you started the activity. This was the issue in my last marathon race as well - start was few meters above sea level and in the finish line, -8 meters. 

    Another problem is that altimeter doesn't show correct altitude change. For example, you run 10-20 meters uphill, but altimeter/elevation shows 2-3 meters only. When you have finished your activity, you may see that the total elevation change is less than half of actual elevation change.

    GPS Elevation data screen also shows wrong elevation during the run activity.

  • Possible workaround when the altimeter does not change although it should: During the run activity when you notice that the elevation does not change anymore (for me usually after few kilometers run), stop running, press stop, wait 20-30 seconds or so, press start and continue running. Now you should see a big difference i.e. the altimeter works nicely again and total elevation is more or less correct after your activity has finished.

  • Hi, did you ever resolve this issue. My brother got a 645 Music and the exact same thing is happening. For lack of better description the barometric height is changing way slower that what he traverserses. After coming to a standstill after an uphill or downhill ride the barometric altitude takes MINUTES to reach the real level. When plotting height vs. distance it looks like he jumped up to 100 ft up or down while being stationary.

    This makes the entire height plot wrong. He got a brand new warranty replacement and that watch does exactly the same thing out of the box. At a complete loss

  • Nope...I just started always using the "Correct Elevation" feature in Strava after every ride. I've come to accept that the altimeter is a piece of crap.

  • That’s disappointing. My 945 is spot-on and my brothers 645 does the same thing. He’s moving back to Polar. I had a long discussion with customer support and they “don’t know of anything”. 

  • Which Firmware do you use, the latest one?

  • I always let it update to the latest.

  • Agree 100%. Correct Elevation is the only way I've been able to get accurate accumulated elevation for a ride. Soaking in soapy water helped *a little* but not to my satisfaction.

  • I can only confirm this. The altimeter is too slow for bike rides or skiing. Works fine for hikes for example because your pace is slow and the altimeter can keep up. I already had one unit replaced under warranty, but this one is the same. I'd like to know if the sensor is the same they use on the 945 or Fenix series or indeed it is a different one, where would I get that info?

  • I've come to realize the same thing after also using it to track hikes more whereas I primarily use it while mountain biking. Hiking the altimeter keeps accurate ascent and descent. Mountain biking I always get shorted.