Result - the XT2 is well capable of getting stuck in a RUT. But a very easy solution definitely fixes this behaviour.
The image on the left is the planned route as produced in Basecamp and how it appears in the Zumo XT2 after it has been imported. The route starts bottom right, and travels in a counter-clockwise direction passing through saved Waypoints
01 Start (about a mile up the road) from my current location.
02 A65 Skip this.
03 Kettlewell (set as a shaping point)
04 Hawes Exit
05 Cleatop
06 is another shaping point - and I'm not bothered about anything after 05 Cleatop.
The first image shows the original route from Basecamp. The second image shows the recalculated route - the same as that produced after pressing Skip to miss out 02 Skip This Via Point. I intend to take that early trun to the South of my first picture - thus deviating from the XT2s recalculated route.
The third image shows what happened on a previous test on the XT - I was 3 miles from the Via point at Cleatop having put up with 11 miles of U turn request every few hundred metres. It was sill insisting that I go back to the junction. In fact it isn't trying to get me to go to the junction - each U turn request only calculates a new section back to its previous calculated route - a few hundred metres back.
- Ribblehead RUT v OK.png (767.73 KiB) Viewed 1240 times
But this final test using the Copied route on the XT2, the route recalculate south - just like image 2 - and it did it the moment that I took the road south instead of continuing along the plotted route.
And Yes, the mImport Byte fix makes it behave properly. But the Copy function on the XT2 is a nice easy option - similar to resaving the active route on the XT - but that methods adds your current location as the new start. The XT2s Cpy function doesn't - and the new route behaves exactly like a route that has been built on the XT2 itself.
I have to say though - in a different test on roads where there were plenty of alternatives, the XT got stuck in a similar RUT to about a mile before reaching the end point. The XT2 showed signes of that, but it managed to escape from it much earlier - about 5 miles after the tipping point and about 10 miles from the final destination. So the XT2 is different in what it does and how it does it. But RUTs are still possible- but so far they have not happened for me on the XT2 or the XT if the imported route has been 'nobbled' to make it look like one that has been built on the XT/ XT2 screen itself.
Footnote. The Tread App - in spite of what you might read to the contrary - I think is a game changer. Routes from the tread app are synchronised with the XT2, and the XT2 treats them as Saved and will behave perfectly from the outset. I'm not a fan - because of the size of the screen - but the features on the Tread App are reproduced on the XT2 screen and you can work on one and then continue on the other. And the XT2 route planner app is much much easier to use then that thing that was put onto the XT.
More on that later.
