I've had enough. But going to waste some more money on Garmin.

You can set a wider track in the Zumo XT so that you can see the magenta line by customising a theme.

This is the line you need to change.

View attachment 501437
Hi Mzokk, This would be amazing if you could fully explain how to do this? It appears to be a notepad document? how do you apply it to the device?? can this be applied to a Nav6 too???
 
Hi Mzokk, This would be amazing if you could fully explain how to do this? It appears to be a notepad document? how do you apply it to the device?? can this be applied to a Nav6 too???
Yes I would imagine that it could work for the NAV 6 as it does on the old Zumo 340/90. I may have explained customised themes here elsewhere. If I have I'll link it if not I'll plonk it here.
 
I do the same with the route/track. Just make it start outside the town/location where I am generally staying (also because in most cases I book day by day).
The idea of putting a separate waypoint at the start makes sense. I do that for the offroad bits. Should start doing it for tarmac routes too.

The detours my Zumo does are like these:
diezumo01.jpg


Never solved. Similar to what you see in the YouTube recording above.

I find that, on the XT, if you set the track to "widest" on some zoom settings you can see the track below the route.
I normally show the active track in yellow, so I can see the yellow border on the magenta route and be sure that is following as planned.

I do not use the audio indications either. Just look down at junctions.

Given all this, I was considering I can live with a Montana for road use.
Would setting the navigation options to shortest distance avoid that silly detour?
 
The older Garmins like the 390 and 590 layered the track above the route so you know instantly you are on the desired route or if you've been recalculated.
You can do that on the XT and the Montana
 
Would setting the navigation options to shortest distance avoid that silly detour?

I tried last year. You still get those sort of errors.

While I ride on B roads it will tell you to go to the side like that. Does it on motorways too. It seems to happen only when routing. If you do A to B navigation seems to work a tad better.
You have to second guess any suggested turn at all times and it gets fairly tiring (and irritating) on the long run.

BTW, this is how a track is displayed below a route (video from a couple of years ago).
As said above, yellow below magenta works a bit better:
track-route.gif
 
I had a Montana 700 for a few weeks. Could not get on with it at all. Far too customisable and then I never knew whether I had induced a problem or one of its many bugs had.

Thankfully the supplier took it back minus a deduction, and I bought an XT2. Still has the RUT problem, but you can easily adjust track widths to be wider than the routes, and do it in all sorts of colours. Doubt I'll "upgrade" to the XT3 unless this one throws itself down the road.
 
this one throws itself down the road

I threw my XT down the road in a fit of rage (RUT and route miscalculation) a couple of years ago. It survived unscathed.
I have to admit, on the hardware side I have no complaints. :)

Still has the RUT problem
I get it. But, we have to be honest, this is completely unacceptable on a device that costs 400 quid and has been on the market for more than a decade.
Not even unacceptable: fucking ridiculous.
 
At least with the RUT there are easy solutions, I can't work out why Garmin can't / won't fix it, maybe they like messing us about? Which is why the faster routing might take longer than the route that takes the shortest time.
 
My Garmin motorhome nav does the same thing Emilio, routing me off main roads and then straight back on again.

Must be a Garmin software thing.

I’ve decided that it is like a spouse, in that, it mainly cooperates well but waits until the most critical moments to let you know just who wears the trousers.
Like arriving in Spain this month, the route was sorted whilst we were waiting on the ferry, but the moment the van’s wheels touched the ground, the screen went blank and it switched itself off.
 
Having a cursory look, for some obscure reasons, on Amazon the 760i (camera - no need) costs less than the 710i…

Also, is there a CN lifetime sub to buy separately, like the one included with the Zumo series (LM)?
 
I’m a biased Garmin user. I’ve conquered Basecamp to my satisfaction.
From 550 to 660 to XT.

I’m sitting on a ferry about to leave Bilbao for Ireland. The XT didn’t make a mistake during the recent 2,000+ miles.
Today kept me off the motorway to ferry and was most enjoyable.

All my planned routes,,,,

I don’t use any audible devices while riding.
Just me, the road and the XT.

I’m very much in this camp, too.

I rarely, if ever, ask the device to take me from A to B itself. Any routes I ride, I’ll create myself in MyRoute or sometimes on the device itself. My two XT devices have been all but faultless.
 
I must be using mine differently as I don't experience any issues with mine apart from occasional detours to a side road and put this down to my route planning.
 
I’m very much in this camp, too.

I rarely, if ever, ask the device to take me from A to B itself. Any routes I ride, I’ll create myself in MyRoute or sometimes on the device itself. My two XT devices have been all but faultless.
Same as my experience. I really only use the XT for routes from MRA. The only A to B I use is "home" if I'm bored and need some guidance getting back :)
 
My two XT devices have been all but faultless.

I am starting to believe that a couple of the extra errors (RUT is for everyone, Garmin is so generous :D ) and weird behaviours I am experiencing can be due to a couple of things:

First assumption.
Mine is a very early unit. Big speculation on my part, but there might be some hardware revisions. I bought the XT when announced back in the day. The first one I had failed within a few months (console prompt at startup out of the blue) and this one is a refurbished unit I was given (not happy) from Garmin under warranty.

Second assumption.
I am growing to think that most of the errors in recalculation can be due to the length of said routes.
If you remember the conversation we had about all the calculation errors I had from the Zumo this summer or previous summer (before I resorted to only using the tracks) were on very long days: routes >6/700km a pop.

For reference, this:
xt-route01.jpg


This Spanish trip, the routes created were shorter (most within 300km) and to be fair the recalculation error or strange behaviours along those were minimal compared to this summer where most of what planned (still talking about routes, tracks are always fine) was completely unusable.
The way I create the routes is the same, yet results vary greatly.

