Cannot connect: Timeout while waiting for tranfer ready pin

Phaedrux

Is that the ribbon cable that came with the Duet?

ceej

@Phaedrux no it is not, do you think I need to buy a new ribbon cable?

jay_s_uk

@ceej do you not have the original cable any more?
Do you need to really run in SBC mode? I see you're using ethernet anyway so just plug it into the 6HC and go standalone

ceej

@jay_s_uk I don't have the orignal cable unfortunately. The ethernet just runs to a pass-through port on the case, I will use it in future but for now I don't have ethernet on this side of the house.

ceej

@jay_s_uk I've now got a new cable and unfortunately I am still having the transfer ready pin error. Is there something else I can try or is one of my boards cactus?

Phaedrux

Can you do this test?

https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#testing-gpio-capability-of-the-sbc

ceej

@Phaedrux thanks, I have just attempted the test and got 1 and 0, I also attempted the test immediately below and got the normal FF.. DEAD BEEF BAAD FOOD response

chrishamm

@ceej It may be a good idea to repeat the test with the ribbon cable, perhaps there is a bad contact somewhere in a cable connector. Also you should have v3.4.5 or newer both on the SBC and on the Duet 3 mainboard.

You can check this via SSH by running dpkg-query -l duetsoftwareframework on the Pi and by sending M122 using a serial console (minicom from the Pi) with a USB cable conected:

ii  duetsoftwareframework 3.4.5 armhf        Meta package for the full Duet software framework

and

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 ...

ceej

@chrishamm thank Chris,

I'm sorry I think I'm lost. I have checked the Pi and it is running 3.5.0~beta.2.

To check the Duet, is it correct to say:

Connect the USB cable from the Pi to the Duet
Only have an SD installed in the Pi, not the Duet
Run M122 (I used cutecom)

If so, when I run the command, nothing appears. It should populate instantly after clicking send right?

ceej

@ceej I decided to try flashing the firmware again on the duet just to make sure they are both the same.

I flashed it to the same beta version.

After trying many times, I was only able to get a response from YAT once for M115:

3.5beta2 ELECTRONICS: Duet 3 MB6HC v1.0 or earlier FIRMWARE_DATE: 2023-02-08 17:43:01<LF>ok<LF>

I am still not able to connect via DWC when I remove the SD and then power on the Pi and Duet.

The board is also showing up with the yellow warning triangle in device manager every now and then, but installing the firmware in device manager says it is up to date.

ceej

I'm worried I won't be able to get this board to work and will need to explore other options.

If so, some things I am considering are:

Getting the board repaired (if its possible / economical).
Getting a second hand 6HC to slot in where the current one is.
Replacing the board with a BTT Octo or Mellow Super or similar and running Klipper or RRF - @jay_s_uk is this something you would recommend?

Any thoughts would be much appreciated.

jay_s_uk

@ceej if you're wanting to use the 3HC (and maybe other CAN boards). If you're going to run more than one CAN-FD board then I would look at either the SKR3 or the Super8Pro as they have native CAN-FD support (note the H7 based boards don't currently support SBC mode). If its just one (or maybe 2) CAN-FD boards then an STM32F4 board + one of the new SPI to CAN-FD modules. Going for one of the first 2 is always best though.
Generally I advise not to bother with the pi in a duet setup.
You could of course just get an ethernet to WiFi adapter if all you're using it for is WiFi and ditch the pi.

chrishamm

@ceej I'm sorry to hear you're still having problems. When did you purchase that board? It might be that the processor has developed a fault. Newer boards have logic buffers between the Pi and Duet MCU but I don't think the v1.0 has them.

I generally operate all my Duets in SBC mode without problems.

droftarts

@ceej said in Cannot connect: Timeout while waiting for tranfer ready pin:

@ceej I decided to try flashing the firmware again on the duet just to make sure they are both the same.

I flashed it to the same beta version.

After trying many times, I was only able to get a response from YAT once for M115:

3.5beta2 ELECTRONICS: Duet 3 MB6HC v1.0 or earlier FIRMWARE_DATE: 2023-02-08 17:43:01<LF>ok<LF>

I am still not able to connect via DWC when I remove the SD and then power on the Pi and Duet.

The board is also showing up with the yellow warning triangle in device manager every now and then, but installing the firmware in device manager says it is up to date.

Did you disconnect the ribbon cable when connecting via USB? I generally find USB connections more reliable when the Duet has no other connections. Otherwise, this sounds more like a bad USB cable, or one that the 6HC (which is a bit picky about USB cables because the processor defaults to a very high baud rate when firmware is erased). Your ribbon cable looks like it doesn't have a top clamp on either end of it; this may be causing poor connections. You said you bought a new cable; did you mean ribbon or USB cable?

Neat wiring, BTW!

Ian