Related
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

Upgraded to V 12, route calculation stops at 39% and crashes device

pertti_s
over 4 years ago

Updated 1030 to v12, and after that I am not able to "ride" any routes.

I have enabled only standard garmin map, also tested with custom OSM map.

Routes were created either RWGPS (IQ app for sync) or Strava.

Every route will fail at 39% calculation and also crashes whole 1030 so it needs be started again.

  • 0 over 4 years ago in reply to pertti_s

    I copied to my routes, now the route is downloadable via CIQ (as a copy) and loads to Edge.
    I have "popularity" turned on, similarly avoiding everything including ferries (route for a road bike) the course is recalculated correctly.

  • 0 over 4 years ago in reply to Prozorowicz

    You dont get any warnings about course points, "last 10 is ignored" when starting the ride at garmin?

    I have:

    Map : Garmin cycle map EU, north east 2021.10

    Popularity routing : On

    Routing mode : road cycling

    Calc method: minimize distance

    Lock on road: off

    Recalcalculation : off

    Avoidance: nothing selected

  • 0 over 4 years ago in reply to hotdogpartysausage

    Spot on, if I turn off this popularity routing course will calculate.

    Strange, as previous firmaware version all worked fine with these same routes wich now with v 12 will fail at 39% and crashes whole device even I had this  popularity routing enabled

  • 0 over 4 years ago in reply to hotdogpartysausage

    I was happy too soon, only one of those failing routes worked. but that is good progress still.

    I have been using VeloMap OSM maps and if using those garmin will crash soone than 39% calculation point

  • 0 over 4 years ago in reply to pertti_s

    Your course is working correctly on Garmin maps. Perhaps the maps you are using are causing problems in the new FW.

    After work, I will check the operation with Velomap OSM, but most likely it will be the same problem as yours. Already in beta there were reported problems with user maps, it was supposed to be fixed, but as you can see not fully and not with all maps (my user maps work properly, but I don't use Velomap).

  • 0 over 4 years ago in reply to Prozorowicz

    Maps used are "default" latest Garmin provided maps, I even did reinstall of maps with garmin express.

    Thanks for investigating this and using your time!

  • 0 over 4 years ago

    I also got the same issue on any 3rd party app, it seems to work fine on original Garmin apps.
    It does not matter if I switch popularity routing on / off, or avoid ferries or not, always crashes at or around 39%.

    Now, of course it is easy to say (as people did here) that "it is your maps causing these problems"; but all these maps are freshly downloaded OpenStreetMap-based maps (and not some weird obscure things), and they did work with previous firmware versions.
    So, yes, the problem has something to do with the maps, but this should still be fixed as these maps should be working fine nonetheless.  

  • 0 over 4 years ago in reply to vortex255

    ...3rd party MAP, not app...

    vortex255 said:
    I also got the same issue on any 3rd party app
  • 0 over 4 years ago in reply to Prozorowicz

    Do you have any IQ datafields installed, as I have 10 allowed installed (mostly Xert iq fields)? Just thinking if this is memory issue, garmin runs out of memory during calculations.

    Need to create new profile where is no IQ data fileds and check if that makes any difference. 

  • 0 over 4 years ago in reply to pertti_s

    Yes, I do use CIQ and I also believe that there is some weird interaction with CIQ data fields using memory also the route calculation wants to use. 
    So, I created a vanilla profile without any CIQ data fields, and indeed it works.

    But...honestly, I rather do not have turn-by-turn navigation than not have the CIQ fields :-)
    I guess the main difference between Garmin maps and many 3rd party maps is that they are more detailed (and thus bigger) - but still, there seems to be an issue with the firmware (and likely with how it handles memory.)