I get you, but like I said, I'm not measuring the steppers travel or anything. This is strictly an error showing up on the digital readouts of Mach4 Mill application.
It gets worse if I raise the acceleration value, and it got worse when I changed from 16256 steps per unit to 1016.
To me that means the math formula for determining what to send to the motion controller is fuzzy. And yes, everybody should be seeing it, based on what I have here.
The original poster of this thread brought it up first, so call it a known problem.
The fact that the error changes with motor tuning specifics would seem to indicate that the math could be improved. In the interest of digital precision.
I'll settle for this kind of accuracy, but it just isn't right, analy speaking.
My motion controller is a piece of work, I can tell you, but I'm not able to measure the output yet.
Hold on. What you said about the software not sending pulses, it sends a number. So what drives the dro values? Is it feedback from the motion controller??