3.5.28 · D5 · HinglishGuidance, Navigation & Control (GNC)
Question bank — Block diagram algebra
3.5.28 · D5· Physics › Guidance, Navigation & Control (GNC) › Block diagram algebra
Shuru karne se pehle, ek vocabulary anchor — taaki neeche koi bhi word undefined na rahe:
- — reference input: woh signal jo hum loop mein daalte hain (the "command", jaise "is altitude par jao"). Yeh woh arrow hai jo sabse pehle summer mein enter karta hai.
- — error signal: summer ka output, , yaani command aur jo feed back ho raha hai uske beech ka gap. Socho "woh gap jo controller ko close karna hai."
- — fed-back signal: woh signal jo feedback block summer ko wapas bhejta hai, .
- — output: woh signal jo forward block se nikalti hai, . Yeh woh cheez hai jo hum actually measure ya move karte hain.
- , blocks hain: aisi boxes jo unme enter hone wale signal ko ki ek function se multiply karti hain. Socho "ek slide jo tumhari speed ko scale karta hai."
- Summer ek circle hai jo usme enter hone wale arrows ko add ya subtract karta hai.
- Take-off point ek dot hai jo ek signal ko kayi wires mein copy karta hai (copying se kuch nahi badalta).
- Loop gain : woh total factor jo ek signal loop mein ek baar jaane aur wapas aane par uthata hai.
Neeche di gayi picture un charon symbols ko real wires se fix karti hai — jab bhi koi derivation , , , ya ka naam le, iske paas wapas aao.

Kyun numerator kabhi nahi badalta jab feedback positive ho jaata hai, yeh dekhne ke liye, do summers ko side by side dekho.

