New Garmin Montana

[Emmbeedee]

Originally Posted by Drif10

Bingo. Exactly that. Been messing with these things for 20 years now, always found the best way to 'get to know' a unit was to make it do things. Take you to the grocery store. Over to your buddy's place.

I usually scan ahead once aroute is plotted by the unit, just to see if it's going what is, to me, the 'right' way. So damn tired on Friday, I didn't do it, mainly because I knew where I was going. Just happy that I caught this little issue, will be interested to see if your unit does the same thing. It's always been my impression that gps units are like snowflakes when it comes to routing.

Well Jim, both my Montana and Nuvi 780 looked like they saw some kind of junction at Metcalf street but they didn't say to get off the 417 to get to it. I can see how it would be confusing, though.


Sent using strings and tin cans and Tapatalk

[ducnek]

Originally Posted by ducnek

Nope it's not on the list. How do I get it there?

Nevermind I think I figured it out! D'oh!

[Emoto]

Originally Posted by ducnek

Nevermind I think I figured it out! D'oh!

One thing to bear in mind is that CN will tend to take precedence over all your other maps unless you disable it.

[Drif10]

Originally Posted by Emmbeedee

Well Jim, both my Montana and Nuvi 780 looked like they saw some kind of junction at Metcalf street but they didn't say to get off the 417 to get to it. I can see how it would be confusing, though.


Sent using strings and tin cans and Tapatalk

Figures.

Like I said, never found any two units routed the same. Any code geeks have any idea why? Not that it'll make any diff, my own curiosity more than anything.

[Drif10]

Originally Posted by Emoto

One thing to bear in mind is that CN will tend to take precedence over all your other maps unless you disable it.

Yes.

This has always been the case in any garmin.

[BigOgre]

Originally Posted by Emoto

One thing to bear in mind is that CN will tend to take precedence over all your other maps unless you disable it.

Came across a very similar issue just this morning and figured if I searched enough I'd find an answer. But seeing as you all brought it up . . . CN loaded into internal memory. 100k Topo loaded onto SD card. Route developed in BC and sent over - all works fine but only if SD card is left out. Once I drop the card in, Montana tells me route doesn't match map. Check of map settings only shows Topo installed and enabled (along with factory loaded maps) and CN seems to have disappeared. Shut down, remove card, and CN shows back up as enabled. I'm doing something wrong, right?

[atlas cached]

Originally Posted by BigOgre

Came across a very similar issue just this morning and figured if I searched enough I'd find an answer. But seeing as you all brought it up . . . CN loaded into internal memory. 100k Topo loaded onto SD card. Route developed in BC and sent over - all works fine but only if SD card is left out. Once I drop the card in, Montana tells me route doesn't match map. Check of map settings only shows Topo installed and enabled (along with factory loaded maps) and CN seems to have disappeared. Shut down, remove card, and CN shows back up as enabled. I'm doing something wrong, right?

Sounds like your City Nav and Topo have similar FID numbers....

Did you use MapSource to send them, or BaseCamp?

[Emmbeedee]

Originally Posted by BigOgre

Came across a very similar issue just this morning and figured if I searched enough I'd find an answer. But seeing as you all brought it up . . . CN loaded into internal memory. 100k Topo loaded onto SD card. Route developed in BC and sent over - all works fine but only if SD card is left out. Once I drop the card in, Montana tells me route doesn't match map. Check of map settings only shows Topo installed and enabled (along with factory loaded maps) and CN seems to have disappeared. Shut down, remove card, and CN shows back up as enabled. I'm doing something wrong, right?

Sounds like a job for JaVaWa Device Manager. Download it, connect the gps and run JDM, and it'll likely tell you what's wrong and how to fix it.

[TravellingStrom]

Originally Posted by dlh62c

A route will always contain at least two via points. In your route, Point A is via point 1 and Point B is via point 2. You can add more, but they can total no more than 50.

daryl

Well to me they are not via points. I am going from a to b, if I go Via C then that is a via point, that is what the word means. Obviously Garmin use the word different but your point is taken

[cablebandit]

I don't think the via points are via points in an A to B route. Like I said I routed 4100 miles to Alaska from Pennsylvania. It sounds like you are saying that each turn point is a via. It's not since the unit made the route. If I add a via point in basecamp it's announced as a via point on the turn by turn directions. There are well over 100 turns in the route I made (that the unit routed) and there is no issue with routing that way.

[Emmbeedee]

Originally Posted by cablebandit

I don't think the via points are via points in an A to B route. Like I said I routed 4100 miles to Alaska from Pennsylvania. It sounds like you are saying that each turn point is a via. It's not since the unit made the route. If I add a via point in basecamp it's announced as a via point on the turn by turn directions. There are well over 100 turns in the route I made (that the unit routed) and there is no issue with routing that way.

I think you're right - via points are things you've added to force a route to go a certain way. If the gps creates the route, the locations it selects for turns, etc, are not via points.

[Emmbeedee]

Only 8 posts left to make then I'll have posted more than DRTBYK! I'm in the final stretch, unless he comes back soon.

[Emmbeedee]

Originally Posted by Drif10

Figures.

Like I said, never found any two units routed the same. Any code geeks have any idea why? Not that it'll make any diff, my own curiosity more than anything.

I think we need to take this up with Garmin Cartography. Here's a series of screen shots I made tonight, while simulating a route through the 417 to Alexandria. As seen in the shots, it clearly looks like you're to get off at the Metcalfe street exit. Even the lane indicator says so.

[slowpoke]

Montana Fail. Went to use it for the first time going to baja. After about 30 minutes of working fine, the screen goes crazy. Side ways, upside down, right side up, then it shuts off. Happend every hour andore frequent as the days went by. I know the connection is good because the Montana powers up and down as the bike does. Garmin tech support never even heard of this. Sent it back today and they're going to send me another one. Irritating because we wen to baja and it was needed.

[Emmbeedee]

Originally Posted by slowpoke

Montana Fail. Went to use it for the first time going to baja. After about 30 minutes of working fine, the screen goes crazy. Side ways, upside down, right side up, then it shuts off. Happend every hour andore frequent as the days went by. I know the connection is good because the Montana powers up and down as the bike does. Garmin tech support never even heard of this. Sent it back today and they're going to send me another one. Irritating because we wen to baja and it was needed.

Sounds like two common issues: you need to lock the screen orientation through Setup/Display/Orientation, and you need an earplug in the battery case to stop the shutdowns.