izabelleferland wrote: ↑Sat Jul 24, 2021 10:48 am
Thanks again for additional info. As you can see in my pictures I have auto set on my XT and for my route as well. I was told a few years ago that it was preferable that way. Before my XT, I had a Zumo 396 and never had the issue I'm living now with my XT. This week I did a lot of reading and I've adjusted some little details. I added a lot of shaping points to my trip. I was told and also read here that it should help.
It is not such a big problem. I use Motorcycle for whatever vehicle I am in. It is just a name that is given for the settings that are stored in the Zumo. The Zumo will remember one group of settings for the Motorcycle and another group of settings for the Car.
So for car
En - I can have Shortest Distance set and Avoidances of U turns, Motorways and Ferries allowed
Fr - Method de calcul: Distance la plus courte and Contournements: Demi-tours, Autoroutes, Ferris = Autoriser
And for motorcycle
En - Fastest Time and U-turns, motorways and Ferris not allowed.
Fr - Method du calcul : Temps le plus court and Demi-tours, Autoroutes, Ferris = Eviter
The XT remembers the settings for both types of vehicle - car and motorcycle.
Whoever told you that it is preferable to have them both set to Auto / Car was not correct - but it is not entirely wrong either. If Basecamp is set to Motorcycle and Zumo is set to Car then that will result in some problems that are difficult to understand. So keeping Basecamp and you Zumo both set to the same thing helps to remove that type of problem. So your friend's suggested solution will work, but it isn't quite the complete answer.
The reason for that is one part of the answer to your next question.
izabelleferland wrote: ↑Sat Jul 24, 2021 10:48 am
Yiou mentionned:
Note also that if you are switching the Zumo from car to bike, then you may think that the Zumo switches to car mode when it is in the car cradle, and to bike mode when it is in the bike cradle. It doesn't. I'll explain that if anyone needs it.
I would be curious to learn more.
When you transfer a trip or route from BAsecamp it sends two additional pieces of information
The vehicle type (eg motorcycle or car)
The routing preferences (eg faster time, shorter distance).
It sends nothing else other than the details of the trip - that is
The Start Point, The End Point, the Via Points and the Shaping Points
and a detailed point by point description of the route - that makes up the plotted magenta line - so the XT does not have to calculate it.
When the route is transferred to Zumo Internal storage, it copies any Waypoints (created in Basecamp with the Flag tool) to the Zumo list of Favourites or Stored Locations. (Enregistre), and it makes the route / Trip available for Import.
With the Zumo in your hand, it may be set to Car and Shortest Distance.
When you load your route (which was set by Basecamp to Motorcycle and Fastest Time), then your Zumo switches to using Motorcycle and Fastest Time. Your Garmin route will remain as it was in BAsecamp. But if it needs to recalculate. (If you press 'Skip'; if you ride away from the magenta route), then the Zumo will have to calculate a new route from where you are to the next route point.
In order to do that it uses its current settings. Those are - Fastest Time, and Motorcycle.
Basecamp didn't send it any information about the motorcycle, so the Zumo uses what you have programmed it to use.
From my example above that was - U-turns, motorways and Ferris not allowed.
Even if you had U turns, motorways and ferries allowed in basecamp - that information isn't passed to the Zumo. It uses whatever is in the XT settings for motorcycle.
Ok So Far ?? Becasue it gets a bit complicated now.
You may think that when you plug the XT into your car cradle it switches to Car mode ?
And when you plug the XT into the motorcycle cradle it switches to motorcycle mode ?
No it doesn't.
What it actually does is switches to the mode that was last set when it was last in the cradle. The XT gives a warning message if it is about to switch. And it doesn't switch it back when it has finished.
So - your XT is in the motorcycle cradle. When you put the XT into the motorcycle cradle, and turn on the ignition, it switches to motorcycle mode - a you expect that it should. You make sure that non of your avoidances are set before you load the route.
You load a route from Basecamp which was created using the Car profile. As soon as you load it, the Zumo switches to Car mode. It is now in the motorcycle cradle with the Zumo in Car mode. The route is set for Car and Shortest Distance. When you navigate the route, If the XT has to recalculate the route (eg you have taken a wrong turn) recalculates the route using the settings in the Zumo for the Car profile. Not the ones for the motorcycle profile that you have just programmed in.
The problem is that you have just programmed the avaoidances for the motorcycle. When you loaded the route (which is a route for the car, it uses the avoidances that are in the XT for the car, not the motorcycle).
OK ??
So you remove the XT and try all of that again. This time you get different results. Why ? Becasue this time, when you plught the XT into the motorcycle cradle, it does not switch to motorcycle. The last mode that it was in when the cradle was used was the car mode. So it switches to car mode instead.
OK ??
Ah - but. You are using the Zumo at your desk, and the screen keeps going dim. So you plug in the power supply with the USB socket. What is this ?? The XT switches itself to car mode.
It turns out that it doesn't recognise the cradle at all. It recognises where it is getting its power from. In the motorbike it comes fromt he two brass pins on the connector. In the car it comes from the USB cable.
Personally, I set everything to motorcycle and fastest time. Then the problem doesn't arise.
If the Zumo gets a route that doesn't have the car, motorcycle or direct profile - the Zumo uses Motorcycle.
If the ZUmo receives a route that is not set to fastest time or shortets distance, the Zumo uses Fastest time.
So there is absolutely no point in using the curvy road feature in Basecamp and expecting the Zumo to follow it. You can use the XT curvy road feature after the route has been loaded.
Footnote.
Anyone reading this who has a 590 and a 595 - similar issues apply to these two units as well, but the behaviour when loading a route is different.