How to start route , but not from start on Nav 5

How do you join a created route, but not from the start, without it taking you back to the start. On my Zumo it asks you if you want to navigate back to the start, you can select no and then manually navigate and join the route, can't seem to do this on my new Nav 5.

Hi.

Did you sort this out? As another ex-660 user, I can't figure out how to start an existing custom route without going to a specific waypoint.

I believe that you do have to tell it where you want to join the route from I.E the next way point or shaping point.

Where is Wapping when you need him

On my 660, I just go the nearest point of the route, and continue on it.

When you select the route in trip planner and push go, the next screen is a list of the waypoints on the route.

Pick the one you want to start from and away you go.

One of the few things I've managed to figure out on this piece of junk...

richardbd said:

When you select the route in trip planner and push go, the next screen is a list of the waypoints on the route.

Pick the one you want to start from and away you go.

One of the few things I've managed to figure out on this piece of junk...

Click to expand...

So does this mean you really need to rename the waypoints so that you know exactly where they are to be able to join the route?

I've been thinking about swapping my Zumo 550 for a 590LM but aware that if I swap for an LC the Nav 5 would surely make sense to enable use of the twirly wheel.

OK, after a half-day out with the Nav 5, I've got some answers, and more questions.

Regarding the route, it seems if you choose any of the waypoints it will pick from there, but the cool thing is that it seems to also take into account shaping points to get to the first waypoint selected. So today for example, I had a start waypoint, a coffee stop waypoint and an end waypoint. However, between each waypoint I had about 20 shaping points. Whenever I started the route, my list of choices were only the start, coffee stop and end. When I selected the coffee waypoint after a fuel stop, the Garmin took me to the waypoint via all the shaping points. I was concerned that it might go direct there via the fastest route, but it still seemed to take into account all the shaping points between my current location and the selected waypoint.

I'll need to do it a few more times to be sure, but going to a chosen waypoint but using all the via points en-route would be a very good way to handle it.

The only thing that was baffling was that unlike the 660, when the unit powered back up after a stop it didn't seem to want to continue the route. It drew a straight pink line direct to the next waypoint and the arrival time was total nonsense. However, selecting the next waypoint from the trip planner app kicked things off again. It seems a backward step to have to use trip planner again each time a route is interrupted by the Nav 5 powering down.

Bobbin-Man said:

So does this mean you really need to rename the waypoints so that you know exactly where they are to be able to join the route?

Click to expand...

yes...

Hamslay said:

OK, after a half-day out with the Nav 5, I've got some answers, and more questions.

The only thing that was baffling was that unlike the 660, when the unit powered back up after a stop it didn't seem to want to continue the route. It drew a straight pink line direct to the next waypoint and the arrival time was total nonsense. However, selecting the next waypoint from the trip planner app kicked things off again. It seems a backward step to have to use trip planner again each time a route is interrupted by the Nav 5 powering down.

Click to expand...

add it the list of dumb things the Nav5 does that none of the earlier ones did. I reckon this model was designed by a TomTom sleeper working at Garmin!

Interesting as I used my nav v for the first time today and after a stop for coffee the route was still active and carried on like my old 660 did. The unit was powered off and in the top box for the duration of the stop over. Our stop was at a via point though, so maybe it's intelligent enough to realise?

My stop was at a waypoint too. I just left the GPS on the bike when I switched off the ignition. The same thing happened earlier in the day when I stopped for fuel which wasn't at a waypoint or shaping point.

Odd. Oh well. In general I like the unit, and so far no regrets switching from a 660. If only I could stop the bloody thing creating favourites...

Hamslay said:

My stop was at a waypoint too. I just left the GPS on the bike when I switched off the ignition. The same thing happened earlier in the day when I stopped for fuel which wasn't at a waypoint or shaping point.

Odd. Oh well. In general I like the unit, and so far no regrets switching from a 660. If only I could stop the bloody thing creating favourites...

Click to expand...

I think if you leave it alone and just start riding it picks up where it left off or at least thats what mine does

My Nav V is definitely doing something odd.

I went out for another ride today A->B->C. Stopped at waypoint B for a coffee. Got back on the bike and the satnav didn't show any pink route. Zooming out, there was a pink line straight between waypoints as if it were in offline mode. Starting riding it still didn't put the line back on the road. I had to cancel the route, restart Trip Planner, chose the route and set waypoint C as a destination before it would recalculate and convert the pink line between waypoints back to pink roads. Every time I stop en-route, I end up with pink straight lines across the map. What the hell is that all about?

I have a 3000-mile ride starting next week. I wish I still had my 660.

Worth checking all its settings to see if something is checked/unchecked?

richardbd said:

add it the list of dumb things the Nav5 does that none of the earlier ones did. I reckon this model was designed by a TomTom sleeper working at Garmin!

Click to expand...

Unfortunately, just like the addition of a Wiggly Roads calculation option, Garmin has listened to all the really dumb bikers who asked them to do just that.

If in doubt, look at all the threads from bods telling us that they never plot anything, they just ask their device to take them from A to B as they'll discover roads that they never would have found otherwise. Add in bods not knowing or wanting to learn (because they can't be arsed) the difference between a waypoint and a shaping point and you can see where everything is heading.

Actually, depending on how anyone choses to use the device and the latest software, the ability to chose between a waypoint and a shaping point (which has been there since the first days of Mapsource, so it's nothing new) is quite useful. For instance, BaseCamp allows you to set specific halt times at certain points - a lunch stop for an hour, for instance - and the balance of the route will be extended for an hour's duration. Of course, the canny operator could just add one hour to the time and come to the same answer.... But some can't manage that, nor can they work out how to display or find 'Estimated arrival time' and / or 'Distance to destination' functions.... But they can find data on how often they've used their brakes and when their next service is due.... Vital to know on their way to Tesco or when crossing the Sierra Nevada wastes.

Hamslay said:

If only I could stop the bloody thing creating favourites...

Click to expand...

If you are creating waypoints (as opposed to shaping points) along your route, then they will appear as Favourites.

Moving on to your routing display problems, which are interesting. To be honest, I am at a loss to explain why, when you stop at a waypoint, on restart the route displays as straight lines. The only thing I can maybe guess at is:

1. You created a route from A to C via B. In this A, B and C were created as waypoints.

2. In between A, B and C you created a number of routing points, to force your route along certain roads that you chose to use.

3. When you stopped at B (your waypoint) you maybe didn't pass through it exactly. For instance, if you plonked the waypoint in the middle of a town (some people do) but stopped at a cafe you know on the ring road, then the device might (this really is a guess) have trouble displaying the route on restart.

Apologies for the guess. It's not something I've seen in 1000's of miles with my two Nav V's but there again I rarely - if ever - use waypoints within routes I've plotted. This leads me to think that there is either something wrong with the way you are using the device (or creating your custom routes) or with the device itself. The older devices used to display straight lines when they couldn't calculate a route; a route created in a different map set for instance. But your route was apparently displaying properly.... Right up to the moment you stopped at waypoint B... Which is very odd.

==============

Edit:.I was going to suggest you could try is changing the waypoint B to a shaping point to see if the same thing happens. But I now see that you had the same problem when you stopped at a fuel station that wasn't a waypoint or shaping point on your route....

I am now just wondering whether it might be as simple as twice you stopped at a point where the device could not get a decent satellite signal, so it could not pinpoint its exact position, so struggled to calculate / display the route, perhaps? I am now really clutching at straws. I'm afraid I can only leave you with four guesses:

1. Operator error, though you are well versed in creating routes, using viapoints and shaping points and have answered the question posed in the opening post, so that might well be unlikely. You've also clearly understood the advantages of using shaping points and waypoints properly, which is great.

2. Some (unknown) glitch in the way you create your custom routes.

3. Poor satellite signal on restart.

4. Bad luck / an oddity twice, which you'll never see again.

It would be interesting to hear if you ever find a solution, as it's not a problem I've seen.

If you send the route to Garmin and a clear explanation of where and how the problem manifested itself (screen shots or pictures of the device displaying the problem are useful) there is a very good chance they can help you. It's what I did when the early Nav V's - or maybe it was the 660's I forget - were struggling loading maps / displaying routes fast enough due to poor satellite signal location difficulties in the Alps. It was all mended in a subsequent software update.

Hey Wapping. Thanks for taking the time to send a long reply.

I've just done another test, and it's becoming a bit clearer. I'm using Tyre, so that may be a contributing factor to the problem.

I did a route that starts a mile from my home. Although in Tyre the start is marked as a shaping point, Tyre saves it as a waypoint in the GPX file with <trp:ViaPoint />. There are then 3 shaping points in the file, indicated by <trp:ShapingPoint />, before the first real waypoint (<trp:ViaPoint />). There are then 3 more shaping points and then the end of the route which in the file is <trp:ViaPoint />.

So the file, trimmed immensely, looks like:
<trp:ViaPoint />
<trp:ShapingPoint />
<trp:ShapingPoint />
<trp:ShapingPoint />
<trp:ViaPoint />
<trp:ShapingPoint />
<trp:ShapingPoint />
<trp:ShapingPoint />
<trp:ViaPoint />

So far so good. But when I use Trip Planner to start the route, it shows road navigation to the start only. All subsequent points are joined by straight lines, as if it stopped calculating at the first point. Is this normal??? I'm sure my 660 would show the whole route mapped onto the roads, although of course that didn't support shaping points.

Anyway, I head off from home, and I'm following the navigation to the first point, a red flag. As soon as I get there, lo and behold the pink line is suddenly a straight line to the next shaping point. Even riding to the shaping point, it just does another straight line to the next shaping point. If I cancel the route, start it again and select the first real waypoint, suddenly the pink line follows the road again heading off to the waypoint. But here's where it gets weird. Again the map only follows roads as far as the red flag. After that, all points are connected with straight lines. True enough, I reach at my proper waypoint, the red flag disappears, and the pink line becomes a straight line to the next shaping point....

So what appears to be happening is that whenever I reach a waypoint that exists in the GPX file as <trp:ViaPoint />, navigation ends and the rest of the route is shown as straight lines between shaping points. To actually resume navigation, I have to pull over, cancel the route and restart it from the next true waypoint.

This can't be right is it? Most of my rides have 2 or 3 waypoints where I expect to stop, each one linked up with shaping points. I certainly wouldn't expect navigation to end at each waypoint. At the moment, navigation ends as soon as I reach the waypoint that is actually the start of the ride!!!

For completeness, here's one of each of the shaping points / waypoints from the file.

<rtept lat="52.05865" lon="-0.33162">
<name>Unnamed Road</name>
<extensions>
<trp:ShapingPoint />
<gpxx:RoutePointExtension>
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
</gpxx:RoutePointExtension>
</extensions>
</rtept>
<rtept lat="52.05679" lon="-0.31079">
<name>Stanford Road</name>
<extensions>
<trp:ViaPoint />
<gpxx:RoutePointExtension>
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
</gpxx:RoutePointExtension>
</extensions>
</rtept>

I guess I'm going to have to fight with Basecamp for an evening and try to create the same 3-mile loop and compare how the Nav V handles it.


edit:

OK, I imported the Tye GPX file into Basecamp and it just showed all the points joined up with straight lines. Nothing on the road at all. I had to double-click the route and click Recalculate and suddenly Basecamp mapped the entire route on the roads. Exporting the file again, here's Basecamp's version of the above GPX section:

<rtept lat="52.058650022372603" lon="-0.331620024517179">
<time>2015-05-27T17:01:53Z</time>
<name>Unnamed Road</name>
<sym>Flag, Blue</sym>
<extensions>
<trp:ShapingPoint />
<gpxx:RoutePointExtension>
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
<gpxx:rpt lat="52.05862345173955" lon="-0.331605607643723">
<gpxx:Subclass>06002D475B01A29B07002116000089011300</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="52.058758735656738" lon="-0.330963134765625" />
<gpxx:rpt lat="52.058758735656738" lon="-0.330963134765625" />
<gpxx:rpt lat="52.058758735656738" lon="-0.330963134765625" />
<gpxx:rpt lat="52.058758735656738" lon="-0.330963134765625">
<gpxx:Subclass>06002D475B01A29B07001F000E00DA3C2902</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="52.058758735656738" lon="-0.330963134765625" />
<gpxx:rpt lat="52.058887481689453" lon="-0.330362319946289" />
<gpxx:rpt lat="52.059144973754883" lon="-0.328946113586426" />
<gpxx:rpt lat="52.059144973754883" lon="-0.328302383422852" />
<gpxx:rpt lat="52.059187889099121" lon="-0.311779975891113">
<gpxx:Subclass>06002D475B01101B16001F020E00BC3B7400</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="52.059187889099121" lon="-0.311779975891113" />
<gpxx:rpt lat="52.057685852050781" lon="-0.310921669006348" />
<gpxx:rpt lat="52.056791419163346" lon="-0.310767441987991">
<gpxx:Subclass>06002D475B01101B16002117000033007400</gpxx:Subclass>
</gpxx:rpt>
</gpxx:RoutePointExtension>
</extensions>
</rtept>
<rtept lat="52.056789994239807" lon="-0.310789989307523">
<time>2015-05-27T17:01:53Z</time>
<name>Stanford Road</name>
<sym>Flag, Blue</sym>
<extensions>
<trp:ViaPoint>
<trp:CalculationMode>FasterTime</trp:CalculationMode>
<trp:ElevationMode>Standard</trp:ElevationMode>
</trp:ViaPoint>
<gpxx:RoutePointExtension>
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
<gpxx:rpt lat="52.056791419163346" lon="-0.310767441987991">
<gpxx:Subclass>06002D475B01101B16002116000033003300</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="52.056441307067871" lon="-0.310707092285156" />
<gpxx:rpt lat="52.056441307067871" lon="-0.310707092285156" />
<gpxx:rpt lat="52.055754661560059" lon="-0.310235023498535">
<gpxx:Subclass>06002D475B01F4A107001F002B00EF6A1A01</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="52.055754661560059" lon="-0.310235023498535" />
<gpxx:rpt lat="52.054853439331055" lon="-0.309591293334961" />
<gpxx:rpt lat="52.054123878479004" lon="-0.309247970581055" />
<gpxx:rpt lat="52.053651809692383" lon="-0.308904647827148" />
<gpxx:rpt lat="52.0504389423877" lon="-0.305655989795923">
<gpxx:Subclass>06002D475B01F4A107002117000024001A01</gpxx:Subclass>
</gpxx:rpt>
</gpxx:RoutePointExtension>
</extensions>
</rtept>

Curiouser and curiouser

edit2:

I've put Basecamp's GPX file into the Nav V and it acts completely different. With the Tyre version, import is instant and does no visible calculation. With the Basecamp version, it ticks up the Calculation % for several seconds. Also, the Tyre route shows no Travel Time in the Trip Planner which I'd wondered about before. The Basecamp route has a Travel Time of 20 minutes. Most importantly though, the Basecamp version of the route, when previewed with the Map button, shows the entire route along the correct roads, rather than straight lines.

So it seems at the moment that although Tyre is correctly creating a GPX file with shaping points and via points, it is missing all of the extra detail that allows the Nav V to calculate the entire route.

That's a real bugger. A week tomorrow I head off on a 3000-mile trip with 10 days of Tyre files.

Does your NAv unit have Tyre ?

Only asking as that may well be the issue here. The unit is designed to work with Basecamp
If it helps see my post on how i use basecamp

Aha, a bit more emerges....

Try it without using Tyre....

Your device was showing all the classic signs of being unable to display a route between points that were not actually on roads. The device does its best, gives up and displays straight lines. It's much as you would do when explaining how someone would get to Manchester from London, standing in the street, without a map.

Report back when ready.

Seriously, the best way to learn how to use BaseCamp (which really is very good and very easy) is to plan and then use it on a holiday such as you are about to embark on. Too many people just muck about and give up, too quickly. Trust me; I cracked it and wouldn't know one end of a computer or software from another.


PS Try it using Moto Go Loco, which everybody is raving about, too.

Cheers guys.

Wapping, you could well be right that shaping points that the unit does not recognise as being on a road are not used in the calculation. An interesting, temporary and frustrating workaround is that if I go into Trip Planner and edit the Tyre-generated route and convert all the shaping points to waypoints, the unit then maps the entire route correctly, along with travel time.

I think Tyre worked great on my old 660 where every point was generated as a waypoint. The problem comes with me switching to a unit that supports shaping points, and Tyre not producing the file quite right.

Unfortunately I've already distributed the Tyre files to my trip companions who I'm sure will have no problems at all with their 660s. How ironic that I spend £500 to get the latest whizzy satnav for this trip and now my own routes don't work!

I'm either going to have to go back into Tyre and convert every shaping point to a waypoint, or pull all 10 GPX files from the Nav V, import them into Basecamp and let it "fix" the shaping points. Or just follow my friends with their working 660s (one of which was mine untul 3 weeks ago!)