Failed to pull back the filament from the toolhead to AMS. Please check whether the filament or the spool is stuck. After troubleshooting, click the retry button. [0700 8004 122508]
I haven’t been able to use my Bambu Lab X1-Carbon for weeks now because I keep getting this error, and retrying isn’t helping. There is NO filament in the AMS, and I have traced through all of the lines that go from the AMS to the printer, and there’s no filament in any of it. Yet, when I start up the printer, it thinks there’s a spool on the 4th slot.
How can I get the printer to realize there’s no filament and continue?
Nevertheless, I did it. The area where the magnet/spring/sensor was looked really clean, but I blew it out anyway, put everything back together, and booted it up.
Same issue.
The error is a little different, though: [0700 8004 180015].
Is that last section of numbers merely the time of day?
You might also be able to leave the filament sensor unplugged and then you can use the other working slots until you get parts it just depends how the communication is setup on this filament sensor circuit.
I swapped the filament “thingy” for #3 and #4. I thought for sure this would result in it saying that there’s filament in #3… but no… it still says that there’s filament in #4. What does this mean?
The error is: Failed to pull back the filament from the toolhead to AMS. Please check whether the filament or the spool is stuck. After troubleshooting, click the retry button.[0700
8004 205830]
I will look maybe they have switches also in the internal filament hub.
My printer is
The Bambu Lab X1 Carbon is on 01.05.01.00
The AMS is on 00.00.05.96
I know you said it will not load any filament in any ams slot do to saying filament is stuck in slot 4 I was just thinking if the extruder filament sensor was seeing filament and saying it is slot 4 do to if that was the last ams slot you used ?
To be clear you can side load filament and the printer will print ok ?
When you connect the AMS with the 6 pin cable the error pops and says filament is in slot 4 and you can not print or load any other filament slots correct ?
Unless some filament is stuck in the hall sensor mechanical lever or the main AMS board has failed.
The filaments hub is located at the bottom of AMS, it consists of four hall sensors, one magnetic rotary encoder, and one brushless motor. It merges four filament paths into one. The hall sensor detects when the filament has reached a specific location, which in turn activates the brushless motor to give the filament a second stage driving force.
Maybe go ahead and open a support ticket being it will be a few days.
Push a fresh piece of filament through the top of the funnel and pull it through the backside
If there’s any debris in there it should come out
If there’s no debris in there then its a slightly more complicated issue
From what I’m reading and what you’ve already tried I’m positive there is something inside the feed funnel or that the funnel assembly itself has a bad sensor
I don’t think it’s the sensor in the funnel because I completely swapped #3 and #4, and it still shows that #4 is the issue. I think the software is just messed up and can’t get itself unstuck. There’s no filament anywhere, but it still thinks there is.
I should add to make sure the plug behind the AMS that goes to the printer is also in good shape snd fully plugged in to the AMS and the port on the back of your printer as well
In fact you might try turning your printer on with the harness from the printer to the AMS unplugged, let it boot up and leave it on for a few minutes like that
Then turn your printer off, plug the harness back into the AMS and see if it clears the fault
When I’m printing materials like TPU or CF I do so with the AMS unplugged and from a filament dryer beside my printer, there will be no issues with tirning your printer on with the AMS unplugged if thats of concern to you
The latest firmware eliminates the need to unplug the AMS but I have had a few small issues with that firmware so I’m on 1.04.01
It is likely though that slot 4 on the board itself has an issue in the AMS, you’ve definitely tried a lot of suggestions to no avail