Exercises — Mechanization equations — integrating IMU to get position, velocity, attitude
3.5.16 · D4· Physics › Guidance, Navigation & Control (GNC) › Mechanization equations — integrating IMU to get position, v
Quick symbol reminder, taaki pehli line koi bhi padh sake:
L1 — Recognition
Problem 1.1
Ek stationary IMU bench pe flat rakha hai (NED, Down ). Har accelerometer axis kya read karta hai, aur gyros kya read karte hain?
Recall Solution 1.1
Gyros: (chhoti si Earth-spin term ko ignore karte hue jo note high-grade gyros ke liye flag karta hai). Accels: . Bench upar push karta hai, aur NED mein up-direction hai, isliye felt (specific) force Down pe baith ta hai. Yeh zero nahi hai: accelerometer gravity feel nahi kar sakta, sirf contact push feel karta hai.
Problem 1.2
Mechanization ke teen "layers" ko us order mein naam do jis order mein inhe compute karna zaroori hai, aur ek-word ka reason batao ki attitude pehle kyun aata hai.
Recall Solution 1.2
Order: Attitude → Velocity → Position. Reason: rotation. Accelerometer ki force body axes mein hoti hai; (attitude) chahiye taaki use nav axes mein rotate kar sako, pehle gravity add karo aur phir velocity integrate karo.
Problem 1.3
Velocity equation mein kaun sa term "gravity wapas add" karta hai, aur yeh add karna zaroori kyun hai?
Recall Solution 1.3
Term hai. Zaroori isliye hai kyunki accelerometer physically gravitation sense nahi kar sakta (gravity har atom ko equally pull karti hai, isliye koi internal strain nahi hoti). Software ko ise wapas dalna padta hai.
L2 — Application
Problem 2.1
Flat-Earth, no rotation. Ek sled nav- pe read karta hai (gravity off-axis handle ki gayi hai). Rest se origin pe start karte hue, pe aur nikalo.
Recall Solution 2.1
Flat-Earth velocity law with no Coriolis, no on-axis gravity: . Ek baar integrate kyun karte hain? Acceleration velocity ka rate of change hota hai, isliye velocity acceleration ka running total (integral) hai: . Dobara integrate kyun karte hain? Velocity position ka rate of change hoti hai, isliye position velocity ka running total hai: . Yeh do-step "integral ka integral" mechanization ki poori spirit hai: rates andar, positions bahar.
Problem 2.2
ke liye skew-symmetric matrix (symbol reminder mein define kiya gaya) compute karo aur verify karo ki yeh ke liye reproduce karta hai.
Recall Solution 2.2
ko skew template mein plug karte hue: se multiply karo: milta hai. Cross product . ✔ Dono match karte hain — yehi exact reason hai ki mein skew matrix cross product ko replace karta hai.
Problem 2.3
Latitude , height pe, vehicle due East pe fly karta hai. Prime-vertical radius of curvature hai. Longitude rate rad/s mein nikalo.
Recall Solution 2.3
Yeh formula kyun? Longitude ek angle hai jo Earth ki spin axis ke around measure hota hai. Jab tum East fly karte ho tum constant latitude ka circle (ek "parallel") trace karte ho. Iska radius poora Earth radius nahi balki shrunken hai, kyunki latitude pe parallel ek small circle hai jiska radius big circle ke radius ka guna hota hai. Sweep kiya gaya angle equals arc-length traveled divided by circle ka radius, isliye Plug in karo: longitude circles ko poles ki taraf shrink karta hai, isliye same East speed se tum longitude ke around jitna upar latitude, utna tez spin karte ho. Dekho Radii of Curvature of the Earth Ellipsoid.
L3 — Analysis
Problem 3.1
Ek gyro mein East axis ke baare mein constant bias hai. Vehicle static hai aur initially level hai. ke baad attitude (tilt) error degrees mein estimate karo.
Recall Solution 3.1
Ek static-vehicle tilt error linearly accumulate hota hai: . Convert karo: . Mechanization believe karta hai ki yeh rotate hua jab hua nahi tha, kyunki yeh fake rate integrate karta hai.
Problem 3.2
Problem 3.1 continue karo. Yeh 0.1 rad tilt gravity ko misrotate karta hai. Spurious horizontal acceleration estimate karo jo yeh inject karta hai, use karte hue.
Recall Solution 3.2
Ek tilt gravity vector ko tilt kar deta hai taaki ek component horizontal channel pe spill ho jaaye: Yeh dominant INS error path hai: ek chhoti attitude error almost poora wahan leak kar deti hai jahan woh belong nahi karta.
Figure geometry ko concrete banata hai. True gravity (red) straight Down point karti hai. Mechanization sochta hai Down dashed white axis hai, se tilted (blue arc). Jab yeh apne tilted axis ke along "gravity" remove karta hai, ek yellow horizontal slice uncancelled reh jaata hai — woh leftover fake horizontal acceleration hai jo tumne compute ki.

