I have 12 A1 w AMS Lites in a classroom… everyone has their own laptop… each has Bambu studio installed for slicing… Every one of us experience the same issues… when changing filament colors on device screen, then going back to colorize, then sync… Studio freezes, then closes… crashes. About 30% of the time… Some of us, when possible, just use PrusaSlicer, and color by layer at that point. Many lose their work, despite the autosave feature… reboot, restart, dont matter. I suppose if youre not changing colors on your rack that often you may not notice as much… but we’re changing colors ALL the time. Anything We doing wrong ? missing something ? thx in advance.
What OS? What version of Bambu Studio? What does the long, detailed OS crash report say?
You have many people probably all logged in at the same time to the same account that has all 12 printers? Or one account for each? Or just lan mode binding? That may be part of the technical problem to include logs about
This is true, at times… multiple on the same wifi… However, this occurs at home as well, they all use their own laptops… some take the printers home for a week or so . I notice it at home as well… As far as I know, we’re all using PC Windows… dont think anyone using mac , could be wrong. ALL printers purchased 3 months ago, NEW, Im sure not all are on the very latest firmware. but some are… didnt matter… ALL of us have same problem… about 1/3 the time while syncing. It just stalls, hourglass for a sec… then closes. no msg.
OK, that sounds like it’s logging a crash or other error.
Can you check and see if your logs folder has reports for the times it crashes on you?
https://wiki.bambulab.com/en/x1/troubleshooting/bambu-studio-log
Bambu will need those logs to figure out the cause of the problem.
I’m having the same issue with my A1 + AMS Lite. Started happening in the last day or two, and I haven’t updated Bambu Studio recently.
When I try to sync filaments using “overwrite”, Bambu Studio crashes completely. Before it crashes, it shows 5 filament colors even though I only have 4 spools loaded in the AMS Lite. It also shows one PETG filament as unmapped - I did have PETG loaded at one point, but I’ve unloaded it and printed with different filament since then. So why is it still showing up?
I’ve tried downgrading Studio to an older version (v02.03.01.51) - still crashes.
Here’s what’s weird: I just tested my X1C using the same sync process with “overwrite” and it worked perfectly. No crash, no issues. So it seems specific to the A1.
This really needs to get fixed. I don’t have a farm of 40 printers, but this is making life more difficult when I’m just trying to get work done. The software not knowing what filament is loaded means I have to either risk the crash every time or manually enter everything.
Does anyone know if there’s a fix being worked on or already in place? How can I contribute my crash logs to help get this corrected as soon as possible?