Related
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

Bug on climb pro

Roberto Ena
over 3 years ago

Hi

when using climb pro, very often the "remaining ascend" freezes. This happens mostly (probably always) on imported gpx tracks.

If I stop/restart the navigation, maybe to a slightly different route, what happens is that the new route shows on the map, but the "climb pro" window retains the old route climbs (still frozen)

I have to switch off the device (and loose the activity)

Any suggestion?

I have version 4.10: I will update the device, but only if this is a known bug that has been fixed.

Thank you

EDIT: I'm attaching images showing the issue. It was a video but my language was not very polite so I'm attaching just two frames.

Here the display correctly says "26 km to destination" (I just loaded a new destination)

But here the climb pro is still stucked on the previous climb (and says "next climb 34 km", that is beyond the end of the current navigation, which is impossible).

  • 0 over 3 years ago in reply to mcinner1

    Thank you, I added some pictures to better explain the problem.

  • 0 over 3 years ago in reply to Roberto Ena

    Hi I have similar issue ClimbPro rider position Icon  keeps freezing as far as I can see Virtual Partner Icon moves along ok. I reported this to Garmin in the same ticket for delayed incline display. On the odd occasion it appears to work ok but rarely. 

  • 0 over 3 years ago in reply to Rogls

    I think the rider position freezing is due to the climb having to few track points. How was the course created. Garmin recommend that a track point be placed every 50 meters or so. 

    I think the rider position currently updates as you pass through each track point. If the track points are too widely spaced then it looks like the rider position has stalled until you pass through the next track point then it jumps forward.

    I have a ticket open on this.

  • 0 over 3 years ago in reply to aweatherall

    Thank you, the "ticket" is encouraging.


    The two tracks are visible in a picture in this 3D (brown: gpx and blue:activity)

    https://forums.garmin.com/sports-fitness/cycling/f/edge-1030-plus/263399/a-bug-following-gpx-track

    In any case, I am pretty sure I cycled almost a kilometer with the frozen display.

    In any case this not explain why I could switch to a different target 26 km away, with the climb pro display still showing the "old" climbs, 34 km away.

    If useful I can extract the precise point where the movie was recorder and place it onto the gpx files, which I can provide as well.


    Thank you again

  • 0 over 3 years ago in reply to aweatherall

    The OP has a different thread about another issue about the same file.

    The problem there was using a file without enough points. 

    It appears he's using a route file, rather than a track file.

  • 0 over 3 years ago in reply to dpawlyk

    No, I don't think so. It's just a track file with reduced number of points.

  • 0 over 3 years ago in reply to Roberto Ena

    The file you are using doesn't have enough points to be an appropriate track file.

    It won't work well for navigation.

    You shouldn't be using it.

    aweatherall seems to think that it has too few points might be an issue (he's somebody who people should listen to).

    Where are you getting this file from?

    You should try a proper track file.

  • 0 over 3 years ago in reply to dpawlyk

    Can you point me to a document of Garmin where it is specified the minimum number of points to be a track file?

    Thanks.

  • 0 over 3 years ago in reply to Roberto Ena

    Point to a document that says what you are using will work.

    ==================

    If the path is a straight line, you'd only need two points. So, there wouldn't be any indicated minimum because it would depend on the path.

    The more curves and turns, the more points you'd need.

    The track should clearly follow the path you intend to follow. If it does, it has enough points.

    The file you are using clearly doesn't follow the roads very closely.

    What you are using doesn't work for navigation (the "off course" issue).

    Why use it at all?

    ==================

    There doesn't seem to be other people having the same issues you are seeing.

    The common thing is the bad file you are using.

    ==================

    Multiple people pointed out the issue with the file you are using. Be sure to read aweatherall's above post carefully.

    I'm not sure why you still want to use the bad file.