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

Climb Pro freezing

MikeDurr
over 3 years ago

Never had a problem in the past, but yesterday on a 3hr ride at the start of any climb the Climb Pro screen would pop up like normal, but then just constantly beep like an alarm for about 20 seconds then disappear back to my default data screen.

Will try a soft reset before next ride, just wondered if anyone else has had this issue.

  • 0 over 3 years ago

    Yes, I've had similar - no beeping, but I got the climb starting notification screen with a "Go" and then it just went back to the standard data screen, that was a couple of rides ago and seems "ok" since - by ok, I mean still laggy and shows you at the start of the climb for most of it and generally behaves poorly - but at least the climb screen stays on....

  • 0 over 3 years ago

     With tones enabled, the Edge will beep as you approach a climb, is your Edge continuing to beep after the climb? Is your Edge defaulting to your default data screen on all climbs and courses or just a specific course?

    Can you go into your menu > Activity Profiles > select a profile > Data Screens > ClimbPro > Pop-up on Climb Approach. Let me know if this is enabled or disabled.

  • 0 over 3 years ago in reply to Garmin-Eric

    Its set to pop up on climb approach, for medium to long climbs. It pops up as it should just before the climb but then just hangs, beeping every second for about 20 seconds or so then vanishes completely. I haven't tried a different course with any climbs yet but I've never had problems before on the course where it happened.

  • 0 over 3 years ago in reply to Garmin-Eric

    Update: Did a ride today different course with 6 climbs, worked perfectly on all climbs so not sure. Hopefully a one-time glitch.

  • 0 over 3 years ago in reply to MikeDurr

    thanks for the update, I'm glad to hear this other course worked for you. Keep us posted if you experience the same thing on future rides. If it was only occurring with that first course then I'd recommend deleting that from the Edge and re-loading it using Connect.