Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Filament Runout Sensor is enabled in MOTION by default and trigger an Advanced Pause #1025

Closed
hagenman opened this issue Aug 14, 2023 · 26 comments
Labels
bug: Confirmed Something isn't working, the bug was confirmed.

Comments

@hagenman
Copy link

hagenman commented Aug 14, 2023

HOW TO SOLVE:

If you don't have an smart filament sensor (as BTT) set the filament active state to HIGH or LOW: #1025 (comment)


Did you test with a precompiled firmware?

Yes, and the problem still exists.

Bug Description

After upgrading, prints will run for a bit, then the runout sensor will trigger (i think?) and it will go to the purging screen. I tell it to continue then it will for a little while before the issue occurs again. Also, the estimate time just keeps climbing until the sensor triggers again.

Bug Timeline

No response

Expected behavior

I expected prints to continue like they did on your previous firmware

Actual behavior

After upgrading, prints will run for a bit, then the runout sensor will trigger (i think?) and it will go to the purging screen. I tell it to continue then it will for a little while before the issue occurs again. Also, the estimate time just keeps climbing until the sensor triggers again.

Steps to Reproduce

No response

Version of Professional Firmware

20230810-11:42

Printer model

Ender 3 S1 F4

Electronics

No response

Add-ons

No response

Bed Leveling

UBL Bilinear mesh

Your Slicer

Prusa Slicer

Host Software

SD Card (headless)

Additional information & file uploads

No response

@anoblet
Copy link

anoblet commented Aug 14, 2023

I'm having a similar issue. My prints will hit the runout screen, although there's still plenty of filament running through the sensor. Afterwards the filament breaks since it stays in the hotend heating.

@classicrocker883
Copy link

check the runout setting, if set to HIGH/LOW set to opposite

@hagenman
Copy link
Author

hagenman commented Aug 14, 2023 via email

@lam522008
Copy link

I am also having this issue on my Ender 3 v2, not sure what to do unable to print anything without it purging and spitting out the filament for no apparent reason. Any solutions?

@mriscoc mriscoc changed the title [BUG] (Keeps going to Runout Senor purging screen) [BUG] Filament Runout Sensor is enabled by default and trigger an Advanced Pause Aug 15, 2023
@mriscoc
Copy link
Owner

mriscoc commented Aug 15, 2023

Seems that the configuration files sets by mistake the filament run-out sensor in the MOTION active state, that is wrong if you don't have an smart filament sensor. Check your filament runout sensor settings: https://github.com/mriscoc/Ender3V2S1/wiki/Filament-Settings-Menu#run-out-sensor

Don't forget to store settings after the changes.

filament-settings1

With the help of the end-stop diagnostic screen, set your Runout Active to HIGH or LOW so that if there is filament in the sensor, it will indicate TRIGGERED. If you have the Ender 3 S1 and the stock filament runout sensor, go to Advanced / Filament settings menu and set Runout Active to HIGH, if you have a Ender 3 V2 without runout sensor, disabled it.

@lam522008
Copy link

Thank you that did help! I don't have errors but can't seem to print anything more than 20 minutes without it messing up. Any solutions?

@mriscoc mriscoc changed the title [BUG] Filament Runout Sensor is enabled by default and trigger an Advanced Pause [BUG] Filament Runout Sensor is enabled in MOTION by default and trigger an Advanced Pause Aug 15, 2023
@mriscoc mriscoc added the bug: Confirmed Something isn't working, the bug was confirmed. label Aug 15, 2023
@mriscoc mriscoc pinned this issue Aug 15, 2023
@monkiki
Copy link

monkiki commented Aug 15, 2023

I've the same issue in my Ender 3 S1. Going back to v20230522 solved the problem.

@Ollipop030
Copy link

How did you go back to that Version?

Here:
https://github.com/mriscoc/Ender3V2S1/releases/tag/20230522

@Ollipop030
Copy link

If you have the Ender 3 S1 and the stock filament runout sensor, go to Advanced / Filament settings menu and set Runout Active to HIGH

Doesn´t work for me. I´ve testet high/low, the printer stops every few minutes. Sometimes it doesn´t even finish the first layer. Only option for me is to disable the sensor. With May firmware it works fine.

@gitfve
Copy link

gitfve commented Aug 17, 2023

Is this a problem in the Ender3 S1 PRO too?

I dont know about any BTT sensor on my Ender3 S1 PRO, it is the stock filament sensor.

I use this one without any problem Ender3S1-F4-UBL-20230312.bin

@NetCaptive
Copy link

Setting "Enable Runout" to "off" solved this problem for me on my Ender 3v2 with BLTouch. My "Runout Active" setting was "Motion" and I left that unchanged.

