Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Time domain analysis is the foundation of understanding how control systems actually behave. When you study control theory, you're being asked to predict what happens when someone flips a switch, changes a setpoint, or disturbs a system. Will the response be fast or sluggish? Will it overshoot dangerously or settle smoothly? Will there be persistent error?
These questions drive everything from autopilot design to industrial process control. The concepts here connect directly to system stability, transient performance, and steady-state accuracy. You'll see them appear in transfer function analysis, controller tuning problems, and system design questions. Don't just memorize definitions. Know what each parameter tells you about system behavior and how changing one affects the others.
These foundational techniques reveal how a system behaves by examining its response to standardized inputs. Simple test signals (steps, impulses, ramps) expose complex system dynamics in predictable ways.
The step response is the most common test signal in control systems. It evaluates how a system responds to a sudden, sustained change in input (like flipping a switch from 0 to 1). A single step test reveals stability, speed, and accuracy simultaneously, capturing rise time, settling time, overshoot, and steady-state error all at once.
This makes it the foundation for controller tuning. PID parameters are often adjusted based on step response characteristics because the step test is easy to perform experimentally and the resulting metrics map directly to design specifications.
The impulse response is mathematically fundamental because it completely characterizes any linear time-invariant (LTI) system. Taking the Laplace transform of directly yields the transfer function .
The convolution relationship is what makes this so powerful: the output for any arbitrary input can be found by convolving that input with the impulse response. In practice, though, generating a true impulse is difficult, so step response testing is more common in the lab.
The ramp response tests tracking ability by analyzing how well a system follows a continuously increasing input . This reveals velocity error: systems that perfectly track step inputs may still show persistent, growing error for ramp inputs.
Real-world relevance is high. Think of a radar dish tracking a moving aircraft or a motor maintaining speed on an incline. Both involve ramp-like reference signals.
Compare: Step response vs. impulse response: both characterize LTI systems completely, but step response is easier to generate experimentally while impulse response connects directly to the transfer function. For problems asking you to "characterize system behavior," step response metrics are usually expected.
These metrics quantify how a system gets to its final value. Transient behavior reflects the interplay between system speed and stability. Faster isn't always better if it causes oscillation.
Rise time measures response speed. It's typically defined as the time to go from 10% to 90% of the final value (though 0% to 100% is sometimes used, so check which convention your course follows).
Settling time defines practical stability: the time required for the response to stay within ยฑ2% (or ยฑ5%) of the final value permanently. For a standard second-order system:
(for the 2% criterion)
This formula shows that settling time is dominated by the product , which equals the real part of the dominant complex poles. Many real applications specify a maximum allowable settling time as a hard design constraint.
Overshoot is quantified as a percentage of the final value:
For a standard second-order system, overshoot depends only on the damping ratio:
Undershoot is a different phenomenon. It indicates non-minimum phase behavior, which occurs in systems with right-half-plane zeros. The initial response moves opposite to the final direction before correcting. This is physically meaningful: for example, an aircraft that briefly dips before climbing when you pull back on the stick.
"Transient response" is the umbrella term for all pre-steady-state behavior, encompassing rise time, overshoot, settling time, and oscillation characteristics. Two key principles:
Compare: Rise time vs. settling time: rise time measures how quickly you reach the target, while settling time measures how quickly you stay there. A system can have fast rise time but long settling time if it oscillates significantly. Exam questions often ask which parameter matters more for a given application.
These concepts address what happens as . A system can have perfect transient response but still fail if it doesn't accurately track the desired output.
Steady-state error is the persistent difference between desired and actual output:
Two factors determine its value:
Increasing loop gain reduces steady-state error, but higher gain can destabilize the system. This is one of the most fundamental trade-offs in control design.
These constants give you a direct way to calculate steady-state error for unity feedback systems:
| Constant | Definition | Steady-State Error |
|---|---|---|
| Position | (step input) | |
| Velocity | (ramp input) | |
| Acceleration | (parabolic input) |
Each constant corresponds to a progressively more demanding input. A system with finite but will track steps with some error but cannot track ramps at all (infinite error).
Compare: vs. vs. : exam problems often give you a transfer function and ask you to calculate steady-state error for different input types. The procedure is always the same: determine the system type, compute the relevant error constant, and plug into the formula.
These parameters capture how fast a system responds and what lags exist in the response. Both fundamentally limit achievable closed-loop performance, but in very different ways.
For a first-order system , the time constant is the time for the response to reach 63.2% of its final value. It relates directly to pole location:
where is the pole. A pole at gives seconds.
In higher-order systems, each pole contributes its own time constant. The dominant time constant (from the slowest pole, closest to the imaginary axis) often determines overall response speed. This is why the dominant pole approximation works: faster poles decay quickly and contribute little to the long-term response.
Pure time delay (also called dead time or transport lag) is modeled as in the transfer function. Unlike poles and zeros, a delay represents pure transportation lag with no dynamics.
Why delays are so problematic:
Compare: Time constant vs. time delay: both slow system response, but time constants represent dynamics (energy storage in capacitors, springs, thermal mass) while delays represent pure lag (fluid traveling through a pipe, signal propagation). A time constant can be compensated with derivative action; a delay cannot. This distinction frequently appears in controller design problems.
These analytical tools determine whether a system will behave predictably or diverge. Stability is non-negotiable: an unstable system is useless regardless of other performance metrics.
Three main approaches to stability analysis:
Poles determine the natural response modes. Each pole contributes an exponential or oscillatory term to the time response:
Zeros affect response amplitude and shape. They can reduce overshoot (left-half-plane zeros near dominant poles) or cause non-minimum phase behavior (right-half-plane zeros).
The dominant poles approximation says that poles closest to the imaginary axis dominate the response because their associated terms decay most slowly. Poles far to the left decay quickly and can often be neglected for approximate analysis.
Root locus tracks how closed-loop pole locations move as feedback gain varies from 0 to . It serves as both an analysis and design tool:
Compare: Routh-Hurwitz vs. root locus: Routh-Hurwitz tells you if a system is stable for a specific gain. Root locus shows how stability changes across all gains. Use Routh-Hurwitz for quick stability checks; use root locus when designing for specific transient response characteristics.
These frameworks provide the language for analyzing and designing control systems.
State-space describes a system using matrix equations:
where is the state vector, is the input, and is the output.
Why state-space matters:
Compare: Transfer function vs. state-space: transfer functions only capture input-output behavior; state-space reveals internal structure. Two systems can have identical transfer functions but different state-space realizations with different controllability and observability properties.
| Concept | Best Examples |
|---|---|
| Response speed metrics | Rise time, time constants, settling time |
| Stability indicators | Pole locations, Routh-Hurwitz, overshoot percentage |
| Steady-state accuracy | Steady-state error, , , |
| System characterization | Step response, impulse response, ramp response |
| Graphical analysis tools | Root locus, pole-zero plots |
| Mathematical models | Transfer functions, state-space representation |
| Performance trade-offs | Rise time vs. overshoot, gain vs. stability |
| Practical limitations | Time delays, time constants |
A second-order system has 15% overshoot and 2-second settling time. If you increase the damping ratio, what happens to both overshoot and rise time?
Which error constant (, , or ) would you use to find steady-state error for a system tracking a linearly increasing reference? What system type is required for zero error?
Compare the information provided by step response analysis versus impulse response analysis. Why might an engineer prefer one over the other in practice?
A system has poles at and . Which pole dominates the transient response, and approximately what is the system's time constant?
Explain why time delay is more problematic for stability than a large time constant, even if both slow down the system response. How does each affect phase margin differently?