Cannot connect through USB. Driver issue?
-
I am building a custom CR10 clone from scratch and a few weeks ago I installed the firmware and was able to connect to the board with no issues. Now that I'm ready to start testing I can't get anything to connect. In the devise manager it says Unknown USB Devise (Devise Description Request Failed) and I get this message in the devise status, Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed. I've tried uninstalling the devise but when I reinstall the drivers I see no change. I've tried different USB cables and ports with no change and at this point I have no idea what to do next.
-
Some people recommend reinstalling the driver, but this often doesn't help.
I would try to use a different USB port, where a different USB chip is used. E. g. a. 4-port USB Hub. In my experience USB 2 is sometimes better than USB 3 for this kind of hardware. If your PC has USB 3 and 2, I would try USB2. I would try the USB port, where your mouse or keyboard are connected.I had a USB 3 port where the connections did not work, USB 2 was ok. After a few weeks all ports worked again. I connected a simple hard drive. One port didn't work at all. I thought it is defect. After some time, I tested again and it worked again. Whether it was a defect electronic part (overheating?), driver problem or conflict - I don't know.
BTW using an active USB hub between PC and printer is recommended anyway, it protects the PC if there are unintentional short circuits on the printer side.
-
The "Device descriptor request failed" message happens in Windows sometimes when you reset a Duet. Windows then seems to lock out that port. The workarounds I know of are:
- Plug the Duet into another USB port
- If the port is on an external hub, disconnect and then reconnect the hub
- Reboot Windows.
-
Now it's showing up as a Bossa Program Port. I'm so frustrated I don't know what to do.
-
There are some findings if you search for bossa port, e.g.
https://community.atmel.com/forum/board-detected-bossa-program-port-help -
After detecting as Bossa port, maybe it is sufficient to reboot or remove/reinstall USB driver now. (I would restart first, then try reinstall). With reboot turn PC off (no hibernate mode, really off).
-
If it is showing up as a Bossa port, that means the firmware has been erased. Probably, you pressed the Erase button. You will need to install main firmware as described at https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3.
-
I've been able to connect to the board now through YAT and the Duet WebControl. Unfortunately when I connect through Web Control and go to System Editor, nothing is there
-
Which firmware version did you install? The Settings/General page of DWC should tell you what you have.
-
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 1.21 (2018-03-21)
WiFi Server Version: 1.21RC4(08b3)
Web Interface Version: 1.21.1 -
you can check with the computer setting and see what issue you are facing if still the problem is not solved, you can check with Microsoft 365 support and get step by step details to a configuration.
-
Perhaps the /sys folder is missing from the SD card?
What happens if you send M21 from the GCode Console page of the web interface?
-
I'm getting this M21 SDHC card mounted in slot 0, capacity 3.98Gb<LF>ok<LF>
-
In that case the card is mounted (at least after you ran M21). Have you checked whether the /sys folder exists on the SD card?
-
Yes /sys file is there.
-
When you get the "Card is not mounted" error:
- Try sending M39 to report the SD card information;
- Send M21 to mount the card, then see if the System Editor page works.
It could be that your SD card socket has a dodgy contact.
