Feature request - move print head when there's a pileup

It would be really nice if the print head would move off of the chute when there’s a filament pileup. It makes it really really hard to clear the pileup with the print head in the way, plus the nozzle is hot and it tends to stick to the pileup. The only way to clear the pileup is from the back and that’s very difficult if a wad of filament is stuck to the nozzle. As someone who does almost exclusively multi-color prints this would make my life a lot easier.

3 Likes

Welcome to the community.

Why wouldn’t you just use the nozzle movement keys found in both the slicer and on the front panel?

Because that would screw up the print that’s in progress.

1 Like

Actually, the printer allows you to hit pause and manually manipulate the nozzle head. This is precisely for the reasons you just expressed. Then once you want to recommence, just hit the resume. Easy peasy.
orca-slicer_GRuxANf7Du
button
orca-slicer_DPJ0IRrDSa

3 Likes

i get layer shifts when trying it. And it would be even easier peasier if the setting in the firmware that tells it to park right over the issue you’re trying to solve instead told it to park slightly to the right instead. it’s possible to clear from the back, it’s just a pain and there’s no reason to default to blocking the chute instead of default to not blocking the chute.

3 Likes

If you’re getting layer shifts when moving the print head with the unlocked on screen controls/in studio and resuming… may I suggest you contact support because there is something wrong

If you use the axis movement controls it (should) inject a home command into the gcode when you resume

Also the reason it stays in place is so it doesn’t potentially bend the nozzle without input from the user who can make a better decicsion

There’s plenty of room above the chute to protect the nozzle while still allowing access to the chute to clear it. It doesn’t need to perfectly and completely block access to the chute. That’s why I said ‘slightly to the right’. Why are you so against being able to easily clear an issue? I sincerely don’t understand your objection. How would it hurt you for me to be able to easily clear a filament pileup without having to go though one annoying process or another? I’m not trying to be difficult here, I’m just unable to understand your interest in the status quo when the alternative would help lots of people (including, admittedly selfishly, me) and would cause you no harm.

2 Likes

Came here for the same reason. I have no idea if moving the head then is a good idea or not, but leaving the print head dead center in the way isn’t going to help. It just leads to more prying and clawing on the thing to get the pileup cleared.

I’m not saying it’s a bad idea to move it, but it’s certainly not clear to the user sitting there looking at it stuck with no way to know what to do. One inch over, and it’s a non problem. Where it is, it sticks itself even harder to the pileup then cools down to ensure it stays firmly attached. NOT good.

1 Like

I would like to put in my support for said feature. When the filament pileup happens, I get a display on my screen that does not indicate that it’s possible to pause the print and then move the printhead with the navigation buttons on the control panel. I’ve been afraid that interacting with that error message will cancel the print job, and that’s the last thing I want to have happen. An option button to “pause print” would be helpful, I think.

1 Like

Let’ go one better for this feature request. How about a button that says something like “clean print head.” When activated, this would park the print head front and center and heat the hotend to 250 deg. There could be a timer on this behavior to prevent mishaps. This would be useful!

1 Like

Thanks for this great suggestion.

I agree completely and actually came here to suggest the same thing. Typically I grab a pencil, remove the top cover and then hit “resume” and then when the head moves I pop the blob out of the way. The fact that it doesn’t just park off to the side a bit or out of the way of the chute is a pain.
And moving the head manually from the front panel is just asking for a failed print IMO. Maybe it works for some but I’ve seen too many weird layer shift comments from people to believe that it works flawlessly.

that also doesnt work when you have a print running

Did you read my post? How does that not work? Perhaps you meant something else or didn’t see the entire post from your phone. :rofl:

is that just an x1 thing then, because my p1 just gives an error: printer is abnormal, unable to operate

If you can elaborate on what you’re doing before the error shows up, I might be able to help.

That feature works - I use it frequently. More often from the front panel since the slicer is laggy.

What I can say is this: the P1 firmware has a lot of defects, and the front panel makes them obvious. Operator input panels should be immediate and responsive. Bambu’s feels more like an “advisory.” Button presses aren’t acknowledged, feedback is inconsistent, and it often feels rushed to market without proper user testing.

In my experience, if the panel seems unresponsive, it’s usually because the printer is busy - for example, “downloading” a model (which is really just processing). Once it finishes, the panel starts responding again.

Just today I had the filament runout indicator lock the printer into a state where the only fix was to cut power and rely on the power interruption recovery feature - which itself is buggy.

there are a lot of bugs in it. for me, the error shows up, and the print automatically pauses, and then whenever i try to move it, it just says, printer is abnormal, unable to operate.

You wouldn’t be chance have a photo or screenshot of the error message? It usually is a four sequences of four Hexadecimal numbers error in the format of: 0300-9D00-0002-0001

If the message is on the front panel, you’ll have to be patient and wait for it to scroll before you can get a photo. It may take a couple of tries and I agree, it is a quite annoying design flaw.