Failed to configure shaper(s) shaper_z with given parameters

General Discussion
21

will surely try this the moment i reach home

22

Thank you for that information.

As others have said, your printer.cfg looks okay but a couple of questions.

  1. When I look at your klippy.log, you have the error:
Config error
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/klippy.py", line 135, in _connect
    cb()
  File "/home/pi/klipper/klippy/extras/input_shaper.py", line 127, in connect
    self._update_input_shaping(error=self.printer.config_error)
  File "/home/pi/klipper/klippy/extras/input_shaper.py", line 179, in _update_input_shaping
    raise error("Failed to configure shaper(s) %s with given parameters"
configparser.Error: Failed to configure shaper(s) shaper_z with given parameters

I have seen this caused by manually changing the “SAVE_CONFIG” area of printer.cfg - have you made any changes there?

You might want to erase the SAVE_CONFIG section and see if that changes anything.

  1. When you merged your old ebb36.cfg file into your printer.cfg, how did you do it?

Did you do it in the Mainsail editor window or did you copy the files into a PC, merge them there and then copy them into the printer?

I’m asking because Klipper (and Linux systems in general) expects files that have lines terminated in just newLine (\n) characters whereas Windows files have lines terminated in carriageReturn/newLine (\r\n) characters - this is invisible to you but can cause parsing errors in Klipper.

23

i didnt change anything there.

24

copied from ebb36.cfg and pasted to printer.cfg directly.

previously i copied from github examples and edited them onto mainsail editor

25

Sorry for repeatedly asking questions but where was this done? Was it done on the host (ie through the Mainsail editor) or was it done on another system?

If you updated printer.cfg on the host (ie Mainsail editor) where did you get the clipboard image of ebb36.cfg?

I’m just asking because I’ve been caught by this in the past. You have to be very careful to not bring in \r\n at the end of a line.

26

done on mainsail editor

27

from here

1 Like
28

For context, input shaper implementation in Klipper is split between the Python and C parts. This particular error is raised as a result of some sanity checks between these two to make sure they stay compatible. To put it another way, this error would typically indicate a bug in Klipper, and regular users should not be able to trigger it regardless of what they put into the config file or add parameters to SET_INPUT_SHAPER command. However, I am presently not aware of such bugs in Klipper, and I also did not see any indications in the logs that corresponding parts of Klipper were modified. So my working hypothesis is that during an update something went wrong and while the source code was updated, the C binary part was not recompile, leaving it unaware of the newly introduced shaper. I’d say there’s no point in further investigations before we rule out this possibility by manually forcing this C part to be rebuilt.

3 Likes
29

looks like this thing worked. no error showing now.

thanks to everyone for ur precious time given to my issue

2 Likes
30

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.