AMS forgetting K Value (and management of multiple printers)

DamoclesSword commented 1 year ago

Bambu Studio Version

1.7.2.51

Where is the application from?

Bambu Lab github releases

OS version

Windows 10

Additional system information

No response

Printer

Bambu Lab X1 Carbon

How to reproduce

As a prerequisite to this, I am assuming you already have calibrations that have been generated and saved to an AMS.

There are two bugs that occur here. The first must be solved so that the 2nd one can be shown.

The First Bug

Open Bambu Studio
In the Device Tab, select a 2nd printer.
In most cases, all the K Values are now zero
Click the edit option on a filament
Click the Drop Down Menu for the PA Profile

Though my mouse is not shown due to snipping an image, you can see the box is green where I have clicked the drop down menu and nothing has happened. (this not just me hovering over it, the option has been clicked. You can tell because the grey portion of the background has a slight green tint which is not present when just hovering over it)

In most cases, this menu is bugged and will not allow for a value to be selected.

Windows registers the menu is open as if the menu is visible, though the menu never appears, you cannot click away until the menu is closed.

To resolve this:

Close the menu
Go the the Calibration Page,
Select Manage Results Here, you can see I clearly have values generated that were previously saved to the AMS (more on this in a moment)
Return to the Device Tab
Now, the AMS will have K Values and they will be editable

With this initial bug solved, a new one occurs in other scenarios.

BUG TWO Note: The same printer is still selected

Ensure that the AMS has the correct selected K value for each filament in the Device Tab
Slice a print and Select which printer to send the print to.
If the printer is not the printer that is selected in the device tab, at times, the K Value zero out on the printer the file was sent to. This is not everytime and potentially is affected by the printer being inactive for awhile. Or, it could be the same issue as the first bug.

The error seems to be dependent on what printer is selected in the Device Tab. The error is not a graphical one as I can see print quality differences on prints sent to a printer with the values at zero (that were previously selected) and ones where the print is stopped and the values are reselected.

As a potential extra bug, this is all exacerbated if you multiple instances of Bambu Studio open. Due to my use case, that is a requirement and you can issues where in one instance, the AMS has K Values and in another, they are zero.

Actual results

Above, you can see that for this printer, all the AMS values are zero. While there can be a delay when you first open Bambu Studio for the AMS to show a K value, this is not related to that.

Expected results

For the first bug:

the drop down menu should be selectable. However, once a K Value is selected, the AMS/Bambu Studio should not forget it.

For the second bug:

the AMS should not forget the K Value

For the Third kinda bug:

K Value should be stored on the printer such that even with multiple instances of Bambu Studio open, they all still know which filaments are in a AMS, so too should this be true with the K Value. It would also be nice to manually be able to input a K Value and edit the filament type.

Project file & Debug log uploads

Save for Github_Second Bug Report.zip

Checklist of files to include

[ ] Log file
[X] Project file

DamoclesSword commented 1 year ago

Given that this issue is still open, I am assuming this was not fixed with the latest 1.7.4 release? Could it also be confirmed whether or not this is a UI bug, or an actual software issue.

By that I mean:

assuming values were previously saved to the AMS, when the AMS shows "0.00" for the K value, but will display it once the "manage results" workaround is used, does that mean the 0.00 is what the printer would have used if a print was sent? Or, would the printer have used the saved K Value, but the UI is just displaying 0.00.

DamoclesSword commented 1 year ago

I can confirm with the latest version of Bambu Studio that this bug is still very much present.

ncr commented 1 year ago

Same here, we have a few carbons and this happens every day. A fix would be greatly appreciated!

DilapidatedMeow commented 2 months ago

I am still experiencing this in 2024!

bambulab / BambuStudio