Wondering how to store more than 16 K factors to my machine. When I do flow calibration now it prompts me to delete other calibrations I have done because it can only hold 16 k factors. That is worse than any ender I ever owned lol.
Just wondering, outside of any custom g-code overides, how to get bambu studio to hold k factors for each of my filaments?
Hi,
I have at least double the k-factors for the 0.4mm nozzle in the printer.
Way more if account for the 0.2mm and 0.6mm nozzle.
Without using g-code, you can edit the filament preset .json files. If this seems ok to you, I can share further details.
As JayZay mentioned , in the filament G-Code , but you do not need to edit the .Json
here is how you can do it , note the green highlighted line:
i am actually using the commented line above with BS, but for that first the preasure_advance needs to be edited via orca slicer , or manually put in the .json file . As i use predominantly orca slicer, the cloud transfers between the BS and oS my json files and on the filament setting has pressure advance option the same command is automatically added when using orca slicer if enabled in the first filament settings tab
I got the M900 g-code. Same flavor as marlin. However, See the image I updated in my original post. How can bambu get rid of that message? You would think a $1600 printer could hold more than 16 presets.
Until this gets figured out, G-code is my only workaround.
I am open to all options at this point. G-code is a temp solution. But I would love to see your json edits.
What makes me curious is the reason for your filament storage limitation. Somehow, your memory is complete, which I would try to address.
Regarding the alternative methods, you can check this thread:
Preassure Advance parameters storage
I quickly tested to see if it still worked without success. So, I am unsure if the process still works or if I just made a mistake. I will recheck and let you know.
If you decide to advance, I suggest creating a new filament preset and playing with it, just in case. To verify if Bambu Studio uses the PA value, export the .gcode and look for M900 K…
Changing the start-up g-code always seems more straightforward and less risky, as @vladimir.minkov shows. Also, it is worth coding the procedure if you are dealing with multiple filaments.
Off-topic: @vladimir.minkov lovely detail on adding detailed notes to g-code.
@off topic @JayZay : i use the advance tab to write comments when ever as at my age the memory refresh rate is a bit off and notes gets lost … 
not that old but …
Please correct me if I am wrong…
I checked the screenshot several times…
Why?
Because it is very odd…
I have no clue how many of these k-factor calibrations I have done but I do them for every new roll of filament…
I also have a whole heap of profiles in use…
Would it possible that the ‘historic’ in the popup suggests the historical calibration data but NOT the actual calibration data in use ?
I can’t replicate this error…
But I ASSUME you problem is an overflow problem.
For some reason you old calibration data keeps building up.
Maybe a bit hardcore but still:
Copy or export your profiles and other vital settings.
Not but copying entire folders but by only copying YOUR files.
Then do a clean install if Studio, copy over your files and try the calibration again.
There should be no issues of any kind to bother you.
Are you using the same profile for your filaments or do individual ones?
E.g.: 20 or so profiles for PLA based on colour, additives, silk and so on?
Or just based on ‘abusing’ the AMS and having like a generic filament profile where then just change the colour and k-factor in the AMS part ?
And probably a stupid question: Where can this limit of 16 k factors be found ?
Or did I really miss the entire point and you store this data on the machine and not in Studio ?
Short update:
It is a software bug.
The X1C does not have such a limitation.
Solution for the problem: ignore the alert message and proceed with the calibration, which will permit you to save the calibration value.
Details:
Details matter.
I was focused on the title and description and only peeked at the screenshot— sorry, @TheGunPsychiatrist.
I could replicate the issue, which only happens in the manual calibration; however, if I ignore the warning and continue the procedure, I can save the filament k value. I repeated the test three times.
In addition:
I communicated the problem to the Bambu Studio team and quickly confirmed a software bug:
I am also intersetd to see how to do this
I just want to thank everybody for their replies. All of you have shared a great wealth of information so great job community! On the last bamboo studio update what’s dropped I think a few weeks ago, bamboo Labs has apparently fix this issue. Next to being able to run 4 K - Factor calibrations to match AMS slots there is also a back door channel to add new K factors in the event that message pops up.
Under calibration you can manage all your K-Factor saves. You can also manually add new ones. Even when the problem was an issue before the update this is how I would add new ones.
Sorry it took me so long to respond to this I’m busy with two kids. I want to thank all you for the wealth of information that you shared though. It won’t go to waste.
Hello,
My wersion BS 1.9.7.52 Bambu P1P.
I have the same problem. I can’t save more than 16 results for K factor.
If I want to calibrate or enter a saved result, I get a message about the maximum number of results (16).
I did a fresh install, with and without downloading data from the cloud, and still the same error. Any suggestions? @ TheGunPsychiatrist
Hi all!
Has anyone managed to fix this? or is it a real limitation of P1P/P1S…I’m having the same problem with my P1S
Is a real limitation.
Workaround is tu use the Orca Slicer. Here you can store the k-parameter in the filiament-settings.
I just switched from BambuStudio 2.0.2.57 to 2.00.03.54 and got this error message. I continued with the calibration, got to the end point, and tried to save it. I got another error message informing me the calibration could not be saved.
