Exercises — Autonomous GNC for reusable rockets — SpaceX approach overview
3.5.55 · D4· Physics › Guidance, Navigation & Control (GNC) › Autonomous GNC for reusable rockets — SpaceX approach overvi
Yeh page ek self-test ladder hai. Har problem apna level batata hai, clean numbers deta hai, aur ek collapsible callout ke andar poora solution chhupata hai. Pehle khud try karo, phir reveal karo. Sab kuch parent overview pe build karta hai.
Shuru karne se pehle, ek picture is page ke har sign convention ko fix kar deti hai. Ise neeche di gayi definition ke saath padho — har arrow ka naam wahan hai.

Level 1 — Recognition
Problem L1.1
GNC ke teen letters ka naam batao aur, ek-ek phrase mein, har ek ka woh sawaal jo woh answer karta hai.
Recall Solution
- Guidance — Main kahan jaana chahta hoon? (desired trajectory / target state compute karta hai).
- Navigation — Main abhi kahan hoon? (sensors se position, velocity, attitude estimate karta hai).
- Control — Gap close karne ke liye actuators ko kaise move karun? (commands ko gimbal / fin / thruster deflections mein turn karta hai).
Problem L1.2
Ek booster ka minimum engine thrust, jab almost empty ho, ek thrust-to-weight ratio (TWR) deta hai jo 1 se zyada ho. Ek single word batao jo yeh explain kare ki yeh hover kyun nahi kar sakta?
Recall Solution
TWR > 1 ka matlab hai minimum upward thrust force weight force se zyada hai (, toh ). Lowest throttle par bhi net acceleration upward hai — rocket upar accelerate karega, float nahi karega. Hovering ke liye thrust exactly weight ke barabar chahiye (TWR = 1), jo engine itna low nahi ja sakta. Isliye ise ek single timed hoverslam karna padta hai.
Level 2 — Application
Problem L2.1
Ek booster downward speed se gir raha hai. Engine ek net upward acceleration produce kar sakta hai. Konsi altitude par engine light karna chahiye taaki velocity exactly ground par zero ho jaye?
Recall Solution
kyun? Is kinematic relation mein koi time nahi — yeh speed ko directly travel ki gayi distance se link karta hai. Hum woh distance chahte hain jis par speed zero ho jaati hai, toh yahi sahi tool hai (time-based nahi). Yaad raho = stopping distance (burn kitna vertical distance cover karta hai); yahan burn poora raasta ground tak jaata hai, toh .
Final speed set karo stopping distance par: Plug in karo: Answer: m.
Agla figure exactly yahi case dikhata hai ek speed-versus-altitude curve ke roop mein. Horizontal axis altitude metres mein hai (pad par 0, right ki taraf badh raha hai); vertical axis speed m/s mein hai. Accent-red line booster ki speed hai jab woh brake karta hai.

