XT2 won't calculate route

[proofresistant]

Please try the following:

1.
Import the track into the Tread app once. Then try to create a route from it in the Tread app.
Recently, I have realized that the Tread app sometimes sets red signs when viewing the generated route where it cannot be calculated.
If this is the case, then perhaps this will help in the search for the cause.

2.
Deactivate the Tread app.
I myself have now completely uninstalled my Tread app because of all the problems.
Then import the file on the zumo XT2, I use the SD card for that.
That seems to be the most reliable way to get routes 1:1 as planned onto the zumo XT2.

Welcome to the clup of sufferers.

PS
Search here in the forum for the TripManager tool
This is also a great help, but first you should get to know the XT2 and its weaknesses a little.

[smfollen]

@Trilergy I regularly connect my XT2 directly to my pc via USB cable when using Basecamp. You get a warning from Basecamp that the XT2 is not fully supported, but it works fine for transferring gpx files and other functions. The warning is because the XT2 has newer features which Basecamp doesn't support.

Like some others here, I have removed the Tread app from my setup entirely because of multiple issues with Tread.

I have found Trip Manager to be an excellent tool for transferring routes from pc to XT2. It has several additional features which are very helpful.
viewtopic.php?p=24080#p24080

I have no problems with route calculation even when route points are not perfectly on the road.
Here are a couple screen shots showing that. The route was created in Basecamp. It was transferred to my connected XT2 directly from Basecamp by right clicking the route, selecting "send to", then zumo XT2, Memory Card, User Data. After disconnecting and restarting the XT2, I imported the route and selected it.

27728[1].png (451.67 KiB) Viewed 233 times

30467[1].png (279.69 KiB) Viewed 233 times

I also did some route tweaking on the XT2 to force recalculation on the XT (e.g. change from fastest to shortest distance). Still no issue.

In general, I would suggest that it is good practice to zoom in on your route points to make sure they are on the intended road. I have, on occasion, accidently placed points on the wrong nearby road or the wrong side of a highway

Hope this helps.

[Trilergy]

Yes thanks for this. After playing around and testing what I had experienced initially I found it would actually work if off the road a bit. However when Tread could not find even a path it showed up as an error and wouldn't calc.
Im not sure what happened...maybe just old maps needing a check first which i have now done. As you suggested I zoom right in and find sometimes they are way off.
Spent my weekend adjusting all my maps and now everything appears fine.
Doing my first live test with the XT2 tooday.