Re: Usb Device_descriptor_failure Driver Download
Luar Ehria
Make sure you have downloaded and installed the latest AMD chipset drivers for your board directly from AMD's website. If the issue is still persisting after the chipset update, and you have plugged the mousepad directly into a USB port on the back of the physical motherboard, reach out to our support team by opening a ticket at
2 days ago, after installing my new enclosure for my ender 3 pro and lifting it in, while also changing my nozzle, and connecting a new webcam I was suddenly no longer able to connect my Ender 3 Pro to my raspberry pi. It has been working for months up until now, but whatever I try now, I get the following error:
My printer is the Ender 3 Pro with the BLtouch. I flashed the firmware once with the BLtouch firmware as Creality had explained in the video. I no longer know the exact version and since I can't connect my printer anymore I can't see it. I would not expect it to be a firmware issue since it was working fine, and suddenly without any changes to my printer it stopped working.
I can't seem to figure out the issue for the life of me, the only option I can think of something to try still is to re flash my firmware of the printer, that it got corrupted somehow, but I don't even know if this is possible from just moving my printer?
Another other possibility is that of the 4 cables, only the original cable is a data cable and the 3 others are not, and by moving it I broke the original cables data part. It was still powering my printer before I covered the 5V pin though, so its not like the cable was entirely broken (I don't see any loose parts in the cable either)
I am able to connect to my raspberry pi through putty yes. I am also able to connect to the web interface of my raspberry pi. My octoprint is unable to make the serial connection to my printer though.
What do you mean with 'connect to the controller'? You do not mean the raspberry pi with the controller then? If you did mean the raspberry pi, I am able to connect to it manually through PuTTY, if you meant something else with the controller, please elaborate.
Cool, I did not know that. I managed to connect to it in PuTTY, the printer suddenly showed up in my devicemanager as a COM, I did try installing a driver earlier that I thought failed, but perhaps it was due to a restart.
Hmm alright, I'll give that a try. Does that mean that you think there's a chance that doing a basic movement on Ponterface will somehow fix the connection between the printer and OctoPrint? Since if I do a basic movement on Ponterface I still didn't actually change something, right?
I didn't get to try Ponterface, but this morning I tried once again to connect OctoPrint to my printer and suddenly it worked.. I then rebooted out of safe mode to normal mode and it still worked. Then I tried connecting my camera and now I'm stuck with the same issue again. I plugged out my camera, tried safe mode again but I can't get anything to work now.
It seems like plugging in my camera once, even though it works, breaks the connection to my printer for a while, and then it randomly starts working again. Any idea what I can do about this? Rebooting the devices in any combination does not seem to work.
I've changed my cable specs. I only buy HIGH QUALITY data cables. I only use 1' or 33 mm cables. My Rpi's set just in front of the USB ports. I'm using Pi4-4gb's, I use a USB 2.x port. Then there is the port discovery, I unplug the cable, reboot the printer, connect the cable. That usually works. It is a "chicken & egg" thing... You have to find what works for you!
Hmh, do you reckon 33mm cable vs for example 300mm cable matters that much? Perhaps I should get a shorter high quality data cable as well then if the problem occurs again. I somehow got it to work by just rebooting many times and trying different combinations of plugging the cable in and out, and now it works even on reboots of the printer. For now I'm definitely not changing any cable at all, but if it would break again, I guess I'll purchase a short cable and see if that improves anything.
Still find it a bit weird that it was working fine, then randomly stopped working for a while and then started working again. I see more people having similar issues where it suddenly just works, and I would find it weird if the cable sometimes consistently works, and sometimes consistently doesn't.
So I've got a follow up on this: I worked on some extruding issues a bit more, during which I shut down the printer and disconnected all the cables, and surely enough after booting everything back up, I had the same issue again.I couldn't get it to work at first, until suddenly at some point in randomly worked again. At this point my camera was not plugged in, but I was able to make the connection. Then I plugged in the camera, executed sudo service webcamd restart and the webcam feed worked. At this point, I got an issue in the conection:
Instead of
State: Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)
I got something like this error:
Offline (Error: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)'
I can see some interesting stuff going on after 4705.242244 and after 4991.877538 but I can't quite put my finger on it. It definitely seems like it is camera related, but I wonder if it is a power issue, or something else. (I am using the official rpi 4 power brick).
Initially it was in there, but whenever I tape the 5V it seems to come loose again after plugging it in and out a couple of times, currently that has happened again so the 5V pin of the USB between the printer and raspberry pi is no longer taped.
If it is indeed a problem of requiring too much current and my 5V pin of the USB between the printer and pi was taped, does that mean that the raspberry pi simply cannot power the camera, since it does not have to power the printer then? In that case, how come that whenever I plug in the camera, that always works?
Good morning, I'm having trouble installing the arduino uno r3 in windows 8.1, ja also tried in windwos 7 and the problem continues go to the device manager I update the driver but the following error:
Windows has stopped this device because it has reported problems. (Code 43)
Hello thanks for the reply, I have done it but says the latest driver is installed ja ja fetched drivers tested with different versions of the Arduino and on different machines and nothing but the arduino uno board is new, do not understand if someone could help
Then I remembered my problems (documented by Adafruit) where the Raspberry Pi sometimes didn't get enough power when a cheap USB cable with thin wires is used (too much voltage drop). So I switched the USB cable to a new high-quality cable and everything immediately started working!
"Hey there, do you have any clues about what to do when the USB drive suddenly become unrecognized with an error message "USB Device Descriptor Failed'?
I Googled this error message; it means that my USB drive isn't recognized by my computer. And I don't know what to do with this error. So do you know any ways or solutions that can make my USB drive work again? How?"
Have you ever met such a problem that your USB drive or SD card suddenly stops working or unable to respond while connecting to PC? If you have a similar problem or device not recognized error, don't worry and you can follow offered methods here below to get your case solved now.
If you are a Windows 10 user, having USB or SD card, etc. devices not recognized error in the computer, you may follow to apply Windows 10 Troubleshooter to fix 'USB\Device Descriptor Failure' error now:
When USB driver is outdated in a new Windows system or bad sectors exist on the USB drive, the USB drive may become unrecognized or undetectable at very high risk. So now you can follow and repair USB isn't recognized with 'Device Descriptor Failed' error now:
EaseUS DriverHandy is a utility to update your device drivers and can free your hands from a complex updating process. It can update your USB driver with one click. Now, download this tool to update your USB drivers.
Here we'd like to recommend you try professional partition manager software to fix and repair bad sectors on the USB drive effectively. You may free download EaseUS Partition Master with the below steps to make the USB drive work again:
In order to resolve this issue, your device or any other devices you want to connect with this same issue, I suggest you do this; Open the Windows PowerShell (Admin) and type: chkdsk /f/r/x. It will inform: 'The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)' select Y then re-boot your machine and follow the on screen prompts.
After the reboot, again, Windows PowerShell (Admin) and type: sfc /scannow and allow the process to finish.
Now clean the registry with a reputable program such as CCleaner then take a note of the device/s name and select 'run' from the Windows menu list bottom left.
Type 'regedit' without the apostrophes and open the registry.
Select 'Edit' then Search... and type the brand name of the device in the search bar.
The search results will point you to a series of strings of the device that was giving the *(device descriptor request failed) code 43* error message.
Every string in the registry with the name of your device will need to be deleted but ensure it is the device's name from which was generating this error example; Logitech, Seagate, whatever brands device name that has generated this error code!
Ensure you have removed every last trace of your devices name in the registry.
Then after completion use the CCleaner again to remove all known traces and re-install the devices software if this is the case.
Your device will come back to life without the error message and start to work again.
Reasons why this happen are not entirely certain but often PC's pick up spyware/malware/virus's and corrupt the registry's strings other times, updates and upgrades in particular over lap information and again, corrupt the software and its registration process.