Climbpro

MartinF said:

Anyone else experiencing this or any suggestions how to fix it?

I had similar problems and have

1. deleted the maps and reinstalled them (this also deletes the ClimbPro databases in the \Garmin\SQL\internal directory and "restores them" when reinstalling).
2. then, as a precaution, the >30 second reset was carried out

Servus peggatsch

Hi, As per the post below delete the maps and re-install. I had the same issue and fixed mine. Post is below 

https://forums.garmin.com/sports-fitness/cycling/f/edge-1040-series/354342/1040-version-19-22---climb-pro-not-work/1746399#1746399

video is in post but here is the link also 

https://youtu.be/TcY75uz9DuE

The last map update brought me that Climbpro detects the end of the climb near the route I am following ( but I am not approaching it in any way ). Apparently, this is the first foray into the DownhillPro function ;P because how can climbpro inform me with a message about a nearby climb when I am at the very top of it.

There are situations where a climb branches off from the current path and this is displayed. Of course, the Edge doesn't know beforehand whether you want to take the climb. For this reason, I find it very helpful that the ClimbPro screen shows the map at the top where the climb can be seen

Servus peggatsch

I'm not a masochist to treat information about a nearby driveway when it's at the level of its peak as a challenge - I'll ride it down and ride it back up - after all, it's so cool to be in the same place I am, but more tired ;P

Thank you and peggatsch for the advice. I deleted the maps, reinstalled and performed a reset. This morning I went for a ride where I know from past experience that there are two climbs rated > 3500. The first climb was detected, climbpro appeared and then a quarter of the way up the climb disappeared. I completed the climb, but it doesn't appear as a climb in the ride statistics either on the Edge or the app. I then changed the climb detection settings so that climbs less than 3500 are not detected. The second climb appeared on the Edge when it was supposed to, stayed until the top and the climb was recorded in the ride statistics. From this it seems possible that the issue is to do with the detection of climbs rated less than 3500. I wonder if instead of detecting one longish climb it detects two short ones, especially when there is a flat section in the middle of the climb. However, this does not explain why climbpro disappears and the climb is not recorded. Hopefully this is something that will be sorted out with a future update, unless of course it only affects me. 

Thanks again. I have just saved the route I did this morning as a course. It's come up with four climbs all labelled easy. However, with the Garmin length × grade I'm sure that two of them are less than 3500 and two are greater. That fits in with what happened when I followed courses on my old Edge 530 which included these climbs, and only two of them showed up. I think I'm better off only getting it to detect climbs greater than 3500, and if I do that, the course now shows only two climbs as expected. There are lots of hills here in Devon and I can see why it might get confused.

For route planning I use cycle.travel. It tries to avoid traffic and can be sent directly to GC and from there to the Edge.

Hi MartinF  thank you also for the feedback and the valuable tip about cycle.travel... I just tried it out, it works very well for me too

Servus peggatsch