After upgrading to 01.07.03.00 firmware, this bug keeps happening.
When switching color, I keep getting Extruding filament failed. The extruder might be clogged. [0700 8007 181509]
There is absolutely nothing wrong with the hot end. It is not clogged and this message only appears when it goes from one color to the next. I’ve restarted the print 3 times and it stops at the exact same spot, color change, each time.
6 Likes
That’s a new feature. 
It’s part of the filament verification routine. You may need to check your filament parameters.
“This function needs to be used with the slice files generated by Bambu studio v01.09.00.67 and above.”
“At present, only the X1 and X1C support this feature on filament parameters, with Bambu PLA Basic and Bambu PETG Basic being default open.”
2 Likes
Might not be related but worth to check if the buffer spring is seated well and the slide is not binding. I had a 0700 8007 164504 code saying the extruder was clogged and it wouldn’t feed the extruder fully on filament change. I traced it back to the spring and simply flicked it back into the seat.
2 Likes
Got the same issue right after updated too.
5 Likes
I just checked my buffer spring, it was pulled so I tried to push back and hopefully it solves the problem.
3 Likes
Same issue here when used with Bambu Studio 1.8.4.51 and an X1C on firmware 01.07.03.00. You can use the Bambu Handy app to roll back your printer’s firmware. I just rolled back to 01.07.02.00 and it’s printing just fine now.
Open up your devices tab in the app, and tap the hamburger menu in the top right corner. Then go to Firmware Version and you should have the option to downgrade to the last build. Looks like this has to be done in the app and has no other way of downgrading.
3 Likes
This isn’t a feature, it’s a bug. Filament will sometimes be able to load or change mid print, but it fails about 90% of the time. Yes, I ran it with Bambu PLA.
If Bambu Lab is going to release a firmware version that only works with a beta slicer version, then the slicer needs to be out of beta and pushed to all users just like the firmware was. But since it isn’t, this definitely is NOT a planned feature.
3 Likes
I’ve figured out a workaround. It is simple and it works. When it gives the error message on the screen, press retry and the AMS will start to retract the filament…when it gets all the way back and just before it starts to refeed the filament, pull the filament all the way OUT! . It will give an out of filament error. Put the filament back in and it goes past the retraction error and finish the print.
BUT, now that I know how to roll back the firmware, I’m trying that now.
2 Likes
Do not update firmware to 01.07.03.00
3 Likes
WOOOHOO - Glad I found this post.
I have the same issue - and have put detailed testing and info in this NEW BETA thread
- Link removed as its private beta thread - but itse easily found for those testing BETA.
I have also raised a support ticket with the same info - just to follow the process.
- So freaking glad I am not alone on this!
Essentially, newer V01.07.03.xxxx firmwares fails to fully grab the filament at the extruder level, using correct new bambu studio BETA and all instructions followed correctly, and retracts and retries the AMS feed 4\5 times before it fails with a FALSE extruder clogged alert.
3 Likes
FYI: The page you linked says “it doesn’t exist or is private”.
The link will only be accessible to people with access to the X1C beta forum and probably shouldn’t be posted here.
2 Likes
I completely forgot, thank you - removed.
Yes sorry, its a secure Private for those that wish to, and are approved to, BETA test firmwares.
- your signing up for potential for some problems… so yeah, its not for general use, apologies I posted a link.
- it IS important thou, that this occured in 01.07.03.00 normal and this thread was started. Means its not the “BETA” that introduced it
1 Like
A similar problem happens using V01.07.02 firmware also but it appears to me it’s a mechanical problem. If you get the option to “Retry” the filament load, see if the feed tube into the hot end can move up and down. It only takes a small amount–Like 2mm. Hold the tube in during the filament feed and see if the filament loads correctly.
I talk about it and have a temporary fix in this thread. It’s basically the hot end tube inlet connector is chewing up the PTFE tubing by the constant push/pull of the filament load/retract.
1 Like
Thanks Ken, however I actually found the thread and attempted that. I have no ‘play’ at all unfortunately and my PTFE end like y our picture shows no wear at all. Considering my semi-casual printing, I kinda of expect low wear etc.
If I rollback firmware - including back to V1.07.2.17 Beta, it all works fine, instantly - no modifing anything else.
If however this is somehow related to mechanical and tigher tolerances in the new firmware\beta studio, its far too tight when I have no play at all yet still doesnt work.
I suspect is not exaclty the same as the original authors code, more reliant upon filament specifics, thus why they are allowing it both in the extruder setting and per filament overrides. Not what the original code reuqires, at least in my setup - and with equivillent if not better waste reduction over Bambu’s implementation.
2 Likes
Same pb after maj. I roll Back. Lose a lot of time
1 Like
Same issue here, printing fine, updated firmware and reported nozzle clog at the first filament change. Rolling back the firmware now, will check if it still reports a clog.
1 Like
Well I be the first reporting to have no issues with the new firmware on the X1C when printing multiple colors.
Same here, I bought my machine Feb 23 and have never had an issue with any of the firmware updates so far. I hope I haven’t jinxed myself now.
This is the slighly older firmware. so Keen to know a few things if people are posting “No Issues”
Specific firmware of Pritner AND Bambu Studio (you need Beta Studio for the new firmware).
Specific filament and are you running the new “retraction” setting (you actually need to turn it on- off by default)
Any other custom g-code you might add\change to machine or filament change
AMS specificc or device code you change?
This will help why some people get the issue - and other - dont.