thekwijibo

A quick question concerning the new "Stepper motor disarming during pause at height" feature. In Cura, it states, "Disarm Timeout - After this time steppers are going to disarm (meaning that they can easily lose their positions). Set this to 0 if you don't want to set any duration." I'm a little fuzzy about this. Does this mean that if you select 0 for Disarm Timeout, the steppers won't timeout? Or will they immediately timeout?

Thanks for looking into it for me. If there are is any future interest, I could upload some video of the stuttering/pauses if that helps. Since nothing in my settings stood out to you, I'm assuming it has something to do with Cura. Hopefully this gets fixed in the next update. It looks like I can mitigate "most" of the pauses and subsequent blobs by slowing down significantly. I might print PETG exclusively for a while.

Thanks a lot for looking into this for me. Model geometry is a simple ellipse with a thickness of 0.8mm for two walls of a 0.4mm nozzle. Elipse_Project.3mf

I tried your suggestion, and still encountered significant pauses and bumps. Max Resolution: 0.1 Max Travel Resolution: 0.1 Max Deviation: 0.02 My previous conservative values: Max Resolution: 0.65 Max Travel Resolution: 0.7 Max Deviation: 0.075 Experimental maximum values: Max Resolution: 0.9 Max Travel Resolution: 0.7 Max Deviation: 0.1 Sanity check absurd values: Max Resolution: 1.5 Max Travel Resolution: 1.25 Max Deviation: 0.25 Even when printing around 20-40mm/s there are significant zits and pauses. There is very little difference in print quality during each iteration which surprises me. I can share some Gcode if it might help. Printer hardware is fine. Other slicers are producing near perfect prints of the same test ellipse geometry at around 40-60mm/s

For anyone following this, I got some pretty dramatic improvement by disabling "Wall overlap compensation" in Cura. I still have stuttering issues and random blobs even when printing slower, but significantly less than before.

Dsplendido, Thanks for the solution, even though not exactly what I was hoping for. I suppose Cura might be moving forward with 32-bit support and leaving the 8-bits in the dust. I'm glad I'm not the only one struggling with this issue. I've been putting off buying a 32-bit board, and possibly printing/building an entirely new 3D printer. This might be the push I needed.

*update* I've made some slight progress... I've been able to get a moderate improvement by reducing the mesh significantly beforehand in addition to slowing down the print speeds down to where I normally print PETG at (20mm/s). There are still occasional imperfections and pauses, but they are reduced by about 70% Slight progress, but even at a painfully slow printing speed, there are still significant pauses that cause zits. Due to the amount of mesh reduction, there are visible "flat" spots and noticeable straight lines to simulate a curves surface. I find it frustrating that another simple slicer can blast through around 40mm/s on a high res mesh, and not encounter these pauses.

I'm still trying to isolate what the problem is with my setup, and have spent an entire day attempting to do so. So far I've tried a few versions of Cura 4.4, and 4.5 all with the same result. I've gradually increased the mesh max-resolution, max travel res, and max deviation, all still with the same result. Since I'm using Octoprint, I decided to eliminate that variable by slicing directly to the SD card, and printing directly, but that has not solved the issue. I recently upgraded from Marlin 1.9 to Marlin 2.0, and assumed that might be the issue. I went back, and still the same problem. Major stuttering, vibrations, and pauses on curved surfaces. As an experiment I tried another slicer, KISS, and spent about 5 minutes setting it up for my printer, and it printed flawlessly! Incredibly smooth lines, and the curvature was so smooth it was reflective! I then uploaded that GCode to Octoprint and had the same smooth result. I really like Cura, but this is beginning to become a major problem, and I haven't discovered a solution yet. If anyone's come across a solution, please let me know.