Skip to content

SAVE_CONFIG conflicts with machine.cfg when saving z_offset and position_endstop #129

@Tealc86

Description

@Tealc86

Description

When trying to save the z_offset after calibration using Z_OFFSET_APPLY_PROBE + SAVE_CONFIG, Klipper throws a conflict error because the same parameter is already defined in machine.cfg.

Error message

Steps to reproduce

  1. Adjust z_offset with babysteps during a print
  2. Run Z_OFFSET_APPLY_PROBE
  3. Run SAVE_CONFIG
  4. Conflict error is thrown, config is not saved

Expected behavior

SAVE_CONFIG should be able to override values from machine.cfg by writing them to the #*# SAVE_CONFIG block in printer.cfg, as Klipper normally does.

Workarounds attempted

  • Adding z_offset manually to printer.cfg → still conflicts
  • Editing machine.cfg directly → works, the new value is applied correctly, but changes will be lost on firmware updates

Additional notes

Same issue occurs with position_endstop in stepper_z when running Z_OFFSET_APPLY_ENDSTOP.

Cosmos version: 0.0.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions