4.2 MIL-STD-1553B Military Avionics Data Bus

4.2 MIL-STD-1553B Military Avionics Data Bus

Current Appendix I topic 5.4 is the broad heading Data buses at level 2 for B1 and B2/B2L. The pre-12 June 2024 detailed description referred to ARINC and other specifications; MIL-STD-1553B is a representative command/response bus used here to develop that historical study scope. It is a United States military standard (1553B superseded 1553A) used on fighters, helicopters, tankers and military transports, and on some military-derived civil types. It is not the Airbus A320 429 backbone and not the 777 DATAC bus. OpenExamPrep publishes this material as independent exam preparation; it is not an EASA document and does not claim official approval or partnership.

The Module 5 paper remains a three-option multiple-choice examination (about 75 seconds per question, 75% pass, no negative marking). Fees vary by NAA and Part-147 organisation; do not treat any euro figure as an official EASA Module 5 fee. Level 2 means you can name the three terminal roles, the dual-redundant twisted shielded pair, the 1 Mbit/s Manchester teaching rate, the 20-bit word, and why a remote terminal stays silent until commanded.

---

Command/response, not autonomous access

ARINC 629 terminals transmit when their unique terminal gap expires. MIL-STD-1553B does the opposite: only the bus controller (BC) may start a transfer. Every exchange is command/response. The BC emits a command word; the addressed remote terminal (RT) responds with a status word and, if told to, with data words. If the BC is silent, the bus is silent. That single-master design makes timing deterministic and makes a failed BC a system-level event — which is why military architectures provide a standby BC and dual media.

Time-division multiplexing shares one pair among many users, but the multiplex is scheduled by the BC, not by CSMA timers and not by an Ethernet switch.

---

Three terminal roles

Addressing uses 5 bits: unique RT addresses 0 to 30, and address 31 as broadcast. A broadcast command is received by all RTs; they do not return status on a true broadcast (otherwise 31 status words would collide). An LRU may contain both a BC function and an RT function, but only one BC is active on a given bus at a time. Dynamic bus control — passing mastership to another terminal — exists in the standard; many installations never enable it.

The bus monitor is the role you occupy with a 1553 analyser in monitor mode. If the analyser is incorrectly set to BC or RT, you have injected a second master or a duplicate address — both are serious protocol faults.

---

Physical layer: dual-redundant twisted shielded pair

The medium is a twisted shielded pair, transformer-coupled in almost every airframe installation, and duplicated as Bus A and Bus B. Characteristic impedance is typically in the 70 Ω to 85 Ω band; 78 Ω is a common teaching and terminator value, not an EASA-published constant. Both ends of each bus are terminated in that characteristic resistance.

Two stub methods appear in the standard:

Transformer coupling lets a stub be added or removed without opening the backbone as a series voltage break, and it limits how hard a stub short can collapse the bus. Direct coupling is electrically simpler but stub length is tightly limited. Follow the wiring diagram: mixing a long direct stub onto a transformer-coupled bus is a classic installation defect.

Typical teaching bit rate is 1 Mbit/s. Encoding is Manchester II biphase: a mid-bit transition represents every bit, so the code is self-clocking and has no DC component that would saturate the isolation transformers. A logic 1 is a high-to-low transition at mid-bit in the usual 1553 teaching polarity; a logic 0 is the opposite. There is no ARINC 429 NULL rest state. If an oscilloscope shows three voltage-mode RZ levels, you are on the wrong family.

---

The 20-bit word

Every 1553 word occupies 20 bit-times, therefore 20 μs at 1 Mbit/s:

• 3 bit-times of sync (an invalid Manchester pattern that cannot appear in data). Command and status words use one sync polarity (1.5 bit-times high, then 1.5 low in the usual drawing); data words use the opposite sync. Receivers distinguish command/status from data by that sync, not by a 429 label field.
• 16 information bits.
• 1 odd parity bit over those 16 bits.

Do not confuse this 20-bit military word with the ARINC 429 32-bit DITS word, and do not assign 429 SDI/SSM bit numbers to 1553.

Command word (16 information bits)

Worked example. Command: RT address 14, T/R = 0, subaddress 3, word count 10. The BC is telling remote terminal 14 to receive ten data words into subaddress 3. On the wire you then see the command word, a short response gap, the RT 14 status word, and ten data words (BC-to-RT). If T/R had been 1, RT 14 would transmit ten data words from subaddress 3 (RT-to-BC).

Status word

The RT replies with its own address plus flag bits that Module 5 expects you to recognise by function: message error, service request, broadcast command received, busy, subsystem flag, dynamic bus control acceptance, and terminal flag. Instrumentation and reserved bits exist in the standard. A message-error bit tells the BC the RT saw a problem (parity, word count, or encoding). Busy means the subsystem cannot handle the data this time. Terminal flag and subsystem flag feed BITE.

Data word

Sixteen bits of payload plus odd parity. Meaning is defined by the subsystem interface control document, not by a universal 429-style octal label.

---

Message types and timing

The BC builds four families of transfer that appear in teaching:

1. BC-to-RT: command (receive), then data words from the BC, then RT status.
2. RT-to-BC: command (transmit), then RT status and data.
3. RT-to-RT: two commands (receive RT then transmit RT), then status and data from the transmitter, then status from the receiver.
4. Mode commands: subaddress 0 or 31; used for transmitter shutdown, override, reset remote terminal, initiate self-test, and related control — the BITE and bus-management toolbox.

Broadcast variants use RT address 31.

Intermessage gap is at least 4 μs in typical teaching. RT response time is a window of about 4 μs to 12 μs after the command. A late or missing status is a timeout; the BC may retry on the same bus or switch to the redundant bus according to the system design.

Worked timing. A BC-to-RT message of ten data words: command 20 μs + response idle (take 8 μs as a mid-window teaching value) + status 20 μs + ten data words 200 μs ≈ 248 μs on the wire, plus the next intermessage gap. At 1 Mbit/s that is still a small fraction of a 20 ms control frame, which is why 1553 can multiplex many subsystems on one pair.

---

Why Module 5 includes 1553B

Topic 5.4 is not an ARINC-only clause. Other specifications includes the military command/response family that certifying staff meet on military and mixed fleets, in type-training excerpts, and as the conceptual opposite of both 429 simplex and 629 autonomous CSMA. You are not required to quote unpublished DoD procurement prices or any EASA fee. You are required to know who talks, on what wire, at what rate, in what word length, and that a bus monitor does not transmit.

Maintenance first questions: is the BC alive, is the RT address unique, are Bus A and Bus B both terminated, is the stub transformer-coupled as drawn, and is your analyser in monitor mode? Duplicate RT addresses and a second live BC are the protocol equivalents of two 429 transmitters on one pair — except here the victim is the whole multiplex, not a single broadcast parameter.