CoreXY - speed constrained?
-
I'm using Slic3r 1.3.1-dev build commit a4a0d52 downloaded a few days ago. Code in there is:
M201 X500 Y500
M204 P500 T500This is run before every geometry type. It is a functional, but ugly hack which I'm hoping they fix soon.
The M204 setting limits the acceleration along the length of the vector so so long as this value is below the X and Y values (or a little less in the case of core XY) then this will result in the same acceleration in any direction in the XY plane. I'm thankful for this thread as I was under the understanding that the XY parameters in the M201 command applied to the individual motors, rather than an axis.
It's not so much the time or distance to get to speed that concerns me, it's more how well the system handles the short vectors that most slicers kick out identified in the following linked thread and also in the work @deckingman presented on mixing with small ratios on one of the extrusion axis.
I would like to be able to limit the acceleration on the small perimeters to keep the motion a bit smoother. I would use an unique speed setting for the small perimeters in Slic3r so a parser could identify that block then append a suitable M204 line before the block of vectors.
https://forum.duet3d.com/topic/8484/what-hapens-with-successive-sub-step-relative-extrusions/4
-
@doctrucker said in CoreXY - speed constrained?:
...........................
I would like to be able to limit the acceleration on the small perimeters to keep the motion a bit smoother.
Just a thought Wes but I'd imagine that if the small perimeters are segmented as is likely, then acceleration won't come into it much. It'll start a small segment at the jerk speed and finish at the jerk speed so if it's a small segment then there isn't likely to be much of an acceleration or deceleration phase. All in all, I'd have thought that changing instantaneous speed threshold (jerk) would have more of an effect on the motion of small perimeters than changing acceleration (but I could be wrong - often am ).