Whats most likely actually happening there is the stepper drive missing the step. This happens a LOT with gecko drives and mach3 at lower speeds. The stepper timing needs to be set to sherline mode, which is a 50% dutycycle per step and the problem goes away. basically geckos, and other drives, are extremely finicky about the timing of steps from the control, and mach 3 is extremely bad at timing steps correctly. emc2 is much better for this.Now, if we go back to my statement about using a servo (clearpath) on the Harmonic drive, I was referring to backlash during reversing. This is where the micro stepping really comes in to play. When you stop somewhere in between 2 full step positions and then reverse the direction, something unique happens. Quite often you will need to execute several small microsteps before you get any motor movement. I've done this with just an arm attached directly to the stepper motor shaft. I found it very strange that the control could be commanding movement, but the motor did not move. My belief is that it has something to do with micro steps. It may be that when you back up it goes immediately to the previous full step position, and then builds the micro steps from there. Whatever the reason, I believe that the tiny amount of reversing delay I experienced would be gone with a clearpath motor.
Royce
Most controllers up til the last 10 years or so were analogue velocity or torque control, and the loop was most definitely controlled by the control. It HAD to be. There was no other way because the drive only knows how to make the motor spin at a certain speed. it has no clue where the motor actually is.
Emc2 can also be made to do this when using servos, kflop definitely does this (you tube the motors with the control). On analogue drives its mandatory. On digital (step and direction) its optional.
Mach3 does NOT facilitate any modal encoder feedback except for a lathe spindle. This is why it can’t rigid tap in mill mode without a dodgy hack. it is entirely open loop. You could likely write a macro to read an encoder and display it, but that’s more or less pointless except to show the true spindle rpm (which is a feature).
If all the control was doing was following error, it can get that from the fault line of the drive. You do NOT want the drive doing any compensation for errors on its own if you can avoid it (obviously you can’t avoid it with basic steppers or in mach3). You want the drive to only do what it’s told. that’s why drives with motion controllers, jerk compensation, etc are basically pointless on a CNC machine. The main control needs to precisely control everything in coordination. If you turn on jerk compensation on a drive, you’ll get a corner that’s not sharp, or a circle that’s not round.
Last edited: