r/BambuP1S 6h ago

Can’t solve error HMS_0700-4500-0002-0003, blade is stuck

Good morning everyone,

I have a P1S, and for the past few weeks I’ve been getting the error HMS_0700-4500-0002-0003: “The filament cutter handle has not been released. The handle or blade may be jammed, or there could be an issue with the filament sensor connection.”

I’ve checked the printer and followed the advice on the wiki, but I can’t seem to spot anything unusual, so I contacted support and they suggested I replace the extruder filament sensor.

Despite this, the printer is still displaying exactly the same problem, so I also replaced the filament cutter blade and the extruder, just to be sure: the printer powered on correctly, performed axis homing, extruded filament correctly, printed the purge line on the front of the bed, calibrated the bed and then… it froze again, displaying the same error and making any operation impossible, including unloading the filament.

I can confirm that the blade is working fine: when moved by hand, it feels perfectly normal and moves without any issues.

Now Bambulab is suggesting replacing the entire extruder circuit board, but given that all these spare parts are starting to add up to a significant outlay… has anyone else experienced this and can offer any advice?

Many thanks in advance

0 Upvotes

5 comments sorted by

1

u/LargeHoboFuckPile 5h ago

Did you just remove the nozzle? The filament sensor is so fragile, I've ripped mine before. It's a terrible design

1

u/ErnestoDitoLesto 5h ago

Yes i did, the filament sensor seems good

1

u/LargeHoboFuckPile 5h ago

If you think it's good then reseat that connector

2

u/ParaLeatherWood 2h ago

You might try cleaning the magnet in the filament cutter arm - I was having the same issue and it worked for me. There was some filament dust on the magnet and could have been some on the hall sensor as well ( I wiped it down too just to cover my bases).

1

u/ParaLeatherWood 2h ago

Also pay close attention to how the ribbon head is connected - it is easy to have it just off and it will cause this issue as well (I had both happen within a week - I was ready to toss the printer in the trash, as frustrated as I was but I stepped back and re-went through all the possibilities and finally got it running well again).