Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Losing USB connection when restart laptop

    Scheduled Pinned Locked Moved
    General Discussion
    4
    11
    407
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Phaedruxundefined
      Phaedrux Moderator @Tricep terry
      last edited by

      @Tricep-terry said in Losing USB connection when restart laptop:

      the duet is not responding anymore

      Can you be more specific about what you mean by this?

      @Tricep-terry said in Losing USB connection when restart laptop:

      I'm controlling my duet over USB

      Do you mean for print jobs, or just USB terminal, or what exactly?

      @Tricep-terry said in Losing USB connection when restart laptop:

      I also noticed that when i power my duet first from the VIN and than plug in my USB, it is not responding aswell.

      Are you taking steps to avoid USB ground loops?

      https://docs.duet3d.com/en/User_manual/Overview/USB_ground_loops

      Z-Bot CoreXY Build | Thingiverse Profile

      Tricep terryundefined 1 Reply Last reply Reply Quote 0
      • Tricep terryundefined
        Tricep terry @Phaedrux
        last edited by

        Dear Phaedrux @Phaedrux

        Sorry for the missing details, I'll explain the scenario more clearly.

        I've a thirty party software that uses python to send single line Gcode to the duet over USB, the USB is connected via a USB isolated (adafruit, the recommended one by duet). When I leave my USB plugged into the laptop and I restart the computer, the communication with the Duet stops, for example if I after restarting the PC open the YAT terminal and send something like M115, i get no response.

        If i unplug the USB cable and plug it back in, the connection is restored and I can send codes via YAT as usual.

        Furthermore, If I power my duet by VIN first and then plug in the USB cable the same behaviour is present as in no communication to duet via programs like YAT. With or without the USB isolator makes no difference (I only test this if my laptop is running on batteries) so the problem is not with the USB isolator.

        I've checked and tried to change USB suspend behaviour, but this did not fix the issue.

        Is there something else I could try?

        Kind regards,

        gloomyandyundefined 1 Reply Last reply Reply Quote 0
        • gloomyandyundefined
          gloomyandy @Tricep terry
          last edited by

          @Tricep-terry What operating system is the laptop running?

          Tricep terryundefined 1 Reply Last reply Reply Quote 0
          • Tricep terryundefined
            Tricep terry @gloomyandy
            last edited by

            @gloomyandy it's windows 11

            chrishammundefined 1 Reply Last reply Reply Quote 0
            • chrishammundefined
              chrishamm administrators @Tricep terry
              last edited by

              @Tricep-terry What firmware version are you using? I know v3.3 or an older release had an issue in the USB stack causing this kind of problem, so make sure you are at least on v3.4.6. Also, make sure to properly close the USB connection of your serial control application before you restart your laptop.

              Duet software engineer

              Tricep terryundefined 1 Reply Last reply Reply Quote 0
              • Tricep terryundefined
                Tricep terry @chrishamm
                last edited by

                @chrishamm

                I've updated to V3.4.6 but the issue persists, I don't think it is my python code as the issue is also there when I do the following:

                • plug in USB cable into PC

                • open YAT terminal

                • send M115 to test for connection, which than responses as intended

                • close YAT

                • restart laptop

                • open YAT terminal

                • send M115 to test for connection, no response, while the terminal at the bottom right says that the com port is open and connected

                to restore the functionality:

                • un plug USB cable
                • plug in USB cable
                • send M115 to test for connection, which than responses as intended

                Could you let me know if by performing this sequence of events, you obtain similar results?

                chrishammundefined 1 Reply Last reply Reply Quote 0
                • chrishammundefined
                  chrishamm administrators @Tricep terry
                  last edited by

                  @Tricep-terry I can try to reproduce it. What Duet do you have?

                  Duet software engineer

                  Tricep terryundefined 1 Reply Last reply Reply Quote 0
                  • Tricep terryundefined
                    Tricep terry @chrishamm
                    last edited by

                    @chrishamm I've a duet 3 mini 5+

                    chrishammundefined 1 Reply Last reply Reply Quote 0
                    • chrishammundefined
                      chrishamm administrators @Tricep terry
                      last edited by

                      @Tricep-terry I can reproduce it with v3.4.6 but not with v3.5.0-rc.3+. I suggest you upgrade to that version.
                      @dc42 do you know if a fix has been backported to 3.4-dev?

                      Duet software engineer

                      Tricep terryundefined 1 Reply Last reply Reply Quote 0
                      • Tricep terryundefined
                        Tricep terry @chrishamm
                        last edited by

                        @chrishamm that indeed did the trick. It also fixed the issue with the order of powering the device. Many thanks.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA