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 Page 0 ft on display...2nd Edge 130 device with this issue

Former Member
Former Member over 5 years ago

I bought an Edge 130 in June 2019, used it for a few months and then the elevation page (graph) stopped working even though elevation gets recorded.  Garmin replaced the unit two months ago, and now I am back to having the same issue even though it worked fine for the first few weeks.  I was told to clean the barometric pressure sensors on the back (two small holes) but this did not do anything, and they never even go dirty in the first place.  

Looking to upgrade to some sort of Wahoo if this does not get fixed.  Clearly, it's been a known issue on this forum for a couple of years.  

  • 0 over 5 years ago

    That's right, it's annoying. I used to have Sigma ROX 6.0 and the altimeter works fine even though I washed it in the washing machine!
    I am also thinking about another company especially reading all these problems with Garmin equipment.

  • Former Member
    0 Former Member over 5 years ago

    I've had the exact same issue, and am also experiencing this with my second device.  t's recording all of the data, it just has trouble displaying it in real-time. Garmin support is aware of the issue and working to fix it.  As of now, I found that I can get the screen back if I press and hold the top right button to activate the main menu.  Then switch back to the live data stream and it works.  

  • Former Member
    0 Former Member over 5 years ago in reply to Former Member

    I bought a Wahoo Element Bolt in mid-April.  The elevation graph is great, regardless of whether or not I am using navigation. 

    Also, I can set up all of my data screens with the app...soooo much easier. The only reason to ever plug in a Wahoo is to charge the battery.  Everything else, from screens to maps/courses, Strava segment data, etc, is all done through the app.   

  • Former Member
    0 Former Member over 5 years ago

    Found a fix if your Edge 130 stops displaying the elevation in real-time.  Press and hold the right up arrow button until the menu appears.  Then simply press the return button (bottom left) to go back and the elevation should show up again.  I've had this happen multiple times and this always fixes it.

  • 0 over 5 years ago in reply to Former Member

    Perusn01, maybe a Connect IQ field that you're using ?
    Any device can have a fault, but 2 times in a row is unlikely.
    My Edge is flawless with the elevation graph. (lucky me)
    I find the barometric elevation sensor on my 130 better than on my Etrex 30.
    That doesn't mean anything, just that not all 130's are crap.

    There could be a possibility that you are doing something that's causing the same situation on your new 130 (and the next etc).
    I agree that Garmin should prevent something like this to happen, but Garmin is known to make an occasional mistake in their firmware releases...


    A general tip for correct elevation:
    I have made waypoints of my starting locations, all with the correct altitude.
    This way the Edge automaticaly calibrates the altimeter upon startup. 
    (and only on startup. the 130 does not recalibrate during your ride, changes in weather result in changes in elevation)
    So, the first thing to do is to make some waypoints (Basecamp) of your stating locations, including the correct altitude.
    House, work, parking, camping, hotel etc.

    Next thing to remember is that the 130 has no map.
    If you are not on a course, the 130 does not know what's coming up.
    It only knows where you are and where you've been. The same goes for elevation.
    A device with a map might know what's in between your location and the start of your course, including an elevation profile of that route. (depending on the device and depending on the map)
    The 130 can only show an elevation profile once you're on the course.
    And the elevation data must be in the file.
    Devices with a map can calculate an elevation profile using map data, the 130 can not.

    Hope this helps.