A good process to tune jerk?

Alex.cr

For what its worth with my Voron 2.4 I just spent the afternoon looking for good values by printing parts. I have been hunting the proper settings with input shaper turned on only to discover that lower values (less than 20hz) for input shaper cause weird things to happen.

Anyway back on topic. Using the fields that @zapta made above. This was my experience for M556 values.

Low values
1-100 -> produced notice slowing/stopping when printing the 360 sided circle. This slow of settings also caused corner buldge to be apparent.

Medium values
120-250 -> These values seem to be the sweet spot for my application (and I would expect the same for most people)

High Values
500-1000 -> Starts to round shallow corners, ringing starting to become more present

Very High Vales
1000+ No major change in print quality from High values.

Here are my movement settings for reference, external print speed at 60mm/s ABS.

M566 X180 Y180 Z60 E300 P1      ; Set maximum instantaneous speed changes (mm/min) 
M203 X25000 Y25000 Z6000 E6000 ; Set maximum speeds (mm/min)
M201 X6000 Y6000 Z3000 E6000     ; Set maximum accelerations (mm/s^2) 
M204 P3000 T6000                ; Set printing acceleration and travel accelerations

Phaedrux

@alex-cr said in A good process to tune jerk?:

M566 X180 Y180

180mm/min? Really? That seems abnormally low to me.

garis

If you understand basic python this script might help you. I posted an earlier version some years ago.

It creates test towers and then test ranges of Mcode from definable start / end / increments.

In essence it can test up to 3 nested for loops of M Code on 3 polygon towers each separately defined (from triangles to near circles eg for jerk !!), each tower at different speeds. Start / end layer locations are definable to control travel paths. (and to change viewing angle during print).

Sides can have 1 or 2 vertical grooves (configurable), and sides can be omitted.

A scan through the code will show more details and parameters.

Wide layers are printing for see where each code is changed, to supplement lots of M117 messages during printing.

I have no skill in creating a user friendly input screen so use the d_settings file that is imported and overrides relevant data in the main script file. Nor do I have skill in automatically creating the location of the output gcode so that needs to be manually set at about line 1008.

Most combinations are possible.

mcopt_p06_2.py d_settings.py

Alex.cr

@phaedrux said in A good process to tune jerk?:

180mm/min? Really? That seems abnormally low to me.

That's what I thought as well. With my input shaper turned on though If I get much over 250-300 the ringing comes back in force at 3000mm/min acceleration.

o_lampe

@garis said in A good process to tune jerk?:

In essence it can test up to 3 nested for loops of M Code

IMHO there's one golden rule about "tuning": Never change more than one parameter at a time.

Beside that, it seems to be a useful tool to generate test patterns.