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.
-
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.
-
@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!