Auto skip many waypoints by itself while I was on route. [5.2.0 - 474]

[M. Schrijver]

Today i had a nice route in the border region of The Netherlands and Germany. In area around Uelsen the cell coverage is pretty bad (KPN and Odido).
It it maybe a coincident. But at the moment MRA siwtched from online to offline navigation (due to the bad cell coverage), MRA skipped 14 waypoints automatic. These were all upcoming waypoints besides the endpoint of the route. Around 70 km of route length.

I heared the skipping beep and saw a lot of waypoints were skipped. I stopped to correct this. This was also the moment i saw there was no cell coverage anymore and MRA was switched to Offline modus. I selected the next upcoming waypoint went on driving. After a few kilometers i hear the autoskipping sound again. Again the same amount of waypoints were auto skipped. This time the cell coverage was back and Online navigation was selected again.

What happend here?

[Reid Squier]

I had the same problem in north west Massachusetts 4 days ago. I was also in an area of poor cell coverage. MRA skipped about 4 waypoints. I reset MRA to navigate to the next waypoint. Then about 10 minutes later, it skipped another 4 waypoints.

[Con Hennekens]

@M.-Schrijver, I don't know what could have happened, and I do not share your experience. What I do know at one time it was implemented that the auto skip algorithm could not skip more than 10 route points at once. I cannot imagine that this has changed, since it was implemented for good reason. Loop protection for example. Did this occur where loops are in play by any chance?

[Con Hennekens]

Also: I cannot imagine how poor cell coverage in itself would trigger recalculations. Normally only leaving the route does. The human mind is programmed to find links between occurrences, even if there are none. But if it is really correlated, it's an interesting case

[paul69]

hi @m.-schrijver
I would also like to mention this does seem very strange behaviour regarding online/offline, cell coverage etc
I recently rode a multi-day tour in Ireland (9 days), and did not have any issues with regards to internet/cell coverage
I use an oukitel RT3 rugged tablet that does not have a SIM card therefore no cell or internet access and everything is navigated offline.
all maps are downloaded to the device and MRA is synced before leaving.
not much help to you I'm sorry, but this may highlight that cell/internet should not have any bearing on navigation.
️

[M. Schrijver]

@con-hennekens
This is the route i'm talking about:
https://www.myrouteapp.com/nl/social/route/14017569?mode=share

And a screenshot were I combined the recorded tracklog and the route

I was heading towards waypoint 40, around a quarter between 39 and 40, when i heared a beep for the autoskipped waypoint. At that moment i saw waypoint 53 as my next waypoint. I stopped and switched on the screen of my phone (i use Android Auto). That was the moment i saw the orange message for switching from online to offline. I went in the menu and manually selected waypoint 40 as my next waypoint. And start driving again.
Around halfway waypoint 39 and 40 i heared the beep again and saw i was skipped to 53 again. Again switched on screen of the phone and again i saw the message switching from offline back to online.
Again selected waypoint 40 as my next waypoint and from that moment on, it went well. Also i didn't see any lost cell coverage anymore.

When i look at the route. The first time it happend, waypoint 53 was one of the closest waypoints. This could explain something. But the second time waypoint 53 was definitely not one of the closest waypoints. But still it was choosen by MRA

[LennyO]

@M.-Schrijver It's a beautifully made Route! I do not see anything strange about it.
The only little thing I see under full magnification is that at the point 40 the black line brakes.
I don't think it would cause this issue... or....

While having nothing to offer in the way of the solution, I am very interested to learn what caused it...
Following this closely.

[Hans van de Ven MR.MRA]

Experienced this twice last week as well; while passing a waypoint, I got the message 'waypoint skipped'... Even though I was simply following the route and hadn't deviated from it.

[M. Schrijver]

@lennyo i recognise what you mean. When i make a route myself and i see this kind of things. I correct them. But i don't think they effect the navigation. I think it is more a kind of a screen error than a real opening in the routeline. This time the route came from the Route Expert library.

@hans-van-de-ven-mr.mra Skipping one waypoint without any signs why, is something i see more often. Maybe the same deeper underlaying cause. I don't know.

[Marinus van Deudekom]

@LennyO the breaking happens when the shaping point is nog 100% on the route. When you move it a bit of disappears

[LennyO]

@Marinus-van-Deudekom 100%! I am aware of that. Thos was the only thing I could spot on the route.
But this should not the cause the problem with crazy skipping.

[Marinus van Deudekom]

@LennyO totally agree with you
I hope that @m.-schrijver has send in the log files so Corjan can have a look at those

[M. Schrijver]

Please remind me. How can i download the log files

[RetiredWingMan]

Long press on the version number.

[M. Schrijver]

Today i noticed also something in autoskipping procedure. I don't know if the rootcause is the same. But still i write it here.

• From my current position i need to drive approx. 20 km before i'm on the route.
• My standard setting is "Closest point" as startpoint when (re)starting a route.
• Auto skipping is enabled as a default setting.

Today MRA auto-selected "point 7" of the route as startingpoint. I changed this manual to "point 2". MRA created a route from my position to "point 2". So far nothing strange.
Pretty after riding away from the where i started, i did need to deviate. MRA did a recalculation and skipped to "point 7". The recalculation was expected but auto-skipping to "point 7" not. Changed manual back to point 2 and keep on driving. A bit further and nicely on (pre-)route, MRA started a recalculation and auto-skipped to point 7. This time both were complete unexpected.

[Marinus van Deudekom]

My guess is that it's normal behavior because you've stated that MRA saw nr 7 as the nearest point therefore skipping 1 to 6

[M. Schrijver]

You can see it as normal behaviour. But there are more ways to look at it.
The selected startpoint of the route is kind of an endpoint for the extra added part of the route. An endpoint normally doesn't change.
Another point of view. When you are riding the route and you are deviating from the route and the next waypoint is still ahead of you. The navigation won't skip this one either.

[Brian McG]

@M.-Schrijver I agree with @marinus-van-deudekom the system is pretty much doing what you asked it to do

your settings "My standard setting is "Closest point" as start point when (re)starting a route." set the system up to designate point #7 as the start

when this is locked into MRA & you then deviate & cause a recalculation, it is going to recalculate to point #7