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/gcode.py | 2 ++ 1 file changed, 2 insertions(+) (limited to 'klippy/gcode.py') diff --git a/klippy/gcode.py b/klippy/gcode.py index 88797077..056f7c50 100644 --- a/klippy/gcode.py +++ b/klippy/gcode.py @@ -254,6 +254,8 @@ class GCodeParser: if not axes: axes = [0, 1, 2] homing_state = homing.Homing(self.toolhead, axes) + if self.inputfile: + homing_state.set_no_verify_retract() self.toolhead.home(homing_state) def axes_update(homing_state): newpos = self.toolhead.get_position() -- cgit v1.2.3-70-g09d2