Skip to content

Conversation

@rogerlz
Copy link
Contributor

@rogerlz rogerlz commented Feb 28, 2025

Now that clear_homing_state() has been implemented, there is no longer a need for each kinematic class to manually register for the "motor_off" event, as the stepper_enable class can directly call clear_homing_state().

Also this changes the homing_axes and clear_axes parameters of the set_position() and clear_homing_state() to pass strings (eg, "xyz") instead of a list of numbers.

fyi @vvuk

Klipper PR: Klipper3d/klipper#6782

@rogerlz rogerlz requested a review from a team as a code owner February 28, 2025 11:26
@rogerlz rogerlz changed the title Klipper pr 6782 Simplify kinematic set_position() and clear_homing_state() calls Feb 28, 2025
Call clear_homing_state() on each motor off event.  This simplifies
the kinematic classes as they no longer need to register and handle
the motor_off event.

Signed-off-by: Kevin O'Connor <[email protected]>
Use strings such as "xyz" to specify which axes are to be considered
homing during a set_position() call.  This makes the parameter a
little less cryptic.

Signed-off-by: Kevin O'Connor <[email protected]>
Pass a string such as "xyz" to kin.clear_homing_state().  This makes
the parameter a little less cryptic.

Signed-off-by: Kevin O'Connor <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants