aboutsummaryrefslogtreecommitdiffstats
path: root/klippy/delta.py
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2017-10-12 00:48:01 -0400
committerKevin O'Connor <kevin@koconnor.net>2017-10-12 01:16:11 -0400
commitcc7c99a4a415fb3c4fa8ef947d12098c13b40d12 (patch)
tree98ad1151403be1572eef832379138f2c0c4f8267 /klippy/delta.py
parentd3eb148cfa411bd8e22f06f190ffda4b2cca5a06 (diff)
downloadkutter-cc7c99a4a415fb3c4fa8ef947d12098c13b40d12.tar.gz
kutter-cc7c99a4a415fb3c4fa8ef947d12098c13b40d12.tar.xz
kutter-cc7c99a4a415fb3c4fa8ef947d12098c13b40d12.zip
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 <kevin@koconnor.net>
Diffstat (limited to 'klippy/delta.py')
-rw-r--r--klippy/delta.py4
1 files changed, 2 insertions, 2 deletions
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.),