So on my last print I was down to the last bit of filament and was ready with a replacement roll to let the print finish when it ran out. Which it did, but what I didn’t realize is that the printer would not verify (or at least assume) what filament was put into the ams after I continued the print…
So when I set up my next print I did not realize that filament in the ams is now labeled as unrecognized (?) and it mapped my new print to the wrong color which caused me to waste 4 hours and a bunch of filament. great
I think this is pretty standard. And if it isn’t all my printers have been doing this for ages, and I assume always. But maybe it was a firmware update many moons ago.
This is the expected behaviour, be a that is how they built it.
It is not the correct behaviour, because they built it wrong.
Until they fix it, get into the habit of double checking your device choices before you printer.
Measure twice, cut once sort of thing.
The “problem” provides a benefit, you can change the filament mid print and it doesn’t perform the identity check, this lets you use a non-matching filament without it moaning.
Remember, the print window shows you the swatches for a reason, check and double check.
I do not think Bambu Lab staff use their own printers, if they did, they would notice these ids and fix them before we ever saw them.
i have no problem with the mid print non-matching filament feature. i just used it the other day. that’s no reason however it shouldn’t simply run an id check on the new filament after the print is done so future prints work properly. i was in the middle of printing 35 different objects. i don’t check the color swatches on every single one of them on the off chance something has changed since the last 34. but at least now i know what to expect. normally I would just load the filament so the system would automatically switch to the new roll just couldn’t in this case because the other 3 slots were loaded with filaments that were also being used… anyways live and learn.