I cant be the only one who has been tripped up by Bambu Studio reassigning numbers whenever there is an empty slot in the AMS. Currently My slot 2 is empty. Instead of marking it empty, Studio reassigns 3 as 2. I know what filaments are in each slot. Now I need to reassign filaments when I import a multi color part.
Hi Philip,
Which numbers are we talking about, these?
Those are not tied to AMS slots, they’re numbered independently and are simply consecutive (in the order in which they were added to the project). With only one AMS on a printer and using the sync function, I could see how they’d often match, but that’s a side-effect. The mapping to actual AMS positions (filaments) is done/verified when sending a print (via Studio, or on the printer screen if initiated from there).
-Max
It is like this since ever (at least since I have my P1S and AMS).
As MaxThreeD said, an empty slot is not shown in the Project Filaments in Bambu Studio, it just assigns numbers to the slots with filaments. Numbers in the Project Filaments list have nothing to do with your AMS slot numbers.
In my AMS the slots are used like
Slot 1 => white PLA
Slot 2 => support material
Slot 3 => empty
Slot 4 => white ABS
external spool was PLA wood
In BambuStudio I see:
Number 4 is actually the external spool.
If I want to print in ABS, I assign filament “3” to it:
But then, just to confuse you more, when printing, it shows the correct AMS slot:
[EDIT] It is the same in Orca Slicer btw.
1 Like
Is the OP labeling the filament colors & types in the printer’s filament ID selection? The system needs to know what the filament is and where to find it. Needs to know what type of filament is being loaded & unloaded for nozzle temps.
I would simply like it to match what is displayed in the filaments display on the printer.
And if we don’t band together and ask for it to change it won’t.
I need to dry my desicant.
Don’t leave any empty AMS slots and then it will match (probably, most of the time)… 
Anyway, I have to respectfully disagree, from my point of view. For the way I work, the project defines the filaments, not whatever happens to be in an AMS at any particular time. Mapping project filaments to AMS/external slots is a last step (and usually the automatic mapping works w/out any changes needed). And, I think having numerical gaps in the project filaments list could add confusion, needing to explain that it matches the AMS slots. Then there’s the question of how external spools would be numbered. And what happens if one opens a project with filaments not matching current AMS filaments/slots? 
-Max
I guess we have different workflows. I normally keep the same filaments in the same slots. Your reasoning does make sense. I need to break free of these self induced shackles.
1 Like