-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] MK3S (3.13.3) stops mid print and reboots/resets itself #4630
Comments
This sounds very important. How far into the print does this happen? What Z height?
At that point the printer has already rebooted. |
Honestly I don't remember. But I narrowed down the problem. The following GCode
So it seems that having the raspberry pi zero W running prusa link connected causes the issue. For the record, my RPI Zero W is connected directly to the Einsy Rambo board (not via USB) as per this tutorial : https://help.prusa3d.com/guide/prusalink-and-prusa-connect-setup-mk3-s-_221744 |
I had my raspi soldered poorly. Printer did the same thing. If you want to be sure this is a hardware issue, send me please the syslog file from the settings page in PrusaLink local web interface |
I've had random rebooting during prints and also when doing an auto home. I was mostly trying to print lithos in pla. I've had lots of issues with this release. 3.13.3 revo version. |
Are you willing to check whether this is a hardware issue? (send the log, confirm you are using the pi on the einsy pins, jiggle it a bit to see if printer reboots) if you just pile on while not providing little to no info, we unfortunately cannot just snap our fingers and fix your issue magically. We'd like to, but real world is dissapointing like that |
Pi 3b connected to usb port on the board. Primarily printing through prusa connect or prusa slicer. |
I'm not at the machine at the moment. I'll try to get the log later on. |
I made a fresh install of PrusaLink on my raspberry pi zero W with another SD Card (I had no reason to suspect the sd card but I had to swap it so I took the opportunity to make a fresh install). |
I've had similar issues with 3.13.3 and 3.13.1 (backed out 3.13.3 to check). It doesn't always happen at the same place, although several times it seemed like it was close to the same place. Big print covering most of the plate, happened multiple times about 12mm height, then on 3.13.1 at maybe 2.5mm. Stock MK3S from kit, working several years, printing from SD card. Two slightly different .gcode files. Small prints (calibration cube, etc.) seem to work. Using 0.8mm nozzle. However... |
I checked all cables and wiggled them with the power on, with no effect. After doing more research I backed out to 3.12.2 and that solved the problem. I can provide the gcode that fails, but not the model or a .3mf file. |
I am also having the same issue on 3.13.3 Printer: MK3S+ I updated the firmware to 3.13.3 about a week ago which is when the failures started:
Troubleshooting steps attempted:
Final Resolution: Flashed back to 3.12.2, was able to print without issues. No matter the steps that occur that issue still persists in 3.13.3. I did attempt to roll back to 3.13.2 but, experienced the 'ghost layer shift' so I attempted to roll it forward again to 3.13.3. I experienced I believe about 10 failed prints, might be more I lost count. 80% of the prints were failing around the same time, then the others were also failing at the same time, just later in the gcode. When connected to PrintRun (Pronterface) I was able to see where it failed, and both times I had it connected it failed right after a WIPE was completed. Here are the lines of failure from PrintRun, along with the associated GCode from each file. PrintRun - 1:
GCODE:
PrintRun - 2:
GCODE:
gcode file (renamed to .txt to attach, rename to .gcode): |
We are currently experiencing similar issues at @HackerspaceWroclaw - two unrelated Prusa MK3S/+ printers seem to be randomly aborting prints.
|
@kosma Thanks for the bug report. but as your printers do not reset please open a new issue. |
Printer type - MK3S
Printer firmware version - 3.13.2 and 3.13.3 (I had the problem with both)
MMU upgrade - N/A
MMU upgrade firmware version - N/A
SD card or USB/Octoprint
Both SD card and Prusa Link (raspberry py zero W) version 0.7.2
Describe the bug
The printer resets/reboots itself during the print and display "Print aborted"
To Reproduce
thumb_bolt.stl
andthumb_nut.stl
from here : https://www.printables.com/fr/model/3407-articulating-raspberry-pi-camera-mount-for-prusa-m/filesExpected behavior
The printer prints all the objects without reseting / rebooting itself
G-code
Here are 2 gcodes that causes the problem with Prusa Link, but I tried similar configurations straight from the SD and I had the issue too.
bad_gcodes.zip
Video
/
The text was updated successfully, but these errors were encountered: