Foundations — MIL-STD-1553 — military avionics bus

5.5.28 · D1 · Coding › Embedded Systems & Real-Time Software › MIL-STD-1553 — military avionics bus

Parent note padhne se pehle, tumhe vocabulary chahiye. Is page par yeh assume kiya gaya hai ki tumhe kuch nahi pata aur har term ek picture se build ki gayi hai. Upar se neeche padho — har idea sirf unhi cheezон ko use karta hai jo uske upar hain.

1. "Bus" kya hota hai?

Figure dekho: har box (radar, nav, weapons) same pair of wires se juda hua hai. Do devices ke beech koi private cable nahi hai — sab ek hi line share karte hain. Isliye bari-bari bolna hi woh poori problem hai jo 1553 ko solve karni hai.

Topic ko yeh kyun chahiye: agar hum wires share na karte, toh 20 boxes ke har pair ke beech alag cable chahiye hoti — yeh $\frac{20\times 19}{2}=190$ cables hoti. Ek shared bus ke liye sirf ek chahiye.

2. Bits, Logic 1 aur Logic 0

1 Mbit/s (ek million bits per second) par, hum har million bits per second mein ek bit bhejte hain, toh:

Topic ko yeh kyun chahiye: parent note mein har timing number (20 $\mu s$ per word, 208 $\mu s$ per message) sirf bit periods ki ginti hai.

3. Voltage, ground, aur "single-ended" measurement

Single-ended ka matlab hai: ek signal wire ko ground ke against measure karo. Parent note mein yeh likha hai:

$V_{\text{signal}}=V_A+\Delta V$

Ise seedhi bhasha mein padho: jo voltage hum dekhte hain ($V_{\text{signal}}$) woh equals hai jo voltage humne bheja ($V_A$) plus jo bhi noise ($\Delta V$) andar aa gayi. Greek letter $\Delta$ ("delta") ka matlab hai "kuch added amount of" — yahan, added noise.

Topic ko yeh kyun chahiye: yeh bura method hai. Yeh samajhna ki yeh kyun fail hota hai, agle idea ko motivate karta hai.

4. Differential signaling — do wires, unhe subtract karo

Figure ko upar se neeche follow karo:

• KYA: dono wires ko same noise bump $\Delta V$ milti hai (grey wiggle).
• SUBTRACT KYUN: receiver $V_{\text{diff}}=V_A-V_B$ compute karta hai.
• KAISA DIKHTA HAI: dono noise bumps perfectly line up ho jaate hain aur subtract karne par gayab ho jaate hain.

$V_{\text{diff}}=(V_A+\Delta V)-(V_B+\Delta V)=V_A-V_B$

Subtraction ke baad dono $\Delta V$ terms ke opposite signs hote hain, toh woh zero mein add ho jaate hain. Hum specifically subtraction isliye use karte hain kyunki yeh woh operation hai jo dono wires par common kisi bhi cheez ko khatam kar deta hai — us shared part ko common-mode noise kehte hain.

1553 mein teen logic cases (har possibility cover karte hue):

Symbol $\pm 1.4V$ ("plus-or-minus") ka matlab hai "$-1.4V$ se $+1.4V$ tak kahin bhi". Ek receiver us dead band mein kuch bhi ignore kar deta hai, toh thodi si bachi khuchi noise kabhi bit samjhi nahi jaati.

Topic ko yeh kyun chahiye: yeh woh physical-layer principle hai. Iske bina, ek jet ka electrical storm har message scramble kar deta.

5. Transformer coupling aur isolation

Do consequences jinhe parent note rely karta hai:

• Galvanic isolation — kyunki koi metal touch nahi karta, ek box par kharab ground bus mein current nahi dump kar sakta.
• Passive failure — agar koi device mar jaaye, uska transformer sirf ek open circuit (ek gap) jaisa lagta hai, na ki ek short (ek dead-end jo poori line jam kar de).

Topic ko yeh kyun chahiye: isliye "ek failed box aircraft crash nahi karana chahiye" physically sach hai.

6. Encoding: bits ko ek self-clocking signal mein badalna

Naive scheme (NRZ) ki problem: agar tum sirf wire ko "1" ke liye high aur "0" ke liye low rakho, toh 100 ones in a row = 100 $\mu s$ mein koi bhi edges nahi. Receiver ki clock poori us stretch mein free drift karti hai.

Manchester II encoding yeh fix karta hai har ek bit ke middle mein ek edge force karke:

• Logic 1 = bit-center par LOW→HIGH transition (upar ki taraf mid-bit edge).
• Logic 0 = bit-center par HIGH→LOW transition (neeche ki taraf mid-bit edge).

Kyunki har bit mein ek mid-bit edge hai, edges ke beech sabse lamba gap hai

$T_{\max }=\frac{T}{2}=\frac{1\mu s}{2}=0.5\mu s$

Hum 2 se isliye divide karte hain kyunki guaranteed edge exactly bit ke beech mein baith ti hai — toh worst case mein, receiver apne agle heartbeat ke liye sirf aadha bit wait karta hai. Poori picture ke liye Manchester Encoding dekho.

Topic ko yeh kyun chahiye: guaranteed edges = no drift = woh deterministic timing jo poora standard promise karta hai.

7. Command / response aur node roles

Parent note mein teen roles:

• Bus Controller (BC) — ek hi master; sirf yahi device conversation shuru karne ki permission rakhta hai.
• Remote Terminal (RT) — ek slave (radar, nav…); sirf tab bolta hai jab BC uska naam le. 31 tak ho sakte hain, har ek ka address 0–31 hota hai.
• Bus Monitor (BM) — chupchap sunता hai, kabhi transmit nahi karta (logging ke liye use hota hai).

Is philosophy ko RS-485 Protocol aur CAN Bus ke "jo bhi kabhị bhi bole" style se, aur ARINC 429 ke master/response style se compare karo.

Topic ko yeh kyun chahiye: command/response hi woh wajah hai kyun 1553 deterministic hai jabki Ethernet nahi.

8. Determinism, latency, aur redundancy

Symbol $p$ yahan ek probability hai: 0 (kabhi nahi) aur 1 (hamesha) ke beech ek number. Agar $p=0.001$, toh $p^2=0.000001$ — ek hazar guna safer bus.

Topic ko yeh kyun chahiye: determinism + redundancy woh do selling points hain jo 1553 ko udaate rakhte hain jabki tez buses zameen par reh jaati hain. Us safety ko certify karna DO-178C Certification ka kaam hai.

Prerequisite map

Left side ka har box is page par define kiya gaya hai; arrows dikhate hain ki kaun si foundation final topic ko feed karti hai. Agar koi bhi left-hand box shaky lage, parent note kholne se pehle woh section dobara padho: MIL-STD-1553.

Equipment checklist

Self-test: right side cover karo aur har sawaal ka jawab do. Agar nahi de sako, toh us section par jaao jiska naam likha hai.