MRA Community Forum

@M.-Schrijver said: Every app has indeed their own quirks. But to my opnion. MRA must be used in a smaller bandwith to get to work correct. There is less room for user errors for the app to handle. Other apps can handle user error better without giving problems. Exactly my point. Let’s just say that is why I personally am not a good match for MRA. (though I am with a range of other navigation apps, that’s for sure ) Simply because I don't want complexity when I'm out on the road and want to focus on the experience of the ride, instead of navigation support that keeps pulling me over because I’ve probably done something wrong again. However, the fact that my setup crashes 6 to 8 times a day makes it unusable for me (for me, that is). I don't experience these crash issues with other apps, so that is where my driving pleasure lies.

I hope one day via points can be skipped. I use shaping points to work around this limitation. This has a side effect : all shaping points are visible, also those which do not represent anything useful and are only added to shape a route. note that via points can be skipped when you add a diversion to avoid a roadblock.

WenPlanung [image: 1783844722389-img_0241.jpeg] In der MRA Navi App Next [image: 1783844746640-img_0242.jpeg]

No not correct. If you pause a route, MRA will continue automaticly when you restart. The function start from nearest point must be active on your phone

It's on the wishlist

@Brian-McG Well, I just ran the route again, running the XT3 and MRA Next app on my phone in parallel. Success! I suspect (it's just my best guess) that skipping WP#7 manually instead waiting for "Skip Waypoints automatically" to kick in was the difference. The first time around, it really did take (in my mind) too long for the skip to trigger, which created problems around WP#8 that doomed the route. I agree that the "Offline Navigation" probably didn't affect what happened with WP#7, but I needed it any way for the second half of the route, where cell coverage was spotty and sometimes non-excitant returning back over the mountains. As for the XT3, instead of just letting the route 'sleep' until auto rejoining further up the road, I instead selected off-route recalculate just to see the result. On the XT's I almost never issue a recalculate (that's another discussion), so it was an additional learning experience too. Like MRA, it recalculated back to the route as originally intended. I'm sure we could have a spirited discussion on the pros-and-cons of a dedicated Garmin GPS vs. the MRA phone app. They both have relative advantages/disadvantages, and a lot depends on where and how you ride. For me, the XT3 will mostly be my first choice. But you're correct -- that's better left to a separate dedicated thread. Anyway, thanks for your time on this. I've learned a lot about the app going through this process. Not all scenarios can be documented, and learning by doing is the only solution. At least I'm comfortable enough now to use either the XT3 or the app based on the situation.

You are most welcome! Seems like an epic trip!

Just tested in the V5.2.1 Beta, just goes [image: 1783797423112-img_0234.jpeg]

What operating system are you using and can the systems file explorer "see" the device?

@martin-white I have experienced that a public file with motorcycle closures for Germany has also caused this message. In the downloaded file were POI s of the signs at the beginning and at the end of the route which is okay but it was also between beginning to end a route in this file. I couldn't see it in MRA and loaded this public file into Basecamp, where I was only able to see it. Then deleted the routes in BaseCamp in the file and there were 106 POI left. I read this file again, and then everything was good. VG [image: 1783781726974-img_0230.jpeg] Link to the file Klick [image: 1783781990155-img_0231.png]

@Mister-B ah ok, dat is toch wat anders, dan waar je ons aanvankelik heenwtuurde. Nee dat kan niet. Wat je wel kunt doen, zoals Nomko schrijft, is, het ount als viapunt aan je route toevoegen en later in een adequate POI-manager (ik gebruik nog steed good old Basecamp daarvoor 🫣) de POI aan een bestaande- of nieuwe lijst toevoegen, die exporteren en in MRA weer inlezen. Het is nogal omslachtig, maar dat is tot nog toe de enige manier.

The BMW Nav 5 can handle a maximum of 30 announcing waypoints (via points) per route, you can also include up to 125 unannounced shaping points between any two waypoints. You have probably exceeded the Via point (announced waypoint limit.). If you MUST have a route overview you'd probably be better exporting the master route as a Track to the Nav 5 and displaying it beneath the magenta line of your routes.

Albyus said: @LE-DIZES-Freddy said: @Albyus È il routing di OpenStreetMap (OSM) a causare questo problema. Utilizza HERE o TOMTOM e il problema scomparirà. traduction Google Ci provo, grazie !! Adesso SI !!!!! tutta un altra cosa, grazie !!!!!!!!!

Hi, I am importing the location of Speed Cameras into MRA via the Library "Add" function. My problem is that there are in excess if 3000 POI's in my file and when added into the I.O.S MRA App, i get an error message stating "Too Many POI's. Only the first 2000 will be displayed" , see screenshot from the App below. I have tried splitting the POI file into multiples of 1000 POI's but i still have the same issue. Is there a limit to total POI's that i can add, if so can it be increased please ? [image: 1783753543432-screenshot-of-mra-app-on-ios-showing-poi-issue-resized.png]

Aaah! No, I just asked whether it worked with the bmw wonder wheel. Why would BMW do that. Ok, we know, to encourage you to use their (expensive) cradle and navigation app…

I’m aware of these buttons. Simply, I never use them because the program is zooming in and out as it should. The issue is that since shortly the programming doesn’t auto zoom. Like today the navigation was zoomed in and staid at that level, it didn’t auto zoom on behalf of speed, roundabouts or what so ever.

The next step is still in the test, so you can turn it very easily from horizontal to vertical ... see sample idea [image: 1783701175534-img_7829.jpeg] This is the 3D pattern print, there are still 10mm missing because of the lock of the BMW bracket. [image: 1783701264038-img_7826.jpeg] [image: 1783701282444-img_7825.jpeg] [image: 1783701310022-img_8618.jpeg] [image: 1783701390362-img_0193.jpeg]

That’s actually quite helpful AI work, thanks. I have been working on a tutorial video - it’s with the MRA team for review and I have a few more tweaks to make. I had an AI review of the script which was helpful; I’ll cross-check with the above (and other posts) and perhaps also make a short printed quick reference card like the AI instructions above.