I do not use the GS that often in the UK these days, I do not tend to use the bikes at weekends that much (and if I do, I don't really use planned routes that much), so each time I jump on the bike it's to cover significant distance abroad, so little time to troubleshoot things.


But, as said in the opening, I am kinda over having to second guess/troubleshoot/reverse engineer how the XT works (or doesn't).
It has let me down, while traveling, a significant amount of times.
Similar (less extreme though) experience from the other XTs and XT2 that the people I rode with had with them: phantom restarts, weird routing, unable to route (same mapping on both devices), unable to find location (again, same mapping), THE FUCKING TRAFFIC OVERLAY THAT POPS EVERY 5 SECONDS EVEN WHEN THERE IS NO DATA AND IT'S JUST A GRAY SIDE DRAWER, etc.

Given the way I do use the GPS: moving map, no audio, no multimedia controls, etc. I think the switch to a different device, that also works in a way that is closer to the GPSmap ones (and can navigate turn by turn a track) could be an option... and the last money I'll spend on Garmin I think. It's already a silly choice to give them some more - I know. :D

I also think there is a solution for full postcode search on the Montana. I'll investigate further :)
 
Last edited:
Second assumption.
I am growing to think that most of the errors in recalculation can be due to the length of said routes.

I have ridden day routes of about 300 miles and many more in the 250 mile range, all created carefully and checked before use. They have all been fine and followed N and D roads.

I don’t see much point in creating a route of much over 350 miles.
 
I don't know what to say.
Mine consistently creates problems. Sometimes minor, I admit, but still irritating. Both with the routes I create and route I got from third parties.

I don’t see much point in creating a route of much over 350 miles.

I do sometimes ride longer legs (6/700km) I generally like to plan it in advance, even though is not strictly necessary as - on those distances - there is a fair amount of motorways involved. Sometimes I have another person in tow, and I want to be able to give them reliable guidance (as we travel at different paces). But that is another problem.
 
Last edited:
Back on the usual, painful topic.

In this last trip, my ageing XT behaved surprisingly well for the first couple of days. Plotted and followed the routes exactly as expected. No U turn issues.
I praised in on the third day, and it all went to shit. :D


Now. I think my specific unit might have some issues.
Couple of major issues I encountered this time was the XT feeling phantom taps on the right side of the screen, opening a set of menus and changing screens while riding. This went on for about 45 minutes (and made me jump on the wrong motorway exit :D ). While this is normal behaviour if it rains, especially by the way my Zumo is mounted, weather was dry and there were no objects interferring on the screen.
After almost having it smashed against a wall, I restarted it and the issue went away for the rest of the trip.
My GoPro battery was flat, so I managed to capture just the tail end of this behaviour, not the "phantom taps". You have to trust me on these.

I've had other minor problems (U turns) that are expected, but also very fucking weird routing where the Zumo started sending me through secondary roads despite the routing settings.
Each time I was crossing a small town it would detour me from the main road... always had to double check.
It also did that thing where you are along a motorway and makes you get out on the ramp and then immediately back in. This means that you have to double check each time it tells you to turn/get off a motorway on transfers.

I do the trick with keeping the track active under the route. At least I have that.

The most annoying was: leaving Porto I had a specific route to follow. I set it up and it asked if I wanted to be routed at the starting point: yes.
After a few miles of stupid detours I realised that it was taking me via backroads.
I stopped, swore at it for a few minutes, then manually selected the beginning of the intended route by tapping on the map, and in this case, the directions where correct (jump on the motorway to get out of town, etc.)

Video here:


I had a number of restarts/resets when riding.


Now:
I am/was generally fairly happy with the rest, hardware-wise. It's the bugs that make this (for me) a pretty much unreliable product. Each trip there is a bunch of issues. (Other XT 1s and 2s in the group too).

But...

For London/inner city navigation I do use (happily) a Beeline Moto 2 as it navigates better than Garmin inside complex scenarios and it's small and more than enough data on screen. That part is sorted.

If I travel, I generally plan in advance routes and options day per day. Both routes and tracks (tracks for both backup and eventual offroad options).
I do use alternative mapping in some cases, generally off-tarmac.

Usually longer trips look similar to this:
View attachment 501361

I'd also like to be able to use proximity alerts on waypoints sometimes, for detours, etc. I can do that on the 62c. Not on XT.

When at the end of the day, or end of a specific route, I just direct the XT to the destination being it an hotel saved as a waypoint, or punching in the address manually.

I do keep it connected to the phone for data/address search.

I do not use it to receive/make calls or control the music. Do not care much about that.


Last week I wanted to have a Garmin developer at reach to shout at them for an hour before physically assaulting them... so the most logical outcome of this would be to move away from Garmin as clearly they dropped the ball ages ago on consumer nav... but me not being a logical person... I was considering (and I asked about this before in previous years) to waste some more money on Garmin and switch to a Montana 7x0i with InReach.
I do not generally travel outside Europe, but I found myself often without mobile service offroad in not-so-remote areas (Strata Florida in Wales above all, trails on the Alps in Italy, etc.) and was considering and InReach for a bit of safety. The Montana (i) has it inbuilt and works like a proper Garmin GPS (I have a GPSMap 62c and fairly happy with it) that probably would be better for my intended use.

Apart from the massive costs (Montana + Mount + CN Maps) my question is to people that made a similar step.

I know a few users here have both XT for road use and Montana for more offroad/exploration use, but I'd rather have a single device and also, as above, I consider my XT a fairly unreliable device.

Installing CN Maps is the address search decent?
I can do without the lane assist screens.

Are there any massive and known bugs (like the U turn one on the XT)?
Am I putting myself in a world of pain?
Is the screen readable compared to the XT? I do like to keep my nav in that weird position you see in the videos. Sometimes doesn't help with glare.


I do not want to have a phone affixed to my bars, and also prefer dedicated hardware.

Just a thought, it might be worth checking 'my maps' in the settings to see if you have more than one of the installed maps ticked, as that can cause navigation errors etc.,
 
No. Always one.
You can tell because, if you have multiple, the speed limit warning disappears.
I did also remove the (single) extra map I normally have installed onto the device to no avail.

As above: I am not trying to troubleshoot anymore. Just considering the switch to a different type of device... and how that could potentially be worse :D
 


Back
Top Bottom