Via-punt niet herkend - te kleine marge
-
Not the only one @Nick-Carthew. This is fascinating @Stefan-Hummelink and @Con-Hennekens, and something I knew nothing about until now.
I know that the Dev Team are looking at testing speed of connection with the offline and online auto action following some feedback that others and I have given. I too have had similar issues to @Con-Hennekens with strong signal areas. Curious where this may end up and the solution. Intriguing thread guys.
-
@Stefan-Hummelink @Con-Hennekens As someone who has zero knowledge of any of the technical matters that you two are discussing, I find myself becoming slightly aroused with your conversation
@Nick-Carthew Oh Gosh ... Getting a Brit aroused is way beyond my expectations and certainly not a what I call positive collateral hahahahahaha.
-
@Stefan-Hummelink @Con-Hennekens As someone who has zero knowledge of any of the technical matters that you two are discussing, I find myself becoming slightly aroused with your conversation
@Nick-Carthew, I am glad for you that you reach such a state on written words alone
I am the first to admit my knowledge on the subject is rather slim. I am just trying to wrap my head around the problem at hand.@Stefan-Hummelink, yes I am aware that the app itself does not talk directly to the hardware. But if devs want to solve this, they first must know what to solve. In my imagination, while the hardware switches from antenna to antenna, there will be a short moment of "no data" while the signal strength is high. The problem is that switching antennas can happen literally ANY time. implementing an internet connection bandwidth test will NOT prevent the hardware from switching towers, resulting in a short "no data" phase. If we know that, for example, the "no data" phase of such a switch is 20ms, dev could perhaps implement a second calculation event 50ms after the first one fails. Probably enough to overcome a no data phase, and little enough for anyone to notice. All completely hypothetical of course.
@Nick-Carthew, are you okay?
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
@Nick-Carthew, I am glad for you that you reach such a state on written words alone
I am the first to admit my knowledge on the subject is rather slim. I am just trying to wrap my head around the problem at hand.@Stefan-Hummelink, yes I am aware that the app itself does not talk directly to the hardware. But if devs want to solve this, they first must know what to solve. In my imagination, while the hardware switches from antenna to antenna, there will be a short moment of "no data" while the signal strength is high. The problem is that switching antennas can happen literally ANY time. implementing an internet connection bandwidth test will NOT prevent the hardware from switching towers, resulting in a short "no data" phase. If we know that, for example, the "no data" phase of such a switch is 20ms, dev could perhaps implement a second calculation event 50ms after the first one fails. Probably enough to overcome a no data phase, and little enough for anyone to notice. All completely hypothetical of course.
@Nick-Carthew, are you okay?
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
@Nick-Carthew, are you okay?
I'm lying back now and having a cigarette
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox BJ8 -
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
@Nick-Carthew, are you okay?
I'm lying back now and having a cigarette
@Nick-Carthew said in Via-punt niet herkend - te kleine marge:
I'm lying back now and having a cigarette
-
Today I drove on the A12 near Gouda and saw 2 times that the app was going offline for a moment. Just a few seconds and than it was back again. Thatβs a problem Iβve never had before. This must be a bug in the MRA-app.
-
I experienced the same issue as the OP this week. At first I thought maybe my waypoint was off the road. I knew where I was going so it didn't matter but when I got home and checked the route, the waypoint was on the road.
It also happened at the end of two different routes with my endpoint. I rode through the final waypoint and it kept trying to route me back to it. I am using a Pixel 7 and this happened once on my phone and twice through Android Auto.
-
I experienced the same issue as the OP this week. At first I thought maybe my waypoint was off the road. I knew where I was going so it didn't matter but when I got home and checked the route, the waypoint was on the road.
It also happened at the end of two different routes with my endpoint. I rode through the final waypoint and it kept trying to route me back to it. I am using a Pixel 7 and this happened once on my phone and twice through Android Auto.
@Tom-Cat said in Via-punt niet herkend - te kleine marge:
I rode through the final waypoint and it kept trying to route me back to it.
This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
@Tom-Cat said in Via-punt niet herkend - te kleine marge:
I rode through the final waypoint and it kept trying to route me back to it.
This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
@Tom-Cat said in Via-punt niet herkend - te kleine marge:
I rode through the final waypoint and it kept trying to route me back to it.
This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.
This is a bit unusual. I've never seen that in a navigation app before.
-
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
@Tom-Cat said in Via-punt niet herkend - te kleine marge:
I rode through the final waypoint and it kept trying to route me back to it.
This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.
This is a bit unusual. I've never seen that in a navigation app before.
@Tom-Cat I prefer it that way though!
-
I find it inconvenient. Extra work and annoying.
-
I find it inconvenient. Extra work and annoying.
@Jack-van-Tilburg, it's ideal. You don't have to restart the route of you need to go around the block. It's VERY convenient. About what extra work are you talking?
Thereby, it has been discussed before. It's by design, so it is what it is.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
@Jack-van-Tilburg, it's ideal. You don't have to restart the route of you need to go around the block. It's VERY convenient. About what extra work are you talking?
Thereby, it has been discussed before. It's by design, so it is what it is.
@Con-Hennekens said in Via-punt niet herkend - te kleine marge:
Thereby, it has been discussed before. It's by design, so it is what it is.
So no further reaction is necessary.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better π
Register Login
-
116158
-
014285
-
07110
-
08193
-
0444
-
0326
-
0464
-
28617.0k
