3.5.52 · HinglishGuidance, Navigation & Control (GNC)

Optimal guidance — ZEM - ZEV formulation

1,887 words9 min readRead in English

3.5.52 · Physics › Guidance, Navigation & Control (GNC)


HUM KYA solve kar rahe hain?

Hum ek thrust/acceleration command chahte hain jo vehicle ko is tarah fly kare ki final time par:

  • position target hit kare:
  • (optionally) velocity match kare: (soft landing / rendezvous ke liye zaroori)

aur minimum control effort kharch ho:

Dynamics (double integrator + gravity) coast ke dauran:

Toh concretely:


KAISE: First principles se Derivation

Hum double-integrator model use karte hain (control acceleration hai):

Step 1 — Control included ke saath true final states likho

True dynamics ko abhi () se tak integrate karo. Kyun? Hume actual endpoint chahiye unknown ke function ke roop mein.

Position ke liye double integral chahiye; integrating by parts karke,

weight kyun? Kyunki acceleration jo pehle apply hoti hai uske paas position move karne ke liye zyada time hota hai — woh do integrations se accumulate hoti hai, lever-arm chhodke.

Step 2 — ZEM/ZEV use karke boundary conditions impose karo

, set karo. Coast parts subtract karo (= ZEM/ZEV definitions):

Yeh beautiful kyun hai: do constraints ab purely coast errors ke terms mein express ho gayi hain. Control ko bas ZEM aur ZEV "bharna" hai.

Step 3 — Un do integral constraints ke subject mein effort minimize karo

minimize karo do vector constraints ke saath. Constant Lagrange multipliers introduce karo: Pointwise stationarity optimal linear-in-time profile deta hai: Linear kyun? Quadratic cost ke liye calculus of variations in constraints ke saath control ko remaining time ka affine function banne par majboor karta hai — optimal profile kabhi "wild" nahi hota.

Step 4 — Current instant par do moment equations solve karo

ko do constraints mein plug karo. Maano , toh , :

Is system ko ke liye solve karo, phir command jo ABHI apply hoti hai woh hai . Algebra karne par:

aur kyun? solve karne par: etc.; combine karne par coefficients aur milte hain. Signs alag hain kyunki ZEM (position error) aur ZEV (velocity error) ko opposite-tendency accelerations se correct karna padta hai end ke paas.


Figure — Optimal guidance — ZEM - ZEV formulation

YEH coefficients blow up kyun karte hain ( ki kahani)

Jab , tab . Physically iska matlab: agar almost koi time nahi bacha aur abhi bhi miss hai, toh usse fix karne ke liye enormous acceleration chahiye — real thrusters saturate ho jaate hain, isliye ek achha guidance system ZEM→0 pehle drive karta hai taaki command bounded rahe. Yahi wajah hai ki ZEM/ZEV ko continuous feedback ke roop mein chalaya jaata hai: har cycle mein ZEM/ZEV recompute hota hai, toh tiny residuals tab khatam hote hain jab abhi bhi bada hai.


Worked Examples


Common Mistakes (Steel-manned)


Active Recall

Recall Khud test karo (hidden)
  • ZEM aur ZEV ko words mein define karo.
  • Optimal acceleration profile time mein linear kyun hai?
  • aur kahan se aate hain?
  • Interception (PN) special case kya hai?
  • par command ka kya hota hai, aur hum ise feedback ke roop mein kyun chalate hain?
ZEM (Zero-Effort-Miss) kya hai?
Final time par position error agar control zero kar diya jaaye aur vehicle sirf gravity ke neeche coast kare: .
ZEV (Zero-Effort-Velocity) kya hai?
Final-time velocity error agar aap zero control ke saath coast karein: .
Full ZEM/ZEV optimal guidance law (position+velocity)?
.
Position-only (interception) guidance law?
, Proportional Navigation ke equivalent hai jisme .
Optimal command profile mein linear kyun hai?
minimize karna do integral (moment) constraints ke saath calculus of variations se force karta hai, jo remaining time ka affine function hai.
Position term weight kyun carry karta hai?
Kyunki acceleration double-integrate hoti hai position affect karne ke liye, remaining time ke barabar lever-arm deta hai.
par coefficients blow up kyun karte hain?
: koi time nahi bacha aur residual miss hai toh infinite accel chahiye; feedback ke roop mein chalao taaki ZEM/ZEV tab khatam ho jab bada ho.
ZEM/ZEV konsa cost functional minimize karta hai?
Control effort (fuel/energy proxy).

Recall Feynman: 12-saal ke bacche ko samjhao

Socho tum chalte chalte ek paper ball bin mein phenk rahe ho. Har moment tum poochte ho: "Agar main abhi chhod doon, toh yeh kahan giregi aur kitni tez se hit karegi?" Agar woh bahut zyada left land karti, toh tum apna throw thoda right nudge karo. Agar woh ek gentle drop ke liye bahut tez land karti, toh tum thoda ease off karo. ZEM hai "tum kitna off land karte," ZEV hai "tumhari landing speed kitni galat hoti." Math bas kehta hai: jab kam time bacha ho toh zyada nudge karo, aur kahan land karo yeh fix karna kitne gently land karo ke saath balance karo.

Connections

  • Proportional Navigation special case.
  • Calculus of Variations & Pontryagin's Minimum Principle — linear costate profile ka source.
  • Double Integrator Dynamics — plant model jo use hua.
  • Time-to-go estimation compute karna practically mushkil part hai.
  • Powered Descent Guidance (Apollo E-Guidance) — historical ZEM/ZEV lander.
  • Lambert's Problem — orbital mechanics mein related boundary-value targeting.
  • Optimal Control — LQR — same quadratic-effort minimization philosophy.

Concept Map

goal

integrate coast

integrate coast

scales

scales

coast miss

coast miss

adds lever-arm weight

early accel moves more

expressed via

solved

correction term

correction term

Min-effort optimal control

Final position and velocity constraints

Double integrator plus gravity

ZEM position error

ZEV velocity error

Time-to-go t_go

Weight t_f minus tau

Constraint integrals equal ZEM and ZEV

Weighted feedback steering command

Deep Dive