Ise right se left padho (girna matlab altitude kam hona): upper right par black dot m, m/s par hai — yeh ignition hai. Red curve ko down-and-left follow karo aur yeh exactly origin par land karta hai, dusra black dot , par — touchdown. Kyunki curve zero altitude par zero speed reach karta hai aur kahin pehle nahi, woh single meeting point hi ek perfect hoverslam hai.
Problem L2.2
Same booster aur burn (, ). Burn kitne time tak chalta hai?
Recall Solution
Ab time-form kyun, distance-form nahi? Figure s02 ne speed ko altitude ke against plot kiya — "speed zero kahan hoti hai" ke liye great, lekin uspar koi clock nahi hai, toh tum seconds nahi padh sakte. Sawaal kitna time poochha hai, jo ek clock sawaal hai. Do kinematic tools cleanly split hote hain is basis par ki woh kya chhod dete hain: mein koi time nahi (distances ke liye use karo), jabki mein koi distance nahi (durations ke liye use karo). Kyunki hum seconds chahte hain, hum woh waala choose karte hain jo actually contain karta hai.
use karo final ke saath: Answer: s. (Sanity check: average speed m/s, 6 s par = 450 m = . ✓ — yeh distance par wapas bridge exactly wahi hai jahan do forms agree karte hain.)
Problem L2.3
Ignition par booster mass kg hai, aur hai. use karke, required thrust kya hai?
Recall Solution
kyun? se, ke liye solve karo: engine ko pehle gravity cancel karni hai () aur phir extra deceleration supply karni hai (). Answer: N (1044 kN).
Level 3 — Analysis
Problem L3.1
L2.1 ke numbers use karke (, correct m), maano computer engine early light karta hai, m par, same ke saath. Booster ki velocity kahan zero reach karti hai, aur physically aage kya hota hai?
Recall Solution
Same aur same starting speed ke saath, stopping distance (burn speed kill karne mein kitna far jaata hai) fixed hai: 600 m par light karne se, booster braking mein 450 m altitude consume karta hai aur ground se m upar rukta hai. Ab woh momentarily 150 m par rest mein hai engine still on ke saath aur TWR > 1 → net upward acceleration → woh wapas upar jaata hai. Woh hover ke liye throttle nahi kar sakta. Toh early ignition "margin add" nahi karta — yeh rocket ko mid-air mein stranded kar deta hai ya wasteful re-fall force karta hai. Answer: velocity 150 m altitude par zero; phir woh upward accelerate karta hai (hover nahi kar sakta).
Problem L3.2
Ab woh late light karta hai, m par, same , same . Impact speed kya hai?
Recall Solution
Burn ke paas ab sirf m stopping distance available hai, lekin usse 450 m chahiye tha. use karo ke saath: Answer: yeh ground par m/s se hit karta hai → crash. Yeh razor-thin corridor hai: ignition-altitude error ke m ka fark hai wapas uthne aur highway speed par slam in karne mein.
Problem L3.3
Explain karo kyun IMU akele poora descent navigate nahi kar sakta, aur ek constant accelerometer bias ke position estimate mein growth law do. Phir batao 3D position-error size ka kya hota hai agar har axis ka same bias ho.
Recall Solution
Pehle, notation: ek bold letter jaise ek vector matlab hai — ek quantity jisme teen components hain (ek , ek , ek ), yahan space mein position; isi tarah acceleration vector hai. Bold sirf kehta hai "iske teen numbers aur ek direction hai."
IMU acceleration deta hai; position twice integrate karke recover hoti hai ( — pehle time ke saath acceleration add karo velocity paane ke liye, phir time ke saath velocity add karo position paane ke liye).
Ek axis explicitly karo. Maano -accelerometer ek fixed wrong offset (metres per second², constant) read karta hai. Velocity error ke liye ek baar integrate karo: Position error ke liye woh ek aur baar integrate karo: Toh har axis par same algebra same shape deta hai — ke baare mein kuch special nahi tha, toh aur bhi produce karte hain. Isliye "argument har axis ke saath identical hai": integration ko pata nahi aur parwah nahi ki woh kis axis par run kar raha hai.
3D error size. Agar teeno axes same bias carry karte hain, toh error vector hai . Uski length (3D mein Pythagoras) hai abhi bhi ki tarah grow kar raha hai — sirf times akele ek axis se bada.
Kyun yeh matter karta hai: error time ke square ke saath badh ta hai — small bias, long flight → huge error. Toh hum ek drift-free lekin slow reference (GPS/radar) ko Kalman filter ke zariye fuse karte hain drift ko bound karne ke liye. Fast IMU + slow GPS = dono ka best.
Level 4 — Synthesis
Problem L4.1
Ek booster altitude m par hai aur m/s se descend kar raha hai. Engine net upward accel deliver kar sakta hai. (a) Kya yeh already us point se past hai jahan ek burn ise save kar sake? (b) Minimum kya hoga jo exactly ise yahan se ground par stop kar de?
Recall Solution
(a) ke liye required ignition altitude (stopping distance ): Kyunki booster 1000 m par hai, jo 666.7 m se upar hai, yeh point se past nahi hai — ise girte rehna chahiye aur baad mein light karna chahiye. Uske paas margin hai.
(b) Minimum woh hai jo barely ise puri 1000 m stopping distance use karke stop kare: Answers: (a) point se past nahi (h_ign ≈ 666.7 m < 1000 m); (b) minimum . Interpretation: capable koi bhi engine ise land kar sakta hai; ek engine bas neechay light karta hai aur chota burn karta hai.
Problem L4.2
Upar wale case ke liye, aur mass kg ignition par () use karke, (a) burn duration aur (b) required thrust find karo.
Recall Solution
(a) Ignition m par hoti hai, speed abhi bhi m/s. (b) Thrust: Answers: (a) s; (b) N (1114 kN).
Level 5 — Mastery
Problem L5.1 — Live closed-loop recompute
Real thrust perfectly steady nahi hoti. Maano actual burn under-performs karke sirf deliver karta hai instead of planned 20. Vehicle har cycle mein live state se use karke commanded net accel recompute karta hai. Jis instant usne light kiya (planned), woh m/s, m par tha. (a) Us instant par closed-loop law kya net accel demand karta hai? (b) Agar engine sirf 18 tak pahunch sakta hai, guidance kya karta hai, aur kya landing abhi bhi possible hai? Reason karo.
Recall Solution
(a) , par: (b) Engine sirf 18 de sakta hai, yaani woh under-brake karta hai. Toh agly cycle mein vehicle planned se kam speed shed karti hai; naye altitude par ratio climb karta hai (speed shrinking altitude ke liye bahut zyada hai). Closed-loop law isliye agly cycle mein zyada accel demand karta hai. Jab tak engine ki ceiling ( jo woh actually bana sakta hai, throttle aur mass diye hue) rising demand se upar rehti hai, tab tak yeh catch up kar leta hai aur at nail karta hai. Agar demand touchdown se pehle engine ceiling se kabhi bhi zyada ho jaaye, toh case L3.2 ke "late ignition" crash ban jaata hai. Yahi exactly kyun guidance closed-loop hai: woh har cycle mein re-solve karta hai ek pre-scripted plan par trust karne ki bajay. Fuel-optimal version of this recompute-under-constraints problem ke liye, SpaceX-style guidance ek real-time convex optimization solve karta hai lossless convexification ke zariye, har cycle mein bounded time mein global optimum guarantee karta hai. Answer: (a) 20 m/s² demand karta hai; (b) woh har cycle mein accel up-command karta hai; landing tab survive karti hai jab engine ceiling rising demand se upar rahti hai.
Problem L5.2 — Degenerate / edge cases
Ignition formula teen limiting cases mein kya predict karta hai, discuss karo, aur batao ki har ek physical hai ya nahi: (a) ; (b) ; (c) bahut bada.
Recall Solution
(a) (already at rest). substitute karo: . Physical meaning: agar tumhari speed already zero hai toh tumhe koi braking distance nahi chahiye () — kinematically tum wahan touch down kar sakte ho jahan ho. (Real gravity phir tumhe neeche kheenchna shuru karega, toh tumhe hold karne ke liye abhi bhi thrust chahiye, lekin pure "speed kill karne ki distance" genuinely zero hai.) Formula correct aur sensible hai.
(b) (engine barely gravity se stronger). Jab positive side se zero ki taraf shrink hota hai, denominator jabki numerator fixed rehta hai, toh . Physical meaning: ek rocket jo barely decelerate kar sakta hai, stop karne ke liye ek infinite runway chahiye — yaani kisi bhi real corridor ke andar woh fall ko rok hi nahi sakta. Yeh boundary hai jahan engine bahut weak hai (TWR just above 1); landing impossible ho jaati hai, aur formula correctly diverge karke warn karta hai.
(c) bahut bada (extremely powerful burn). Jab , denominator bina bound ke badh ta hai, toh . Physical meaning: ek enormously powerful engine ko almost koi stopping distance nahi chahiye — tum almost poora raasta deck tak girte ho, phir ek violent, bahut-short burst tumhe rok deta hai. Mathematically fine, lekin yeh near-perfect timing (ek vanishingly small ignition window) aur punishing g-loads maangta hai, toh real vehicles deliberately ek moderate choose karte hain taaki timing corridor aur structural loads dono sane rahen.
Takeaway: formula har extreme par sensibly behave karta hai — ; weak engine (impossible); strong engine (twitchy). Koi bhi case surprise nahi karta, jo exactly ise ek trustworthy live decision rule banata hai.
Final figure poori family plot karta hai: engine ke ke against, fixed m/s ke liye. Horizontal axis net accel m/s² mein hai, vertical axis ignition altitude m mein hai, aur accent-red curve hi ignition law hai.

Red curve trace karo: far left par (small ) yeh infinity ki taraf shoot up karta hai — woh case (b) hai, too-weak engine. Far right par (large ) yeh zero ki taraf flatten hota hai — woh case (c) hai, twitchy super-strong engine. Do annotated ends exactly wahi limits hain jinke baare mein tumne upar reason kiya.
Active recall
Recall Ladder ka one-line summary
Upar sab kuch ek equation hai jo paanch angles se dekhi gayi hai: . Recognition ise naam deta hai, Application ise plug karta hai, Analysis ise tod ta hai (early/late/IMU drift), Synthesis ise aur burn time ke saath combine karta hai, aur Mastery ise live (closed-loop recompute) aur robust (edge cases) banata hai. Prerequisite tools Kinematics — v²=v0²+2as, Rocket Equation (Tsiolkovsky), PID Control, Thrust Vectoring (Gimbal), aur Attitude Dynamics & Quaternions mein hain.