Latest XT2/Tread software version

[jfheath]

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

It is an effective and popular solution and always worth mentioning.

But if you like the ability of a route to find a different way to the next route point -- should you need to deviate for whatever reason - then this method is of no use. This was a really useful feature on all Zumos that I have owned up until (and including) the Zumo 590. After that Garmin seem to have decided that if you wander off route then that is your problem - forgetting that roadworks, traffic jams or the urgent need to go and get some fuel are all part of a journey.

But your method works well to show you the way. As does displaying a track under a route. And they have made that much easier with the use of collections that do not need Tread to be involved.

[proofresistant]

Just a short anecdote

• i build a race track

• i buy an Aston Martin Vanquish

• i get all the know-how for a racing driver from experts ( with a lot of effort )

The day has come, my dream shall come true
i want to have fun on my race track
with all my learned skills
with my Aston Martin Vanquish
I am so well equipped and believe I have the best of the best

• i put on my racing gear
  and start the engine
  what an exciting feeling!

i drive out of my pit lane straight just onto the race track

• i switch the cruise control to 50 mph
  Why 50 mph? well, I've always done so well and I know it works fine

Check it out, maybe there was a suboptimal solution somewhere


PS
Just something to smirk about
And and just a reminder, this thread has the topic "Latest XT2/Tread software version"


PPS
After a long time, I have even more experience.
I'm still sure cruise control to 50 mph works well.

[Dutchgixxer]

With garmin you will be in need of the towtruck to help you out of the gravel box, every time. So the 50 mph is not so bad

[smfollen]

@proofresistant

But here we are (i am) only testing the Garmin approved planning methods right now.

I think this is the source of much of your frustration. More specifically, I believe the tread app is the major source of frustration. (More on that below.)
I have eliminated the Tread app entirely from my world.

... and the zumo XT2 must work as planned!

With the Tread app eliminated, I find that the XT2 does work as planned, including CEP, and off route recalculation.

There are, of course, a few things to be aware of or a few techniques to be followed. Some of that is due to Garmin quirks, some of it is the nature of satellite navigation. jfheath's Everything you need to know post is extremely helpful viewtopic.php?p=9356#p9356

Most any route planning tool of choice, including Basecamp, will produce good routes, tracks and waypoints which can be reliably imported directly to the XT2 (without using the Tread app). This can be done via gpx file, or using FrankB's Trip Manager.

As we recently discussed in another thread here, I find CEP to generally work well as long as there are no u-turns, points misplaced off the road or placed at intersections.

Jfheath pointed out that he only had to use his convert numbered shaping to via once. If you stop while navigating a route, when you turn the bike off or remove the XT2 from its mount, it will go into standby and will automatically resume the route where it left off when powered back up.

Off route recalculation is subject to RUT if the route was imported, but there are simple workarounds for that such as saving a duplicate copy of the route and navigating that, or using Trip Manager.

My suggestions:
- don't give up on the XT2, just eliminate the Tread app.
- don't expect Garmin to fix anything, just come to this forum and accept the solutions you get here.

Others here have found ways to use Tread but avoid Tread sync to the Explore database, which is the heart of the problem. I don't criticize that approach at all. I simply choose to avoid it entirely.

The Tread app syncs routes with explore. You can log into your Garmin account at explore.garmin.com to see what is there. You will see that explore does not route and does not support shaping points at all. It is no wonder why routes with shaping points get mangled by the Tread app.

[proofresistant]

I have taken note of response that do not really fit the topic, but I am ignoring, especially when there is not much appreciation how much knowledge and experience some newbies have accumulated also (based, of course, on the knowledge of the forum experts).

Back to the topic.
I think there is still a little hope for the Tread app
Based on my conversation (with whomever), I assume that the synchronisation problem is still known and hopefully optimisations are being worked on.

However, anyone who assumes that support for problems with sample routes from other sources will have any impact on Garmin may be disappointed.
Garmin has cut off the old ties (a German phrase) finally, that's just how it is.

If you want that going something forward at Garmin, you might try this:
Flood Garmin with input (Even if it's already done, continue it).
Don't let up.
Provide concrete, reproducible examples using their on-board tools (XT2 and Tread app).

PS
I have no doubts whatsoever about the old methods, and I certainly don't doubt the whole experience, as long as it fits the topic.

PPS
Hope dies last, and who knows, maybe the Tread app in general will prove to be a real added value.
Let's continue to look forward.

[turbo19]

I have taken note of response that do not really fit the topic, but I am ignoring, especially when there is not much appreciation how much knowledge and experience some newbies have accumulated also (based, of course, on the knowledge of the forum experts).

Back to the topic.
I think there is still a little hope for the Tread app
Based on my conversation (with whomever), I assume that the synchronisation problem is still known and hopefully optimisations are being worked on.

However, anyone who assumes that support for problems with sample routes from other sources will have any impact on Garmin may be disappointed.
Garmin has cut off the old ties (a German phrase) finally, that's just how it is.

If you want that going something forward at Garmin, you might try this:
Flood Garmin with input (Even if it's already done, continue it).
Don't let up.
Provide concrete, reproducible examples using their on-board tools (XT2 and Tread app).

PS
I have no doubts whatsoever about the old methods, and I certainly don't doubt the whole experience, as long as it fits the topic.

PPS
Hope dies last, and who knows, maybe the Tread app in general will prove to be a real added value.
Let's continue to look forward.

Continuing with what you're saying, I think it could be a good option for people who travel a lot.

If the app worked well, and the syncs weren't too much of a problem, I think it would be a good idea to be able to draw on the fly in the Tread app.

Last year I traveled through the Balkans, and having the entire Michelin Guide on my tablet made it much easier to create routes for each day. I could also view the pre-drawn tracks from home, which could help guide me. In my case, the route times calculated are often not as accurate as those calculated with Google Maps or Waze, for example. Therefore, I don't usually mind navigating tracks instead of routes. If you're one of those who has every millimeter of the trip calculated in advance, this doesn't make much sense, but for those of us who are a bit on the fly, it's very useful.

It also serves as a "mini Basecamp." I can consult all the Tracks and WP collections during the trip (for example, The Most Beautiful Villages in France) and draw on them.

As @proofresistant says, I'd like to give it a try; I think the idea is good. The problem is that it has too many bugs, and it should be more "friendly" to routes drawn in Basecamp or similar apps (MRA, Kurviger, etc.).

[Oop North John]

A new problem, or one I'd not noticed before.

The time between the start and only other point, ie the finish, should be the same in the headline journey time as the time between the two points. Except for the attached it is badly wrong!

Reported in Tread.

[GeePee]

Ive had a reply from Garmin. I didn't mention about the Cameras. They need another test before passing it on to the development team as a bug. So I'll jump through that hoop, and mention that issue at the same time.
/quote]

I am so relieved to find this post because I am experiencing the same problem, which drives me m*d!
I recently purchased an XT2 to replace my Zümo 350.
Custom POIs work and display fine with the old Zümo 350.
My XT2 does not display the custom POI icons...
Nothing appears even if I go to the Categories / Custom POIs and select the information button.
POI at the centre of the map that displays, but NO ICON.
I was desperately trying to figure out what I was doing wrong…
Apparently, nothing!
It a software BUG.
If you need endorsement, please let me know.
Do you have an e-mail address, URL where I can confirm there definitely is annoying BUG?
Thanks.

[Oop North John]

Found out that the XT2 and Tread both prevent routing through a road that is closed due to it being time limited if you're between the closure times.

I was checking out routes in Tread from Fussen to the Dolomites via the Timmlsjoch pass and was getting some unwanted routes, until I worked out what was happening.

Road opening times here:

Timmelsjoch - High Alpine Road & Timmelsjoch Experience | Gurgl | gurgl.com https://share.google/5DJBVyveMUSaQO8wq

[jfheath]

That is good info @Oop North John .

Map source (and Basecamp) have 'always' taken into account roads with seasonal closures. It took me a long time to work out what was going on because it was only a short section of road that it would not route along. Once I realised it was over a summit (which wasn't immediately obvious to me) , the solution was easy - I had to plan the route on the date that I would be riding it. I was planning in the cold winter months for the following year's Summer ride so I changed the computer date from December to August and it all worked ok.

I don't think that I knew about setting the date of travel in the Via Points at the time - I would have been using Mapsource at the time, so I didn't try that.

I have only one example where I have seen a local road being treated as impassable by the recent Zumos, when in fact it was only closed between 22:00 and 06:00. It's not enough to draw a firm conclusion that the XT / XT2 may not be able to handle such timed closures. Just a suspicion.

Whether the map closure data is now defunct with the arrival of phone based data streams, I do not know.