Pronterface is unable to connect to Prusa i3 mk2
 
Benachrichtigungen
Alles löschen

Pronterface is unable to connect to Prusa i3 mk2  

  RSS
Matt
 Matt
(@matt-22)
New Member
Pronterface is unable to connect to Prusa i3 mk2

Hello!

I'm a newbie to the world of 3d printing, and I just received my printer today!

I am having trouble getting the provided Pronterface application downloaded from the Prusa website to connect to my printer via USB.
I installed the latest drivers 1.7.6

My current setup is..
Windows 10 Pro
Prusa i3 MK2 (COM3) @9600

Under Devices and Printers -> Prusa i3 MK2, the port was set to 3dPrinterPort.13131... and I changed it to match my Device Manager's port for it at COM3. The FirmwareUpdater also is unable to connect, yielding the message

avrdude.exe: ser_open(): can't set buffers for "\\.\COM3" avrdude.exe: ser_drain(): read error: The handle is invalid. avrdude.exe: ser_send(): write error: sorry no info avail avrdude.exe: stk500_send(): failed to send command to serial port avrdude.exe: ser_recv(): read error: The handle is invalid. avrdude.exe: stk500v2_ReceiveMessage(): timeout avrdude.exe: ser_send(): write error: sorry no info avail avrdude.exe: stk500_send(): failed to send command to serial port avrdude.exe: ser_recv(): read error: The handle is invalid. avrdude.exe: stk500v2_ReceiveMessage(): timeout avrdude.exe: ser_send(): write error: sorry no info avail avrdude.exe: stk500_send(): failed to send command to serial port avrdude.exe: ser_recv(): read error: The handle is invalid. avrdude.exe: stk500v2_ReceiveMessage(): timeout avrdude.exe: ser_send(): write error: sorry no info avail avrdude.exe: stk500_send(): failed to send command to serial port avrdude.exe: ser_recv(): read error: The handle is invalid. avrdude.exe: stk500v2_ReceiveMessage(): timeout avrdude.exe: ser_send(): write error: sorry no info avail avrdude.exe: stk500_send(): failed to send command to serial port avrdude.exe: ser_recv(): read error: The handle is invalid. avrdude.exe: stk500v2_ReceiveMessage(): timeout avrdude.exe: ser_send(): write error: sorry no info avail avrdude.exe: stk500_send(): failed to send command to serial port avrdude.exe: ser_recv(): read error: The handle is invalid. avrdude.exe: stk500v2_ReceiveMessage(): timeout avrdude.exe: stk500v2_getsync(): timeout communicating with programmer avrdude.exe done. Thank you.

Any help/suggestions would be greatly appreciated,

Thanks!

Veröffentlicht : 28/04/2017 9:02 am
JoanTabb
(@joantabb)
Veteran Member Moderator
Re: Pronterface is unable to connect to Prusa i3 mk2

9600 seems awful slow, have you tried 115200 baud?

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Veröffentlicht : 28/04/2017 11:02 am
JeffJordan
(@jeffjordan)
Mitglied Moderator
Re: Pronterface is unable to connect to Prusa i3 mk2

the baudrate is defined inside the Configuration.h with a fixed value at 115200 bit/s #define BAUDRATE 115200.

dem inscheniör is' nix zu schwör...

Veröffentlicht : 28/04/2017 12:18 pm
Matt
 Matt
(@matt-22)
New Member
Themenstarter answered:
Re: Pronterface is unable to connect to Prusa i3 mk2

9600 seems awful slow, have you tried 115200 baud?

regards Joan

I've tried 115200 as well, no dice 🙁

Veröffentlicht : 29/04/2017 1:25 am
JoanTabb
(@joantabb)
Veteran Member Moderator
Re: Pronterface is unable to connect to Prusa i3 mk2

Are you sure that there is nothing else trying to use the com port....?
for example, if you have arduino IDE connected then you will be unable to connect pronterface as well.

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Veröffentlicht : 29/04/2017 1:36 pm
Matt
 Matt
(@matt-22)
New Member
Themenstarter answered:
Re: Pronterface is unable to connect to Prusa i3 mk2

Finally got it to connect!
It seems uninstalling/reinstalling the drivers + restarting my computer did the trick 🙂

Veröffentlicht : 01/05/2017 3:11 am
Teilen: