Edge 130 Plus restart during course activity with custom course points

rus89
11 months ago

Hello,

as the title says, I have an issue with the Edge 130 Plus restarting during course activity on which I added custom course points (i.e Energy Gel).
This is very annoying since I'm using custom course points as a big helpers during my XCM races, and it's very important to me to work as expected.
It takes about 10-20s to restart, to connect all sensors again and waiting for me to press play again to continue where it stops.
This is very easy to reproduce.
Just make a custom course (or edit existing one) in Garmin Connect and add at least 1 custom course point.
Regarding notification settings, everything is set correctly as it is described here for the iOS, since this is my 3rd Garmin device for the last 10 years.
Regarding sensors that are attached to Edge are Garmin Rally XC100 powermeter pedals, speed sensor, and Garmin HR strap.

Has anyone else experienced this, or does anyone have any suggestions on how to resolve this issue?

Thanks in advance.

EDIT: Workaround is to use General Point type of custom points!!!
EDIT 2: I reached out to them over support, and they confirmed that the Edge 130 has been discontinued and won’t receive any further software updates. Unfortunately, this means the issue won’t be officially fixed.
  • 0 2 months ago in reply to 4291694

    Have the same and up until today I stick to the following assumption on when it happens:

    • record an activity with garmin device
    • sync with garmin connect and have the activity in Komoot
    • create a new route in komoot based an that activity
    • while sticking to original route
    • save in komoot
    • let garmin connect sync and send to garmin device
    • ride that route with garmin device

    Then the *** happens, garmin looses track, sometimes on a roundabout, sometimes ….

    I think garmin gps gets *** up while facing several route waypoints close togheter ( due to import with stick to original route).

  • 0 2 months ago in reply to 9320854

    It happened to me again,but I had some that doesn’t do that thing on turnarounds,it’s so stupid ,some courses it works perfectly,others a nightmare when coming near a turnaround ,it is ridiculous what is happening,and not even a single answer from garmin ?

  • 0 27 days ago

    Hey all,

    I think the issue with both course points and roundabouts has to do with
    how courses are formatted, as .fit files.  

    I typically make courses on the Garmin Connect website and upload them to
    my Edge 130Plus wirelessly using the android app.  Either (or both) the website
    or the app perform some reencoding of the .fit file before it is uploaded to the device,
    and at some point in 2024 the way they started encoding roundabouts changed
    to some encoding that causes the device to crash.  If a course point is causing a
    crash, it is presumably also encoded in a way that the Edge 130Plus just doesn't understand.  

    A firmware update isn't the only solution here, although it would be ideal.  Garmin could
    instead update Garmin Connect so it uploads to the Edge 130Plus with a
    compatible .fit encoding for roundabouts and course points.  

    As neither of those solutions are guaranteed,the workaround is to make courses
    on other websites and upload them using USB     (put .fit file in "newFiles" folder). 
    I'm not sure if Garmin is the only one using this crash-inducing encoding, but I've
    used courses from other websites and even the navigation and course points work.  

  • 0 25 days ago in reply to 4826923

    It is exactly as you describe it. If you compare FIT files generated with old and new versions of the connect SW, then you will see that the new ones have course points added with types in the 70..75 range. Looks like the 130plus can not interprete those and crashes

    10:44:50 AM 12 47.641203 -3.155271 9,350.10 right
    10:52:25 AM 13 47.644385 -3.192893 12,515.15 70
    10:52:25 AM 14 47.644385 -3.192893 12,515.15 77
    10:52:52 AM 15 47.645860 -3.193712 12,698.80 left
  • 0 22 days ago in reply to hardwerker

    So nothing could be done?is that it ?,no garmin technician could resolve this ?what a joke

  • 0 22 days ago in reply to 4291694

    More like no Garmin tech *will* solve this. 

    Anyway, I noticed that if I create a course on Garmin Connect and set the type to Road, roundabouts seem to have fewer/no issues. The same course saved as Gravel has issues. 

  • 0 21 days ago in reply to 4291694

    I filed this issue under the product warranty, and after three videos and three weeks of emails with Garmin, they replaced my Edge 130+ with an Edge 530.

    I'm mentioning this for those who are still under warranty.

  • 0 21 days ago in reply to OscarOML

    Ok, not a bad idea, but a terrible solution, I’m gonna check it out, cause my brother has the same device and subconsciously the same problem, but what a joke from a company that want to be at the EDGE 

  • 0 13 days ago in reply to OscarOML

    What a terrible "solution". This problem is not a device issue. It could be solved either in the Connect SW (generate .fit files without messages 70..79) or in the device firmware (interpret the roundabout messages correctly).
    As an engineer I do not understand that Garmin offers a device replacement as solution.