3.5.45 · D3Guidance, Navigation & Control (GNC)

Worked examples — TVC dynamics — gimbal servo bandwidth, time delay

1,958 words9 min readBack to topic

This page is a drill sheet. The parent note built the machinery: the second-order servo lag, the bandwidth formula, and the phase-eating delay. Here we throw every kind of case at that machinery — normal numbers, edge cases, zeros, limits, a word problem, and an exam trap — and grind each one out fully.

Before we start, one reminder of the three tools we keep reaching for, so no symbol appears unearned:

Recall The three formulas we reuse (from the parent)
  • Natural frequency & damping: , . is how fast the nozzle can swing; is how much it rings (0 = pure ringing, 1 = no overshoot).
  • Bandwidth: . The fastest wiggle the servo still follows within of full size.
  • Phase eaten by a pure delay at frequency : radians degrees. ( is just the radians→degrees converter.)

The scenario matrix

Every problem this topic can ask lives in one of these cells. The examples below are tagged with the cell they cover.

Cell What makes it special Covered by
A · Nominal under-damped , ordinary numbers, Ex 1
B · Sweet-spot damping so exactly Ex 2
C · Over-damped / critical , sluggish, Ex 3
D · Degenerate: zero delay — delay eats nothing Ex 4 (part)
E · Limiting: zero damping — resonance, bandwidth blows up Ex 4
F · Delay phase-budget given : how much margin lost Ex 5
G · Word problem (real vehicle) translate hardware into numbers, decide safe/unsafe Ex 6
H · Exam twist: "add gain to fix delay" trap — raising gain makes delay worse Ex 7
I · Padé wrong-way sign first-order Padé RHP-zero, output goes wrong way first Ex 8

Example 1 — Cell A: nominal under-damped servo

  1. . Why this step? is fixed purely by the stiffness-to-inertia ratio — the "spring vs. mass" contest sets the swing speed.
  2. . Why? compares actual damping to the critical amount . Here it's exactly half, so it rings.
  3. . Then Why? Under-damped systems resonate a little before rolling off, so the dB point sits above .

Verify: Units: ✔. is dimensionless ✔. Ratio — matches the parent's "".


Example 2 — Cell B: the sweet spot

  1. (unchanged — depends only on and ). Why? Damping doesn't touch ; it only affects ringing.
  2. by construction. Why? We chose to hit this value; it's the classic control target.
  3. . So Why? When the formula collapses to — bandwidth equals natural frequency, the reason engineers design to .

Verify: Plug into ✔.


Example 3 — Cell C: over-damped, sluggish

  1. . Why? Now the term is negative — this is what pushes below .
  2. . Why? The inner keeps positive, but subtracting 1 shrinks it → bandwidth drops to .
  3. Interpretation: a critically damped servo follows commands cleanly but only up to — slower than its own . Why it matters: over-damping trades ringing for sluggishness; both extremes cost you.

Verify: Ratio — matches parent's "" ✔.


Example 4 — Cells D & E: degenerate zero-damping and zero-delay limits

  1. (a) Put : , so Why? Zero damping means the magnitude spikes at resonance, so the dB point pushes far above (widest of any ).
  2. (b) rad . Why this step? Phase lost is proportional to . A perfect (zero) delay steals nothing — the degenerate baseline.
  3. Sanity limit: as we approach , the largest possible ratio. Any real damping pulls it back down.

Verify: , times ✔. And trivially ✔.


Example 5 — Cell F: delay eats the phase margin

  1. Phase eaten . Why this step? A pure delay contributes phase (magnitude stays 1). Multiply frequency by delay.
  2. Convert to degrees: . Why? Phase margin is quoted in degrees; converts.
  3. Remaining margin . Why it matters: Below the safety floor — the vehicle will ring in gusts. Fix by reducing (faster computer) or lowering , never by adding gain (see Ex 7).

Verify: ; ; ✔. Units: rad/s · s = rad ✔.


Example 6 — Cell G: real-vehicle word problem

  1. Required . Hardware gives . Why this step? The 5× rule keeps the servo's phase lag tiny compared to the loop's needs.
  2. : fails the rule of thumb (marginally). Why? Too-slow a servo lets its lag creep into the loop's stability budget.
  3. Servo phase lag at (parent's small-angle estimate): . Why? For a lightly-loaded second-order lag well below , phase radians.
  4. . Why it matters: 18° is above the ~16° the rule targets — confirming the hardware is slightly too slow. Either speed the servo or slow the autopilot.

Verify: ; ; ✔. See also the trade-off with bending modes — you can't just crank up.


Example 7 — Cell H: the exam trap "add gain to beat delay"

  1. Original loss: (parent Ex 2). Margin left . Why? Baseline to compare against.
  2. After more gain, crossover rises to . New loss . Why this step? Delay's phase is — it grows linearly with crossover. Raising raises the toll.
  3. Now margin worse than the 27.8° we started with, and under the 30° floor. Why the fix fails: a pure delay has magnitude ; gain never fights it, it only pushes higher into more phase lag. The real cure: shrink (see computational delay) or lower bandwidth.

Verify: ; ; (worse) ✔.


Example 8 — Cell I: Padé wrong-way-first sign

  1. (a) Zero where numerator : . Why this step? A positive real means a right-half-plane (RHP) zero — the mathematical mark of non-minimum-phase, "wrong-way-first" behaviour.
  2. (b) Step response value at : for the initial value (limit of for a step ) gives . Why? At the first instant the output jumps to — the opposite direction of the commanded before curving up to . Look at the red dip in the figure.
  3. Final value: — it does eventually reach the command, just after going backward first. Why it matters: that initial backward lurch is exactly the destabilising essence of transport delay, captured by a rational function root-locus tools can chew on.
Figure — TVC dynamics — gimbal servo bandwidth, time delay

Verify: RHP zero at ✔. Initial value , final value ✔ (both computed above).