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

Navigating a course - loses the course and directs to start

Former Member
Former Member
First the good news - I have the latest firmware and have found the route recalculation works well. Today I tested it by ignoring a left turn on my route. I took a different road so that I would join up with my planned route a mile further on. The 820 initially asked me to do a U turn but as I re-approached my original route, it realised and directed me back to join that route.

Now the bad news - I have a different problem. On two occasions in the past week, the 820 has briefly said 'Off Course' when I'm not off course. It has then very quickly said 'Proceed to XXX road' (where XXX is the name of a road from much earlier in the course). Even though I am continuing to follow the course, it will not recognise this and simply keeps saying 'Proceed to XXX road'.

I have tried stopping navigation and then re-selecting the course. However, it then still tries to direct me to XXX road and won't seem to recognise that I am actually on the course.

The map continues to move and I can actually see my course on the screen and continue to follow it visually. However, the navigation prompts don't come up and the 'distance to next' etc doesn't work.

Has anyone else experienced this and/ or have a solution?

The first time was 15 miles into a 100 mile sportive - which was particularly annoying.

Thanks

Dave
  • The same file is used to load the course and the data for VP.

    You are correct that from a pure navigational perspective time stamps are not needed, but as the same file is used to provide VP support as well the Edge may place an additional requirement on the input data.

    This topic has come up before on some other units and there a time stamp was needed.

    I would need to run some tests.

    Do we have an example of a GPX file that would not load?
  • I did some testing and the Edge will correctly process GPX files without any time stamps. As part of the processing the Edge adds its own time stamps to each record for use by the VP.

    I would need to see the GPX file that was causing the problem in order to understand this issue.
  • I am pleased Masters and Gurus are again involved to this major and basic problems for a device called GPS.
    After BRIANTJUK tell me about TimeStamps and activities files, I ride again 3 trips without any problems on routes I load like this:
    I draw with RWGPS, save like a trip (check on the save window), export to the mac and load true JaVaWaRTWtool (there is a check "use track timestamps") on the 820
    I give it for what it's worth, but my 3 last rides where ok. Because of this? I don't know...
    Anyway there is still that other issue: start or restart in the middle of a route (for EX. on km 30 from a route with 60 km total) TBT never works, Km to end is right and after a while (mostly 6/7 km) then total km (60).
  • I am pleased Masters and Gurus are again involved to this major and basic problems for a device called GPS.
    After BRIANTJUK tell me about TimeStamps and activities files, I ride again 3 trips without any problems on routes I load like this:
    I draw with RWGPS, save like a trip (check on the save window), export to the mac and load true JaVaWaRTWtool (there is a check "use track timestamps") on the 820
    I give it for what it's worth, but my 3 last rides where ok. Because of this? I don't know...
    Anyway there is still that other issue: start or restart in the middle of a route (for EX. on km 30 from a route with 60 km total) TBT never works, Km to end is right and after a while (mostly 6/7 km) then total km (60).


    Nope, don't work !!!! Again only 15 m out of track and ...
    Yesterday the thing happened on km 52 from a route 78,9 Km long.
    I have the impression that the problem always becomes after about 40 km before I can do huge detour, as big as I want and when I am back on the right way the 820 works again correctly with Turn by Turn, distance etc.. after 40 km, just some meters and it is blowing up ...
    Just thinking... somewhere a memory problem????
  • I give it for what it's worth, but my 3 last rides where ok. Because of this? I don't know...


    Are you using the virtual partner?

    Are you exporting the route from ridewithgps as a tcx or gpx track file?

    The gpx track file exported as a "route" from ridewithgps doesn't include timestamps. The tcx files include trackpoints but they are generated using some arbitrary speed, which makes using the virtual partner pointless.

    Many, many people use these the gpx track files with no issues on various Edge units. Even though the 820 is sort of new, there should be many reports of these files not working.

    The timestamps are not used in navigation. They are required for the virtual partner.

    Issues with navigation are not uncommon with all of the units (more on some models than others). Those issues are seen even with tcx filles, which do have timestamps.
  • I did some testing and the Edge will correctly process GPX files without any time stamps.

    This is the expected result.

    Ridewithgps doesn't and timestamps to there gpx track files and it's a popular site. If the lack of timestamps was a problem with the units generally, it would have been fixed years ago. It's possible that the 820 works differently but not likely. People also have navigation issues with tcx files , which have timestamps.

    As part of the processing the Edge adds its own time stamps to each record for use by the VP.

    I wonder where it gets the speed from. I wonder if the other units do this.
  • Are you using the virtual partner?

    Are you exporting the route from ridewithgps as a tcx or gpx track file?

    The gpx track file exported as a "route" from ridewithgps doesn't include timestamps. The tcx files include trackpoints but they are generated using some arbitrary speed, which makes using the virtual partner pointless.

    Many, many people use these the gpx track files with no issues on various Edge units. Even though the 820 is sort of new, there should be many reports of these files not working.

    The timestamps are not used in navigation. They are required for the virtual partner.

    Issues with navigation are not uncommon with all of the units (more on some models than others). Those issues are seen even with tcx filles, which do have timestamps.


    Thank you for this replay,

    In fact I do not want that virtual partner at all, I put (do not know if this helps) the speed of VP at 0 (zero) and I unable the datascreen, I suppose that there are no other ways to disable it (?) but on the other side I see several time and in this configuration the unit recalculate Virtual partner (!?)

    I swear to you that I try every GPX, TCX with or without timestamps draw and load from a lot of sites, after I load true the site (like for example RouteYou) true LoadMyTracks or JaVaWa, or simply copy/past into NewFile
    Yesterday like I explain higer in this Post I use a GPX track from RWGPS that I load on the unit true JaVaWaRTWtool
    Honestly I got 3 Edge 800, one was stolen, I broke one by accident and I still have one here, I can not remember that I have once this kind of problem with one of them
  • It's somewhat hard to follow what you are doing.

    It sounds like you are having navigation problems with or without timestamps.

    I don't think your problems have anything to do with timestamps or the virtual partner.

    Do you have "automatic recalculation" enabled?

    (I'm assuming you are using a unit that has detailed maps for your region.)

    Trying to "do things" to files from popular websites (like ridewithgps) is not likely to help you.
  • It's somewhat hard to follow what you are doing.

    It sounds like you are having navigation problems with or without timestamps.

    I don't think your problems have anything to do with timestamps or the virtual partner.

    Do you have "automatic recalculation" enabled?

    (I'm assuming you are using a unit that has detailed maps for your region.)

    Trying to "do things" to files from popular websites (like ridewithgps) is not likely to help you.


    No, recalculation is disable since my first 800, I read that on different sites and forum (BTW it is write now on the RWGPS help site specifically for the 820), anyway if I remember well I also tried with calcul enable (now, for my tomorrow ride I put it on and I will tell the result)
    About the Maps, I have: the last updated Garmin Cycle Map EU 2016.20, Topo Belux PRO (Buy from Garmin site) the last OSM generic routable new and Benelux Cyclemap (buy from Garmin) with of course only one that works at the time, never together (however I use to enable on the 800 both Garmin Cycle Map EU and Topo Belux and it also works perfect with a beautiful looking screen), and I have the issue with all the maps
    I also remind you that sometimes TbT works perfectly, like the 5 rides after update to 6.2
  • About the Maps, I have: the last updated Garmin Cycle Map EU 2016.20, Topo Belux PRO (Buy from Garmin site) the last OSM generic routable new and Benelux Cyclemap (buy from Garmin) with of course only one that works at the time, never together (however I use to enable on the 800 both Garmin Cycle Map EU and Topo Belux and it also works perfect with a beautiful looking screen), and I have the issue with all the maps


    The device can only use one overlapping map at a time. It might not cause a problem having more than one overlapping map enabled but the device is still using only one of the maps. The problem is that you might not know which map it ends up using.

    There can be navigation issues with maps. Ideally, you want to use the same maps for planning that are on the device. All of the web route planners allow you to use OSM maps.

    The "OSM generic routable" map might not include cycleways.

    The "Garmin Cycle Map" is based on OSM data. It appears to be the same as the "openfiets" maps based on OSM data.

    I also remind you that sometimes TbT works perfectly, like the 5 rides after update to 6.2

    I'm suspecting your earlier problems were due to a software bug. Maybe (hopefully), it was fixed with the 6.2 firmware version.

    It's frustrating when it doesn't work but there usually isn't anything you can do about it.