Prusa-firmware: MK3 3.5.0 Randomly stops printing without any reported error

[jonnieZG]

MK3 with 3.5.0, happened a few times after the fw upgrade that the printer just stops mid print, or at the very beginning during intro-line, without any error being reported on the display. The printer remains stuck until a manual reset is performed. Printing PLA, enclosure in a cold environment, temp inside enclosure 18°C.

Head and bed temperatures remain at the set temperature 215/60°C.

If it is a temperature-related issue (which is likely), or any other issue,, then at least there should be a message shown on the display.

_PLEASE NOTE_ that this is not the same as the issue when a printer randomly makes long pauses during a print, but resumes on its own after a while (after a few seconds or a minute).

[MimbaMonkeyHouse]

Same issue here

[GWdd]

Same here --- in my case printer is working normally at 0.150, and 0.200 layers, but was doing this "pause" every once in a while when building a 0.100 layer part. There were overhangs and bridges that may have been involved. It could be as simple as an oddball Slic3r setting, but that doesn't explain the printer moving along, and just stopping -- no head movement up, sideways, etc. Just extrudes to a point and sits there. Then a minute later it starts going again. Print finishes as expected.

I do have a .gcode from the event.

part_pauses_during_print.zip

Mk3 - 3.5.0 fw - filament sensor disabled

[jonnieZG]

Just extrudes to a point and sits there. Then a minute later it starts going again. Print finishes as expected.

Please beware that the situation you are describing is not the same issue that I reported. In my case the print does not resume -- the head sits in a place until I reset the printer. Yesterday it just sat in the middle of the intro-line for 9+ hours until I came back home from work and did a reset.

[ChrisVahi]

Your g code has a lot of changes to acceleration and jerk settings. Are these your settings or did Prusa as a bunch of noise to the start code? If they are your changes then this may be the problem.

Acceleration values have to be processed by the firmware before moves can be made. If resulting values exceed the limit for the variable type (eg. >255 for a byte) then the firmware hangs and your print is lost. Try setting your acceleration in eeprom (Google Marlin eeprom acceleration) and reset your print acceleration values in Slic3r to default. I've also seen linear advance (found in filament custom g code tab) cause hangups when values get too high.

[GWdd]

The code was generated by Slic3r PE, though I have rearranged the Start-Up gcode segment to reduce ooze during bed level calibration (initial nozzle temp at 175 rather than 215). And I didn't post-process the gcode.

If I did anything else, it was only via menus for overhang (slower print speeds) or fill (limiting speed of infill). I was having issues getting a couple small 0.2mm gaps to print correctly.

[jonnieZG]

Guys, please don't hijack this thread, since it has nothing to do with the topic in the subject. You can open a new issue for that, or look into already existing ones that are addressing the situation that GWdd is describing.

If this was a gcode-related problem, than the same gcode would not work fine after a reset, nor would remain stuck until a reset, which does in the case that I am referring to.

[GWdd]

If you suspect the FW, then down-rev to 3.4 and provide assistance to the developers by demonstrating it is 3.5 that is causing your issue. Then provide some evidence the problem is unrelated to something in your own gcode - like an example of the problem happening on a common debug print like Benchy..

[blgli]

I am having the same problem with 3.5.0 on my MK3

I print with ABS and the printer in an enclosure. There's really no rhyme or reason why this happens. Just happened about 3 hours into 8 hour print. Print head just stopped where it was at, heaters for both the bed and hotend were turned off, screen had no errors what so ever on it. It does not happen at the same spot on print, its sporadic where it decides to stop. I've noticed a power cycle of the machine "usually" fixes this until it happens on another print. This has happened to me on numerous occasions after switching to 3.5.0 and I've had enough. Until something can be done to remedy this I will go back to older firmware.