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

Edge 130 random reboots in firmware 3.40

Since firmware 3.40 I have a lot of random reboots.

It seems like it’s only happening when it’s connected to an ant+ speed sensor an especially when I’m not close to my bike. (When the connection is less stable?)

It happens almost every time when I finish a ride and sometimes during a ride.

Firmware 3.30 didn’t seem to have this problem and a factory reset also didn’t help.

Can this be solved in a newer firmware?

  • Is there anything that can be done about this problem?

    So far I narrowed it down that only happens when I’m at a certain distance of the ant+ speed sensor. It happens at a distance when the garmin switches between connected and not connected with the sensor. At some point in the next few minutes, it will just reboot.

    Also tried two different sensors, which doesn’t make a difference.

    Are there any other people who have this problem?

  • Also, I never have a reboot when there aren’t any sensors connected.

  • Don't understand what you are saying.
    You move away from your speedsensor ?
    The Edge is on your bike, and so is your speedsensor. How can you moving away from your speedsensor make any difference ?
    And even if you take the Edge with you, the bike would be standing still and therefore the speedsensor is not sending a signal.

    Could it be you and your HR sensor moving away from the Edge ?

  • After a ride at home, or at a coffee stop, I take the garmin off my bike. The garmin is than between 5 till 10 meters away from the speed sensor.

    But the reboots sometimes also happen during a ride when there’s interference

  • I am using the 130 for about a year now and I have seen maybe 3 reboots during that time in different FWs, so far I have not seen a reboot using FW3.40 and I am using ANT+ cadence and speed sensors.

  • I just read that this is also a problem with cadence sensor. 

    Both speed and cadence sensors stop transmitting when there is no movement, so the part where the gps moves away from the sensor does not make sense. Once the bike is stopped, there is no transmission anyway. The only sensor still transmitting is your HR sensor, and by taking the gps with you, they stay whitin range. 

  • When there’s no movement, the speed sensor is still transmitting for a few minutes. After that it switches off.

    As long as the ant+ speed sensor is still on, and the connection with the edge 130 isn’t very stable/strong, it reboots at some point.

    I can replicate the the problem everytime when there’s around 10 meters distance between speed sensor and edge 130, just within the distance before it completely loses the connection with the sensor (just before the speed sensor icon on the garmin starts to blink).

    For now I switched to a bluetooth connection with the speed sensor instead of ant+ and this solved the reboots completely. It never happened again. Whenever I switch back to ant+, the problem is back.

    So I’m really sure it has to do with the ant+ connection with the speed sensor.

    I don’t have cadence so I can’t test this as well. My ant+ heart rate monitor doesn’t seem to give problems

  • If any of you have an ERR_LOG.TXT file in the Garmin\Debug folder could you post it?

    I would be interested in taking a look.

  • Hi,

    I just replicated the problem with the speed sensor twice to create an error report. I managed to replicate the reboots in the way I described in an earlier post.

    Thanx for looking into it. I'll hope it can be fixed in the next firmware.

    Here's my err_log.txt:


    2909 (Edge 130) SW ver: 340
    Build Type: RELEASE
    Commit:36086edac6d739a02890011940bdc4776a5fb7e7
    ESN: 3972249641
    07/30/19 16:58:16
    RTL
    errnum: 0x00a
    r0: 0x20006288
    r1: 0x000000c8
    r2: 0x0000003e
    r3: 0x0000003f
    r4: 0x0454fa55
    Stack frame PC, SP: 0x0009eab5, 0x200060c0
    Call Stack - SP at 0x200060c0:
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    Uptime: 267560

    2909 (Edge 130) SW ver: 340
    Build Type: RELEASE
    Commit:36086edac6d739a02890011940bdc4776a5fb7e7
    ESN: 3972249641
    07/30/19 17:01:53
    RTL
    errnum: 0x00a
    r0: 0x20006288
    r1: 0x000000d5
    r2: 0x0000003e
    r3: 0x0000003f
    r4: 0x0454fa55
    Stack frame PC, SP: 0x0009eab5, 0x200060e8
    Call Stack - SP at 0x200060e8:
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    Uptime: 198581