diff options
| author | Kevin O'Connor <kevin@koconnor.net> | 2024-01-16 20:40:55 -0500 |
|---|---|---|
| committer | Kevin O'Connor <kevin@koconnor.net> | 2024-01-16 20:40:55 -0500 |
| commit | 3d3b87f97fc91d93ae4198b36198262207e1202b (patch) | |
| tree | 942196be020186f1a960fc5fec5e7c062d781c77 /klippy/extras/force_move.py | |
| parent | 447a88eb086829fd6139fda6e41eb8dc2e6a4366 (diff) | |
| download | kutter-3d3b87f97fc91d93ae4198b36198262207e1202b.tar.gz kutter-3d3b87f97fc91d93ae4198b36198262207e1202b.tar.xz kutter-3d3b87f97fc91d93ae4198b36198262207e1202b.zip | |
toolhead: Ensure full kin_flush_delay after flush_step_generation()
Commit b7b13588 made it possible that the kinematic code could be
restarted after a flush_step_generation() call without a sufficient
delay.
Rename last_sg_flush_time to min_restart_time and use that to ensure
_calc_print_time() always pauses kin_flush_delay time since the last
flush_step_generation() call.
Also, update force_move to invoke flush_step_generation() after any
movements. This is needed to ensure there is a sufficient delay
should force_move be called on a stepper motor that is part of the
toolhead kinematics and is using a step generation "scan time".
This fixes possible "internal error in stepcompress" reports when
using FORCE_MOVE.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'klippy/extras/force_move.py')
| -rw-r--r-- | klippy/extras/force_move.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/klippy/extras/force_move.py b/klippy/extras/force_move.py index 7501ea98..9cf49519 100644 --- a/klippy/extras/force_move.py +++ b/klippy/extras/force_move.py @@ -90,8 +90,8 @@ class ForceMove: print_time + 99999.9) stepper.set_trapq(prev_trapq) stepper.set_stepper_kinematics(prev_sk) - toolhead.note_kinematic_activity(print_time) toolhead.dwell(accel_t + cruise_t + accel_t) + toolhead.flush_step_generation() def _lookup_stepper(self, gcmd): name = gcmd.get('STEPPER') if name not in self.steppers: |