30
« on: October 24, 2019, 09:36:01 PM »
After contacting Artsoft and Warp 9 the consensus seems to be that the soft limits have to be set to something negative of the 0,0 position. I have set my x and y soft limits to -.0050 and took that extra code back out.
From Warp 9:
The ESS does allow for the possibility of both +0.0 and -0.0 This arises from the way that the SmoothStepper keeps track of the direction it is (or was last) going in, which can create a -0.0 This ability to track the direction of last movement along with the position helps with backlash compensation and a few other motion related details. But the ESS is working with the position in terms of integer steps. What we report to Mach4 is converted from integer steps to a double precision float.
My initial assumption would be that Mach is comparing -0.0 to 0.0 and that would likely result in a value of less than.. Why? Rounding - I am guessing that the number reported is something like -0.0000000001 due to the floating point conversion, This isn't reflecting that the SmoothStepper's position is off, since the integer steps are still true, but rather the mathematical issues of computer based floating point numbers.
Setting your Y soft limit to -0.01 should fix the issue.
From Artsoft:
I ran into this issue yesterday and the guy was homing too close to his soft limits, I can modify your ref all home function to see if moving the axis further away from the limits helps any, otherwise I'd suggest that your soft limits shouldn't be so close to your homing location (assuming they are).
I will however try to replicate this issue on a machine we have here using your profile.
Best Regards,