Half a year P1S user, mostly a pleasant experience.
My brand new X1C did two-three small test prints, OK. I had to print some large (BL) ASA supports, I have printed one, checked, OK, all good.
Second long print with the rest of three supports, scheduled over night. Stopped some time in the night for some “possible Spaghetti detection” and DID NOT continue. The BL ASA cooled down a bit, contracted 1%, so I got a 1mm gap in my print…
While printing ASA, stopping the print is another way to say:
“Your print might not be OK, let’s fail it for sure”
So I ended up with the largest failed print in years.
The software should be updated - while printing ASA it should not stop or just briefly stop.
You can adjust the sensitivity of the spaghetti detection to make this less likely to occur. I have found everything above “Low” sensitive to be a bit trigger happy.
Thank you - I have completely deactivated the AI support - it did enough damage.
The issue is different: the state of the art BL company should have implemented in the software a “no ASA printing stopping” policy - because otherwise the AI turns a potential failure in a certain failure
I am really surprised to discover such “basic” bugs in a software that is in use for a number of years.
Well, I am still a bit careful with the “should” in 3D printing.
With the Bambu’s, printing PLA is a bit like riding a bicycle. Put the helmet on (dry filament, clean build plate) and there’s a very good chance to get spectacular prints with only the odd tour failure from an unexpected squall (I swear my filament was dry ).
With anything else than PLA, it is a bit more like driving a hire car with all support systems doing their own unexpected thing in their very own manner .
).
.