3.5.51 · D5 · HinglishGuidance, Navigation & Control (GNC)
Question bank — Augmented proportional navigation — gravity compensation
3.5.51 · D5· Physics › Guidance, Navigation & Control (GNC) › Augmented proportional navigation — gravity compensation
Stage set karna — pehle har symbol earn karo
Kisi bhi trap se pehle, yahan woh picture hai jisme poora page jeeta hai. Do cheezein ek vertical plane mein move karti hain: missile aur target. Missile se target tak ka seedha arrow line of sight (LOS) hai — socho jaise unhe ek tight dhaga jod raha ho.

Ab woh second-order dynamics build karo jo "cancel " ko kuch matlab dete hain.

Neeche use hone wale har symbol ka quick refresher:
- = LOS angular rate; = uski rate of change; = LOS elevation angle (horizontal se upar).
- = LOS-normal direction; = perpendicular gravity ka magnitude.
- = commanded accel par project ki gayi; = target accel par project ki gayi.
- = navigation constant; = closing speed; = target accel LOS; = time-to-go.
- Net perpendicular dynamics: , with .
- Full law: .
True or false — justify karo
Commanded acceleration mein gravity ka effect already include hai, isliye humein term ki zaroorat nahi.
False — sirf wahi hai jo autopilot command karta hai; gravity uske upar se act karti hai. Physical normal accel hai, isliye us sum ko pure-PN demand ke barabar banane ke liye pre-subtract karna zaroori hai.
Gravity compensation missile ko straight line mein fly karata hai.
False — yeh effective guidance loop ko aise behave karata hai jaise gravity-free ho; missile physically phir bhi droops karta hai, lekin guidance us droop ko ab target motion ki tarah nahi padhti.
Agar target kabhi maneuver na kare, augmentation term vanish ho jaata hai lekin term generally nahi hota.
True — augmentation ko khatam karta hai, phir bhi gravity LOS ko bend karti rehti hai jab tak shot vertical na ho, isliye compensation abhi bhi required hai.
Ek poore ballistic arc mein gravity average out ho jaati hai, isliye homing ke dauran ise ignore karne ka koi cost nahi.
False — terminal homing ke dauran missile actively close ho raha hai; downward ka continuous effect ek persistent produce karta hai jo ek steady miss mein accumulate hoti hai, yeh average out nahi hoti.
Bada navigation constant target-maneuver term ko increase karta hai lekin gravity term ko untouched chodta hai.
True — gravity term hai, se independent; sirf PN aur augmentation terms ke saath scale karti hain.
Compensation reactive hai: miss aane ke baad droop fix karta hai.
False — yeh predictive hai; advance mein supply karke woh hold karta hai taaki droop-induced error kabhi appear hi na ho.
Purely vertical (seedha-upar) engagement ke liye gravity-compensation term zero hai.
True — gravity phir poori tarah LOS ke saath () lie karti hai, isliye aur kuch bhi perpendicular cancel karne ki zaroorat nahi.
Gravity ka LOS ke saath wala component guidance ke liye harmless hai.
True ( ke liye) — sirf closing speed ko change karta hai; yeh sightline ko rotate nahi karta, isliye woh LOS-rate corrupt nahi karta jis par PN steer karta hai.
Transverse equation mein, ko ke andar chodne par bhi zero par settle ho sakta hai.
False — ek uncancelled ek constant forcing term ki tarah kaam karta hai, isliye (hence ) kabhi steady zero nahi pahunchta; yahi woh persistent rate hai jise PN wastefully chase karta hai.
Error dhundo
"Set karo ."
Wrong sign — gravity subtract honi chahiye. add karna droop ko cancel karne ki jagah double kar deta, kyunki real gravity already physical normal accel mein contribute karti hai.
"Poore se compensate karo: likho ."
Over-correction — sirf LOS-normal part hi sightline ko bend karta hai. Poora subtract karna ek phantom perpendicular pull se ladna hoga jo wahan hai hi nahi aur control authority waste karega.
"Kyunki negative hai, compensation term plain dot product se honi chahiye."
Half-right, half-trap — dot product is negative hai kyunki , ke tilt ke opposite point karta hai, lekin projection ke magnitude ke roop mein define hai, aur command gravity ki downward direction explicit minus sign se carry karta hai; dono conventions ko mix karna sign ko double-count karta hai.
"LOS elevation par, use karo."
Wrong trig function — is convention mein ( horizontal se upar measure kiya gaya) : horizontal LOS () maximum deta hai kyunki , jabki galti se kehta ki koi compensation chahiye hi nahi.
"Kyunki abhi hai, bilkul koi command nahi chahiye, gravity term bhi nahi."
Error — inertial target aur momentarily fixed LOS ke saath, pure PN deta hai, lekin gravity turant ek droop create kar deti; compensation phir bhi command karta hai ko zero par rakhne ke liye.
"APN ka gravity ko bhi handle karta hai, kyunki gravity bhi sirf ek aur acceleration hai."
Error — woh term target ke known maneuver ko zero-effort-miss ke zariye feed-forward karta hai; gravity ek self acceleration hai jo missile par act karti hai aur apne alag term ki zaroorat hai.
" mein upar-neeche gravity ko average karne se aaya hai."
Error — yeh target maneuver ke kinematic ZEM se aaya hai; command gain ke against cancel hota hai aur chodta hai, gravity se koi lena-dena nahi.
" ko poore engagement mein ek fixed constant ki tarah treat kiya ja sakta hai."
Error — impact par zero tak shrink hota hai; ise fixed maan lena kisi bhi ZEM-based feed-forward ko galat scale karega jab range collapse ho.
Why questions
Sirf gravity ka perpendicular component LOS rate ko kyun affect karta hai?
Kyunki mein sirf transverse accel hi drive karta hai; ke along koi force radial equation mein jaati hai aur sirf range ko lengthens/shortens karti hai, sightline ko kabhi rotate nahi karti.
Gravity compensation ke liye horizontal LOS worst case kyun hai?
ke saath poora gravity vector LOS ke perpendicular hai, isliye — sightline ka maximum possible bending.
Uncompensated gravity missile ki g-capacity kyun waste karti hai?
PN continuously lateral accel command karta hai gravity-induced ko null karne ke liye, isliye precious acceleration budget real target ki jagah ek ghost se ladne mein kharch hota hai.
ko engagement badhne ke saath recompute kyun karna chahiye, ek baar fix karne ki jagah?
LOS elevation poori flight mein change hoti hai, isliye bhi change hota hai; ek stale value geometry rotate hone par over- ya under-compensate karti.
Gravity ko sirf uski vertical value use karne ki jagah par projection ke zariye kyun express karte hain?
Kyunki guidance LOS frame mein kaam karta hai; sirf LOS-normal direction par projection hi dynamics mein enter karti hai — dekho Coordinate frames & projections.
Half-factor se free ek clean number ke roop mein kyun survive karta hai?
Kyunki target miss ki tarah grow karta hai jabki ZEM-to-command gain ek compensating carry karta hai; dono cancel ho jaate hain, sirf chodkar.
Loop ko "effectively gravity-free" banana non-maneuvering target par intercept guarantee kyun karta hai?
Kyunki gravity-free frame mein pure PN drive karta hai, jo constant-bearing, decreasing-range collision condition hai — sightline rotate karna band kar deti hai isliye paths meet karte hain.
Edge cases
LOS elevation exactly (target seedha upar, straight-up shot).
; koi compensation term act nahi karta, lekin along-LOS gravity phir bhi closing speed slow karti hai — ke liye harmless lekin energy ke liye real.
Closing velocity (missile ab close nahi ho raha, ).
PN term collapse ho jaata hai aur , isliye command se dominate hoti hai; geometrically yeh ek degenerate near-parallel engagement hai jahan PN apni intercept guarantee khota hai. Agar toh range badh rahi hai — overshoot/opening pass.
Target maneuver unknown / unestimated ( ko set kiya gaya jabki target turn kar raha hai).
Law PN plus gravity compensation tak reduce ho jaata hai; yeh true maneuver se lag karega aur ek residual miss chodega, kyunki feed-forward sirf wahi cancel kar sakta hai jo estimation provide kare.
inertial target aur horizontal LOS ke saath.
Pure PN aur augmentation dono dete hain, phir bhi ; command exactly hai, woh maximum predictive push jo true collision course ko drooping se rokta hai.
Descending LOS jahan target horizontal se neeche ho ().
Kyunki even function hai, — ka sign compensation ka magnitude nahi badlata, sirf geometry badlati hai; ek shallow depression ( chhota) abhi bhi nearly full chahata hai, ek steep dive () almost kuch nahi chahata.
LOS elevation se zyada (, target above-and-behind).
negative ho jaata hai, isliye projection , ke saath direction flip karta hai; convention ke zariye carry karne par compensation push automatically sign reverse karta hai — geometry cosine handle karta hai, haath se nahi.
Bahut kam time-to-go ( impact par).
ZEM-based augmentation finite rehta hai jabki spike kar sakta hai; vanishing interval mein gravity ka contribution negligible ho jaata hai, isliye term bilkul end par sabse kam matter karta hai.