Latest XT2/Tread software version

[proofresistant]

Yes and no.

It doesn't have to crash.
The way I have observed it, there are situations with routes where the Tread app or even the Zumo XT2 have problems.
There is also the possible theory that there are too many "complex" routes being synchronized at once.
So a thought, when synchronizing is always also calculated and if both do this and this asynchronously, one good and the other "not so good", that all this is asynchronous, then they are in a loop and issue is there.

Translated with DeepL.com (free version)

[turbo19]

I don't understand Garmin's philosophy. It seems like we'd have to transfer all our GPX data to the Tread App, but if it gets overloaded, it starts to saturate and restarts the XT2 when syncing?

Garmin's own technical support team says we should stop using Basecamp (in several emails) because they're not compatible (I'll continue using it for the rest of my life). So, what's their solution for archiving all of our GPXs? None?

I have about 400 synced tracks, with 2200 WP and about 15 routes. If the system can't maintain and sync this, I'll obviously have to keep using Basecamp. Or does Garmin want us to use third-party software like MRA? I don't understand.

[proofresistant]

I have just received a similar reply from Garmin,
it's about the CEP problem in my case.
I should plan with Tread App says Garmin support, because Basecamp is no longer supported what madness.

But I can't plan more complex routes with the Tread app (or if I can, it's painful horror, more painful than I could ever experience in Basecamp ) and certainly not throw away all my routes, as you described.
You also need to be able to use other people's routes in a “user-friendly” way.

We have to seriously disagree with such answers from Garmin and fight back.
PS
I am also working on a "best practice" solution on how to get wirelessly via "Tread App" reliably and effectively into the XT2.
My thanks go to the TripManager and especially FrankB.
Nevertheless, I don't want to give up the desire to use the wireless “plug and play” option.

[proofresistant]

... It seems like we'd have to transfer all our GPX data to the Tread App, ...

I think it's much worse than what you already suspect
Garmin wants you to create everything only with the XT2 or the Tread app and everything starting from the scratch.
Dealing with results from alternatives or other planning “standards” are then no longer the responsibility of Garmin.

[jfheath]

I have just received a similar reply from Garmin,
it's about the CEP problem in my case.
I should plan with Tread App says Garmin support, because Basecamp is no longer supported what madness.

But I can't plan more complex routes with the Tread app (or if I can, it's painful horror, more painful than I could ever experience in Basecamp ) and certainly not throw away all my routes, as you described.
You also need to be able to use other people's routes in a “user-friendly” way.

We have to seriously disagree with such answers from Garmin and fight back.
PS
I am also working on a "best practice" solution on how to get wirelessly via "Tread App" reliably and effectively into the XT2.
My thanks go to the TripManager and especially FrankB.
Nevertheless, I don't want to give up the desire to use the wireless “plug and play” option.

Just point out to them that if you create a route in the Tread and export it as a gpx file, the same problem arises with that gpx file. The problem is not with Basecamp compatibility, it is with Tread or with the transfer of routes to the XT2. I use gpx files from Basecamp and they work perfectly - but that is only because I do not allow Tread to synch with the XT2. And I set my routes as Saved.

Something happens in the transfer process that renames route points, relocates route points, moves shaping points onto faster roads taking the route with it. Some of this also happens when using the Route Planner on the Tread app as well - eg when changing VIas to Shaping, often they are moved onto nearby faster roads. That is without synching with anything - just using the App on my ipad.

Also - I checked out a route that I had planned in Basecamp, and noticed that a few shaping points - that I had placed specifically to avoid awkward junctions and town centres - had been moved so that the route went through the junctions and towns that I wanted to avoid.

So I recreated the route on the Tread App. and let it synch. It did exactly the same thing. The programmers are treating shaping points as irrelevant.

And yes - I told them and gave them the evidence.

[turbo19]

I have just received a similar reply from Garmin,
it's about the CEP problem in my case.
I should plan with Tread App says Garmin support, because Basecamp is no longer supported what madness.

But I can't plan more complex routes with the Tread app (or if I can, it's painful horror, more painful than I could ever experience in Basecamp ) and certainly not throw away all my routes, as you described.
You also need to be able to use other people's routes in a “user-friendly” way.

We have to seriously disagree with such answers from Garmin and fight back.
PS
I am also working on a "best practice" solution on how to get wirelessly via "Tread App" reliably and effectively into the XT2.
My thanks go to the TripManager and especially FrankB.
Nevertheless, I don't want to give up the desire to use the wireless “plug and play” option.

Just point out to them that if you create a route in the Tread and export it as a gpx file, the same problem arises with that gpx file. The problem is not with Basecamp compatibility, it is with Tread or with the transfer of routes to the XT2. I use gpx files from Basecamp and they work perfectly - but that is only because I do not allow Tread to synch with the XT2. And I set my routes as Saved.

Something happens in the transfer process that renames route points, relocates route points, moves shaping points onto faster roads taking the route with it. Some of this also happens when using the Route Planner on the Tread app as well - eg when changing VIas to Shaping, often they are moved onto nearby faster roads. That is without synching with anything - just using the App on my ipad.

Also - I checked out a route that I had planned in Basecamp, and noticed that a few shaping points - that I had placed specifically to avoid awkward junctions and town centres - had been moved so that the route went through the junctions and towns that I wanted to avoid.

So I recreated the route on the Tread App. and let it synch. It did exactly the same thing. The programmers are treating shaping points as irrelevant.

And yes - I told them and gave them the evidence.

Yes, we already know that.

In this case, we're talking about random, pointless restarts due to the sync issue. With Tread Active. It's a different issue, not a compatibility issue between Basecamp and the Tread App.

I went for a ride today, and after deleting the last collection with one route, the XT2 stopped restarting. God knows why it restarted with that collection that only contained one route drawn in the Tread App. The syncing system is absolutely crap.

When I delete two tracks from one of my collections (permanently delete), they stay in the unorganized folder. I have to delete them manually on the XT2. In the Tread App, it seems fine (unorganized empty), but on the XT2, they stay in the unorganized folder. Disaster.

When it feels like it, it syncs "halfway" well, and sometimes, God knows why, it does these things.

Garmin could hire better software engineers.

[proofresistant]

@jfheath, have you ever managed to name or rename shaping points in XT2 or with the Tread app?
For me, it always named "Shaping point" in the Tread app and has instead also real names in XT2.
And yes, both manipulate shaping points extremely and especially if you delete via points or convert them into shaping points.
The reverse (shaping becomes via) is (usually) better (with little to no negative effects)
But that's a topic in itself, as @turbo19 already wrote.
Then there are problems if BaseCamp is the source. But here we are (i am) only testing the Garmin approved planning methods right now.
Then another tip, or at least an observation.
If the route sections are Adventure and then a via to shaping is changed in XT2, the remaining shapings most are not changed In the same way. It's different with the Tread app, there it usually causes more problems most. This is not yet a final statement because I'm still working on it.

@turbo19, I spent the whole day today trying to reproduce the CEP problem with routes from the Tread app or the XT2 using only one or two route versions.
I definitely noticed that there were hidden duplicate or multiple copies of a routes (*.trip) in the XT2 .system\Trips folder.
Maybe if I just created it in one route and then observed it in the other device, or if the route was recalculated and or resynchronized between the two devices.
Maybe also by renaming them in one device when I had them open in the other.
Then i noticed, XT2 calculationg severel times during openeing a route synchronized from Tread App and spends up to a minute for this calculations only for 63km.
But honestly, I don't know exactly whot is going wrong

[jfheath]

No - They are just get called shaping points - as if they have no significance.

I've been through all of what you are currently looking at and sent my written, screenshot, gpx file s and videos of it happening to Garmin.
They had no way out of it - it is definitley Tread and synch that is causing the issue.

But they haven't changed anything so far, so I expect that they wont.

But I'm happy with what I do - my route points (via and shaping) keep the name that I give them and all of the points remain in place.

How the routes work with CEP, I don't know. I stopped using that after I first tested its behaviour many years ago when I first got the Zumo XT1. Via points to shaping point move locations on the Zumo 595 and later. But change a shaping to a Via, it stays in place.

So for foreign trips where I don't know the place names, I'd number them - 3 digits - to represent the distance in miles / km from the start of the route. Set my trip meter when I set off. If I need to restart the route I can tell which shaping point I need to change to a via from my trip meter - the first one with a higher mileage number. Change that to a Via and select that as the next destinations. But I think I have only ever used that technique once while out riding. That is much more reliable than CEP.

[proofresistant]

But I'm happy with what I do

Hi @jfheath fheath
I can only praise and recognize the way you do it!

At the moment I also spend a lot of time with the XT2, but the Zumo XT2 will not get that much time in the long run!
It must be possible to design a route, definitely without BaseCamp, instead with something modern tools or tours from others “just plug and play” and the zumo XT2 must work as planned!
If I don't succeed, I'll throw it out of the window (or to NL).
Everyone I know is already moving towards Android/Apple apps with or without AndroidAuto/Carplay devices and no one is as frustrated as I am with the zumo XT2.
At the moment, it's only the researcher's instinct that drives me, but unfortunately it's far too great.
Then CEP must work, it's basically the only useful solution as long as the XT doesn't remember where it's already been. Where do we end up if every normal user first notes the KM or Miles in the route and then uses this as an entry point? I can't even select the shaping points, what do I do then? Anyway, the workaround of just changing the next upcoming shaping to the via point(s) certainly seems to work reliably for CEP, maybe keep that in mind and try it.

Otherwise the workflow is predetermined, I have a GPX from wherever, transfer it wirelessly to the device and not much more [*1]. My next attempt to deal with the CEP and synchronization problems in a practical way will probably be to use a track import instead of the GPX route, turn it into a route in the Tread app (Track to route conversion is much faster using the bloody App than in the XT2 device) and then ride it.
It remains to be seen whether I can then live with not recalculating (due to unplanned detours and so on) and whether there will be RUT problems.

And don't misunderstand, I appreciate your knowledge, but you are an absolute zumo professional with a lot of experience and also a fan. I am neither a professional nor a fan and others may also have a different view.


[1]
TripManager will then also be an essential part of my future workflow, it's impressive what you can do with it, just in between work. I plan to share details of my positive experiences in another topic in the near future.

[Dutchgixxer]

Create a route in whatever program. Export the route as a track. Import track in the XT2 for instance with tread . On the XT2 convert the track to a route. Turn recalculation of. Works like a charm. If Garmin has sorted out the route shit use the route option. Just my 2 cents