Garmin 590LM to strictly follow route from Basecamp

Eric,

Hope I can help a fellow Beemer rider (F800ST here).

First, Basecamp will never perfectly match a GPS in its settings and preferences, so you have to settle for "close enough." I've had good luck on my zumo 660 with Fastest Time, allowing U-Turns, and prompting for recalc.

But the key is using enough vias or waypoints to "force" the route you want. While planning the route in BC, keep asking the program to recalc and see if it wrecks your plan.

I also store all my routes on the 660's SD card as GPX files copied from my iMac after exporting from BC. That way I have all my routes with me all the time and can always reload one that gets messed up en route by a recalc. I don't fully trust the transfer process.

As for tracks, are you asking because you want to create routes from them? I find it best to display a track in BC and trace over it with the route tool, then test it per above (recalc) and add vias as needed to keep it on the route you want.

-dan

Hi Dan,

Many thanks for the speedy reply and the support.
Yes I realized that adding "points" would indeed force the GPS to follow your route.
Probably a reflex to get when creating a route.

Looking to see if there are any other trick to even further improve correspondence between BC & GPS.

Thanks again.

Eric

Don't strip the shaping points from your BaseCamp Routes, your 590 uses them.

Try to have the same map versions on both your device and your computer. If you can't accomplish that then keep the 590 plugged in to your computer and use the maps on it to plan your routes.

Some people recommend using the automobile driving mode instead of the motorcycle mode on both BaseCamp and the 590 when designing and transferring routes to ensure the best route fidelity.

Turn off automatic off-route recalc on the 590

If route fidelity is critical there are two ways to ensure it:

1. Once the route is designed in BaseCamp convert it to a Track in BaseCamp and transfer that to the 590 and use the 590 to make a Route out of it.
2. Or, Transfer both a Route and a its Track from BaseCamp to the 590 and then set the Track to be visible on your 590 and change it to a contrasting color so that you can see both the Track and the Route on the 590 at the same time. If there is any deviation it will be obvious.

Your 590 has enough track point storage so you do not need to simplify tracks by removing intermediate points.

Not certain about "Always send the original route in case you want to recalculate later" If you think you might want to edit a route designed on BaseCamp and transferred to the 590 then you do need to transfer it as a Direct Route. If the preferences are the same on the 590 and Basecamp and the Map revisions are the same then theoretically you will end up with the same route when the 590 calculates it.

Match Route to the Map on My Device -- I think it means that if the Map revisions are different or if the Map is entirely different then do an automatic recalc of the route.

Hi Jack,

Also very very useful. Thanks so much.
I'm need now to try all these tips but sure it will help!!!

Thanks again.

Eric

Glad its been of some help to you.

One other tip: if your device asks you for a point to start navigating a route don't choose the final point, i.e., the destination because it will usually then recalculate and end up with an entirely different path than the one you designed. The easiest way I've found to think about Routes is as a specific path from a designated point to another designated point. In general, to be "safe" you need to be navigating when you hit the first point in the Route and then it will follow your designated path to the next point.

Hi Jack,

I spent last week in Provence (France) and deeply tested your option (Once the route is designed in BaseCamp convert it to a Track in BaseCamp and transfer that to the 590 and use the 590 to make a Route out of it).
I just would like to confirm that this is EXACTLY what I need and what I've been looking for a long time!!!.
The routes are now finally 100% reflecting the one I designed in Basecamp.

So again? MANY MANY THANKS!!!

Cheers

Eric

I tried this in the past and although it is the best solution I have found so far, I found that if you go off the planned route, then the device recalculates and throws away the whole plan.

When you setup a route with multiple shaping points and waypoints to force it to take your route and for some reason you deviate, it will re-route only up to the next point.
When you get the device to calculate the route based on a loaded track, it only creates two points, if you deviate, it recalculates to the next point (the final point).

The only way to get around it is by disabling the automatic recalculation which is OK sometimes but not other times (ie: if the route takes you through the middle of a city and you don't know the way).

Anybody had the same results?

I just tested this theory.

It works if:

You either have no auto recalculation in the settings (so it will retain the original calculation)
Or you don't deviate at all from that route.

If you have the settings as "no recalculation" then you may as well load the track, change the colour and follow it rather than converting it to a route.

If you have auto recalculation, then it will most likely loose the original plot as soon as it recalculates, either if you deviate or if it looses satellites and thinks its in a different spot momentarily.

A route created from a track either by basecamp or by the GPS itself, only contains two visible waypoints (begin and End)....

So I am back to having to add more points to retain the route...