-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
Comments
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. |
check the runout setting, if set to HIGH/LOW set to opposite |
Mine is set to Motion.
…On Mon, Aug 14, 2023 at 6:39 PM Andrew ***@***.***> wrote:
check the runout setting, if set to HIGH/LOW set to opposite
—
Reply to this email directly, view it on GitHub
<#1025 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALW2LJZKY5X42EYGPW3HNUTXVKSKVANCNFSM6AAAAAA3QEHNCE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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? |
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. With the help of the end-stop diagnostic screen, set your |
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? |
I've the same issue in my Ender 3 S1. Going back to v20230522 solved the problem. |
Here: |
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. |
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 |
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. |
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. |
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. |
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. |
If it helps, I also had the same problem on my Ender 3 S1 with the latest version 20230805. |
Disabling runout in the menus did not work for me, but adding M412 S0 to my start code did |
After disable it in the menu you need to save settings. |
@ Belliqueu, As i read the code your M412 wont do anything?
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. |
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. |
Solved in the last version |
Thank you Miguel for all your hard work and all the improvements you've made with all these firmwares ! Much appreciated. |
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 |
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!
|
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. |
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
The text was updated successfully, but these errors were encountered: