Comm error?
Hey all.
I'm trying to print a fairly complex and large model ("Faceless": http://www.3dprintmakers.com/collection/fantasygraph/item/faceless-v2 ) and twice now, at different points about 30 minutes into the print, the printhead stops. Checking the comm log I see this:
Send: N36756 G1 X153.629 Y108.187 E0.01659*101
Recv: ok
Send: N36757 G1 X153.691 Y108.247 E0.00231*99
Recv: ok
Send: N36758 G1 X153.872 Y108.362 E0.00577*108
Recv: ok
Send: N36759 G1 X153.836 Y108.590 E0.00620*103
Recv: ok
Send: N36760 G1 X154.268 Y108.158 E0.01641*109
Recv: Error:checksum mismatch, Last Line: 36758
Recv: Resend: 36759
Recv: Error:Line Number is not Last Line Number+1, Last Line: 36758
Recv: Resend: 36759
Communication timeout during an active resend, resending same line again to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N36758 G1 X153.872 Y108.362 E0.00577*108
Recv: Error:Line Number is not Last Line Number+1, Last Line: 36758
Recv: Resend: 36759
Communication timeout during an active resend, resending same line again to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
The printer never recovers and I lose all the material that has printed to that point.
Is this a problem with the model, with the print server (Octopi) or the printer?
#mikec
Re: Comm error?
There are known issues with the latest firmware and OctoPi.
Which firmware are you running?
Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage or loss. If you solve your problem, please post the solution…
Re: Comm error?
Same problem here!
My MK2S is running flawlessly with OctoPi 1.3.6 and FW 3.1.0.
However, my MM MK2S stops after a few dozens of layers, and I get the error seen above. Cannot print anything with it currently.
Ciao,
Martin
Re: Comm error?
You should check https://github.com/prusa3d/Prusa-Firmware/issues/331 and https://github.com/3d-gussner/Prusa-Firmware/releases
Re: Comm error?
Same problem here!
My MK2S is running flawlessly with OctoPi 1.3.6 and FW 3.1.0.
However, my MM MK2S stops after a few dozens of layers, and I get the error seen above. Cannot print anything with it currently.
Ciao,
Martin
If you don't want to use an unofficial firmware build just compile the MK2 firmware from official Prusa github for your MK2MMU, as said Prusa merged the M110 fix in December but never released an new firmware hex files since November.
Re: Comm error?
Same problem here!
My MK2S is running flawlessly with OctoPi 1.3.6 and FW 3.1.0.
However, my MM MK2S stops after a few dozens of layers, and I get the error seen above. Cannot print anything with it currently.
Ciao,
Martin
If you don't want to use an unofficial firmware build just compile the MK2 firmware from official Prusa github for your MK2MMU, as said Prusa merged the M110 fix in December but never released an new firmware hex files since November.
Even with the M110 fix - I downloaded from here:
https://github.com/thess/Prusa-Firmware/releases
It will seem to work for a while, but will eventually get the "printer reset detected." For me, that happens for prints >6 hours, which is very frustrating.
The solution is to print from the SD card, or roll back to an earlier version of the firmware.
Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage or loss. If you solve your problem, please post the solution…
Re: Comm error?
Same problem here!
My MK2S is running flawlessly with OctoPi 1.3.6 and FW 3.1.0.
However, my MM MK2S stops after a few dozens of layers, and I get the error seen above. Cannot print anything with it currently.
Ciao,
Martin
If you don't want to use an unofficial firmware build just compile the MK2 firmware from official Prusa github for your MK2MMU, as said Prusa merged the M110 fix in December but never released an new firmware hex files since November.
Even with the M110 fix - I downloaded from here:
https://github.com/thess/Prusa-Firmware/releases
It will seem to work for a while, but will eventually get the "printer reset detected." For me, that happens for prints >6 hours, which is very frustrating.
The solution is to print from the SD card, or roll back to an earlier version of the firmware.
Sorry to hear that...It fixed several issues but not yours. Let's hope Prusa will fix that soon. Thanks for the 1st negative feedback about this fix.