None of my AMS units on my two X1C printers will recognize this new filament either with the RFID tag or manually. Bambu Studio allows me to assign it on the Prepare page but not on the Device page.
1 Like
Is your AMS firmware up to date?
1 Like
I think it’s less of an issue assigning the filament type in Studio and more his AMS not detecting the RFID tag as outlined in @thumpernator1 's post. I think verifying the AMS firmware is updated and then if so, reboot the AMS and try reseating the filament might work after. I know I was able to auto-detect, but it could also be due to a faulty RFID tag, try another spool, if available
You’re completely correct. @thumpernator1 Can you check the software version number of your AMS via the X1C display, Handy or in Bambu Studio?
Yes, they are all up to date.
Tried two different rolls. Will not accept the RFID input nor will it accept Manual entry. Manual entry appears to work for about 10 seconds, then changes to a ? and shows color as white or clear.
3 Likes
What version of software is your AMS using? Is your printer connected to the internet or in LAN mode? What version of Bambu Studio are you using?
I’m up to date according to the printers and Bambu Studio.
Printer Firmware- 1.08.00.00
AMS Firmware- 00.00.06.44
Bambu Studio- 1.9.3.50
Connected to the internet as I have been since I started printing.
Sounds like it’s time to escalate this to a support ticket.
Works fine on my P1P printer with AMS. Currently have all three printers printing so I can’t really try anything new until they finish. But I think I’ll hook up the AMS that’s currently working on the P1P and try it on the X1C’s when they finish printing.
1 Like
I GOT IT! I had Bambu Studio open on another computer (meaning BS was open on two different computers) and when I closed one of them I was able to assign PETG HF to the AMS slot.
I’ve had BS open on more than one machine before and this had never happened. Strange that it did with just this type of filament. It would assign PLA all day with more than one BS open.
Very Strange! Thanks everyone for your advise.
5 Likes
Good job figuring it out and thanks for reporting back.
Uff I hate when something like that happens. When a new verified session is opened, it should automatically kill other sessions under the assumption that the user needs the new session to take priority.
I hope Bambu Labs developers are reading this, because having two active sessions battle for priority is not exactly best priority, and programming wise, it’s probably an easy fix.
Good that you figured it out - and now we all know, should anyone else experience a similiar issue (which is highly likely).
1 Like
I would not assume they will see a post here. I would suggest filing a feature request on GitHub:
1 Like
Good point - thanks, most of my brain is apparently still on vacation…
1 Like
im having the same problem
Welcome to the forum.
Which problem are you having? If it is that you can’t see the new PETG HF have you tried updating your configuration and adding it to your filament list as detailed below?
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.