AMS filament K factor setting?


It seems that with Orca I can calibrate a filament and set K-factor etc in the filament profile.
In BS, there is no such option.
So how do I save the K-factor for a filament in BS?

Secondly, in the AMS, the wiki shows selecting a filament and having a “Cali” buitton, which doesn’t exist in the version I am running (
Nor can I edit anything if I click on the edit button for a slot. Can’t change the colour (for non-RFId spools), cannot change the K-factor or anything else.
I guess the K may be filled in if I run the Calibration from Device panel rather than the AMS panel itself but then it will ioverwrite the value I want with one Bambu decides is appropriate - I want to put my own value in, either in the filament profile of the AMS profile.

Can it be done? What am I missing?

Thanks for any pointers.

Orca Slicer refers to “K-factor” as “Pressure advance”.

If you want to do it in Bambu Studio without upgrading the firmware, add the following line to your filament start g-code (replace the number written in bold italics with your k-value):

M900 k0.03

In case of multiple nozzles, you must add the following script (replace the k value and delete the not-relevant nozzle diameters).

; Filament gcode
{if (nozzle_diameter[current_extruder]==0.2)}
M900 k0.02
{elsif (nozzle_diameter[current_extruder]==0.4)}
M900 k0.04
{elsif (nozzle_diameter[current_extruder]==0.6)}
M900 k0.06
{elsif (nozzle_diameter[current_extruder]==0.8)}
M900 k0.08

I am not aware of a more straightforward method.


I know. It’s not showing in BS.

Yes I can do it in start gcode but that means a mm ending filament profiles in BS and in Orca separately (they don’t sync) and that I can’t see in the Device interface that the right “Generic [filament]” is in AMS.

Sorry, I mis-read the question.

I have both BS and Orca installed, but Orca is the only one I actually use to print. Lack of a PA setting in BS is one reason why.

BS is adding features, but I still prefer Orca.

The current OrcaSlicer (1.7.0-beta) includes “Merged BambuStudio 1.7.4 changes to have better support for BambuLab printers.” I don’t see any reason to use BS.

I always used both slicers, even when the Orca had massive improvements regarding the Bambu Studio, just by precaution. There is no clue about BL plans, and despite Bambu Studio being open source, they can release addons, which aren’t. An example was the network plugin, which limited the Orca installation process until recent versions. Now, pressure advance values are stored in the AMS and not shared. I am not arguing about their policy, as they were and are pretty clear about it. Yet, the lesson learned from reading and listening to a few of their communications was that there are no guarantees regarding anything outside their closed environment.

For me, the script was the only solution that didn’t hinder any of the slicers, survive a printer factory reset, and ?maybe? future proof. Even so, having filament settings outside the slicer and closed can easily hinder its use.


PS: You can use both the script and orca slice PA value without any problem. In case values are different, Orca PA overrides the script.
Regarding the AMS, I still need to find the time to create and carry out a test to verify which one has priority. But I guess the AMS.

@JayZay it worked to sync between orca slicer and BS and use the visual value from Orca slicer and is applied to the Bambu g-code file , as still have only 0.4mm extruders for X1C, but from Prusa multiple extruders has different flow changes and sometimes temperature varies so for Prusa i created Filament profile per Extruder PLA 0.4 and PLA 0.6… Any way here is what i added and got sync automatically in the BS , the second command is actually what Orca slicer generates in the g-code, but i used the simplified version it seems to be enough not quite sure that L and M are correct but when sent with it also works and that is the default output from Orca slicer

M900 k[pressure_advance] ; BS transfer test
;M900 k[pressure_advance] L1000 M10; BS transfer test based on Orca slicer output

EDIT: requires first from Orca slicer to be ticket enable pressure advance

Once saved the filament from orca slicer then open BS and check if in the advance section the change is already there and yes

That sounds great - I shall check that changed made in Orca filament profile are reflected in BS gcode, but there’s no way I can see them in the BS filament profile.

It’s still annoying that you can’t change what the AMS shows - the Calib button shown in parts of the wiki doesn’t exist and Calibration will overwrite the manual calibrations.

There’s work yet to be done to get AMS properly integrated into BS I think.
Sometimes switching to P1P makes BS not show the X1C AMS filaments, sometimes I still see them even though I can’t use them.
If they do go away (as they should) they often don’t show up again if I switch back to the X1C.
I could use Orca for one printer and BB ambu for the other but then I would lose all Orca’s features for one printer - in particular the comprehensive calibration facilities.

All this should be seamless really.
Pity, as the printers are a country mile ahead of any of my others (though that may change when they go wrong and need Bambu support!)

I tested it , that BS gcode file generated with the above code gets into effect with the correct value from Orca slicer , just cant see one parameter the pressure advance, unless you open the Json file manually or just use the actual value instead of the variable ,

Not sure about the AMS but try Orca Slicer, it works perfect between Prusa , X1C and Ender
But i have seen a few times not updated the AMS information and had to close it and open the application again both on Bambu studio and Orca Slicer , i keep one Orca slicer opened per printer usually instead of switching between

i gave up long time ago on Bambu calibrations manual or auto really annoying well since i learned for Orca

Yes it is great printer for the price, but i like my Prusa mk3s+ with Revo six high flow extruder it is better for some tasks , and not cheaper with the mods and fitting(down) time :frowning:

@vladimir.minkov, many thanks for sharing. I made intensive tests, and it works flawlessly.
It’s an interesting finding, at least for me. So, calling cloud-stored Orca parameters from BambuStudio is possible. I am always learning. TY