@andrenalin282
Copy link

Same problem for me Ender 3V2, high, low, runout deactivation, nothing works, plugged off the cable works for me, i wait for the fix.

@mriscoc
Copy link
Owner

mriscoc commented Aug 21, 2023

Same problem for me Ender 3V2, high, low, runout deactivation, nothing works, plugged off the cable works for me, i wait for the fix.

The problem was only with the default value of Runout active, deactivating or set it properly and then save settings, should solve the issue.

@RejZoRSheep
Copy link

Jesus, wasted almost 1 hour trying to figure out the problem, then finally come here and see it's not just me. The buggy update with invisible toolbar didn't cause me any problems, updated to latest fixed version and haven't printed anything then. Tried now and kept pausing even though I just put new 1KG spool on it.

@plastisizer
Copy link

plastisizer commented Aug 25, 2023

Had the same issue with the Advaced pause, turned off the runout detector and now was able to move past that point. I was then able to start the print, but the extruder was not pushing any filament. I rebooted and was able to restart the print without issues.

@Crapoulos
Copy link

If it helps, I also had the same problem on my Ender 3 S1 with the latest version 20230805.
When I re-installed version v20230522 it solved the problem.
I tested version 20230805 again and the problem returned. Runout sensor comes back every 4mn or so. Not yet tested the suggestion "set your Runout Active to HIGH or LOW".

@mriscoc
Copy link
Owner

mriscoc commented Aug 30, 2023

Not yet tested the suggestion "set your Runout Active to HIGH or LOW".

Step 4 of the Calibration guides, a must-read for anyone trying to install this firmware.

image

@Belliqueu
Copy link

Disabling runout in the menus did not work for me, but adding M412 S0 to my start code did

@mriscoc
Copy link
Owner

mriscoc commented Aug 30, 2023

After disable it in the menu you need to save settings.

@gitfve
Copy link

gitfve commented Aug 31, 2023

@ Belliqueu, As i read the code your M412 wont do anything?
From the code:

#if ENABLED(FILAMENT_RUNOUT_SENSOR)
  #define FIL_RUNOUT_ENABLED_DEFAULT true // **Enable the sensor on startup. Override with M412 followed by M500.**

There are so many reports on the RunOutSensor. I do not understand why this version is not disabled, and a new is released. I can see the developer have solved it in the source code, but no new .bin file is released. I think it will be a help to many users if new bin was released.

@Rippeee
Copy link

Rippeee commented Aug 31, 2023

For those who are having issues with BTT sensor triggering every 30sec, I think I found the solution. I'm not using any custom configs or G-godes. I'm using the latest mriscoc firmware with BTT sensor, Mode set as motion. The recommended Distance for BTT is 7 mm, and that doesn't work, unless your sensor is literally Next to the extruder. I would recommend to set it to 14 mm, if that doesn't work, try 20,30,40,50 etc. In my case, I'm running Sprite pro Direct drive upgrade kit, and I'm mounting the sensor at the top, next to the filament spool. For that reason, there is a lot of ''slag'' between the extruder and the sensor, so there will be moments when the filament ain't moving at all. 7 mm would never work in my case and in my case it doesn't really matter even if the distance is 100 mm because once the filament is out of sensor, there is still like 20CM of filament going in the extruder. In a Nutshell the solution is Crank up your distance from 7 to 8,9,10,11,12,13,14,15,16… etc. Until it works.

@mriscoc
Copy link
Owner

mriscoc commented Sep 6, 2023

Solved in the last version

@mriscoc mriscoc closed this as completed Sep 6, 2023
@Crapoulos
Copy link

Thank you Miguel for all your hard work and all the improvements you've made with all these firmwares ! Much appreciated.

@Rippeee
Copy link

Rippeee commented Sep 9, 2023

Little of the topic but if some of you're running BTT Smart filament sensor with a Sprite extruder and Looking for a mounting system that allows to have that 7 mm Run out distance, and actually WORK

You are welcome… https://www.thingiverse.com/thing:6209226

@zfkdnop
Copy link

zfkdnop commented Oct 23, 2023

EDIT: Disregard. The issue was caused by my own configuration edits. My apologies. And thank you Miguel for your hard work. This firmware is EXCELLENT!

Solved in the last version

Now I can't compile:

