Skip to main content

Configuration Modification Notes

This page summarizes the most common formatting issues when modifying Klipper configurations. After modifying the configuration, save and restart Klipper, and locate problems based on error messages.

Caution

General configuration items should not be indented arbitrarily. Only the G-code content after gcode: within [gcode_macro XXXX] needs to be indented according to macro syntax.

Space and Indentation Errors

  • Cause: Residual spaces or indentation before configuration items prevent Klipper from correctly identifying parameters.
  • Solution: Remove extra spaces so that parameters start from the beginning of the line.
Loading...

Comparison Examples

Incorrect Example:

Loading...

Correct Example:

Loading...

Configuration Comment Errors

Retaining Unnecessary Configurations

  • Cause: The configuration file retains configuration sections that should not exist or are duplicated.
  • Solution: Delete erroneous configurations, keeping only the configuration sections actually required by the current hardware.
Loading...

Incomplete Section Commenting

Simply commenting out the [probe] section header is insufficient. All parameters within that configuration section must be commented out or deleted together until the next [xxxx] configuration section.

In the example below, the next configuration section is [homing_override].

Incorrect Example:

Loading...

Correct Example:

Loading...

Quick Reference for Common Configuration Errors

Error KeywordCommon CauseSolution
Option 'xxx' is not validMisspelled configuration parameter nameCheck if the parameter name matches the official documentation
Section 'xxx' is not a valid config sectionIncorrect configuration section name or missing pluginCheck section spelling, Klipper version, and plugin installation status
Unable to open config fileThe file referenced by include does not existCheck if the file path is correct
Unable to parse optionParameter format does not meet requirementsCheck numbers, coordinates, commas, and Chinese punctuation
Pin 'xxx' is not a valid pinIncorrect pin name formatConfirm the correct pin name based on the mainboard documentation
pin xxx used multiple timesSame pin repeatedly occupied by multiple featuresSearch all include files and delete duplicate occurrences
Duplicate chip nameDuplicate configuration sections with the same nameDelete duplicate [xxxx] configuration sections
Unknown temperature sensorMisspelled temperature sensor typeConfirm that the sensor_type name is correct

For more configuration startup-related errors, refer to: Configuration Errors.

Loading...