I’ve got a 530 on 9.5 and you can change the Climb Detection sensitivity in the ClimbPro data screen for whichever profile you are using
1 Like
Thx. While ClimbPro is on screen?
Nevermind, I turned on my 530 and see it under Settings > Activity Profiles > Road
I assume you could (top right button), but i saw that when i was playing around with the 530 earlier today when not riding
1 Like
You’re in luck that I can answer this question specifically - my 1040 is brand spanking, and I haven’t yet sold my old 530.
On the 1040:
Activity Profile> Climbs> Climb Detection
On the 530 (running 9.5):
Activity Profile> Data Screens> Climb Pro> Climb Detection
1 Like
Sweet. Mines happening on open roads as well a gravel. Thanks
Oh fwiw yesterdays ride was a ride with gps link uploaded to strava then saved to Garmin.
Another question regarding climb pro screen
At the beginning of the climb the screen pops up but after few seconds the screen is changing
You have to manually push the buttons in order for the climb pro screen to appear again
You are right
It does pop up
But doesn’ t remain on the course of the climb
I have a fenix 6X sapphire
Let me know if you want the GPX files of the two Strava HC climbs below…
- About 6.5 months ago I wrote this about a Strava course on my Garmin 530:
and yes, it was a course synced from Strava.
worked perfectly on first 3 sub-climbs of a long HC climb. Simple out-and-back course. Issue happened on the descent, which had two short climbs.
- About 8 months ago I did an HC climb on this Strava course:
and it was a single climb on my 530:
No issues with ClimbPro, the climb finished at the top exactly as per the course. The barometer however only give me 5266’ climbing, but thats how barometers roll sometimes 
- Couple weekends ago I rode a course synced from RideWithGPS and no issues with ClimbPro.
1 Like
Sent
1 Like
exactly
Did you look at the other two climbs that didn’t have a problem (Diablo and Shasta)?
BTW I uploaded that Strava route to RWGPS and see the problem.
not confusing for symmetrical My Hamilton:
thanks, figured this out a minute or two before you posted. My method was to upload Strava .gpx to RideWithGPS, note that elevation error was also on RWGPS, so I deleted the downhill and told RWGPS to make me an out and back. Download and compare using the GPSVisualizer method.
Clearly a Strava bug.
Guess its good that BWR AZ got me to pay for RWGPS again 
1 Like
On this theme, one thing I noticed is that it seems the behavior may differ between older routes and newer routes. I don’t know it’s a route data error/accuracy issue or a change in some calculation on the Garmin side
I have a bike trail that is part of a number of my routes. A couple of these routes are at least 2 years old. I created a new one recently, using the same section. I noticed I was getting more climbs detected than on the older routes.
Similarly, with a different segment, I have two routes that share it. One detects the climb, the other does not. I have climb detection set to the most inclusive as I’m not the über climbers the rest of you are.
It’s not critical to me but it is annoying. Sharing this theory in case it helps with your investigation.
ok, Mt Hamilton route was created by finding segment, finding someone that started near where I was going to start, and then copying their route to my Strava Routes.
If I create one by hand - this one took about 2 minutes - no elevation error:
Maybe the elevation error was introduced by the bike computer that captured the original route? And compounded by Strava not attempting to fix GPS data? I randomly picked a route to copy, have no idea when it was created.
I traditionally have used Garmin Connect’s route editor to create my routes. It is far from bug free, but I’ve learned the quirks and I can make it work. I just tried to re-create one of my usual routes in Strava Routes and had to quit after just a few minutes of frustration.
I’m fortunate to have some great paved bike paths, that are long established. Garmin generally uses them just fine. Strava kept giving me convoluted routes and generally got confused. For example, one part of the route follows a river. I dropped a point along the path on the river – Strava tried to put me on the other side of the river! The dot on the right is where I put the point; the endpoint is where Strava placed it.
That’s roughly a 10-15m error.
I imported a file from ride with gps into strava and the sent it to my edge 830. Had issues mid ride after that. Typically I’m only using routes created in strava. Im wondering if the added step from rwgps has something to do with my issues.
1 Like
I had an issue with ClimbPro at Rebecca’s Private Idaho last September. It got worse as the race progressed. I was guessing that it was a stacking error of some sort but never imagined it was caused by a sync from Strava to Garmin Connect.
Continuing to watch this. 
In order to do this I’m guessing you have to have your device plugged into a laptop? Can’t do it from phone to device?
Thanks
Maybe of interest but after reading this thread I thought I would do a test.
I took a random route that was created in Strava and exported to Garmin connect and just selected “duplicate” on the Garmin connect website.
The duplicate that it created moments later has different elevations.
I assume that the duplicate is using elevation correction but could be wrong?
Could be interesting to see which of the two plays nicer with climb pro?
Nice video
6 Likes