AIT MIL-STD-1553 Protocol Tutorial

1 September Rev AProtocol TutorialMIL-STD-15533703 N. 200th Street,Omaha, NE 68022 Tel: : Rev. AProtocol TutorialMIL-STD- 1553 Doc No. 4020F00 ASeptember 2010 Omaha Office3703 N. 200th Street,Omaha, NE 68022 Tel: : Office2689 Commons Boulevard,Beavercreek, OH 45431 Tel: : ext. 202 Sales and Support Staff located in 19 Statesfind the closest to you MIL-STD- 1553 Protocol TutorialIITable of ContentsSection This Manual .. Documents Section History and Application .. Bus Components .. Bus Controller (BC) .. Remote Terminal (RT) .. Bus Monitor (BM) .. Cabling .. Coupling .. Bus Topology .. Test Procedures .. Developmental Testing .. Design Verification .. Production Testing .. Systems Integration Testing .. Filed/Operational Testing Section Specification Scope.

2 Scope .. Application .. Referenced Documents .. Issue of Document .. Definitions AIT MIL-STD- 1553 Protocol Bit .. Bit Rate .. Pulse Code Modulation (PCM) .. Time Division Multiplexing (TDM) .. Half Duplex .. Word .. Message .. Subsystem .. Data Bus .. Terminal .. Bus Controller (BC) .. Bus Monitor (BM) .. Remote terminal (RT) .. Asynchronous Operation .. Dynamic Bus Control .. Command/Response .. Redundant Data Bus .. Broadcast .. Mode Code .. General Requirements .. Test and Operating Requirements .. Data Bus Operation .. Characteristics .. Data Bit Transmission Data Transmission Bit Word SizeAIT MIL-STD- 1553 Protocol Word Command Remote Terminal Data Word Count/Mode Table 3-I Assigned Mode Codes Optional Dynamic Bus Synchronize (without a data word).

3 Transmit Status Initiate Self Transmitter Override Transmitter Inhibit Terminal Flag (T/F) Override Inhibit T/F Reset Remote Reserved Mode Codes (01001 to 01111).. Transmit Vector Synchronize (with data word).. Transmit Last Command Transmit Built-in-Test (BIT) Selected Transmitter Override Selected Transmitter Reserved Mode Codes (10110 to 11111).. Data DataAIT MIL-STD- 1553 Protocol Status RT Message Error Instrumentation Service Request Reserved Status Broadcast Command Received Busy Subsystem Flag Dynamic Bus Control Acceptance Terminal Flag Parity Status Word Message Bus Controller to Remote Terminal Remote Terminal to Bus Controller Remote Terminal to Remote Terminal Mode Command without Data Mode Command with Data Word (Transmit).

4 Mode Command with Data Word (Receive).. Optional Broadcast Bus Controller to Remote Terminal(s) Transfer(Broadcast).. Remote Terminal to Remote Terminal(s) Transfer(Broadcast).. Mode Command without Data Word (Broadcast).. Mode Command with Data Word (Broadcast).. Intermessage Response TimeAIT MIL-STD- 1553 Protocol Minimum No-Response Terminal Operation .. Common Word Transmission Terminal Bus Controller Remote Superseding Valid Invalid Illegal Valid Data Invalid Data Bus Monitor Hardware Characteristics .. Data Bus Characteristic Cable Cable Cable Stub Transformer Coupled Coupling Transformer Input Transformer Waveform Transformer Common Mode Fault Cable Stub Voltage RequirementsAIT MIL-STD- 1553 Protocol Direct Coupled Fault Cable Stub Voltage Wiring and Cabling for Terminal Terminals with Transformer Coupled Terminal Output Output Output Output Output Terminal Input Input Waveform Common Mode Input Noise Terminal with Direct Coupled Terminal Output Output Output Output Output Terminal

5 Input Input Waveform Common Mode Input Noise Redundant Data Bus Electrical IsolationAIT MIL-STD- 1553 Protocol Single Event Dual Standby Redundant Data Data Bus Superceding Valid Commands**.. 10. General .. Redundancy .. Bus Controller .. Multiplex Selection Criteria .. High Reliability Requirements .. Stubbing .. Use of Broadcast Option .. **20. Referenced **30. General ** Option Selection .. ** Application .. ** Unique Address ( ) .. ** Mode Codes ( ) .. ** Subaddress/Mode ( ) .. ** Required Mode Codes ( ) .. ** Remote Terminal Required Mode Codes .. ** Bus Controller Required Mode Codes .. ** Reset Remote Terminal ( ).

