More Zumo woes: what about the new update?

[er-minio]

Still in France. All going well apart from weather and me getting sick (more of that in a report post ).

All the routes I created for the Zumo worked 95% ok and almost never had to rely on the tracks hidden underneath*.
There is 2 of us, both with XT, both with latest firmware update and maps.

The issues are: zumo sometimes places the shaping points off the road, so it tells you to turn left for no reason. Or sometimes ask you to do a u-turn as if it wants you to ride twice over the shaping points.

Interestingly the behaviour is different between the two sat navs. Like: these errors are totally randomized between the two units.
Tomorrow I'll check his avoidances, on mine I have faster time and the only avoidances are unpaved roads and (maybe) sharing lanes or the other "odd" setting, as I general plan my routes down to details.

What happens is: Zumo every once in a while (more in built up areas) provides some spastic detours...

I generally put shaping points every 2 miles, so this is kept under control, but the few times I made routes with shaping points every 10k, or let it route just to a destination... it has been completely unreliable. I now have to double check every time it suggest to take a turn (manually zoom out, etc.)

Also, every time I deviate from a route for more than 500 meters... it cannot calculate.

The problem is compounded because in the example above (Rue Curie) the road was clear, I just kept going straight, and midway (we are talking 300 meters or less) it said "I cannot recalculate" and dropped it there. Had to stop at the side of the road and reload the route.

Imagine that this happened about 4 or 5 times while trying to get out of Valence... not ideal for an "adventure GPS"

These were happening on my unit only, not my friend's.

I noticed a new update came out in the last 48 hours. What is that for? Seems like a bug fix to me? Anything related to this by any chance?



*once again: the tracks management on the XT with Explore accounts is completely retarded. Highlighting every track within 200k is a stupid idea.
In the area where we are riding I have several routes (various options per day) each route has its own track (because I cannot trust the sat nav) so... it is essentially a clusterfuck on the map.
I do keep the "active" track in blue and make the others gray... but it is a lot of menus to tap through... instead of being able to activate a single track...

 

[er-minio]

I would add... I was trying to update the Zumo from the hotel tonight... but stupidly I connected the Zumo to the Ibis Wifi... that is a captive network (asks your detail to authorise the connection).
Zumo apparently cannot handle that and freezes as soon as it connects to the wifi... I now cannot start it and have to wait to be away from the hotel tomorrow to reboot it.

 

[casbar]

No idea what is going on. I have had my xt for nearly two years. Nav with routes and tracks with trips across France and Belgium and UK and it has never let me down. I have plotted all routes with MRA.

 

[Wapping]

I am with casbar on this.

The only time I had problems with my XT was when the TFT screen on my new 1600 was leaking EMF’s, sufficient to affect my XT and my phone. In all my many years of Garmin ownership, I don’t think I have ever seen the message ‘Cannot calculate the route’.

From a look around in Google, there are some references out there to ‘Cannot calculate the route’, many of them coming from America. The common theme is:

A. There is a load of guessing (much of it bollocks) as to what it might mean and why it appears.

B. A maybe compelling reason seems to be that, the device thinks (or knows) the owner is off-route. The device gives out a number of requests to perform a U-turn, which the owner ignores. After receiving repeated refusals to perform a U-turn, the device gives up and displays the message that it is unable to calculate a route. Of course I have no idea if this reason is correct.

C. Another possibly compelling reason, is that some think the problem happens when a part of the route is created using Open Street Maps. Again, I have no way of knowing if this is even remotely correct. To this, there is another school of thought, that it is some misfit between the conventional Garmin maps and the Topo maps, both installed in the XT.

Just from Google, it seems to be a very US-centric problem.

I did though find this: https://support.garmin.com/en-GB/?faq=7wWiqrx3Qx9BmP0IF1usI9

 

[er-minio]

The weird thing is that the “cannot calculate” happens on mine only. My friend’s recalculates.

I’ll check his settings this morning.

 

[Keith Chapman]

I had Cannot Recalculate message on my old 550, but that seemed to be because a bit of the map was missing.

You have to be careful when creating routes to make sure that you are accurate with the placing of points, I have put them on the wrong side of the road before now and my unit tried to send me back to hit the mark. A friend did a double crossing of the Humber bridge for exactly the same reason

 

[crumbles]

Whilst away last year having a jolly in Europe last year with No routes planned,just a wake up in the morning and where shall I go today...type jolly..
I am no Garmin expert and even basecamp is a minefield my brain does not understand..

I Looked at a map,point finger,and then look on Xt for the place and say go there..

Several times it did the same too me..even taking me off the main road into the country side and then back onto the road I was on again..
But miles further down...
I ended up in Fetiya eventually..
But I had friend's there..

 

[Wapping]

