I found the idea quite intriguing, and thought about integrating the surface
correction idea better. After bouncing a few ideas with Andy, this is what I
have so far:
probekins: a kinematics module which be default behaves like trivkins
it accepts a mesh of triangles which define Z correction va
We ran into this problem today in the 2.5 branch we are using (and it is also
in 2.4.7). It is REALLY bad when our Z-axis tries to move at 1500ipm when we
have have it defined to go no faster than 500ipm.
Can this fix be added to 2.5?Or alternatively, how would I apply this patch
(to what?)
