Zumo User Forums

My first attempt was a disaster. I had been playing with a route up the A6 to CArlisle, placing shaping points to keep it off the M6.

That was a yesterday. I sent your gpx file to Basecamp so that I could create a track of it - as I didn't know the route as well as you do.
(Except I had a bit of a detour last year from Tomintoul where we were staying to Ballater. Except they decide to close the Lecht road - possibly the new bridge ?) and we had to detour along part of your route)

Anyway - my phone decided that Tread needed to be shut down. When it fired up again. your two shaping points had been replaced with my two A6 shaping points south of Carlisle.

I decided that was probably a glitch and deleted everything from my XT2 Explore routes, tracks, waypoints and from the phone. And restarted.

I emailed the track and your original route to my phone and opened them on the phone using selecting Tread App.
They imported fine and the route plotted stayed glued to the track. Even minor edits (to the name) and resaving (which is a good way of forcing a re-synch) did not change the route.

That was what I was hoping for. I know very well that if I put the GPX files onto the SD Card or Internal Storage, it would change the route. So I didn't bother doing that.

I wonder if the XT2 has got confused with the name of the route froms the XT2 and the name of the route in Tread. And you are looking at the wrong one ?

I can do a video of what I see if you like. XT2 and phone side by side. ??

I gave them testing 6, 7, 8, 9 so that they had a unique name.

I'm sure that switching the XT2 / Tread on and off causes a recalculation and they then mess about using their own foibles.

There's a replacement bridge over the River Gairn here to stop buses, in particular, grounding out and damaging the old one:

https://www.google.com/maps/place/Gairn ... FQAw%3D%3D

Opp Norht John wrote:
I'm now convince that Tread and the XT2 are incompatible

PLEASE tell Product.Support@garmin.com. They won't fix it unless they hear from many customers.

I was once behind a coach coming along that nice fast highland road going down gradually to Gairnsheel Lodge. I thought - shall I overtake (we were in the car). Decided we wouldn't bother and just enjoy the Cairngorms and the prospect of seeing deer. Bad mistake. The bus got stuck - not on the apex, but taking the corner and wedging itself against the bridge wall front right and mid left.

That is a pretty big detour.

WHat is interesting about your route is that without the shaping point it heads NW and then near mossatt heads SW back down the A97.
With the shaping point so close to the junction near Glenkindie, Im surprised the route on the XT doesn't take the the A944 and 97 then just turn off to pick up the shaping point. That and the fact that the route is that the XT2 ends up with is identical to the track I created from the route you sent - suggests that somehow the gpxx route point extensions have been transferred with the route.

(Remember I imported the gpx file into the tread app as it was and let it synch. It took ages to synch - which would be the case as it has over 1,000 invisible route points.)

Those routes had the shaping points put in them as it needs them to avoid the faster roads problems. Just like your A6 / M6 route.

For now, I don't use shaping points, but make way / via points that I put the suffix "SP" in front of them. Not ideal, but better than points being moved around etc etc.

I raised a call with Garmin product support, and sent them the two routes I have shown here.

Thanks John

A good point to raise with them if they suggest using mor Vias as a solution is that it seems that the XT / XT2 do not look any further ahead than the current segment - ie to the next Via Point or Stop, when it is seeking out traffic information, road closures.

I do not know this for a fact, but I did observe it a few weeks ago, altered a few points and that was the opinion that I formed. Whether it looks there first and it needs to be traveling along the route for some time before it looks beyong the current segment - I don't know.

Have you tried the method using the Tread App to import the GPX file ? THis has worked so far for me - except this morning with @proofresistant's route. Still pondering that one.

jfheath wrote: ↑Fri Oct 25, 2024 10:46 am Have you tried the method using the Tread App to import the GPX file ? this has worked so far for me - except this morning with @proofresistant's route. Still pondering that one.

I unfortunately recognise the limitation of only using way points.

Yes I did, I saved the test route #xx as a gpx file, then transferred it over to my Android phone and opened it up in Tread first and then saw this as per the earlier post:
I then turned on my XT2, and let it sync, and the route is almost the same, BUT both shaping points moved, not a lot, and the route hasn't materially altered. The "Road" one is near to Tillyfourie and has moved 0.3 miles "Road1" near to Glenkindle moved 0.9 miles.

I can't remember if once the XT2 was opened up, and they did their synchronisation dance(s), whether they managed to mess things up, and devalue sending the gpx to Tread first. Will try to have a look at that tonight.

OK, some more experimenting that may be of interest, certainly to the MRA fanboys like me.

I've just done four routes, all planned using MRA HERE mapping but with the OSM overlay (something I've picked up on from elsewhere that allows more accurate waypoint placing).

1. Laptop, fully shaped with enough points to go on the roads I want, sent to XT2 via cable as gpx1.1.
2. Laptop, only enough shaping points to make a route in MRA, sent via cable to XT2 as gpx1.1.
3. Laptop, only enough shaping points to make a route in MRA, sent via cable to XT2 as gpx1.2.
4. Phone, cross-checked with Tread (exported as gpx1.1) and enough shaping points added so both agree. Route saved in Tread.

Results are good, all routes are compared with tracks which get sent across via cable or export at the same time:

1. Works fine on the XT2 even after sync. The tread route agreed with MRA anyway.
2. After sync, XT2 route and Tread route differed but that did NOT change my route in the unit which worked fine.
3. As above in 2. This seems to be the foolproof way of definitely getting the 'nailed' route. However, from experience, deviation from this route
results in RUT unless auto-recalculate is switched off. The answer to both is to stop and restart the route from the nearest entry point or navigate
yourself back to
the track.
4. A near full success apart from one small section that the XT2 changed (yes) which then synced the change back to Tread. Another shaping point
would solve this but one to watch out for even if Tread and your route agree. You can always just follow your track if it happens and you've not
noticed before.

Routes tested with XT2 in simulator mode and all routes started.

Conclusion:

None of my cable transfers were messed with, do not mess on Tread with these routes and all should be well.
Use OSM for waypoint (shaping/via/ whatever) placing.
If exporting to Tread, use enough shaping points to make reasonably sure of going on the roads you want. Tread has been seen known to move shaping points if it thinks it knows a better way but from my messing around, it was only where there was sufficient gap between points to make it decide to.

IMPORTANT I THINK: I will use enough shaping points in my gpx1.1 routes from now on (cable or export) in order for Tread not to make these re-routing decisions.

I hope that all makes sense. I'm sure you'll let me know if it doesn't. For the Basecampers, sorry but I've not used it for a few years. Mapsource before that. Lat/long and/or GR before that. Map & compass before that. Followed the leader before that. Never lost but temporarily unsure of my position

jfheath wrote: ↑Fri Oct 04, 2024 7:28 pm The JavaWa Solution has been found to work with the XT2 just as well as it did with the XT1

Jaco has changed his webpages. It now reads XT(2) to indicate the solution works for both XT and XT2.

https://www.javawa.nl/triprepair.html

FrankB wrote: ↑Sat Oct 26, 2024 10:58 am Jaco has changed his webpages. It now reads XT(2) to indicate the solution works for both XT and XT2.

https://www.javawa.nl/triprepair.html

On the XT I used the in-device method of changing the route to avoid the RUT problem. With this tool can I save the routes as a GPX file on the computers hard drive, amend it, and then send it to the XT2?