Bug on climb pro

You thought you were following it. In the other thread, you were complaining about off course warnings.

The point is that, whatever you do, the device is using the track, in one way or another.

Depending on Climbpro works with loaded routes, you might have been following it (in the vertical dimension).

There are a few things you needed to be clear about at the start (that you weren't following the track or whether the route was recalculated) that are important for people trying to help.

dpawlyk said:

You thought you were following it. In the other thread, you were complaining about off course warnings.

No, please read at the end of a previous post: the gpx issue occurred somewhere else. I specified that to be sure there is no misunderstanding (but still).

 I am considering to open anther 3D on this and reporting only the substatial information because admittedly the long exchange of posts between the two of us makes very difficult for other users to focus on the real problem.
It is quite natural that the information changed during this exchange since I spent some time to do debugging.

Regards

It's the same track.

You had an off course issue in the horizontal dimension in one place and and off course issue in the vertical dimension in another.

Climbpro may have been trying to use the track.

Off topic:
...and it is very complicated to follow a discussion in that sort of forum software...

-opening post on every page
-top answers (no idea what‘s the way they are selected)
-all answers

It is very difficult to follow the discussion.

There are tons of „normal“ forum software out there - but no, Garmin choses the worst and most confusing!

Roberto Ena said:

The issue we should focus now is why Edge1030+ retains a climbpro profile of a 150 km ride while my destination was just 26 km away.

Because you had a track loaded and where not following it (I believe).

• You might not have had the Climbpro problem if you were using a track you were following.
• You might not have had the Climbpro problem if you were not using a track at all.

(The device shouldn't freeze. Not sure if you mean you changed the destination for navigation or just rode to somewhere else with "after the destination changed").

One more try to bring light into shade:

let‘s start from the scratch. I‘m referring to your - Roberto‘s - opening post:
You say:
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)

Please explain what exactly you did when you „restarted the navigation, maybe to a slightly different route“.

mcinner1 said:

...and it is very complicated to follow a discussion in that sort of forum software...

I would add the fact that my typing window disappears if someone else just replied to the same post while I'm typing.
And also having the possibility to completely change the containt of a message after it is published, without any tracking of changes, may ingenerate misunderstanding between users.

mcinner1 said:

Please explain what exactly you did when you „restarted the navigation, maybe to a slightly different route“.

OK.

"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)"

If you are off track, the 1030+ can give you alternative routes. Maybe, he picked one of those.

If you select another course or have the device calculate a route to a different place, the device will ask if you want to stop the current navigation. You can also just stop the navigation. In these cases, the anything associated with the prior track or route should be cleared (including the climbpro stuff).

Since he was talking about prior climbpro stuff and off course warnings, I don't think he stopped the navigation.

Picking alternative routes doesn't stop the current navigation (the device keeps it "in mind" because it's expecting you might return to it).

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

The Climbpro stuff might not be recalculated when using recalculated routes because it might just take too much time (I said this earlier). The recalculations have to be fast (and dealing with climbpro might make it too slow).

Things like distance-to-end and the virtual partner are paused when you go off course. Both of these are using data read from the track (the device can't do anything sensible with them if you are off course). The same thing might be done with climbpro.  (I said this earlier.)

The climbs are determined when the device generates a route without using a track but (like above) I don't think the device recalculates the climbs if the route changes while you ride (I said this earlier).