Prusa i3 mk2 - 'machine does not support plaintext .gcode files'

[urbite]

For reference, I'm on a Win 7 Pro machine.

When I try and print directly from Simplify 3D to my Prusa i3 mk2, I get an error dialog box with the following message: "This machine does not support plaintext .gcode files"

I tried changing the format to binary, but still nothing was printed. The strange thing is that this has worked in the past. Here's what I know.

1. If I save the ascii/non-binary gcode file to disk, copy it onto an SD card, then put it in the Prusa I can print just fine from the Prusa LCD interface. So clearly the Prusa understands textfile gcode. I looked at the .gcode file in an editor and it is indeed plain text.

2. The Machine Control Panel connects to the Prusa, and the following connection dialog is observed using COM3

Attempting connection at \\.\COM3...
Testing plaintext communication protocol...
READ: G90
Testing binary communication protocol...
Connected to machine!
SENT: d501015e
READ: d501015e

3. If I look at my Ports in Device Manager, there IS NOT A COM3. But there is a COM80 listed with the following description [Original Prusa i3 MK2]. Oddly enough, even though THERE IS NO COM3 listed in Device Manager, COM3 is the only port that will result in a connection to the Prusa from Simplify3d.

Here's the Machine Control result when attempting to connect using COM80.

Attempting connection at \\.\COM80...
Testing plaintext communication protocol...
Testing binary communication protocol...
Testing alternate communication protocols...
Connection failed.

Either something is really flaky or I'm missing the obvious. Help, someone, so I don't have too keep up the SD card shuffle.

[S3D-Jake]

The printer speaks plaintext G-Code, as we have one in our office for testing. It appears from the READ: G90 that the communication is presenting with non-standard replies to standard G-Code commands. Have you tried walking through our guide to connecting to USB printers?

https://www.simplify3d.com/support/faq/#faq-4630

[urbite]

Found the problem, it was an ID10t issue. Baud rate was set to 250000 instead of 115200. Not sure how it changed, I thought in the past that this was persistent. Everything working as expected again after setting to 115200.

Found the answer here on Prusa message board.

https://shop.prusa3d.com/forum/others-a ... t4347.html

[DistractionMachine]

I'm having the same problem with a Makergear M2. I get eh error on both new and previously printed models, But I have COM3 and my baud rate is 115200