[BUG] SKR 1.4 Filament Runout Sensor on Pins 1.26 & 1.25 don't work when printing. M600 is not executed.

[kkberg]

Bug Description

Both runout sensors are configured to pins 1.26 and 1.25 M119 shows correct working behavoir when Filament is in or out status changes between open and triggered correctly. M600 isn't executed.

My Configurations

Config.zip

Steps to Reproduce

1. try sensors with M119 when filament is in and out
2. start a print
3. simulate an empty filament spool

Expected behavior: I would expect running of M600 which is configured

Actual behavior: No reaction on missing filament M412 is activated

Additional Information

There is no sensorless homing and no diag pins

• Provide pictures or links to videos that clearly demonstrate the issue.
• See How Can I Contribute for additional guidelines.

[rhapsodyv]

Well.... I think we found the problem..

Marlin have an internal flag that indicate if a printing is active. That flag is set in the following conditions:

• start a print from SD
• start a print from LCD
• when PRINTJOB_TIMER_AUTOSTART is enabled and the gcode have one of the following commands: M104/M109/M190
• when PRINTCOUNTER is enable and marlin receive M75

You aren't doing anything of those options, so, for Malin, you didn't start a print...

It's very uncommon to not use M109. I think you should use it in our gcode and do another test.

[kkberg]

Okay, I'll try it again. Thank you.

[kkberg]

Changed gcode to M109 as it should be done usually, but M600 isn't performed!!! LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0 LESEN: TFilamentMonitor::run(): e: 0, !filament_ran_out: 1, printingIsActive: 1, did_pause_print: 0

[rhapsodyv]

e: 0, means the runout is disabled

[kkberg]

okay, but it is swiched on with M412 S1

; horizontalSizeCompensation,0

G90 M82 M412 S1 ;PetG ozeanblau Spectrum 0.40mm M106 S0; Luefter aus falls an ;G28

[kkberg]

Okay, you are right :). After the first filament change the sensor was switched off and I manually sent M412 S1 again and then I triggert a filament runout and I did what it should. I'm very sorry if I was the problem and making such a lot of work!

Thank you very much again

[kkberg]

Just a second please

[kkberg]

Okay, the runout thing is solved, but that the status of M412 is changed after performing the M600 is still there. Don't know if I have to open next issue or if it's wanted that the status of M412 is changed when having done the filament change. In the first image you see what apears when have to go on with printing. At first I have to confirm runout sensor and when I push the button M412 S0 happens, after that I have to confirm print again. That should be changed I think.

[kkberg]

Now all is solved and both sensors are working. Logic off sensor I had to change and pullups had to be commented, because pullup on both sensors. After that logic shows triggered when filament is in and open when out. This works perfectly for me. Thank you for all the help from the team.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.