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

    Duet3 + SBC (Timeout while waiting for transfer ready pin)

    Scheduled Pinned Locked Moved
    General Discussion
    6
    19
    421
    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.
    • Polyneutron21undefined
      Polyneutron21 @andywm
      last edited by

      @andywm I have the same issue. I had Chinese boards that played nice until they started getting drop outs. I purchased a genuine Duet 3 6HC and used the included cable to connect the Pi5 to the 6HC and "Timeout waiting for transfer pin. I noticed a 16 gb micro-SD card in the 6HC and thought it may be the issue, but no. Then I tried a new 24-40 pin cable and still had the same issue. Formatted thee 64GB stick with 2024-09-19-DuetPi_arm64.img and tried it after booting all Led's were bright but still had the same issue, tried a different Pi5 with a fresh copy and still "timeout waiting for transfer pin.

      20250213_143138[1].jpg

      I am at the end of my rope,

      droftartsundefined 1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @Polyneutron21
        last edited by

        @Polyneutron21 Did you remove the SD card from the 6HC? It won't be running in SBC mode if it is still in the 6HC. In our experience, most "Timeout while waiting for transfer ready pin" issues are caused by interference on the ribbon cable; see https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup#warning-lost-connection-to-duet-timeout-while-waiting-for-transfer-ready-pin-error
        You appear to have a stepper driver cable running pretty close to the ribbon cable.

        If you have a second Raspberry Pi, I'd also test with that, in case it's an issue with the RPi rather than the Duet. Also worth checking the 6HC functionality by setting it up in Standalone mode, if possible.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        Polyneutron21undefined 1 Reply Last reply Reply Quote 0
        • Polyneutron21undefined
          Polyneutron21 @droftarts
          last edited by

          @droftarts I did remove the 16GB micro SD but this did not resolve the "Timeout waiting for transfer pin" and I have two Pi 5's and have tried both. The one dedicated to the SBC roll used to work fine. I took the Pi5 off the display and tried that one with a fresh image but that didn't work either. I also have two 24-40 pin cables and neither of those make a difference.

          Polyneutron21undefined 1 Reply Last reply Reply Quote 0
          • Polyneutron21undefined
            Polyneutron21 @Polyneutron21
            last edited by

            @Polyneutron21 I looked at the contents of the Micro SD that came with the 6HC and put it back into the 6HC then connected to the ethernet and only the red and green lights are on but I don't see any communication through the router. Do I need a jumper or something to tell it to go to stand alone mode?

            droftartsundefined 1 Reply Last reply Reply Quote 0
            • droftartsundefined
              droftarts administrators @Polyneutron21
              last edited by

              @Polyneutron21 Has the 6HC ever communicated with the RPi? If not, probably bench testing the 6HC and a Pi would be a good idea, ie with nothing else plugged in apart from power and the ribbon cable between them.

              What firmware version is on the 6HC, and have you updated the DuetPi? I believe there were some issues initially with RPi 5 support (@chrishamm will know better). To update see https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup#update-firmware

              There is also a newer RPi image, see https://forum.duet3d.com/topic/37011/duetpi-bookworm-2024-11-27-now-available, it may be worth trying that.

              Do I need a jumper or something to tell it to go to stand alone mode?

              No, just the SD card in the 6HC SD socket. You also need correct command to enable networking in config.g - M552 S1 P0.0.0.0, or send it via a USB connection using YAT. You may need to have the correct version of DWC on the SD card, to match the firmware version.

              Ian

              Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

              Polyneutron21undefined 1 Reply Last reply Reply Quote 0
              • Polyneutron21undefined
                Polyneutron21 @droftarts
                last edited by

                @droftarts I just shh into Pi and updated to version 3.5.4 and still waiting for transfer PIN. I will take out the Pi5 again and then put the card in and follow the instructions on getting it to stand alone. What is the point of all this. I think it is time to move past duet.

                jay_s_ukundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @Polyneutron21
                  last edited by

                  @Polyneutron21 good luck with klipper!

                  Probably best to sort out your wiring as suggested rather than complaining something doesn't work

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  Polyneutron21undefined 1 Reply Last reply Reply Quote 1
                  • Phaedruxundefined
                    Phaedrux Moderator @Polyneutron21
                    last edited by

                    @Polyneutron21 said in Duet3 + SBC (Timeout while waiting for transfer ready pin):

                    What is the point of all this.

                    That may be a good question actually. Is there something you require the Pi for, rather than just standalone mode?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Polyneutron21undefined 1 Reply Last reply Reply Quote 0
                    • Polyneutron21undefined
                      Polyneutron21 @Phaedrux
                      last edited by

                      @Phaedrux I would rather use SBC mode. if I cannot get the SBC mode straight, there is little to no point. I have Two Manta M8P with integrated CM4 with 8 gb memory and 16GB EMMC and I had klipper on the emmc for years. CanFD was the clear choice as Can was too flakey. I still have a couple EBB36 tool boards but UUID's kept getting lost.

                      1 Reply Last reply Reply Quote 0
                      • Polyneutron21undefined
                        Polyneutron21 @jay_s_uk
                        last edited by

                        @jay_s_uk I took it out of the printer, connected it to a 24 VDC power supply and the pi to the computer with the USBC and the 24-40 pin cables. The wiring could not be simpler yet there was no change. I updated the firmware in the Pi 5 to 3.5.4 but the transfer pin faulted there as well. The update did finish.

                        Then I took it all down to pieces and used only the microSD card that came with the board and a USBC cable to the computer and the computer doesn't see it and the device manager doesn't have it.

                        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                        • jay_s_ukundefined
                          jay_s_uk @Polyneutron21
                          last edited by

                          @Polyneutron21 maybe you need to flash the board with firmware then. Best look at bossa recovery for the board you have

                          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                          Polyneutron21undefined 1 Reply Last reply Reply Quote 1
                          • Polyneutron21undefined
                            Polyneutron21 @jay_s_uk
                            last edited by

                            @jay_s_uk Okay I used Bosa to flash the 6HC with the newest firmware. Neither Pi 5 would connect without the error. I purchased a new Raspberry Pi 4B it arrived today. I burned the newest Duet Web control to the Duet microSD card using the raspberry pi imager. Then I connected the 24 pin plug to the mainboard and the 40 Pin GPIO on the pi SBC. I inserted the new image. Used a PSU to supply power to the Pi and a 24V PSU to power the 6HC mainboard. It booted up, tried to connect and "waiting for transfer pin" error again. I have not been able to connect this board without the waiting for transfer pin satisfied.
                            20250310_154805[1].jpg

                            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                            • jay_s_ukundefined
                              jay_s_uk @Polyneutron21
                              last edited by

                              @Polyneutron21 you have the cable connected incorrectly to the pi...
                              https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup

                              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                              Polyneutron21undefined 1 Reply Last reply Reply Quote 2
                              • droftartsundefined
                                droftarts administrators @andywm
                                last edited by

                                @andywm said in Duet3 + SBC (Timeout while waiting for transfer ready pin):

                                Hello, I need help troubleshooting this issue;

                                A few months ago, I converted one of my machines to use an SBC mode Duet3 6HC. The machine now randomly halts. DWC will report status=disconnected. And this warning will be in the console;

                                "Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin"
                                

                                Sorry for not replying to your initial post, not sure how I missed it. Generally, intermittent timeout issues are due to interference. There is some troubleshooting advice in the documentation here: https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup#warning-lost-connection-to-duet-timeout-while-waiting-for-transfer-ready-pin-error

                                Ian

                                Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                1 Reply Last reply Reply Quote 0
                                • Polyneutron21undefined
                                  Polyneutron21 @jay_s_uk
                                  last edited by

                                  @jay_s_uk You are correct, I re-connected all of it correctly and nothing changed. First time for everything. I have tried two different pi 5's and two different 26 pin to 40 pin GPIO and this was a new Pi 4B 8GB.
                                  20250312_171520[1].jpg

                                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                  • jay_s_ukundefined
                                    jay_s_uk @Polyneutron21
                                    last edited by

                                    @Polyneutron21 take the SD card out of the 6HC...

                                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                    Polyneutron21undefined 1 Reply Last reply Reply Quote 0
                                    • Polyneutron21undefined
                                      Polyneutron21 @jay_s_uk
                                      last edited by

                                      @jay_s_uk SD card is out. Cables are correct. Shh in and updated software. Still incomplete connection as it is waiting for the transfer pin.20250313_121039[1].jpg

                                      elmoretundefined 1 Reply Last reply Reply Quote 0
                                      • elmoretundefined
                                        elmoret @Polyneutron21
                                        last edited by

                                        @Polyneutron21 Had a chance to troubleshoot your 6HC return today. First tests did confirm the transfer ready pin error, but then I noted that the erase jumper was left on the pins, continuously erasing the firmware. I took a close look at the photos you posted to the forum, and I can see the erase jumper was installed then, too:

                                        ee54ba38-508a-4867-b9cd-3a1eda306160-image.png

                                        I removed the erase jumper, flashed the firmware with Bossa, and tested the board - it works fine:

                                        bf951c7f-9a86-4612-aa3c-e25296ec8181-image.png

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