I was having the same issue, thanks for the tip. I created a guide for this here: Solution: Printer not saving a custom filament profile to an AMS Slot
Any update on when we can create custom filaments for the A1?
Just tried this on H2D. Did not work. Recent firmware and latest Studio. I did calibration, no result, I did log-off/log-in, no result. I see my custom filaments in Studio but only in projects so I am able to use them for slicing. NO way to set them on AMS using Studio and neither have them in printer menu. Connected with cloud.
Latest BS (yep, that’s about right) and firmware. Somewhere in the flurry of recent updates, a few recent FR calibrations vanished. BTW that 16 calibration limit per nozzle is total BS - I really, really wish I had known all the ways that Bambu Labs intentionally tries to cripple using anything but their filaments before purchasing this 2 months ago. Calibration for custom filaments has been a a complete nightmare from day 1, usually requiring at least one, often more, application restarts and often at least one or more hardware restarts per filament. 2 months ago this also required deleting the login information and reentering it every single time. Things got progressively better for a while and a recent update’s release notes suggested a bug in the calibration was being fixed. And at first I thought it had. But then a number of bug fix updates appeared to re-introduce the problem even worse. Furthermore, it appeared to have lost some of the recent filament configuration changes and now I occasionally hit a BS lockup which says I have to update BS but BS is already at latest update. This happens when trying to contact the cloud service. Is this a security feature? Can’t break into something that is bricked?
Apologies for the rantings but I abhor when “upgrades” reintroduce old bugs, particularly in a seemingly destructive way. Seems like there’s some inconsistency with a method of storing filament config data and a new method (incompatible data structure?). That kinda thing does happen, but seriously, automated test cases should find that kinda ■■■■ as part of the QA cycle. I bought this when Core One shipping was slipping and figured the tradeoff for the closed system requiring comms with the mother ship was worth it for a system that “just worked” and didn’t require me re-entering work mode every night. I should have been patient but other things looming sped up my decision. Anyone else re-experiencing difficulties?
I serious doubt anyone from BL looks at these threads, but maybe if big mother is watching, please let dev know that they need to get back in the game - it’s time for them to knock one out of the park in a good way.
I can’t believe y’all have got me riled up enough to break my lurker shackles. My therapist is gonna be livid. My gal is tired of hearing me scream murderous things from my office on the other side of the house. And now I feel like I’m getting sucked into trying to reverse engineer this BS. A rebound like this doesn’t sit well with my stomach and won’t be good for anyone within mushroom cloud radius. Please, for the love and sanity of all things good and pure, help me contain this beast - fix your BS.
Ok, I’m gonna have to walk back some of this. Somewhere in the process of restarting BS, power cycling the P1S, making a backup of the BambuStudio.conf, pulling the SD card and backing it up, and deleting and rebinding the network connection, BS found my ObXidian nozzle again and the recent calibrations were found there. The release notes did mention originally that support was added for the new ObXidian nozzle collaboration but that one couldn’t select it in BS. During the turmoil I think it was lost on the P1S device and only appeared as a hardened nozzle. I suspect I unintentionally installed the Beta release implementing this functionality. Somewhere in the production release versions that were intentionally installed later, configuration/calibration items were lost. It seems that the most recent version brought this data back. I find the upgrade process a bit awkward, but this one’s on me. It’s totally understandable that beta features would cause some issues, and it’s surprising that a) the lost config/calibration data was not lost and b) a wipe and reinstall wasn’t required (although that might be a good idea). Kudos to BL dev’s for that resiliency.
I still think the whole calibration process is unnecessarily disjointed and clunky and that’s certainly worth a good rant. But I went through the process a few times to get some of my filaments moved over to the new ObXidan nozzle printer profile and things have been running pretty smoothly. I’ve now gone a solid 24 hours or so since a power cycle of the P1S was required. BS crashed but understandably so when painting supports on a very complex model with a bunch of other things running on an Apple silicon Mac Air suffering a severe lack of RAM and very little space left on the SSD. I’ll be dialing in a new filament soon but I’m hopeful this will go better. I just wish that 16 calibration limit was higher.
I’m having this problem with my P2S AMS2.
No custom presets showing in BambuStudio or Handy.
I’m new to AMS, not Bambu Printers. So far this is the one finicky thing I’ve experienced.