F
Member
【Editorial Discussion】
A servo that tracks well in the middle of a move and then throws a following-error spike at reversal is a regular field complaint. Turning every gain down will often hide the spike and ruin the rest of the move. The usual split is mechanical backlash or compliance, friction that is not accounted for, or an interpolation / encoder issue that only shows when velocity crosses zero.
1) Look at the error against position and against velocity, not only against time. A dead-band around zero velocity that is repeatable in both directions points more at friction or backlash; a spike that changes with approach speed points at how the loop and the feedforward treat the zero crossing. If the error also depends on where on the travel the reversal happens, inspect the mechanics at that location before you retune the whole axis.
2) Friction feedforward and backlash compensation are different knobs. A Coulomb-friction term can reduce the flat spot at reversal; a backlash model cannot invent stiffness that is not there, and it can oscillate if the lost motion was actually compliance. Measure lost motion and the torque needed to start motion as two separate numbers.
3) Encoder interpolation and counting should be checked at the same crossing. Missing or irregular counts near zero speed, or a load encoder and a motor encoder that disagree only at reversal, will look like a tune problem and will not be cured by a friction table.
4) Record load, temperature, and whether the axis was approaching from plus or minus. Grease viscosity and preload change the reversal, and a tune done when the machine was warm may fail on the first move of the day.
Open question: on your last reversal spike, what actually fixed it — a friction term, a mechanical adjustment, or an encoder/interpolation issue? Any case where lowering gains only moved the problem into settling time? Field notes welcome.
A servo that tracks well in the middle of a move and then throws a following-error spike at reversal is a regular field complaint. Turning every gain down will often hide the spike and ruin the rest of the move. The usual split is mechanical backlash or compliance, friction that is not accounted for, or an interpolation / encoder issue that only shows when velocity crosses zero.
1) Look at the error against position and against velocity, not only against time. A dead-band around zero velocity that is repeatable in both directions points more at friction or backlash; a spike that changes with approach speed points at how the loop and the feedforward treat the zero crossing. If the error also depends on where on the travel the reversal happens, inspect the mechanics at that location before you retune the whole axis.
2) Friction feedforward and backlash compensation are different knobs. A Coulomb-friction term can reduce the flat spot at reversal; a backlash model cannot invent stiffness that is not there, and it can oscillate if the lost motion was actually compliance. Measure lost motion and the torque needed to start motion as two separate numbers.
3) Encoder interpolation and counting should be checked at the same crossing. Missing or irregular counts near zero speed, or a load encoder and a motor encoder that disagree only at reversal, will look like a tune problem and will not be cured by a friction table.
4) Record load, temperature, and whether the axis was approaching from plus or minus. Grease viscosity and preload change the reversal, and a tune done when the machine was warm may fail on the first move of the day.
Open question: on your last reversal spike, what actually fixed it — a friction term, a mechanical adjustment, or an encoder/interpolation issue? Any case where lowering gains only moved the problem into settling time? Field notes welcome.