h3n3/klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

stepper: Do not set min_stop_interval in micro-controller

Browse Source 
The min_stop_interval safety check is fragile and leads to a notable
amount of complexity.  Avoid these issues by not programming this
safety check.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor
2021-04-25 14:53:50 -04:00
parent d1946fb6ed
commit 5a5ecd88e2
12 changed files with 5 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
klippy/kinematics/corexy.py
View File

@@ -34,14 +34,6 @@ class CoreXYKinematics:
ranges = [r.get_range() for r in self.rails]
self.axes_min = toolhead.Coord(*[r[0] for r in ranges], e=0.)
self.axes_max = toolhead.Coord(*[r[1] for r in ranges], e=0.)
# Setup stepper max halt velocity
max_halt_velocity = toolhead.get_max_axis_halt()
max_xy_halt_velocity = max_halt_velocity * math.sqrt(2.)
max_xy_accel = max_accel * math.sqrt(2.)
self.rails[0].set_max_jerk(max_xy_halt_velocity, max_xy_accel)
self.rails[1].set_max_jerk(max_xy_halt_velocity, max_xy_accel)
self.rails[2].set_max_jerk(
min(max_halt_velocity, self.max_z_velocity), self.max_z_accel)
def get_steppers(self):
return [s for rail in self.rails for s in rail.get_steppers()]
def calc_tag_position(self):