Occasionally RFID filament detection fails to identify the Bambu Labs filament. Re-inserting the filament and clicking the refresh button in Bambu Studio also does not fix the issue. I find that doing a hard restart with the power switch in the back does the trick and things work properly after that. It seems like others are experiencing a similar issue.
Is there anything I can provide to troubleshoot the issue which seems to be a bug in the AMS?
Which is a bug. @BambuLab anything we can do to help eliminate this bug? It is annoying especially given this requires a hard reset and there is no way to reboot remotely.
Happening with a new Bambu Lab Red ASA for me. Practically the first time I’ve used a Bambu Lab spool in the unit since I bought it…and then it doesn’t save me one bit of time or effort. There’s little incentive to buy their branded filaments if the RFID stuff doesn’t work.
Unfortunately, this seems to be still an issue. Just bought a P1S with AMS. After working corectly for the first few prints, I also encounter this behaviour. No reliable detection of Bambu filament. This is really annoying, because there is no advantage using/buying Bambu filament. Hopefully this will be solved soon.
Same problem, first spool i used it worked than nothing since…guess i should start using other companies filament if i am not going to get a benefit…
Any fixes on this at all? I recently purchased Bambu PA6-CF, which the AMS detected fine, but since then i’ve swapped that filament out for some Generic PLA Silk. However, the AMS refuses to believe that the PA6-CF is not there and continues to show it instead of a ? , which is normally what I see when I load Generic PLA types. It’s almost like the SW just assumes it is the same filament type when you change filament to something that doesn’t have an RFID tag. Gotta be honest this seems like a very easy SW fix guys?