Has anyone gotten the filament runout sensor to work yet with the official marlin firmware??
It doesn't do anything when it triggers mid print and it causes octoprint to not want to print anything because it says the filament has ran out.
I saw some people having a lot more success with klipper. Is it worth it to switch? I've always used ultimakers (2, 2+, 3, 5) in the past (at work) and they required minimal maintenance so I am not super experienced.
I'm using the DSH with bimetal heatbreaks to fix the heat creep. I also adjusted the cooling fan so it doesn't blow against the heating block but against the nozzle.
I performed some troubleshooting on Marlin 2.0.9.3 DSH.
M119 returns the correct status for both filament sensors.
M412 returns host handling OFF as expected and Filament runout OFF
OK, that was likely because of filament runout being triggered at the beginning of the first few trials I did with the printer, I likely selected to disable the filament runout detection.
So I tried M412 S1 to activate the runout detection. It immediately triggered the runout procedure (M600 command if I'm not mistaken) despite the presence of filament and M119 reporting an open status.
My conclusion was a) either their is a bug in Marlin, or 2) the wiring of the filament sensors is done incorrectly. As I did not want to change the wiring, I tried to modified the Marlin configuration... and it worked :-)
In Configuration.h, change the following defined value from LOW to HIGH.
#define FIL_RUNOUT_STATE HIGH
Compile and upload the new firmware. It should now detect correctly filament runout events. Of course, this is just a workaround and not a clean fix as the M119 will now return a TRIGGERED status for the sensors in the presence of filament.
Let me know if you need more information.