Nav V not following set route

Status
Not open for further replies.
I would expect a sophisticated unit to recalculate the set route from my new start point and rejoin it at the nearest point. Obviously this not how it works. Not sure now how I'd add a deviation off a set route & then back to it.

If you had a via point somewhere near to where you want to rejoin your route (these are the announced points) then you could restart your planned route and choose this via point from the list that you are presented with when you press 'Go'. It will calculate fastest/shortest/curviest route to this point and then carry on with the preplanned route.

If you don't have a convenient via point then you've got two other options. You could select a point on your planned route - such as a town - and get the GPS to take you there, then restart the original route. You may need to use the 'skip' button to skip any points that you have already passed. Or you turn off recalculation, run the original route (select the first point in the list) and use the map display to simply ride back to the magenta line. Once you're back on the route you may again need to use 'skip' to stop the device taking you back to a point near the start.
 
Although in all fairness I would have expected the unit to follow a route if I selected a route , otherwise why have the option?
This also explains why when I saw Dachau signposted as I was on a route and navigated to it (see earlier post) and then re selected the route it completely missed out Alianz Arena. I would expect a sophisticated unit to recalculate the set route from my new start point and rejoin it at the nearest point. Obviously this not how it works. Not sure now how I'd add a deviation off a set route & then back to it.

I'm going to use mine, for the first time, in three weeks and I would have had the same trouble as you. I too thought that it would automatically take you to your chosen start point (nearest on route) from wherever you are. I haven't made the routes on basecamp yet but will now be extra careful when choosing start points. Having a waypoint near your chosen start point also sounds a good idea.
 
Reading posts on this site seems to show that Mac users including myself seem to fair better with BaseCamp. The PC version is a very different program. Used MapSource with my 2610 for many years until I changed to a Mac. Been using BaseCamp since 2011. No real problems that I can recall.

I've used Basecamp on a PC and, more recently, on a MAC. I have to say the MAC version is a lot better & more user friendly. That's saying something considering I am a lifelong MAC hater.
 
Just changed from 660 to 590 using Basecamp on a Mac and I have learned a whole heap from this thread. Thanks to all concerned :D
 
I'm going to use mine, for the first time, in three weeks and I would have had the same trouble as you. I too thought that it would automatically take you to your chosen start point (nearest on route) from wherever you are. I haven't made the routes on basecamp yet but will now be extra careful when choosing start points. Having a waypoint near your chosen start point also sounds a good idea.

Yes always worth having a few waypoints in your route, when you activate your route, the Nav V will only give you waypoints as options to go to, shaping points are not in the list of options.
As Wapping mentioned here earlier if you select the last waypoint in the list, the Nav V will take you there (fastest time if that's the calculation mode) and any set route will be discarded, I have experienced this myself to great pain.
This (choosing the last waypoint) is deemed user error, however to my mind the set should work as most people would expect, you have carefully built and put a route into trip Planner you would believe the Nav V will endeavour and be manufactured for its software to follow it road by road.
To re-calculate (change) a route at any given opportunity is poor software design from Garmin.
Also interesting that Garmin sees routes as "unplanned trips" when actually they are usually extremely well planned, however the software algorithm seems to be built to ignore as soon as, or wherever, possible.

Any how Garmin rant over, if you have a waypoint in there (close to the beginning of your route) it helps as an option to choose it when activating the route, and for the Nav V to follow the rest of the route including any shaping points after it. Waypoints have priority.

If for example your first waypoint (not the start point) was half way down your route and you have shaping points prior to it when you activate your route and select that first waypoint (because it will be the first option) the shaping points prior to it are ignored and the Nav V builds its route to that waypoint by the calculation mode (i.e. fastest time, shortest dist).

Also if you have say five waypoints and you selected the third, the fist and second waypoints are then ignored (including all shaping points to that third waypoint) and the Nav V will take you straight to the third waypoint by the set calculation mode.
Basically when your selecting a waypoint in your route you are requesting the GPS to take you straight there by the calculation mode so be careful when choosing.
 
Thanks for the clarification - I'll maybe make a start to creating routes at the weekend and have two waypoints near the start of all my routes. Thanks again - as they say "the devil is in the detail" and their appears to be a lot of detail doing this successfully.:beerjug:
 
I agree with your comments - that certainly mirrors my experience.

It would be so simple if, when selecting a route planned on Basecamp and imported into the Nav, it would simply allow the user to select the route and then direct him/her to the nearest part of it and thence continue along as planned without the user having to identify the start point from a list. The waypoints identified in the initial selection screen are often not recognisable and it is sometimes difficult to determine where each is. The answer as you suggest is to create a waypoint early in the route so that it can be selected.

Hope I've understood and interpreted your comments correctly!
 
I agree with your comments - that certainly mirrors my experience.

It would be so simple if, when selecting a route planned on Basecamp and imported into the Nav, it would simply allow the user to select the route and then direct him/her to the nearest part of it and thence continue along as planned without the user having to identify the start point from a list. The waypoints identified in the initial selection screen are often not recognisable and it is sometimes difficult to determine where each is. The answer as you suggest is to create a waypoint early in the route so that it can be selected.

Hope I've understood and interpreted your comments correctly!

Yes you have :thumb2
 
Nothing has really changed. On earlier devices you were asked if you would like to 'Navigate to the start of the route'. That option is still there, it is just shown on a screen.

In the past, if you said, "No" then you received an instruction to "Navigate to highlighted route" ie. Work out your own way of getting onto the route. That still exists on the new devices.

The OP's problem only occurred because he was not on the route he created, when he selected 'Take me to the end point'. That would have happened just the same on earlier devices. Had he been on his route or at its start point he could have selected his end point quite happily.

Get used to using the modern devices. The trouble, if there is one, is that bods want umpteen different things, which Garmin then seek to cater for. Fellows then go away on holiday, without thinking whether they really know how their all singing all dancing state of the art Navigator V works. Once they learn, it's all very easy as the OP confirms in post #17.
 
Thanks for the clarification - I'll maybe make a start to creating routes at the weekend and have two waypoints near the start of all my routes. Thanks again - as they say "the devil is in the detail" and their appears to be a lot of detail doing this successfully.:beerjug:
I usually set my start point a little bit away from my actual location and then choose navigate to.

Sent from my SM-G920F using Tapatalk
 
from what i have read on this forum with reference to garmin sat navs it seems most people expet them to obey a set of rules that they themselves think it should use, and when it does not behave that way blame the unit. I admit there are a few things that dont seem logical and some are even stupid, but thats the way it works and we have to deal with it, take the op problem he presumed that although he was not at the start point of his route, that selecting his destination would take him onto the route he had built and then follow it to his destination, but infact by selecting this he told the sat nav to ignore the route and take him to his destination using its own routing preferences that the op presumably had setup himself, just the same as if he had picked a random waypoint or any poi or even any of his favourites, it may seem daft or counter intuative but thats the way it works.
Take a bit of time to understand the way the unit works and if you can not figure it out, do like the op did and ask the question, because unless its a faulty unit or mounting hardware related or even a limitation of the unit any other problems will be user related.
 
(Newer zumo's 350, 390, 590 & Nav V) The concept of being on the route when you activate it and select the last waypoint ('Take me to the end point') means the GPS will then follow your desired route is a myth, it doesn't, it will take you to that waypoint by the calculation mode and your route will be ignored. (unless some of your route happens to qualify within that calculation mode)

Tested this out today with my 590 I have a route built on it with multiple waypoints and many shaping points, over 12 miles.

I added the a track of my route to show on the map as a reference, stopped the bike on a road just after the start of my route and selected the destination waypoint, compared the calculated route to the
destination with the track. They were completely different, which confirms regardless of where you are it all depends on which waypoint you select.

IF your considering going away and don't quite know how the Nav V works, I would recommend building a few test routes and using it to get used to how it works. Using familiar routes around where you live before you venture on holiday and find out it wont do what you expect.
Also use a track of your route every time, if the track line disappears from the magenta road your following while on your route, the GPS will have re-calculated another way. With a track on the map you realise just how often this happens.
Apps - Tracks - choose route - Spanner Top LHS - set colour - (I use black) save - tick "show on map"
 
All good info, and has been said get use to the way it works before using it, or you may end up going somewhere you dont want to.
 
I used my Nav V today, to try out all the things I've learnt about running routes. It behaved faultlessly.

In BaseCamp I plotted a pre-planned roughly circular route, starting and ending about 40 miles from home. The start and end points were waypoints, by default. Into the route I inserted several unannounced shaping points (just to force the route down certain roads) and three waypoints, all of them announced.

Leaving home, I summoned up the route into the device. I was then presented with a choice of going to the start, to the end or to one of the three intermediate waypoints. As I was 40 miles away from the start point but knew that I needed to go there to meet someone, I chose the start point as my objective. The device very quickly:

1. Plotted me a route from home, to a destination 40 miles away.

2. It did this according to my preferences.

3. It tacked it onto my pre-planned route, without altering the balance of my pre-planned route in anyway

4. I rode the device generated 40 miles, purposley going off-route several times. When prompted, I asked the device to recalculate for me. Each time it did it perfectly, always without altering the pre-planned portion.

5. On arriving at my start point, the route I had pre-planned started running seamlessly. I did not have to start it manually.

6. During the day, I purposley skipped one of the intermediate waypoints. Again, the pre-planned route did not miss a beat, it only stopped when I reached the end point.

7. Around in the broad circle I went. It all went completely to plan.

Love your Nav V and it will love you.
 
As ever - put the right info in - you get the desired response out......

The NAV V is dependable and alongside the iwheel on the GS is a superb bit of kit.

Rik
 
6. During the day, I purposley skipped one of the intermediate waypoints. Again, the pre-planned route did not miss a beat, it only stopped when I reached the end point.



I would be seriously pissed off if my 390 did that! If I go to the trouble of inserting a waypoint into my planned route it is because I really want to get to that point, otherwise I would use a via point.

John
 
Relax, John

I chose to miss out the waypoint. It was created just as a point on a side road, just so I could miss it out and check that the Nav V's software worked just as I imagined it would. The device did not force me to miss out the waypoint, I chose to. The device allowed me to skip the waypoint and continue on my pre-planned route as if nothing had happened; in short, it obeyed me right through to the end of my pre-planned route.

Me? I'd be pissed off (or at least a bit miffed / confused) if the device refused to allow me to skip a waypoint.

I can, without screwing my eyes shut too hard, imagine circumstances when I might want to skip a pre-planned waypoint during a ride; others may struggle. Here's an example:

I plot a route from A to D going via several shaping points and two waypoints, B and C. Waypoint B is a rendezvous point where I have planned to meet several likeminded bikermates for a day's hooning of our awesome steeds through the twisties. I want to be sure to get there, so it's a waypoint. Waypoint C is a great biker friendly cafe, which we want to be sure to visit, so I make that a waypoint, too. Off we hoon, pausing en-route only to press some flowers, during which we meet up with another bikermate coming the other way, who engages us in bikermate banter:

Us: Hi bikermate

Him: Hi, bikermates, where you hooning to?

Us: To the cafe at (insert name) as we hear it's the bollox and then on to biker friendly digs at (insert name)

Him: Cool, but the cafe has burnt down. I suggest you skip it out, mate

Us: Cheers, bikermate. But, wait, we made it a waypoint as we wanted to be sure that, no matter what, we would always get there. Now you tell us it's ashes and we are wasting our time. The whole day is ruined. We'll end up always being sent to a burnt out cafe and it's all Garmin's fault; pile of shite it is.

Him: Don't worry bikermates, I see you have the awesome Nav V. Simply use the skip button or you can choose to turn the waypoint into a shaping point, right now from within the device itself, all without altering your pre-planned route.

Us: You saved the day, unknown random bikermate, mate!
 
Relax, John

I chose to miss out the waypoint. It was created just as a point on a side road, just so I could miss it out and check that the Nav V's software worked just as I imagined it would. The device did not force me to miss out the waypoint, I chose to. The device allowed me to skip the waypoint and continue on my pre-planned route as if nothing had happened; in short, it obeyed me right through to the end of my pre-planned route.

Me? I'd be pissed off (or at least a bit miffed / confused) if the device refused to allow me to skip a waypoint.

I can, without screwing my eyes shut too hard, imagine circumstances when I might want to skip a pre-planned waypoint during a ride; others may struggle.


You really are a patronising twat sometimes!

John (very relaxed, thank you)
 
Status
Not open for further replies.


Back
Top Bottom