BaseCamp 4.4.2 Is Now Available

Then I'm told to go back to Mapsource.

I do not understand this...

As 'MrGPS' I made a training DVD about Basecamp (sorry: at this time only in dutch). This DVD is often used by 550/660 owners who want to switch from Mapsource to Basecamp. I also gove live-training, receiving direct feedback.
I often hear about import-trouble; with basecamp and mapsource. Looking deeper into a problem almost always leads to a logical explanation; usually some user-error. Once the error is corrected, the problem is solved.
Some routes made in a specific version of mapsource/basecamp (don't know which one) keep having errors; only solution is to re-draw the route manually.

In general I do NOT think there is any reason NOT to work with Baescamp - and no reason to switch back to mapsource.

Maybe this can help:
Some time ago I made two movies on importing routes in the zumo 660. In the first video I show different route-types and recalculation effects; in the second video I look at what happens after import in the zumo 660. It's all in dutch, but you might still recognize what I am demonstrating."

Only one video per message allowed; so I'll split:

Different routes/recalculations/glitches etc in basecamp:
http://youtu.be/WksUQ8CN_vE

The effect of the routes described in the first video; after import in the zumo 660:

http://youtu.be/-3sbqWIZWq0

Using the track as route-export basis is a splendid way to prevent trouble. In the video below I demonstrate using basecamp/zumo350. But this method can also be used for the zumo 660.

http://youtu.be/AtS3UV5moCg

No. We have been working on it. We wanted some test data. Something more representative of what we are seeing in the field to be sure that this gets fixed properly.

Discussion about whether the straight-line problem is caused by BC or the device: doesn't the above statement from a BC developer tacitly acknowledge that the problem is in BC, that they recognize it, and are testing a fix? As to the prevalence of the issue on 660's, I'm guessing that the root cause relates to BC routes sometimes slightly deviating from the road (the short straight line segments), and Guess #2 is that the 660 for some reason is programmed with a smaller tolerance for deviation from the route triggering recalculation, and therefore is more sensitive to it and warns sooner and more often. Just a guess, but that would explain it. (It doesn't explain why it would recalc without prompting when that violates the recalc setting, though!)

A. U-Turns: 3. I have NEVER seen in ANY Zumo that a BC route was altered after import in the device; adding U-turns. I feel there must be something else causing this problem

What I was referring to is not a recalc upon importing, I was referring to when I choose to deviate from the route, or make a wrong turn, whatever. After reaching the internal route deviation limit setting, it will recalc (or prompt for recalc) to get you back to the route. That's when it frequently says to make a U-turn. I think you will see this on any device, and at least on my 550, it does this without regard to my "no U-turns" avoidance setting.

[QUOTE=Jason Bell;418475]Regarding the U-Turn issue... BC also shows using the wrong exit and making a U-Turn (I need eight (8) lanes of road to make a U-Turn) and I force it the correct way, but the device is changing it.
How did you "force it the correct way"? Did you use shaping points (the usual way)? I've never heard of a device completely ignoring shaping points and direct you some other way. This is very curious, could you export the route to a .gpx file and post it here? Perhaps someone can find something that would explain it?

...Guess #2 is that the 660 for some reason is programmed with a smaller tolerance for deviation from the route triggering recalculation, and therefore is more sensitive to it and warns sooner and more often.

FYI this seems to be the case with the GPSmap 60/76x models. I've seen my 76CSx "recalculate" many times while simulating a route it created.

Bottom line: in BC, there would really never be a U-turn that is planned by the routing algorithm, even though in the real world, in many cases it would require a U-turn if there is not a way to get off the road, turn around, and re-enter the road. So it makes me wonder why there is a U-turn avoidance available, I can’t think of any case where it would make a difference.

OK, to give BC developers credit where credit is due, I need to retract my statement quoted above. I’ve now created a case where the setting of the U-turn avoidance does in fact affect the route BC creates:

I created a route from I90 WB just east of the intersection with Barrington Rd in Hoffman Estates, IL, to a Starbucks on Barrington Rd south of I90. The WB off-ramp there exits I90 and then splits into two ramps, one for NB Barrington Rd, the other for SB. As expected, the plain route takes the SB ramp and all is well. But if I then intentionally put a shaping point on the NB ramp to see what happens, the route goes north at first, as it must, but has to come back to the south somehow. It turns out that without U-turn avoidance set, it turns onto a side road and shortly makes a U-turn to get back to Barrington and turn SB. But if you set the U-turn avoidance, it does go further north and finds a side road that circles around at its end where you can get turned around without a U-turn.