The weird thing is that the “cannot calculate” happens on mine only. My friend’s recalculates.

I’ll check his settings this morning.

Whilst I have my device set to not recalculate (or to prompted, yes or no) I - like your friend - have never seen the warning.

I don’t know why but I think I smell some misfit in the maps installed into your device but not your friend’s. I say this only because the only time(s) I have had a significant problem, is when I have accidentally selected both the generic Garmin map and an Open Street Map, installed on an SD card.

I could though be miles wrong.

 

[er-minio]

I do have an OSM map installed, but it is disabled.
But it might have something to do with it.

I’ll email garmin but I expect the usual, useless, “reset the device” advice.


PS. I know that the OSM map is disabled because, if it is on by mistake and hidden BELOW the city navigator map layer, you lose the speed limit indicators and distance to turn info. So, easy to spot.
We discovered this a couple of years ago on this very pages

 

[casbar]

I did have an issue on a uk route, where if I deviated off the route, the xt came up with can not recalculate route. Only happened once and I contacted Garmin support. They advised me to go onto the xt drive and delete all the files in the archive folder. Which I did and never had another issue, apparently sometimes the files in archive can get corrupted and this impacts the recalculation. Maybe give them a call.

 

[Wapping]

….
We discovered this a couple of years ago on this very pages

We did indeed.

 

[Popell]

I would add... I was trying to update the Zumo from the hotel tonight... but stupidly I connected the Zumo to the Ibis Wifi... that is a captive network (asks your detail to authorise the connection).
Zumo apparently cannot handle that and freezes as soon as it connects to the wifi... I now cannot start it and have to wait to be away from the hotel tomorrow to reboot it.

Could you hotspot to your phone?

 

[Berin]

I do have an OSM map installed, but it is disabled.
But it might have something to do with it.

I’ll email garmin but I expect the usual, useless, “reset the device” advice.


PS. I know that the OSM map is disabled because, if it is on by mistake and hidden BELOW the city navigator map layer, you lose the speed limit indicators and distance to turn info. So, easy to spot.
We discovered this a couple of years ago on this very pages

You could try the reset method l posted in the other thread. I think I had a corrupted file somewhere causing problems and that fixed it. You will lose your data but not your maps.

Also do yourself a favour and en,tirely ditch Explore - l mean disconnect it from your device and delete it from your phone


Sent from my iPad using Tapatalk

 

[casbar]

Delete the files in the archive folder, that worked for me. You don't need them.

 

[er-minio]

I have some more “cases” from today.
In Reims now, home tomorrow. Will investigate. What casbar says makes sense re: removing leftover files.

Berin: I always forget to remove the pairing with Explore. I know that of I do that, tracks go back to the old NORMAL behaviour.

 

[John Armstrong]

With my XT I now don't trust it and will use the bodge of having a track to make sure the XT's doing the right thing. Such a pity that it's such a superb machine, apart from it's raison d'etre to be a navigation device.

 

[er-minio]

Could you hotspot to your phone?

Didn't think about it.
I hotspotted Garmin Express to download the maps to my laptop at the beginning of the vacation, since I am using another MacBook. Downloaded the damn maps 3 times on roaming and all three times it failed.

 

[casbar]

With my XT I now don't trust it and will use the bodge of having a track to make sure the XT's doing the right thing. Such a pity that it's such a superb machine, apart from it's raison d'etre to be a navigation device.

Half the problem is people do not understand the difference between a track and a route. The track is like a line on a map and will never change. The route is the device using whatever priorities it has been told to try and keep to the track. Even having your phone connected, it will change a route if it gets traffic information. The best way is to display a track and a route, then you can manually get yourself back onto the track if the device decides to re route you. There is nothing wrong with the XT.

 

[John Armstrong]

Half the problem is people do not understand the difference between a track and a route. The track is like a line on a map and will never change. The route is the device using whatever priorities it has been told to try and keep to the track. Even having your phone connected, it will change a route if it gets traffic information. The best way is to display a track and a route, then you can manually get yourself back onto the track if the device decides to re route you. There is nothing wrong with the XT.

Having used Garmin Sat Navs since the SP3 the XT has been the only one I don't trust with its routing algorithms. This is the first sat nav where people are having to use the track and route options to overcome the routing mayhem, especially if you've downloaded a route with a via /way point, and it gets into the repeated u-turn madness.

"Fastest" in the routing options used to mean the shortest amount of time, now it seems to mean it'll use "faster" roads for as much as possible, even if that's not the shortest time.

You are correct in your last sentence, but only when it's (a) shut down or (b) not navigating.

 

[Wapping]

My XT ‘experience’, using bespoke routes, created by me, has been fine. I’m happy to say.

The only problem was caused exclusively by the leaking EMF’s from the new 1600’s TFT screen but those screwed my phone as well.