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 broken after maps upgrade to 2023.10 version

After latest upgrade of software 9.29 and after upgrading the maps to versione 2023.10 climb pro in free mode seems not to be funtioning anymore. No climb is detected even if all the settings are the same as before the upgrade when all was functioning.

Anyone else facing same issue?

Top Replies

filogo over 1 year ago in reply to danielran +3

I solved the issue cleaning completely the installed maps and then proceeding to re-install all the maps. The climb pro function needs special maps to function. After the update something was broken and…

All Replies

0 danielran over 1 year ago

i have the same issue….

0 filogo over 1 year ago in reply to danielran

I solved the issue cleaning completely the installed maps and then proceeding to re-install all the maps. The climb pro function needs special maps to function. After the update something was broken and re-installing the maps should fix this issue.

From Garmin manual:

ClimbPro Without Navigation

To support climb detection during a free ride, Garmin added supplementary maps to the regional Garmin Cycling Maps. These additional maps include information about the climbs in a given network along with the terrain type (paved, unpaved or mixed) for each climb. In order for ClimbPro to work in "Free" mode, you must be using the latest version of Garmin Cycling Maps and have the ClimbPro maps enabled. The ClimbPro map version should match the Garmin Cycling map version for the same region to trigger ClimbPro during a free ride.

The link below gives advices on how to verify if the maps for clim pro function are enabled:

https://support.garmin.com/en-US/?faq=zdggRttcfT4PGwTbfifMY5

0 danielran over 1 year ago

Solved ! Great ! Thank you !!

0 Zavyalov Cycling 10 months ago in reply to filogo

Thank you for this solution. Got this problem right after the maps update and solved in the same way. Posted a video on this problem today. It seems more and more owners are stuck with this.

https://www.youtube.com/watch?v=TcY75uz9DuE