False nozzle covered with filament message on every print

Near the beginning of each print I get an error message saying that the nozzle is covered with filament or the build plate is installed incorrectly. This occurs with any nozzle or filament and multiple build plates. It usually occurs 1-5 minutes into the print and pauses until I take action to resume the print. This started a couple weeks ago and I’ve had my mini for about 3 months now. I’ve followed the maintenance procedures diligently and have the print always proceeds after this single message to successful completion. It never occurs again during a print.

Hi,
Perhaps you should try this :

This check is done at layer 3. It runs the nozzle all the way past the back right corner, and checks if it hits anything.
Run a print, and watch for it, see what happens.
You didn’t happen to install a plate alignment guide, did you?

I did install a plate alignment guide and I think that is the culprit. Actually I submitted it to Maker World and I saw a little bit of filament rubbed off on the top right edge of the alignment guide. I think the nozzle is not able to touch the plate surface due to the height of the alignment guide with the additional filament that has adhered to it and interprets this as filament covering the nozzle. It has not been an issue since I cleaned the excess filament off of the guide top. I’m going to modify the guide so it doesn’t protrude as high above the bed surface on the right and hope that will fix the issue since I find the alignment guide to be very helpful when putting down a magnetic plate.

3 Likes

There are some alignment guides that have been redesigned to be compatible with the new code. But, In my case, I just removed it. TBH, I found the guides to only be minimally useful.

I’m getting the same. Exact. Error. I have clump detection OFF, tangle detection OFF and also bed detection OFF and I’m getting this error on EVERY. SINGLE. PRINT.

I think I’m gonna revert firmware and see what happens. I didn’t have this issue before. Now I do.

firmware didnt help. So on to my next idea… ill keep everyone posted.

Did you fix it? Mine just started doing this and I don’t have any plate guides or anything.

After trying a few things, I myself was able to solve my issue.

I switched to an older version of the slicer. Upon doing so, even with the newest firmware installed, my false errors stopped.

I tested both orca slicer and Bambu lab slicer. Both of the most current slicers produced the false error. I then tested older variants, and the issue resolved itself. (Fwiw: I own a Mac and I save my version installs individually because of issues such as this… this isn’t the first program I’ve seen have hiccups lol)

If anyone else wishes to try and test my resolution, just grab an older version of orca and try it. I jumped to 2.0.1 for example and my problems stopped. Dunno why… but I’ve been printing 24/7 now since my last comment with absolutely zero false errors.

I get this error as soon as I upgrade Bambu Studio to a higher version. I tried to upgrade to two different releases, but they both generate this false error. I went back to version 1.08.02.56 and my A1 prints flawlessly. Go figure!

dehighlight the dynamic check pre print, just use bed level.

It is a 3rd layer thing, I used a gcode friendly text editor and found
damn it, 420… G0346… thats not it but closeish

I killed all those manually in the start code for all 4 or 5 profiles I made.
I have all but clump turned back on, runs fine … with a 4 noz

I have the same issue and after some research, I found that the “Mini Tool Storage Box with Lid” was the culprit, I modified the STL and made a negative square to the LID in the middle to the nozzle don’t touch the LID when is trying to check for the plate.

Go to settings> print options and turn off filament tangle detection, nozzle clumping and build plate detection.
Then if it happens again, hit the continue button. .
Works for me every time.

I’m getting this issue consistently with certain models. It prints the first layer just fine (or maybe first two, as people are saying it’s a third layer issue? I’ll pay closer attention next time), then throws this error. I have no mods installed on my A1. I have clumping detection turned off. Most models print just fine, but the few that do exhibit this error do so consistently. If I hit continue, it will finish the print, but the rest of the layers are offset slightly from the first one (or two).

I’m running the latest firmware on the printer (01.04.00.00) and Bambu Studio 1.10.1.50

Clump detection occurs on all prints (whether detection is turned on or off) after the walls of the 3rd layer. At that point the nozzle will move to the right rear just barely beyond the plate and attempt to drop down just below the level of the plate surface. If it succeeds in dropping down, it will return and continue starting with the 3rd layer infill. If it can’t drop without hitting something, it assumes that filament is stuck to the nozzle and the print likely failed to adhere to the plate, and it will stop and notify on the error. If clump detection is turned on, this same process will repeat throughout the print rather than only on layer 3.

As a first step to troubleshooting it, I would suggest watching it as it goes to that rear corner and make sure it doesn’t hit anything on the drop, whether it’s something on the plate or the printer (like a plate aligner) or something stuck to the nozzle or sock.

1 Like

There’s nothing preventing the nozzle from dropping down. Here’s a video of it happening: https://www.icloud.com/photos/#/icloudlinks/079iW5Gteg9ZaeSUmCe0VkIkg/0/

Again, this only happens on certain models (in this case, https://makerworld.com/en/models/496460)—most models print just fine.

Ok, I’ve fixed the issue by creating a print profile that removes the Time Lapse G-code (which includes the third layer nozzle clog detection). Here are the steps:

  1. Choose your usual print profile and click the edit button to the right:

  1. Select Machine gcode on the printer settings page (toggle the Advanced button if you don’t see that):

  1. Scroll down to the “Time lapse G-code” section and select everything and just delete.

  1. Click the save button and save the new profile (I just added “- No Timelapse” to the end)

It’s possible you can just delete the if block after the “; enable nozzle clog detect at 3rd layer” comment and leave everything else…I haven’t tried that yet. I don’t use time lapse anyway.

I’m wondering how it’s going after this implementation? Have you had to chase this issue any more since the fix? I’ve only had this A1 since after Black Friday just adding the AMS Light now. I recall it starting to happen on a couple of prints just prior. This said, I’ve been 3D Printing for nearly a decade but just got this machine. Is what we’re doing here creating a Print Profile? I’ve seen mention of the terminology quite a bit, as I’ve scrolled through Online Models section of Bambu Handy, but thought it was merely referring to layer height or ironing or the like. Or have I got it wrong and we’re just modifying the Gcode?

The issue has not occurred since I made this change (actually, that’s not quite true—it happened to my print last night, but that’s because I forgot to select my “no timelapse” profile). I’m not sure what the exact BS terminology is, but Print Profile seems right. But it is just modifying the Gcode. It’s clearly a bug, likely in the firmware, so I hope it will eventually get patched and this hack won’t be necessary.

From what I’ve observed, Bambu Lab as a company, like so many others, have begun to scouer these message boards to include the multitudes of Facebook pages and groups, to YouTube influencers finding bugs like the BL A1 power cord debacle. One of these is Snapmaker. Many who received them to review on their YT channels had some major finds that would work so much better if… sorta finds. Snapmaker changed their print head to simply snap off and laser or CNC modules to just snap into place without much brain power for the use of the machine(s). I’m hoping BL does this, because things like this when avoided have bankrupted many a start-up. Standing by…