Problem:
No display of the current filament in AMS - incorrect display of the filament currently used for the print job when using multiple AMS (Automatic Filament Storage) units simultaneously
Background:
I have been using the BambuLab X1C for 18 months without any problems.
During the last Black Friday sale, I purchased a second AMS to complement my existing one.
Connecting it to the BambuLab X1C with one AMS was seamless.
The two AMS units are filled with different colored filaments, as well as with the same filament spool but with varying amounts of filament in each unit (all PETG).
For example, each AMS unit contains a spool of black PETG with a corresponding RFID chip.
Bambu Studio recognized both AMS units, and the device view correctly displays both AMS units with their respective contents, and they are correctly integrated into the respective print jobs.
Bambu Studio recognized both AMS units, and the device view correctly displays them with their respective contents, and they are also correctly integrated into the respective print jobs. Unfortunately, Bambu Studio does not display the currently selected filament spool for the print job in the device view (highlighted connecting line between the current filament spool and the printhead).
Only by switching to the individual AMS (Automatic Print Management System) via mouse click does it show which filament spool in which AMS is actually being used for the print job.
I have attached two screenshots to this post illustrating this issue.
Image 1: The print job using the black filament spool from AMS No. 1 is not displayed when printing begins without the corresponding update (mouse click on the AMS).
Image 2: Only after clicking on AMS No. 1 is the actual and correct use of the black filament spool displayed.
This situation is problematic because, without the corresponding update of the view of each AMS connected to the BambuLab X1C, it is impossible to see which filament spool is currently being used for the print job.
The background to this is, among other things, that I want to ensure that, for large print jobs, the current print job proceeds without changing the filament spool, or that the spool with the larger supply is printed first.
The Bambu Studio software should therefore automatically update the status of all AMS connected to the BambuLab X1C whenever a new filament is selected for a print job, since you don’t usually check the status directly on the AMS itself.
I hope I’ve explained the situation clearly for the Bambu Studio developers, and I’m hoping for this small software improvement.
Your users are already thanking you.
