465T Routing/via point/stop error..
15 years
|
Hello, we have finally got the Garmin Nuvi 465t truck GPS to do OK for trucking with a lot of help from Map Source and the big RandMcnally Truck Map. The big issue is routing and stop errors. When creating multiple "via" points or way points for custom routing, even to the exact coordinate-in the lane of travel, once we get close to the point the 465 will say "Approaching """ then after the last 100 feet as we pass exactly through the point it says "recalculating" "please go 1.2 miles" and turn around" Thus we have to fumble with the unit while driving "hit route" then hit next stop...which can get frustrating as you may actually miss your next exit if you placed the point to close in Map source. The same happens when you have reached your destination. For example: "Approaching Pilot on right....As we get close to the driveway..."recalculating" please drive 6.3 miles and turn left on Joe Schmoes street (it's turning you around (but we are here). This issue seems to be a speed Vs Time issue at every via point or way-point. Reason...10-15 minutes later at Pilot, like in the example above, it will finally say, You have arrived at your destination, Continue or next stop. (So it is in the program) However, it would be inconvenient to stop at the via point in the middle of the freeway for 10-15 minutes for the nuvi 465t to recognize you have reached your final destination. I have called Garmin a couple times and they were amazed about my problem. In simulator mode, it works fine...but the vehicle (stops) at every point) There should be like a 1/8 mile buffer for these points and addresses or the option box should pop up right away letting you choose as you approach your destination or routing point. This gets frustrating and can be rather dangerous especially in heavy traffic. For originally $500, this GPS should be able to know this rather basic problem as my co-pilot knew. Any fixes to this routing problem? Thanx Jake
routing issues
Don't feel bad about your frustration. I've had some similar issues with routing using the 2011.1 maps.
First off, check Mapsource. Be certain it is routing the way you need, fastest time and not shortest route. I had the exact same problem (or at least very similar) laying out a route with waypoints. Changing Mapsource to fastest time fixed a lot of those errors.
My experience is the routing with 2011.1 is it needs to be thrown out and a new baby brought in. For years we have had problems with the routing engine and Garmin's map encoding equating ramps and access roads the same as mainline expressway lanes. Garmin will also route you off the expressway to local roads when the local roads may be shorter in distance, but definitely longer time because of lower speed limits and stop lights. An example can be seen by creating a route from the Pilot in Cambridge Ohio (N39.99650 W81.57761) to Greensburg, IN (N39.33766 W85.48496). Rather than keep you on the 270 bypass around Columbus, it routes you through the city.
ɐ‾nsǝɹ Just one click away from the end of the Internet
Same with 2010 map
Actually a slight improvement with Mapsource on 2011.1 with road and address updates and finally figured out that 294 in Chicago is usually faster as default. However I called out Garmin on Atlanta issue and also Cleveland. Again my main issue is the routing points themselves--as you approach them, it will always re-calculate you back to them and same for your destination as you must stop for at least 10-15 minutes for it to finally say "next point"? or "you have arrived. The Pilot is right here! Why is it saying recalculate when we exactly hit the point? Sometimes it the option to go to the next stop will be grayed out therefore needing to reload your entire route when driving (when it does the recalculate thing when you use an intersection as a via point "add as a stop" When you "blow" by that point, exactly, it will say "recalculating" and your route will be destroyed. (calling it up again all the way from the beginning, which is a bummer) So we always need to hit "next stop" manually..however, you hit a bump and hit the 3rd via instead of the 2nd...you will not be able to go back until you reload the entire thing. I called Garmin as this is a safety issue because we should not have to fumble with the route manually when we import our own custom points or add them as a stop on the unit it self. It would be nice if just one thing "pops" up saying "you have arrived, what would u like to do?" "Mark as done?" "Recalculate back" or "Go to next stop" (Again this works if you do stop near your point for a min of 10-15 minutes. But you must stop. Rolling exactly through the point will not cut it. What I am asking is a little more hands free automation.
Sorry for structural grammar, I have to write fast as we have to roll soon. Thx Jake
routing
Fixing the routing won't be a trivial matter in any event. There are so many different pieces that come into play. The saying, Garbage In, Garbage Out is as true today as when it was first used 50 years ago.
If the map data is bad or incorrect, then the routing will be bad. If the map data has too many points describing road segments, then the calculation time is too long and the data that has to be stored increases and it takes more processor power to search. There really are a lot of factors that weigh in that are not apparent when we say "Fix the freakin' routing!"
ɐ‾nsǝɹ Just one click away from the end of the Internet
Try this
I'm thinking an external antenna may help give you more accuracy. For $30 or so, it may be worth a try, and adds a lot of signal to the unit. I love mine!
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK