S.K.
CHAUDHARY EDUCATIONAL TRUST’S
SHANKARA INSTITUTE OF TECHNOLOGY
KUKAS, JAIPUR
DEPARTMENT OF ELECTRONICS AND COMMUNICATION
SESSION (2011-2012)
A SEMINAR REPORT
SUBMITTED IN PARTIAL FULFILLMENT FOR AWARD OF DEGREE OF
BACHELOR OF TECHNOLOGY
RAJASTHAN TECHNICAL UNIVERSITY (KOTA), JAIPUR
MILITARY STANDARD 1553
SUBMITTED TO: - SUBMITTED BY:-
ASHUTOSH MISHRA CHAVDA PARAS (09ESIEC201)
(H.O.D.) B.TECH.(VIII SEM)
ECE DEPARTMENT
S.K.Chaudhary Educational Trust’s
SHANKARA INSTITUTE OF TECHNOLOGY
Kukas-Jaipur
DEPARTMENT OF ELECTRONICS AND COMMUNICATION
CERTIFICATE
This is to certify that the seminar report entitled “ MILITARY STANDARD 1553”
has been submitted CHAVDA PARAS , B.Tech final year (ECE) whose Roll NO. is
09ESIEC201, in partial fulfillment for the award of Bachelor of Technology Degree
of Rajasthan Technical University, Kota in the session 2011-2012.It has been found
to be satisfactory and here by approved for the submission.
Date:-
Place:-
Mr. RAJESH KANWADIA Mr. ASHUTOSH MISHRA
Ms. SHWETA AGARWAL H.O.D
(Seminar incharge) (ECE Department)
PREFACE
The 1553 Standard contains several sections and describes the method of communication,
the data bus requirements and the electrical interface requirements for subsystems
connected to the data bus. Although there are some very specific requirements, there are also
many vague requirements and many options to give the designers flexibility in their
applications. MIL-STD-1553 IS A STANDARD, NOT A SPECIFICATION. Invoking MIL-
STD-1553 by a simple reference is not sufficient or adequate. There needs to be a multiplex
system specification written around MIL-STD-1553 and the specific system requirements.
There are three types of terminals in 1553: the bus controller, remote terminal and bus monitor.
The bus controller is the master device and there is only one terminal operating as bus controller
at any one point in time. The bus controller initiates all information transfers on the data bus.
The standard requires information transfers between terminals to follow a command/response
format. The bus controller sends commands to the remote terminals to tell them what to do. The
bus controller can be a separate subsystem or just a portion of a subsystem.
ACKNOWLEDGEMENT
At the outset, I thank God almighty for making our endeavor a success. I
also express our gratitude to Mr. ASUTHOSH MISHRA. Head of the
Department for providing me with adequate facilities, ways and means by which
we were able to complete this seminar.
I express my sincere gratitude to my seminar Guide Mr. RAJESH
KANWADIA AND MISS SWETA AGRAWAL for his constant support and
valuable suggestions without which the successful completion of this seminar
would not have been possible.
I express my immense pleasure and thanks to all the teachers and staff of the
Department of electronics and communication engineering, for their cooperation
and support.
Last but not the least, I thank all others, and especially our classmates who in
one way or another helped me in the successful completion of this work.
A special word of thanks goes to our department, whose help and guidance
made this effort a bright success.
Yours Sincerely,
CHAVDA PARAS(09ESIEC201)
CONTENTS
1. Historical Development Of Mil-Std-1553
2. What Is Mil-Std-1553?
3. Functional Elements Of 1553
4. 1553 Communication
5. 1553b Hardware Components
6. Interface Description
7. Definitions
8. General Requirements
9. Characteristics
10.Conclusion
11.Bibilography
1) Historical Development of MIL-STD-1553
After the end of World War II, it was clear that future aircraft would be carrying too many
subsystems to individually wire one subsystem to another. It was necessary to reduce the size
and weight of the subsystems and the wiring that connected them, to eliminate duplication of
subsystems, to increase system performance and reliability and to reduce costs.
A common data bus that all the subsystems could be connected to was needed to solve these
problems. In 1968, the Society of Automotive Engineers (SAE) formed a sub-committee of
government and industry personnel to develop a digital time division multiplex data bus.
After five years, in 1973, MIL-STD-1553 was published as an Air Force standard. The Standard
was revised twice; MIL-STD-1553A was published in 1975 as a tri-service standard and MIL-
STD-1553B was released in 1978 as a tri-service/NATO standard. Since then, two notices
incorporating further changes and clarifications were issued: Notice 1 in 1980 and Notice 2 in
1986. Also in 1986, the RT Validation Test Plan was published to provide a standard set of tests
for remote terminals.
2) What is MIL-STD-1553?
MIL-STD-1553 is a military standard that specifies the requirements for a digital
command/response time division multiplex data bus for integration of aircraft subsystems.
Simply stated, digital command / response time division multiplexing is the transmission of
information between subsystems over a pair of wires with different subsystems transmitting at
different points in time in response to commands.
The 1553 Standard contains several sections and describes the method of communication,
the data bus requirements and the electrical interface requirements for subsystems
connected to the data bus. Although there are some very specific requirements, there are also
many vague requirements and many options to give the designers flexibility in their
applications. MIL-STD-1553 IS A STANDARD, NOT A SPECIFICATION. Invoking MIL-
STD-1553 by a simple reference is not sufficient or adequate. There needs to be a multiplex
system specification written around MIL-STD-1553 and the specific system requirements.
3) Functional Elements of 1553
The functional elements of 1553 consist of the data bus and terminals. The Standard defines the
data bus to be a single path between the bus controller and all remote terminals. This includes the
twisted, shielded pair cable, terminators and couplers. Most systems today use two buses
operating standby redundant bus, meaning that one bus operates as the data path and the other
serves as the back-up.
There are three types of terminals in 1553: the bus controller, remote terminal and bus monitor.
The bus controller is the master device and there is only one terminal operating as bus controller
at any one point in time. The bus controller initiates all information transfers on the data bus.
The standard requires information transfers between terminals to follow a command/response
format. The bus controller sends commands to the remote terminals to tell them what to do. The
bus controller can be a separate subsystem or just a portion of a subsystem.
The remote terminal is the device that connects the data bus to the sub-system and transfers data
in and out of the subsystem in response to the bus controller. The remote terminal can be a
separate subsystem or just a portion of the subsystem. The Standard allows for up to 31 remote
terminals in the system.
The bus monitor is optional and is a passive device that examines all data that is on the bus. It
can record all data or selected data for off-line applications such as flight-test recording,
maintenance or mission analysis. The data could also be used as an information source for a
back-up bus controller.
4) 1553 Communication
1553 communication uses three word types: command, status and data. All words are 20 bits
long. Three bits are used for the word sync, 16 bits are used for information and 1 bit for parity.
The word sync differentiates data words from command and status words. Command words are
only transmitted by the bus controller. They direct a remote terminal to transmit data, receive
data or perform a specified operation. The status word is only transmitted by a remote terminal
and provides general information on the state of the remote terminal. Data words may be
transmitted by either the bus controller or remote terminals.
Information is transferred in packets or messages with a maximum of 32 data words per
message. Messages are defined for bus controller to remote terminal transfers, remote
terminal to bus controller transfers, and remote terminal to remote terminal transfers. In
addition, mode messages are defined for managing the bus system and error recovery
The digital data bus MILSTD 1553B was designed in early 1970's to replace analog point to
point wire bundles between electronic instrumentations. The MILSTD 1553B has four main
elements.
5) 1553B Hardware Components
MIL-STD-1553B defines three types of terminal devices that are allowed on the bus:
Bus Controller (BC)
Remote Terminal (RT)
Bus Monitor (BM).
5.1 Bus Controller
The main function of the bus controller (BC) is to provide data flow control for all transmissions
on the bus. In addition to initiating all data transfers, the BC must transmit, receive and
coordinate the transfer of information on the data bus. All information is communicated in
command/response mode - the BC sends a command to the RTs, which reply with a response.
The bus controller, according to MIL-STD-1553B, is the “key part of the data bus system” and
“the sole control of information transmission on the bus shall reside with the bus controller,
which shall initiate all transmission”. The bus can support multiple BCs, but only one can be
active at a time.
Normal BC data flow control includes transmitting commands to RTs at predetermined time
intervals. The commands may include data or requests for data (including status) from RTs. The
BC has control to modify the flow of bus data based on changes in the operating environment.
These changes could be a result of an air-to-ground attack mode changing to air-to-air, or the
failure mode of a hydraulic system. The BC is responsible for detecting these changes and
initiating action to counter them. Error detection may require the BC to attempt communications
to the RT on the redundant, backup bus.
5.2 Remote Terminal
The remote terminal (RT) is a device designed to interface various subsystems with the 1553
data bus. The interface device may be embedded within the subsystem itself, or be an external
interface to tie a non-1553 compatible device to the bus. As a function of the interface
requirement, the RT receives and decodes commands from the BC, detects any errors and reacts
to those errors. The RT must be able to properly handle both protocol errors (missing data, extra
words, etc) and electrical errors (waveform distortion, rise time violations, etc). RTs are the
largest segment of bus components. RT characteristics include:
Up to 31 remote terminals can be connected to the data bus
Each remote terminal can have 31 subadresses
No remote terminal shall speak unless spoken to first by the bus controller and
specifically commanded to transmit
Primary Bus (A)
Secondary Bus (B)
5.3 Bus Monitor
The bus monitor (BM) listens to all messages on the bus and records selected activities. The BM
is a passive device that collects data for real-time or post capture analysis. The BM can store all
or portions of traffic on the bus, including electrical and protocol errors. BMs are primarily used
for instrumentation and data bus testing.
This is a differential serial bus used in military and space equipments comprised of multiple
redundant bus connection and communicates at one MBps. Bus has single active bus control and
up to 31 remote terminals. Data transfer contain up to 16 bit data word.
6) INTERFACE DESCRIPTION
MILSTD 1553 is military standard that defines the electrical and protocol characteristic for data
bus. A data bus is used to provide a medium for exchange of data between various systems. It is
similar to LAN in personal computers and office automation industry. A data transmission
medium which would allow all systems and subsistence to share a common set of wires was
needed. So MILSTD 1553 standard redefines TDM as the transmission of data from several
signal sources through one communication system with different signal samples staggered in
time to form a composite pulse train.
6.1 DNx-553-1553: MIL-STD-1553 Interfaces
The DNA-1553-553 and DNR-1553-553 are high-performance, two-channel MIL-STD-1553
interfaces for UEI’s popular “Cubes” and RACKtangle I/O chassis respectively. Each port
operates fully independently and provides a complete dual, redundant 1553 interface and may be
set as 1553a or 1553b. The “b” interface fully implements specification notices 1 and 2. Each
port is transformer coupled, though direct coupling is available as an option.
Many 1553 functions are implemented in an on-board FPGA. This greatly reduces the burden
placed on the chassis CPU and ensures the DNx-1553-553 does not interfere with the
functionality of other I/O boards installed.
Each port may be independently configured as Bus Controller (BC), Remote Terminal (RT) or
Bus Monitor (BM). As Bus Controller, the board supports all standard BC-RT, RT-BC and RT-
RT transfers. The Remote Terminal support allows the board to emulate up to 31 different RTs
on the bus. Bus Monitoring (BM) mode provides the ability to monitor all activity, or selective
activity based upon RT address. In addition to monitoring data, BM monitors time tags, error
status and RT response time. Finally, each DNA-1553-553 channel may be set to simultaneously
act as an RT and BM or BC and BM.
DNA-1553-553 for PowerDNA Cubes
DNR-1553-553 for PowerDNR RACKs
When installed in the Cube, the DNA-1553-553 is well suited for the harsh environments
sometimes encountered in flight testing applications. The board is specified for operation from
40° to +85° C, from 0 to 70,000 feet. The system is also fully tested for operation at 5g vibration
and up to 50 g shock.
The DNx-1553-553 includes a standard MIL-1553 cable interface. Also included is a helpful,
self-test loop-back adaptor.
The DNA/DNR-1553-553 includes our 1553 API, designed to offer simple, easy-to-use controls
and yet maintain the ability to access all 1553 functionality. The software driver is compatible
with all popular operating systems including Windows Vista and XP and Linux as well as most
real-time OS’s such as RTX, QNX, RT Linux and more. Software support is also included for all
popular programming languages and data acquisition (DAQ) application packages including
LabVIEW and MATLAB.
7) Definitions
7.1Bit
Contraction of binary digit: may be either zero or one. In information theory a binary digit is
equal to one binary decision or the designation of one of two possible values or states of
anything used to store or convey information.
7.2Bit Rate
The number of bits transmitted per second.
7.3Pulse Code Modulation (PCM)
The form of modulation in which the modulation signal is sampled, quantized, and coded so that
each element of information consists of different types or numbers of pulses and spaces.
7.4Time Division Multiplexing (TDM)
The transmission of information from several signal sources through one communication system
with different signal samples staggered in time to form a composite pulse train.
7.5 Half Duplex
Operation of a data transfer system in either direction over a single line, but not in both
directions on that line simultaneously.
7.6 Word
In this document a word is a sequence of 16 bits plus sync and parity. There are three types of
words: command, status and data.
7.7 Message
A single message is the transmission of a command word, status word, and data words if they are
specified. For the case of a remote terminal to remote terminal (RT to RT) transmission, the
message shall include the two command words, the two status words, and data words.
7.8 Subsystem
The device or functional unit receiving data transfer service for the data bus.
7.9 Data Bus
Whenever a data bus or bus is referred to in this document it shall imply all the hardware
including twisted shielded pair cables, isolation resistors, transformers, etc., required to provide a
single data path between the bus controller and all the associated remote terminals.
7.10 Terminal
The electronic module necessary to interface the data bus with the subsystem and the subsystem
with the data bus. Terminals may exist as separate line replaceable units (LRU’s) or be contained
within the elements of the subsystem.
7.11 Bus Controller (BC)
The terminal assigned the task of initiating information transfers on the data bus.
7.12 Bus Monitor (BM)
The terminal assigned the task of receiving bus traffic and extracting selected information to be
used at a later time.
7.13 Remote terminal (RT)
All terminals not operating as the bus controller or as a bus monitor.
7.14 Asynchronous Operation
For the purpose of this standard, asynchronous operation is the use of an independent clock
source in each terminal for message transmission. Decoding is achieved in receiving terminals
using clock information derived from the message.
7.15 Dynamic Bus Control
The operation of a data bus system in which designated terminals are offered control of the data
bus.
7.16 Command/Response
Operation of a data bus system such that remote terminals receive and transmit data only when
commanded to do so by the bus controller.
7.17 Redundant Data Bus
The use of more than one data bus to provide more than one data path between the subsystems,
i.e., dual redundant data bus, tri-redundant data bus, etc.
7.18 Broadcast
Operation of a data bus system such that information transmitted by the bus controller of a
remote terminal is addressed to more than one of the remote terminals connected to the data bus.
7.19 Mode Code
A means by which the bus controller can communicate with the multiplex bus related hardware,
in order to assist in the management of information flow.
8) General Requirements
8.1 Test and Operating Requirements
All requirements as specified herein shall be valid over the environmental conditions which the
multiplex data bus system shall be required to operate.
8.2 Data Bus Operation
The multiplex data bus system in its The multiplex data bus system shall function
asynchronously in a command/response mode, and transmission shall occur in a half-duplex
manner. Sole control of information transmission on the bus shall reside with the bus controller,
which shall initiate all transmissions. The information flow on the data bus shall be comprised of
messages, The following General Requirements outline Data Bus Operations as it applies to this
standard.
MIL-STD-1553B defines the data bus system as having asynchronous, half duplex
communications in a command/response mode. Command/response mode means that the bus
controller initiates all messages on the bus and no terminal device transmits to the bus without
first being commanded to do so.
General information flow on the bus is comprised of messages, made up of three different
types of words: command, data and status.
8.3 Data Integrity and System Reliability
MIL-STD-1553 provides a high degree of data integrity by specifying word and message
validation requirements. These include checks for parity, proper Manchester encoding, bit
count, word count and proper timing. The Standard also specifies a tolerance to input signal zero
crossings, requirements for noise rejection and wide margins between the transmitted signal and
the received signal.
To improve system reliability, most systems today use two buses operating standby redundant
(dual standby redundant).
8.4 Testing 1553
When working with MIL-STD-1553 there are a number of phases of testing that should be
considered: development testing, validation testing, system integration/simulation.
Once the system has been deployed, periodic maintenance is required to spot check
performance and test for operational failures or battle damage. Since the Standard emphases
word and message validation it is necessary to test with injected errors in all phases of testing to
verify the operation of the validation and error detection circuits. The use of special test
equipment designed for 1553 testing should provide this capability and save time and money.
9) Characteristics
9.1 Data form
Digital data may be transmitted in any desired form, provided that the chosen form shall be
compatible with the message and word formats defined in this standard. Any unused bit positions
in a word shall be transmitted as logic zeros.
9.2 Bit Priority
The most significant bit shall be transmitted first with the less significant bits following in
descending order of value in the data word. The number of bits required to define a quantity shall
be consistent with the resolution or accuracy required. In the event that multiple precision
quantities (information accuracy or resolution requiring more than 16 bits) are transmitted, the
most significant bits shall be transmitted first, followed by the word(s) containing the lesser
significant bits in numerical descending order. Bit packing of multiple quantities in a single data
word is permitted.
The Characteristics section of the General Requirements begins to develop strict guidelines for
word formats, commands, message timing and response times.
Data words transmit 16 bits of data, with the most significant bit (MSB) being transmitted first.
There is no other standard describing the content of a data word. Content and format vary from
application to application. Most bus architectures have a self-defined standard for their particular
word formats.
9.3 1553 Coupling
Coupling connects a terminal device to the main data bus via interconnecting buses called stubs.
Connecting terminals create a load on the main bus, creating impedance mismatches and
resultant signal reflections that can distort and degrade signal quality on the bus. System error
rate performance and good signal to noise ratio require a balance between stub impedance being
low enough to provide adequate terminal signal levels but high enough to reduce signal
distortion from reflections. MIL-STD-1553B allows two methods of coupling terminal devices
to the main bus:
Direct coupling
Transformer coupling.
9.4 Direct Coupling
Direct coupling connections are wired directly to the bus cabling. The isolation resistors and
transformer are internal to the terminal device, not requiring additional coupling hardware.
Direct coupling connections can only be used with stub lengths of less than 1 foot.
Isolation resistors provide some protection for the main bus in the event of a stub or terminal
short, but MIL-STD-1553B cautions the use of direct coupling because a terminal short could
disable the entire bus. Direct stubs can also cause significant impedance mismatches on the bus.
9.5 Transformer Coupling
Transformer coupling utilizes a second isolation transformer, located external to the terminal
device, in its own housing with the isolation resistors. Transformer coupling extends the stub
length to 20 feet and provides electrical isolation, better impedance matching and higher noise
rejection characteristics than direct coupling. The electrical isolation prevents a terminal fault or
stub impedance mismatch from affecting bus performance.
10) APPLICATIONS
Applied to satellites as well as in space shuttles. Used in large transporters, aerial refuelers and
bombers, tactic fighters and helicopters. It is even contained in missiles and may act as primary
interface between aircraft and missiles. Navy has applied this data bus to surface and subsurface
applications. Army has put 1553 in to tanks.
Section 30 of this appendix shall apply to all dual standby redundant applications for the Army,
Navy, and Air Force. All Air Force aircraft internal avionics applications shall be dual standby
redundant, except where safety critical or flight critical requirements dictate a higher level of
redundancy.
Commercial applications have applied standard to systems like manufacturing production lines
and BART (bay area rapid transport). UK has issued standard 0018 P and NATO has published
STANAG 3838 AVS both in accordance to 1553 B. MILSTD 1760 A the air craft store
interconnect has 1553 B embedded in it
11) CONCLUSION
SYSCOM may model any protocol with three partswhich include Finite State
Machine diagrams, shared and localvariables and predicate action tables. After the
protocol hasbeen modeled, thecorrectness of the model is very fied through
reachability analysis. The analysis should show that themodel is error free, within
restrictions placed upon thesystem by the associated hardware.SYSCOM was used
to specify the Mil-Standard 1553.Assumptions were made to simplify the model
and promoteunderstanding.
.
Although the model alone issufficient to fully describe the protocol, additional
explanation was provided to describe how features of the Mil-Standard were
incorporated.
12) BIBLIOGRAPHY
1. Kiran K. Gunnam, Declan C.Hughes, John L Junkins, and Nasser Kehtamavaz,
A Vision Based DSP Embedded Navigation Sensor. IEEE Sensors journal,
Vol 2, NO: 5,October 2002
2.http://dspvillage.ti.com
3.http://www.gpsworld.com
4.Thyagarajan, Electronic navigation systems.
5.http://jungfrau.tamu.edu/~html/visionlab
6. ILC Data Device Corporation, "Mil-Std-1553 Designer's
Guide," Second Edition, ILC Data Device Corporation, 1988.
