#5M Pro (Klipper + KlipperScreen) keeps pausing uncommanded mid-print

1 messages · Page 1 of 1 (latest)

civic imp
#

My 5M Pro (running Klipper w/ KlipperScreen) keeps stopping prints mid-way and throwing "SET_FILAMENT_SENSOR SENSOR=runout_sensor ENABLE=1" but ONLY in the console access using the printer's LED (it doesn't show at all using the web GUI). Running exactly what it says does nothing. I can try to hit resume, but the only thing that happens is speed data reappears and the GUI console spits "Print is not paused, resume aborted" when it clearly IS paused (the button on the LCD even reads "Resume"). I'm getting very fustrated at this and might just abandon Klipper altogether if it keeps acting up like this. The stock Flashforge software didn't have any issues like this.

astral harborBOT
#
AI Help

It sounds like there may be a configuration issue with the filament sensor setting in your Klipper configuration file. I recommend double-checking your settings to ensure they are correct. You may also want to reach out to the Klipper support community for further assistance troubleshooting this issue. Abandoning Klipper altogether may not be necessary if the issue can be resolved through proper configuration and troubleshooting.

WARNING: This response is AI generated and may contain errors.
civic imp
#

Turned the sensor off. Now, it doesn't throw that but it STILL stops mid-print, this time with nothing at all in console. Grr...

rapid ember
#

You can post your klipper log here. Otherwise people can only guess whats wrong.

civic imp
#

I came across this whilst looking through it myself:

virtual_sdcard read
Traceback (most recent call last):
  File "/root/printer_software/klipper/klippy/extras/virtual_sdcard.py", line 237, in work_handler
    data = self.current_file.read(8192)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xad in position 7420: invalid start byte
Exiting SD card print (position 49152)

It's odd because that line in the GCODE file is a simple G1 command:
G1 X3.925 Y18.031 Z.6

rapid ember
#

gcode file would be at position 49152

#

As far as I understand

civic imp
#

GCODE file is only 24475 lines long

lucid merlin
#

position as in byte not line

civic imp
#

Using Notepad++, going to offset 49152 brings me to line 2013, which reads
G1 E-.8 F2100

#

If it helps, I noticed this in the klipper.log file not far before the virtual sd card error:

Lines 60711 and 60712:
TMC 'stepper_z' reports GSTAT: 00000001 reset=1(Reset) TMC 'stepper_z' reports GSTAT: 00000000
When that happens, a setting called "print_stall" gets set to 1 in the list of variables it spits out.

civic imp
#

Turns out it was due to having "Arc Fitting" enabled in OrcaSlicer which somehow caused a data overload when sending the file over.

#

?solved