How to measure Overshoot Undershoot Settling time in Simulink

Understanding the dynamic behavior of control systems is essential, especially when designing or tuning controllers. In this tutorial, we’ll walk through how to measure overshoot, undershoot, and settling time from the scope window in Simulink, using a simple second-order system as an example.

Setting Up the System in Simulink

To begin, we need a transfer function to analyze. In this example, we use a second-order system with the form:1 / (s² + s + 1)

A constant input of value 1 is applied to the system. This simple input allows us to focus on how the system responds over time, making it easier to observe the key characteristics of the output waveform.

Running the Simulation

After setting up the system and input, the simulation is run. To better visualize the response, the simulation time is increased (e.g., up to 100 seconds). Once the simulation is complete, the system’s response to the input can be viewed through the Scope block in Simulink.

The output typically shows a curve that rises, possibly overshoots the final value, and then settles into a steady state. This curve helps us determine the overshoot, undershoot, and settling time.

Accessing Measurement Tools in Scope

To measure key response parameters:

Click the measurement arrow icon in the Scope window.
Select “Cursor Measurements” or “Peak Response (Overshoot/Undershoot)”.
The scope will now display values such as Overshoot, Undershoot, and other peak response data directly on the graph or in a side panel.

This tool simplifies identifying how much the signal exceeds (overshoots) or dips below (undershoots) the final value.

Enabling Settling Time Measurement

Sometimes, the settling time is not immediately visible. To enable it:

Click the Settings icon in the Scope window.
Locate the Settling Time Tolerance parameter.
By default, it might be set too low (e.g., 0.02 seconds). If your system takes longer to settle, increase this value. In the example, it is changed to 25 seconds.
Once adjusted, the settling time will appear, helping you understand how long it takes for the system to reach and stay within a certain range of the final value.

In our demonstration, the measured settling time was approximately 6.96 seconds.

Why These Measurements Matter

Knowing the overshoot, undershoot, and settling time is crucial when:

Evaluating system stability
Tuning controllers (like PID controllers)
Comparing different system designs or responses

These metrics give insight into how responsive and stable your system is—key information when optimizing for performance or reliability.