Print stuttering around curves, LaErrors
-
@Charlie said in Print stuttering around curves, LaErrors:
by re slicing in Cura 4.5 (Cura 4.6 was where I was having the issues).
That sounds plausible and would match with the update notes in my custom version being a fix for the issue.
I think @NitroFreak is having a separate issue though. Or at least an additional issue.
-
@bot I was thinking of using a diff checker (any recommended tools would be greatly appreciated) to see what the difference between the two versions may be. I'll update on my findings.
-
@Charlie said in Print stuttering around curves, LaErrors:
I was thinking of using a diff checker (any recommended tools would be greatly appreciated)
Notepad++ on windows, Atom on Mac probably
-
I use Visual Studio Code because it comes with a nicer out-of-the-box config than notepad++ (my former choice). Nice comparison functionality, and an all around great little mini-IDE style text editor.
-
Thank you both for your replies! I tried a normal diff checker, but there was far too much different for me to compare. Using "gcodeanalyser.com" (amazing tool, way better than the "gcode.ws" that I used originally which didn't depict accelerations) I think I found my issue.
First image is using Cura 4.5 (no issues).
Second image is using Cura 4.6 (stuttering issues).
Same exact settings, same layer, but notice how Cura 4.6 speeds up and slows down many more times during the layer. I would assume that it would accelerate once for the layer start, and again for the small radius corner (as in 4.5) but 4.6 changes a lot more.
It's worth noting that the version of Cura that @Phaedrux kindly provided does not appear to have the issues that "stock" Cura 4.6 seems to have.
Please let me know if I'm mistaken with any of my assumptions.
-
@Charlie said in Print stuttering around curves, LaErrors:
Have not seen that one before. I'll have to compare the gcodes and see if I get the same.
-
Unfortunately my 30mb gcode file is choking the analyser and it eventually crashes the page. I'll see if I can find a smaller one that was sliced with that version.
-
@brisma said in Print stuttering around curves, LaErrors:
Why 1428 (that's useless) and not 1400 on extruder?
What's useless about 1428 instead of 1400? That's a 2% difference. Seems more than worthwhile to correctly define.
-
Did you guys report this over on the Cura Github?
-
@CCS86 On Duet2 Wifi/Ethernet, the current can only be set in increments of 100 mA, and will be rounded down always.
IE 1428 == 1400, and 1478 == 1400
On Maestro, the current can be set in increments of 50 mA, rounded down in the same fashion. I'm not sure of the Duet3.
*not actually a robot
-
@CCS86 said in Print stuttering around curves, LaErrors:
@brisma said in Print stuttering around curves, LaErrors:
Why 1428 (that's useless) and not 1400 on extruder?
What's useless about 1428 instead of 1400? That's a 2% difference. Seems more than worthwhile to correctly define.
He means (however bluntly) is that you only have a 100ma resolution with the Duetwifi and 50ma on the Maestro
https://duet3d.dozuki.com/Wiki/Gcode#Section_M906_Set_motor_currents
-
@CCS86 said in Print stuttering around curves, LaErrors:
Did you guys report this over on the Cura Github?
No, but I think it's known because the custom build from a few days ago lists "upstream changes" and a fix for geometry simplification, which sounds applicable. I quickly poked around the github of the smartavionics build but not yet the main cura github.
-
@CCS86 said in Print stuttering around curves, LaErrors:
Did you guys report this over on the Cura Github?
Could be this one: https://github.com/Ultimaker/Cura/issues/7588
-
@bot said in Print stuttering around curves, LaErrors:
On Maestro, the current can be set in increments of 50 mA, rounded down in the same fashion. I'm not sure of the Duet3.
@Phaedrux said in Print stuttering around curves, LaErrors:
He means (however bluntly) is that you only have a 100ma resolution with the Duetwifi and 50ma on the Maestro
Doh, I was reading too fast and thought is was steps/mm. Sorry to derail!
-
-
4.6.1 is out, which might fix the issue.
-
@CCS86 Yes, Cura 4.6.1 does appear to fix the issue (at least it looks fixed in "GCode Analyzer"). Much appreciated!
