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

7.20 appears to break Turn Guidance

The secondary route for Turn Guidance was calculated and you can see the list of turns and the magenta line but nothing happens beyond that.

It seems to think that you aren't moving.

The track following works.

Another rider with a 1030 on 6.30 didn't have the problem using the same route.

The route didn't quite begin where we started. I tried restarting the route many times and it had the same problem (the Turn Guidance part didn't think I was moving). The ancient 800 was able to pick up routes in the middle reliably. The Touring had similar problem starting routes in the middle (it thought you were at the start).

Top Replies

All Replies

  • chrabu - Are you using a third party map or the Garmin Cycle Map?


    Matthew
    What is your supposition?

    I had one problem with TBT a week ago but I did not reply as I did not had any clue why it did not work.
    Route was imported from Strava IQ app and navigate the saved FIT
  • chrabu - Are you using a third party map or the Garmin Cycle Map?


    I have Garmin Cycle Map, but they are disabled. I used third party map (UMP-topo http://ump.waw.pl/).
  • krazyeone - We have seen a correlation with using supplemental maps with the Turn By Turn not working correctly. chrabu thanks for your feedback and I will add this to our case that we are using to research this problem.
  • krazyeone - We have seen a correlation with using supplemental maps with the Turn By Turn not working correctly. chrabu thanks for your feedback and I will add this to our case that we are using to research this problem.


    I have a theory but I cannot test it because I don't have yet 7.30 in GC
    When I have multiple maps on 1030 , yet on activity profile you have only one map enabled , the rest disabled , if you update the firmware then you will have all maps Enabled by default , maybe that was my case also
  • krazyeone - We have seen a correlation with using supplemental maps with the Turn By Turn not working correctly. chrabu thanks for your feedback and I will add this to our case that we are using to research this problem.


    I am glad this issue is getting a direction. I want to emphasize the importance if it being expedited. TBT guidance is a core feature. The use of 3rd party maps is also a core feature of the Edge ecosystem. There are tons of users doing it. Either they travel and the basemap they have does not cover the visited area, or they need a speacialty map that provides more details than the basemap, for example for gravel riding and mountain biking. In every case supporting 3rd party maps is essential. Most 3rd party maps are OSM based and produce using a program called mkgmap. They are more detailed and also updated much faster than the Garmin basemap. Please do not let that issue fall on the backburner because it pertains to non-Garmin maps. We need this. Thank you.
  • Just for the record I just made my Edge compute a TBT route after updating to FW 7.30 and it is still broken. Not that I expected it to be fixed since this issue was not part of the release, but just want to post that bit of information. TBT with 3rd party maps (openfiestmap based in my case) is not working with FW 7.30.
  • Martin868 - Do you experience the same problem on roads that exist on the third party map and the Garmin Cycle Map? Or is this only happening on roads that are only available with the third party map?
  • Just for the record I just made my Edge compute a TBT route after updating to FW 7.30 and it is still broken. Not that I expected it to be fixed since this issue was not part of the release, but just want to post that bit of information. TBT with 3rd party maps (openfiestmap based in my case) is not working with FW 7.30.


    My Edge is on v7.30, I use OpenFietsMap maps, and TBT works fine. I have ridden multiple routes since 7.30 and had no problem whatsoever. Did you do a reset?
  • Martin868 - Do you experience the same problem on roads that exist on the third party map and the Garmin Cycle Map? Or is this only happening on roads that are only available with the third party map?


    I experience the issue even with routes that only follow roads that are also on the Garmin cycling map. I wonder if a device reset may help, but this is a lot of pain since I have a complex configuration with lots of Activity Profiles, some 15 sensors, custom settings, etc.
  • My Edge is on v7.30, I use OpenFietsMap maps, and TBT works fine. I have ridden multiple routes since 7.30 and had no problem whatsoever. Did you do a reset?


    I haven't done a reset. My setup is complex with many activity profiles that were tuned do different uses, some 15 sensors configured, and lots of customized settings. Doing a reset mean redoing all this and it is many hours and major pain. However I use my unit is now experiencing the Halo issue (and it is already a replacement unit itself) so I may have to go through that process anyway if I have it replaced. Now since you ask, do you expect a reset to fix this TBT issue ? Why ?