Introduction to Feedback Control
Control systems engineering studies how to make a dynamic system behave in a desired way despite uncertainty, disturbances, and imperfect components. Nise's opening chapter frames the subject as a design loop: translate requirements into a physical system, draw the functional block diagram, derive a mathematical model, reduce interconnected subsystems, then analyze and redesign until transient response, steady-state error, and stability meet specifications.
The central idea is feedback. In an open-loop system the command passes forward to the plant without measuring the result. In a closed-loop system the output is sensed and compared with the reference, producing an error signal that drives correction. The price of feedback is extra hardware, modeling effort, and possible instability; the benefit is accuracy, disturbance rejection, and tunable dynamics. This page sets the vocabulary used by the modeling, response, stability, and design pages that follow.
![]()
Figure: Feedback loop block diagram in control theory. Image: Wikimedia Commons, Inductiveload, public domain.
Definitions
A control system is an interconnection of components whose purpose is to cause an output, often called the controlled variable, to follow or regulate against an input, often called the reference or command. A plant or process is the physical subsystem being controlled: a motor-load assembly, furnace, aircraft attitude channel, chemical reactor, disk-drive head, or antenna. A controller produces the actuator signal that drives the plant.
An open-loop system has no measurement of the controlled output in the decision path. If the input is and the plant output is , the command is processed according to a designed chain, but the actual is not compared with . Open-loop control is simple and cheap, but it cannot correct for unmodeled disturbances or parameter drift.
A closed-loop or feedback system measures the output and returns a signal through a sensor or output transducer. For negative feedback, the comparator forms
where is the feedback signal. If the sensor has unity gain, and is the tracking error. With controller , plant , and feedback , the closed-loop transfer function is
for negative feedback, assuming zero initial conditions and linear time-invariant models.
Nise emphasizes three major performance objectives. Transient response describes the part of the output before the long-term behavior is reached: speed, overshoot, ringing, and settling. Steady-state error is the final mismatch between command and output after transients die out. Stability asks whether the natural response decays, persists as a bounded oscillation, or grows without bound.
Standard test inputs include the impulse , step , ramp , parabolic input , and sinusoid . They are not arbitrary classroom choices: they expose different control properties. A step reveals transient behavior and position accuracy, a ramp reveals velocity tracking error, and sinusoids support frequency-response analysis.
Key results
The basic negative-feedback relation follows from the summing junction and block equations. Let the forward path be and the feedback path be . Then
so
This formula already shows why feedback can be helpful and dangerous. Large loop gain can reduce sensitivity to plant gain changes and disturbances entering after the controller, but the same denominator determines closed-loop poles. If those poles move into the right half of the -plane, the controlled system becomes unstable even when the open-loop plant is individually stable.
For unity feedback, the error transfer function is
Thus increasing low-frequency loop gain tends to reduce tracking error for slowly varying inputs. This is the intuitive basis for proportional gain, integral action, lag compensation, and high-gain designs. It is also why Nise repeatedly returns to trade-offs: gain that improves error may worsen overshoot or reduce stability margin.
The design process can be written as an engineering loop:
- Convert requirements into performance specifications.
- Choose a physical configuration and draw a functional block diagram.
- Derive a schematic and identify simplifying assumptions.
- Obtain a transfer-function, signal-flow, or state-space model.
- Reduce the model to a form suitable for analysis.
- Analyze, design, simulate, test, and revise.
This sequence is not strictly one pass. If testing shows that a neglected effect matters, the model is updated. If specifications conflict, the requirements must be renegotiated or a new controller structure introduced.
The first modeling judgment is where to draw the system boundary. A cruise-control problem may treat the engine and drivetrain as the plant, or it may include throttle actuator dynamics, tire slip, road grade, and sensor filtering. A temperature-control problem may treat the room as a single thermal capacitance, or it may include walls, vents, heater delay, and outdoor temperature. The boundary should include the dynamics that materially affect the specifications being claimed. Leaving out a fast amplifier may be harmless for a slow antenna, while leaving out a slow valve can invalidate a process-control design.
The second judgment is how to name signals. Good signal naming prevents mathematical mistakes later. The reference is the desired behavior expressed in controller-compatible units. The measured output may be rather than the physical output . The controller output may be a voltage, duty cycle, commanded torque, or valve position. Disturbances should be shown at their real entry points because feedback suppresses a load disturbance differently from sensor noise.
The third judgment is how to interpret specifications. "Fast" must become a settling-time, rise-time, or bandwidth requirement. "Accurate" must become a steady-state error limit for a specific class of inputs. "Not oscillatory" must become a damping-ratio, overshoot, or phase-margin target. "Robust" must be tied to gain variation, delay, disturbance rejection, or unmodeled high-frequency dynamics. Control design becomes tractable only after qualitative requirements are translated into measurable quantities.
Feedback also changes the economics of a design. A higher-quality sensor may reduce the burden on the controller. A larger actuator may allow faster response but increase cost and saturation risk. A more complex compensator may meet specifications but become harder to implement, tune, and maintain. Nise's design loop is therefore not purely mathematical: it repeatedly converts between physical choices, model assumptions, performance calculations, and implementation limits.
Finally, a control diagram should be read as a hypothesis. The arrows and transfer functions assert what affects what, which effects are linear, and which dynamics are negligible. Simulation and laboratory testing are not afterthoughts; they are the checks that decide whether the hypothesis is good enough. When the measured response disagrees with the model, the right response is not to force the data into the old block diagram, but to revisit assumptions such as friction, saturation, sensor delay, backlash, and parameter uncertainty.
Visual
| Feature | Open-loop control | Closed-loop control |
|---|---|---|
| Uses output measurement | No | Yes |
| Corrects disturbances | Only if modeled ahead of time | Yes, within bandwidth and actuator limits |
| Cost and complexity | Lower | Higher |
| Stability risk from feedback | None from feedback itself | Possible if closed-loop poles move to unstable region |
| Typical examples | toaster timer, fixed motor drive | thermostat, antenna positioning, cruise control |
| Main design variables | calibration and feedforward command | gain, compensator dynamics, sensor dynamics |
Worked example 1: closed-loop transfer function
Problem: A unity-feedback system has controller and plant
Find the closed-loop transfer function and determine the characteristic equation.
Method:
- Form the forward path:
- Use the unity-feedback formula:
- Substitute and clear the complex fraction:
- The characteristic equation is the denominator set to zero:
Checked answer: . For , the second-order denominator has positive coefficients, but later Routh-Hurwitz analysis will give the more general stability test. Here the roots have real part for all positive , so the system is stable for .
Worked example 2: disturbance rejection comparison
Problem: A plant output is affected by an additive constant disturbance after the plant. The forward path is with unity feedback. Compare the output due to a unit-step disturbance for open-loop and closed-loop operation when the reference is zero.
Method:
Open loop has no correction. If the disturbance is added directly at the output,
The final value is
For closed-loop operation with , write the output equation:
With unity negative feedback and zero reference,
Therefore
Substitute :
With ,
The final value is
Checked answer: feedback reduces the steady disturbance effect from to . The disturbance is not eliminated because the loop has finite dc gain .
Code
import numpy as np
from scipy import signal
K = 2.0
num = [10 * K]
den = [1, 2, 10 * K]
sys = signal.TransferFunction(num, den)
t = np.linspace(0, 8, 500)
t, y = signal.step(sys, T=t)
overshoot = (np.max(y) - y[-1]) / y[-1] * 100
settled_value = y[-1]
print(f"final value approx: {settled_value:.3f}")
print(f"percent overshoot approx: {overshoot:.1f}")
print(f"closed-loop poles: {np.roots(den)}")
Common pitfalls
- Treating feedback as automatically beneficial. Feedback changes the denominator of the closed-loop transfer function; it can create instability.
- Calling every summing-junction output an error. It is exactly the physical error only when the reference and feedback signals are in comparable units and sensor scaling is unity.
- Ignoring sensor dynamics. A slow or noisy sensor is part of the loop, not an afterthought.
- Confusing transient response with natural response. The visible transient is the portion of the total response before steady behavior dominates; the natural response is the system-dependent homogeneous component.
- Using only a step input. Different specifications require different tests: ramps for velocity error, sinusoids for frequency response, and impulses for natural dynamics.
Connections
- Laplace transfer functions develop the algebra behind block diagrams.
- Time response defines the transient specifications used in design.
- Routh-Hurwitz stability tests whether the feedback denominator is stable.
- Steady-state error quantifies the final tracking mismatch.
- Applied vehicle control uses the same feedback ideas in path tracking.