This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

bug reporting: conflicting indications of direction

Former Member over 4 years ago

Hello all!

I thought version 6.20 was bug free but it's been 2 weekends in a row that, 2 or 3 times on a route that I had prepared on Connect and that I was following, the direction indication in the upper left corner is in contradiction with the route.

The strangest thing is that sometimes it is the direction on the map that is correctly drawn on the screen, but sometimes it is the direction in the top left corner that is correct!

I talked about this problem on the "Garmin Edge 530 User Group" community on Facebook and I'm not the only one to suffer this inconvenience

Top Replies

Wongataa over 4 years ago in reply to Former Member +1

You don't have to switch to the MTB profile to allow gravel trails. Go in to the navigation settings for the road profile and modify adjust the avoidance setup.

All Replies

0 Former Member over 4 years ago in reply to Wongataa

ok. And how do you prevent the unit to recalculate? If I have to leave the planned route for one reason or another, I would like to be guided around the area that I can't go BUT I would like to be put back on the planned route as quickly as possible.
Is this not possible?

Maybe I do not use the route following feature correctly..;

0 Wongataa over 4 years ago in reply to Former Member

Profile settings -> Navigation -> Routing -> Recalculation to change the recalculation settings on the 830. I would assume the 530 is similar. It should be in the manual.

If you want to be guided around a detour and back along your route you need to get a 1030 plus. Those capabilities are available in that unit. No other Garmin unit with navigation can do that.

0 Former Member over 4 years ago in reply to Wongataa

OK. Thank you very much for your time ;-)

0 8029610 over 4 years ago in reply to Wongataa

Never was aware of this (the recalc makes a new route to the endpoint), this explains a lot frustration, because indeed this could be easy the way back a long the "original" route... wil test it again with recalc disabled, thx!