3.5.26 · D3Guidance, Navigation & Control (GNC)

Worked examples — Control system fundamentals — plant, actuator, sensor, controller

2,028 words9 min readBack to topic

Prerequisites we lean on (all built in the parent topic): Transfer Functions and Laplace Domain, Poles Zeros and Stability, Second-order System Response, PID Control, and Actuator Saturation and Anti-Windup.


The scenario matrix

Before working anything, let us list every distinct case class a closed-loop problem can hand you. Each row is a "shape" of problem; each worked example below is tagged with the cell it fills.

# Case class What makes it different Example
A First-order plant, +ve gain one pole, always stable, finite Ex 1
B Second-order plant, sweep the gain damping changes sign of "overshoot" behaviour across a range of Ex 2
C Negative / sign-flipped gain wrong-sign feedback → runaway; a whole quadrant of that fails Ex 3
D Integrator in the plant (pole at ) degenerate DC gain → zero step error Ex 4
E Non-unity sensor sensor scaling changes both stability and where you settle Ex 5
F Limiting case and boundary behaviour of the loop Ex 6
G Real-world word problem drone altitude hold, translate words → blocks Ex 7
H Exam twist: add an integrator, find stability boundary Routh-style "for which is it stable?" Ex 8

Every numeric answer below is machine-checked in the verify block.


Forecast: Guess first — with one plant pole and positive gain, do you expect this to blow up or settle? Will the error to a step be zero or some leftover?

  1. Forward path . Why this step? Cascaded Laplace blocks multiply, so the whole forward chain is one product.

  2. Apply the boxed formula. Why? , so .

  3. Read the pole. Why? The denominator root is the closed-loop pole; its sign decides stability.

  4. Steady-state error to a step. Why? , valid because the loop is stable (final value theorem applies).

Verify: Pole moved from (open loop) to (closed loop) — feedback sped it up, which matches "more gain, faster." Error is small but nonzero because there is no integrator. ✓


Forecast: One value gives lazy no-overshoot motion, the other snappy-but-ringing. Guess which rings more before reading on.

  1. Closed loop. Why? Same procedure as the parent's Ex 1.

  2. Match to the standard second-order form. Why? Comparing to (see Second-order System Response) lets us read damping straight off.

  3. Plug . Why? Test the low-gain corner.

  4. Plug . Why? Test the high-gain corner.

Look at the figure: as grows the two poles slide off the real axis and up into the complex plane — that vertical climb is the ringing.

Figure — Control system fundamentals — plant, actuator, sensor, controller
  1. Overshoot for . Why? The percent overshoot depends only on : .

Verify: sits exactly on the boundary between overshoot and none — consistent with being critically damped. Raising from 1 to 16 quadrupled and quartered . ✓


Forecast: A minus sign in feedback usually means "you push away from the target instead of toward it." Guess whether the pole ends up left or right of zero.

  1. Forward path. Why? Same product, now with negative .

  2. Closed loop. Why? Apply the formula and watch the sign land in the denominator.

  3. Pole. Why? Root of .

Verify: The open-loop pole was at ; positive feedback pushed it right across the imaginary axis. Physically: an error makes the controller push in the wrong direction, growing the error — exponential blow-up . This is why sign convention on the sensor/actuator is life-or-death. ✓ (Contrast Ex 1, same plant, correct sign → pole at .)


Forecast: There is a lonely in the denominator (a pole at ). Guess whether the step error is finite or exactly zero.

  1. Forward path. Why? Multiply.

  2. DC gain. Why? Step error needs .

  3. Steady-state error. Why? .

Verify: A pole at (a "free integrator") means the loop keeps accumulating error until it is exactly wiped out. This is exactly why the "I" in PID Control kills steady-state error — it inserts that deliberately. Contrast Ex 1 (no integrator → ). ✓


Forecast: If the sensor under-reports by half, will the controller stop too early or overshoot the true target? Guess the direction of the mistake.

  1. Closed loop with . Why? Now use the full .

  2. Final value of . Why? for a unit step.

  3. Interpret. Why? The loop drives the measured signal toward the reference, not itself.

Verify: Because the sensor halves the reading, the controller must double the true output to make the measurement match — so the true ends above the target. A "1.0" command produced a physical 1.43. This is the mistake the parent warns about: an "accurate-looking" but mis-scaled silently biases the loop. ✓


Forecast: One limit turns the loop "off," the other cranks it as hard as physics allows. Guess what the poles do at each extreme.

  1. . Why? Turn the controller down to nothing. The poles return to the open-loop locations — with a pole at , the output no longer tracks (loop effectively opened).

  2. . Why? Push gain to the ceiling. Undamped oscillation: poles rocket up the imaginary direction, . Response rings forever (marginally toward instability).

  3. Middle ground. Why? Best trade at .

Verify: As runs from , runs monotonically — every intermediate damping is hit exactly once, and gives the textbook "nicest" damping. Consistent with Ex 2 (: ; : ). ✓


Forecast: There's an integrator in the plant again. Guess whether hover height locks exactly onto 10 m or drifts.

  1. Translate words → blocks. Why? Reference (a step of height 10), .

  2. DC gain & step error. Why? Integrator ⇒ ⇒ zero error (Case D logic).

  3. Damping for . Why? Close the loop and match second-order form.

Verify: → underdamped: the drone rises past 10 m, dips, then settles at exactly 10 m (zero steady error thanks to the integrator). Units: in rad/s, dimensionless. ✓


Forecast: Adding the integrator gives zero steady error — but integrators are destabilizing. Guess whether there's an upper limit on .

  1. Characteristic equation. Why? Stability lives in the roots of .

  2. Routh array for . Why? Routh–Hurwitz tells us sign changes = right-half poles without solving the cubic.

col 1 col 2
  1. All first-column entries must be . Why? Any sign change ⇒ a right-half-plane pole ⇒ instability.

  2. Boundary check . Why? At the edge the row vanishes → poles sit on the imaginary axis (sustained oscillation). Purely imaginary pair ⇒ marginal, oscillating at rad/s.

Verify: At we get exactly (marginal) and one stable real pole at ; for just below 6 those complex poles move left (stable), just above 6 they cross right (unstable). So is the full stable window. ✓


Recall Which cell was which? (quick self-quiz)

Cell A (first-order, +gain) which example? ::: Ex 1. Cell C (wrong-sign gain → RHP pole) which example? ::: Ex 3. Which two examples give exactly zero step error, and why? ::: Ex 4 and Ex 7 — both have a plant pole at (an integrator). In Ex 8, the stability window is? ::: . At the Ex 8 boundary , oscillation frequency? ::: rad/s.


Active recall

What is the closed-loop pole for Ex 1 (, , unity fb)?
; step error .
Why did Ex 3's identical plant become unstable?
The gain sign flipped (positive feedback), pushing the pole to in the right half-plane.
How does an integrator in the plant (Ex 4, Ex 7) affect step error?
, so .
In Ex 5 with , where does the true output settle for a unit step?
— the loop drives the measured half-value to 1, so true overshoots.
What is the stable gain range in the Ex 8 integrator problem?
, from the Routh condition and .