Lecture 3 PPT
Controller Design — Full Educational Summary
Page 1 — Introduction
Controller design This lecture block consists of 6 lectures/exercises.
This means you are starting a new course module focused on automatic control systems.
The core idea:
How do we make a system automatically behave the way we want?
Examples:
- keep temperature constant
- keep pH constant
- keep liquid level stable
- control pump speed
This is one of the most important engineering concepts.
Page 2 — Course outline
The lecture gives the roadmap:
1) Structuring a control problem
Before solving, we must define:
- What should be controlled?
- What can we manipulate?
- What disturbs the system?
This is system thinking.
2) Description / modelling
This is the mathematical part.
We convert the real physical system into equations:
- differential equations
- transfer functions
- block diagrams
3) Controller design
Once we know system behavior, we can design a controller.
Examples:
- on-off controller
- proportional controller
- PID controller
4) Lab exercise
Practical implementation.
Very important for exam projects.
Page 3 — Outline for today
Today’s topics:
- Introduction to control
- Feedforward control
- Feedback control
- Block diagrams
- On-off control
This is basically the control theory foundation lecture.
Page 4 — Control and supervision system
This slide shows a real industrial control system.
The system contains:
Inputs (measured variables)
Sensors measure things like:
- temperature
- level
- oxygen concentration
- pH
These are called process variables (PV).
Outputs / actuation
The system can change:
- power
- valve position
- mixing speed
- pump velocity
These are manipulated variables (MV).
Signal chain
The flow is:
sensor → computer/controller → amplifier → actuator
This is extremely important.
The controller never directly changes the process.
It changes actuators.
Example:
controller changes valve opening
which changes
hot water flow
which changes
room temperature
Page 5 — Main purposes of a controller
This slide is extremely important.
1) Stationary conditions
This means steady state behavior.
Question:
When the system settles, is it close to the desired value?
Example: Wanted temperature = 25°C Actual = 24.9°C
Very good steady state.
2) Dynamic conditions
This means:
How fast does the system recover after change?
Example: Someone opens window → room cools
How quickly does it return?
Fast recovery = good controller
3) Disturbance and noise reduction
Real systems are constantly disturbed.
Examples:
- room window opens
- external temperature changes
- noisy sensors
Good controller minimizes their effect.
4) Stability
This is one of the most important ideas.
A bad controller can cause oscillation.
Example: temperature: 24 → 27 → 23 → 28 → 22
This is unstable / oscillatory.
A good controller converges smoothly.
Page 6 — Why use control?
Two main reasons.
Follow a reference
Reference = desired target value.
Examples:
- temperature profile
- fixed pH
- nutrient addition
The controller makes output follow this target.
Reject disturbances
Very important.
Example: Outside temperature suddenly drops
The controller compensates.
This is classic disturbance rejection.
Page 7 — Controlled vs uncontrolled
This is a conceptual slide.
Three cases:
A) Poor control
Large variation.
Because of large fluctuation, you must stay far from system limits.
Example: If maximum safe temp = 50°C you operate at 40°C
for safety.
B) Better control
Less variation.
Safer and more accurate.
C) Excellent control
Very small variation.
Now you can move reference closer to optimal limit.
This improves:
- efficiency
- productivity
- safety margins
Very important in industry.
Page 8–10 — Indoor temperature example
This is a fantastic beginner example.



Feedforward control
This means:
act before measuring output
Example: You know night is coming → room will cool
So you increase heater before temperature drops
This is predictive control.
Feedback control
This means:
measure output and correct error
Example: Room too cold → open valve more
Room too hot → close valve
This is the most common control strategy.
Important difference
This is highly exam-relevant.
Feedforward
Uses prediction / knowledge.
No direct error correction.
Fast, but sensitive to modelling errors.
Feedback
Uses measured output.
Corrects actual error.
More robust.
Pages 11–17 — Block diagrams
This is one of the most important sections.
Why block diagrams?
They simplify complicated systems.
Instead of drawing real hardware, we draw functional blocks.
Example:
Reference → Controller → Plant → Output
Standard feedback loop (VERY IMPORTANT)
Page 17 is fundamental.



The standard setup is:
Reference → Error → Controller → Plant → Output
with sensor feedback loop.
Definitions
Reference
Desired value
Example: 25°C
Error
Difference:
e = reference - output
This is central.
e = r - y
If output too low → positive error
Controller
Computes action from error.
Example: increase heater power
Plant / System
The physical thing.
Example: room + heater
Sensor
Measures output.
Example: thermometer
Disturbance
External unwanted input.
Example: open window
Pages 18–21 — Heat exchanger
Very important industrial example.



This is the real-world application of the theory.
The goal:
control outlet temperature
Manipulated variable:
valve opening / hot water flow
Measured variable:
output temperature
Classic process engineering example.
Very exam-relevant.
Pages 23–26 — On-off control
This is extremely important.
What is on-off control?
The controller only has two states:
- ON
- OFF
No intermediate values.
Exactly like home thermostats.
Example
If temperature < setpoint → heater ON
If temperature > setpoint → heater OFF
Important consequence
Output oscillates around setpoint.
This is normal.
It does NOT settle perfectly.
This is explicitly mentioned.
pH example
Very good example.
Target: pH = 4.8 \pm 0.05
If pH too high → add acid
If pH low enough → stop
This is discrete switching control.
Timer logic
Very important practical design.
The acid is not continuously added.
Instead:
- dose for some time
- wait
- measure again
This avoids overshoot.
Very realistic industrial logic.
Pages 27–31 — Dynamic modelling
This is where math starts.
Very important.
Liquid heating model
This is classic first-order system.
The equation:
cM\frac{dT_L}{dt}=P_-hA(T_L-T_s)
cM\frac{dT_L}{dt}=P_-hA(T_L-T_s)
This is simply:
accumulation = input heat − heat loss
Physical meaning
Left side
Temperature change over time
Thermal storage
First term
Heat supplied by heater
Second term
Heat loss to surroundings
Bigger temperature difference → bigger loss
Very intuitive.
Time constant
This is one of the most important concepts.
\tau = \frac{cM}{hA}
\tau = \frac{cM}{hA}
This tells how fast system responds.
Large τ
Slow system
Example: large tank
Small τ
Fast system
Example: small cup of water
The famous 63% rule
At
t=\tau
the system reaches 63% of final value
y(\tau)=0.63K
This is extremely important in control engineering.
You should absolutely remember this.
Pages 32–35 — Transfer functions
This is a major concept.
Instead of differential equations, we transform them into Laplace domain.
This makes calculations algebraic.
Why useful?
Differential equations are difficult.
Laplace transform converts:
\frac{dy}{dt}
into
sY(s)
Much easier.
Transfer function
General form:
G(s)=\frac{Y(s)}{U(s)}
G(s)=\frac{Y(s)}{U(s)}
This describes system response.
Extremely important for controller design.
Pages 36–40 — Block diagram algebra
These pages are very important for problem solving.
Series / cascade
Two blocks in sequence:
A then B
Equivalent:
AB
G_=AB
Parallel
Two paths added:
C + D
G_=C+D
Block transformations
These slides teach how to simplify complex diagrams.
Very likely exam topic.
Page 41 — Detailed real implementation
Excellent practical slide.
This shows real digital control.



Flow:
- sensor
- ADC
- controller algorithm
- DAC / PWM
- amplifier
- actuator
- system
This is how embedded systems work.
Very relevant for engineering.
Page 42 — Mini project
This slide is extremely exam relevant.
Project requires:
- control concept
- dynamic model
- theoretical controller
- implementation + test
This is basically the entire course workflow.
Big-picture understanding
This whole lecture builds the foundation:
real process → model → block diagram → controller
That is the control engineering workflow.
One-sentence takeaway
A controller continuously compares the actual output with the desired reference and changes the system input to minimize error while remaining stable.