6 ** Initiate RT Self Test ( ) .. ** Status Word Bits ( ) .. ** Information Content .. ** Status Bit Requirement ( ) .. ** Busy Bit ( ) .. ** Broadcast ( ) .. ** Data Wrap-Around ( ) AIT MIL-STD- 1553 Protocol ** Message Formats ( ) .. ** RT to RT Validation ( ) .. ** Electrical Characteristics ( ) .. ** Cable Shielding ( ) .. ** Shielding ( ) .. ** Connector Polarity .. ** Characteristic Impedance ( ) .. ** Stub Coupling ( ) .. ** Power On/Off Noise Section and AbbreviationsSection - Notices Applied to MIL-STD- 1553 BAIT MIL-STD- 1553 Protocol This ManualThis manual was developed to provide a general overview of MIL-STD- 1553 itsspecifications and applications. The first chapter provides a discussion of MIL-STD- 1553 , its history, application andoperational overview.

7 Included is a reference to MIL-STD-1760C as it applies to WeaponStores Interface and its relationship to MIL-STD-1553B. The second chapter includes a complete annotated version of the MIL-STD- 1553 Bspecification and an interpretation of the specification specification is on the topof each page and the Avionics Interface Technologies (AIT) interpretation is located on thelower portion of the page. Notices 1 though 4, addendum's to the MIL-STD- 1553 Bspecification, are summarized at the end of this manual, and have been incorporated into thespecification discussed within this document. AIT provides Commercial-Off-The-Shelf (COTS) products to design, produce, integrate, testand troubleshoot all systems and capabilities mentioned in this MIL-STD- 1553 Tutorial aswell as for ARINC 429, MIL-STD-1760, MIL-STD-1760e, Fibre Channel, and ARINC664applications.

8 Supported hardware platforms include PCI, PCIe, cPCI, VME, VXI, PXI, PMC,XMC, and USB. AIT software products also support full Remote Terminal production testing, full bus analysisand complete system emulation and test capabilities per MIL-STD-1553B specifications. For detailed information at the AIT website, visit or email AIT MIL-STD- 1553 Protocol DocumentsThe following documents shall be considered to be a part of this document to the extentspecified Documents MIL-STD-464, Electromagnetic Environmental Effects Requirements for Systems, March18, 1997 MIL-HDBK-1553A, Multiplex Application Handbook, March 23, 1995 MIL-STD-1553B, Department of Defense Interface Standard for Digital Time DivisionCommand/Response Multiplex Data Bus, Notice 1-4, January 1996 MIL-STD-1760C, Interface Standard for Aircraft/Store Electrical Interconnection System,March 2, 1999 SAE AS4111, Validation Test Plan for the Digital Time Division Command/ResponseMultiplex Data Bus Remote Terminals, October 1998 SAE AS4112.

9 Production Test Plan for the Digital Time Division Command/ResponseMultiplex Data Bus Remote Terminals, January 1989 SAE AS4113, Validation Test Plan for the Digital Time Division Command/ResponseMultiplex Data Bus Controllers, January 1989 SAE AS4114, Production Test Plan for the Time Division Command/Response MultiplexData Bus Controllers, January 1989 SAE AS4115, Test Plan for the Digital Time Division Command/Response Multiplex DataBus System, January 1989 SAE AS4116, Test Plan for the Digital Time Division Command/Response Multiplex DataBus Bus Monitors, September 1990 SAE AS4117, Test Plan for the Digital Time Division Command/Response Multiplex DataBus Couplers, Terminators, and Data Bus Cables, March 1991 AIT MIL-STD- 1553 Protocol Tutorial32 MIL-STD- 1553 OverviewMIL-STD-1553B is the military specification defining a Digital Time DivisionCommand/Response Multiplexed Data Bus.

10 The 1553 databus is a dual-redundant,bidirectional, Manchester II encoded databus with a high bit error reliability. All buscommunications are controlled and initiated by a main bus controller. Remote terminaldevices attached to the bus respond to controller commands. MIL-STD-1553B definesspecifications for terminal device operation and coupling, word structure and format,messaging Protocol and electrical characteristics. AIT MIL-STD- 1553 Protocol History and ApplicationMIL-STD-1553B was developed from the growing complexity of integrated avionics systemsand the subsequent increase in the number of discrete interconnects between terminal devices. Direct point-to-point wiring became complex, expensive and bulky, requiring definition of amultiplex data bus standard. The first draft of a standard in 1968 by the Aerospace Branch ofthe Society of Automotive Engineers (SAE) laid the foundation for the US Air Force sadoption of MIL-STD- 1553 in 1973.