True or false — justify
Series blocks phir same output dete hain agar tum unka order phir kar do
True — scalar transfer functions ke liye multiplication commute karta hai, , isliye cascade output identical hota hai. (Yeh sirf matrix/MIMO blocks ke liye fail hota hai, jo commute nahi karte.)
Parallel blocks har case mein combine hote hain, chahe summer ke signs kuch bhi hon
False — sign summer se inherit hota hai. Agar lower branch minus ke saath enter kare, to milega; plus automatic nahi hai.
Negative feedback ke liye closed-loop transfer function hai
True — aur se milta hai. mein jo hai woh negative summer ki pehchaan hai.
Positive feedback sirf numerator ka sign flip karta hai, jisse milta hai
False — yeh denominator ka sign flip karta hai: . Summer ab fed-back signal ko add karta hai, isliye , jisse denominator badalta hai, numerator nahi (upar s02 derivation dekho).
Agar (unity feedback) hai to loop gain forward gain ke barabar hota hai
True — loop gain hai , isliye round-trip factor exactly forward block hai. Closed-loop TF ban jaata hai .
Tum ek summing junction ko block se aage downstream move kar sakte ho bina kisi correction ke, kyunki summers sirf add karte hain
False — summer ne jo bhi add kiya woh sab se multiply ho jaayega. Arithmetic sahi rakhne ke liye, har moved branch ko se pre-multiply karna hoga: (figure s03 dekho).
mein jo "" hai uska koi physical meaning nahi; yeh sirf algebra hai
False — yeh direct passthrough hai: output bina kisi feedback trip ke ek baar input tak pahunchta hai. woh trip hai; ka matlab hai "tum, seedha ek baar through jaate hue."
ko bada karna hamesha closed-loop gain ko bada karta hai
False — bada matlab bada , jo denominator mein baitha hai, isliye zyada feedback closed-loop gain ko shrink karta hai. Yahi shrinking feedback ka poora point hai (ek huge ko tame karo).
Ek take-off point ko ek block ke across freely slide kar sakte ho kyunki signal copy karna kuch nahi badalta
False — signal ko copy karna use nahi badalta, lekin kahan copy karo yeh matter karta hai. Block ke baad tap read karta hai ki jagah, isliye original value wapas paane ke liye insert karna padega (figure s04 dekho).
Spot the error
"Inner aur outer loops? Main pehle outer loop reduce karunga kyunki yeh main control loop hai." — flaw dhundho
Outer feedback formula ko apna forward path already ek single block hona chahiye, lekin woh path abhi bhi un-reduced inner loop chhupa raha hai. Tumhe inside-out kaam karna hoga: pehle inner loop ko ek block mein collapse karo (figure s05).
"Cascade forward path with feedback : closed-loop ." — isko pakdo
Loop gain poora round trip hai , sirf nahi. Correct denominator hai ; dono forward blocks loop ke andar hain.
"Unity feedback ka matlab hai, isliye closed-loop TF bas hai." — isko pakdo
Tum substitute nahi kar sakte; ek function of hai, number 1 nahi. Unity feedback set karta hai jisse milta hai, jo nahi hai jab tak exactly 1 na ho.
"Ek take-off ko ke downstream move karte hue, main branch ko se multiply karta hoon match karne ke liye." — isko pakdo
Ulta hai. Downstream tap already read karta hai (bahut bada), isliye tum se divide karte ho, yaani insert karo. se multiply karna woh rule hai jab ek summer ko ke aage move karo, take-off ke liye nahi.
"Parallel branches dono same wire se start hote hain, isliye mujhe take-off point ki zaroorat nahi." — isko pakdo
Chahiye hoga — ek single wire bina take-off dot ke legally do blocks mein fan out nahi ho sakta jo copy ko mark kare. Yeh woh primitive hai jo ek signal ke do jagah feed hone ki permission deta hai.
"Loop gain stability ko affect nahi kar sakta; sirf numerator poles matter karte hain." — isko pakdo
Stability denominator se set hoti hai (characteristic equation), jo puri tarah loop gain se bani hai. Numerator poles set nahi karta.
Why questions
Blocks apne inputs ko multiply kyun karte hain, add kyun nahi karte?
Kyunki ek LTI system time mein convolution se kaam karta hai, aur Laplace transform convolution ko mein multiplication mein convert kar deta hai. Isliye "ek block se guzarna" literally hai "by multiply karna."
Nested loops ko inside out reduce kyun karna padta hai?
Har feedback reduction ke liye zaroori hai ki uska forward path pehle se ek single transfer function ho. Un-reduced inner loop ko wrap karne wala outer loop us condition ko violate karta hai, isliye pehle innermost collapse karo.
Feedback "one-plus-loop-gain se divide" kyun karta hai loop gain subtract karne ki jagah?
Kyunki fed-back signal ke khud proportional hai: . ko cross move karne se milta hai, phir factor hota hai, isliye . terms ka ek collect-and-factor hai — kabhi bhi gains ka subtraction nahi.
Wahi formula Op-amp gain ka dil kyun hai?
Ek op-amp ka enormous, poorly-controlled open-loop gain hota hai; feedback wrap karne se yeh ek stable, resistor-set closed-loop gain tak divide ho jaata hai jab . Same block algebra, alag hardware.
Ek poore feedback loop ko reduce hone ke baad ek equivalent block kyun treat kar sakte hain?
Kyunki block algebra us equation ko kabhi nahi badalta jise diagram encode karta hai — yeh sirf picture ko rewrite karta hai. Reduced single block ka identical input-output relation hota hai.
Hum kabhi kabhi Mason's gain formula ko in moves ke upar kyun prefer karte hain?
Kyunki tangled multi-loop diagrams mein equivalence moves error-prone ho jaate hain; Mason's formula seedha graph ke paths aur loops se answer read karta hai bina kuch slide kiye.
Edge cases
Closed-loop TF kya hoga agar loop gain (bahut bada open-loop gain) ho?
— output sirf feedback path se govern hota hai, se independent. Yahi exactly reason hai kyun bade wale op-amps clean, -controlled gain dete hain.
(positive feedback) ka kya hoga jab ?
Denominator , isliye closed-loop gain blow up karta hai — system instability/oscillation ke edge par hai. Yeh positive feedback ki resonance/runaway boundary hai.
Ek parallel pair ka equivalent block kya hoga jab ek adding summer mein ho?
— branches cancel ho jaate hain aur equivalent block zero hai; koi bhi signal output tak nahi pahunchta. Ek degenerate lekin perfectly legal result.
Agar feedback block ho to loop kya reduce karta hai?
— bilkul koi feedback nahi, isliye tum open-loop forward block wapas paate ho, jaise expected hota hai jab return path cut ho.
Series-equivalent block kya hoga agar chain mein ek block (ek pure wire) ho?
Yeh 1 ka factor contribute karta hai: . Ek unity block ek identity element hai — yeh signal ko unchanged pass through karta hai.
Kya tum ek summing junction ko take-off point ke past bina correction ke move kar sakte ho?
Nahi — tumhe dono par har signal value preserve karni hogi. Aise rearrangements ko compensating blocks ya duplicated summers chahiye; hamesha dummy input se test karte hue insist karo ki har wire apni exact value rakhe.
Connections
- Transfer functions — woh , objects jo har block ke andar rehte hain; upar har trap asal mein ek statement hai is baare mein ki yeh kaise multiply aur combine karte hain.
- Laplace transform — woh reason hai kyun "ek block se guzarna" ka matlab "multiply karna" hai, kyunki yeh time-domain convolution ko -domain multiplication mein convert karta hai (pehle Why question ka jawaab).
- Feedback control loops — Rule 3 ka engineering context; is page par /// derivation exactly woh loop hai jo woh systems close karte hain.
- Signal flow graphs & Mason's gain formula — woh move-free alternative jo Spot-the-error section mein take-off/summer sliding traps ko sidestep karta hai.
- Op-amp gain — woh hardware jahan edge case actually stable amplifiers banane ke liye use hota hai.
- Stability & characteristic equation — explain karta hai kyun denominator (numerator nahi) poles set karta hai, last Spot-the-error item justify karta hai.