Cannot connect: Timeout while waiting for tranfer ready pin
-
@jay_s_uk Hi Jay,
Yeah the diag light is dim, the rest are solid. I can see that means the firmware is deleted, but I have just tried to turn off the power and plug in via USB and it switches to steady on off, which seems to indicate normal operation, so I'm confused?
-
@ceej Flash the firmware again and check if the problem persists
-
Hi @chrishamm the board is not showing up in my device manager when I connect directly to USB.
The ports tab is not showing, I tried using this guide but I don't think its showing the duet?
The light is still flashing normally when connected via USB
-
@chrishamm Hi Chris,
I have been trying to get this working again. After using three different micro usb cables i bought a new one and I was able to reflash the firmware.
I still am having the 'waiting for transfer ready pin' issue.
I have the pi hooked up to a screen and keyboard and so far I have tried updating to an unstable release, and that doesn't seem to have fixed the issue.
The diag light was flashing when the duet was connected directly via usb, but is now dim again that is connected to the pi.
What should I try next?
-
@ceej if its dim it means theres no firmware. did you remember to remove the erase jumper?
-
@jay_s_uk said in Cannot connect: Timeout while waiting for tranfer ready pin:
if its dim it means theres no firmware.
I'm not sure that's the case for my board because I just plugged the duet in to USB directly again and the light went black to flashing on and off normally.
I did remove the jumper after updating.
-
@ceej are you removing the sd card when connecting the board to the pi?
-
@jay_s_uk Yep i've only got an SD card in the pi
-
@ceej can you post a photo of the LEDs on the board when its just connected to the pi and powered?
-
@jay_s_uk thanks Jay!
-
Is that the ribbon cable that came with the Duet?
-
@Phaedrux no it is not, do you think I need to buy a new ribbon cable?
-
@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 -
@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.
-
@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 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
-
@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 sendingM122
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 ...
-
@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 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.