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

Navigation "back to start" issue

lytleric
over 3 years ago

I was recently navigating a mountain bike route I had built in Trail Forks, but the route was not taking me where I had expected it to.  So I decided to bail on the route and tried to navigate back to start.  I selected "most direct route" and it popped up with a message "This route may take a long time to calculate.  Consider adding via points."  I thought that was strange, because I had ridden only a few miles at that point.  

I tapped the checkmark anyway, and here's the point it took me back to:

But here's where I actually was, trying to get back to my start point:

Why did the Edge try to get me back to a point over 200 miles away?  Interestingly, that is a point on another route I have saved on my Garmin.  So it is confusing routes somehow.

  • 0 over 3 years ago

    You posted the same question in the 530 subform.

    It's quite unusual to be using a 530 and 830 at the same time.

    Or, you should avoid cross posting. 

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

    You added extra info here.

    The pins you dropped aren't where you started. The pins get saved to locations and you can navigator them by picking the pin from the locations list.

    The start point is where you started recording. I suspect you didn't save (close out) the earlier ride and the start was taken from that.

  • 0 over 3 years ago in reply to dpawlyk

    My post in the 530 forum was by accident; I didn't realize I was posting in the 530 forum.  I have the 830.  I tried to delete that post by going into Profile -> Activity -> More (under my post) -> Delete, but strangely that does not actually delete my post from the forum as expected.

    After ending navigation, I simply selected "Navigate back to start."  I did not drop any pins.  I started this ride from the start point shown in the third screenshot above.  Why did the Edge navigate back to the point it did, instead of where I started the activity?  That location was from a ride I had done weeks ago.  I've done probably ten other rides since then (starting them and stopping them when finished).

  • 0 over 3 years ago in reply to lytleric

    The problem you had was that, somehow, the device thought the start was a very long distance away. The "too long to calculate" message was the result of the weird far-off start point.

    I'm not sure if there's enough information to know why it had the wrong start point.

    It doesn't seem other people have this problem.

    Maybe, it won't happen again.

    Not that you can drop a pin (at your start) and navigate to the pin.

    Or, you can reload the course and have the unit navigate to start (if you are using a course).

    That is, there's an easy way around the problem, if it happens again.