Parametrized Printer Setup/Calibration

Hornetrider

Hi

I have been scrolling thru some interesting approaches to calibrate the printer for different parameters.
In one thread there has been an approach for Pressure Advance that, in my opinion, goes in the right direction.
https://forum.duet3d.com/topic/6698/pressure-advance-calibration?_=1578666654636
thx @DigitalVision

Can such scripts also be used for determining the optimum values for:

acceleration
jerk
simultanious speed changes
speeds
print speeds
obviously pressure advance
dynamic acceleration control
non linear extrusion
etc.

My main interest is to learn from your knowledge and experience and to find out:

which parameters do make sense to be tested this way?
are there any limitations, and if so which?
the right sequence of parameters to be tested?
how could an output be generated?

Or, maybe has somebody run a kind of DOE (Design of Experiment) to find the right parameters for the printer, instead of running hours of try and error..?

Looking forward for your input

Hornetrider

Hey

it seems that nobody has interest in this topic or that some solutions are around.
I'll keep searching and trying

Cheers

dc42

I expect to see more sers developing scripts when RRF 3.01 with conditional GCode is released.

wesc

Check out Kisslicer’s <TUNINGVAL> wizard. It’s perfect for tuning gcode configurable settings.

Something similar can be done in prusaslicer now that they support expressions in gcode. Something like: (on phone so will gets syntax wrong)

Gxx P{min + (max-min)*layer_z/height)

Where you wish to interpolate the P parameter from min to max over the height of the test object.

wesc

Derp. I meant Mxx P...

@wesc Interesting, and with 3.01RC1 fersh off github I hope to see more native solutions soon

wesc

Klipper also has a TUNING_TOWER command. Perhaps a tuning_tower gcode could be implemented.

MXXX P’MYYY P<Val>’ Lmin Ffactor Bband
Where MYYY P### is emitted for each layer. Might require some slicer conventions to indicate layer start. Could also just emit this when Z changes, unfortunately including z hops...

Klipper doc:
TUNING_TOWER COMMAND=<command> PARAMETER=<name> START=<value> FACTOR=<value> [BAND=<value>]: A tool for tuning a parameter on each Z height during a print. The tool will run the given COMMAND with the given PARAMETER assigned to the value using the formula value = start + factor * z_height. If BAND is provided then the adjustment will only be made every BAND millimeters of z height - in that case the formula used is value = start + factor * ((floor(z_height / band) + .5) * band).