Stuck filament detection causing filament to get stuck?
 
Notifications
Clear all

Stuck filament detection causing filament to get stuck?  

  RSS
ntdesign
(@ntdesign)
Reputable Member
Stuck filament detection causing filament to get stuck?

Hi all, just wondering if anyone else has this problem or it's just me...
I tried the new stuck filament detection (with the load cell) in 6.0.0 firmware. When it's on I get a stuck filament warning on almost every print, and it turns out the filament is actually stuck. I don't know what's causing this, maybe filament gets cooked in the nozzle while it's sitting there and waits for user intervention, or it does some retraction that causes heat creep. I'm guessing these are false alarms because everything works fine when the feature is off. Same gcode, same filament. The problem happens on all toolheads, different print models and different kinds of filament, but at random layers in the print. I could unclog it in all cases by raising the temperature and pushing more filament through, but to do that you have to stop the print.

Anyway this feature seems mostly useless in the current state. All you can do is unload/load the filament, but if the nozzle is clogged whats the point? What you really want is access to the head and ability to change the temp. It needs to save the last position and then give some control over the printer, otherwise there's no chance to save the print. In the current state, supposing it would work, all it does is potentially save some filament when it clogs. Maybe if the bed happens to be low enough you could stick a needle in the nozzle but that's about it.

Has anyone else seen this? There's no mention of it in the 6.0.1 changelog, no chance yet to try it.

Posted : 27/05/2024 6:50 am
juanjo.c
(@juanjo-c)
Active Member
RE: Stuck filament detection causing filament to get stuck?

Hello 🙂

I have been looking for your question on the forum,,, I am doing a 5 day print in which I had to cancel the first time because the nozzle really got stuck, so this next time I have decided to activate the "Stuck filament detection" function, today When I woke up I went to look at the print and the error "Stuck detection" was on the screen, I had to take out the filament and put it back in, I don't know the reason but I had to insert the filament manually, different from when you do Load filament from the menu, in short, nothing was stuck, everything was fine, a false detection? ,, I have disabled it from Tune and now it continues printing normally, I will try it again in a while because I think this function still needs to be improved...

 

Posted by: @ntdesign

Hi all, just wondering if anyone else has this problem or it's just me...
I tried the new stuck filament detection (with the load cell) in 6.0.0 firmware. When it's on I get a stuck filament warning on almost every print, and it turns out the filament is actually stuck. I don't know what's causing this, maybe filament gets cooked in the nozzle while it's sitting there and waits for user intervention, or it does some retraction that causes heat creep. I'm guessing these are false alarms because everything works fine when the feature is off. Same gcode, same filament. The problem happens on all toolheads, different print models and different kinds of filament, but at random layers in the print. I could unclog it in all cases by raising the temperature and pushing more filament through, but to do that you have to stop the print.

Anyway this feature seems mostly useless in the current state. All you can do is unload/load the filament, but if the nozzle is clogged whats the point? What you really want is access to the head and ability to change the temp. It needs to save the last position and then give some control over the printer, otherwise there's no chance to save the print. In the current state, supposing it would work, all it does is potentially save some filament when it clogs. Maybe if the bed happens to be low enough you could stick a needle in the nozzle but that's about it.

Has anyone else seen this? There's no mention of it in the 6.0.1 changelog, no chance yet to try it.

 

Posted : 28/05/2024 5:53 am
Share: