From cc7c99a4a415fb3c4fa8ef947d12098c13b40d12 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Thu, 12 Oct 2017 00:48:01 -0400 Subject: cartesian: Fix min_stop_interval calculation error It is possible to have an acceleration greater than max_z_accel on XY+Z moves. That needs to be taken into account when calculating the min_stop_interval. This prevents spurious "No next step" MCU errors. Signed-off-by: Kevin O'Connor --- klippy/delta.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'klippy/delta.py') diff --git a/klippy/delta.py b/klippy/delta.py index e3ec0123..8eddc3c9 100644 --- a/klippy/delta.py +++ b/klippy/delta.py @@ -32,9 +32,9 @@ class DeltaKinematics: self.max_z_velocity = config.getfloat( 'max_z_velocity', self.max_velocity, above=0., maxval=self.max_velocity) - max_xy_halt_velocity = toolhead.get_max_axis_halt(self.max_accel) + max_halt_velocity = toolhead.get_max_axis_halt() for s in self.steppers: - s.set_max_jerk(max_xy_halt_velocity, self.max_accel) + s.set_max_jerk(max_halt_velocity, self.max_accel) # Determine tower locations in cartesian space angles = [config.getsection('stepper_a').getfloat('angle', 210.), config.getsection('stepper_b').getfloat('angle', 330.), -- cgit v1.2.3-70-g09d2