Unknown Filament Type

I have a P1S with AMS.

One of my spools in the AMS ran out the other day during printing. it was a Bambu spool.

Ever since then I am getting this error when I ask Studio to refresh settings.

“Filament type is unknown which is required to perform this action. Please set target filament’s informations.”

I tried power cycling, unloading and reloading the filament, changing spools to different spots in the AMS. None has helped.

2 Likes

Is it another Bambu spool you’re trying to load? Perhaps a bad RFID tag?

2 Likes

No. The problem occurs even if I remove all the spools. I believe now based on more reading that there’s some filament left in one of the little tubes. But I have never dealt with that problem before so I’m not positive how to fix it.

1 Like

having the same issue on both AMS units. Suddenly they do not allow mapping or show the correct filament. Suspect a software glitch. On one AMS I changed out all the cables and the buffer to no favorable result. submitted a ticket so maybe in a couple of days I might get a solution.

1 Like

The printer/AMS should read your BL filament spools because of the RFID chip in the spool core.
Non-BL filaments have to be configured manually.
This link is outdated and focuses on how to load filament in an X1 series printer but where it refers to the X1 digital screen, use the same basic screens you get in Bambu Studio.
AMS setup and Filament Loading

Stuff in the Prepare tab
Click settings icon and choose filaments you use or may use in the future.

Edit non-BL filaments

Tools in Device tab

You can click on the slot number of your AMS and it will do a Read action on the slot clicked. I’m hazy on this part but for example if you click A1 because that is a BL filament loaded spool it may a Read on all the downstream slots. If so, just let it do its thing.

Thanks. In my case it was a filament that had broken off in one of the tubes. It turned out easy to fix once I figured out (YouTube) what to try. Of all the possible places where the filament could have broken, mine was a very easy one to correct.

2 Likes