 # Feedback: easier TUNING_TOWER syntax

I’d like to request some quick feedback on an improvement to the TUNING_TOWER command I’d like to implement.

Many (including myself) get confused with the current syntax, which works well for towers where the parameter changes smoothly, but requires extra calculations, or even a spreadsheet, when using the BAND option. Specifically I’d like easier syntax for printing towers like this one: Smart compact temperature calibration tower by gaaZolee - Thingiverse.

Here’s the current documentation:

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).

I’d like to be able to specify “start at 225C, skip 2mm, then decrease by 5C every 5mm”. I don’t want to have to calculate the factor, or adjust for the .5 in the formula.

• STEP=<value>. This can be used instead of FACTOR. If specified, the formula used is value = start + step * floor(z_height / band). It would be an error to specify both FACTOR and STEP.
• SKIP=<value_mm>. Skips this many millimeters of Z height before starting the tower. Useful for e.g. the base or stand of a tower.

The following simple command can then be used for the above tower. Note the values for the parameters are immediately known to the user, and no calculations are needed:

TUNING_TOWER COMMAND=“SET_HEATER_TEMPERATURE HEATER=extruder” PARAMETER=TARGET START=225 SKIP=2 BAND=5 STEP=5

This change would be 100% backwards compatible.

3 Likes

I like the addition of the `SKIP`; that’d be useful for this gaaZolee tower, which is my go-to. I just went through this myself to run a temp tower and I do think making it a bit more user-friendly would be nice.

Probably the best way to propose this is to submit a working PR. Ah, well, there you have it! Nice work!

guys i actually have a serious concern with the formula

value = start + factor * ((floor(z_height / band) + .5) * band)

particularly the section floor(z_height / band). if the purpose of this is to identify the band that a particular layer belongs to, then the correct implementation should be based on format ceil(x-y/y) instead. otherwise the first band will always be short of 1 layer compared to the other bands, for example a 0.2 layer height model will only have 4 layers in the first band when it should have 5. as long as layer height is a nonzero value (it has to be–layer height zero is technically not a layer), this change is backwards compatible. unless this actually ties into another part of the code which does allow for layer height = 0 for some strange reason, then i guess the floor() method works but it still bugs me.

thoughts? sorry if i should have started another thread.

``````Layer Height	floor(z_height / band)		ceil((z_height-band)/band)
0.2				0							0
0.4				0							0
0.6				0							0
0.8				0							0
1				1							0
1.2				1							1
1.4				1							1
1.6				1							1
1.8				1							1
2				2							1
2.2				2							2
2.4				2							2
2.6				2							2
2.8				2							2
3				3							2
``````

when dealing with custom STLs and TUNING_TOWER, we often have to look at the slicer preview whereby layer 1 is always a nonzero z_height and in my example table above temperature changes every 1mm should happen on 1.2, 2.2, 3.2, 4.2 and so on, instead of 1.0, 2.0, 3.0 etc which the current implementation using floor() will do.

This has now been merged into master. The final syntax uses the new STEP_DELTA and STEP_HEIGHT parameters, like this:

TUNING_TOWER COMMAND=“SET_HEATER_TEMPERATURE HEATER=extruder” PARAMETER=TARGET START=225 SKIP=2 STEP_HEIGHT=5 STEP_DELTA=5

1 Like

Greetings! I’m attempting a temperature tower using this recent enhancement, and it is failing when it tries to issue the heater commend:

`````` \$ TUNING_TOWER COMMAND=“SET_HEATER_TEMPERATURE HEATER=extruder” PARAMETER=TARGET START=280 STEP_DELTA=7 STEP_HEIGHT=10 SKIP=1.4
11:23:57  // Starting tuning test (start=280.000000 step_delta=7.000000 step_height=10.000000 skip=1.400000)
11:24:04  !! Malformed command '“SET_HEATER_TEMPERATURE TARGET=280.000000000'
11:24:04  !! Malformed command '“SET_HEATER_TEMPERATURE TARGET=280.000000000'
``````

klippy.log (2.6 MB)

I’m using Klipper version v0.9.1-786-gc2d3a168

My klippy.log is attached. Thanks for any guidance!

John

Your quotes (“) look strange. Did you copy paste it from a source in the www or did you enter it by hand?

I think you are on to something – but I used the quotes as shown in the item above from @matthewlloyd

Let me try it with the single quotes.

Yep – thanks for the tip – the problem was using double quotes not single quotes. It is working fine with single quotes.

`TUNING_TOWER COMMAND='SET_HEATER_TEMPERATURE HEATER=extruder' PARAMETER=TARGET START=280 STEP_DELTA=7 STEP_HEIGHT=10 SKIP=1.4`