From 9755182adfa09de6886a0b482aa03d236f75f3ce Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Mon, 28 Nov 2016 11:23:26 -0500 Subject: homing: Check homing distance to verify endstop trigger after retract Instead of checking the endstop trigger directly after a retract move, verify some distance is traveled during the following homing operation. This reduces the amount of synchronization between mcu and host during homing. Signed-off-by: Kevin O'Connor --- klippy/cartesian.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'klippy/cartesian.py') diff --git a/klippy/cartesian.py b/klippy/cartesian.py index f6fe86bb..09a2a094 100644 --- a/klippy/cartesian.py +++ b/klippy/cartesian.py @@ -61,7 +61,8 @@ class CartKinematics: homing_state.plan_retract(list(coord), [s], s.homing_speed) # Home again coord[axis] = r2pos - homing_state.plan_home(list(coord), homepos, [s], s.homing_speed/2.0) + homing_state.plan_second_home( + list(coord), homepos, [s], s.homing_speed/2.0) homing_state.plan_calc_position(self.get_homed_position) def motor_off(self, move_time): self.limits = [(1.0, -1.0)] * 3 -- cgit v1.2.3-70-g09d2