Hi, I use the last firmware on my X1C and I use the last Bambu Studio and I have a bug with the auto fill feature.
I have 2 spools of Bambu Lab PLA Basic Red and Blue. When I put in my AMS, the 4 spools was recognize, but in Bambu Studio, the color of the 2 red and the 2 blue are different (when I click on the color at left of the filament slot in the main screen of Bambu Studio), the color code (six colon with number that make the color) was different. The autofill ams feature doesn’t detect the backup spool and when I have print, the backup feature and not take the the spool. It’s the first time we see this problem!
Is this still available? I just got back and it isn’t letting me update to the beta. I have been part of the beta testing for over a year and restarted the printer, no help.
I’m guessing you are part of the private beta test group. The release is for the public beta test group which you’re probably not a part of. To join it you need to op into it via the Handy app. They are two separate groups. Confusing I would agree.
Agreed. More so when there is no preceding private beta build.
Maybe an adjustment in terminology is in order, such as “Public Preview” or “Release Candidate” to help differentiate from the Private Beta builds.
My X1C runout sensor works with AMS. Yesterday tested for all 4 slots. 3x so-so empty rolls and last new roll. Start printing and watching first change - OK. Then I go to sleep. At the morning I see succesfully printed and three empty rolls.
But I have problem when using ext spool. Without AMS the filament sensor not active. Here my print fails.
Firmware 1.8.50.18
AMS 0.1.6.60
same issue here;
40+ X1C, all running beta firmware 50.18
2 issues;
-without AMS the filament runout sensor does not trigger a pause in printing if it runs out. filament sensor does work and detect if filament is present (tested by loading filament) but printing is not paused. can replicate on all printers.
-all printers have 256gb sandisk SSD. if SSD is inserted, when sending a print it will stop with “error parsing print” before starting the print. removing the SSD fixes the issue. all SSD’s test without issues.
Huh, I had this happen too I thought it was because i’d skipped one part because I didn’t need it and it messed up the gcode but I had an AMS slot run out and it was set up to refill fromm 4 to 3 but when it ran out it just carried on air printing (there was a warning it ran out… it just didn’t stop).
Not had that happen again though so maybe it was related to the skip