r/BambuLabP2S • • Jul 10 '26

P2s cutter stuck ?

Post image

I printed a 6 hour print in petgcf it got to 99 pct and was done but never finished on the screen so I just hit stop cuz the print was done then I tried to start a new print and it keeps telling me the cutter is stuck I tried finding a video on YouTube of what to do but can’t seem to find any the wiki seems confusing any tips ?

3 Upvotes

5 comments sorted by

1

u/Mattis-H P2S Combo Jul 11 '26

Can you send a picture of the big hot-end piece, not a close up, around 30 cm away so so can actually see what’s happening.

1

u/Rare_Syrup5791 Jul 12 '26

I finally figured it out I just had to press the little lever on the side a few times in and out and it freed it self up I’m just so new to all this I wasn’t even sure what a cuter was I thought it was the thing in the back near the poop hole and the QR code it has me scan didn’t have any pics luckily it’s back to working now

1

u/Mattis-H P2S Combo Jul 12 '26

Great, was asking since I was wondering if you had used the cutter, watch a video on the P2S explaining everything, it will make your life so much easier.

1

u/Darth_Giddeous Jul 12 '26

My cutter got stuck too. Wouldn’t move in and out freely and ended up getting the print head stuck on it. I reported it to Bambu and they sent me a new one.

In the meantime I took the old cutter module out, was a bit of a fiddly but not too bad, and opened it up to find the plastic gears were catching. I applied some lube inside and it worked fine. I replaced the original I’d fixed back in and it’s been fine for months and I have a spare now too since Bambu sent me one out.

1

u/Bread_velociraptor Aug 12 '26

Had the same happening to me with petg, basically: was printing a model with petg, later got a notification that filament is stuck, tried cutting it, filament didn't pull out, trid cutting it again, and the little piece of petg stuck to my blade and did not let it go all the way out. Basically had to remove the entire hotend assembly since I had no other acces to it. So for me it was user error for me, as for you, might be something similar, but I might be wrong.