control system stability
A control system is stable if, after you nudge or disturb it, it eventually settles back down to a steady state instead of swinging wider and wider out of control. Picture a bowl with a marble in it: tap the marble and it rolls around for a moment, then quietly comes to rest at the bottom — that is stable. Now flip the bowl over and balance the marble on top: the tiniest tap sends it rolling off and away, never to return — that is unstable. Stability is simply the difference between disturbances that fade and disturbances that grow.
Why does this matter so much? A feedback controller is constantly reacting to error, and a badly designed one can react too hard, overshoot, react hard again the other way, and feed its own mistakes until the swings explode. A stable design guarantees the opposite: knock the system off course and the wobbles shrink with each cycle until calm returns. This is the single most important property any controller must have. Speed, accuracy, and smoothness are all nice, but a fast and accurate system that is unstable is worse than useless — it is dangerous, because the motion runs away.
Stability is not all-or-nothing in practice; engineers talk about how stable a system is — its margin of safety. A design can be technically stable but still teeter on the edge, taking forever to settle or breaking into oscillation the moment the load changes. So good control aims not just to be stable, but to stay comfortably stable across the real range of conditions the machine will actually meet.
A self-balancing scooter that is stable rights itself after you lean and let go; an unstable one would tip further and faster the instant it started to fall.
Stable: leans, then recovers. Unstable: leans, then falls away.
Engineers often judge stability from a system's poles: for a continuous-time system, if they all sit in the left half of the complex plane, disturbances die out and the system is stable.