NAV problem starting in the middle of a stored route

If the 1030 behaves like a 530 it’s best to turn off route recalculation (unless you need it to be on) and not load a course until at the start or some point along it. It should then find the course without problem and guide you along it.

Recording your activity and navigating are independent, so a course can be stopped and another loaded without stopping the activity.

I'm pretty sure it's very similar to the 530, although I know they added some enhancements to the plus model regarding recalculation options from what I remember. (Like options related to where to rejoin the current route, etc)

Before I read this I was out riding tonight experimenting and while I was randomly riding around (and recording my activity) I stopped and loaded a route where I knew the start was a few miles away. When it asked me if I wanted to navigate to the start I clicked on "X" instead of the checkmark (which I believe means "no") and it successfully calculated my route to the nearest point along that route so that I could join it and continue on from there. This is what I was hoping to see, but it doesn't always seem to work. One difference this time was that I didn't cancel a current route I was on.  I just loaded one while already out riding and recording.

I wish it would tell you what "error in calculation" means when it happens. (Like it can't find a street or a satellite or something else? Is it related to problems with coordinates in the route itself, depending on how it was created?)   I'll keep testing, and I will also take your advice and turn the recalculation off until needed.

One last comment...I'm not sure about the 530, but navigating the 1030 menus (especially while on a ride) and looking for "any" of the NAV functions feels like it's a lot harder than it needs to be - especially coming from a company that is known for navigation! I feel like an idiot fumbling around looking for the right screen each time! I don't use NAV daily, but I do like touring around new places so I'm hoping that I will eventually get used to it. LOL

Anyway, thanks for the advice! 

Show us the route that failed and where roughly you where. It’s supposed to work.

Ideally, you should be on the route (somewhere) before you calculate it. 

I can definitely do that. I'm new to this forum so I'm trying to figure out how to load it here. Where can I look at ttecroute?  Not sure what that is and I tried Googling it...  I'm planning on taking this same trip this weekend so I can troubleshoot this for my own sake. I just want to learn how to do this correctly. (Creating routes and actually using them on the fly...) 

Usually, people get the route from a website. If that's what you did, you can provide a link to the page.

(My earlier post got mangled.)

You might need to be on the route for the device to be able to calculate it.

Pasquale61 said:

I wish it would tell you what "error in calculation" means when it happens. (Like it can't find a street or a satellite or something else? Is it related to problems with coordinates in the route itself, depending on how it was created?)   I'll keep testing, and I will also take your advice and turn the recalculation off until needed.

This can happen if the track you loaded doesn't follow any roads/paths that are on the map installed on the device.

Note that "recalculation" refers to the device calculating a new route when you go off course. The devices appear to strongly prefer trying to get you back to where you left the course.

Got it.  And maybe that's what it was. Below is a link to the actual route I was trying to get on.  It's one way.  I was on the eastern portion of the Poplar Creek Forest Preserve on a trail south of Golf Road and between Barrington Road on the east side and Bartlet Road on the west side.  I should have tried again after I made it to a main road...but I will say that my Garmin was showing all the trails I was on during my ride, so it knew they were there.  (That's actually how I found my most direct way out of the trails to the main street, by just looking at my screen.)

www.komoot.com/.../836982753

I'll keep playing around and figure it out.

Thanks again for your help!

Ugh, Komoot (requires payment to download the route).

Anyway...

The route calculation requires that there be roads/paths on the map (used for routing) to work.

The Garmin may have been showing the trails using "TrailForks", which might not be included in the map used for routing.

It seems probable that moving to a road would have allowed the calculation to work.

Thanks for the tips, and the link to that OpenStreetMap site. I like it!  Much appreciated.  Now you have me thinking about looking at the TrailForks map..,I will pay closer attention going forward.

Garmin uses Openstreetmap (OSM) to generate their normal maps. Most (if not all) route planners let you choose OSM.

The Openstreetmap is a better way of understanding how the Garmin "sees stuff".

The TrailForks map is separate. It only has "mountain bike" paths. The TrailForks is separate from the OSM maps (the two don't connect), which means the device can't route from something that is one map to something else that is on the other map.

(I don't do much with the TrailForks stuff.)