Zumo User Forums

The XT behaves slightly differently when it is loading a Trip from Basecamp. The vehicle and the Calculation Mode (eg M/Cycle, Fastest) depends upon what the XT receives from Basecamp. It does not use the settings that were set for the XT before a trip was loaded.

The Zumo XT will recognise three of the Basecamp’s Activity Profiles. These are Driving, Motorcycling and Direct. That is all. If you transfer a route with any other Activity Profile, the Zumo will default to Motorcycle. Curiously, it does not recognise the Basecamp ‘Off Roading’ profile, or any of the others.

The XT will recognise only two of Basecamp’s Route Preferences: Faster Time or Shorter Distance.
Although Basecamp has Curvy Roads as an option for Motorcycle, the XT does not recognise this.
If the Zumo receives a route with an unrecognised Routing Preference, the Zumo will default to using Faster Time.

If you send a route from other route creation software without a vehicle name or navigation type, the Zumo will resort to using its default Motorcycle / Faster Time combination.

This is quite an alarming revelation. The following are some examples of how the Zumo deals with various route settings from Basecamp or other sources.

When a route is loaded into the XT with the Trip Planner App, it reveals what settings it will use. The vehicle icon shows what vehicle the Zumo has decided to use. The spanner reveals the Route Preferences that it will use. These two settings over-rule what is set for the Zumo when a route is not loaded.

In the three examples below the route name shows what modes I used to create the route in Basecamp.
The settings that the Zumo uses for these routes is shown outlined in red boxes or circle.

Before conducting each test, The Vehicle was set to Off Road and Calculation Mode was set to St. Line so that any changes were obvious.