Parent note the parent topic padhne se pehle, tumhe har letter ka ownership lena hoga jo woh use karta hai. Yeh page unhe bilkul zero se build karta hai, us order mein jisme woh ek dusre par depend karte hain. Koi cheez use nahi hoti jab tak draw na ho.
Picture: ek signal ek curve hai. Horizontal position batata hai kab; height batati hai kitna.
Figure s01 — Ek wiggly curve. Magenta curve (signal) dekho, phir violet dashed drop-line jo ek instant t mark karta hai, aur orange dashed line jo uski height x(t) read off karta hai. Takeaway: curve par ek dot = ek moment par ek number.
Kyun yeh notation chahiye. Control un quantities ke baare mein hai jo evolve hoti hain: rocket ka angle, motor ki position, error. "5°" jaisa ek akela number ek snapshot hai; x(t) poori movie hai. Humein movie ke baare mein baat karni hai, isliye (t) chahiye.
Picture: target line r aur measured curve ym ko stack karo; unke beech vertical distance, har instant par, e hai. Target se upar, e negative hai (overshoot); neeche, positive.
Figure s02 — Do curves plus vertical bars. Flat violet line (target r) dekho, rising magenta curve (measurement ym), aur unke beech orange vertical bars — har bar ki length us instant par error e hai. Takeaway: error woh shrinking gap hai jo tum band karne ki koshish kar rahe ho.
Kyun subtraction aur ratio nahi? Kyunki ek difference apna sign rakhta hai. 2 ka ratio nahi bata sakta tum upar ho ya neeche — lekin e=−3 kehta hai "tune 3 se overshoot kiya, doosri taraf push karo." Sign steering direction hai. Isliye loop ek subtraction ke around bana hai.
Har block ek signal andar leta hai aur ek signal bahar deta hai. Har ek ko ek machine samjho: signal left se aata hai, changed signal right se nikalti hai.
Kyun hardware ko software se alag karo? Controller C sirf arithmetic hai — woh koi bhi number output kar sakta hai. Actuator A metal hai — woh sirf itna hi push kar sakta hai (yeh limit saturation kehlati hai, Actuator Saturation and Anti-Windup mein explore ki gayi hai). Donon ko confuse karna real failures ko chhupa deta hai, isliye parent unhe alag letters mein rakhta hai.
Yeh tool question hai. Har block apna input delay, smooth, ya amplify karta hai — ek differential equation (rates of change) se describe hota hai. Boxes ko chain karna matlab derivatives ko chain karna, jo time mein horrible algebra hai.
Picture:s ek 2-D map par rehta hai (s-plane). Left half = decaying = safe. Right half = exploding = unstable. Bilkul vertical middle line par = na yeh na woh — sustained oscillation. Signal ka behaviour decide hota hai ki uske special points is map par kahan hain.
Figure s03 — S-plane map. Violet-shaded left half dekho (poles yahan = decaying, STABLE, violet ×'s ki tarah drawn), magenta-shaded right half (poles yahan = growing, UNSTABLE), aur orange dots jo bilkul vertical axis par baithe hain (σ=0) — poles yahan na grow karte hain na decay, forever-ringing oscillation dete hain (marginal stability). Takeaway: horizontal position = stability, height = wobble speed.
Kyun yeh tool aur ODEs solve karna nahi? Kyunki ek baar hum s mein hain, "signal box C se phir box A se phir box P se guzrta hai" simply C(s)A(s)P(s) hai — plain multiplication. Yahi akaula reason hai ki parent itni casually G=CAP likh sakta hai. Full details Transfer Functions and Laplace Domain mein hain.
Upar ke (numerator) roots zeros kehlate hain — s ki woh values jo output ko vanish karti hain.
Neeche ke (denominator) roots poles kehlate hain — s ki woh values jo box ko "blow up" kar deti hain. Poles stability decide karte hain (dekho Poles Zeros and Stability).
Kyun ek fraction? Kyunki ek physical system kuch frequencies par strongly respond karta hai aur kuch par weakly. Do polynomials ka ratio exactly woh shape hai jo "yahan amplify karo, wahan ignore karo" capture karta hai. Example: parent ka motor P(s)=s(s+2)1 mein poles s=0 aur s=−2 par hain.
Forward boxes ko chain karne se G=CAP milta hai. Loop ke puri tarah around jaana (forward through G, back through sensor H(s)) unhe multiply karta hai: yeh round-trip factor GH loop gain hai.
Picture: signal loop ke around ghoomta hai, har lap −GH se scale hota hai, laps alternately add aur cancel hote hain jab tak settle na ho. Agar ∣GH∣ chhota hai, woh jaldi mar jaate hain; agar zyada bada, woh badhte hain — instability.
Figure s04 — Bars plus running total. Orange bars dekho (har lap ka contribution (−GH)n — notice karo woh sign flip karte hain aur shrink karte hain), magenta dotted line (running sum jaise laps pile up hoti hain), aur violet dashed line jis par woh settle hoti hai, 1/(1+GH). Takeaway: feedback subtraction, repeated, exactly woh geometric series hai jo 1+GH produce karta hai.
Jab loop ka denominator ek quadratic s2+2ζωns+ωn2 hai, do numbers sab kuch describe karte hain ki woh kaise settle hota hai (dekho Second-order System Response).
Kyun yeh do aur raw coefficients nahi? Kyunki ζ aur ωn directly jo tum feel karte ho se map karte hain: speed aur wobble. Woh parent ko kehne dete hain "bada Kωn badhata hai lekin ζ ghatata hai" — eternal speed-vs-stability trade-off — plain human terms mein. Note karo ζ=0 (no damping) bilkul imaginary axis par baithta hai — Figure s03 se marginal case: forever ringing.
Kyun yeh tool? Hum aksar steady-state error chahte hain — sab settle hone ke baad hum kitna off hain — forever simulate kiye bina. s se multiply karke aur s→0 let karke (s-plane ka "DC" corner) woh final value seedha transfer function se read ho jaati hai. Isi tarah parent ess=1/(1+G(0))=3/8 kisi bhi time-plot ke bina pata karta hai.