So it appears that U-turn avoidance does work after all, just not if it’s at a waypoint or shaping point. Mea culpa.

I do not understand this...

In general I do NOT think there is any reason NOT to work with Baescamp - and no reason to switch back to mapsource.

I suppose if you don't mind having to reload your routes 10 to 20 times a day while on a trip, even though you have automatic recalc disabled, then yes, you can keep using Basecamp. I would prefer that my unit honor the 'do not recalc' setting so I don't have to keep reloading the route just in case the unit recalculated a route which deviates from what I created on my computer. I just want to create my routes and have the unit follow them. If the Zumo feels I've deviated from the route then it should just wait until it thinks I'm back on route and continue on. I've been burned and missed roads I researched and programmed into a route by trusting the Zumo to come up with the same route my PC did using both Mapsource and Basecamp.

First, setting your zumo's Navigation pref to Recalculation=OFF, only applies to when a Route is being navigated. If your zumo is recalculating a route when you deviate from it then you should call Garmin.

Second, to avoid the "I've been burned and missed roads I researched..." issue, once you have a route you want to travel in BaseCamp just create a Track from the Route and send both to the zumo. Import the Track as an Off Road Track and show it on the Map when you are going to navigate that Route. In this way you will have the Track & Route showing on the map and if the Route should ever deviate it will be obvious and just follow the Track. I leave my Garmin set to Recalculation=Prompt or Auto and let it catch up to me as I follow the Track - unless of course I need to Detour.

First, setting your zumo's Navigation pref to Recalculation=OFF, only applies to when a Route is being navigated. If your zumo is recalculating a route when you deviate from it then you should call Garmin.

I understand the setting is for when I am navigating?? Did I give the impression it was for something else? The Zumo is recalculating the route as I'm riding the route, say south on I5 and I haven't left the freeway. It just suddenly says "recalculating", recalculates, then continues on the new route. Of course I don't know if this new route is still the route I intended to ride.

Second, to avoid the "I've been burned and missed roads I researched..." issue, once you have a route you want to travel in BaseCamp just create a Track from the Route and send both to the zumo. Import the Track as an Off Road Track and show it on the Map when you are going to navigate that Route. In this way you will have the Track & Route showing on the map and if the Route should ever deviate it will be obvious and just follow the Track. I leave my Garmin set to Recalculation=Prompt or Auto and let it catch up to me as I follow the Track - unless of course I need to Detour.

Again, why would I want to, or even have to do this?? In all the years I've been using Garmin units capable of routing I've NEVER had this issue until now. If I deviated from the route, or if the gps signals give the unit the impression I had deviated, I just ignored the prompt for recalculation. Once the unit settled back in and realized I was back on the route, whether it was induced by the satellite signals or if I deviated to a gas station, it simply popped back on route when I got back on route.

All these suggestions to load tracks or load the routes into Mapsource and then into the unit are ridiculous (in my opinion) solutions to issues that were never there until Garmin lost the ability to develop software which works with the firmware in the units they sell.

I just want to be able to create detailed routes in Basecamp, load it into my 660, turn recalculating off (or set it to prompt) and follow my route. If I deviate from my route far enough I'll ask the gps to recalculate to get me back to my route. Once I get back on route I'll reload the route to be sure I have the correct route loaded for the rest of the trip. Having to reload the route 10 to 15 times a day because the unit spontaneously recalculates the route, even though I haven't left the route, is ridiculous!

It just suddenly says "recalculating", recalculates, then continues on the new route.

Thing is: you state a situation I (and others) do not recognize at all.

a. working with the zumo660, with recalculation off the unit will not recalculate. There used to be one exception: in older firmware-versions it would recalculate once you drive in the opposite direction of the route (or the unit THINKS you do; e.g. in hairpin situations). The zumo550 still has that behaviour; in the 660 is was solved via firmware-update. This is the only explanation I can think of. You might want to check if you have the most recent firmware in your Zumo.

b. essentially, working with a zumo 660 there is no relevant technical difference between a route from basecamp or mapsource; there are minor differences but they will not affect recalculation behaviour.

There might be other aspects causing your problem. You might want to check your unit using the JDM tool. http://www.javawa.nl/jdm_en.html