Whiskey Tango Foxtrot...
Sat, 12/28/2013 - 1:06am
 |
16 years
|
My 3590 suddenly responds with "The route is too long. Navigation instructions are added as you approach the destination" when it is turned back on after downloading routes from Mapsource. After the message is displayed, I checked and found that none of the routes have been loaded in.
I have done both hard and soft unit resets and even reinstalled the latest firmware, but nothing seems to fix the problem. I've done these same route downloads off & on successfully for the last 18 months with no problems.
Do you think I've screwed something up in the unit or that maybe the unit has gone blink? It's still within a 2 yr warranty, that might be a way out of this mess.
.
It sounds like your routes are too long. Routes with many turns will typically cause this message. (Note that new maps and/or new firmware can cause different routing "length" in terms of routing complexity.)
Break them up into segments such as one day length per segment.
BTW, working as designed.
I agree with MM
When I take a multi day trip - sometimes 10-15 days of driving - I break it down "usually" in 1 day travels for routes ! Sometimes I even break into 1/2 day routes.
That way if I make a modification for one day I don't have to redo the total multi day route if I I foul up (heaven forbid) .
And I don't overload the routing processor !
Just my way of doing it !
MrKenFL- "Money can't buy you happiness .. But it does bring you a more pleasant form of misery." NUVI 260, Nuvi 1490LMT & Nuvi 2595LMT all with 2014.4 maps !
Maybe you're right.
It sounds like your routes are too long. Routes with many turns will typically cause this message. (Note that new maps and/or new firmware can cause different routing "length" in terms of routing complexity.)
Break them up into segments such as one day length per segment.
BTW, working as designed.
This is the first time I've downloaded those routes with the 2014.3 map version being on my 3095 unit. However, the routes are all less than 575 miles in length. I think I'll reinstall an earlier version of the map and try again just to see if that is what is causing the message.
Thanks for the info MM.