Understanding ClimbPro on the Edge - Updated for build 9.50

I thought it would be helpful to write-up how ClimbPro works on the Edge. 

This write-up is based on the recent 9.50 software release.

New in Build 9.50 is

Estimated time to the top of the climb

Understanding ClimbPro on the Edge V1.9.pdf

  • Hi, I tried the Beta 7.85 and used the option to show the Elevation Profile below the map - but I do not understand it. I expected to see whats coming up, like the Climp sreen shows not only a dark red bar.

    Is my understanding wrong? What shows the 830?

    BR

  • Something is not right there, could you post the course file?

  • Hi, attached the fit file from the edge 1030; created it with openmtbmap alps in BaseCamp.

    Schöckl_Wald_course.zip

  • The problem is that the course file has no elevation data in. That is why the elevation profile is a flat line.

    Data 5 record timestamp 0 s position_lat 562440558 semicircles position_long 183956988 semicircles distance 2.31 m
    Data 5 record timestamp 1 s position_lat 562440704 semicircles position_long 183955968 semicircles distance 8.88 m
    Data 5 record timestamp 4 s position_lat 562442240 semicircles position_long 183956480 semicircles distance 23.68 m
    Data 5 record timestamp 9 s position_lat 562445312 semicircles position_long 183956480 semicircles distance 52.19 m
    Data 5 record timestamp 11 s position_lat 562446336 semicircles position_long 183956480 semicircles distance 61.7 m
    Data 5 record timestamp 17 s position_lat 562449920 semicircles position_long 183956480 semicircles distance 95.15 m
    Data 5 record timestamp 20 s position_lat 562451712 semicircles position_long 183956223 semicircles distance 111.96 m
    Data 5 record timestamp 25 s position_lat 562454528 semicircles position_long 183956223 semicircles distance 138.2 m
    Data 5 record timestamp 27 s position_lat 562455552 semicircles position_long 183955968 semicircles distance 148.2 m
    Data 5 record timestamp 31 s position_lat 562457856 semicircles position_long 183955199 semicircles distance 170.05 m
    Data 5 record timestamp 35 s position_lat 562459648 semicircles position_long 183954175 semicircles distance 187.98 m
    Data 5 record timestamp 43 s position_lat 562464512 semicircles position_long 183951872 semicircles distance 235.52 m
    Data 5 record timestamp 50 s position_lat 562468096 semicircles position_long 183950335 semicircles distance 270.39 m
    Data 5 record timestamp 52 s position_lat 562469376 semicircles position_long 183949568 semicircles distance 283.46 m
    Data 5 record timestamp 59 s position_lat 562472960 semicircles position_long 183947520 semicircles distance 319.38 m
    Data 5 record timestamp 74 s position_lat 562480896 semicircles position_long 183942144 semicircles distance 400.99 m
    Data 5 record timestamp 93 s position_lat 562490624 semicircles position_long 183936256 semicircles distance 498.88 m
    Data 5 record timestamp 100 s position_lat 562494720 semicircles position_long 183933952 semicircles distance 539.96 m
    Data 5 record timestamp 103 s position_lat 562496512 semicircles position_long 183933184 semicircles distance 557.39 m
    Data 5 record timestamp 112 s position_lat 562501120 semicircles position_long 183930880 semicircles distance 602.77 m
    Data 5 record timestamp 116 s position_lat 562503424 semicircles position_long 183929856 semicircles distance 625.38 m
    Data 5 record timestamp 134 s position_lat 562513408 semicircles position_long 183924735 semicircles distance 724.01 m
    Data 5 record timestamp 151 s position_lat 562522368 semicircles position_long 183920384 semicircles distance 811.74 m
    Data 5 record timestamp 153 s position_lat 562523648 semicircles position_long 183920128 semicircles distance 824.03 m
    Data 5 record timestamp 155 s position_lat 562524941 semicircles position_long 183919905 semicircles distance 835.94 m
    Data 5 record timestamp 158 s position_lat 562526720 semicircles position_long 183920128 semicircles distance 852.73 m
    Data 5 record timestamp 174 s position_lat 562535680 semicircles position_long 183922687 semicircles distance 937.94 m
    Data 5 record timestamp 185 s position_lat 562541824 semicircles position_long 183924480 semicircles distance 996.46 m
    Data 5 record timestamp 193 s position_lat 562545920 semicircles position_long 183926272 semicircles distance 1036.5 m
    Data 5 record timestamp 199 s position_lat 562549504 semicircles position_long 183928064 semicircles distance 1071.48 m
    Data 5 record timestamp 208 s position_lat 562554112 semicircles position_long 183930112 semicircles distance 1116.74 m
    Data 5 record timestamp 210 s position_lat 562555392 semicircles position_long 183930623 semicircles distance 1128.96 m
    Data 5 record timestamp 219 s position_lat 562560256 semicircles position_long 183931904 semicircles distance 1174.91 m
    Data 5 record timestamp 227 s position_lat 562565120 semicircles position_long 183932928 semicircles distance 1221 m
    Data 5 record timestamp 234 s position_lat 562568704 semicircles position_long 183934208 semicircles distance 1255.43 m
    Data 5 record timestamp 239 s position_lat 562571520 semicircles position_long 183934976 semicircles distance 1282.1 m
    Data 5 record timestamp 246 s position_lat 562575616 semicircles position_long 183936000 semicircles distance 1320.68 m
    Data 5 record timestamp 250 s position_lat 562577664 semicircles position_long 183937024 semicircles distance 1341.12 m
    Data 5 record timestamp 251 s position_lat 562578432 semicircles position_long 183937280 semicircles distance 1348.13 m
    Data 5 record timestamp 257 s position_lat

    562580992

    semicircles position_long 183940351 semicircles distance 1379.03 m
    Data 5 record timestamp 258 s position_lat 562581760 semicircles position_long 183941120 semicircles distance 1387.77 m
  • ok - but how can I integrate the elevation data with BaseCamp?

    and why shows the climb page the different gradients?

  • Getting the elevation data into the course file is probably a question that is better directed to the basecamp forum.

    https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-windows

    https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-mac

    I'm guessing that the Edge is trying to use the DEM data on the unit, which is why it has some elevation information, but support for using the on-board DEM data has not been implemented yet by Garmin.

  • Gasthof_Lug_Ins_Land_bis_Egelsee_Steg_course.zipHi, thank you for your expertise - I found some hints at https://openmtbmap.org/de/about-2/plan-routes/ (german) that the course will not contain elevation data - I need to convert the course to a track and send the track to the Garmin device.

    I would like to check the difference tomorrow (well it is already tomorrow) and prepared a track for my walk. Could you please take a look on it - does you expect it to work?

  • It is a pretty sort course, but it does meet the requirement of ClimbPro. ClimbPro has identified one climb.

    I'm not sure how well the 1030 will perform at walking speeds. I would recommend disabling auto-pause if it is currently enabled.

  • Solved!

    1. create a course in Base Camp

    2. convert it to a track

    3. send the track to the Edge

    4. route and gradient is shown on the map-page and also ClimbPro works

    Thanks!