Durango Dave wrote: Mon Jun 23, 2025 3:11 pm
Thanks to smfollen I have this resolved.
The key point is to use the Tread app rather than drive.
Here's how to transfer routes to Zumo XT2:
Plan route on PC with MyRouteApp.com
Open MyRoute-app and Tread on phone
go to Routes
find your route and download as .gpx 1.2 (route, track, PIO)
Press Download
Press export > export to Garmin Tread
When the route is in Garmin Tread it will also be in the Zumo XT2
I think this is the same instructions that Scarecrow is implying. Or if there is a simpler method let me know.
Just some additional information to complete the picture.
When you export using gpx v1.2 from MyRouteApp, it sends the route 'ghost points' to the gpx file so that the Zumo can reproduce the route exactly.
It also sends the Via Points (hands on MRA, orange flags on the Zumo)
It does not send any of the shaping points (tear drops on MRA, blue discs on the Zumo)
This means that if the route has to recalculate, then the Zumo has only the Via Points to work with.
Using Tread almost guarantees that the route will be recalculated.
From MRA, V1.1 exports the via points and the shaping point, but not the ghost points.
At present, on the XT2, the Tread App has shown a tendency to will move shaping points onto faster roads.
If you insist on using the method you describe, it would be safer to use only Hands in MRA = Via Points in the XT2.
The XT1 had a limit of 31 Via Points in a route, including the start and end. I don't know whether the XT2 has this limit. Possibly not.
Since I like to use Via Points only to mark exits from stopping places, my routes only ever have a handful of Vias.
Since Tread does not honour my plotted shaping points, It makes Tread unusable for me.
So I am stuck with USB Transfer of gpx files to the Zumo. For that I use
TripManager which keeps things exactly as I like them and also prevents the dreaded RUT problem.
Ghost Points = the term I used to avoid saying Garmin's gpxx route point extensions. Every route has many hundreds of these plotted a few metres apart, and the route joins these together with short straight lines. The result is a magenta line which follows the twist and turns of the road exactly. If the route has no ghost points, the Zumo has to get them from the map files. I the route is ever recalculated, then all ghost points are deleted and new ones from the map files are substituted.
A good technique is to put the Routes, MRA's POIs (= Garmin's Waypoints), and Track all into the same collection and make it visible. You will be able to see when your route has been altered, because the track - which is normally hidden by the magenta line - will be revealed if the route has been altered. Tread or the XT2 will never alter the track. That will reveal any issues that you may encounter - without losing track (ho-ho) of where you intended to ride.
RUT behaviour
An explanation of RUT behaviour can be found
here.
It relates to the XT1, but the XT2 does the same thing.....
.
..except, it looks like they have attempted to tackle the repeated requests for U turns by limiting the number of consecutive U turn requests to 2 or 3. This hides the symptoms, not the cause. It still wanted me to go back - to the last point that it created a new route by looking for side roads or housing estates to get me to turn back without actually asking for a U turn. On open country roads, this new behaviour forces the XT2 to look much further ahead - maybe a few miles - which may result in it being able join up with the original route before it asks you to go back. So in some circumstances this can have the desired effect and is an improvement. But in my tests, more often than not, it made the situation worse - because for a long time - 7 miles in one test - it gave the appearance of navigating ahead until it found a small housing estate to turn me around and then head 7 miles back. The only clue was that the distance to the next via point suddenly increased by 14 miles.