Right, I have somehow managed to get myself a 595.
I cannot reproduce your results. I have used the same Skipton to Fort WIlliam route that I showed on the couple of maps above. I did the same test on the 590 before I redid the conversion to a 595. Both gave the same results.
First, I tried it with the Via Point and Shaping points in place. It was taking an age to import the map which is not correct - it should import it in a few seconds, and this was taking a couple of minutes. It turned out that I had prepared the route a while ago, and since then I had installed the latest UK maps 2020.30. I hadn't recalculated the route in Basecamp. Also, I noted that I had some OSM maps on my system, and these were turned on. I have noted before that these maps cause problems with the Garmin maps if both are ticked at the same time. They can both be loaded, but not active. So I unticked the OSM maps.
Then I tried the route like yours, with all route points set as shaping points. There was no change in the route when loaded or after pressing GO.
Then I tried stripping the shaping points in both versions (ie with a few Via Points intact, and without. This can be useful for seeing if a route recalculates. Without the shaping points in place, it will be very obvious if there is a recalculation. But neither versions of my route recalculated on loading or when Go was pressed or when Start was pressed. For routes with Via Points included, I tried selecting a point further into the route as the starts. That DID calculate a route - but only up to the selected point after which the route was the same as before. Even with the shaping points stripped out.
Pressing SKip (its in the Change Route link) for any route point, and the route is recalculated and the sahpe is lost. It still goes through the Via Points though (if there are any).
(A word about stripping out the shaping points. - In Basecamp you can shape a route with the shaping points, and then remove them - leaving the shape of the route intact. When this gets transferred and imported to the Zumo, the Zumo retains the same shape. But as soon as it recalculates for whatever reason, it only has the Via Points as guides, so the original shaped route is lost. It is very obvious when looking at the map whether a recalculation ahs taken place, using this trick.
rbentnail wrote: ↑Fri May 29, 2020 9:40 pm
Only the middle box "Always match route to the map on my device when transferring." is ticked.
I always have all of those checkboxes unticked on Device Transfer Options in Basecamp. But I tried with always match maps ticked, and it made no difference. I have noticed on a previous occasion that it did make a difference. It forced a recalc on import of the route. I don't have any notes and I don't remember the details.
rbentnail wrote: ↑Fri May 29, 2020 9:40 pm
The device is completely useless to me in the Motorcycling activity. Both the device and Base Camp are set to the Driving activity. Both Base Camp and the device are set to Faster Time.
Its the settings in the Basecamp route that are used - (or just the vehicle and the routing properties.) Usually changing the vehicle type will force a recalculation, but it switches the unit to car as soon as you load the route. Beware of using custom profiles though. The Zumo doesn't know what a custom profile is, so when the Zumo receives it, it makes a decision about which profile to use, And it uses Bike. Which WILL force a recalculation of the route !!
I see no difference in the ZUmo being told that it is a car or a bike. If you set up the routing preferences and navigation preferences to be exactly the same, as far as I can see, they behave the same. Its just a way of storing 2 sets of settings. When the Zumo loads a route for the bike, it switches to bike mode, and apart from faster/shorter, it uses the settings (avoidances, tolls, etc) that are stored in the bikes profile.
The unit also switches mode according to the cradle it is in. But load a bike route into the Zumo when it is in the car cradle, and the cradle then becomes set as a bike cradle. There were so many ways of messing things up, I set up car and bike to be identical. Then I don't care.
rbentnail wrote: ↑Fri May 29, 2020 9:40 pm
You can see in this thread
viewtopic.php?f=12&t=93 when I asked roughly the same questions. I've been trying for 2 yrs to get this damn thing to simply follow a premade route. The gist of that thread (with no real results, obviously) is that I am doing something wrong.[/color]
I'll take a good look through that. Thanks.
rbentnail wrote: ↑Fri May 29, 2020 9:40 pm
Base Camp 4.7.1 with Navigator North America NT 2021.1
On the device is Software Version 4.60 and Map: Full Coverage of North America 2021.10
Aha. Now - is that a typo or is it really version 2021.1 on Basecamp and version 2021.10 in the Zumo ??
Now you and I know that they are both the same decimal number. But it seems that the Zumo doesn't. Years back there was a similar situation with the numbering of the Zumo map and the Basecamp map. One had a nought on the end, the other didn't. The Zumo saw this as meaning that the maps were not identical, so every single route on import would get recalculated by the Zumo. The difference is that this can take a few minutes per route, as opposed to a few seconds. It remained like this until they brought out the next update.
So back to a comment I made further up - how long does it take to import a route ? It should be just a couple of seconds during which time the display will indicate calculating. If it takes longer than that for a route transferred from Basecamp, then that is where we need to look further.
If you're happy to stick with this to get it sorted and answer a load of questions, I'm happy to keep working at it. We might have to switch to email at some point.
It's late now, I'll read through your previous topic on the same subject tomorrow.
John
