Please Bambu, add ability during First layer inspection (or manually) . allow it to cancel printing certain objects that failed inspection and continue with rest.
I realize this isnt the first request for this feature but I feel like the more we ask the more likely things will be implemented
It would rather help to not spam the forum with new threads for already existing requests, but simply answer to the already existing threads to add to them.
I think that’s asking a lot if you understand firmware the way I do, unless I’m mistaken keeping in mind I’m self taught regarding firmware and code
The biggest issue I forsee with your request is if you get false spaghetti detection which happens often if the camera is dirty (same thing with Octoprint) you could end up with only a fraction of the pieces printed or in the case of no detection have an item break loose and start a collision course with the other pieces
Your request would indeed be an amazing feature but I just don’t think the AI is quite there yet and it would be too buggy
The only way I think we could trick the AI into doing what you’ve suggested would be if we were to combine the print by layer and print by object in the firmware then cancel or resume the failed object
That would take up a lot of space in the firmware and slow down the processing which could cause many more issues in the firmware reading the G-Code
Another option would be a camera mounted on the extruder assy itself instead of fixed to the panel, that way the AI could detect failures quickly while covering the complete print area
Once again though, the more features we add the more likely we are to have multiple detection issues and a camera mounted on an BL print head would need to process the video at a much higher rate due to the speeds we’re printing at
I hope I’m wrong though because canceling a failed piece on a multi object print then resuming the others that didn’t fail would be a pretty neat trick
doesnt need Ai. Klipper and reprapfirmware have a object cancel function. where you just select which item has issues and it will ignore code for those items. during slicing each object is labeled in gcode so specific portions can be jumped over without affecting the rest.
Oh, you know, because who wouldn’t want to dig through ancient threads with outdated information and side conversations? Starting a new thread is just SO much better, really. It’s like shining a spotlight on your issue, making it the superstar it deserves to be! Plus, it’s always fashionable to be current, and with a new thread, you’re practically walking the digital red carpet. Let’s not forget the beauty of a clean slate, unmarred by off-topic banter – it’s like unwrapping a fresh candy bar of knowledge. And, of course, you’ll be opening the door for a whole new crew of internet superheroes to join your cause. Last but not least, your new thread will serve as a living, breathing progress report. So, go ahead and let that issue shine in its very own thread – because, really, why blend in when you can stand out? 
I’m not familiar with Klipper or Mainsail but if that option already exists then I’m pretty sure the software engineers at BL will take some of that open source and implement it into BS
I still don’t see how detection is picked up without a camera watching the print and using a predetermined set of values to catch an anomaly during the print ?
Obviously I’m a bit behind the curve on my understanding which is cool with me because I know I’ve got a lot to learn
Perhaps its what I define as AI is where my lack of understanding starts
Thank you @BambuLab for adding this feature!
hi! where is this option :(?
On the touch screen or in the Handy app:
Skip objects | Bambu Lab Wiki.
