MRA Community Forum

@gerrit-1c zijn meldingen van de kaartleverancier (Here) waar MRA niets aan kan doen.

@Carl-Lee said: Traffic and Closures, even though the info comes from the same place, are treated differently. You can configure Traffic to either auto-recalculate in which case your GPX1.2 route will probably be destroyed depending on your routing or prompted and then it's your own doing. My advice would be to treat traffic warnings with suspicion anyway. That's what I've been saying in my last few posts. The concept hasn't been sinking in. It's an XT Navigation Setting -- you either turn Auto on, or you handle it yourself. It's completely under rider control. For closures, I don't know. No personal experience for me. Actually, it's usually the opposite situation where a road is closed and the XT doesn't know about it. In any case, there definitely isn't a Navigation setting to deal with the situation. But if you've experienced automatic closure recalculation, I'll take your word for it. It doesn't make sense to me how it would do that real-time, but...... I'll have to try that out on a road that's closed and see what happens.

Hi Anonymouse! You hit the nail on the head. Having a "Depart at hh:mm" function instead of just a flat "pause duration" would be an incredible quality-of-life upgrade. When we are on a multi-day trip, the overnight hotel stop is exactly as you described: it doesn't really matter if we arrived at 17:00 or 18:30 the day before. What matters for the route timeline is that kickstands are up and we are rolling out exactly at 08:30 the next morning. A fixed departure time setting would solve that perfectly without breaking the continuous route calculation. Your point about the running total of driving hours is spot on, too. Even for those of us who prefer to manually pick our coffee spots and lunch breaks, having a clear metric showing pure saddle time between points—or a running daily total—would eliminate all the mental math. Whether the developers give us a full automated wizard or start with these highly practical UI tweaks like you suggested, it would be a massive win for all of us planning long-haul tours. Great ideas!

@Ioan-Dragulescu No, not at all. But I switched to the DMD Nor7e tablet a few months ago.

I would really appreciate this feature (subject to some of the detailed points others gave raised). Dropping a point off the road edge is the number one error route designers make. And it is very difficult to detect in the design process. When you take a group of 30 people out on the road, discover the error live, and have 29 people going in a circle because MRA is trying to get to that waypoint, that’s a pretty unpleasant situation!

Well that would be great. But I hope if AI integration is under discussion then the developers will open some conversations about what we want from AI. Or we could have a separate thread in this in the forum. I’d be glad to contribute what I have been using AI for so far. And I still think a lossless export/re-import would be straightforward to implement and very valuable in the interim and probably long term.

@Koen-Bergmans for more info: https://routes.lexwill.cyou/gps-routes-maken/#Garmin-Drive-app For other languages, hit the translation button

NN dyslectische vingers???

@Marco-Forte-0 Not in the current planner. However, it is a feature request for the planner that will replace the current website.

@Marinus-van-Deudekom That's what I figured. The MRA support person I was working with only had that patch being issued as a possible solution for my issues.

Thanks for your reply !

I agree that point 56 pretty close 42 is. And from certain point of view it is not that strange that MRA skipped to point 56. But.... 1. There was no reason recalculate. No roadworks, no deviation from my side. Me, the blue and white line were all still on the same road. 2. The issue is reproducable. This means something is wrong. But what? 3. When MRA is forced to recalculate (whatever the reason is). Why not recalculate to point 43. This is more obvious for the user.

Als de route in MRA niet op de HERE kaart gemaakt is, forceert MRA Navigatie de Route-als-track modus en deze kan je dan niet uitzetten. Daarnaast kan je de modus niet in- of uitschakelen als er een route actief is. Ook voor mij heeft "gewoon de route" de voorkeur boven route-als-track. Ik heb een paar keer Route-als-track geprobeerd maar liep tegen een aantal dingen aan, die lastig te herstellen waren onderweg.

Ik ben bij myroute app gold member van het eerste uur. Maar nu pas ook met de navigatie app. Voordien altijd met TomTom gereden, 2j.geleden mijn 550 verkocht en met de TomTom navigation expert gereden. Maar met de perikelen die ik heb de laatste dagen zou het zomaar de laatste keer kunnen zijn dat ik hem gebruikt heb. Ondertussen nog wat zoekende naar de beste instellingen met de mra app.

I also heard (viavia...) that MRA is working on its POI manager... so I just wait...

Anders dan bij een benzine of diesel krijg je met een electrisch voertuig tot op de kilometer nauwkeurig te zien wanneer hij stil gaat vallen. Dus als je de route en beetje fatsoenlijk hebt gemaakt, heb je rekening gehouden met de actieradius van je voertuig en op tijd en stekker gepland

Voor je eerste probleem kan je dit verhelpen door je offline navigatie aan te zetten en de offline kaarten die je nodig hebt te downloaden. Dan heb je daar geen lastmeer van als de verbinding weg valt.

Blackvieuw is een robuuste mobiele telefoon en samsung een gewone.

They are actually working on that for a next update. There are different items written on this forum for this problem.

@M.-Schrijver Thnx, die pak ik nog even mee.