Written and maintained by CASRAI Editorial Board
Published
On this page
MATLAB Control System Toolbox is MathWorks’ add-on product for analysing, designing and tuning linear control systems. You build a model of a plant or controller (transfer function, state-space, zero-pole-gain or frequency-response data), check its behaviour with functions such as step, stepinfo and bode, and tune compensators either interactively in the Control System Designer app or with automatic tuning for SISO and MIMO loops, including PID and gain-scheduled controllers. This guide walks through that workflow with the commands exactly as the current MathWorks documentation gives them.
What Control System Toolbox is used for in research
MathWorks describes the toolbox as providing “algorithms and apps for systematically analyzing, designing, and tuning linear control systems.” In research practice that covers three jobs: representing a dynamic system as a linear model, analysing how that model responds in time and frequency, and tuning a controller until the closed loop meets numeric requirements.
- Modelling. Linear models can be created as transfer function, state-space, zero-pole-gain or frequency-response models.
- Analysis. The documentation lists step response and Bode plots as the standard analysis views, and describes validating rise time, overshoot, settling time and gain and phase margins against requirements.
- Tuning. You can tune interactively with Bode loop shaping and root locus, or automatically tune SISO and MIMO compensators, including PID controllers and gain-scheduled controllers.
Control engineering results are often reported as exactly these quantities, which is why a reproducible script is worth more than a screenshot of a plot. If you only need the transfer-function syntax, the sibling guides tf in MATLAB and transfer functions in MATLAB go deeper on that single step, and Bode plots in MATLAB covers frequency-response plotting in detail.
Install or access
Control System Toolbox is a MATLAB product, so the functions below exist only in a MATLAB installation that includes it. The official starting point is the MathWorks documentation page “Getting Started with Control System Toolbox” (https://www.mathworks.com/help/control/getting-started-with-control-system-toolbox.html); the same help tree documents every function named in this guide. For installing MATLAB itself, see the CASRAI guides on MATLAB installation and running MATLAB on Linux.
Some features you may expect to find in the toolbox are documented as requiring other products. Check the dependency notes before you plan a workflow around them:
- Uncertain models (the
ussobject) need Robust Control Toolbox. - Identified models such as
idtfneed System Identification Toolbox. - Tuning a controller in a Simulink model from the Control System Designer app needs Simulink Control Design.
- Optimisation-based tuning needs Simulink Design Optimization.
Step-by-step: from a model to a tuned response
The sequence below uses only syntax shown in the MathWorks reference pages. Run each command in the MATLAB Command Window or a script.
1. Create a transfer function model
Use tf with numerator and denominator coefficients, listed in the order shown in the documentation example:
numerator = 1;
denominator = [2,3,4];
sys = tf(numerator,denominator)
The reference page shows this producing the continuous-time transfer function 1/(2 s^2 + 3 s + 4). The call returns a tf object for numeric input, a genss model if the input is tunable, and a uss model if it is uncertain. You can also define the Laplace variable and write the model as an expression:
s = tf('s');
2. Plot the step response
With no output arguments, step draws the response:
step(sys)
To limit the simulation to 15 seconds use step(sys,15); to overlay two models use step(sys1,sys2). To get the numbers instead of a plot, request outputs:
[y,tOut] = step(sys);
For a MIMO model, step plots an array of responses, and in the returned data y(:,i,j) is the response from input j to output i. Name=Value options include Bias, Amplitude, Delay and InitialCondition.
3. Quantify the response with stepinfo
S = stepinfo(sys)
This returns a structure of response characteristics (listed in the table below). To change the definitions, pass options, for example stepinfo(sys,SettlingTimeThreshold=0.005,RiseTimeLimits=[0.05 0.95]).
4. Plot the frequency response
H = tf([1 0.1 7.5],[1 0.12 9 0 0]);
bode(H)
bode plots magnitude in decibels and phase in degrees against frequency. Use [mag,phase,wout] = bode(sys) to return the data instead of plotting, and bode(H,{1,100}) to restrict the frequency range.
5. Tune a controller in Control System Designer
- Open the app by typing
controlSystemDesignerin the Command Window, or from the Apps tab choose Control System Design and Analysis. From Simulink, use Apps tab, then Control Systems. - Load your plant. The scripted form is
controlSystemDesigner(plant,comp,sensor,prefilt), and you can choose the opening views with"rlocus","bode","nichols"or"filter". - Design the SISO controller with the interactive Bode, root locus or Nichols editors, or use the automated PID, LQG or IMC tuning.
- Analyse the closed loop and compare candidate designs in the Data Browser.
- Export the tuned blocks from the Control System tab, or choose Create Simulink Model; use Save Session to keep your work.
Output and how to read it
stepinfo is the quickest way to turn a plot into reportable numbers. The reference page defines these fields, with default thresholds of 2 percent for settling time (SettlingTimeThreshold=0.02) and 10 to 90 percent for rise time (RiseTimeLimits=[0.1 0.9]).
| Field | What it reports |
|---|---|
| RiseTime | Time to rise between the rise-time limits (default 10 to 90 percent of the steady-state value) |
| TransientTime | Transient time of the response |
| SettlingTime | Time to settle within the settling threshold (default 2 percent) |
| SettlingMin, SettlingMax | Minimum and maximum of the response after the rise |
| Overshoot, Undershoot | Percentage overshoot and undershoot |
| Peak, PeakTime | Peak absolute value of the response and the time it occurs |
The documentation’s worked example uses sys = tf([1 5 5],[1 1.65 5 6.5 2]). Running stepinfo(sys) on it gives approximately RiseTime 3.85, SettlingTime 27.98, Overshoot 7.49 (percent), Peak 2.69 and PeakTime 8.05 (time values in the model’s time units). Use that example to confirm your installation behaves as documented before you apply the same calls to your own plant.
On a Bode plot, read magnitude in dB on the upper axis and phase in degrees on the lower axis, both against frequency. The toolbox overview names gain and phase margins as the quantities to validate against design requirements.
Troubleshooting
The step response looks stable but the system is not
The step reference page includes an internal-delay example in which the default step plot can hide instability. A finer time vector, 0:1e-2:500 in that example, reveals it. If a model has delays, do not trust the default time grid alone; pass an explicit time vector or span.
A function or model type is not recognised
Check the dependency list in the Install or access section. uss models, idtf identified models, Simulink-model tuning and optimisation-based tuning each belong to a separate product.
The transfer function is not what you intended
Print the model after creating it. In the documentation example, [2,3,4] produces 2 s^2 + 3 s + 4, so coefficients run from the highest power of s down. A reversed vector gives a different system.
stepinfo values do not match a published figure
Check the thresholds. The defaults are 2 percent settling and 10 to 90 percent rise; a paper that used 5 percent settling or 5 to 95 percent rise limits needs the matching Name=Value options.
Free alternatives
Two open-source packages cover similar linear-control ground. The data table below compares the toolbox with them on the facts their documentation states.
| Tool | What its documentation says it is | Environment |
|---|---|---|
| python-control | A package that “provides common functions for analyzing and designing feedback control systems”; includes a MATLAB compatibility module that offers many commands corresponding to the MATLAB Control Systems Toolbox | Python; requires NumPy and SciPy, Matplotlib for plotting, optional Slycot |
| Octave control package | “Control package for GNU Octave including system analysis and control synthesis”, using routines from the SLICOT-Reference library; GPL-3.0-or-later and BSD-3-Clause | GNU Octave 6.4.0 or later (version 4.3.0 of the package) |
If your wider workflow is a MATLAB-versus-open-source decision, the CASRAI comparison MATLAB vs R sets out the trade-offs at the language level. Whichever tool you use, record the toolbox or package version in your methods so the analysis can be reproduced.
Frequently asked questions
What is MATLAB Control System Toolbox?
It is a MathWorks product that provides algorithms and apps for analysing, designing and tuning linear control systems, using transfer function, state-space, zero-pole-gain and frequency-response models.
How do I open the Control System Designer app?
Type controlSystemDesigner in the Command Window, or use the Apps tab and choose Control System Design and Analysis. In Simulink, use Apps tab, then Control Systems.
Which function gives overshoot and settling time?
stepinfo(sys) returns Overshoot and SettlingTime, along with RiseTime, Peak, PeakTime and other fields, with default thresholds of 2 percent for settling and 10 to 90 percent for rise time.
Does the toolbox tune PID controllers?
Yes. MathWorks lists automatic tuning of SISO and MIMO compensators, including PID and gain-scheduled controllers, and the Control System Designer app also offers automated PID, LQG and IMC tuning for SISO designs.
Can I tune a Simulink model from the app?
Yes, but the documentation states that Simulink models require Simulink Control Design.
Sources
- MathWorks, Getting Started with Control System Toolbox, https://www.mathworks.com/help/control/getting-started-with-control-system-toolbox.html (read 2026-11-15)
- MathWorks, tf reference, https://www.mathworks.com/help/control/ref/tf.html (read 2026-11-15)
- MathWorks, step reference, https://www.mathworks.com/help/control/ref/dynamicsystem.step.html (read 2026-11-15)
- MathWorks, stepinfo reference, https://www.mathworks.com/help/control/ref/dynamicsystem.stepinfo.html (read 2026-11-15)
- MathWorks, bode reference, https://www.mathworks.com/help/control/ref/dynamicsystem.bode.html (read 2026-11-15)
- MathWorks, controlSystemDesigner reference, https://www.mathworks.com/help/control/ref/controlsystemdesigner-app.html (read 2026-11-15)
- python-control documentation, https://python-control.readthedocs.io/en/latest/intro.html (read 2026-11-15)
- GNU Octave packages, control, https://gnu-octave.github.io/packages/control/ (read 2026-11-15)
Data: MATLAB Control System Toolbox: task, function, output and extra product needed
Maps common linear-control tasks to the documented Control System Toolbox function or app, what it returns, and any additional MathWorks product the documentation says is required. Compiled from the MathWorks reference pages.
| Task | Function or app | Output | Additional product documented as required |
|---|---|---|---|
| Create a transfer function | tf(numerator,denominator) | tf object (genss if tunable, uss if uncertain) | Robust Control Toolbox for uncertain (uss) models |
| Create an identified transfer function | idtf | Identified model | System Identification Toolbox |
| Plot or compute a step response | step(sys) | Plot, or [y,tOut] data | None stated |
| Measure rise time, settling time, overshoot | stepinfo(sys) | Structure of response characteristics | None stated |
| Plot frequency response | bode(sys) | Magnitude (dB) and phase (deg) vs frequency | None stated |
| Tune a SISO controller interactively | controlSystemDesigner | Tuned compensator, exportable blocks or Simulink model | Simulink Control Design for Simulink models |
| Optimisation-based controller tuning | controlSystemDesigner | Tuned controller parameters | Simulink Design Optimization |
Sources
- MathWorks tf reference (accessed 2026-11-15)
- MathWorks step reference (accessed 2026-11-15)
- MathWorks stepinfo reference (accessed 2026-11-15)
- MathWorks bode reference (accessed 2026-11-15)
- MathWorks controlSystemDesigner reference (accessed 2026-11-15)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







