Unable to cancel print on printer when filament runout sensor trigger

[lin-ycv]

Describe the bug When filament runout sensor is triggered, there's no way to cancel the print, the only option is to load filament, but sometimes there's other problems that needs to be solved, so it'd be nice if there was a cancel print option when the sensor is triggered.

To Reproduce Steps to reproduce the behavior:

1. start a print without filament loaded
2. sensor triggered after start gcode
3. unable to cancel print from printer other than power off

Expected behavior an option to disable filament sensor when triggered, or to cancel the print.

Screenshots If applicable, add screenshots to help explain your problem.

Version (please complete the following information): Ender3V2-422-BLTUBL-20221002.bin

Additional context Add any other context about the problem here.

[mriscoc]

The latest version has a Runout sensor enable/disable menu item in the tune menu

[mriscoc]

If the M600 process (change filament) is already ongoing there is no option to cancel the print in the middle of it. I will reopen this issue for future research.

  // Commands to execute on filament runout.
  // With multiple runout sensors use the %c placeholder for the current tool in commands (e.g., "M600 T%c")
  // NOTE: After 'M412 H1' the host handles filament runout and this script does not apply.
  #define FILAMENT_RUNOUT_SCRIPT "M600"

Maybe a first dialog to select cancel or start an M600 could be better but Marlin expects simple G-code here.

[RaffaeleO]

Ender 3 V2 Neo, estrusore creality Sprite Pro e firmware [Ender3V2-422-BLTUBL-MPC-20221222.bin]. Il sensore viene rilevato senza alcun problema e viene visualizzato anche nel monitore della stampante. Il grosso problema è che nonostante venga rilevata la rottura o esaurimento filamento, la stampa non va in pausa. continua a stampare senza filamento. Il firmware sarebbe il top se si risolvesse questo Bug e il bug del ripristino stampa dopo interruzione corrente. Grazie

[RaffaeleO]

Ender 3 V2 Neo, creality Sprite Pro extruder and firmware [Ender3V2-422-BLTUBL-MPC-20221222.bin]. The sensor is detected without any problems and is also displayed in the printer monitor. The big problem is that although the filament breakage or runout is detected, the print does not pause. continue printing without filament. Firmware would be top if this bug and print restore after power outage bug were fixed. Thank you

[mriscoc]

Ender 3 V2 Neo, creality Sprite Pro extruder and firmware [Ender3V2-422-BLTUBL-MPC-20221222.bin]. The sensor is detected without any problems and is also displayed in the printer monitor. The big problem is that although the filament breakage or runout is detected, the print does not pause. continue printing without filament.

Reduce the filament runout distance in filament settings menu.

[RaffaeleO]

Thank you for your kind reply, but unfortunately even if I reduce the distance to 1 mm unfortunately the print does not pause. I also take this opportunity to confirm that in the event of a blackout, printing restarts from home and not from where it left off. I can not solve even interacting on file configuration.h Could you give me some advice for both problems? Thanks and sorry to bother you

Il giorno dom 8 gen 2023 alle ore 01:07 Miguel Risco-Castillo < @.***> ha scritto:

Ender 3 V2 Neo, creality Sprite Pro extruder and firmware [Ender3V2-422-BLTUBL-MPC-20221222.bin]. The sensor is detected without any problems and is also displayed in the printer monitor. The big problem is that although the filament breakage or runout is detected, the print does not pause. continue printing without filament.

Reduce the filament runout distance in filament settings menu.

— Reply to this email directly, view it on GitHub https://github.com/mriscoc/Ender3V2S1/issues/507#issuecomment-1374662703, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4UGSJIJA6BIC56FMEVA6S3WRIANZANCNFSM6AAAAAASEC5OUY . You are receiving this because you commented.Message ID: @.***>

-- Raffaele Ommeniello

[mriscoc]

but unfortunately even if I reduce the distance to 1 mm unfortunately the print does not pause.

In Advanced / Runout diagnostic you can debug your filament sensor. See about filament settings menu in the Wiki.

[RaffaeleO]

Hello Miguel, meanwhile thank you for your availability, filament sensor problem solved, I was a defect of the sensor hardware and not of your professional firmware. What remained a big problem is the resumption of printing after the power outage, unfortunately when printing resumes after several nozzle cleanings it starts from home, in fact I risked 3 times (making attempts) to break holden. There is probably some bad code in the gcode. I also tried to check the file with visual studio code but I can't find the dedicated section. Thanks in advance for the help. Raffaele Ommeniello (Italy)

Il giorno lun 23 gen 2023 alle ore 01:41 Miguel Risco-Castillo < @.***> ha scritto:

but unfortunately even if I reduce the distance to 1 mm unfortunately the print does not pause.

In Advanced / Runout diagnostic you can debug your filament sensor. See about filament settings menu in the Wiki.

— Reply to this email directly, view it on GitHub https://github.com/mriscoc/Ender3V2S1/issues/507#issuecomment-1399660526, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4UGSJJERL7RQHIDZBV7IQLWTXHUXANCNFSM6AAAAAASEC5OUY . You are receiving this because you commented.Message ID: @.***>

-- Raffaele Ommeniello

[github-actions[bot]]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[RaffaeleO]

With the latest firmware everything goes perfectly, no problems encounteredInviato dal mio Galaxy -------- Messaggio originale --------Da: "github-actions[bot]" @.> Data: 23/04/23 04:24 (GMT+01:00) A: mriscoc/Ender3V2S1 @.> Cc: RaffaeleO @.>, Comment @.> Oggetto: Re: [mriscoc/Ender3V2S1] Unable to cancel print on printer when filament runout sensor trigger (Issue #507) This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[github-actions[bot]]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[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.