Naval aviation
MIL-STD-1553 data bus explained
MIL-STD-1553 defines a 1 Mbit/s command-response data bus with a bus controller, remote terminals, and rules for dual standby redundancy.
Nov 10, 20266 min read5 sources
Why it matters
Reading the bus roles and exact standard revision helps an integration team specify compatible aircraft interfaces.
The short version
- 1MIL-STD-1553 uses 1 Mbit/s command-response transfers directed by a bus controller.
- 2The bus supports up to 31 individually addressed remote terminals; address 31 is reserved for broadcast.
- 3MIL-STD-1553C is the active revision; SAE AS15531A describes equivalence to revision B with Notice 2.
MIL-STD-1553 defines a 1 Mbit/s command-response data bus used to connect electronic subsystems. It specifies the wiring interface, electrical signals, message formats, and rules for exchanging data. A bus controller directs traffic between remote terminals (MIL-STD-1553C).
The familiar arrangement is dual-redundant: an active path and a standby path. The standard supports up to 31 individually addressed remote terminals, plus the controller and a bus-monitor function.
1553 bus explained
A 1553 bus lets several subsystems share a communication path under central control. Time division means their transmissions occupy different times on that path.
The standard covers both the physical interface and the conversation. It defines the cable, terminal electronics, signals, and information flow. It leaves application-specific options, such as redundancy and traffic patterns, to the system designer (MIL-STD-1553C, foreword).
| Feature | Meaning |
|---|---|
| 1 Mbit/s | The transmission bit rate, not the useful application-data rate |
| Command-response | The controller initiates transfers; addressed terminals respond |
| Half-duplex | Transmission goes in 1 direction at a time |
| Shared bus | Subsystems use a common communication path |
| Dual standby redundancy | An alternate bus provides another path when required |
The rate and operating rules appear in MIL-STD-1553C. Command words, status words, synchronization, and gaps consume transmission time. Allow for that overhead when estimating useful throughput (MIL-STD-1553C, transmission method).
For a different question, communication between aircraft and other platforms, see Link 16 explained.
Bus controller, remote terminal, and bus monitor
The bus controller schedules the exchange; remote terminals carry it out; a bus monitor observes it.
| Role | What it does |
|---|---|
| Bus controller (BC) | Issues commands, participates in transfers, receives responses, and monitors system status |
| Remote terminal (RT) | Receives or transmits data when commanded |
| Bus monitor (BM) | Receives traffic and extracts selected information |
Only 1 terminal actively controls a bus at a time. A controller can be a separate terminal or part of another subsystem (MIL-STD-1553C, terminal operation).
A monitor does not take control simply because it sees the traffic. The standard permits monitoring for flight-test recording, maintenance recording, mission analysis, or backup-controller preparation. An addressed device combining roles still has to follow the applicable terminal rules.
The National Aeronautics and Space Administration (NASA) illustrates these roles with an F-16 network. That example connects aircraft subsystems to redundant bus lines (NASA flight-test instrumentation memorandum).
When reading a block diagram, label the roles before following the wires. A box's mission function and its bus role answer different questions.
Why are there only 31 remote terminals?
The address field has 5 bits, but address 31 is reserved for broadcast. Individually addressed terminals use addresses 0 through 30 (MIL-STD-1553C, remote terminal address).
That gives up to 31 unique RT addresses. It does not mean 31 application messages or 31 data items. Commands also contain a subaddress or mode field.
Broadcast sends a permitted command to the common address. Receiving terminals suppress their normal status responses, avoiding simultaneous replies. The standard therefore warns that broadcast lacks the usual positive acknowledgment (MIL-STD-1553C, broadcast operation).
For an integration review, make an address table. Record each terminal's assigned address, supported subaddresses, and implemented mode commands. Keep the broadcast address separate from ordinary equipment addresses.
What are the 1553 word types?
The 3 word types are command, data, and status. Each occupies 20 bit times: a synchronization waveform, 16 information bits, and an odd-parity bit (NASA flight-test instrumentation memorandum).
| Word | Main contents | Purpose |
|---|---|---|
| Command | RT address, transmit/receive direction, subaddress or mode, and word count or mode code | Tells a terminal what exchange to perform |
| Data | Application information | Carries the payload |
| Status | RT address and status flags | Reports the terminal's response condition |
These fields have defined positions. A command's transmit/receive bit describes the remote terminal's action. A transmit command tells the RT to send; a receive command tells it to accept data (MIL-STD-1553C, word formats).
The standard supports controller-to-terminal, terminal-to-controller, and terminal-to-terminal exchanges. Even terminal-to-terminal traffic begins with controller commands. The controller directs the receiving and transmitting terminals.
For normal data transfers, the count field allows up to 32 data words in a message block. A zero value in that field represents 32 words. Mode commands use the field differently, so a decoder must identify the command format before interpreting it.
To read a captured exchange:
- Identify the command and addressed RT.
- Read the requested direction and subaddress or mode.
- Match the expected data words to the command.
- Examine the status response and reported errors.
What does dual-redundant mean?
Dual standby redundancy provides alternate bus paths, with only 1 active at a time under the normal rule. The standard also defines how a valid command on the other bus supersedes an ongoing command (MIL-STD-1553C, redundant data bus requirements).
The distinction matters: redundant paths do not double normal useful bandwidth. They support continued communication through an alternate path.
Redundancy is an application design decision under the general standard. Appendix A adds service requirements for dual standby applications. Air Force internal avionics must use dual standby redundancy unless critical requirements demand more.
Review the wiring and failure response together. Ask which controller selects the alternate path and how the design handles a failed terminal.
MIL-STD-1553B, revision C, and notices
MIL-STD-1553C, dated February 28, 2018, is the active revision. The Acquisition Streamlining and Standardization Information System (ASSIST) lists it as current. The record lists no later C notice (ASSIST revision history).
| Document part | Date | Listing in ASSIST |
|---|---|---|
| Revision B | September 21, 1978 | Base revision |
| B Notice 2 | September 8, 1986 | Change notice |
| B Notice 3 | January 31, 1993 | Validation |
| B Notice 4 | January 15, 1996 | Change notice |
| Revision C | February 28, 2018 | Current revision |
ASSIST also archives B Notice 1, interim notices 5 and 6, and Notice 7 labeled cancellation. Historical entries do not change the record's current active status.
SAE International's AS15531A is a separate aerospace standard. The publisher lists it as stabilized on March 21, 2017. The scope describes functional equivalence to MIL-STD-1553B with Notice 2 (SAE AS15531A).
Record the exact document and notice baseline in an interface review. A reference to AS15531A, B with notices, or C should remain identifiable throughout the review.
Where is MIL-STD-1553 used?
Government documents show applications in aircraft avionics, aircraft-store interfaces, and spacecraft payload systems.
| Application | Public example |
|---|---|
| Aircraft subsystems | NASA's F-16 network example |
| Aircraft-store communication | MIL-STD-1760F defines redundant 1553 interfaces for digital information, store control, and status |
| Space-station payloads | NASA describes 1553B carrying payload commands, health, status, safety, and ancillary data |
MIL-STD-1760E specifically required MIL-STD-1553B Notice 4. MIL-STD-1760F, dated September 9, 2025, now cites MIL-STD-1553C (ASSIST MIL-STD-1760 record). Check which revision of an application document the interface baseline invokes, because each revision can name a different 1553 baseline.
For aircraft changes, follow the applicable engineering approval process alongside the interface review. See Naval Air Systems Command (NAVAIR) flight clearances for that separate question.
What to do next
- Identify the exact standard revision and notices in the interface baseline.
- Label the BC, RTs, and monitor on the system diagram.
- Check unique RT addresses and separate broadcast behavior.
- Read command, data, and status words as parts of a complete exchange.
- Review redundancy, traffic timing, and application-data definitions together.
Azcuna's ELLMENT, the E-2D Large Language Model Entity, was proposed to NAVAIR PMA-231 under Navy SBIR Phase I topic DON26BZ01-NV010. The prototype, built at private expense on publicly available doctrine, answers with a page-level citation and refuses when the documents do not support an answer. The proposal has been submitted.
Questions people ask
What is MIL-STD-1553?
MIL-STD-1553 is a military interface standard for a digital command-response data bus. It defines electrical characteristics, terminal behavior, and message formats. MIL-STD-1553C specifies a transmission rate of 1 Mbit/s, with a bus controller directing exchanges among remote terminals.
How many remote terminals can a 1553 bus have?
MIL-STD-1553C provides 31 unique remote-terminal addresses, from 0 through 30. The remaining address, 31, is reserved for broadcast. That limit concerns individually addressed terminals, not the number of messages or application data items a terminal can exchange.
What is the difference between a bus controller and a remote terminal?
Under MIL-STD-1553C, the bus controller initiates transfers and monitors responses. A remote terminal sends or receives data when commanded. Only 1 terminal actively controls a bus at a time. A bus monitor observes traffic for permitted monitoring purposes.
Is MIL-STD-1553B still the latest revision?
No. ASSIST lists MIL-STD-1553C, dated February 28, 2018, as active. Revision B and its notices remain in the revision history. Older application documents, such as MIL-STD-1760E, specifically required a B baseline, so retain the exact revision and notices specified for the interface being reviewed.
Sources
- 1MIL-STD-1553C, Digital Time Division Command/Response Multiplex Data Bus (ASSIST-QuickSearch document details and revision history) · Defense Logistics Agency
- 2AS15531A: Digital Time Division Command/Response Multiplex Data Bus · SAE International
- 3Digital Signal Conditioning for Flight Test Instrumentation · National Aeronautics and Space Administration
- 4MIL-STD-1760F, Aircraft/Store Electrical Interconnection System · Department of Defense
- 5ISS Science Payload Command & Data Handling · NASA Johnson Space Center
Where this shows up in our work
- ELLMENT, the offline LLM for E-2D crews answers a crew's question from the aircraft's own manuals and cites the page, with no network.
- TRACE, the offline S1000D and IETM viewer opens S1000D, MIL-STD-3001 and PDF technical manuals on a tablet with every marking intact.