From my understanding the exclusion area is for Z axis clearance and if so why is it enforced on X and Y?
Or am I misunderstanding what that area is for.
1 Like
You are misunderstanding what the exclusion area is. It’s the area where the filament cutter is activated on the side of the print head via the side of the printer. The bed moves in Z and the head moves in X and Y.
Here is the wiki article that explains it further. Print volume limitations, and how to use the full build volume 256x256x256mmÂł | Bambu Lab Wiki
Hi Jon
If you read the Wiki the only restriction setting override is for Z height so they are enforcing a cubic limit when the only clearance issue is in the Z. I had a model that was 100mm tall but was 256X256 on the plate but because it was in the exclusion zone I couldn’t print it without the kludge.
The Wiki used to be a little clearer about this. The info is there but just in the details.
- Clear the “Excluded bed area” in Printer settings
This is what the stock settings are.
This is what you need to change it to.
Be aware that you still need to install the cutter override part as detailed in the wiki.
1 Like
If you read the wiki, there is an exclusion zone in the front left corner of 18(x)x28(y) mm², because moving the head into that area at any height will cut the filament.
Using the area in that corner at any height requires a hardware modification to prevent cutting the filament, and changing plate dimensions in the printer preset.
Edit: @JonRaymond is faster at the keyboard than I am…
2 Likes
Ok starting to get a feel for it and certainly I can now work around it. I still fail to see why X and Y is effected because any bed motion during printing for the exception of Z hop is downward and away from the print head. When the head moves over to the cutter if the bed moved upward it would crash the print into the print head.
Again it seems they are enforcing a cubic limit when in reality the only limit that needs enforcing is the 250MM Z height.
I’m beating a dead horse at this point as you all have given me the info to kludge it.
Thanks
Derek
Ok I lied that horse needs a few more whacks 
I only use the AMS to hold extra spools of filament for long prints or to use up shorts from my non AMS P1S. When the printer runs out of filament and switches to a new spool does it use the cutter?
I gave the Wiki another read and I now understand why the exclusion area is in X,Y and Z. The spring lever is a hard stop and the head presses against it to push the cutter. At least that’s how I’m interpreting it. I guess spring loading it is the only way they could legally advertise a 256X256X256 build volume.
Thanks
Derek
I don’t think it does so this should work.
Just wanted to add that if you want to remove the filament you have to remove the stopper first. (duh)
I’m running a few short spools in the X1 AMS. I’ll try and keep an eye on it to see if I can observe it switching out the filament to see if it needs the cutter.
Jumping into this conversation with my own problems. I’ve done all the steps according to the wiki but I can’t clear the “Bed exclude area” section in the printer settings. It’s grayed out and all my fiddling about can’t figure out why it is greyed out for me.
Tried pasting a screenshot but the site won’t let me include media to this post. But the input section is greyed out with the exclusion zone coordinates unable to change.
2 Likes
Welcome to the forum.
What version of Studio are you using? You should be able to post a screenshot now.
(greyed out)
vs
3 Likes
Looks like it’s a known bug that will be fixed soon.
1 Like
I guess that would be fixed at the next software update but does anyone know how long that will take ? I have stuff to print and down want to back down to the last version if I don’t have to
2 Likes
I would upload my preset for no exclusions if I could, but this forum wont let me. Tell me where I can upload it and we can figure something out.
You can upload it to Makerworld, just upload a model with it that utilizes the full space.
I thought I was going crazy until I found this! I was sure I was missing something, just wasted 2 hours reading only to find it’s a bug 
1 Like
Has anyone seen an oficial statement that Bambulab actually are working on this? The only thing I’ve seen is third hand information.
Are Bambulab really aware?
1 Like
I’ve posted a potential workaround here…
1 Like