3.5.16 · D5 · HinglishGuidance, Navigation & Control (GNC)

Question bankMechanization equations — integrating IMU to get position, velocity, attitude

2,252 words10 min read↑ Read in English

3.5.16 · D5 · Physics › Guidance, Navigation & Control (GNC) › Mechanization equations — integrating IMU to get position, v

Ye bank paanch classic misconceptions dhundhta hai: (1) accelerometers gravity "feel" karte hain, (2) rotations numbers ki tarah add hote hain, (3) Coriolis ek real force hai, (4) flat-Earth core hamesha safe hai, (5) drift time mein linear hota hai.


True or false — justify karo

Ek stationary, level accelerometer apne Down axis par zero read karta hai.
False. Yeh read karta hai (NED mein, Down , reading support ke opposite hai). Table usse upar push karti hai, aur specific force contact force hai, isliye static reading support ke opposite magnitude hai — zero sirf free fall mein hota hai.
Free fall mein (drop kiya gaya) ek IMU apni khud ki falling acceleration measure karta hai.
False. Yeh read karta hai. Gravity proof mass ke har part ko equally accelerate karti hai, isliye kuch bhi sensor ko squeeze nahi karta — free fall ke dauran koi specific force detect nahi hoti.
Gyro bias se velocity error time ke saath linearly badhta hai.
False. Isko step out karo: ek gyro bias attitude ko linearly tilt karta hai, . ka tilt gravity ko misrotate karta hai isliye ek horizontal acceleration level channel mein leak hota hai. Use ek baar integrate karne par velocity aur dobara integrate karne par position milta hai — isliye gyro bias se position error ki tarah badhta hai, accelerometer bias ke se bhi bura.
Agar pehle accelerometer integrate karo toh attitude se pehle velocity compute kar sakte ho.
False. Accelerometer output body axes mein rehta hai. Tumhe (attitude) chahiye taaki use nav axes mein rotate kar sako () gravity add karne se pehle, isliye attitude pehle aani chahiye.
Velocity equation mein add kiya gaya gravity vector pure Newtonian gravitation hai.
False. Yeh plumb-bob (apparent) gravity hai = gravitational attraction minus Earth ke spin se centrifugal acceleration. Isliye yeh local vertical (Down) ke along point karta hai, na ki exactly Earth ke centre ki taraf.
Ek short indoor run par Earth-rate aur transport-rate terms safely drop kar sakte ho.
True. Short baselines ke liye aur corrections negligible hain; flat-Earth trio (NED mein) 80/20 core hai. NED convention us trio mein har sign fix karta hai.
Gyro se rotation rates ko sirf time ke saath add karke total rotation angle mil sakta hai.
False. Finite 3-D rotations commute nahi karte; orientation curved manifold par rehti hai. Yahi wajah hai ki hum matrix/quaternion propagate karte hain (, upar define kiya gaya skew matrix use karke) angles sum karne ki jagah.
mein minus sign ek computational convention ki wajah se hai, physics ki wajah se nahi.
True (yeh ek convention hai). NED mein "Down" axis Earth ki taraf point karta hai, isliye positive downward velocity height decrease karti hai; sign purely axis direction ke choice se hai. (ENU mein yeh hota.)

Error dhundho

"Accelerometer acceleration measure karta hai, isliye main use directly double-integrate karke position get karta hoon."
Device specific force measure karta hai, acceleration nahi. Static rehne par raw integrate karne par ek fake inject hota hai; tumhe nav axes mein rotate karna hoga aur puri use karni hogi taaki gravity pehle add ho sake.
"Kyunki gyros read karte hain, main use seedha mein plug karta hoon."
Tumhe nav frame ke relative rate chahiye, , aur phir iska skew matrix banao. raw use karne par attitude Earth aur moving frame ke saath rotate ho jaata hai.
"Coriolis term vehicle par acting ek real physical force hai."
Yeh ek fictitious (frame) correction hai, real force nahi. Yeh sirf isliye appear hota hai kyunki hum Newton's law ko rotating/curving nav frame mein express karte hain; iske peeche koi physical push nahi hai.
"."
missing hai: correct hai , jahan East velocity component hai aur transverse radius hai. Longitude circles poles ki taraf shrink hote hain, isliye same eastward speed high latitude par zyada longitude sweep karti hai.
"Dono position rates same Earth radius use karte hain."
Ye alag radii of curvature use karte hain: latitude rate meridian radius use karta hai, longitude rate transverse radius use karta hai. Ellipsoid north-south vs east-west mein alag curve karta hai (north-south mein zyada sharply), isliye Radii of Curvature of the Earth Ellipsoid dekho.
"Velocity error aur position error thodi der baad same size ke hote hain."
Nahi — velocity acceleration error ka ek integration hai, position do integrations ka hai. Position error zyada tezi se accumulate hota hai (accel bias se ) velocity error se ().
"Main gravity ko remove karne ke liye accelerometer reading se subtract karta hoon."
Tum add karte ho: equation hai , isliye term woh jagah hai jahan gravity re-enter karti hai. Accelerometer pehle se hi true gravitational acceleration miss kar chuka tha (woh use feel nahi kar sakta), isliye gravity software mein daali jaati hai remove karne ki jagah.

