A new configuratiion of PrusaSlicer makes a problem with "FW crash detect!" error
Hi All,
I started to receive the "FW crash detected!..." error on all my three MK3S+ printers (firmware 3.14.1).
It looks like, it started to happen after the last configuration update for PrusaSlicer 2.9.4
When I start print a new .gcode file, printer beeps, restart, and after the restart the "FW crash detected!..." error appears on the printer screen.
The issue appears even for very small and simply file, like a small cube.
Old .gcode files (even big ones) generated a few months ago can be printed without issue.
I tested it on my 3 (!) MK3S+ printers with the same firmware - all the same result.
If I press the select button, the printer shows the main menu, and if I select an old .gcode file, the printer starts to print...
It looks like, all newly generated .gcode files from PrusaSlicer cause the error...
Anyone else, have similar issue ?
RE:
I recently rebuilt a mk3s+ and have only tried to print a file from the newer version of Prusa slicer, and have been constantly getting a Fw Crash and unable to continue print as well and have been beating my head against a wall trying to figure out what’s wrong, do you happen to have a smaller print older .gcode I could test to see if it fully prints without a crash?
RE: A new configuratiion of PrusaSlicer makes a problem with "FW crash detect!" error
After two weeks, the problem still persists... 😩
The new PrusaSlicer 2.9.5 did not change much, but after installation I managed to generate a printable file once!
Unfortunately, after a moment, the error started to appear again.
I restored factory defaults to one of my printers - no effects.
I switched to an old snapshot and I managed to print once again...!
After a while, the error appeared again.
On FB, I received suggestion that maybe a certain infill pattern can create the issue....
So, I tested several prints of the same model and yes, sometimes the generated gcode file was OK.
Sometimes the change of infill pattern yielded good result, and sometimes it was changing number of peripheral lines (from 4 to 5) that caused the issue...
So now, I am really confused...