In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/HAL_SPI.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
Compiling .pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_wired.cpp.o
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/HAL.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
Compiling .pio/build/STM32F103RC_creality/src/src/HAL/STM32/fast_pwm.cpp.o
Compiling .pio/build/STM32F103RC_creality/src/src/HAL/STM32/fastio.cpp.o
Compiling .pio/build/STM32F103RC_creality/src/src/HAL/STM32/msc_sd.cpp.o
Compiling .pio/build/STM32F103RC_creality/src/src/HAL/STM32/sdio.cpp.o
Compiling .pio/build/STM32F103RC_creality/src/src/HAL/STM32/timers.cpp.o
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/MarlinSerial.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/HAL_SPI.cpp.o] Error 1
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/fastio.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/Servo.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/eeprom_bl24cxx.cpp:32:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/eeprom_sdcard.cpp:31:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/eeprom_if_iic.cpp:32:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/eeprom_flash.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/eeprom_sram.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/eeprom_wired.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/fast_pwm.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/HAL.cpp.o] Error 1
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/sdio.cpp:27:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/MarlinSerial.cpp.o] Error 1
In file included from Marlin/src/HAL/STM32/../../inc/MarlinConfig.h:52,
                 from Marlin/src/HAL/STM32/timers.cpp:26:
Marlin/src/HAL/STM32/../../inc/SanityCheck.h:2753:6: error: #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
 2753 |     #error "RUNOUT_TUNE_ITEM requires HAS_FILAMENT_SENSOR."
      |      ^~~~~
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/fastio.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_sdcard.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_if_iic.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_wired.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_sram.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/Servo.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_flash.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/eeprom_bl24cxx.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/fast_pwm.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/sdio.cpp.o] Error 1
*** [.pio/build/STM32F103RC_creality/src/src/HAL/STM32/timers.cpp.o] Error 1

And if I remove RUNOUT_TUNE_ITEM, there are further errors which are to complex for me to resolve by simply removing configuration lines:

Marlin/src/lcd/marlinui.cpp: In static member function 'static void MarlinUI::media_changed(uint8_t, uint8_t)':
Marlin/src/lcd/marlinui.cpp:1813:11: error: 'clear_menu_history' was not declared in this scope
 1813 |           clear_menu_history();
      |           ^~~~~~~~~~~~~~~~~~
In file included from Marlin/src/lcd/../inc/MarlinConfigPre.h:37,
                 from Marlin/src/lcd/../inc/MarlinConfig.h:28,
                 from Marlin/src/lcd/marlinui.cpp:23:
Marlin/src/lcd/marlinui.h:255:91: error: 'menu_media' was not declared in this scope
  255 |     #define MEDIA_MENU_GATEWAY TERN(PASSWORD_ON_SD_PRINT_MENU, password.media_gatekeeper, menu_media)
      |                                                                                           ^~~~~~~~~~
Marlin/src/lcd/../inc/../core/macros.h:609:26: note: in definition of macro 'THIRD'
  609 | #define THIRD(a,b,c,...) c
      |                          ^
Marlin/src/lcd/../inc/../core/macros.h:206:29: note: in expansion of macro '___TERN'
  206 | #define __TERN(T,V...)      ___TERN(_CAT(_NO,T),V)  // Prepend '_NO' to get '_NOT_0' or '_NOT_1'
      |                             ^~~~~~~
Marlin/src/lcd/../inc/../core/macros.h:205:29: note: in expansion of macro '__TERN'
  205 | #define _TERN(E,V...)       __TERN(_CAT(T_,E),V)    // Prepend 'T_' to get 'T_0' or 'T_1'
      |                             ^~~~~~
Marlin/src/lcd/../inc/../core/macros.h:201:29: note: in expansion of macro '_TERN'
  201 | #define TERN(O,A,B)         _TERN(_ENA_1(O),B,A)    // OPTION ? 'A' : 'B'
      |                             ^~~~~
Marlin/src/lcd/marlinui.h:255:32: note: in expansion of macro 'TERN'
  255 |     #define MEDIA_MENU_GATEWAY TERN(PASSWORD_ON_SD_PRINT_MENU, password.media_gatekeeper, menu_media)
      |                                ^~~~
Marlin/src/lcd/marlinui.cpp:1815:23: note: in expansion of macro 'MEDIA_MENU_GATEWAY'
 1815 |           goto_screen(MEDIA_MENU_GATEWAY);
      |                       ^~~~~~~~~~~~~~~~~~
Marlin/src/lcd/marlinui.cpp:1815:11: error: 'goto_screen' was not declared in this scope
 1815 |           goto_screen(MEDIA_MENU_GATEWAY);
      |           ^~~~~~~~~~~
Compiling .pio/build/STM32F103RC_creality/src/src/libs/numtostr.cpp.o
*** [.pio/build/STM32F103RC_creality/src/src/lcd/marlinui.cpp.o] Error 1

@mriscoc mriscoc unpinned this issue Nov 6, 2023
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug: Confirmed Something isn't working, the bug was confirmed.
Projects
None yet
Development

No branches or pull requests