It is not possible to change the shaper frequency without rebooting. When entering commands like:
SET_INPUT_SHAPER SHAPER_FREQ_X=
TUNING_TOWER COMMAND=SET_INPUT_SHAPER PARAMETER=SHAPER_FREQ_Y START=30 STEP_DELTA=5 STEP_HEIGHT=3
There are no changes from the shaper when printing (I tried everything - ZV/MZV/El…).
Only one command works:
SET_INPUT_SHAPER SHAPER_TYPE
But the frequency cannot be changed. I checked it many times (about 20+ test towers to understand what is going on).
Obtaining the frequencies is one thing.
To apply them and get the values to all parts of Klipper is another thing.
This can only be done by a reboot and not on the fly.
I’ll put it more simply.
SET_INPUT_SHAPER SHAPER_FREQ_X
Does not work.
Messages in the console (screenshot) are “false”.
Do you want to say that TUNING_TOWER COMMAND SET_INPUT_SHAPER SHAPER_FREQ… , which was used to manually configure IS for years, should never have worked?)
Everything worked before, I’ll look for the old version of the klipper…
Actually I’m not sure, what you are reporting here
You do not seem to follow the procedure outlined in the official documentation. As of this it may very well be that your TUNING_TOWER command missed the interesting spots
I ran the tests according to the official documentation and everything worked as expected
As stated by @EddyMI3D, a TUNING_TOWER will just provide you with results that you need to interpret and reflect in your printer.cfg. A TUNING_TOWER has never and probably will never update any values in your printer.cfg
In this context, only the SHAPER_CALIBRATE will update the printer.cfg and request you to make it permanent with SAVE_CONFIG
I follow the procedure from the official documentation, but I have a different test turret - that’s all.
Do you see the result of changing the shaper (height) on the print? Or only in the console?
I don’t expect TUNING_TOWER to change anything in the configuration file. I expect that the difference will be visible on the print when changing the frequency of the shaper - there is no difference. At any acceleration, at any shaper, at any frequency. There are changes only when I write the .cfg shaper and reboot the printer. During printing TUNING_TOWER COMMAND=SET_INPUT_SHAPER PARAMETER=SHAPER_FREQ_Y START=30 STEP_DELTA=5 STEP_HEIGHT=3 - does not affect printing (it doesn’t matter what type of shaper ZV/MZV/EI is…). Although TUNING_TOWER works great if the speed or acceleration changes, but not the frequency of the shaper.
On the photo in the header, side X, during that printing, a command was executed to change the frequency at X. Please read more carefully, and don’t consider me an inattentive fool, I spent several days and printed 20+ test towers to understand what was going on, I tried X and Y, >>>ALL!!!<<< types of shapers. I checked everything many times before creating a topic here. You can switch the shaper TYPE using console commands on the fly (this can be seen on the print), but there are NO CHANGES when changing the >>>FREQUENCY<<< (ON THE GO, THROUGH THE CONSOLE, or by command from the test tower). Even if you change from 5Hz to 50-90-200 - there is no difference. ALTHOUGH THE CONSOLE SAYS THAT THE FREQUENCY HAS BEEN APPLIED. So on any shaper at least 3HUMP_EI.
The working shapers for my printer are:
MZV
X 64Hz
Y 64Hz
I’m already tired of hearing the same answers from dozens of people. Just believe me - for some reason, my printer does not apply the shaper frequencies either by the test tower code or by a direct console command. The frequency is APPLIED only if you change the config and reboot the printer - THIS IS A BUG.
All other parameters are correctly changed (applied) on the fly right during the printing process. Except for the shaper frequency.
It worked, I removed the LA coefficient from the g-code (but in theory the standard one from the config continues to be used, in my case 0.04). And for the first time I see the result of changing the frequency on print. I don’t know how this could be connected…
Or something else helped, I reinstalled the klipper the other day, but I loaded the old configs.
With LA you are referring to PA, right?
If so, of course it will get enabled when you have it your gcode (should be kind of self explaining). If you just have it in your cfg and issue a SET_PRESSURE_ADVANCE ADVANCE=0 then it will stay disabled until Klipper is restarted OR a PA value passed via gcode.
