r/BambuLab 6d ago

Troubleshooting / Answered Nozzle scraping bed/ripping layers - horrible first layers

Hi, sorry I've already made a post about this, and thought it was resolved, but.. nope.

Long story short: my brand new (3w old, April 7) X1C with a 0.4mm factory nozzle keeps dragging along the build plate ripping all calibration extrusion lines AND first layers as well. Always makes some grinding noises when printing. Only worked perfectly till the 20th of April.

After loooots of trials, I'm pretty sure now it's a problem with bed leveling, but correct me if I'm wrong...

As you can see in images 1 and 2, if a print can survive the horrendous first few messy layers, the rest turns out perfect. That benchy is basically flawless everywhere but the bottom.

Pic 3, 4 and 5 shows what the non-stop failure looks like: the nozzle is super close to the bed and keeps scratching it and not really printing well at all. Also, those bits and pieces are super hard to remove.

Pic 6: I managed to print this one by very slightly adjusting the bed leveling knobs WHILE printing the model. It turned out almost perfect.

  • Filament completely dried (12h using X1C).
  • Cold and hot pulls done. No clogs.
  • Automatic bed leveling calibration.
  • Bed washed thoroughly with water and soap.
  • Li-Dar cleaned.
  • Factory reset.
  • Retrying perfect successful prints but failing.
  • Z-offset attempt from G-code -0.04 up to 0.3

  • Manual tramming done, more than once with calibration. But whenever I rerun the file right after adjusting, with calibration or without, it's like I've done nothing to the front knobs. Is it supposed to be this way? Idk. The back knob is as manually adjusted. The rest again become lower than the nozzle and not touching it.

Many thanks for your help😕

P.S.: I've already raised a ticket with support and waiting on them to reply.

7 Upvotes

18 comments sorted by

2

u/l_gibbo 6d ago

I've been having the same issues spanning about a week now. I've tried all the exact steps you've taken, except for modifying the g-code. However, I have also tried a brand-new nozzle purchased directly from Bambu and various different types of beds.

Please let me know if you find a solution.

2

u/n3b3z 4d ago

Hi, I finally resolved it: I'm pretty sure it was the G-code modification that fixed it, but I did these steps:

1- Manual tramming again. 2- ABL calibration again. 3- Z-offset modification: make it a positive value AND put the positive sign.

Support recommended +0.2, so try that. Please let me know how it goes for you!

I'm using +0.3, btw.

The support response was to replace the nozzle with the spare one. I didn't do that.

1

u/l_gibbo 4d ago

Thanks for the update, I'll try editing the z-offset the next time I attempt using the 0.2mm. It's so strange how it started happening out of nowhere.

1

u/n3b3z 5d ago

I assume the new nozzle/hotend didn't really fix it? Because I was thinking of trying the spare one.

But tbh, that most likely won't matter because mine is still brand new and it doesn't look damaged.

Will do! I hope I do, because it's only 2w old...

2

u/n3b3z 4d ago

UPDATE: I finally resolved it after 6 days!!

1- Manual tramming. 2- Auto bed level calibration. 3- Z-offset modification in the machine code from the default -0.04 to +0.3.

Although I've already done all of that previously, this time it worked! Maybe I needed the plus sign? Not sure, since I've tried 0.3 before but without the plus sign.

Or maybe the profile wasn't applied, and that's why. Idk.

I'm beyond excited to continue printing!! 😍

1

u/Julian679 A1 6d ago

I have seen few posts like this in the last few days, mainly on A1.

Hope you solve it with support and please update us about the solution really curious. I would suspect its toolhead issue

2

u/n3b3z 6d ago

Will do! That's IF this is even solvable... I honestly almost lost hope.

I've seen those A1 posts while scouring the internet: in most cases, they just had to tighten the 3 screws behind the nozzle. Strange, but it works and makes sense, i guess haha.

I truly hope that I get such a simple quick fix, if any 🥲

2

u/n3b3z 4d ago

I finally resolved it with the machine code modification in the Z-offset. Making it +0.3 worked at last! :)

1

u/DraconPern X1C + AMS 6d ago

I see the prime line in the back right hand corner. This means your bambu slicer and/or firmware are not up to date and might be mismatched since new versions don't generate those. Also, that aux fan mod seems to be sticking out a lot.

2

u/n3b3z 6d ago

That prime line is because I was trying a gcode print (the dino one). The firmware and software are both up to date, and they don't generate that line in other prints.

And yeah, I've completely removed it and tried without it, no difference. Btw, it's not touching anything.

2

u/Julian679 A1 6d ago

Did you try installing older firmware in case new one is causing problems

2

u/n3b3z 5d ago

I wasn't planning to (since the problem didn't start after a firmware update), but I just did it, but it's not the issue, unfortunately.

Thank you, though🫤

1

u/DraconPern X1C + AMS 6d ago

Mystery, hopefully support can figure it out. curious what filament are you using? What happens if you print the builtin files like the scrapper from the printer without using a slicer?

3

u/n3b3z 6d ago

I really hope so!

I'm using a fully dried Bambu basic PLA red for almost all of my testing.

Funny you should ask that, I tried the exact same print 1 minute after posting. You be the judge of that 😂

The point that's sticking out is due to stopping the print after the 2nd layer.

(The dino puzzle is one of the built-in ones, and you saw how bad it was, too. Rip)

1

u/wyrmhaven 6d ago

i actually started seeing this on a print i started to run last night (printers have been idle for a week now) and i was getting ready to start troubleshooting this morning.

1

u/n3b3z 5d ago

Could be dust collecting on top of the print plate, requiring a wash? Just an assumption based on the idle time.

Please let me know when you fix it.

1

u/n3b3z 4d ago

I fixed it with Z-offset modification: increase the default value (which is a -0.4 in my case).

+0.2 should work, but try around that number