Step 12.35 — Add [input_shaper] and [exclude_object]¶
Step 35 of 37 · Chapter 12 — Software: Pi OS image, Klipper/Moonraker/Mainsail, firmware, printer.cfg
(no image — see text)
Parts: none.
Do: Add both. [input_shaper] goes in as a disabled placeholder so Ch 14 has somewhere to write:
#####################################################################
# Input shaper — ADDED, placeholder. Values come from Ch 14.
#####################################################################
[input_shaper]
## Leave both frequencies commented until you have run SHAPER_CALIBRATE
## on a machine that has already produced a good first print (survey §3.3).
## The ADXL345 is on the toolboard; [resonance_tester] is already configured.
#shaper_freq_x: 0
#shaper_freq_y: 0
#shaper_type: mzv
#####################################################################
# Object exclusion — ADDED
#####################################################################
[exclude_object]
Check
Klipper accepts a bare [input_shaper] with no frequencies: a valid "shaping disabled" state, not an error. [exclude_object] takes no parameters.
What you're looking at
Input shaping is Klipper's anti-ringing filter, fitted to the machine's measured resonance in Ch 14; the empty section here is somewhere for those numbers to land. [exclude_object] is what lets one failed part be cancelled mid-print without abandoning the rest of the plate.
Also: for cancel-object to actually work, the G-code needs object labels. Either turn on PrusaSlicer's Output options → Label objects → Firmware-specific, or set enable_object_processing: True under [file_manager] in moonraker.conf and let Moonraker inject them. Slicer-side is cheaper — Moonraker's preprocessor is file-I/O heavy. Decide this in the slicer chapter, not here. src · src
Source: Klipper docs § input_shaper · Klipper docs § exclude_object · Moonraker configuration