I have an AMS that’s less than a month old. I recently bought Bambu PETG-HF and loaded the AMS with it. Upon loading, AMS briefly detects the filament spool’s RFID tag and shows the correct filament type (PETG-HF) and color (eg: orange), along with an eye symbol below the filament type on the printer’s touchscreen. A few seconds later, the filament type just reverts to ‘?’ and attempting to manually input the filament brand and type result in ‘?’ appearing again.
I power cycled the printer and AMS, but this didn’t change anything.
Any potentially useful information that is related to the problem
Up until today, loading non-Bambu branded filament and manually entering filament brand and type values has worked without issue. After the issue with the AMS failing to detect/store filament values correctly, attempts to manually enter filament info for non-Bambu filament are also failing. Is the AMS just toast? I’ve heard reports of poor QC on these units, but hoping this isn’t the issue on a nearly brand new unit.
If you have Orca studio open and connected to your printer it will do this. Orca studio doesn’t have PETG HF data yet in the release version. You need to add your own custom filament with the same settings as the Bambu one and manually select it to prevent this from happening.
I’m seeing the same issue here. Brand new roll of PETG-HF filament. Printer one print with no issues. Restarted the printer, now filament detects for a min and then X1C loses filament info. Original BambuLab filament. Three other Bambu branded filament in other slots has no issues, just the one in the first slot. This was also a slot where in the past Inhad and issue of it thinking that there was filament loaded when it wasn’t. I had to disassemble it to clean the presence sensor but it worked for a while with no issues after that.
Are you running more than one instance of Bambu Slicer (and/or Orca)? This really needs to find its way into Bambu’s faq, because I’m seeing a ton of posts with this same issue and I fought with it a few days ago. Mine turned out to be an instance of Orca that I was running in a docker container that I had forgotten all about. It was hung up to the point where I couldn’t get it to recognize any filament change, but the problem stopped instantly when I shut that down. I’m not sure why, but the PETG-HF seems to trigger it for most people, but the solution seems to be shutting down all but one instance.
I’m not using Orca buy I do have both Bambu Studio open on my machine and Bambu Handy open on my phone. But it’s also interesting is that I can move another filament from another slot to the problematic slot and that filament would detect fine and the working slot fails to detect the spool with issue.
One more thing of note is that this started happening after I updated the firmware on my X1C last night.
I am having this exact same issue with my new X1C and AMS. I also have an issue where the filament disappears after the print… whichever filaments are used turn to ? in the display.
