3.5.28 · D5Guidance, Navigation & Control (GNC)

Question bank — Block diagram algebra

1,756 words8 min readBack to topic

Before we start, one vocabulary anchor so nothing below uses an undefined word:

  • — the reference input: the signal we feed into the loop (the "command", e.g. "go to this altitude"). It is the arrow entering the very first summer.
  • — the error signal: the summer's output, , i.e. how far the command is from what's fed back. Think "the gap the controller must close."
  • — the fed-back signal: what the feedback block returns to the summer, .
  • — the output: the signal leaving the forward block, . It's what we actually measure or move.
  • , are blocks: boxes that multiply whatever signal enters them by a function of . Think "a slide that scales your speed."
  • A summer is a circle that adds or subtracts the arrows entering it.
  • A take-off point is a dot that copies one signal to several wires (copying changes nothing).
  • Loop gain : the total factor a signal picks up going once around the loop and back.

The picture below fixes those four symbols to real wires — refer back to it whenever a derivation names , , , or .

Figure — Block diagram algebra

To see why the numerator never changes when feedback turns positive, look at the two summers side by side.

Figure — Block diagram algebra

True or false — justify

Series blocks then give the same output if you swap their order to then
True — for scalar transfer functions multiplication commutes, , so the cascade output is identical. (This fails only for matrix/MIMO blocks, which don't commute.)
Parallel blocks combine to regardless of the summer's signs
False — the sign is inherited from the summer. If the lower branch enters with a minus, you get ; the plus is not automatic.
For negative feedback the closed-loop transfer function is
True — from and you get . The in is the fingerprint of the negative summer.
Positive feedback just flips the numerator sign, giving
False — it flips the denominator sign: . The summer now adds the fed-back signal, so , changing the denominator, not the numerator (see the s02 derivation above).
If (unity feedback) the loop gain equals the forward gain
True — loop gain is , so the round-trip factor is exactly the forward block. Closed-loop TF becomes .
You can move a summing junction downstream past a block with no correction, since summers only add
False — everything the summer added now gets multiplied by . To keep the arithmetic, each moved branch must be pre-multiplied by : (see figure s03).
The "" in has no physical meaning; it's just algebra
False — it is the direct passthrough: the output reaching the input once without any feedback trip. The is the trip; the is "you, going straight through, one time."
Making larger always makes the closed-loop gain larger
False — larger increases , which sits in the denominator , so more feedback shrinks the closed-loop gain. That shrinking is the whole point of feedback (tame a huge ).
A take-off point can be slid across a block freely because copying a signal changes nothing
False — copying doesn't change the signal, but where you copy does. Past the block the tap reads instead of , so you must insert to recover the original value (see figure s04).

Spot the error

"Inner and outer loops? I'll reduce the outer loop first since it's the main control loop." — find the flaw
The outer feedback formula needs its forward path to be a single block, but that path still hides the un-reduced inner loop. You must work inside-out: collapse the inner loop to one block first (figure s05).
"Cascade forward path with feedback : closed-loop ." — spot it
The loop gain is the full round trip , not . Correct denominator is ; both forward blocks are inside the loop.
"Unity feedback means , so the closed-loop TF is just ." — spot it
You cannot substitute ; is a function of , not the number 1. Unity feedback sets giving , which is not unless happened to equal 1.
"Moving a take-off downstream past , I multiply the branch by to match." — spot it
Backwards. Downstream the tap already reads (too big), so you divide by , i.e. insert . Multiplying by is the rule for moving a summer past , not a take-off.
"Parallel branches both start from the same wire, so I don't need a take-off point." — spot it
You do — a single wire cannot legally fan out into two blocks without a take-off dot marking the copy. It's the primitive that licenses one signal feeding two places.
"Loop gain can't affect stability; only the numerator poles matter." — spot it
Stability is set by the denominator (the characteristic equation), which is built entirely from the loop gain. The numerator does not set the poles.

Why questions

Why do blocks multiply their inputs rather than add them?
Because an LTI system acts by convolution in time, and the Laplace transform turns convolution into multiplication in . So "pass through a block" literally is "multiply by ."
Why must nested loops be reduced from the inside out?
Every feedback reduction requires its forward path to already be a single transfer function. An outer loop wrapping an un-reduced inner loop violates that, so you collapse innermost first.
Why does feedback "divide by one-plus-loop-gain" instead of subtracting the loop gain?
Because the fed-back signal is proportional to itself: . Moving the across gives , then factoring , so . The is a collect-and-factor of the terms — never a subtraction of gains.
Why is the same formula the heart of Op-amp gain?
An op-amp has enormous, poorly-controlled open-loop gain ; wrapping feedback divides it down to a stable, resistor-set closed-loop gain when . Same block algebra, different hardware.
Why can we treat a whole feedback loop as one equivalent block once reduced?
Because block algebra never changes the equation the diagram encodes — it only rewrites the picture. The reduced single block has an identical input-output relation .
Why do we sometimes prefer Mason's gain formula over these moves?
Because equivalence moves get error-prone in tangled multi-loop diagrams; Mason's formula reads the answer straight off the graph's paths and loops without sliding anything.

Edge cases

What is the closed-loop TF if the loop gain (huge open-loop gain)?
— the output becomes governed by the feedback path alone, independent of . This is exactly why op-amps with big give clean, -controlled gain.
What happens to (positive feedback) when ?
The denominator , so the closed-loop gain blows up — the system is on the edge of instability/oscillation. This is the resonance/runaway boundary of positive feedback.
What is the equivalent block of a parallel pair when into an adding summer?
— the branches cancel and the equivalent block is zero; no signal reaches the output. A degenerate but perfectly legal result.
If a feedback block is , what does the loop reduce to?
— no feedback at all, so you recover the open-loop forward block, as expected when the return path is cut.
What is the series-equivalent block if one block in the chain is (a pure wire)?
It contributes a factor of 1: . A unity block is an identity element — it passes the signal through unchanged.
Can you move a summing junction past a take-off point with no correction?
No — you must preserve every signal value at both. Such rearrangements need compensating blocks or duplicated summers; always re-derive by insisting each wire keeps its exact value, then test with a dummy input.

Connections

  • Transfer functions — the , objects that live inside each block; every trap above is really a statement about how these multiply and combine.
  • Laplace transform — the reason "pass through a block" means "multiply", since it turns time-domain convolution into -domain multiplication (answers the first Why question).
  • Feedback control loops — the engineering context for Rule 3; the /// derivation on this page is exactly the loop those systems close.
  • Signal flow graphs & Mason's gain formula — the move-free alternative that sidesteps the take-off/summer sliding traps in the Spot-the-error section.
  • Op-amp gain — the hardware where the edge case actually gets used to build stable amplifiers.
  • Stability & characteristic equation — explains why the denominator (not the numerator) sets the poles, justifying the last Spot-the-error item.