Rerouting on Edge 1040 (compared to Karoo)

Coming from an HH K2 (see https://forums.garmin.com/sports-fitness/cycling/f/edge-1040-series/381370/switched-from-k2-to-edge-1040-several-questions) I have now found that rerouting is far from effective on the 1040 compared to a K2. So, the K2 is way more flexible and will figure out a new way to get you to your destination, while the Edge just wants you to turn around to get back on route. Is there a way to change that? I’ve got rerouting for course and route set to automatic, but what’s the deal with course versus route on an Edge btw?

What I usually do is ride without a specific route loaded, and when I'm about halfway, I want to choose the option to navigate back to my target (taking the most direct way) to check my ETA and see if I can make a detour or not. But the route it comes up with is often not the most straight-up or ideal, so I end up going off track a lot or detour since I have time left. Instead of recalculating a new route, the Edge keeps insisting I make U-turns to get back to the original planned route. Only after deviation "too much" it seems to come up with a new route (which sometimes is even more direct...) How can I make this device behave better?

  • I think many want rerouting to take them back to their planned course, because they planned it and want to ride it.  That's how I am riding the bike.  Driving a car,  I haven't planned a specific route and simply want to get to a destination by the most expedient route, so rerouting to the destination is what I want. Way back when I had a Edge 705, it would always reroute to the destination, and I never wanted that.  Optimally, we would be able to choose the type of rerouting we wanted. 

  • The Edge will always try to route you back to the course you are riding. Depending on the possibilities this can lead to U-turns but it can also re-route you to join the course further ahead. You can influence how the re-routing behaves with the options under Course Recalculation (this can be found in settings of your profile, Navigations > Routing).

    For your use case of checking how long it takes to get back home, what you could do is stop the current course, then plan a route back to your starting point. You can then follow that route. When you deviate from that route the Edge will not try to get you back on the originally planned route but will calculate a new route based on your current location.

    So Course = pre-planned route that the Edge will try to follow, Route = ad-hoc planned route and the Edge will try to get you to your destination based on routing settings.

  • I understand that if you're on a route, that rerouting back to the route/course makes sense. However, I'm specifically routing to a destination (but this also holds for a POI). It doesn't matter if I move of track but still want the best route from my current position to the destination/POI. So it should work differently depending on your type of navigation?

  • Yes because in the Garmin world route navigation is not the same as course navigation.

    Course navigation is loading a pre-planned route and the device will try to keep you on the path of the course.

    Route navigation is where you select a destination on the device (can be a POI or a location or back-to-start) and the device will navigate you to that destination.

    It is explained further in this support article: support.garmin.com/.../

  • >>>It is explained further in this support article: support.garmin.com/.../<<<

    Hey.  That's a great link.  In 14 years of using Edge devices, I can't remember ever using one to route to a destination and have always ridden pre-planned courses, which I wanted to stick to.  It's good to know the difference in the unlikely event I'll use an Edge to navigate to a destination.

  • This is almost exactly like I use it indeed (except ti don't run a "Course" before selecting "back to start". While the "route" is calculated back to my start (or destination) I still feel the Edge is providing way too many u-turns instead of new routes though.

  • You could play around a bit with the routing settings and see if that improves the results. For example popularity routing sometimes leads to unexpected results where the Edge will take a route that is much longer than needed. Other than that I don't there's much you can do about the way the Edge will guide you.

  • garmin routing has taken a turn for the worse a while back. my edge 1000 consistently gives better routes than the 1040.

    some bug thst would make it do 120mi instead of 17 has been quietly fixed, but mamy settings are either inverted, or the algorythm do buggy that makes it look like it.

    many tests from A to B, for instance, trying shortest x fastest x least climb leads to shortest thst are not the shorter, and more elevation on the "lowest climb".

    popularity routing is often a joke, specially in longer routes, instead of taking better routes it will make you go up every side mountain where people train on weekends, instead of a more reasonable route.  leave it off - and good luck figuring if off is on or off.

    high traffic roads setting seems to have limited effect, and the unit will NOT route you through some roads no matter what, it seems.  shoukd be my choice if i want to ride 0.5mi on a legal narrow shoulder country road with traffic or take 10mi of lower traffic detour.

    it cannot be called a NAVIGATING gps at this point.

  • yeah I did so already but seems the options are limited and I have disabled popularity routing for that reason (unexpected results).

  • This entry in the beta forum seems promising:

    Change Log 25.18

    • Added remote media controls. Now you can configure your shifter buttons to control media playback.
    • Added new SRAM gear presets for 13 speed gravel groupsets.
    • Updated Shimano STEPS terminology to "Shimano E-bike".
    • Fixed layout of graphical data fields.
    • Fixed Back to Course calculation that requires a u-turn.

    Change Log 25.17

    • Fixed route recalculation errors after deviating from planned course.

    But perhaps is only relevant to course navigation and not route navigation (which is my use case)