English
Login

Stuck filament detection

#31101 (CORE One) #35101 (CORE One L) #26101 (MK4S) #13101 (MK4) #27101 (MK3.9S) #21101 (MK3.9) #17108 (XL)

Relevant for

CORE One family
MK4 family
XL family
MK3.9 family
Article is also available in following languages
English
Čeština
Polski
Deutsch
Français
Español
Italiano
日本語

The Prusa CORE One, CORE One L, and the Original Prusa XL, MK4/S, MK3.9/S are equipped with a loadcell. Thanks to this component, starting from firmware 6.0.0, the printer can detect whether the filament is stuck and not moving, for example when the nozzle is clogged. 

If this is detected, the print pauses and the printer shows the message: "Stuck filament detected. The filament seems to be stuck. Please unload it from the extruder and load it again." 

Once the unload button is pressed, the printer unloads the filament. After this, it prompts filament loading and resumes the print. 

It is important to note that detecting stuck filament is possible only inside the Nextruder, as pressure builds up from the nozzle to the upper part of the Nextruder. However, if your filament is tangled on the spool, there will be no internal pressure, just outside tension, which the loadcell won't recognize.
Stuck filament detection won't be possible on MK3.5 and MINI/MINI+ as they aren't equipped with the loadcell sensor.

Repeated detections

Loadcell troubleshooting

In case of multiple, repeated stuck filament detections in rapid succession, troubleshoot the loadcell and the components around it, using the steps in the dedicated loadcell troubleshooting article

Temperature and speed settings 

If loadcell troubleshooting does not improve the multiple and repeated detection, consider slight changes to temperature and slight reductions in the movements and extrusion movements. Those can be set individually through PrusaSlicer, or in a single print speed setting, mid-print, using the Tune menu

Deactivating the detection

It is possible to deactivate the stuck filament detection in LCD Menu -> Settings. Deactivating the detection comes with an increased risk of nozzle clogging

Was this article helpful?
This action is available only to registered users. Please log-in.
 

36 comments

Log in  to post a comment
Anhalter
Gents,
After three months of flawless printing I am getting bored by the same issue. It started in the middle of the printing of a bigger model.
I am using a MMU3 and was so proud on getting it running, now all prints are getting stuck, and with MMU3 the print does not restart after reload….
So I shut down the MMU3 and load the material manually which seems to be a trouble shoot. At least a stopped print is now to be continued again. I am not sure if the deactivation of the stuck filament sensor would help. May be that is the next I try.
Dan the Man
I am also having the same issue. The filament extrudes perfectly for that 50mm strip, and then reports stuck filament, then the printer demands a reload and prints flawlessly from there. The proposed troubleshooting step "consider slight changes to temperature and slight reductions in the movements and extrusion movements" is useless.
lptr
I am getting this error a lot, too. It would already be an improvement if there was an option to ignore the error and continue the print without unloading the filament first.
Toolmaker240
FIXED!
Well in my case it did, but I did do two things at once. Apparently the tension on the idler lever is pretty crucial, it actually mentions in the instructions for the kit in BIG BOLD LETTERS, STOP TIGHTENING AS SOON AS THE SCREW TIPS REACH THE FRONT FACE OF THE IDLER NUT..

I also ran the gearbox alignment step and I have a feeling that this was the actual issue because I had tried just about every possible tension scenario that I could think of.

As a side note the teeth on my extruder gear (the ones that grip the filament) have a pretty clear wear pattern, I assume from a couple spools of Fiberon PET-CF.

My printer had this problem so often that I couldnt get through an entire print without having to deal with it. Going on about a month now of several hours worth of printing and haven't had anymore issues.
mousestalker
Have this exact issue. I've adjusted nozzle temps, hotbed temps and speed with no joy. The only thing that works (mostly) is deactivating the sensor.

I also installed the latest firmware and then downgraded back one version. That didn't help either.