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

Distance/turn limits when using turn notification navigation?

Hello,

I recently imported a 110km route with Garmin Connect to use on my watch, and I enabled the turn notifications (they are very handy). Off I go and everything works fine, but sadly with about 40km to go the turn navigation stopped. There were no clues anymore to the next turn/point just one distance to the finish. I could still navigate by looking at the map and following the track, but it's especially for a long trail run very convenient to have the active turn notifications to limit navigation burden and mistakes.

- Why did I not get turn notifications for the last part of my course?
- If there is some kind of a limit on the number of turns, why is it so low?- If there is some kind of a limit on the number of turns, why did Garmin connect not warn me and suggest to split the route into multiple parts?

- How can I avoid similar issues in the future? I like to use one route/track if possible, to know the total distance remaining for trips like this.

  • Every turn notification you get is a so called course point.

    The maximum number of course points on my previous watch, a forerunner 935, was ridiculous low with 50 and I was hoping garmin had increased this.

    But so far I only found this info: https://support.garmin.com/en-US/?faq=aisqGZTLwH5LvbExSdO6L6

    This indicated that bike computers have a limit of 200 and all watches have a limit of 50. 

    This is so stupid. 50 is way too low and you run into trouble with a simple long run or anything close to a decent bike ride. 

    Like I said before, my new 965 is a replacement for my 935 but nowhere near an upgrade. In 6 years time garmin added a lot of bs to their watches and few useful things.

  • That is really annoying indeed. I don't see why it's such a low and artificial limit. I'd have thought that even the limited hardware of a watch would not have any issues with multiples of those limits.

  • I can only think of 2 reasons

    1. gamin wants to buy more garmin devices and forces you into a bike computer. (Although any half decent long runs also suffers from this limit. 

    2. Garmin doesn’t give a damn about usefulness of features. Only the quantity of features is important, not the quality  

    Personally, I think 2. 

  • 3. Garmin made some poor choices many years ago when 50 way-points sounded like more than enough, and wrote their code in a way that makes it hard to extend (e.g. by baking the 50 limit into the fit-file specification, which makes it *very* hard to change as so many people/tools/websites rely on being able to parse these).

    But I agree that 50 is too low and I agree that this is a tech debt that they must address asap, even if it is hard.

  • Possible but unlikely, since the edge bike computers have a limit of 200.

    There once might be a valid reason to limit it, probably  memory, but that isn’t valid anymore. Garmin just couldn’t be bothered changing this hard coded limit. 

  • I was not even cycling, just an ultra-run which I feel does fit in the target audience of this watch.

    I'll have to learn to live with the limit for now, too bad. They really should get rid of silly artificial limits like that, that especially with newer hardware, do not make any sense anymore.

  • If they could at least increase the limit to 200 on the FR (so it's in line with the bike computers) it will make it a limit that won't be as easily reached on a run (but it still seems low for a more technical bike ride). Sounds that should not be impossible in software/hardware...