Open pennystockss opened 1 year ago
1 One machine may need different K value, even with same filament, after a long time using. 2 Third party printing filaments, with same kind and brand but different batches, often vary greatly in K value. 3 When printing sliced file(from other people) in SD card but don't have same filament, saving K value in printer can help user to get better quality.
I would like to add to this request.
The ability to set K value in the filament profile would really be nice but also keeping the K value override in the AMS section would also be great to override the profile.
I find it too frustrating to document the K factor for each of my filaments myself and then have to look them up and copy them into the Device tab / AMS area of Bambu Studio every time I change spools.
As a workaround, I have been adding Start G-Code with the setting for each of my filaments:
M900 K0.020; adjust linear advance
I wish it were simply a setting in the filament profile area as it is in Orca Slicer.
@SaltWei I understand that it may differ per-printer and per batch, however with the P1-series we have to find these values manually and yet there is nowhere to store all these values within Bambu Studio. I like the idea of storing it in the filament profile but being able to override it per-printer from the Device tab, if-needed, but a core value should exist in the filament profile as a starting point.
Edit: Also wanted to mention that if K the value varies between machines, but was stored in filament profiles, we could simply have a copy of the filament profile for each of our machines with separate K values in them.
I agree with storing the k-factors in the filament profiles
I'm finding my self printing a single layer calibration square sheet in order to fine tune the k-values.
This is because a single line isn't enough data to select the correct value from -- a lot of them look good as a line, but terrible when printing.
another thought is that machine k-factor deltas are likely to be consistent? for example M1 might have higher k-factors
fine-tune the filament k-factors for that specific machine
// k = sum of deltas
K = filament_base_k + (object_k_delta || 0) + (machine_k_delta || 0)
// filament profile
{
...
"k-factor": {
"Machine_001": 0.02,
"Machine_002": 0.025,
"Machine_003": 0.015
}
}
print 7 square sheets with a 0.005 k-factor deltas
@softwareByAndi you might like the PA Tower calibration print better than the lines. OrcaSlicer has it built in. It's a lot easier to read (especially if the filament color matches the bed) and a lot easier to clean up. Does requires measuring, though.
@softwareByAndi you might like the PA Tower calibration print bettee than the lines. OrcaSlicer had it built in. It's a lot easier to read (especially if the filament color matches the bed) and a lot easier to clean up. Does requires measuring, though.
nah, the PA Tower shows the same data as the lines test. The sheets show 2 important data:
I have just had to reset my printer back to factory settings as it was complaining about something... This now means that I have to re-calibrate all my K values again. It would be great to be able to store these in BBL and push them to the printer.
Throwing support in for storing K factor values in filament profile setting. Even if just a note section to reference.
Whatever solution you come up with here also need to address the issue that all K values are forgotten at poweroff.
I mean, you can even resume a print that halted at a power loss... BUT you'll resume it with all K changed to 0.00 mid-print?! Come on.
Just to confirm, K values are NOT overridden in the X1C's firmware when a print job w/ filament profile(s) is sent to the X1C, correct?
I would also prefer when the k values are saved in the filament profiles. It's annoying to write down the values by myself somewhere and enter them after every change.
I back up this idea. Come on bambu release an update
Whatever solution you come up with here also need to address the issue that all K values are forgotten at poweroff.
I mean, you can even resume a print that halted at a power loss... BUT you'll resume it with all K changed to 0.00 mid-print?! Come on.
I have found out that if I store a PA calibration with its default name (eg. Bambu PLA Basic
) it will survive a power cycle, but if I (as actually suggested by the calibration instructions) add color to the name (eg. Bambu PLA Basic orange
), it will not (the profile is there but I have to manually enable it - a tedious process with my two AMS units and double that for power users with four of them). That's a sad shortcoming as different colors tend to get different values. My current workaround is to store the most common result (such as 0.020 for PLA) with the default name and all other results with an amended name. This way I get fewer ones to manually correct.
Some documentation of this current behavior would have saved me some time and some suboptimal prints 😢 and a fix so the printer also remembers the non-default-name settings should be pretty high priority IMHO.
Here's a thought with working with Bambu brand filament with RFID tags - associate K values and flow rate values to the RFID number on the filament roll. Since the printer has an odometer, once the roll has been used it automatically deletes that information from the printer. Or if you don't use it up and have left over filament you know you won't use, be able to delete that information manually.
Even better would be able to write the K values and flow rate to the RFID tag. That way you can takeout then later put it back in later or move rolls of filament in the AMS and not have to worry remembering what value goes with what spool. But I believe that would require an updated AMS unit so the RFID reader board can push the information to the writable RFID tags on the spool. But that could be a newer upgraded AMS unit and updated RFID tags on the spools.
P.S. I would be nice if Bambu would allow other filament manufacturers to use RFID tags on their filament also (with a licensing fee if needed).
+1 for actually saving the K-Value in the filaments profile. The current behaviour is user-hostile and not befitting the level of automation Bambu Labs printers are capable of.
Thank you for the consideration.
Please make this happen!!
I add my voice to adding the K-factor to the filament profile. it is really annoying to have to reconfigure it every time I restart my printer (X1C). I tend to turn off my printer when not using it and I often forget to reconfigure the k factor when starting it back. Adding it to the profile would be a set it and forget it solution. Maybe hidden in the advanced settings or something similar.
Is your feature request related to a problem? Please describe. Sort of. Having the K Factor on the AMS side seems counter intuitive especially if changing multiple manufactures and types. It should be on the filament side.
Describe the solution you'd like An option to change K Factor in the slicer filament profile instead of the AMS section. I would do it with Gcode but I'm unsure if AMS would override it.
Describe alternatives you've considered Changing Gcode for filament.
Additional context