Cannot connect to Prusa Mini+ using the USB Mini on Windows
 
Notifications
Clear all

Cannot connect to Prusa Mini+ using the USB Mini on Windows  

  RSS
Afonso Santos
(@afonso-santos)
New Member
Cannot connect to Prusa Mini+ using the USB Mini on Windows

Hi all,

As the title says, I'm having some issues while trying to connect to my Prusa Mini+, using my Windows 11 PC.

Prusa Support sayed that the Mini+ is not compatible with Pronterface nor Octoprint (which is false, I used OctoPrint via a Raspberry Pi 4 before).

I also installed OctoPrint on my PC and cannot find the port, and then checked on Device Manager:

Translated: the device could not be started. I've tried on USB 3.1 and 2.0 ports,  no luck.

Anyone have any ideas?

Thansks!

Napsal : 06/12/2022 9:01 pm
nano007 se líbí
nano007
(@nano007)
New Member
RE:

For what it's worth, I have the same issue...

Seems like it works for some folks.. at least the impression I get from reading some of the forum and reddit posts..

For example - https://forum.prusa3d.com/forum/hardware-firmware-and-software-help/using-pronterface-with-mini/#post-344374

But I have same error as one mentioned by OP, and seems to be the problem which prevents me from connecting to my mini+ from my computer.

 

 

Would appreciate any insights or help on resolving this issue.

Thanks

This post was modified před 2 years by nano007
Napsal : 28/12/2022 4:14 am
René
(@rene-3)
Reputable Member
RE:

The mini+ is a serial device within Windows.

In that case, that means that the printer is placed in the COM tab in the device manager.

You need to install a special driver for this.

It is the CH340/341SER driver.

You can download it here,

http://www.wch-ic.com/downloads/CH341SER_EXE.html

If you have installed the driver, a com port is assigned to the printer (in my case it is COM9).

Proterface is working here.

Napsal : 28/12/2022 8:53 am
Afonso Santos
(@afonso-santos)
New Member
Topic starter answered:
RE: Cannot connect to Prusa Mini+ using the USB Mini on Windows

Hi,

The issue was due to the latest firmware version, and it's now fixed by upgrading to the latest version available.

Thank you.

Napsal : 28/12/2022 9:36 am
Share: