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

    DCS Not starting (Could not connect to Duet)

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    3
    33
    1.4k
    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.
    • bcrazycramerundefined
      bcrazycramer
      last edited by

      Same thing.

      d6c8494c-4ce2-4a38-88fd-788c5cfa64ea-image.png

      Verify:

      6ca1b85d-1473-4e14-82d3-dbe58826760b-image.png

      1 Reply Last reply Reply Quote 0
      • A Former User?
        A Former User
        last edited by

        other options include SAM-BA software or atmel studio. you could also find it works with another computer and/or usb cable.

        1 Reply Last reply Reply Quote 0
        • bcrazycramerundefined
          bcrazycramer
          last edited by

          I got it to switch to COM4 and got farther:

          c923c661-a704-43a6-a7fa-7b2ed654206d-image.png

          1 Reply Last reply Reply Quote 0
          • A Former User?
            A Former User
            last edited by A Former User

            thats a bit fishy; sounds like the connection was broken when it was COM3 and because the software still were using COM3 it had to be assigned to COM4 when it reconnected (or do you happen to have two separate Duet3 boards connected to to different USB ports?)

            edit: I'd focus on trying other usb cables/usb ports based on that

            1 Reply Last reply Reply Quote 0
            • bcrazycramerundefined
              bcrazycramer
              last edited by

              I will give all this a try tomorrow. Thanks!!

              1 Reply Last reply Reply Quote 0
              • bcrazycramerundefined
                bcrazycramer
                last edited by

                I'm having the same issue this morning using a Dell Laptop. The Duet 3 shows up as Com 3 in Device Manager. Bossa Program Port (Com3). When I try to verify I get the SAM-BA operation failed.

                1 Reply Last reply Reply Quote 0
                • bcrazycramerundefined
                  bcrazycramer
                  last edited by

                  With another USB cable when I Verify I get Verify failed with page errors and byte errors.

                  1 Reply Last reply Reply Quote 0
                  • A Former User?
                    A Former User
                    last edited by

                    given the board was flashed and tested before it shipped I'm inclined to think the issue is the usb cables still. its not the first time someone have tried 3 and 4 cables before getting a new one and then succeeding.

                    alternatively trying sam-ba or atmel studio instead of bossa.

                    1 Reply Last reply Reply Quote 0
                    • bcrazycramerundefined
                      bcrazycramer
                      last edited by

                      I wasn't clicking write and then verify. My bad.

                      Current status after the write and verify:

                      Aug 18 19:43:25 duet3 systemd[1]: Stopped Duet Control Server.
                      Aug 18 19:43:25 duet3 systemd[1]: Started Duet Control Server.
                      Aug 18 19:43:26 duet3 DuetControlServer[1654]: Duet Control Server v3.1.1
                      Aug 18 19:43:26 duet3 DuetControlServer[1654]: Written by Christian Hammacher for Duet3D
                      Aug 18 19:43:26 duet3 DuetControlServer[1654]: Licensed under the terms of the GNU Public License Version 3
                      Aug 18 19:43:26 duet3 DuetControlServer[1654]: [info] Settings loaded
                      Aug 18 19:43:26 duet3 DuetControlServer[1654]: [info] Environment initialized
                      Aug 18 19:43:26 duet3 DuetControlServer[1654]: [fatal] Could not connect to Duet (Board is not available (no header))
                      Aug 18 19:43:26 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
                      Aug 18 19:43:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
                      Aug 18 19:43:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 51.
                      Aug 18 19:43:32 duet3 systemd[1]: Stopped Duet Control Server.
                      Aug 18 19:43:32 duet3 systemd[1]: Started Duet Control Server.

                      1 Reply Last reply Reply Quote 0
                      • bcrazycramerundefined
                        bcrazycramer
                        last edited by

                        How can I get an original 26 pin to 40 pin ribbon cable for the Duet 3 to Raspberry Pi?

                        1 Reply Last reply Reply Quote 0
                        • A Former User?
                          A Former User
                          last edited by A Former User

                          achrn said in Spare ribbon cable??:

                          https://shop.pimoroni.com/products/downgrade-gpio-ribbon-cable-for-pi-a-b-pi-2-pi-3-pi-4-40p-to-26p

                          (but it's not going to affect the issue at hand)

                          1 Reply Last reply Reply Quote 0
                          • bcrazycramerundefined
                            bcrazycramer
                            last edited by

                            Why do you say it won't help?

                            1 Reply Last reply Reply Quote 0
                            • A Former User?
                              A Former User
                              last edited by

                              The Pi seems to indicate the Duet is connected but not responding properly.

                              Are you able to connect to the usb serial console and execute M115 to show which version of the firmware is running on the Duet now?

                              bcrazycramerundefined 1 Reply Last reply Reply Quote 0
                              • bcrazycramerundefined
                                bcrazycramer @A Former User
                                last edited by

                                @bearer said in DCS Not starting (Could not connect to Duet):

                                The Pi seems to indicate the Duet is connected but not responding properly.

                                Are you able to connect to the usb serial console and execute M115 to show which version of the firmware is running on the Duet now?

                                So connect it up with Repetier host or something similar and issue M115?

                                1 Reply Last reply Reply Quote 0
                                • A Former User?
                                  A Former User
                                  last edited by

                                  Yeah, although any serial terminal will suffice

                                  1 Reply Last reply Reply Quote 0
                                  • bcrazycramerundefined
                                    bcrazycramer
                                    last edited by bcrazycramer

                                    Duet 3 MB6HC Firmware Version 3.1.1 Electronics: Duet 3 MB6HC V1.01 or later

                                    1 Reply Last reply Reply Quote 0
                                    • A Former User?
                                      A Former User
                                      last edited by

                                      Well, thats good news!

                                      Is the cable damaged? Its theoretically possible the cable is the issue, but its at least partially functioning.

                                      There are a few tests you could run to verify the pi and cable is okay by placing some jumpers to connect together some pins on the duet end of the ribbon cable.

                                      this post (and the rest of the thread has a lot of information on this) https://forum.duet3d.com/post/149055

                                      i'd set up the software according to that that link, test the pins of the pi without a ribbon cable, then connect the ribbon cable, and move the shorts to the duet side of the ribbon cable with the pi end connected to the pi. should help pinpoint where the issue is

                                      1 Reply Last reply Reply Quote 0
                                      • bcrazycramerundefined
                                        bcrazycramer
                                        last edited by

                                        Do we know which pins are being used between the two? My old cable it damaged on the raspberry pi side. The first 20 pins are still in the connector.

                                        1 Reply Last reply Reply Quote 0
                                        • A Former User?
                                          A Former User
                                          last edited by A Former User

                                          its noted on the wiring diagram and pretty thoroughly covered in that thread ๐Ÿ‘†
                                          (the one in the picture looks alright?)

                                          1 Reply Last reply Reply Quote 0
                                          • bcrazycramerundefined
                                            bcrazycramer
                                            last edited by

                                            New ribbon cable installed and I still can't connect to the Duet:

                                            Aug 21 19:31:09 duet3 systemd[1]: Stopped Duet Control Server.
                                            Aug 21 19:31:09 duet3 systemd[1]: Started Duet Control Server.
                                            Aug 21 19:31:10 duet3 DuetControlServer[1868]: Duet Control Server v3.1.1
                                            Aug 21 19:31:10 duet3 DuetControlServer[1868]: Written by Christian Hammacher for Duet3D
                                            Aug 21 19:31:10 duet3 DuetControlServer[1868]: Licensed under the terms of the GNU Public License Version 3
                                            Aug 21 19:31:10 duet3 DuetControlServer[1868]: [info] Settings loaded
                                            Aug 21 19:31:10 duet3 DuetControlServer[1868]: [info] Environment initialized
                                            Aug 21 19:31:10 duet3 DuetControlServer[1868]: [fatal] Could not connect to Duet (Board is not available (no header))
                                            Aug 21 19:31:10 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
                                            Aug 21 19:31:16 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
                                            Aug 21 19:31:16 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 64.
                                            Aug 21 19:31:16 duet3 systemd[1]: Stopped Duet Control Server.
                                            Aug 21 19:31:16 duet3 systemd[1]: Started Duet Control Server.

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