Peobody wrote: ↑Sat Apr 23, 2022 4:23 pm
I read somewhere that setting a route to Custom in Basecamp prevents recalc by the XT. When the profile is set to Custom, the profile for every Via Point in the route gets changed from Motorcycle to Driving. Comments by jfheath indicate that the XT doesn't know about Custom so will default to Motorcycle. Does the XT ignore the profile of each Via Point? Is there really any benefit to setting every route profile to Custom when creating them in Basecamp?
That may depend on where you read it and to which devices it related. My experience with Basecamp is only with the Zumos.
I had noted that evey Via Point declaration repeats the same calculation mode - eg like this Cusotm Route set for Shorter Distance.
<trp:ViaPoint>
<trp:CalculationMode>ShorterDistance</trp:CalculationMode>
<trp:ElevationMode>Standard</trp:ElevationMode>
</trp:ViaPoint>
The <rte> declaration normally defines the transportation mode, but in the case of a custom profile, the transportation mode isn't defined at all, so it must leave it up to the satnav to decide how it is going to deal with it.
In the case of the Zumos where I have records of testing this (590, 595 and XT), the default been motorcycle. I think it did that on the 660 as well, but I have no records.
In the case of the XT if the Calculation Mode is set to something that the XT doesn't recognise, it assumes Faster Time. The XT does this, not Basecamp.
Regarding the XT not recalculating if the mode is 'Custom' - I don't know becasue I haven't considered that as a possibility. For the XT, I doubt that that is the case, because the XT substitutes Motorcycle if it doesn't get a transportation mode. But that may be something to prove or disprove.
It isn't the case that the XT doesn't know about Custom. Basecamp doesn't send it any vehicle information - so the XT defaults to using Motorcycle.
If you send the XT a route using Hiking, Off-Road, Walking, Bicycling etc. The appropriate term is transfrerred to the XT, but the XT ignores it and uses Motorcycling.
So - that goes back to my first comment - it may depend on where you read it and what device is being discussed. I've never used Basecamp with anything but Zumos.
Incidentally - a similar thing happens with other routing preferences. Set the routing to Curvy Roads, and the XT will default to Faster Time.
(That wasn't true of all Zumos, but it is for the XT. I reckon the reason for that is that the XTs curvy roads is more advanced than Basecamp.
The only advantage that I can see of using Custom routes is to avoid the big disadvantage of using Profiles. There is one Motorcycle Profile. You set your preferences for that and you use it to create a lot of routes. A couple of years down the line, you fancy expeimenting with the avoidances and routing, so you change it. And Basecamp sets to the very time consuming task of applying the new motorcycle profile to every single motorcycle route in itse database. Loading them in turn and recalculating each one. You might as well go and have a coffee, 'cos it will take some time.
So I use Custom Profiles if I want to apply avoidances and different types of routes - to see what BC comes up with. The chnages are displayed instantly. I create a track of the route that it creates, then remove all of the avoidances, change it to Faster time and then edit the route by adding route points to make it follwo the same line - still marked by the track.
Then I set it back to Motorcycle. But I don't think there is need to do that - since it will default to that anyway. My motorcycle profile is always Faster time and no avoidances.