Short circuited route

I've just run into an odd issue with my Montana 600 with 5.30 and Basecamp 4.2.2. I tried to create a route that's about 100 miles long that begins at waypoint 1 and ends at another waypoint very close to waypoint 1. There are two other stops along the way about 50 miles out. Using BC to create the driving route for shorter distance works fine, route instructions are good. When I try to run the route on the Montana it basically short circuits the far waypoints and routes me directly to the destination with no intermediate stops at all.
I can get this to work by either setting direct routing on BC before sending to the 600 or by moving the destination waypoint several miles away.
I'm not sure if this is a Montana or BC issue. Anyone else seen something like this?
  • My guess is a Montana issue. I have a 62 series and imported routes show a variety of behaviors. For instance, if my device is set to Direct activity, uploaded routes will load as a direct route regardless of the activity in the file. If the device is set to any other activity, it will load the route as created in BC (no calculation, no ability to edit route and no auto-rerouting). On the 62, it is possible to recalculate a route with a different Activity, but it will only use the Start and End points, ignoring all other user points in the original route (to me, this is fundamentally wrong). This may be related to the problem on your device.

    You should report the problem thru product support. But don’t get your hopes up. I have found communication between users/product support/device programmers pretty poor at Garmin. In the past, I have reported an example of a positional error of over 2,000 miles, but I can’t seem to get the device programmers to fix or even acknowledge the issue.
  • I've just run into an odd issue with my Montana 600 with 5.30 and Basecamp 4.2.2. I tried to create a route that's about 100 miles long that begins at waypoint 1 and ends at another waypoint very close to waypoint 1. There are two other stops along the way about 50 miles out. Using BC to create the driving route for shorter distance works fine, route instructions are good. When I try to run the route on the Montana it basically short circuits the far waypoints and routes me directly to the destination with no intermediate stops at all.
    I can get this to work by either setting direct routing on BC before sending to the 600 or by moving the destination waypoint several miles away.
    I'm not sure if this is a Montana or BC issue. Anyone else seen something like this?


    It's a Montana issue. It is now common Montana practice to build the route in BC in whichever activity profile you intend to duplicate on the Montana, then set it to Direct before transfer (this also makes it reversible and editable). Plus, the maps must be IDENTICAL on each. All avoidances must be IDENTICAL. It's also good practice to keep beginning and end points separated by a mile or so. Those two other waypoints SHOULD force the Montana to route the way you expect, but experience tells us otherwise. It usually works, but not always.