XT Insists that I follow original Route, rather than calculate a new one.
Posted: Fri Jan 14, 2022 5:14 pm
I am starting this thread as an individual topic to try to find out whether anyone else has experienced this issue.
The problem has been lodged with Garmin a few days ago. I have yet to receive a reply.
I am not after suggestions for what I could have done to avoid this problem. I know how to do that. What I want to know is whether anyone else has come across a similar situation where the XT refuses to deviate from a route that the XT itself has calculated.
The problem occurred after the route was recalculated when I skipped a Via Point at Hawes. The XT created a new route from my current position to the next Via Point at Mearbrook (at the south end of the red line on the OS map. I have shown the route that it plotted as the cyan coloured line on the Ordnance Survey map below. According to the XT this route is marginally faster. That's OK. That is not the problem.
Click the map to obtain a clearer image. The knife/fork symbols have nothing to do with the route. I must have had up ahead places turned on.
When I arrived at Ribblehead, I took the route that I had originally plotted - the red route, expecting the XT to recalculate its route when I deviated from the Cyan Route at Ribblehead. 5 minutes down the red route B6479 would make this a much faster option. That is what the 590 and 595 would have done.
Not the XT. It refused to take the route ahead - as if it thought that 'Beyond here there be dragons'. It kept recaclculating the route, finding new ways to make me turn back to pick up the cyan route at Ribblehead.
Here is the screen shot just after passing through Settle.
Now, how ridiculous is that ?
When I got home, about half an hour later, I asked the XT to plot a route from a mile south of Ribblehead to Mearbeck. It plotted the (red) route without any problem. So why was it determined to take me back.
Eventually, with less than a mile before the red route met the cyan route, it gave in and plotted the route ahead.
Here is the screen shot. The white arrow indicates the roundabout where the red route and the cyan route on the A65 meet up.
I want to go back and repeat this exercise in case it was a glitch caused by some other issue. (And I now have a different XT). There are no other route points involved in this example. There were no avoidances set and the Zumo had been reset before I loaded the route from Basecamp. Auto-recalculate was turned on, traffic was disabled.
v6.30 of software Europe 2022.20 maps. No 3rd party maps (like OSM) were loaded.
The ordnance survey map is obtained from OS Open Data. It can be used freely providing their copyright is acknowledged with this statement:
Contains OS data © Crown copyright and database right 2020.
The problem has been lodged with Garmin a few days ago. I have yet to receive a reply.
I am not after suggestions for what I could have done to avoid this problem. I know how to do that. What I want to know is whether anyone else has come across a similar situation where the XT refuses to deviate from a route that the XT itself has calculated.
The problem occurred after the route was recalculated when I skipped a Via Point at Hawes. The XT created a new route from my current position to the next Via Point at Mearbrook (at the south end of the red line on the OS map. I have shown the route that it plotted as the cyan coloured line on the Ordnance Survey map below. According to the XT this route is marginally faster. That's OK. That is not the problem.
Click the map to obtain a clearer image. The knife/fork symbols have nothing to do with the route. I must have had up ahead places turned on.
When I arrived at Ribblehead, I took the route that I had originally plotted - the red route, expecting the XT to recalculate its route when I deviated from the Cyan Route at Ribblehead. 5 minutes down the red route B6479 would make this a much faster option. That is what the 590 and 595 would have done.
Not the XT. It refused to take the route ahead - as if it thought that 'Beyond here there be dragons'. It kept recaclculating the route, finding new ways to make me turn back to pick up the cyan route at Ribblehead.
Here is the screen shot just after passing through Settle.
Now, how ridiculous is that ?
When I got home, about half an hour later, I asked the XT to plot a route from a mile south of Ribblehead to Mearbeck. It plotted the (red) route without any problem. So why was it determined to take me back.
Eventually, with less than a mile before the red route met the cyan route, it gave in and plotted the route ahead.
Here is the screen shot. The white arrow indicates the roundabout where the red route and the cyan route on the A65 meet up.
I want to go back and repeat this exercise in case it was a glitch caused by some other issue. (And I now have a different XT). There are no other route points involved in this example. There were no avoidances set and the Zumo had been reset before I loaded the route from Basecamp. Auto-recalculate was turned on, traffic was disabled.
v6.30 of software Europe 2022.20 maps. No 3rd party maps (like OSM) were loaded.
The ordnance survey map is obtained from OS Open Data. It can be used freely providing their copyright is acknowledged with this statement:
Contains OS data © Crown copyright and database right 2020.