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

Lost Turn by Turn. Incorrect Distance to go Navigating a course

Lost Turn by Turn. Incorrect distance to go. Navigating a course.
Garmin
When following a track (TCX or GPX) I quite often get a problem where the 820.
a) Stops providing Turn by Turn.
b) Gives an apparently random distance to go (to complete the course). Often longer than the course.
c) stoping and restarting the course has been known to fix it on rare occasions. But usually the turn by turn is wrong (some random next turn either near the beginning or the end). The distance to go may correct temporarily after a restart but will at sone point become incorrect.

Usually my routes are between 50 & 100 miles. The end is usually near the start (within 500yds). They sometimes cross themselves.

The garmin going wrong is usually triggered by either going off course or by being turned off or going in to sleep mode when I stop for coffee.

If I ride the same route twice it won't necessarily fail in the same place.

This is a real problem when I'm in a strange area.
Nick
PS - a friend has the same problem on his edge 1000
  • Former Member
    0 Former Member over 8 years ago
    Lost Turn by Turn. Incorrect distance to go. Navigating a course.
    Garmin
    When following a track (TCX or GPX) I quite often get a problem where the 820.
    a) Stops providing Turn by Turn.
    b) Gives an apparently random distance to go (to complete the course). Often longer than the course.
    c) stoping and restarting the course has been known to fix it on rare occasions. But usually the turn by turn is wrong (some random next turn either near the beginning or the end). The distance to go may correct temporarily after a restart but will at sone point become incorrect.

    Usually my routes are between 50 & 100 miles. The end is usually near the start (within 500yds). They sometimes cross themselves.

    The garmin going wrong is usually triggered by either going off course or by being turned off or going in to sleep mode when I stop for coffee.

    If I ride the same route twice it won't necessarily fail in the same place.

    This is a real problem when I'm in a strange area.
    Nick
    PS - a friend has the same problem on his edge 1000


    Well known problem, you can find many posts and threads about it on this forum.

    Garmin has never acknowledged it. If you contact customer support they'll claim it's the first time they've heard about it and ask you to reset your device. This will not solve the issue.

    Chances of Garmin ever fixing the issue are slim. The device has been out for about ten months and so far they failed to fix any of the major issues. They don't even seem to be trying.

    The only solution to the problem is to get rid of the 820 and to buy a Wahoo Elemnt Bolt :-)
  • Well known problem, you can find many posts and threads about it on this forum.

    Garmin has never acknowledged it. If you contact customer support they'll claim it's the first time they've heard about it and ask you to reset your device. This will not solve the issue.

    Chances of Garmin ever fixing the issue are slim. The device has been out for about ten months and so far they failed to fix any of the major issues. They don't even seem to be trying.

    The only solution to the problem is to get rid of the 820 and to buy a Wahoo Elemnt Bolt :-)


    Well Unprincipled,
    I think that is very disappointing. I'll call Garmin when I get back to the UK. Assuming I don't get lost.
    Nick
  • @nickdodo -- your initial post could have been written by myself, almost verbatim, with respect to my 820. I'm sorry to hear about your friend's experience with the 1000, which I just ordered (the Explorer version) in the hope it would be better/more consistent. But I'll still try it out with fingers crossed that it will be better....
  • @nickdodo -- your initial post could have been written by myself, almost verbatim, with respect to my 820. I'm sorry to hear about your friend's experience with the 1000, which I just ordered (the Explorer version) in the hope it would be better/more consistent. But I'll still try it out with fingers crossed that it will be better....


    Rogerinnyc,
    I wish you the best of luck with your edge 1000. Unfortunately I think it will behave the same as the 820.
    My friend's 1000 exhibited the same behaviour as mine all week.
    Nick

    PS
    I'll be phoning Garmin later.
    Nick
  • If you have this issue then report it to Garmin.

    I reported this to Garmin on their chatline. After some chat here is a summary of the essential point.

    Garmin:It would appear that we are currently investigating this issue. I have added to the Case 1329838. You will be notified as soon as possible with a resolution.
    Is there anything else I can help you with?

    Me: Ok - So its a known issue and not just me and my friend.
    Garmin: We haven't received a lot of reports, but we have received enough to request for the US to look in to it for us. You will be updated via email.


    If you have this issue then report it to Garmin. Don't just moan about it here. The more it is reported the more effort will be put into fixing it.
    Nick
  • Former Member
    0 Former Member over 8 years ago
    I contacted Garmin Support via the chat to add my +1 to this issue. I will say that Thomas (the Garmin rep) was great to converse with and he collected as much detail as I could provide him.
    I referenced Case 1329838 which is actually a UK based case. My problem occurred on a course that was created entirely in Garmin Connect (the original case noted the issue was with tcx / gcx files). Perhaps the more detail they get the easier it will be to diagnose and fix the bug.
  • I contacted Garmin Support via the chat to add my +1 to this issue. I will say that Thomas (the Garmin rep) was great to converse with and he collected as much detail as I could provide him.
    I referenced Case 1329838 which is actually a UK based case. My problem occurred on a course that was created entirely in Garmin Connect (the original case noted the issue was with tcx / gcx files). Perhaps the more detail they get the easier it will be to diagnose and fix the bug.


    👍
    Excellent. I have had problems with courses in the UK and Mallorca.
    Nick
  • Former Member
    0 Former Member over 8 years ago
    That's great, that's my case.

    Gives me confidence that they are taking it seriously. Recently I've had a lot more correspondence from Garmin and I did some test rides for them.

    Fingers crossed it won't take long now!
  • Gives me confidence that they are taking it seriously. Recently I've had a lot more correspondence from Garmin and I did some test rides for them. w!


    Excellent. Let's hope.
    Nick
  • Former Member
    0 Former Member over 8 years ago
    I have noticed something concerning turn by turn navigation. When I load a gpx track for navigation and wait for calculation (which always starts wether I choose navigate to start or not) end before I start to move, turn by turn navigation works. Tried it seven times the last two weeks. But when I start to move before calculation ends in 4 of 5 times turn by turn navigation gets lost. Another point is that the map must support the track for the chosen bike type. If for example the track contains parts the map does not "allow" for road bike and your activity type is road bike the navigation gets lost thus you are on this part of the track.