Has anyone been able to use the new PETG Translucent in the X1Cs AMS? My AMS recognizes other filaments no problem and reports to be on the latest firmware. (00.00.06.40) With my X1C running 01.07.02.00
Tried multiple slots and no luck. Can’t even manually set the filament type on the AMS but CAN in the slicer.
Any help is appreciated!
I’m having the same issue. I printed with the basic petg preset which seemed fine although I think my translucent petg was very wet out of the packaging because half of the part printed nicely, and the other half is completely foamed up and was crackling out of the nozzle
I’m having the same issue with PETG translucent light blue, I was able to set the filament no problem manually, but the AMS would just not detect it automatically. I wonder if there’s a problem with the RFID tags on PETG translucent. I’ve got a second spool in another color on the way, I’ll update here if it doesn’t auto-detect either.
Same issue here with the light blue translucent.
Anyone came out with a solution so far?
No solution, I just set it manually. This is the only spool from Bambu that has ever had the problem for me and I’ve gone through dozens now.
having the same issue with purple translucent lokos like the tag is on the wrong side of the spool compared to my other spools.
Welcome to the forum.
Normally there is a tag on either side of the spool.
Having issue with petg translucent, it will be recognized by ams/x1c but then it disappears. also try to manually load it, but that disappears as well.
Same problem.
Using Light Blue and Teal.
Both I cant seem to get to play with the AMS>
Here is what I just did.
Took all the filament out of the AMS, Turned the printer off.
Waited 10 seconds,
Turned it back on.
Loaded Filament, 2x Translucent
Went to my PC, loaded a print, Picked the printer, Clicked Sync AMS.
It pulled the correct information in the filament list.
Going to print now.
Its working.
I’m not sure why the AMS has trouble.
But a solid reset and refeed seemed to have worked for this this time.
It’s a bug in the AMS firmware. Sometimes it loses the connection to the reader chips. Turning it off and on fixes it.