I recently got my Snapmaker 2.0 A350 (Woohoo!!)
After a 3Dbenchy and calibration cube that printed well, and a Snapmaker Vase that went fine until the half way and then had a nozzle clog so it printed into the air, I started attempting to print a goose, found here (specifically the
I created the goose with Luban (188.8.131.521 and an earlier version for the first tries) on MacOS 10.15.5.
During 3 attempts to print the goose it failed in the same way that I believe is a gcode issue (or possibly firmware, but not reproduced on the vase that got about twice as high). During the print at 53% complete (the third time, which had ever so slightly different gcode, might have failed as early as 49%) I heard a knocking sound which I assume to be the extruder contacting the back of the print and sending it flying. In the attached photo there appears to be a dent/melted spot from the nozzle in roughly the same position on each goose.
I’m unable to attach logs since I’m new to the forum, but if it would help debug I can attach them after awhile. In the two versions of the gcode the main difference I can see is the min_z and max_z goes from -/+67.7 in one file vs 0 to 135.4 in the other. No changes after line 40.
My Snapmaker is on firmware version, touch: 1.10.0, and controller 3.1.8.
Any ideas how to debug or prevent this sort of failure? (I guess my next step is to grep through the gcode and see if the Z position seems to go in the wrong direction.)