Disturbance rejection in Simulink - Deep Dive

Overview - Disturbance rejection

What is it?

Disturbance rejection is the ability of a system to reduce or eliminate the effect of unexpected changes or disturbances on its output. In control systems, disturbances are unwanted inputs that can cause the system to behave incorrectly. Disturbance rejection techniques help keep the system stable and performing well despite these disruptions. This concept is important for making systems reliable and predictable in real-world conditions.

Why it matters

Without disturbance rejection, systems would react unpredictably to changes like noise, environmental shifts, or sudden inputs, causing poor performance or failure. For example, a temperature control system without disturbance rejection might let the room get too hot or cold when a door opens. Disturbance rejection ensures smooth operation and safety, which is critical in industries like manufacturing, robotics, and transportation.

Where it fits

Before learning disturbance rejection, you should understand basic control system concepts like feedback loops and system stability. After mastering disturbance rejection, you can explore advanced control strategies such as robust control and adaptive control that handle more complex uncertainties.

Mental Model

Core Idea

Disturbance rejection is about detecting unwanted changes and adjusting the system to keep the output steady and correct.

Think of it like...

Imagine you are riding a bike on a windy day. The wind pushes you off balance, but you steer and adjust your body to stay on the path. Disturbance rejection is like your brain and muscles working together to keep you steady despite the wind.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│   Disturbance │──────▶│   System      │──────▶│   Output      │
│   (unwanted)  │       │   Controller  │       │   (desired)   │
└───────────────┘       └───────────────┘       └───────────────┘
          ▲                      │                      │
          │                      │                      │
          └──────────────────────┴──────────────────────┘
                 Feedback loop adjusts system to reject disturbance

Build-Up - 6 Steps

1

Foundation

Understanding disturbances in systems

Concept: Introduce what disturbances are and how they affect system outputs.

Disturbances are unexpected inputs or changes that affect a system's behavior. For example, in a temperature control system, opening a window lets cold air in, which is a disturbance. These disturbances cause the output to deviate from the desired value.

Result

You can identify disturbances as external factors that push the system away from its goal.

Understanding disturbances as external influences helps you see why systems need ways to handle unexpected changes.

2

Foundation

Basics of feedback control

Concept: Explain how feedback loops help correct errors caused by disturbances.

A feedback control system measures the output and compares it to the desired value. If there is a difference (error), the controller adjusts inputs to reduce this error. This process helps the system respond to disturbances by correcting deviations.

Result

Feedback loops allow systems to self-correct and maintain stability despite disturbances.

Knowing how feedback works is essential because disturbance rejection relies on feedback to detect and fix errors.

3

Intermediate

Measuring disturbance rejection performance

🤔Before reading on: do you think disturbance rejection means completely eliminating disturbances or just reducing their effect? Commit to your answer.

Concept: Introduce metrics like disturbance attenuation and steady-state error to evaluate how well a system rejects disturbances.

Disturbance rejection is measured by how much the system output changes when a disturbance occurs. Perfect rejection means no change, but usually, systems reduce the effect to an acceptable level. Steady-state error shows the difference between desired and actual output after the system settles.

Result

You learn to quantify disturbance rejection and compare different control designs.

Understanding performance metrics helps you design and tune controllers to meet real-world requirements.

4

Intermediate

Designing controllers for disturbance rejection

🤔Before reading on: do you think a simple controller can reject all disturbances effectively? Commit to your answer.

Concept: Explain how controllers like PID adjust system inputs to reduce disturbance effects.

A PID controller uses proportional, integral, and derivative actions to respond to errors. The integral part is especially important for disturbance rejection because it accumulates error over time and eliminates steady-state error caused by constant disturbances.

Result

Controllers can be tuned to improve disturbance rejection by balancing responsiveness and stability.

Knowing the role of each controller part helps you understand how to improve disturbance rejection in practice.

5

Advanced

Using Simulink for disturbance rejection simulation

🤔Before reading on: do you think simulation can predict real system disturbance rejection perfectly? Commit to your answer.

Concept: Show how to model systems and disturbances in Simulink to test disturbance rejection strategies.

In Simulink, you build block diagrams representing the system, controller, and disturbances. You can simulate how the system responds to disturbances like step changes or noise. This helps you visualize and tune disturbance rejection before real implementation.

Result

You get hands-on experience with disturbance rejection and can experiment safely.

Simulation bridges theory and practice, allowing safe exploration of control strategies.

6

Expert

Limitations and trade-offs in disturbance rejection

🤔Before reading on: do you think improving disturbance rejection always improves overall system performance? Commit to your answer.

Concept: Discuss how aggressive disturbance rejection can cause instability or slow response, and the trade-offs involved.

Improving disturbance rejection often requires stronger controller action, which can make the system oscillate or react too slowly to other changes. Designers must balance disturbance rejection with stability and speed. Advanced methods like robust control handle these trade-offs better.

Result

You understand that disturbance rejection is not about maximum correction but optimal balance.

Recognizing trade-offs prevents over-tuning and system failures in real applications.

Under the Hood

Disturbance rejection works by continuously measuring the system output and comparing it to the desired value. The controller calculates the error and adjusts inputs to counteract disturbances. Internally, this involves feedback loops, error integration, and dynamic adjustments that happen in real time. The system's ability to reject disturbances depends on controller design, sensor accuracy, and system dynamics.

Why designed this way?

Control systems were designed with feedback to mimic natural regulation processes, like body temperature control. Early open-loop systems could not handle disturbances well. Feedback and disturbance rejection evolved to improve reliability and performance in unpredictable environments. Trade-offs between complexity, cost, and performance shaped current designs.

┌───────────────┐      error      ┌───────────────┐      control      ┌───────────────┐
│   Desired     │───────────────▶│   Comparator  │───────────────▶│   Controller  │
│   Output      │                │               │                │               │
└───────────────┘                └───────────────┘                └───────────────┘
        ▲                              ▲                                │
        │                              │                                │
        │                              │                                ▼
┌───────────────┐                ┌───────────────┐                ┌───────────────┐
│   Actual      │◀──────────────│   System      │◀──────────────│   Disturbance │
│   Output      │                │               │                │               │
└───────────────┘                └───────────────┘                └───────────────┘

Myth Busters - 3 Common Misconceptions

Quick: Does disturbance rejection mean the system never changes output when disturbed? Commit yes or no.

Common Belief: Disturbance rejection means the system output never changes no matter what disturbance occurs.

Reality: Disturbance rejection means reducing the effect of disturbances, not completely eliminating them. Some disturbance impact is inevitable.

Why it matters: Expecting perfect rejection leads to over-designed controllers that can cause instability or excessive cost.

Quick: Is the integral part of a PID controller optional for disturbance rejection? Commit yes or no.

Common Belief: Only the proportional part of a PID controller is needed for disturbance rejection.

Reality: The integral part is crucial because it removes steady-state errors caused by constant disturbances.

Why it matters: Ignoring integral action results in persistent errors and poor disturbance rejection.

Quick: Can disturbance rejection be improved infinitely by increasing controller gain? Commit yes or no.

Common Belief: Increasing controller gain always improves disturbance rejection.

Reality: Too high gain can cause oscillations and instability, worsening performance.

Why it matters: Misunderstanding this leads to unstable systems that fail in real use.

Expert Zone

1

Disturbance rejection performance depends heavily on sensor noise characteristics, which can limit achievable accuracy.

2

Nonlinearities in real systems can cause disturbance rejection methods designed for linear models to fail or behave unpredictably.

3

Time delays in feedback loops reduce disturbance rejection effectiveness and require special compensation techniques.

When NOT to use

Disturbance rejection techniques relying on feedback are less effective in systems with very fast or unpredictable disturbances; feedforward control or adaptive control methods may be better alternatives.

Production Patterns

In industry, disturbance rejection is often implemented using PID controllers tuned via methods like Ziegler-Nichols, combined with filters to reduce sensor noise. Advanced systems use model predictive control or robust control to handle complex disturbances and uncertainties.

Connections

Robust control

Builds on disturbance rejection by handling model uncertainties and worst-case disturbances.

Understanding disturbance rejection is foundational to grasping robust control, which extends these ideas to more challenging real-world conditions.

Biological homeostasis

Shares the principle of maintaining stable internal conditions despite external changes.

Recognizing this connection helps appreciate how natural systems inspired control theory concepts like disturbance rejection.

Noise filtering in signal processing

Both aim to reduce unwanted effects (disturbances or noise) to recover desired signals or outputs.

Knowing how filtering works in signals helps understand how control systems reject disturbances by filtering error signals.

Common Pitfalls

#1 Ignoring steady-state error caused by constant disturbances.

Wrong approach:

Using only proportional control: u = Kp * error

Correct approach:

Using PID control with integral action: u = Kp * error + Ki * integral(error) + Kd * derivative(error)

Root cause:

Misunderstanding that proportional control alone cannot eliminate steady-state error.

#2 Setting controller gain too high to reject disturbances faster.

Wrong approach:

Increasing Kp to a very large value without tuning other parameters.

Correct approach:

Carefully tuning Kp, Ki, and Kd to balance speed and stability.

Root cause:

Believing that more aggressive control always improves performance.

#3 Not modeling disturbances in simulation leading to unrealistic expectations.

Wrong approach:

Simulating system without adding disturbance blocks in Simulink.

Correct approach:

Including disturbance inputs like step or noise blocks to test rejection.

Root cause:

Overlooking the importance of realistic disturbance modeling in design.

Key Takeaways

Disturbance rejection helps systems maintain desired outputs despite unexpected changes.

Feedback control, especially integral action, is key to reducing disturbance effects.

Simulation tools like Simulink allow safe testing and tuning of disturbance rejection strategies.

Improving disturbance rejection involves trade-offs with stability and response speed.

Understanding real-world limitations and noise is essential for effective disturbance rejection design.

Practice

1. What is the main goal of disturbance rejection in a Simulink control system?

easy

A. To keep the system output stable despite external changes

B. To increase the system's input signal strength

C. To remove all feedback loops from the system

D. To make the system run faster without delays

Solution

1. Step 1: Understand disturbance rejection purpose

   Disturbance rejection aims to keep the system output steady even when outside changes happen.

2. Step 2: Compare options to this goal

   Only To keep the system output stable despite external changes matches this goal by focusing on output stability despite disturbances.

3. Final Answer:

   To keep the system output stable despite external changes -> Option A

4. Quick Check:

   Disturbance rejection = output stability [OK]

Hint: Disturbance rejection means steady output despite changes [OK]

Common Mistakes:

• Confusing disturbance rejection with increasing input
• Thinking disturbance rejection removes feedback loops
• Assuming it speeds up the system only

2. Which Simulink block is commonly used to reduce the effect of disturbances in a control system?

easy

A. PID Controller block

B. Gain block

C. Scope block

D. Mux block

Solution

1. Step 1: Identify blocks that affect disturbance

   PID Controller blocks adjust system response to reduce disturbance effects.

2. Step 2: Eliminate unrelated blocks

   Gain changes signal strength, Scope shows signals, Mux combines signals but doesn't reduce disturbances.

3. Final Answer:

   PID Controller block -> Option A

4. Quick Check:

   PID Controller reduces disturbances [OK]

Hint: PID blocks help control disturbances in Simulink [OK]

Common Mistakes:

• Choosing Scope block which only displays signals
• Confusing Gain block with disturbance rejection
• Selecting Mux block which combines signals

3. Given this Simulink feedback loop with a disturbance input, what will happen if the PID controller gains are set too low?

Disturbance --> + --> System --> Output
               ^                 |
               |-----------------|
               PID Controller

medium

A. The system output will oscillate rapidly

B. The system output will closely follow the disturbance

C. The system output will reject the disturbance completely

D. The system output will be zero regardless of disturbance

Solution

1. Step 1: Understand low PID gains effect

   Low PID gains mean weak correction to disturbances, so system output follows disturbance closely.

2. Step 2: Analyze other options

   Complete rejection needs strong gains, oscillation usually comes from too high gains, zero output is unrealistic here.

3. Final Answer:

   The system output will closely follow the disturbance -> Option B

4. Quick Check:

   Low gains = poor disturbance rejection [OK]

Hint: Low PID gains mean weak disturbance correction [OK]

Common Mistakes:

• Assuming low gains cause oscillations
• Thinking output will be zero regardless
• Believing disturbance is fully rejected with low gains

4. You have a Simulink model with a disturbance rejection loop, but the output still shows large fluctuations. Which of these is the most likely error?

medium

A. The feedback loop is missing the disturbance input

B. The system has no input signal

C. The Scope block is not connected properly

D. The PID controller gains are set too high causing instability

Solution

1. Step 1: Identify cause of large output fluctuations

   High PID gains can cause the system to become unstable and oscillate, causing large fluctuations.

2. Step 2: Check other options

   Missing disturbance input means no disturbance effect, Scope connection affects display only, no input signal means no output but not fluctuations.

3. Final Answer:

   The PID controller gains are set too high causing instability -> Option D

4. Quick Check:

   High gains cause instability and fluctuations [OK]

Hint: Too high PID gains cause unstable output [OK]

Common Mistakes:

• Blaming Scope block for output fluctuations
• Ignoring PID gain settings
• Assuming missing disturbance input causes fluctuations

5. You want to design a Simulink model that rejects a sudden step disturbance affecting the system output. Which combination of blocks and settings is best to achieve fast disturbance rejection with minimal overshoot?

hard

A. Use a Scope block to monitor output and manually adjust input

B. Use only a Gain block with high gain and no feedback loop

C. Use a PID Controller block with tuned proportional and derivative gains, plus a feedback loop including the disturbance input

D. Use a Mux block to combine disturbance and input signals without control

Solution

1. Step 1: Identify blocks for disturbance rejection

   PID Controller with tuned gains helps react quickly and reduce overshoot; feedback loop is needed to correct disturbances.

2. Step 2: Evaluate other options

   Gain block alone cannot reject disturbances well; Scope only monitors signals; Mux combines signals but does not control.

3. Final Answer:

   Use a PID Controller block with tuned proportional and derivative gains, plus a feedback loop including the disturbance input -> Option C

4. Quick Check:

   PID + feedback = fast, minimal overshoot rejection [OK]

Hint: Combine PID with feedback loop for best disturbance rejection [OK]

Common Mistakes:

• Relying on Gain block without feedback
• Using Scope as control instead of monitoring
• Ignoring feedback loop importance