Speed control with PID in Simulink - Time & Space Complexity

Time Complexity: Speed control with PID

O(n)

Understanding Time Complexity

We want to understand how the time to run a PID speed control system changes as the input size grows.

Specifically, how does the system's computation time grow when controlling speed with a PID controller?

Scenario Under Consideration

Analyze the time complexity of the following Simulink PID control snippet.

// Simulink PID Speed Control Model
// 1. Read speed sensor input
// 2. Calculate error = desired speed - actual speed
// 3. PID block computes control signal
// 4. Apply control signal to motor
// 5. Loop repeats every time step

for each time step t {
  error(t) = setpoint - speed(t);
  control(t) = PID(error(t));
  speed(t+1) = motor(control(t));
}
    

This code controls motor speed by repeatedly calculating error and adjusting control signals using a PID controller at each time step.

Identify Repeating Operations

Look at what repeats as the system runs:

• Primary operation: The PID calculation and motor update happen once every time step.
• How many times: This repeats for each time step in the simulation or control period.

How Execution Grows With Input

As the number of time steps increases, the total operations increase linearly.

Input Size (n = time steps)	Approx. Operations
10	10 PID calculations and motor updates
100	100 PID calculations and motor updates
1000	1000 PID calculations and motor updates

Pattern observation: Doubling the time steps doubles the work because each step does a fixed amount of work.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows directly in proportion to the number of time steps.

Common Mistake

[X] Wrong: "The PID calculation time grows faster than the number of time steps because it does complex math."

[OK] Correct: Each PID calculation is a fixed set of operations done once per step, so total time grows linearly with steps, not faster.

Interview Connect

Understanding how control loops scale helps you explain system performance clearly and shows you can think about real-time system costs.

Self-Check

"What if the PID controller included nested loops for adaptive tuning at each step? How would the time complexity change?"

Practice

1. What is the main purpose of using a PID controller in speed control systems in Simulink?

easy

A. To randomly change the speed for testing

B. To increase the machine speed without limits

C. To stop the machine immediately

D. To keep the machine speed steady and close to the target

Solution

1. Step 1: Understand the role of PID controller

   A PID controller adjusts the speed by balancing three parts: proportional, integral, and derivative to maintain steady speed.

2. Step 2: Identify the main goal in speed control

   The goal is to keep the speed steady and close to the desired target, avoiding sudden changes or overshoot.

3. Final Answer:

   To keep the machine speed steady and close to the target -> Option D

4. Quick Check:

   PID controls speed stability = To keep speed steady [OK]

Hint: PID keeps speed steady near target by adjusting smoothly [OK]

Common Mistakes:

• Thinking PID increases speed without limit
• Believing PID causes random speed changes
• Assuming PID stops the machine immediately

2. Which of the following is the correct way to add a PID Controller block in Simulink for speed control?

easy

A. Drag the PID Controller block from the Simulink Library Browser and connect it to the motor model

B. Write pid() function in the MATLAB command window only

C. Use the 'Gain' block instead of PID Controller block

D. Add a 'Scope' block and rename it to PID Controller

Solution

1. Step 1: Identify how to add PID in Simulink

   Simulink uses blocks from its Library Browser; the PID Controller block is dragged and connected to the system.

2. Step 2: Check other options for correctness

   Writing pid() in MATLAB does not add a block in Simulink; 'Gain' block is not a PID; renaming 'Scope' does not create PID functionality.

3. Final Answer:

   Drag the PID Controller block from the Simulink Library Browser and connect it to the motor model -> Option A

4. Quick Check:

   PID block added by drag-drop in Simulink [OK]

Hint: Add PID block by dragging from Simulink Library [OK]

Common Mistakes:

• Trying to write PID code in MATLAB instead of using block
• Using Gain block as PID controller
• Renaming unrelated blocks to PID

3. Given this Simulink PID speed control setup, what will be the output speed if the setpoint is 1000 RPM and the PID gains are tuned correctly?

Setpoint = 1000 RPM
Initial speed = 0 RPM
PID gains: P=1, I=0.5, D=0.1
Simulation time = 10 seconds

medium

A. Speed will reach and stay close to 1000 RPM

B. Speed will stay at 0 RPM

C. Speed will overshoot to 2000 RPM and stay there

D. Speed will oscillate wildly without settling

Solution

1. Step 1: Understand PID tuning effect

   Properly tuned PID gains help the speed reach the setpoint smoothly without large overshoot or oscillations.

2. Step 2: Predict output behavior

   Starting from 0 RPM, the PID will increase speed to near 1000 RPM and maintain it steadily within simulation time.

3. Final Answer:

   Speed will reach and stay close to 1000 RPM -> Option A

4. Quick Check:

   Correct PID tuning = steady speed near setpoint [OK]

Hint: Good PID tuning means speed reaches setpoint smoothly [OK]

Common Mistakes:

• Assuming speed stays at zero without control
• Expecting large overshoot without reason
• Thinking speed oscillates wildly if tuned well

4. You built a PID speed control model in Simulink but the motor speed never reaches the setpoint and stays low. What is the most likely error?

medium

A. The Scope block is not connected

B. The motor block is missing from the model

C. PID gains are too low, causing weak control action

D. The setpoint value is set to zero

Solution

1. Step 1: Analyze symptoms of low speed

   If speed stays low and does not reach setpoint, weak control action is likely due to low PID gains.

2. Step 2: Check other options for feasibility

   Missing motor block would cause no output; zero setpoint means target is zero; Scope block only displays signals and does not affect control.

3. Final Answer:

   PID gains are too low, causing weak control action -> Option C

4. Quick Check:

   Low PID gains = weak control, speed stays low [OK]

Hint: Low PID gains cause weak control and low speed [OK]

Common Mistakes:

• Ignoring PID gain tuning importance
• Confusing Scope block role with control
• Assuming setpoint zero when it is not

5. You want to improve the speed control of a motor in Simulink using a PID controller. The motor speed shows oscillations around the setpoint. Which combination of PID tuning changes will most likely reduce oscillations?

hard

A. Increase the integral gain and decrease the derivative gain

B. Decrease the proportional gain and increase the derivative gain

C. Increase the proportional gain and integral gain equally

D. Remove the derivative gain completely

Solution

1. Step 1: Understand oscillations cause

   Oscillations often happen when proportional gain is too high, causing overreaction to error.

2. Step 2: Effect of derivative gain

   Increasing derivative gain helps dampen oscillations by reacting to speed change rate.

3. Step 3: Choose tuning changes to reduce oscillations

   Decreasing proportional gain reduces aggressive response; increasing derivative gain adds damping, together reducing oscillations.

4. Final Answer:

   Decrease the proportional gain and increase the derivative gain -> Option B

5. Quick Check:

   Lower P and higher D reduce oscillations [OK]

Hint: Lower P gain and raise D gain to reduce oscillations [OK]

Common Mistakes:

• Increasing integral gain which can worsen oscillations
• Removing derivative gain which dampens oscillations
• Increasing proportional gain causing more oscillations