I don’t think we have either. Especially since I don’t think it would have much effect.
But here’s another interesting wrinkle.
Following the successful prints of older GCODE, I realized one thing I hadn’t done since making all the other adjustments. Trying the original slicer again. So I figured it’s worth eliminating that option.
Take a look at the pic. From left to right in order of size and complexity, and the same order I printed them. All on the original laptop, Cura 4.11, and the original profile.
Small Emblem, success
Medium block, success
Urn print, failure at approximately 45%
From that, I’m hypothesizing something - something is corrupting the printer’s ability to read or process the Z axis portion of the G0 commands. It isn’t immediate, but occurs during progression, so perhaps the printer can complete one or two small prints before it starts to fail or it completes a portion of a bigger print, then fails. The failure remains continuous for all layers about the base layers until something, somewhere resets, and the process starts over again.
Maybe I’m way off, but I can’t see what else makes sense in terms of a logical process.
wonder if it’s a memory Leak, Try the same set again but power off and power on the printer in between each print.
Back row is the prior set of prints. Front row is the repeat with power off between each print.
I’m more convinced than ever that this is hardware at this point. Either something with the mainboard control for the Z Axis, the wiring, or the stepper motors, though I’m less than convinced it’s in the motors. The calibration cube I printed is higher than the two failed prints here, and the larger prior prints were much lower. I think it has to be a malfunction that occurs after it processes a certain volume of print or volume of code.
I tend to agree however with a caveat.
I think the stepper drivers are overheating and causing the failures.
If you do a print with very little Z-axis movement, i.e. no mesh bed levelling can you print the item taller without failure than something with Mesh bed levelling enabled?
Let’s say for example you take your previous calibration cube, increase the infill to 50% and ensure the G29 is in the start Gcode I would expect it to fail much sooner than the same printer with a 50% infill and without a G29 in the start Gcode.
I am wondering if your calibration cube that was successful has the G29 in the start code?
The only reason I am increasing the infill percentage is to force the Z motors to move more as it’s moving over the print surface.
ON the same note, Is the fan for the mainboard working? Just to ensure the stepper drivers are staying cool?
I’ll have a look at the cube gcode and give a try on the taller print. As far as I know all of the fans are working. They’re definitely audible when it’s operating. I’ll double check again today, and when prints are finished I’ll open it up and check for certain. It’ll give me a chance to inspect the mainboard connections too. I’ll let you know how it pans out.
ok, sounds good, Still scratching my head on that. Cannot think of what else it could be.
Welcome to my daily dose of frustration and what’s rapidly approaching despair.
From left to right:
60mm high calibration cube at 50% infill with ABL
Prior failed urn print for reference at ~31mm
Failed STL print. Known good STL, able to print no issue on my Ender 3. Height is approximately 1.65mm. Printer read 2.4mm when I stopped it.
60mm high calibration cube at 50% infill without ABL
All sliced with the same stock Cura profile. In fact, I didn’t close Cura in between. I literally just cleared the build plate, added the next object, sliced and saved.
This makes no sense. At this point, the printer is completely useless unless all I want to print are calibration objects. If I hadn’t just paid out for it in August and if I had money to replace it, I’m at the point where I think I’d throw it out.
I reached out to Creality support too. They sent me back some very generic maintenance videos which I did follow and replied to and provided the photos and videos I have of the problem and have not gotten a response since.
I can deffinately see where the frustration is coming from.
Are you local to us? do you mind sending me the Gcode and / or STL files for the failed items and I will run them on a printer here in the store?
Only other thing I can think at this time to troubleshoot it difinitavely.
I’m not local - in Newfoundland here, but I can easily send you the GCode and STLs.
I’d prefer to send them via email if that would be okay - these are STLs that I bought and have commercial licensing on, so there may be issues with posting them on a forum.
No problem you can e-mail them to me direct.
I will DM you my e-mail address.
Thanks for sending me the STL files
I am finishing a print on a test printer right now then I am going to run yours.
Any progress on the test prints?
So interesting part, I have run the cube Gcode, It measures 40x40x60
I have the untitled print running now, going to see if it exhibits the same behaviour
the next print looks like its printing ok, Do you know the hight its supposed to be?
The InnerSpine should be approximately 17mm total and the dice lander urn should be approximately 69.7mm