Describe the bug
The filament runout sensor still doesn't do anything when it triggers while printing a model with Octoprint. Same as #739.
How to reproduce
Turn printer on
On the printer's menu, go to the load or change filament screen
Load the filament as per the prompts (note how the printer is able to tell there is no filament during loading, so the sensor works)
Once all loaded, connect octoprint
Start a print
Pull the filament out and hear the filament sensor trip/click
Observe the printer extruding air and happily carrying on printing despite the filament having run out
Note that on step 3, you can also "pretend load" by inserting the filament just past the sensor but not all the way into the extruder. This makes it easier and quicker to trip the sensor while printing as you can just yank the filament out of the sensor and is logically the same to the printer and the bug. It also saves on wasted filament because you're not physically extruding any during tests.
Also note that printing from USB and yanking the filament out does trigger the filament change sequence => filament sensor not defective.
Please don't label as "wontfix" because it's only occurring over serial. This printer was (and still is) marketed as a printfarm workhorse, not supporting the filament sensor (that Prusa charges extra for) while printing from serial makes this printer not suitable for the exact scenario it's being marketed for.
I have been able to reproduce both on 4.3.3 and 4.3.4.
Expected behavior
The filament runout sensor triggers a filament change operation on the printer.
Printer type MINI
Printer firmware version 4.3.3 and 4.3.4
Original or Custom firmware Original
Optional upgrades Filament Runout Sensor
USB drive or USB/Octoprint Octoprint
Describe the bug The filament runout sensor still doesn't do anything when it triggers while printing a model with Octoprint. Same as #739.
How to reproduce
Observe the printer extruding air and happily carrying on printing despite the filament having run out
Note that on step 3, you can also "pretend load" by inserting the filament just past the sensor but not all the way into the extruder. This makes it easier and quicker to trip the sensor while printing as you can just yank the filament out of the sensor and is logically the same to the printer and the bug. It also saves on wasted filament because you're not physically extruding any during tests.
Also note that printing from USB and yanking the filament out does trigger the filament change sequence => filament sensor not defective.
Please don't label as "wontfix" because it's only occurring over serial. This printer was (and still is) marketed as a printfarm workhorse, not supporting the filament sensor (that Prusa charges extra for) while printing from serial makes this printer not suitable for the exact scenario it's being marketed for.
I have been able to reproduce both on 4.3.3 and 4.3.4.
Expected behavior The filament runout sensor triggers a filament change operation on the printer.
G-code Any model does it.
Crash dump file N/A
Video N/A