Visual walkthrough — Control system fundamentals — plant, actuator, sensor, controller
We assume you know only this: a signal is a number that changes with time (how far off you are, how hard you push). Everything else we build.
Step 0 — What is a "block", and why do things multiply?
WHAT. Draw a box. A wire carries a signal in; the box does something to it; a wire carries the signal out. The box is labelled with a letter like . The rule of the box is: output = (the box's factor) (input).
WHY this matters. In the real world signals are wiggly functions of time , and combining them is messy (it needs convolution — a smearing operation). Engineers use a trick called the Laplace transform: it re-labels every signal by a new variable , and in that new language cascaded boxes just multiply. So a chain of three boxes becomes one multiplication. That is the only reason we work in — it turns "smear" into "times".
PICTURE. Two boxes in a row: the signal is multiplied once, then again.

Step 1 — Lay out the four blocks as one wire-loop
WHAT. We place the four organs from the parent note in the order a signal actually travels: controller → actuator → plant (these three push the vehicle), and sensor (this one watches and reports back).
WHY. Control is decide → push → watch → report → decide again. Drawing it as a loop (not a line) is the whole point: the output curls back to meet the input. Everything downstream lives in this ring.
PICTURE. Follow the arrow all the way around once. The four named signals ride on the wires:
- — the reference: where Guidance wants us.
- — the error: reference minus what the sensor reported.
- — the control signal: the controller's decision.
- — the true output: where the vehicle really is.
- — the measured output: what the sensor says is.

Step 2 — Write the error (the subtraction that starts everything)
WHAT. At the very front sits a comparator: a circle that subtracts the fed-back measurement from the reference.
WHY. A controller should only work when we are off target. If measurement equals reference, and the controller relaxes. So the error is literally "gap between wish and reality." Note passes through the sensor box before it is subtracted — the loop compares against the reported value, not the raw truth.
Term by term: is the target signal; is the true output; reshapes into the report ; the minus sign is what makes it negative feedback — the correction always opposes the gap.
PICTURE. The comparator circle with a on the reference wire and a on the feedback wire.

Step 3 — Push the error through the forward path
WHAT. The error is the input to the big forward box . Its output is the true position:
WHY. By Step 0, sending a signal through cascaded blocks is one multiplication. The error decides how hard to correct; turns that decision into an actual movement .
PICTURE. The straight run: enters the box, leaves it — the "action" half of the loop, drawn apart from the feedback for clarity.

Step 4 — Substitute to kill the internal signal
WHAT. We have two equations sharing . Put Step 2 inside Step 3:
WHY. is an internal wire — we can't measure it from outside and we don't care about it. We want a clean statement linking only what we ask () to what we get (). Substitution erases the middle-man.
Term by term: = the "if there were no feedback" response (pure forward push on the reference). = the correction the loop feeds back — the output travels once around the ring (through , through ) and comes back to fight itself. That extra term is feedback made visible.
PICTURE. The output traced backward through and forward through again — the same signal appearing on both sides of the equation.

Step 5 — Collect and solve
WHAT. Gather every on one side:
WHY. This is just algebra now — factor out , divide across. The reward is a single box that swallows the whole loop: ask it , it hands you .
Term by term:
- Numerator = the forward push (controller·actuator·plant). Big → strong action.
- Denominator = one, plus the loop gain. The "" is you asking; the "" is the loop pushing back.
PICTURE. The whole ring collapses into one equivalent box labelled .

Step 6 — WHY exactly ""? (the chasing picture)
WHAT. Follow a signal around the ring step by step instead of solving at once. Send in . The loop subtracts of the last output, then that gets subtracted again, and again:
WHY. This is a geometric series — each trip around the loop multiplies the leftover by (the minus from negative feedback, the from one full lap). Each correction overshoots a little less than the last, and the infinite sum settles at . The formula is the loop converging on balance.
PICTURE. A staircase of shrinking corrections, each times the one before, piling up to the final value.

Step 7 — The edge cases (never leave a scenario unshown)
Every combination of "how big is the loop gain" tells a different story. Read all four.
Case A — (perfect unity sensor). The report is the truth, so This is the parent note's "unity feedback." Nothing special — just set to .
Case B — huge loop gain, . The "" is dwarfed: The output no longer depends on the messy plant at all — only on the sensor ! WHY it matters: strong feedback makes the loop immune to plant errors. This is the deep reason feedback is used.
Case C — tiny loop gain, . Now , so — the loop behaves as if open, no self-correction. Feedback that is too weak does nothing.
Case D — degenerate/dangerous: . The denominator hits zero and blows up. WHY this is the whole ballgame: the -values solving are the closed-loop poles. If any sits in the right half of the -plane, the loop is unstable — the staircase in Step 6 grows instead of shrinking (because now , the geometric series diverges). This single equation is why we can't just "crank up the gain": push too far and a root crosses over.
PICTURE. The four regimes side by side on a single map of loop gain, from "does nothing" to "blows up."

The one-picture summary

Everything above, on one canvas: the ring with its four blocks and five signals, the subtraction that makes the error, the forward push , the feedback path , and the collapse into with the shrinking-staircase reason for the denominator.
Recall Feynman retelling — the whole walkthrough in plain words
Picture a wire bent into a ring. At the top sits a subtracting circle: it takes where you want to be () and subtracts what your eyes reported (), giving the gap (). That gap flows into one big pusher-box — that's your brain, your muscles, and the vehicle all rolled into one — and out comes where you really are (). But doesn't just leave; it loops back around through your eyes (the sensor box ) and returns to the subtracting circle, so the loop is always comparing against itself. When we do the algebra to link only "asked" and "got," the loop's own pushback shows up as sitting next to a on the bottom of the fraction. The is you asking once; the is the loop answering, over and over, each answer a little smaller — a staircase of shrinking corrections that settles down to . And the one place it doesn't settle — where hits zero — is exactly where the loop goes unstable. That is the entire story of feedback in one bent wire.
Recall Quick self-test
Why do cascaded blocks multiply instead of add? ::: In the Laplace () domain, sending a signal through blocks in series is one multiplication — that is the whole reason we switch to . What does the minus sign in create? ::: Negative feedback — the correction always opposes the error, so the staircase of corrections shrinks. In one line, why is the denominator ? ::: It is the geometric series of the loop feeding back on itself: . With very large loop gain, what, and why is that good? ::: — the output stops depending on the plant, so the loop is immune to plant errors. What equation gives the closed-loop poles? ::: — its roots decide stability.
See also: State-Space Representation and Kalman Filter and Navigation for how "where am I" (, ) is estimated when sensors are noisy.