Why questions

ko nav frame mein rotate karna kyun zaroori hai gravity apply karne se pehle?
Gravity naturally local vertical ke along express hoti hai (ek nav-frame direction). Do vectors add karne ke liye unhe same frame share karna hoga, isliye body-frame force pehle se rotate ki jaati hai ().
Velocity equation mein kyun hai lekin position aur attitude equations mein nahi?
Coriolis rotating frame mein observe ki gayi velocity differentiate karne se arise hota hai — yeh inherently ek first-derivative-of-velocity effect hai. Attitude aur position kinematics mein woh cross term same tarah involve nahi hoti (dekho Coriolis and Centrifugal Effects — Coriolis hai, tab sabse bada jab velocity rotation axis ke perpendicular ho).
Tilt error INS error ka dominant path kyun hai raw accelerometer bias ki jagah?
Ek chota attitude tilt full ko horizontal channel mein ke roop mein leak karta hai. Kyunki hai, even tilt zyattar accelerometer biases se bada horizontal acceleration inject karta hai.
Hum propagation ke liye roll-pitch-yaw angles ki jagah quaternion ya DCM kyun prefer karte hain?
Euler angles gimbal lock (singularities) suffer karte hain aur unki rates pitch ke paas blow up karti hain. DCM/quaternion har jagah well-behaved rehta hai — lekin tumhe ise ek sahi initial condition dena hoga (ek initial alignment ya unit quaternion) aur, kyunki numerical integration constraint se drift karta hai, har step renormalize karna hoga (DCM ko orthonormalize karo, ya quaternion ko unit norm par scale karo). Dekho Direction Cosine Matrix and Quaternions.
Transport rate exist hi kyun karta hai?
Kyunki local "down" direction physically re-tilt hoti hai jab tum curved Earth par travel karte ho. Nav frame rotate hota hai down point karte rehne ke liye, aur woh rotation gyro measurement se remove karni hogi.
Strapdown INS mechanization software par gimbaled ki tulna mein zyada demanding kyun hai?
Strapdown mein sensors body se bolted hote hain, isliye saari frame rotations (attitude layer) high rate par numerically karni padti hain; ek gimbaled platform frame ko mechanically hold karta hai, rotation hardware mein karta hai (dekho Strapdown vs Gimbaled INS).
Arc-rate ko radius se divide karne par angular rate kyun milta hai?
Arc length , isliye aur . Northward speed meridian arc rate hai, isliye .
Kalman filter un sensor biases ko kyun estimate kar sakta hai jo drift cause karte hain?
External aids (jaise GNSS) growing INS error reveal karte hain, aur kyunki bias-driven error ka ek known time signature hota hai (, , ), filter drift ko underlying bias se attribute karke correct kar sakta hai (dekho Kalman Filter for INS-GNSS Integration — filter ek drifting-but-smooth INS ko noisy-but-bounded GNSS fix ke saath blend karta hai).

Edge cases

Geographic pole par position rates mein kya break hota hai, aur kya fine rehta hai?
Longitude rate diverge ho jaata hai kyunki — pole par longitude ill-defined hai. Latitude rate perfectly finite rehta hai (meridian radius wahan normal positive length hai), isliye sirf east-west channel singular hai; wander-azimuth ya alag frame ise fix karta hai.
Ek perfectly stationary vehicle ke liye kya hona chahiye, aur sirf kyun nahi?
Yeh hona chahiye. Upward support force ( mein Down) nav axes mein rotate hoti hai aur add ki gayi Down gravity ko exactly cancel kar deti hai, isliye ke dono terms zero sum karte hain.
Attitude propagation mein kya hota hai jab gyro exactly zero read karta hai?
, isliye orientation constant hold hoti hai — non-rotating body ke liye sahi hai, aur iska matlab yeh bhi hai ki koi bhi zero-rate bias frame ko silently tilt karta rehta hai.
Kya flat-Earth model ek slow-moving vehicle ke liye safe hai jo ghanton tak run kare?
Nahi. Low speed par bhi, Earth rate () aur transport effects long time par accumulate hote hain, isliye long-duration navigation ko speed se regardless full Earth terms chahiye.
Constant accelerometer bias se time ke saath position error ka limiting behaviour kya hai?
Yeh ki tarah unbounded badhta hai — unaided INS drift signature. Isliye long missions ke liye bounded external aiding (GNSS) zaroori hai.
Equator par rest par ek accelerometer exactly gravitational attraction read karta hai?
Nahi — yeh apparent gravity read karta hai, jo gravitational attraction minus equatorial centrifugal term hai ( chota). Mechanization yahi apparent value use karta hai (dekho Gravity Model and Geoid).

Recall Yahan har trap ki one-line summary

Accelerometer specific force feel karta hai gravity nahi; rotations add nahi hote ( ko sahi initial alignment aur renormalization ke saath propagate karo); Coriolis ek frame term hai force nahi; flat-Earth core (NED) long time par fail hota hai na ki sirf distance par; aur drift (accel bias) ya (gyro tilt) ki tarah badhta hai — kabhi linearly nahi.