Problem 3.3
Ek accelerometer bias se velocity error jaisi kyun grow karti hai, jabki same bias se position error jaisi kyun grow karta hai?
Recall Solution 3.3
Velocity acceleration ka ek integral hai: (linear). Position ek aur integral hai: (quadratic). Har integration "time" se multiply karta hai, isliye chain ki har layer error mein ki ek power add kati hai — yehi reason hai ki INS drift accelerate karta hai aur GNSS correction ki zaroorat hoti hai.
L4 — Synthesis
Problem 4.1
Level IMU, no rotation, flat-Earth. Accels m/s read karte hain (ek chhota -bias of ). ke saath, nikalo, phir aur North position ke baad rest se.
Recall Solution 4.1
Kyunki attitude identity hai (no tilt, no rotation) . Flat-Earth velocity core use karte hue: Down cancel ho jaata hai (static vertical channel ✔). Sirf North bias survive karta hai. . North position . Ek -scale bias ne hume do minute se kam mein 100 m off kar diya.
Problem 4.2
Gyro bias ko accel channel ke saath combine karo. Static, level, gyro bias East ke baare mein ke liye. Nikalo (a) tilt, (b) leaked horizontal acceleration s pe tilt ko instantly uss value ka maante hue, aur (c) roughly bound karo horizontal velocity error yeh maante hue ki acceleration se uss value tak linearly ramp karta hai.
Recall Solution 4.2
(a) . (b) . (c) Tilt linearly grow karta hai, isliye leaked accel small angles ke liye. Integrate karo: Velocity error yahan jaisi grow karta hai kyunki bias ek tilt feed karta hai jo khud ke saath grow karta hai — ek compounding, faster-than-linear leak.
L5 — Mastery
Problem 5.1
Ek pilot propose karta hai: "30-second drone hop under 1 km ke liye, Earth-rotation aur transport terms skip karo." Dono terms ko quantify karo jo tum drop kar rahe ho. (i) Coriolis/Earth-rotation part for . (ii) Transport-rate part : same East aur ke liye iska dominant component use karo, aur ise acceleration mein convert karo. Dono ko typical accel-bias-driven acceleration ke against compare karo. Kya inhe drop karna justified hai?
Recall Solution 5.1
(i) Coriolis magnitude bound: . (ii) Transport rate: . Frame-correction acceleration ke roop mein . Bias-driven se compare karo: Coriolis almost chhota hai, aur transport term se bhi zyada chhota hai. mein dono mein se bada (Coriolis) se zyada se zyada ka position error milta hai; transport term ka kuch centimetres ka hai. Verdict: Earth-rotation aur transport dono drop karna is short, slow, low-accuracy hop ke liye justified hai (flat-Earth 80/20 core). Yeh ek long-range, high-grade system ke liye justified nahi hoga jahan dominate karta hai. Dekho Coriolis and Centrifugal Effects aur Strapdown vs Gimbaled INS.
Problem 5.2
Design check. Tum chahte ho ki pure inertial coasting (no GNSS) ke ke baad horizontal position error se kam rahe, ek single accel bias se dominated ho (level, no tilt maano). Maximum allowable kya hai?
Recall Solution 5.2
Constant bias se position error: . , set karo: "Milli-g" mein (): . Toh tumhe half a milli-g se behtar accelerometer chahiye — ek real navigation-grade requirement, aur exactly yehi reason hai ki INS-GNSS fusion exist karta hai is drift ko bound karne ke liye.
Recall Poori ladder ki ek-line summary
Ek IMU rate aur specific force feel karta hai; software rotate karta hai, gravity add karta hai, aur integrate karta hai — aur har integration ek chhote se bias ko ek fast-growing error mein badal deta hai, yehi reason hai ki real systems GNSS ke saath fuse karte hain.