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

Auto Calibrate Elevation to Location? Baro Altimeter?

Here's another one:

On my Edge 800 it is possible to have the Elevation Auto Calibrate to my starting location. I saved the location, and every time I start a ride from that location I get the pop-up that says the Elevation has Auto Calibrated to that location.

I can not find the same feature on my Edge 820. As a workaround, before starting a ride I go to Navigation>Adjust Elevation and set the elevation immediately before a ride. It is a bit cumbersome, and doeasn't seem to do as good a job as the 800 in managing Elevation over the course of the ride.

The 800 has a barometric Altimeter which means it does not take all the Elevation data from GPS. This has proven very reliable.

The specs for the 820 say it also has a barometric Altimeter, but the recorded Elevation data look like all the data points come from GPS.

Does the 820 indeed have a barometric Altimeter?

TIA for any help.
  • Former Member
    0 Former Member over 8 years ago
    Same problem here: roughly 60m too low.

    I wrote garmin support (Switzerland) with reference to this forum.
    Garmin Switzerland seems not aware about a general problem: " So far there are no reports of a general issue of multiple devices with this error.":confused:
    They asked me to send back the device, but looking at the reaction here i'm hesitant as it seems it will not solve the elevation issues.

    Fingers crossed some Firmware update will fix it. I 'm also curious to hear if there are people with correct elevation.


    Nobody knows - not a LBS and not even a local Garmin support. Or do they but just keep buying time with returning units? I've already had 2 units with the same problem, waiting for #3... :confused:
  • Former Member
    0 Former Member over 8 years ago
    Or do they but just keep buying time with returning units?


    That's what I believe, but I find it hard to understand why it's taking so long to sort out, maybe there's some underlying hardware issue, that a firmware update is unable to correct.
  • Former Member
    0 Former Member over 8 years ago
    that may be, Garmin does not fix , because this problem is not possible to delete and software and hardware , and so it will be on the edge 820
  • Former Member
    0 Former Member over 8 years ago
    6400 Rio Bravo

    I wrote garmin support ..........


    I also wrote and they said they are working at the problem

    " We've ask to Navstar to move all the sat 50m above to fix the problem
    We hope it will work, but we are not so sure about Glonass "


    M
  • Former Member
    0 Former Member over 8 years ago
    07/23/2016 reported problem
    03.10 .2016 still nothing
    Congratulations Garmin, why sell? 820 as it is bad software?
  • Former Member
    0 Former Member over 8 years ago
    I don't have the 820 but based on how the 520 handles elevation here are so things to consider.

    There are some differences from earlier models. For models prior to the 520, displayed and recorded elevation are the same and the calibration for current ambient pressure is updated periodically throughout the activity. For the 520 the displayed and recorded elevation are not the same. The recorded elevation is no longer re-calibrateted so the same setting is used for the entire activity. The displayed elevation is tied more closely to the GPS elevation.

    It sounds like the 820's problem is with the GPS elevation and, if so, I think you may find that it is affecting the displayed elevation only and not the recorded. If the 820 is the same as the 520 is should be using only one setting for the recorded elevation. If so, the drifting you are seeing in the displayed should not be in the recorded. Also I think you will find when a elevation set point is used it holds for the recorded. For the 520, if the elevation is set after the activity is started the new setting is applied to the previous recorded elevations.

    The calibration setting has no effect on the elevation profile and the total gain calculation. The elevation difference between bottom and top is the same. The setting just slides the elevation side to line up with true elevation.

    An added note just to avoid confusion for 520 users because it is a little different. For it, if a set point is provided the displayed elevation is not tied to GPS elevation and remains the same as the recorded. If no set point is provided the displayed is tied to GPS elevation. It appears that for the 820 the displayed is always tied to the GPS elevation.
  • Former Member
    0 Former Member over 8 years ago
    I think you may find that it is affecting the displayed elevation only and not the recorded........


    Thankyou for your suggestion ..... but ...

    If I go cycling around for 30 km, not watching the display (i want to skip the problem now), at the sea level, not going to hill or mountain, the recorded trace is ...

    -45m at the start ....... -45 ......... -45 ............ and -45 at the end

    A long, perfect line 20.000 Leagues Under the Sea ....


    bye M
  • Former Member
    0 Former Member over 8 years ago
    Funny, in the last few days the offset has turned even worse. I live by the seaside and my unit was -50 / -60m off, pretty consistently, but lately it is -90 / -100m off. Way to go Garmin!
  • Funny, in the last few days the offset has turned even worse. I live by the seaside and my unit was -50 / -60m off, pretty consistently, but lately it is -90 / -100m off. Way to go Garmin!


    Me too - I'm at +55m, since the last update I've gone down from -60m to -86m!
  • Former Member
    0 Former Member over 8 years ago
    Naff Garmin 820

    This is a joke best part of £400 and it just dont work Mines doing exactly the same picking up a replacement tomorrow will see what happens but after reading all the above I dont hold out much hope ......Do we all get a FULL refund if this is not sorted ?????