5.5.28 · D1Embedded Systems & Real-Time Software

Foundations — MIL-STD-1553 — military avionics bus

2,076 words9 min readBack to topic

Before you can read the parent note, you need the vocabulary. This page assumes you know nothing and builds each term from a picture. Read top to bottom — each idea uses only the ones above it.


1. What is a "bus"?

Figure — MIL-STD-1553 — military avionics bus

Look at the figure: every box (radar, nav, weapons) hangs off the same pair of wires. There is no private cable between two devices — they all share one line. That is why taking turns is the whole problem 1553 must solve.

Why the topic needs it: if we didn't share wires, we'd need a separate cable between every pair of 20 boxes — that's cables. A shared bus needs one.


2. Bits, Logic 1 and Logic 0

At 1 Mbit/s (one million bits per second), we send one bit every millionth of a second, so:

Why the topic needs it: every timing number in the parent note (20 per word, 208 per message) is just counting bit periods.


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

Single-ended means: measure one signal wire against ground. The parent note writes this as

Read this in plain words: the voltage we see () equals the voltage we sent () plus whatever noise () leaked in. The Greek letter ("delta") means "a small added amount of" — here, the added noise.

Why the topic needs it: this is the bad method. Understanding why it fails motivates the next idea.


4. Differential signaling — two wires, subtract them

Figure — MIL-STD-1553 — military avionics bus

Follow the figure top to bottom:

  • WHAT: both wires get the same noise bump (grey wiggle).
  • WHY subtract: the receiver computes .
  • WHAT IT LOOKS LIKE: the two noise bumps line up perfectly and vanish when subtracted.

The two terms have opposite signs after subtraction, so they add to zero. We use subtraction specifically because it is the operation that kills anything common to both wires — that shared part is called common-mode noise.

The three logic cases in 1553 (covering every possibility):

Meaning
Logic 1
Logic 0
near (within ) undefined / no valid bit

The symbol ("plus-or-minus") means "anywhere from to ". A receiver ignores anything in that dead band, so tiny leftover noise never gets mistaken for a bit.

Why the topic needs it: this is the physical-layer principle. Without it, a jet's electrical storm would scramble every message.


5. Transformer coupling and isolation

Two consequences the parent note relies on:

  • Galvanic isolation — since no metal touches, a bad ground on one box can't dump current into the bus.
  • Passive failure — if a device dies, its transformer just looks like an open circuit (a gap), not a short (a dead-end that jams the whole line).

Why the topic needs it: this is why "one failed box shouldn't crash the aircraft" is physically true.


6. Encoding: turning bits into a self-clocking signal

The problem with the naive scheme (NRZ): if you just hold the wire high for a "1" and low for a "0", then 100 ones in a row = 100 with no edges at all. The receiver's clock drifts free for that whole stretch.

Manchester II encoding fixes this by forcing an edge in the middle of every single bit:

Figure — MIL-STD-1553 — military avionics bus
  • Logic 1 = LOW→HIGH transition at bit-center (upward mid-bit edge).
  • Logic 0 = HIGH→LOW transition at bit-center (downward mid-bit edge).

Because every bit has a mid-bit edge, the longest gap between edges is

We divide by 2 because the guaranteed edge sits exactly halfway through the bit — so worst case, the receiver waits only half a bit for its next heartbeat. See Manchester Encoding for the full picture.

Why the topic needs it: guaranteed edges = no drift = the deterministic timing the whole standard promises.


7. Command / response and the node roles

The three roles in the parent note:

  • Bus Controller (BC) — the single master; the only device allowed to start a conversation.
  • Remote Terminal (RT) — a slave (radar, nav…); speaks only when the BC names it. There can be up to 31, each with an address 0–31.
  • Bus Monitor (BM) — listens silently, never transmits (used for logging).

Compare this philosophy with the "anyone talks anytime" style of RS-485 Protocol and CAN Bus, and the master/response style of ARINC 429.

Why the topic needs it: command/response is the reason 1553 is deterministic where Ethernet is not.


8. Determinism, latency, and redundancy

The symbol here is a probability: a number between 0 (never) and 1 (always). If , then — a thousand-times-safer bus.

Why the topic needs it: determinism + redundancy are the two selling points that keep 1553 flying while faster buses stay grounded. Certifying that safety is the job of DO-178C Certification.


Prerequisite map

Bits and bit period T

Manchester encoding

Voltage and ground

Differential signaling

Physical layer noise immunity

Transformer coupling

Shared bus idea

BC RT BM roles

Command response protocol

Determinism and latency

Probability multiply rule

Dual redundancy

MIL-STD-1553

Each box on the left is something this page defined; the arrows show which foundation feeds the final topic. If any left-hand box feels shaky, re-read that section before opening the parent note: MIL-STD-1553.


Equipment checklist

Self-test: cover the right side and answer each. If you can't, jump to the section named.

What does a "bus" physically mean here?
One shared pair of wires that all devices take turns talking over.
Why is at 1 Mbit/s?
Because ; period is the reciprocal of rate.
What is ?
A small amount of added noise voltage that lands on the wire.
Why does subtracting two wires kill noise?
Noise is common to both wires, so — the terms cancel.
What are the three differential voltage cases?
= logic 1, = logic 0, within = undefined dead band.
Why transformer coupling instead of a direct wire?
Galvanic isolation plus a passive open-circuit failure mode, so a dead box can't jam the bus.
What problem does Manchester II solve, and how?
Clock drift from long runs of same bits; it forces a mid-bit edge every bit so the max gap without an edge is .
Who is allowed to start a conversation on the bus?
Only the Bus Controller (BC); RTs speak only when addressed — so zero collisions.
What is the difference between address, subaddress, and word count?
Address = which RT (0–31), subaddress = which channel inside it (0–31), word count = how many 16-bit words follow (1–32).
Why does a second bus give failure probability?
Both buses must fail together (independent AND), and independent probabilities multiply: .
What makes a system "deterministic"?
It has a guaranteed maximum latency that is never exceeded.