Control Theory Overview
Why control theory exists
Control theory is the engineering discipline for making a system behave as intended despite disturbance, noise, and model error.
A PID loop is only one layer. This page maps the full workflow — plant, feedback, controller, estimator, and verification — so you can see where each concept fits before going deeper.
The control loop in one picture
flowchart LR
R["Reference / Setpoint r"] --> C["Controller"]
C --> U["Control Input u"]
U --> P["Plant / Process"]
P --> Y["Output y"]
D["Disturbance d"] --> P
P --> S["Sensors"]
S --> M["Measured Signal"]
M --> E["Estimator / Filter"]
E --> FB["Feedback"]
FB --> C
P --> X["True State x"]
Every element below maps back to a block in this diagram.
Control system at a glance
The physical system being controlled — motor, process, vehicle, or machine axis.
Computes actuator commands from reference and feedback. PID is one option among many.
Turn noisy measurements into usable feedback. Not all states are directly measured.
Check stability, margins, and real-world behavior before commissioning.
Open-loop vs closed-loop
Open-loop
flowchart LR
R1["Reference"] --> C1["Controller"]
C1 --> P1["Plant"]
P1 --> Y1["Output"]
- Command based on model or assumption
- Fast and simple
- No self-correction — weak against disturbance
Use when: disturbances are small and the plant model is accurate (e.g. feedforward terms in a combined controller).
Closed-loop
flowchart LR
R2["Reference"] --> SUM(("Σ"))
SUM --> C2["Controller"]
C2 --> P2["Plant"]
P2 --> Y2["Output"]
Y2 --> H2["Sensor"]
H2 --> SUM
- Command based on measured response
- Self-correcting against disturbance and model error
- Can improve or damage stability if badly designed
Use when: disturbance, uncertainty, or safety require verified tracking (nearly all industrial control).
Where PID fits
PID is the most common industrial controller — but it is one block in a larger architecture.
flowchart TD
A["Planning / Recipe / Motion Profile"] --> B["Reference Generation"]
B --> C["Controller: PID / State Feedback / MPC"]
C --> D["Actuator / Drive / Valve / VFD"]
D --> E["Plant / Machine / Process"]
E --> F["Sensors"]
F --> G["Filtering / State Estimation"]
G --> C
E --> H["Verification: Bode / Nyquist / Simulation"]
- Above PID: recipe management, motion profiles, setpoint scheduling
- Below PID: actuator dynamics, drive/VFD response, valve characteristics
- Beside PID: state estimation, filtering, feedforward terms
- After PID: verification of stability and performance margins
Beyond PID — controller families
| Family | Best for | Typical examples | Industrial use |
|---|---|---|---|
| Classical | Simple loops, machines, process control | PID, lead/lag | Very high |
| State-space | Multivariable and model-based design | Full-state feedback, observer-based control | Medium |
| Robust | Uncertainty-heavy plants | H-infinity, μ-synthesis, ADRC | Medium |
| Adaptive | Changing dynamics | MRAC, gain scheduling | Medium |
| Optimal | Performance tradeoff tuning | LQR | Medium |
| Predictive | Constraints and multivariable control | MPC | High (advanced) |
| Intelligent | Heuristic or learned behavior | Fuzzy, RL | Specialized |
Industrial reality: PID handles the vast majority of single-loop process and machine control. State-space, MPC, and gain scheduling appear in coordinated axes, thermal systems, and advanced process plants.
What the controller really sees
Real controllers act on sensor measurements, not the true plant state. Measurements include noise, bias, and latency.
Observability means the controller can reconstruct the internal states it needs from the measurements it has. If a state is not observable, no estimator can recover it.
flowchart LR
X["True State x"] --> P["Plant"]
P --> Y["Measured Output y"]
Y --> N["Noise / Bias"]
N --> K["Estimator"]
K --> XH["Estimated State x̂"]
XH --> C["Controller"]
| Method | When to use |
|---|---|
| Kalman filter | Linear systems with Gaussian noise |
| Particle filter | Nonlinear or non-Gaussian problems |
| Running average | Simple smoothing when no model is needed |
| Luenberger observer | Deterministic state reconstruction from a known model |
How engineers verify control performance
flowchart LR
M["Model"] --> S["Simulation"]
S --> FR["Frequency Response"]
FR --> ST["Stability Margins"]
ST --> HW["Hardware Test"]
HW --> TUNE["Retune / Validate"]
| Tool | What it tells you |
|---|---|
| Bode plot | Frequency response — gain margin, phase margin |
| Nyquist diagram | Closed-loop stability from open-loop transfer function |
| Simulation | Validate response before commissioning |
| Hardware test | Confirm behavior under real disturbance, load, noise, and saturation |
Rule of thumb: simulate first, then commission. Retuning on live hardware without simulation is a common source of instability incidents.
References and further reading
Core theory
| Source | Covers |
|---|---|
| MIT OCW — Feedback Control Systems (16.30) | Feedback, state-space, frequency response, estimator framing |
| Caltech — State Estimation notes (Murray) | Observer and Kalman filter concepts |
| CMU — State Estimation, Observers, and Kalman Filters | Accessible bridge from control theory to robotics and software |
Analysis tools
| Source | Covers |
|---|---|
| MathWorks — Bode Plot documentation | Frequency response, gain margin, phase margin |
| MathWorks — Nyquist Plot documentation | Closed-loop stability from open-loop data |
Industrial context (this site)
| Topic | Page |
|---|---|
| PID intuition and tuning | PID Foundation · PID in Practice |
| Servo and VFD commissioning | Servo Commissioning · VFD Commissioning |
| Safety instrumented systems | IEC 61511 · IEC 62443 |
Where to go next
| If you want to… | Go to |
|---|---|
| Build PID intuition without heavy math | PID Control — Intuitive Foundation |
| See P, I, and D terms in practice | PID Intuition — P, I, and D in Practice |
| Understand industrial PID implementation | Industrial PID Implementation |
| See loop architecture patterns | Control Loop Architectures |
| Commission a VFD or servo | VFD Commissioning · Servo Commissioning |
| Understand safety instrumented systems | IEC 61511 |
This site is an independent educational reference for industrial automation standards. It paraphrases and organizes guidance in original language; it is not a substitute for the official published standards, professional engineering judgment, or legal review, and content has not been independently verified against current published editions.
Items marked Review pending await technical review against the identified edition. Items marked Planned have no reviewed source material behind them. Do not rely on this site for compliance determinations, safety-critical design decisions, or legal interpretation.