Navigator V Map problem

I do the same, import the file by "send to device" then either choose the SD card or the Device.
Weirdly, the route shows differently in BC to start with though. If i click the route form my Home Address to the ferry port in the more basic map it gives me "basic route" with a lot less detail on it. If I click the map that is stored in my SD card, It takes me the route I actually want to go. I think the final key here is working out why it seems to want to continue to use the older less detailed map as opposed to the newer one?
So in "my maps" do you have all the maps ticked?
CN Europe NTU 2017.10 ALL
Europe DEM
CN EUROPE NTU 2017.10 3D

My 590 only has Europe DEM & CN Europe NTU 2017.10 all both ticked
 
I opened the route in Mapsource (no amphibian predilections required!) and it certainly looks like it should work. Being picky I would point out that several of the waypoints are just off the route. It pays to really zoom in and check each one. If it were me I would replace the waypoints with via points. When I do this in Mapsource it is very easy to see where I have placed a point just off the road on the route as it appears as a green dot. A proper via point remains as small dot. In Mapsource such via points are automatically marked as do not announce for the device.

As it is there will be lots of minor diversions to visit these rouge waypoints, annoying but you will get there.

John


That's true but somewhere or somehow the OP's device is carrying out a recalculation to display garbage, too. Now that I have thought about it, I don't think your and his problems are the same at all. There are so many variables creeping into the OP's set-up that, short of a hard re-set and starting from square one, it's getting hard to suggest what to do. The good thing is that we and he know that there is nothing wrong with the OP's route or with his BaseCamp itself.... but somewhere in the device most possibly there is a glitch. Most device centred glitches are easy to spot if you have the device in your hands - as you know - but that option is not open to us.

In the meantime, here's a monkey with pond life.....

PB1897449.jpg.jpg
 
Wapping et al, you've all been helpful! I think we have cracked it.
Many thanks for your time AND effort!
 
Personally i'd temporarily remove the SD card and install the 2017.10 maps straight onto the device there should be enough memory (or has the Nav V got less memory than the 590?)

See if that fixes things
 
You two have, I think, missed the point. The OP has managed to apparently successfully create a route in BaseCamp (something alone that raises him above pond life) and transferred it to his device, something that others struggle with. His problem appears to be that the route displayed on his device carries little or no resemblence to that created on his computer.

Now, if you can solve that one problem we'll all be cooking on gas.

Don't know if this is relevant but watching some Youtube videos on the subject of Basecamp, I'm sure I remember on one video, the author suggested that before transferring the route to your device, that if you change the activity profile on you computer to driving instead of motorcycling, the route will not get changed.

Don't take this as gospel , but costs nothing to try it.
 
Doesn't have enough memory @Jersey GS. I bought the memory card the it told me that :)
Personally i'd temporarily remove the SD card and install the 2017.10 maps straight onto the device there should be enough memory (or has the Nav V got less memory than the 590?)

See if that fixes things
 
Thats the video by @jobybyrne I think? Yeah, I contacted him as well.....as so often is the case, without these gurus sat infant of the device, it's often to hard to work it out
Don't know if this is relevant but watching some Youtube videos on the subject of Basecamp, I'm sure I remember on one video, the author suggested that before transferring the route to your device, that if you change the activity profile on you computer to driving instead of motorcycling, the route will not get changed.

Don't take this as gospel , but costs nothing to try it.
 
What was the cause as it's now been cracked?

I believe it was to do with the "tick boxes" that were set as part of my device settings from BC. I unchecked them all and it appears to have done something positive?!!!
 
I did - good post. I hadn't actually realised exactly what tick boxes I was looking for initially. I've had a fair choice.
Thanks for the link though, could've saved a bit of time if i'd known more about BC to start with
 
All avoidances unticked on both

Each to his own, I prefer to use the avoidances feature as I often really don't want to use a motorway and never want to use unpaved roads if there is any alternative. I don't find using such avoidances causes me any problems when transferring my routes to the device. There is more than one way to use a SatNav, obviously unticking everything works for some, it's just not the only way.

John
 
I plot my own routes so decide which roads I use, not BaseCamp or my device. The problems on this thread were caused by having different avoidances on BaseCamp & the device. They need to be as close as possible to avoid recalculations as the op was experiencing. Unchecking them all from the start means new users especially can start with a level playing field.
 


Back
Top Bottom