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

Problem with the loading cable

I received my 5x yesterday. Unfortunately I have problems with the loading cable. The connection to the PC is not stable and need to bend the cable slightly at the connector to the watch. Has anyone have similar problems?
Garmin Support will send a new cable and i hope it solves the problem and there is no defect at the connector of the watch.
By the way I am not very happy with the new design of the connector as dirt will get in there quite easy. A plastic cap would be nice to cover it.
All the best
wolf
  • Same problem for me

    Same issue for me on my 5x. If I touch or move the watch at all while connected it immediately disconnects and then sometimes reconnects. I have isolated the USB end so the problem occurs at the watch connection. Very frustrating and scary to think it could crash or disconnect while updating. I will report to Garmin today and link them to this thread.
  • After contacting Garmin support, they shipped me a new cable but the same exact problem with being sensitive to any movement still exists. They provided a return shipping label and wanted me to send back my original cable so that they can "have a few of the cables that are experiencing this issue in the warehouse for testing".. so seems like they're halfway admitting there might be an issue.
  • bg, are you on the beta 2.96?
  • bg, are you on the beta 2.96?


    Beta 2.95. Just about to plug in and update to 2.96, will report back with any change
  • The reason I ask is I just tried mine on my work PC and with the 2.96 I no longer get the disconnects, when I get home I will verify it there as well.
  • The reason I ask is I just tried mine on my work PC and with the 2.96 I no longer get the disconnects, when I get home I will verify it there as well.


    **Update:
    On Beta 2.96 I am no longer able to reproduce any disconnects from my MacBook. Longer term tests will tell the story but I was pretty rigorous with it and never once could get it to eject like usual. It hardly took a mouse-fart before to get it to eject so initial results are promising... I'll update after some time
  • Former Member
    0 Former Member over 8 years ago
    This is bizarre.

    Having read the success of others in updating to V2.96 I carefully attached the watch to the computer, making sure nothing touched it etc and updated to v2.96.

    Unfortunately this has made no difference to me. If I have the watch face down on my desk, with it orientated so that the socket is in line with the natural lie of the cable so there is no tension, and do not move anything in the slightest I get a connection. The slightest movement and the connection goes.

    So, unfortunately for me, v2.96 has made no difference at all to the connection issue.
  • No change with V2.96

    Same for me. I thought V2.96 solved this issue, but today any movement at all and it loses connection. So no better with V2.96 for me. I am in contact with Garmin now on the issue. Hopefully something can be done without a redesign.
  • Road hickory

    Mine did the exact same thing. I'm not worried about it anymore, as I returned it and got the 935 instead, which does not display this problem for me.
  • Is the USB signal interrupted during transmission? If the initial measurement system or gyro system is incorrectly closed during the USB transfer, could it give these symptoms?

    I have no F5X and just follow the debate.

    Can be tested with a very good electrical USB connection, which should not be able to fail. If the USB connection fails when the clock is moving, it may be due to software failure.

    Google Translation from Danish, sorry. //Jørgen