AI Nozzle clumping detected. Bambu, please move the print head!

The feature is great when it works, but how are we supposed to clean any clogs when the print head is parking above the poop chute.

When this error is detected, can we add the feature that the printhead is being moved into a position where we can actually fix the issue ?

It’s impossible to do so from its parking position.

8 Likes

Why aren’t you Manually moving it?

2 Likes

Yea this would be a nice quality of life change

Totally agreed, it would be a nice feature to have an option to bring the print head to the front and center for repairs or cleaning.

1 Like

Stepper motors are energized and engaged as it waits. So it fights you.

2 Likes

Manually move it by using the XY controls, or by using the home button will move it to the center.

1 Like

you lose the print then
252525

2 Likes

Ahh sorry, my bad, I get the picture now. Carry on.

2 Likes

though honestly i don’t think that it would be really useful… pausing a long time = a huge shrinkage line on the print and weak layer bonding over there… :stuck_out_tongue:

1 Like

agree, if its an aesthetic print, it’s 100% lost already

Just open your text editor, write M18 on first line, save the file as stepper_off.gcode (or whatever).

Insert the file at the root of your USB stick and whenever you want to de-energize your stepper motors without waiting to move the toolhead manually, just “print” the file.

How to test:
Move Y or X or both from the screen menu, the head is locked
Run the file, the head unlocks

@philch did you actually test this? I ask because I tried many such single-command things on the X1C (several fw versions ago) and it never worked, the execution would just hang (with no command executed) until power off. When instead including a couple of “normal” commands in the top and/or bottom, it did work fine. I never established what minimum was actually needed but got it working after looking at the official bed tramming gcode for clues (and probably copied more than strictly needed).

That said, this thread’s scenario is in the middle of a print so even if the gcode works it’s not applicable here. But I’m very interested in doing other things with short snippets of gcode like you suggested.

I tested it and it worked but did I power it off before testing I don’t know. I re-read the OP query and did not understand he wanted to fix the clumping and resume printing

Sorry didn’t expect my question wasn’t clear. Let me try again :slight_smile:

Basically, if you print a model and AI detects clumping on the nozzle, it parks the head back at the nozzle wiper and pauses the print and asks you to hit continue once you fixed it.

The GCode fix won’t work in this case. Also you say you tested it by powering off - that’s not a real test because of course it works because if you powering the printer off, the head won’t be on and the motors locked. So yes, turning off means you can move the head manually.

But obviously this isn’t an option if you want to continue the print.

No I did not say I powered off to test just that the gcode when in the stick might only be available for further use after power off the first time. When it’s there it should always work.

But it does not solve your issue though as it will be handled as a new print effectively killing the print in progress.

But now, on a real clumping, I wonder how you could resume the print after attending to the nozzle and fix the clogging on an effective manner.

This said, while on pause you can still send commands from the printer to move X, Y and Z, you can cut the filament by hand pushing the lever, you can extrude etc you can switch nozzle, you can heat the nozzle, you can even remove it, clean it, replace it. You reconnect everything and heat resume, printer will park the head, load the filament and resume.

Will this guarantee the quality of the print after resume, may be not. A false positive can be handled by just hitting « resume » but any physical action on the hotend will most certainly require to cancel the print and restart if you really care on the quality of your print.

You can experiment on all you can do by launching a small print, hit « pause », do all sort of things and hit « resume ».

Had that happen…my fix was to unload filament, change to a spare nozzle, load then resume.

I don’t think you’re allowed to run another gcode file while one is paused and waiting for user input. Pretty sure it will clobber it, if you tell it to run. I’ve staged a file and written myself a note to try it next time.