USB not connected #31602 (CORE One) #35602 (CORE One L) #26…

What happened?

During firmware flashing on your Original Prusa Printer, you might get the message "USB drive not connected! Please insert a USB drive with a valid firmware file".

Error name: USB not connected

Error code: #31602 (CORE One) #35602 (CORE One L) #26602 (MK4S) #13602 (MK4) #27602 (MK3.9S) #21602 (MK3.9) #28602 (MK3.5S) #23602 (MK3.5) #17602 (XL) #12602 (MINI)

This issue happens when there is an error reading the USB drive.

How to fix it?

Make sure that the USB drive is connected to the printer, and that the USB port in the mainboard is not damaged. If the error persists, try using a new, FAT32-formatted USB drive.

Are you still having issues? Contact our support team and let them know that you tried to fix the issue with these instructions. We will take it from there.

Was this article helpful?

This action is available only to registered users. Please log-in.

2 comments

Foothills Restoration Werks

•

I ran into the same problem of losing connectivity to my Prusa USB thumb drive on my MK4s printer. I could read the drive when plugged into my laptop with no problem, so the problem was not with the drive itself. To correct the problem, I used an industry standard electronics aerosol cleaner on the printer LCD connections for the USB, ground cable and data ribbon cables. After reconnecting everything, and powering up the printer, the Prusa USB thumb drive was accessible again. The bottom line is that the quality of the electrical contacts, on the Prusa LCD board, are not as good as they used to be when I started with the original Mk3 many years ago, which has been upgraded several times. Occasional cleaning of the on board and peripheral insert connectors is required to maintain proper data and electrical conductivity.

Squiggleypuff

•

This happened to me on my MK3.5S upgrade. It turned out the ribbon cable was not totally seated on the LCD board. After plugging it in fully, the USB drive was recognized and I could update firmware.

SafetyLighting

•

Thank you for posting this. Had the same issue and this saved me.