3.5.45 · D5Guidance, Navigation & Control (GNC)

Question bank — TVC dynamics — gimbal servo bandwidth, time delay

1,858 words8 min readBack to topic

Before the questions, let's pin down every symbol these traps rely on, because the whole point of a concept trap is that it hides in an undefined letter.

The figure below is the mental picture for the whole page — glance back at it whenever a trap mentions "delay," "phase," or "magnitude."

Figure — TVC dynamics — gimbal servo bandwidth, time delay
Recall What to read off the figure (alt text / caption)

Left panel ::: A yellow commanded step in nozzle angle; the blue actual response starts only after the red band (the delay ), then rings before settling — showing the "commanded vs actual" gap. Right panel ::: For a pure delay, the green magnitude curve stays pinned at 1 for all frequencies while the red phase curve slides steadily downward () — the visual proof that delay touches phase only, never amplitude.


True or false — justify

True or false: A pure delay makes the servo's output smaller at high frequency.
False. Its magnitude is at every frequency — it touches only phase, never amplitude (right panel of the figure).
True or false: For a delay, the phase lag grows without bound as frequency rises.
True. is linear in , so it keeps sliding more negative forever — unlike a second-order lag which levels off at .
True or false: Bandwidth always equals natural frequency .
False. They coincide only at . For , ; for , .
True or false: Raising loop gain is a valid cure for a delay-induced stability problem.
False. Gain lifts the crossover frequency , and phase lost is — a higher spends more phase, making it worse.
True or false: A higher servo bandwidth is unconditionally good for the vehicle.
False. If climbs into the structural bending or slosh frequencies, the servo starts exciting flexible modes and TVC turns into an oscillator — see Structural bending modes & notch filters.
True or false: The first-order Padé approximation of a delay has a right-half-plane zero.
True. It places a zero at ; that RHP zero is the mathematical fingerprint of "output first moves the wrong way," the destabilising essence of delay — see Padé approximation of transport delay.
True or false: An under-damped servo () has bandwidth below its natural frequency.
False. Under-damped systems resonate slightly before rolling off, so they still track faithfully past ; hence for .
True or false: At the servo's frequency response has a flat resonant peak (no overshoot in magnitude).
True. is the maximally-flat (Butterworth) condition where the magnitude curve rolls off with no peak, which is exactly why it's the design sweet spot.
True or false: If we double the actuator authority (with ), the DC gain moves further from unity.
False. Larger drives toward 1, which is why a strong inner loop is assumed to have unit steady gain.

Spot the error

"The delay eats radians of gain margin." — what's wrong?
It eats phase margin, not gain margin. Delay's magnitude is 1, so it can't touch gain; is a phase angle.
"Since gives , I'll just always assume they're equal." — what's wrong?
The equality holds only at that one value of . Always check the actual damping ratio first, because at the bandwidth is 27% higher than .
"A delay of 20 ms is fine because 20 ms is tiny." — what's the missing consideration?
What matters is , not alone. At rad/s that "tiny" delay costs rad of phase — a big bite from a margin.
"To make the servo faster I only need to reduce its inertia ." — what did this overlook?
, so raising stiffness works too; and speed alone is not the goal — you must keep below the first bending mode.
" can be dropped from root-locus analysis because it's just a shift." — what's wrong?
Root-locus needs a rational transfer function; the transcendental must first be replaced by a Padé approximation, which introduces real poles/zeros that do alter stability.
"We set to 0.3 for a snappy servo." — why might a designer object?
is lightly damped: it overshoots and rings, and its resonant peak can amplify commands near , feeding energy into flexible modes. The sweet spot avoids the peak.

Why questions

Why is a pure delay considered more dangerous to stability than an equivalent-looking slow lag?
Because its phase lag grows without limit, so at high frequency it can push total phase past where a bounded lag never could, silently crossing the instability threshold.
Where do the bandwidth factors like () and () come from?
From the closed form : plugging gives the factor , and gives . Intuitively, less damping lets the servo resonate past (factor ); heavy damping rolls it off early (factor ).
Why do designers target (servo bandwidth well above loop crossover)?
Near crossover the second-order servo's own phase lag is , which for a small ratio reduces to about rad. With and ratio that's roughly — small enough that the servo looks "instantaneous" to the rigid-body loop.
Why is the servo modelled as second order rather than first?
It is physically a motor torque driving a nozzle inertia against damping and stiffness — a mass–spring–damper, which is inherently second order (see Second-order systems — natural frequency & damping).
Why does adding gain to fight a delay backfire?
Gain raises the crossover frequency , and phase lost is ; a bigger multiplies the same into a larger phase loss, eroding margin further.
Why does the Padé form use rather than a simple pole ?
Both match the Taylor series of to first order, but only the Padé form reproduces the right-half-plane zero — the "goes the wrong way first" behaviour that a lone pole would completely miss.
Why must servo bandwidth sit below the first structural bending frequency?
Because a fast servo responds to frequencies inside its passband; if bending resonances fall in that band, the actuator drives them, and TVC couples to the flexible mode instead of steering — a margin-destroying feedback loop.

Edge cases

Edge case: What happens to bandwidth as (no damping)?
The formula gives , and the resonant peak grows toward infinity — the "bandwidth" number becomes misleading because the response wildly amplifies near .
Edge case: What is the phase eaten by delay at zero frequency ()?
Zero — , so a steady (DC) command sees no phase penalty at all; delay only bites the fast, oscillatory commands.
Edge case: If (no delay), does the Padé zero still exist?
No — the zero sits at , which runs off to infinity as , so the wrong-way behaviour vanishes and the delay term becomes .
Edge case: For an over-damped servo (), what happens to bandwidth relative to ?
It falls below (e.g. at ); the servo is sluggish and rolls off earlier than its natural frequency, so it can't even track up to .
Edge case: What if the digital sampling rate is the dominant delay source?
Then is roughly one sample period (plus computation), so faster sampling directly shrinks and buys back phase margin — see Digital control — sampling & computational delay.
Edge case: In the limit , what does the servo DC gain become and why does it matter?
It approaches , meaning the nozzle settles exactly at the commanded angle in steady state — the unit-gain assumption used everywhere downstream in Thrust Vector Control geometry & torque.

Recall One-line summary to lock in

Which quantity does a pure delay change, and which does it leave untouched? ::: It changes phase (by ) and leaves magnitude untouched — that's the whole reason it's a silent margin-eater.