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

Edge 530 bad navigation and appearance of course line on the screen

7808603
over 2 years ago

Yesterday I experienced very unpleasant problem with my Edge530. I prepared a course with Garmin Base Camp, loaded it to Edge and wanted to navigate. But I rode 100 m from the start and Edge displayed that I should go back to the start. I was riding in my direction and Edge was beeping and displaying its annoying message. So I stopped and decided to ride by course without annoying navigation. I stopped navigation in my Edge, loaded the course once again, set its color and the option "always visible" and selected the map. The whole course was displayed on the screen with arrows showing direction. The direction was as I planned. So why did Edge want me to return to the starting point? When I turned on recording the arrows disappeared. Why?

I rode all my course successfully, but now I am wondering how to prepare my next bicycle trips? Perhaps should I make my courses in Base Camp in 2 versions? Forward and reverse?

  • 0 over 2 years ago

    Similar thing happened to me this morning (and it wasn't the first time). After a turn and right at the beginning of a long straight section of road, it just began telling me to make a u-turn, while the course was clearly straight and seamlessly visible on the display. I ignored it and after a couple of km it stopped. Course was prepared with rwgps. Happens every now and then, just another small quirk to get used to.

  • 0 over 2 years ago in reply to ctulhu

    Did you have route recalculation on?

    Did you let the Edge navigate to the start?

    Either of these settings can give unpredictable results.

  • 0 over 2 years ago

    This has nothing particularly to do with BaseCamp. 

    It seems your route might have been an out-and-back along the same roads. These kinds of routes can have issues. Creating two routes (one outbound, one inbound) is not a bad idea. 

    Another thing to try is reloading the route and have it calculate while you are moving in the correct direction. 

    Note that, for loop routes, you want the start point closer than the end point to the place you load the route. 

  • 0 over 2 years ago in reply to dpawlyk

    Thanks, I will check it. When I plan bicycle trips I usually have the start and end point almost in one position. Or one about 10-20 m from the other. So I think the distance should be at least 100 m or more. When I/'m near home returning from a trip I know where to ride so I need not any navigation Slight smile Even in the night

  • 0 over 2 years ago in reply to 7808603

    Yes, it’s never really a problem having the points separate. The trick is to remember to always do it when creating the route. 

    It’s fairly common that the course is started not exactly at the first point in the course. 

    The idea is to have the first point be closer to whatever that point is than the last point in the course.

    The issue isn’t really having a gap between the first and last point. It’s the relation between these two points and the point where the course gets started.

  • 0 over 2 years ago in reply to dpawlyk

    And we have to remember that the course name should be specified so as Edge read it properly. The Windows file name need not to be the same. I prepared a few courses which were read as e.g. track025.

  • 0 over 2 years ago in reply to 7808603

    The name doesn’t affect navigation at all. 

    The files can contain multiple tracks. So, the name used has to be the track name.