[BFW-5545] [BUG] MK4 keeps requesting filament path to be cleared upon empty spool change #3129
Comments
bolsoncerrado
changed the title
|
+1 But after the last time the restart didn't help, sensor calibration also shows always "NO". I need to push the filament to the left, but after that the calibration failed. After a little test print I retried with success. ¯_(ツ)_/¯ I'm wondering if it's a firmware bug or a hardware problem or both... |
|
@marcelismus what fw version did u have issues with? mine is 4.6.1 -- i'll install alpha3 now. |
|
I am having the same issue with 4.7.1 firmware - goes to park position, unloads and shows confirm screen (selected "yes") but still shows to clear the path |
|
Made a test with colorchange today and there the filament change worked - don't know what the difference between both cases (color change <-> filament runout) internally is |
|
Idk either but I lost another print today again, pretty frustrating. |
|
@bolsoncerrado are you on alpha3 now or still on 4.6.1? |
|
Now on 4.7 |
|
Confirmed issue on 4.7.1, however I did get it to clear after inserting and removing filament quickly a few times. Before doing so, verified there was no filament in the idler area. New MK4 build, third print. |
|
I tried that technique and it didnt work for me :( |
|
I would consider this a rather serious issue. Have Prusa responded? |
|
No :( |
|
It happened to me as well twice. I realized the filament sensor is not calibrated for me and will always register as a detected filament. Temp Fix: The only way to fix this is to do a control > filament sensor calibration. Proposed Fix: There should have been a way to overwrite the sensor during such an issue. |
|
Firmware 4.7.2 got released. Has anyone already tested, if it is fixed? Release note does not mention anything related. |
|
Why would they? No one from Prusa ever commented here :( |
|
Same issue on v5.0.0-alpha4. Stuck on requesting filament path to be cleared. |
|
same here on 5.0.0-alpha4. pushing in and pulling out a piece of filament multiple times worked in some cases. had it 8 times in 2 weeks. also on 5.0.0-alpha1..3. that really tends to ruin your print if you want to empty a spool completely before switching to a new one. |
|
Happens also if you plan to leave and don't trust enough on the filament sensor stopping the print while away if spool dries out, hence if you manually opt to change filament manually, sensor may ruin the print awaiting you remove the filament you've already acknowledged to have removed correctly. Pretty absurd altogheter. |
|
Just wanted to comment that this is easily duplicated with a filament change from the printer menu as well. Even after you confirm the filament is removed (yes on the prompt), you have to toggle the filament in and out for the printer to recognize nothing is loaded. |
|
What I just said yep. |
|
Had the same odd behaviour today. Would be nice if Prusa can response if this is a software or hardware bug. For me it cleared after putting the filament in and out multiple times |
|
SOunds to me they have a severe hardware design issue with this filament sensor placement :( This radio silence is nothing but worrysome! I also wonder if XL people is having the same issue... EDIT: Apparently, they're: https://www.facebook.com/groups/Prusai3users/posts/2417025891815211/ |
|
I think the problem is that the sensor is blocked by fine strings of unloaded filament. It often works if you put filament in and out many times or print a little longer. Whether design flaw (and as far as I know, the sensor cannot be reached "just like that") or just too sensitive, no idea. But a "No filament loaded" button is necessary. |
|
Well it's quite absurd the screen asks you "was the filament removed correctly?" just to ask you again to please remove the filament from the sensor path when you can't clearly reach it AND no other option (specially mid print) left than pray that wiggling multiple times the new filament will trigger the sensor :( So I think it's both a hardware design flaw (like having a hole that gravity will end up filling with dust and such anyway) and a firmware issue... |
|
+1 on this. It just happened to me when I runed out of filament. Wasted 24h of print.... |
|
I had this happen a few times and could fix it by sticking the filament in and pulling out again a few times. It seems the hall sensor does not spring back, you can notice that there is no resistance when doing the above. At least that's what I think is happening. |
|
In the Podcast they just mentioned that new final firmware with input shaping will be released (around) Friday - let's see if this included |
|
I just had this issue on 5.0.0-RC. The ball didn't spring back, there was no resistance. Inserting and pulling out a looot of times very rapidly finally made it spring back, resistance was there and the printer started detecting filament correctly. |
|
I think all these posts prove they have a serious hw design issue... |
danopernis
added
the
UI
|
I love my Prusa MK4, I plan to buy an XL, and I want to love Prusa as a company, but this issue makes me doubt the competence of people answering here. What I am going to write will most likely be considered by some as rude and unprofessional, so I say upfront that I don't want to hurt or target anyone, I want Prusa to improve.
|
|
A-Men! |
|
"Disconnecting components while the printer is powered on is something you should really avoid. Not to mention that this workaround would most likely only postpone the problem."
But if you gave us an "ignore and continue" button, as @miyconst suggest, we could finish the print after the spool ran out on a long print. I believe that none of us have proposed this change to do 20+ filament changes. Most of us would have liked to have this option to use once to complete a long print after a spool of filament ran out. It is not even always true that it postpones a problem. As many of us said, there was nothing in the way of the filament and, after resetting the machine, the filament sensor would no longer "see" a filament (or debris). |
CZDanol
changed the title
CZDanol
removed
in progress
unable to reproduce
|
+1 I'm facing the same problem with the new MMU3 and the newer idler filament sensor. A 2-hour, single filament print stopped five times. I need to click continue after it ejects the filament, and it will reload it and continue printing. Annoying. I need to be there to click a button. Now, I will need to wake up at night hourly to see if I need to click the button. LOL |
|
My Prusa Mk4 arrived a few hours ago, set it up, got it working, decided to simulate an out of filament issue and I have the same sodding problem as everybody else. If I push an old piece of filament in 5-10x, it appears to work. So I can safely say that Prusa has not quietly fixed the hardware problem or used software to fix it. This thread started 11 months ago and we still have it on brand new printers. Mine is three hours old. I've just brought a brand new printer that is not as good as my old Mk3 that it replaces and was going to be given to the local school. I am furious that this major issue has not been fixed. I'm contacting Prusa to send it back, its not fit for purpose. Rob |
|
I'd really like to see Prusa staff to come here one last time and repeat, after this last evidence, that it's filament debris the ONLY issue this filament sensor has... As the saying goes... "There's none so blind as he who will not see." Geez. |
|
I've just cut the filament to see what happens. Filament unloaded OK, this time it did load but I had to reload it to get it to work. it put up the message "Ramming" on the screen. I pushed a little harder and it worked. So lets do another one and see what happens. This is on a printer that has less than two hours usage from coming out the box. The last two have worked OK, lets keep doing it and see. Rob |
I never cut the filament. In my case I just click continue and it will reload and continue to print. No interaction with the printer. I will try to calibrate the finda better. This never happened with mk4 alone. It started after the MMU3. |
|
The filament sensor just failed to recognise it was out of filament. Six hours of printing down the drain. If this was a Creality Ender 3 Pro V1 from five years ago, fair enough, this is a £1,100 machine and it doesn't even recognise it's out of filament. Its three days old. Just tried it again and its happily printing with no filament. This is garbage. Also Prusa do not have a Live 24/7 chat, isn't working at the moment. |
|
I did calibrate my Finda sensor and was able to print a 5h part with no issue. I believe my problem is not related to this. I think it was the Finda all the time. |
|
Happened to me second time. First time it was on last 5v and this time is on latest 6.0.2. Old filament unloaded - asked to remove the end, tried to load to finda twice and just sits there waiting for idk what. Last time I talked with support they couldnt help it and we threw it off as a random bug. This time I am waiting 20min for the chat. Already restarted the mmu3 twice, on this latest version there is an option now to disable MM. |
|
At this point im not sure but seems like MMU bug is "slightly" different than stock MK4 bug... could be same bug or just different firmware bug, but both could be solved with a CANCEL or GO ON options on the menu... sigh |
|
I put together simple album with videos of my issue. Does it look similar? Support can't help and they dont think it may be software related. after I disabled MM i cant reenable it and therefore no longer can retry feeding to finda. https://photos.app.goo.gl/ZFkBccxFhXkvQwAu5 EDIT: I pushed the filament all it could go, which is up to the PG. Then I pulled the plug from the wall and inserted it back in after a second. Printer rebooted, homed, and continued the print. I have a layer gap because there was a gap in the filament but otherwise the print may be saved. Or it may snap in half but at least will finish the print. |
|
I've had the same issue happen on an Mk4 I built just a few days ago, using firmware 6.0.3+14092. Given the behavior I've observed, I think it's a mix of hardware issues and software bugs (or if not a bug, behavior one would not expect with common sense alone). Hardware issues: when I have the block (printer asking to remove filament when no filament is present), manipulating the filament sensor ball with a piece of filament or the 1.5mm allen key unblocks the printer, but not instantly. After enough manipulations, I can clearly feel resistance when inserting a piece of filament, and by shining a smartphone light through the open idler and up the filament path, I can clearly see the ball extending into the filament path. A few seconds later without touching anything, the printer manages to move on to the next step in the change process. My best guess is this comes from the sensor taking time to react to the change in the magnet's presence. Software issue: in order to avoid the block, the procedure I have found works all the time is to remove the filament only after confirming it has been removed successfully, and only once the printer actually asks to remove it. I don't understand why such a procedure is necessary: if the printer asks the user to confirm the filament has been removed, the first thing anyone would do is take the small bit of filament out of the extruder and only then confirm that yes, they were able to take it out of the printer without any issue. Asking to remove it when it has already been removed is counter-intuitive to the extreme, especially since the printer knows whether the filament is still present or not. I don't know about the hardware issue, if anyone can confirm and refine the cause it would be good. As for the software part, I don't know if it's an actual bug or a counter-intuitive feature, but I suggest changing the filament swap procedure so that it skips the "Please remove the filament" step if the filament sensor already reports no filament being present. |
This! Please! |
|
Happened today with one extruder of my XL. Since the firmware had no button to force-confirm, I cut the power and the print finished successfully. Please add a force skip check button. |
|
I still get this on both my MK4's. The printer keeps thinking there is filament there when I have removed it. I also get this sometimes, but less often, when it runs out of filament and the printer keeps on printing. Thats really annoying. Also the current Prusa firmware doesn't communicate correctly (or at all) with Octoprint when it is out of filament. This has now been fixed with an Octoprint plugin here, https://github.com/jneilliii/OctoPrint-PrusaFilamentRunoutMonitor, so thats one less thing to worry about. It is not quite as good as the developer and I would like (I funded the work), but after talking to Ginna, it's as good as it can be given that Prusa don't appear to give a rats arse about this problem. |
|
IRONIC MODE ON Stop commenting this bug! This does not exist! Sincerely, Prusa Support. IRONIC MODE OFF |
|
Have had this issue 4-5 times in a month. @Prusa-Support stop wasting people's time with this asshole design and put in a simple option |
|
Yeah - this is really bad of them. I had two online chats with support
last year where I really thought I'd gotten through and put it on their
to-do list! But alas, I guess not? Poor showing, Prusa.
…-j-
- - - - - - - - - -
Jascha Narveson
computer department
Saint Ann's School
On Fri, Aug 30, 2024 at 12:03 PM mvayala ***@***.***> wrote:
Have had this issue 4-5 times in a month. @Prusa-Support
<https://github.com/Prusa-Support> stop wasting people's time with this
asshole design and put in a simple option
—
Reply to this email directly, view it on GitHub
<#3129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGHQCHIV6W2IKP4CEXZRO2DZUCJUBAVCNFSM6AAAAAA2A4ZWDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRRG43TMNRRHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I discovered that my filament runout sensor was mis-calibrated, and it (almost) always thought that filament was inserted. In normal operation (even for normal filament changes that aren't happening mid-print) this isn't an issue, and you won't really even notice that this is the case. I then re-calibrated the filament runout sensor, and I haven't had an issue since. Actually, one time I still had an issue when I pulled out the filament and some stringing was left behind, but once I jammed a piece of filament in a few times to move it out of the way, it cleared. So here's my suggestion: Go to the calibration menu, try re-calibrating the runout sensor, then insert/remove filament a few times (doesn't have to be a full load/unload, i.e. you can do this cold) and make sure it properly and reliably recognizes that the filament is being inserted and (more importantly) removed. I DO think that Prusa should still provide an option on the menu when doing an in-print filament change (whether it's due to a planned color change or an actual filament runout) to "continue" past the "remove filament" screen even if the sensor thinks that filament is still inserted. Even if it has a big red warning. |
|
Yeah - I'd be happy with the "Proceed at your own risk" style warning on
the UI - I'm happy to take responsibility for overriding the system if the
system clearly sometimes makes mistakes!
…-j-
- - - - - - - - - -
Jascha Narveson
computer department
Saint Ann's School
On Fri, Aug 30, 2024 at 12:30 PM Adam Batkin ***@***.***> wrote:
I discovered that my filament runout sensor was mis-calibrated, and it
(almost) always thought that filament was inserted. In normal operation
(even for normal filament changes that aren't happening mid-print) this
isn't an issue, and you won't really even notice that this is the case. I
then re-calibrated the filament runout sensor, and I haven't had an issue
since.
Actually, one time I still had an issue when I pulled out the filament and
some stringing was left behind, but once I jammed a piece of filament in a
few times to move it out of the way, it cleared.
So here's my suggestion: Go to the calibration menu, try re-calibrating
the runout sensor, then insert/remove filament a few times (doesn't have to
be a full load/unload, i.e. you can do this cold) and make sure it properly
and reliably recognizes that the filament is being inserted and (more
importantly) removed.
I DO think that Prusa should still provide an option on the menu when
doing an in-print filament change (whether it's due to a planned color
change or an actual filament runout) to "continue" past the "remove
filament" screen even if the sensor *thinks* that filament is still
inserted. Even if it has a big red warning.
—
Reply to this email directly, view it on GitHub
<#3129 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGHQCHMCICY6G5JAG6N5YBTZUCM2ZAVCNFSM6AAAAAA2A4ZWDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRRHA4DANZXGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I was on the same boat of miss calibration twice but the problem returned shortly after so I'm not sure if it's their way of calculating or the margins they use to realize filament is in or not but what it makes no sense and no logic is to give you NO OPTION to cancel nor continue if filament is out and printer keeps requesting you to remove it. That's plainly DUMB at this point in the... "market". |
|
Found this long thread, same issue on the Prusa Mini, color change, remove filament, then stuck at the screen when there is no filament. |
and others
Please, before you create a new bug report, please make sure you searched in open and closed issues and couldn't find anything that matches.
Printer type -
MK4
Printer firmware version - [e.g. 4.0.5, ...]
Any
Original or Custom firmware - [Original/Custom]
Original
Optional upgrades - [e.g. Filament Runout Sensor]
Stock Factory Assembled MK4
USB drive or USB/Octoprint
USB
Describe the bug
How to reproduce
Read above.
Expected behavior
Since it has happened to me already TWICE and non correlative, I asume this is a firmware glitch. I already opened the idler door and removed any filament (first time none was there, second time a section was there, I chose NO to the question, but apparently it didnt detect I removed it), blowed air, moved filament on the port hole, nothing helps when the bug is present. ONLY Reset button fix the issue and once the printer reboots, everything works as intended.
G-code
No particular gcode.
Video
Next time it happens I'll tape it.
The text was updated successfully, but these errors were encountered: