XT2 won't calculate route

[animal]

I created a route in my tread app on my ipad, 8 waypoints and 49 shaping points 344 miles. When the route syncs to my XT2 it won't calculate the route. It goes to 21% and says "can't calculate route". Can anyone help with this?

[Oop North John]

Hi, and welcome

I've had similar with my XT2 and IIRC I adjusted something, and it worked. Maybe a butterfly took off in Japan, and that was enough for the software to behave nicely.

Are you aware of the problems using shaping points will almost certainly occur with the XT2 and Tread app? I don't use shaping points anymore, only via = waypoints.

[smfollen]

@animal Basecamp still works fine with the XT2, despite the warnings that it is not supported. Basecamp, as well as various third party apps that can write routes to gpx files, handle shaping points just fine. The problems occur when the Tread app syncs routes on the XT that contain shaping points. Specifically, tread tends to make dramatic changes to routes that contain shaping points. As long as you do not let the XT2 sync routes with the Tread app, that problem is avoided.

As Opp North John points out, you can use only via points, which Tread does not mess with, but shaping points are important to me.

[animal]

@smfollen are you calling way points via points? I don't see via points on the tread app. Only waypoints and shaping points.

[smfollen]

@animal Welcome to the world of GPS related term confusion. Many, including Garmin, tend to use the same terms to mean different things and different terms to mean the same things. See this thread and post viewtopic.php?p=22308#p22308 for some [hopefully] clarification.

[smfollen]

@animal To hopefully clarify further, and to answer your question directly, what Tread refers to as a waypoint appears to actually be a via point.

I've based my thinking of all this on the GPX file standards. There, routes are made up of route points. There are two types of route points, via and shaping. Those two types are actually defined by a Garmin extension to the GPX standard, although Garmin sometimes does not follow or support its own standard! Waypoints, which are simply saved locations, may be used (basically copied) as route points (either via or shaping), but routes are always made up of route points, never waypoints.

The tread app, adds to the confusion, in my opinion anyway, because it sync's with the explore database, which does not support shaping points at all. Nor does explore route. I suspect that is the root (not route) of some issues we experience with Tread syncing routes.

Some applications that do not support the two types of route points (via and shaping) tend to refer to all route points [incorrectly] as waypoints. Tread seems to be mixing the two.

BTW: Although Basecamp supports both types of route points, it refers to them as via points that alert on arrival and via points that do not alert on arrival - those are actually via and shaping points, respectively.

Hang in there, it will all make sense soon.

[Oop North John]

The tread app, adds to the confusion, in my opinion anyway, because it sync's with the explore database, which does not support shaping points at all. Nor does explore route. I suspect that is the root (not route) of some issues we experience with Tread syncing routes.

I always chose not to sync with the Explore database, as I understand it can cause other issues.

And how very unhelpful to have an Explore database and an Explore app on the XT2

[proofresistant]

In advance,
I suspect the use of Basecamp or the need for Explore really have no bearing on the original question. Nevertheless, it should be noted that BC is not really compatible with XT2 and the Explore database is not always a problem with shaping points.

Regarding the actual question, a tour was planned with the Tread app, so it can be assumed that in this case the Tread app is not the cause of shifted waypoints.
In this case, you should of course synchronize via the Tread app, because this is exactly how the Tread app Zumo XT2 works together. The fact that everything is then stored in the local XT2 Explore database is probably firstly necessary and secondly not the main problem, at least in my experience.

If I understand the original problem correctly, 8 waypoints (often orange flags in the app) and 49 shaping points (smaller blue dots) were used.
If the Tread app can handle it, the XT2 should be able to handle it too. Unfortunately, XT2 and or the Tread app have very strange behavior far too often.

My approaches would be the following (each of the options 2 - 4 mentioned can be the solution on its own):
1. look for an alternative device, Zumo XT2 is not really the best choice
2. deactivate all avoidances in the XT2. In any case, avoidances in the XT2 should be the same as those in the Tread app.
3. first activate the City Navigator map in the XT2 and then, step by step, all possible maps available on the XT2 (but only those that correspond to the route destination environment). Even if this leads to success, it is usually better to use as few maps as possible. In any case, the selected maps in the XT2 should be the same as those in the Tread app.
4. divide the route into two or more sections. Note that 344 miles can be a real challenge for the XT2. A modern device with outdated performance is unfortunately a reality for the XT2.

[proofresistant]

Please share your route and post it here as an attachment.
Maybe I or someone else here can then check it out.