MRA Community Forum

@Stevedo-6-0 said: @Nick-Carthew That's great. Where is it documented in the support pages? I looked but couldn't find it. Thanks I’m not sure that it is documented yet.

Probeer dat eens direct in de navigatie app zelf. Eerst in de planner en verrassing laten maken en dan navigeren in de app is een stap teveel

@Martin-White As far as I am aware it is a maximum of 2000 POI files across all categories.

Also ich habe die Gold und Next Version ohne Gerätelimit gekauft, da dies nun einseitig geändert wurde, ich aber immer mehr Geräte benötige, Planung am Tablet, 2 Handys (Privat und Firma) meine Freundin auch gerne damit fährt, würde ich die 5 benötigen, naja wenn sich das nicht ändert, werde ich die App verkaufen und mir etwas anders kaufen.

@Hubert-Thoring What makes you think I didn't...... Sometimes people forget or mis-interpret the instructions or text. That's why this forum exists, no?

Two days on the road, the app closed after a few seconds of being open and connected to CarPlay, at least three times. I then tried to put it Offline, but it did it again, in the same way... app version 5.2.0-473 with iOS

This is just an adapter to flexibly rotate the original BMW bracket by 90 ". The display is a sep. Topic. Which display can be horizontal and vertical and still compatible with the WW has to be clarified by someone else. A CP or AA display can also be operated with the glove finger not everyone needs the WW,

@Brian-McG @brian-mcg You're right. This has nothing directly to do with transferring files other than it being one of the pieces that ensure Zumos operate correctly as navigation devices. If that doesn't interest you, so be it. BTW, Garmin GPS routing algorithms have changed over the years, pre-Zumo you could take a Basecamp route calculation to the bank in that it would 100% match when recalculated in the Garmin GPS. That's no longer the case. I'm surprised you didn't know this given your "mult-multi years" Garmin experience. To the topic, this discussion has everything to do with: The HERE map not placing the road where it actually is. The MRA app recognizing the map discrepancy, but the Web Routeplanner not showing any overt alert. Sync should actually mean Sync. The MRA "Skip Waypoints automatically" enabled not working in this scenario. I was able to dynamically enable the XT3 to successfully recalculate at WP#7, so what's with the blanket "advice not to enable the recalculate function is decades old"? Nothing is absolute, yet you're hanging your hat on it. Odd. I'm trying to be transparent and reasonable, and I can say with complete honestly that the XT3 worked better than the MRA app in successfully routing the section from WP#7 to WP#8. If this had not been a verification test, and I was just routing with the XT3 (forgetting the app), I probably wouldn't have known there was a problem at all. I would have been on the straighter section on top of the mountain ridge before being able to look down at the route, and I wouldn't have seen that the XT3 handled the situation without any intervention. Again, thank you for helping me unravel what happened. We obviously don't agree on some things, but I appreciate the input you provided.

A route works... It doesn't matter if I put a point on the map on site, at the destination or select the existing POI there. At Kurvenreich comes the message shown. [image: 1783882936292-img_0284.png]

@cvlmtg said: I have to say I agree with Thomas. I love MRA route planner, it's the most powerful I have ever tried and works quite well, but I tried the navigation app once and I think I'll never use it again. You can say that to solve the first waypoint problem you can just move it to another place, but that's the problem! You always have to remember this or that workaround. You even have to tell the app that if you are calculating a route while you have no internet connection then yes, you want to calculate the route with no internet connection. It seems this app always require a lot of extra manual work just to do what other apps do by themselves. It doesn't matter that there are videos or tutorials explaining how the app work, because the problem is that you need all these videos and tutorials while other apps just work. Bulls eye !

@corjan-meijerink quick feedback and just wanted to say Wow. What a difference with stability compared to the previous build, which I used for a 10 day tour to Misano, Italy from the UK - had constant crashes on wireless CarPlay disconnect. The testing I have been doing has not had any crashes at all with this new build 480 and functions very well. I like the new search functions and they work well. Some of the vehicle type options could be changed slightly - toilets for motorcycle but there will always be a discussion for a future date. As an aside, when will the roadblock options and route type options be introduced into CarPlay? Top job. Thank you.

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

It's on the wishlist

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?

@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 !!!!!!!!!