Filament Run Out sensor not working

Artillery Genius' Pre-installed filament run out sensor is not stopping prints if the filament runs out

octoprint.log (3.4 MB)

Latest OctoPi version with Cancel objects and a TSD plugin running on an RPi2 with a PiCamera

I think it would help us if you upload a serial.log of the runout part.

Just start a print and cut your filament off after a few seconds. Stop the print after the sensor triggered and upload the serial.log.

Hi here is the serial log serial.log (888 Bytes)

You may have to activate the serial logging:

2020-04-11 13:18:29,236 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2020-04-11 15:03:45,347 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2020-04-11 15:22:19,578 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2020-04-11 15:22:33,659 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2020-04-11 15:24:16,474 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2020-04-11 19:03:44,381 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
1 Like

Here is the working logserial.log (691.8 KB)

Ok, so here the filament runout sensor is detected. Or did you manually paused the print?

2020-04-12 14:32:04,064 - Changing monitoring state from "Printing" to "Pausing"
2020-04-12 14:32:04,082 - Recv: ok
2020-04-12 14:32:04,195 - Recv:  T:252.27 /250.00 B:85.07 /85.00 @:62 B@:0
2020-04-12 14:32:04,364 - Send: N399882 M400*22
2020-04-12 14:32:04,448 - Recv: ok
2020-04-12 14:32:04,476 - Send: N399883 M114*23
2020-04-12 14:32:04,530 - Recv: X:196.54 Y:66.09 Z:20.50 E:16.02 Count X:15747 Y:5295 Z:8195
2020-04-12 14:32:04,786 - Recv: ok
2020-04-12 14:32:04,796 - Changing monitoring state from "Pausing" to "Paused"
2020-04-12 14:32:06,162 - Recv:  T:251.56 /250.00 B:84.96 /85.00 @:66 B@:5
2020-04-12 14:32:08,116 - Recv:  T:250.23 /250.00 B:85.03 /85.00 @:76 B@:0
2020-04-12 14:32:10,115 - Recv:  T:248.67 /250.00 B:85.17 /85.00 @:87 B@:100:

M400 finishes the last moves and M114 stores the actual position.

Depending what you have entered into the After a print job is paused script field, something should happen, or nothing. There also should be something in the field Before a print job is resumed.

You also may check it the sensor is proper connected to the printer board. Is the filament runout reported on the printer's LCD?

1 Like

@Ewald_Ikemann, I paused it manually there. The LCD does not say it is printing at all apart from the temperature changing, there is no print bar or anything so no the filament runout does not show, but it has done before so it must be OctoPrint. I am printing from the Pi not the SD if that affects anything

Referring to the serial log, there is no information from the printer to OctoPrint that a filament change is needed and therefore OctoPrint has to pause.
On the other hand, the serial log starts at line 393466, the change is that the runout occurred before. You may print a small piece and manually initiate a runout event (e.g. snipping the filament) for an updated serial.log.

1 Like

Here is an updated serial log where I did remove filament but the printed did not stop Link to serial.log https://drive.google.com/file/d/1MtLjDP2JQ0T-Use83PPpVFa3Gy5hDH07/view?usp=drivesdk

mine does not work on my ender 5 plus either. real pita because you have to disassemble the bowden tube to extract the piece of filament. not sure why creality or others add these if they dont work.

@jshutrump it worked sans octopi do must be something that octopi is not looking for

Don't get confused with OctoPi and OctoPrint. These are different things: What is the difference between OctoPrint and OctoPi? Are they the same thing?

Ok, to your serial log:

When start printing, this occurs:

2020-04-13 14:33:08,266 - Send: N1 M405*35
2020-04-13 14:33:08,277 - Recv: echo:Unknown command: "M405"

(M405: https://marlinfw.org/docs/gcode/M405.html)

You may use M412 instead: https://marlinfw.org/docs/gcode/M412.html

But first check it on the OctoPrint terminal to make sure the firmware knows it.

1 Like

The printer seemed to understand that terminal command so should i put that in the start gcode script on octoprint?

You put it there, where you put M405 before. Either OctoPrint or in the startcode of the slicer.

1 Like

@Ewald_Ikemann
Yeah, it still wont work, can Octoprint even detect serial messages from the printer?
Also the USB on my printer is not detected by octoprint, can i fix that?

That's the main thing octoprint does. Getting and sending messages via serial connection :slight_smile: