Octoprint stoping MK4
I have been using Octoprint for some time now on my mini, mk3s+, and mk4. I have raspberry pi 4b installed on all of them.
Recently my mk4 has been stoping in mid print and just sit there and do nothing. I have tried multiple things to get it going again with no luck. Doing a reset and start the print over is the only option I know. It appears that printing from the flash drive this does not happen. Anyone else having this issue?
I have also noticed that when filament runs out the printer keeps printing and does not ask for new filament. The filament sensor appears to be working fine as it detects it during load.
Hope I put this question in the correct location.
Thank you for the help!
RE: Octoprint stoping MK4
MK4 stopping: do you use (or try to use) OctoLapse? If yes, do you use the "Stabilization" feature? This does not work and can cause the printer to stop. Deactivate Stabilization and use "Smart Trigger - Snap to Print" instead.
Filament runout sensor on the MK4: does not work with OctoPrint because of lack of feedback from the printer to OctoPrint. Octoprint gets no information if the filament runs out and keeps spooling gcode data to the printer.
Apart from that I have been using OctoPrint with my MK4 just fine.
RE: Octoprint stoping MK4
I don’t use octolapse, it has the Timelapse on and I have started messing with that, but set it off and it still does it. If the network has glitches will that stop the print? I have been having some network issues lately.
MK4 stopping: do you use (or try to use) OctoLapse? If yes, do you use the "Stabilization" feature? This does not work and can cause the printer to stop. Deactivate Stabilization and use "Smart Trigger - Snap to Print" instead.
Filament runout sensor on the MK4: does not work with OctoPrint because of lack of feedback from the printer to OctoPrint. Octoprint gets no information if the filament runs out and keeps spooling gcode data to the printer.
Apart from that I have been using OctoPrint with my MK4 just fine.
RE: Octoprint stoping MK4
You mean WiFi? I have my Pi connected to Ethernet because it is more reliable than WiFi and the switch was already next to the printer.
No idea if the printer gets stopped because of bad WiFi. One would think WiFi quality should not matter after the gcode file has been transferred to the Pi. During the print job the only communication is via USB between the Pi and the printer. Did you check your USB cable? Can you perhaps try another one?
RE:
I don’t use octolapse, it has the Timelapse on and I have started messing with that, but set it off and it still does it. If the network has glitches will that stop the print? I have been having some network issues lately.
A network problem will not affect an active print from Octoprint. At that point, Octoprint has the entire file and is communicating it line-by-line to the printer, so only the pi-to-usb connection is involved. A problem with the cable (poor cable, poor connector, poor shielding, etc.) can cause issues.
Look at the octoprint.log file. A problem with the pi's power supply can cause all kinds of issues, but these will be recorded in the log. If you don't see any obvious errors there, enable Octoprint's serial logging before the next print. If the print stalls again, download the serial.log file from Octoprint and view the last portion to see what happened between Octoprint and the Printer.
The octoprint.log and serial.log files can be found in Octoprint at "Settings, Logging". The Serial log can be enabled at the bottom of the "Settings, Serial Connection" panel.
RE: Octoprint stoping MK4
I had a lot of random freezes as described when using the Input Shaper alpha firmwares with octoprint. No wifi, no timelapse running, just random full crash of the printer (nozzle and bed would remain heated, but all motion would stop, and the system is unresponsive). Running the exact same gcode would work just fine after a reset.
Updating to the latest 5.0.0-RC firmware has resolved all of the freezing issues for me. I would recommend updating to this if you haven't already.