Failed to configure shaper(s) shaper_z with given parameters

General Discussion
1

Basic Information:

Printer Model: voron trident
MCU / Printerboard: octopus pro h723 v1.1
Host / SBC rpi 3b+
klippy.log

klippy (3).log (256.5 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

did a shaper_calibrate command in console. everything worked well but when did save_config error shows as ‘‘failed to configure shaper(s) shaper_z with given parameters’’. i also tried to manually put [input_shaper]

shaper_type_x: zv

shaper_frequency_x: 61.4

shaper_type_y: mzv

shaper_freq_y: 47.2

still same error shows.

removing the input shaper config removes the error.

2

I know the instructions say:

But, in cases like this, the most likely problem is that you’ve broken up your printer.cfg into separate files and information required for the SAVE_CONFIG is in an included file and not in hte mainline printer.cfg.

3

for that shall i add the needed configuration file from ebb36.cfg to printer.cfg? let me try that….

it didnt worked

4

even adding [input_shaper] to printer.cfg gives this error.

5

Please post your printer.cfg (along with any included files) as requested.

1 Like
6

will post asap…

7

Please as a file. Thank you.

8

here it is

config-20251104-231046.zip (5.0 KB)

9

Yeah, everything in ebb36.cfg needs to be in printer.cfg.

What’s KAMP_Settings.cfg? I suspect that needs to be in printer.cfg as well.

Now, where did sb led.cfg come from? I’m not sure about the space character in the filename and if Klipper/Jinja will handle that appropriately.

I expect that once you move the contents of ebb36.cfg into printer.cfg you’ll be able to save the parameters but I’d like more information about the other two .cfg files.

10

here i have added every cfg files

config-20251105-084932.zip (26.1 KB)

11

did that too but same problem persist. i think the issue is different. something related to shaper’s z axis though i only did shaper callibrate for x nd y axis. input shaper used to work before on my printer but when i reinstalled my printer firmware to latest version, it threw out this error.

12

Could you post the latest printer.cfg with the changes along with the included additional .cfg files?

13

even disabling sb_led,

config-20251105-110139.zip (11.5 KB)

ebb36 and its parameters not solving the issue…..the error throws the moment i add [input_shaper] to printer.cfg

14

Sorry, the “error throws”? Is this a new error that happens when you “SAVE & RESTART” or try the input shaper?

Please describe exactly what happens (and post screen shots if possible).

15

when i do SAVE & RESTART

16

Isn’t that different than what you first reported?

Please post your latest klippy.log and the printer.cfg and other .cfg files as requested.

17

here i have attatched recent cfg as well as klippy log.

config with log.zip (263.9 KB)

20251104_085605
20251104_0856051920×1440 794 KB

18

For me the configs look fine and the content of ebb36.cfg and others is properly included in printer.cfg.

On github I see that @dmbutyugin changed the resonance_tester.py to allow Z input shaping.
Maybe those Z parameters are now mandatory or that is a bug?
However the documentation already lists the Z parameters:

So I guess you need to at least define those parameters with 0 or something like that.

The used Klipper version is: v0.13.0-375-gba79d72fb

19

i even tried adding

[input_shaper]

shaper_freq_x = xx

shaper_type_x = mzv

shaper_freq_y = xx

shaper_type_y = zv

shaper_freq_z = 0/50 (checked with both values)

shaper_type_z = zv/mzv/2hump_ei/3hump_ei

still same error showing

20

At first glance it does not look like your config has any problems. Perhaps when you pulled a Klipper update something got borked. You can try running on your Pi

rm ~/klipper/klippy/chelper/*.so

and restart the printer. This will rebuild the C part of Klipper, and perhaps this get the issue fixed. And at least resonance_tester has nothing to do with it.

1 Like