This is still an issue on my X1C. Nothing works
Same issue on my H2D, newest FW on printer and AMS 2 Pro. Running bambu studio beta 02.6.1.51.
I have several custom filaments visible on both the printer itself through the display and on the device page in bambu studio that i can assign to AMS slots, some are very old (2+ years, before i even had an AMS) and some are quite recent, perhaps six months old.
I added a bunch of new custom filaments the other day and i cant seem to make them visible on the device page or on the H2D screen, i’ve tried the following solutions:
- Re-bind printer. (2 times, once through the handy app and once through bambu studio)
- Cleared the %user%/appdata… bambu studio (beta in my case) cache.
- Restarted printer, bambu studio and PC.
- Enabled LAN-Mode
Oddly enough, when i deleted old profiles that were visible on the AMS they immediately disappeared from the device page and from the printers AMS interface.
I finally found a solution to this issue! (well, the variant i had at least)
After some digging in my filament .json files i saw that all my newly created filament profiles that didnt show up in the AMS had a filament id starting with ‘GF_’ followed by random capital letters, while all other profiles had ID’s with lower-case, upper-case and numbers without special signs.
I also found a log_iotc file (C:\Users\%user%\AppData\Roaming\BambuStudioBeta\log) with this line:
[26-05-12 18:18:33.735843][D][7924][IOTC] [IOTC_Check_Session_Status] Error: Not Initialized!
[26-05-12 18:18:33.735843][D][7924][IOTC] @@@@@ IOTC_DeInitialize called
[26-05-12 18:18:33.735843][D][7924][IOTC] @ErrCode -12 - Line (13010)
I went into windows firewall settings and made sure Bambu studio was allowed on both private and public networks (I also noticed i had an instance of orcaslicer that did not have permissions on private networks, i change this one too just in case)
After this any newly created custom filament instantly shows up when assigning filament in the AMS (both on the printer and in the slicer)