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

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

Scheduled Pinned Locked Moved
General Discussion
6
21
450
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.
  • undefined
    Polyneutron21 @droftarts
    last edited by 14 Feb 2025, 18:51

    @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.

    undefined undefined 2 Replies Last reply 14 Feb 2025, 18:53 Reply Quote 0
    • undefined
      jay_s_uk @Polyneutron21
      last edited by 14 Feb 2025, 18:53

      @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

      undefined 1 Reply Last reply 14 Feb 2025, 21:46 Reply Quote 1
      • undefined
        Phaedrux Moderator @Polyneutron21
        last edited by 14 Feb 2025, 20:10

        @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

        undefined 1 Reply Last reply 14 Feb 2025, 21:41 Reply Quote 0
        • undefined
          Polyneutron21 @Phaedrux
          last edited by 14 Feb 2025, 21:41

          @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
          • undefined
            Polyneutron21 @jay_s_uk
            last edited by 14 Feb 2025, 21:46

            @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.

            undefined 1 Reply Last reply 14 Feb 2025, 21:50 Reply Quote 0
            • undefined
              jay_s_uk @Polyneutron21
              last edited by 14 Feb 2025, 21:50

              @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

              undefined 1 Reply Last reply 10 Mar 2025, 21:03 Reply Quote 1
              • undefined
                Polyneutron21 @jay_s_uk
                last edited by 10 Mar 2025, 21:03

                @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

                undefined 1 Reply Last reply 10 Mar 2025, 21:49 Reply Quote 0
                • undefined
                  jay_s_uk @Polyneutron21
                  last edited by 10 Mar 2025, 21:49

                  @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

                  undefined 1 Reply Last reply 12 Mar 2025, 23:46 Reply Quote 2
                  • undefined
                    droftarts administrators @andywm
                    last edited by 12 Mar 2025, 13:41

                    @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

                    undefined 1 Reply Last reply 16 May 2025, 10:02 Reply Quote 0
                    • undefined
                      Polyneutron21 @jay_s_uk
                      last edited by 12 Mar 2025, 23:46

                      @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

                      undefined 1 Reply Last reply 13 Mar 2025, 06:41 Reply Quote 0
                      • undefined
                        jay_s_uk @Polyneutron21
                        last edited by 13 Mar 2025, 06:41

                        @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

                        undefined 1 Reply Last reply 13 Mar 2025, 17:15 Reply Quote 0
                        • undefined
                          Polyneutron21 @jay_s_uk
                          last edited by 13 Mar 2025, 17:15

                          @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

                          undefined 1 Reply Last reply 26 Mar 2025, 17:08 Reply Quote 0
                          • undefined
                            elmoret @Polyneutron21
                            last edited by 26 Mar 2025, 17:08

                            @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
                            • undefined
                              andywm @droftarts
                              last edited by 16 May 2025, 10:02

                              @droftarts

                              Sorry to bump a really old topic. I actually did solve this issue, I attended SMRRF and spoke with someone at the Duet booth, possibly even you actually. And had just never come back to check. Forgot my forum etiquette a bit. In my case the included ribbon cable

                              I am updating for anyone else in the future that may come across this thread, as there are already sporadic posts spanning months.

                              As per
                              https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup#warning-lost-connection-to-duet-timeout-while-waiting-for-transfer-ready-pin-error
                              Ribbon cable should ideally be not longer than 150mm.
                              The included ribbon cable that shipped with the Duet 6HC was too long per this advise, about 220-250mm from memory.

                              Once I cut it down, this problem was eliminated for me.

                              undefined 1 Reply Last reply 16 May 2025, 12:14 Reply Quote 2
                              • undefined
                                droftarts administrators @andywm
                                last edited by 16 May 2025, 12:14

                                @andywm Thanks for the follow up, and glad it's working for you now. For some reason it used to work with the older, longer ribbon cable (and sometimes quite a lot longer cables), though I can't say we've tested it recently, and now generally recommend a shorter cable. It may just be down to cable quality, and how good the connection is between the ribbon wire and press-on connector, as they rely on a small 'fork' cutting through the ribbon wire insulation.

                                I've added a fair amount of notes to the troubleshooting page, including links to loopback tests for Duet and SBC, which should help narrow down where the issue is.

                                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
                                • First post
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA