MIL STD 1553 Overview

Overview
An Interpretation of MIL-STD-1553B
Overview
0. Introduction
This document provides an explanation of each part of MIL-STD-1553 on clause-byclause basis. Each clause of the Standard is presented for completeness (typed in italics
for easy reference) together with appropriate explanation or interpretation wherever
necessary. The numbering of the clauses and figures in this document are compared to
those in MIL-STD-1553 in Table 3.
Although the Standard specifies a multiplex data bus for aerospace applications, it is by
no means limited to these applications. MIL-STD-1553 has been widely accepted
around the world in such unlikely places as the London underground and some factory
locations.
A brief summary of the requirements introduced by Notice 1 and Notice 2 to MILSTD-1553 is given at the end of this document.
1. Scope
This Standard defines requirements for digital, command/response, time division multiplexing
techniques for a I MHz serial data bus and specifies the data bus and its interface electronics.
An example of typical multiplex data bus architecture is shown on Figure 1. This Standard
also defines the concept of operation and information flow on the multiplex data bus and the
electrical and functional formats to be employed.
2. Purpose
The purpose of this document is to establish uniform requirements for multiplex data system
techniques which will be used in system integration and to promote standard digital interfaces
for associated subsystems to the data bus. Even with the use of this Standard, subtle
differences may still exist between multiplex buses used in different applications due to the
options allowed in the Standard; system designers must recognize this fact. These designer
selected options must exist, so as to allow the necessary flexibility to assemble a custom
multiplex system from the functionally standard parts.
The above clauses are largely self-explanatory introducing the Standard and outlining
its extent. In highlighting the fact that different implementations of the Standard could
be incompatible in some of the options used and the extent to which the Standard is
used, system designers are reminded to ensure that they engineer coherent systems.
3. Definitions of Terms
The following definitions apply:
SBS Technologies, Inc
(505) 875-0600
1-800-SBS-1553
An Overview of MIL-STD-1553B
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.
Bit. 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.
Bit rate. The number of bits transmitted per second.
Broadcast. Operation of a data bus system such that information is transmitted by the bus
controller or a remote terminal for reception by all terminals using the broadcast mode
address.
Bus controller (BC). The terminal assigned the task of initiating information transfers on the
data bus.
Bus monitor (BM). The terminal assigned the task of listening to bus traffic and extracting
selected information to be used at a later time.
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.
Data bus. Whenever a data bus or bus is referred to in this document it shall imply all the
hardware including screened twisted pair cables, isolation resistors, transformers, etc.,
required to provide a single data path between the bus controller and all the associated
remote terminals.
Dynamic bus control. The operation of a data bus system in which designated terminals are
offered control of the data bus.
Half duplex. Operation of a data transfer system in either direction over a single line, but not
in both directions on that line simultaneously.
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
the data words.
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.
Pulse 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 number of pulses and spaces.
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.
Remote terminal (RT). All terminals not operating as the bus controller or as a bus monitor.
Subsystem. The device or functional unit receiving data transfer service from the data bus.
(505) 875-0600
1-800-SBS-1553
General Requirements
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.
Time division multiplexing (TDM). The transmission of information from several signal
channels through one communication system with different channel samples staggered in time
to form a composite pulse train.
Word. In this document a word is a sequence of 16 bits plus a synchronization signal (sync)
(three bit times) and one bit parity.
Definition of terms. Although the above definitions include some generally accepted
terms, definitions of word size, message content, and data bus system terminology are
specific to this MIL-STD.
4. Test and Operating Requirements
All specified requirements shall be valid over the environmental conditions in which the
multiplex data bus system shall be required to operate.
This clause is included to specify that the environmental conditions in which the bus is
to operate are determined by the vehicle in which it is placed. The environmental limits
of operation will be largely determined by the terminal components and their enclosure.
5. Data Bus Operation
The multiplex data bus system in its most elementary configuration shall be as shown on
Figure 1. The data bus 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 which are, in turn, formed
by three types of words (command, data, and status) as defined in clauses 13-16.
6. 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.
7. 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 numerically descending order. Bit packing of multiple
quantities in a single data word is permitted.
(505) 875-0600
1-800-SBS-1553
Optional
Redundant
Cables
Bus
Controller
Remote
Terminal
Subsystem
with Embedded
Remote Terminal
Subsystem(s)
Figure 1: Typical Data Bus Architecture
Single bit data and other parameters which are characterized by bit patterns of fewer
than 16 bits will not fill the 16 bits of data allowed in data word format. Two
approaches can be adopted to use all the bits in a word:
1. Packing multiple parameters in a word
2. Filling in zeros for all unused bits
In the first approach the encoding and decoding complexity must be considered, while
in the second approach the inefficiency of sending as little as one bit/word must be
considered.
Transmission Methods
8. Modulation
The signal shall be transferred over the data bus in serial digital pulse code modulation form.
Baseband modulation was chosen in view of its advantages over carrier modulation
techniques which need a greater bandwidth of transmitting media and more complex
terminal hardware.
9. Data Code
The data code shall be Manchester 1I bi-phase level. A logic one shall be transmitted as a
bipolar coded signal 110 (i.e., a positive pulse followed by a negative pulse). A logic zero
shall be bipolar coded signal 011 i.e., a negative pulse followed by a positive pulse). A
transition through zero occurs at the midpoint of each bit time (see Figure 2).
(505) 875-0600
1-800-SBS-1553
Like polar Return to Zero (RZ), Bi-phase Level consists of a self-clocking waveform
and is well-suited to applications in which bit synchronization cannot be conveyed by
other means. Unlike Polar RZ, Bi-phase level is compatible with transformer coupling,
and may, therefore, be used to convey data via the primary transmission medium. Biphase level is most appropriate for use on short transformer-coupled local buses, or on
the transformer-coupled primary transmission medium when bit synchronization
information is conveyed by the signaling waveform and cannot be provided via a
separate channel.
One
Bit
Time
(+)
(0)
(+)
(0)
(+)
(0)
(-)
1 MHz Clock
*NRZ Data
Manchester II
Bi-Phase Level
Note
*NRZ-Non return to zero
Figure 2: Data Encoding
With the Bi-phase Level data code, signal inversion can be caused by reversed
connection of the data bus signal conductors.
10. Transmission Bit Rate
The transmission bit rate on the bus shall be 1.0 megabit per second with a combined
accuracy and long-term stability of + 0.1%. The short-term stability (i.e., accuracy over 1.0 s
interval) shall be at least 0.01%.
11. Word Size

The word size shall be 16 bits plus the synchronization signal (sync) and the parity bit for a
total of 20 bit times as shown on Figure 3.
12. Word Formats

The word formats shall be as shown in Figure 3 for the command, data, and status words. A
specification of each format is given in clauses 13-16.
The 20-bit word size represents the number of bit times for a word of 16 data bits,
three bit time sync pattern and one bit time for a single parity bit. The three bit time
sync pattern is described in clause 13.2.
(505) 875-0600
1-800-SBS-1553
Bit
Times
Command
Word
5
Sync
Remote
Terminal Address
10
11
15
16
17
18
19
20
T/R
Data Word
Count/Mode Code
16
Data
Message Error
Instrumentation
Service Request
Reserved
1
Terminal Flag
Remote
Terminal Address
Dynamic Bus Control Acceptance
Subsystem Flag
Busy
Broadcast Command Received
Note
T/R - Transmit/Receive
P - Parity
14
Subaddress/
Mode
Sync
Sync
13
Data
Word
Status
Word
12
1
P
Figure 3: Word Formats
Word Formats
13. Command Words
13.1 Content
A command word shall consist of a synchronization signal (sync), RT address,

transmit/receive bit, subaddress/mode, data word count/mode code, and parity bit (see Figure
3).
13.2 Sync
The command sync waveform shall be an invalid Manchester waveform as shown on Figure 4.
The width shall be three bit times, with the waveform being positive for the first one and half
bit times, and then negative for the following one and a half bit times. If the next bit following
the sync is a logic zero, then the last half of the sync wave form will have an apparent width of
two bit times due to the Manchester encoding.
+ Volts
- Volts
Word Sync
Address
Bit (1)
Figure 4: Command and Status Sync Waveform
(505) 875-0600
1-800-SBS-1553
Word Formats
13.3 Remote Terminal (RT) Address
The next five bits following the sync shall be the RT address. Each RT shall be assigned to a
unique address. Decimal address 31 (11111) shall not be assigned as a unique address. In
addition to its unique address, a RT shall be assigned decimal address 31 (11111) as the
common address, if the broadcast option is used.
Each remote terminal is assigned a unique address for which it is responsible to respond
when that address is transmitted as part of a command word on the data bus by the
active bus controller. It should be noted that decimal address 31 cannot be assigned as
a unique address. This address has been assigned to all remote terminals as the common
address for which they may receive broadcast data if the system uses the broadcast
option (see clause 24).
13.4 Transmit/Receive
The next bit following the address shall be the transmit/receive (TIR) bit, which shall indicate
the action required of the RT. A logic zero shall indicate the RT is to receive, and logic one
shall indicate the RT is to transmit.
13.5 Subaddress/Mode
The next five bits following the transmit/receive bit shall be used for either an RT subaddress
or mode control, as is dictated by the individual terminal requirements. The subaddress/mode
values of 00000 and 11111 are reserved for special purposes, as specified in clause 13.8, and
shall not be used for any other functions.
This field has two mutually exclusive functions:

1. It identifies the subaddress of specific messages to a remote terminal.
2. It identifies that a mode command is being transmitted.
The use of either 00000 or 11111 in the subaddress/mode field is decoded to indicate
that a mode code command is present in the next five bit field. In this case the
subaddress range will be limited to 30 unique addresses. It is recommended that 11111
is used to invoke mode control in order to allow distinction to be made between
command and status words as described in the explanation of clause 15.5. If the
instrumentation bit in the status word is implemented, the subaddress will be limited to
15 unique subaddresses. The requirements for use of the instrumentation bit are defined
in clause 15.5.
The subaddress identification can serve to identify one of a number of subsystems
connected to a single RT, alternatively it may be used as pointer to specific store
locations in a single subsystem. It should be noted that by using the T/R bit, a
maximum of 30 transmit and 30 receive subaddresses are available if the
instrumentation bit is not used.
13.6 Data Word Count/Mode Code
The next five bits following the subaddress/mode control shall be the quantity of data words to
be either sent out or received by the RT or the optional mode code as specified in clause 13.8.
(505) 875-0600
1-800-SBS-1553
A maximum of 32 data words may be transmitted or received in any one message block. All
1's shall indicate a decimal count of 31, and all 0's shall indicate a decimal count of 32.
The dual function of this field provides for the identification of message lengths for data
messages or mode codes for managing the information transfer system. The five bit
field allows up to 32 data words to be transmitted in a message or 32 specified mode
codes. As zero word count data cannot be sent, five bits can specify up to 32 data
words.
13.7 Parity
The last bit in the word shall be used for parity over the preceding sixteen bits. Odd parity
shall be used.
The use of single parity bit per word is provided to identify any single or odd bit errors
occurring during the transmission and detection of a word.
The total number of bits in any word, including the parity bit, should be odd. Only one
parity bit is used as it is considered that this, together with the protection provided by
use of Manchester II encoding and the word synchronization field, gives adequate
integrity. However, if a greater degree of integrity is required, additional error checking
capability may be incorporated in the data, such as Cyclic Redundancy Checks (CRC)
or Checksums.
13.8 Optional Mode Control
For RT's exercising this option a subaddress/mode of 00000 or 11111 shall imply that the
contents of the data word count/mode code field are to decoded as a five bit mode command.
The mode codes shall only be used to communicate with the multiplex bus related hardware
and to assist in the management of information flow, and not to extract data from or feed data
to a functional subsystem. Code 00000 to 01111 shall only be used for mode codes which do
not require transfer of a data word. For these mode codes, the TIR bit shall be set to 1. Codes
10000 to 11111 shall only used for mode codes which require transfer of a single data word.
For these mode codes, the TIR bit shall indicate the direction of data word flow as specified in
clause 13.4. No multiple data word transfer shall be implemented with any mode code. The
mode codes are reserved for the specific functions shown in Table 1 and shall not be used for
any other purpose. If the designer chooses to implement any of these functions, the specific
codes, TIR bit assignment, and the use of data word, shall be used as indicated. The use of the
broadcast command option shall only be applied to particular mode codes as specified in
Table 1.
Mode commands are used to manage the data bus system and are considered a
necessary overhead to assist in the control of the data flow. The overheads comprise
command words and status words. Command and status words are associated with
both control messages and data messages. Message formats within this protocol can be
transmitted to a single receiver or to multiple receivers based upon the command word
address for the message.
Although the Standard states that the optional mode control function should not be
used to extract data from or feed data to a functional subsystem, the extent of RT
functions and hence those of subsystems can vary. There are also cases where mode
(505) 875-0600
1-800-SBS-1553
Word Formats
commands may reflect back into the subsystem, for instance a broadcast sync command
could be used to revert to a specific state or time (e.g., sync to weapon firing mode).
None of the mode codes are mandatory. Some RTs may not handle all mode codes. Use
of those not implemented should provide an illegal command response (see clause
30.4).
Within the command word, the mode codes provide a data bus management capability.
The mode codes have been divided into two groups: mode codes without a data word
(00000 - 01111) and mode codes with a data word (10000 - 11111). The use of bit 15
in the command word to identify the two groups was provided to aid in the decoding
process. Also, the use of a single data word instead of multiple data words was adopted
to simplify the mode circuitry within RT's. Generally, with these two groups of mode
command, all management requirements of an information transfer system can be met.
Some mode codes in each of these two groups are reserved for future use (see clauses
13.8.10 and 13.8.17).
Table 1 provides a list of assigned mode codes indicating (in column d) whether or not
a data word is associated with each mode code. In some cases e.g., transmit last
command, the data word is associated with the response from the RT to a receive mode
command rather than with the transmit mode command. This is shown in the examples
of all types of mode command transfer formats given in Figure 13.
Table 1: Assigned Mode Codes
T/R
Bit
(a)
Mode
Code
(b)
1
1
1
1
I
00000
00001
00010
00011
00100
Dynamic Bus Control

Synchronize
Transmit Status
Initiate Self Test
Transmitter Shutdown
No
No
No
No
No
No
Yes
No
Yes
Yes
1
I
1
1
1
00101
00110
00111
01000
01001
Override Transmitter Shutdown

Inhibit Terminal Flag Bit
Override Inhibit Terminal Flag Bit
Reset Remote Terminal
Reserved
No
No
No
No
No
Yes
Yes
Yes
Yes
TBD*
01010
to
01111
10000
10001
10010
10011
10100
10101
10110
10111
to
11111
Reserved
No
TBD*
Reserved
Transmit Vector Word
Synchronize
Transmit Last Command
Transmit Built In Test Word
Selected Transmitter Shutdown
Override Selected Transmitter Shutdown
Reserved
Reserved
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
TBD*
No
Yes
No
No
Yes
Yes
TBD*
TBD*
Reserved
Yes
TBD*
1
1
0
1
1
0
0
1 or 0
1 or 0
1 or 0
Function
(c)
(505) 875-0600
Associated
Broadcast
Data Words Command Allowed
(d)
(e)
1-800-SBS-1553
10
Note to Table 1: *TBD - To Be Determined (see clause 13.8.10)
13.8.1 Dynamic Bus Control
The controller shall issue a transmit command to an RT capable of performing the bus
control function. This RT shall respond with a status word as specific in clause 15. Control of
the data bus passes from the offering bus controller to the accepting RT upon transmission of
the status word by the RT. If the RT rejects control of the data bus, the offering bus controller
retains control of the data bus.
The dynamic bus control mode command (00000) is provided to allow the active bus
controller a mechanism (using the information transfer system message formats) to
offer a potential bus controller (operating as a remote terminal) control of the data bus.
The response to this offering of bus controller is provided by the receiving remote
terminal setting the dynamic bus control acceptance bit in the status word (see clause
15.11). Rejection of this request by the remote terminal requires the presently active
bus controller to continue offering control to other potential controllers or remain in
control. When a remote terminal accepts control of the data bus system by setting the
dynamic bus control acceptance bit in the status word, control is relinquished by the
presently active bus controller handing over to the new bus controller.
Note: The sequence above requires software (or firmware) implementation in
all bus controllers.
13.8.2 Synchronize (without data word)
This command shall cause the RT to synchronize (e.g., to reset the internal timer, to start a
sequence, etc.). The RT shall transmit the status word as specified in clause 15.
See clause 13.8.12 for explanatory note.

13.8.3 Transmit Status Word
This command shall cause the RT to transmit the status word associated with the last valid
command word. This mode command shall not alter the state of the status word.
This command would normally be used after a broadcast command or message transfer
to determine whether an RT had correctly received the data. Normally status is reset on
receipt of a valid command but this mode command enables the status word associated
with the last valid command word to be obtained by the bus controller.
In some situations (for example, where the RT does something unexpected after
receiving a command) the transmit last command can be used to determine what
command the RT received (see clause 13.8.13). It is important to note that the transmit
status word mode command will be stored in the RT's last command buffer, and thus
the transmit last command mode command should be used first.
Terminal designers must ensure that in no circumstances must the content of the status
word be changed from that which was associated with the previous valid command.
(505) 875-0600
1-800-SBS-1553
Word Formats
11
13.8.4 Initiate Self Test
This command shall be used to initiate self test within the RT. The RT shall transmit the status
word as specific in clause 15.
The initiate self test mode command (00011) is provided to initiate Built In Test (BIT)
circuitry within remote terminals. (Note: The abbreviation BIT is not to be confused
with that for binary digit. The meaning of each is clear in the context in which they are
used.) The mode code is usually followed, after sufficient time for test completion, by a
transmit BIT word mode command yielding the results of the test. The message
formats provided for this mode command allow for both individual requests and
multiple requests via the Broadcast command. Notice that the initiate self test mode
command is associated with the multiplex system terminal hardware only. The level of
testing associated with this command depends on the capability of the RT, and no
specific requirements for BIT are specified within the Standard. It should also be noted
that the status word response required on receipt of the command does not indicate the
result of the test, but only that the command has been received.
If a remote terminal cannot respond normally while carrying out a self test operation,
the busy bit must be set in the status word. The RT must not go off-line during
execution of a self test command.
13.8.5 Transmitter Shutdown
This command (to only be used with dual redundant bus systems) shall cause the RT to
disable the transmitter associated with the redundant bus. The RT shall not comply with a
command to shut down a transmitter on the bus from which this command is received. In all
cases, the RT shall respond with a status word as specified in clause 15 after the command.
13.8.6 Override Transmitter Shutdown
This command (to only be used with dual redundant bus systems) shall cause the RT to enable
a transmitter which was previously disabled. The RT shall not comply with a command to
enable a transmitter on the bus from which this command is received. In all cases, the RT
shall respond with a status word as specified in clause 15 after this command.
Four mode code commands (see clauses 13.8.5, 13.8.6, 13.8.15, and 13.8.16) are
provided to control transmitters associated with terminals in a system. These
commands can be sent to a single receiver or broadcast to multiple users. The above
two commands are used in dual redundant systems to shutdown and restart an RT
transmitter. The transmitter shut down command would normally be used to disable a
"jabbering" transmitter. (see clause 28.3 for details of the terminal fail-safe mechanism
which should also operate in these circumstances). Note that the bus controller must
issue this command on the standby bus.
13.8.7 Inhibit Terminal Flag (T/F) Bit
This command shall cause the RT to set the T/F bit in the status word specified in clause 15 to
logic zero until otherwise commanded. The RT shall transmit the status word as specified in
clause 15.
(505) 875-0600
1-800-SBS-1553
12
The inhibit terminal flag mode code (00110) is used to set the terminal flag bit in the
status word to an unfailed condition regardless of the actual sate of the terminal flag
being addressed. This mode code is primarily used to prevent continued interrupts to
the error handling and recovering system when the failure has been noted and the
system reconfigured as required. Commanding this mode code prevents future failures
from being reported which would normally be reported using the terminal flag in each
subsequent status word response. The message format associated with this mode code
allows for both single receivers and broadcast receivers to respond. No data word is
required with this mode code. Depending on the implementation, this command may be
registered in the returned status word, but it should not be registered until the next
status word. Therefore, to be positive, it is advisable to interrogate the status word
with a separate command.
Note: The terminal flag, which is used to indicate an RT fault condition, is
implicitly limited to terminal faults.
13.8.8 Override Inhibit (T/F Bit)
This command shall cause the RT to override the inhibit T/F bit specified in clause 13.8.7.
The RT shall transmit the status word as specified in clause 15.
The override inhibit T/F bit mode command (00111) negates the inhibit function, thus
allowing the T/F bit in the status response to report the present condition of the
terminal. Note: It is advisable to interrogate the status word with a separate command
in this case. This mode code can be transmitted by the bus controller to both single and
broadcast receivers. There is no data word associated with this mode code.
13.8.9 Reset Remote Terminal
This command shall be used to reset the RT to a power up initialized state. The RT shall first
transmit its status word, and then reset.
If a remote terminal cannot respond normally while undergoing reset, the busy bit must
be set in the status word. The RT must be capable of receiving the next valid command.
13.8.10 Reserved Mode Codes (01001 to 01111)
These mode codes are reserved for future use and shall not be used.
13.8.11 Transmit Vector Word
This command shall cause the RT to transmit a status word as specified in clause 15 and a
data word containing service request information.
The transmit vector word mode code (10000) is associated with the service request bit
in the status word and is used to determine specific service being required by the
terminal. The service request bit and the transmit vector word are the only means
available for the terminal to request the scheduling of an a periodic message. The
message format for this single receiver operation contains a data word associated with
(505) 875-0600
1-800-SBS-1553
Word Formats
13
the terminal's response. Figure 6 illustrates the use of this mode command in
association with the service request bit.
13.8.12 Synchronize (with data word)
The RT shall receive a command word followed by a data word as specified in clause 14. The
data word shall contain synchronization information for the RT. After receiving the command
and data word, the RT shall transmit the status word as specified in clause 15.
Synchronize mode commands (see also clause 13.8.2) inform the terminal(s) of an
event time to allow coordination between the active bus controller and receiving
terminals. Synchronization information may be implicit in the command word (mode
code 00001), or a data word (mode code 10001) may be used to follow the command
word to provide the synchronization information. If a data word is used, the definition
of the bit meanings is the responsibility of the system designer. These may not
necessarily be only associated with the management of data flow, they may also be used
as system control functions.
13.8.13 Transmit Last Command Word
This command shall cause the RT to transmit its status word as specified in clause 15
followed by a single data word which contains bits 4-19 of the last command word, excluding
a transmit last command word mode code received by the RT. This mode command shall not
alter the state of the RT's status word.
The transmit last command mode code (10010) is used in the error handling and
recovery process to determine the last valid command received by the terminal, prior to
this mode code. Note that this mode code will not change the contents of the last
command or the status word. A remote terminal receiving this mode command will
transmit the previous status word followed by a data word which contains the previous
16-bits of the last valid command word received. Notice that this mode command will
not alter the state of the receiving terminal's status word, thus allowing this mode
command to be used in error handling and recovery operation without affecting the
status word which can have added error data.
13.8.14 Transmit Built-In-Test (BIT) Word
This command shall cause the RT to transmit its status word as specified in clause 15
followed by a single data word containing the RT built-in-test (BIT) data. This function is
intended to supplement the available bits in the status word when the RT hardware is
sufficiently complex to warrant its use. The data, containing the RT BIT data, shall not be
altered by the reception of a transmit last command or a transmit status word mode code.
This function shall not be used to convey BIT data from the associated subsystem(s).
The transmit BIT word mode code (10011) provides the bus controller with the BIT
results available from a terminal, as well as the status word. Obviously the bus
controller must not issue this as a broadcast command. The contents of the BIT data
word are provided to supplement the appropriate bits already available via the status
word for complex terminals, and designers are free to use these as required. Notice that
the contents of the BIT word within the remote terminal "...shall not be altered by the
reception of a transmit last command or a transmit status word mode code". This
(505) 875-0600
1-800-SBS-1553
14
allows error handling and recovery procedures to be used without changing the error
data recorded in this word. However, the RT will only save the last command, and the
status code field (of the status word) will not be changed if transmit last command or
transmit status word mode commands are transmitted. If, however, any other
transmissions are made to the RT, the status code field may change, for example, if a
message error occurred during the transmission. See clause 13.8.3 and clause 13.8.13.
Another point worth noting is that the function of transmitting RT BIT data "shall not
be used to convey BIT data from the associated subsystem(s)." Subsystem fault
investigation, when indicated by the subsystem flag, is not specified or otherwise
restricted by MIL-STD-1553. System designers must, therefore, make the necessary
provisions.
13.8.15 Selected Transmitter Shutdown
This command shall cause the RT to disable the transmitter associated with a specified
redundant data bus. The command is designed for use with systems employing more than two
redundant buses. The transmitter that is to be disabled shall be identified in the data word
following the command word in the format as specified in clause 14. The RT shall not comply
with a command to shut down a transmitter on the bus from which this command is received.
In all causes the RT shall respond with a status word as specified in clause 15.
13.8.16 Override Selected Transmitter Shutdown
This command shall cause the RT to enable a transmitter which was previously disabled. The
command is designed for use with systems employing more than two redundant buses. The
transmitter that is to be enabled shall be identified in the data word following the command
word in the format as specified in clause 14. The RT shall not comply with a command to
enable a transmitter on the bus from which this command is received. In all cases, the RT
shall respond with a status word as specified in clause 15.
Four mode code commands (see clauses 13.8.5, 13.8.6, 13.8.15, and 13.8.16) are
provided to control transmitters associated with terminals in a system. These
commands can be sent to a single receiver or broadcast to multiple users. Care should
be taken to ensure that all RT's are aware of the bus numbering convention.
13.8.17 Reserved Mode Codes (10110 to 1111)
These mode codes are reserved for future use and shall not be used.
Any future use of reserved mode codes will be notified in updated issues of the
Standard.
14. Data Word
14.1 Content
The data word shall consist of a sync waveform, data bits and parity bit (see Figure 3).
(505) 875-0600
1-800-SBS-1553
Word Formats
15
14.2 Sync
The data sync waveform shall be an invalid Manchester waveform as shown on Figure 5. The
width shall be three bit times, with the waveform being negative for the first one and on-half
bit times, and then positive for the following one and one-half bit times. Note that if the bits
proceeding and following the sync are logic ones, then the apparent width of the sync
waveform will be increased to four bit times.
+ Volts
- Volts
Word Sync
Parity
Bit (0)
Data
Bit (0)
Figure 5: Data Sync Waveform
Note that the term invalid Manchester waveform refers to the description of the
waveform in terms of the Manchester bi-phase encoding. Being a defined part of the
message, it is actually valid for detection purposes.
14.3 Data
The 16 bits following the sync shall be used for data transmission as specified in clause 7.
14.4 Parity
The last bit shall be used for parity as specified in clause 13.7.
Data words are distinguished from command and status words by the inverted 3-bit
sync pattern. Both packed and unpacked data may be transmitted in the 16-bit data
field. Odd parity on the data field provides a data integrity check identical to the
command and status word formats.
15. Status Word
15.1 Content
A status word shall consist of a sync waveform, RT address, message error bit,
instrumentation bit, service request bit, three reserved bits, broadcast command received bit,
busy bit, subsystem flag bit, dynamic bus control acceptance bit, terminal flag bit, and a
parity bit. For optional broadcast operation, transmission of the status word shall be
suppressed as specified in clause 24.
15.2 Sync
The sync waveform shall be as specified in clause 13.2.
(505) 875-0600
1-800-SBS-1553
16
15.3 RT Address
The next five bits following the sync shall contain the address of the terminal which is
transmitting the status word as defined in clause 13.3.
15.4 Message Error Bit
The status word bit at bit time nine (see Figure 3) shall be used to indicate that one or more
of the data words associated with the preceding receive command from the bus controller has
failed to pass the RT's validity test as specified in clause 28.1. This bit shall also be set under
the conditions specified in clauses 28.2, 30.4, and 30.6. A logic one shall indicate the
presence of a message error, and logic zero shall show its absence. All RT's shall implement
the message error bit.
The message error bit is set to logic one to indicate one or more of the data words
associated with the preceding received message has failed to pass the message validity
test. The message validity requirements are:
Word Validation: Word begins with valid sync, Manchester II code correctly
transmitted, 16 data bits plus parity, and word parity odd. Invalid commands should not
set the message error bit.
Continuous words within a message.
Address Validation: Matches address to unique terminal or broadcast address.
Messages with incorrect addresses should be treated as being invalid.
Terminals that do detect illegal commands set the message error bit and transmit the
status word (see clause 30.4). Illegal commands should not be confused with invalid
command (see clause 30.3).
The status word will be transmitted as shown in the data and mode code message
formats (see Figures 6 and 7) if the message validity requirements are met. When a
message error occurs in a broadcast message format, the message error bit will be set in
the status word and the status response withheld as required by broadcast message
format. It should be noted that any error condition renders the entire message invalid.
15.5 Instrumentation Bit
The status word bit at bit time ten (see Figure 3) shall be reserved for the instrumentation bit
and shall always be a logic zero. This bit is intended to be used in conjunction with a logic
one in bit time ten of the command word to distinguish between a command word and a status
word. The use of the instrumentation bit is optional.
Since the sync field (3 bits) is used to distinguish command/status words from data
words on the bus, a mechanism is also required to enable passive monitoring equipment
to distinguish between command and status words so as to interpret the bus traffic
correctly. If this bit is used the Standard specifies setting bit 10 in the command word
to a logic one which can then be distinguished from the corresponding bit 10 in the
status word (instrumentation bit) which is always set to logic zero. The use of the
instrumentation bit, however, results in the loss of fifteen usable subaddresses, 00001 to
01111, and 00000 for mode command identification.
(505) 875-0600
1-800-SBS-1553
Word Formats
17
An alternative method can be defined which only involves the loss of one usable
subaddress. For this method the system designer must prohibit the use of subaddress
codes 01000 and 00000 in the command word. As a result, examination of bits 10, 12,
13, and 14 would only reveal all logic zeros if the word in question was a status word.
This is true because this combination of zero bits can no longer occur in any command
word thus providing immediate and correct separation of command and status words.
Either one or other of the above two methods of distinguishing between command and
status words could be used.
15.6 Service Request Bit
The status word bit at bit time eleven (see Figure 3) shall be reserved for the service request
bit. The use of this bit is optional. This bit, when used, shall indicate the need for the bus
controller to take specific predefined actions relative to the RT or associated subsystem.
Multiple subsystems, interfaced to a single RT, which individually require a service request
signal shall logically "OR" their individual signals into the single status word bit. In the event
this logical "OR" is performed, then the designer must make provisions in a separate data
word to identify the specific requesting subsystem. The service request bit is intended to be
used only to trigger data transfer operations which take place on an exception rather than
periodic basis. A logic one shall indicate the presence of a service request, and a logic zero
its absence. If this function is not implemented, the bit shall be set to zero.
The service request bit is provided to indicate to the active bus controller that a remote
terminal requests service. When this bit in the status word is set to logic one, the active
bus controller uses a mode command (transmit vector word) to identify the specific
request (Figure 6). The message format for acquiring this is discussed under transmit
vector word mode command (see clause 13.8.11).
15.7 Reserved Status Bits
The status word at bit times 12 to 14 are reserved for future use and shall not be used. These
bits shall be set to a logic zero.
15.8 Broadcast Command Received Bit
The status word bit at bit time 15 shall be set to a logic one to indicate that the preceding
valid command word was a broadcast command and a logic zero shall show it was not a
broadcast command. If the broadcast command option is not used, this bit shall be set to logic
zero.
The broadcast command received bit is set to logic one when the preceding valid
command word was a broadcast command (address 31). Since the broadcast message
format requires the receiving remote terminals to suppress their status words, the
broadcast command received bit is set to identify that the command was received
properly.
If the broadcast message validity is required by the bus controller, the message format
illustrated on Figure 7 is used to determine this information. The broadcast command
received bit will be reset when the next valid (non-broadcast) command is received by
the remote terminal, unless the next valid command is a transmit status word or a
transmit last command mode command.
(505) 875-0600
1-800-SBS-1553
18
Single Receiver Only - Bus Controller to Remote Terminal

Notes
** Response Time
# Intermessage Gap
Command
Word
Data
Word
Data
Word
Continued
Service Request Bit Set to

"1"
11
Reserved
Mode Code
Command
Status
Response
**
Source: Single
Receiver
Parity
Source: Bus Controller

Address: Unique Address of S/R
Status Response
Subaddress: 00000 or 11111
Mode Code: 10000
1
Parity
Service Request
Terminal Flag
Instrumentation
Subsystem Flag
20
Busy
14
5
Remote
Terminal Address
Message Error
Sync
#
below
Source: Single Receiver

Address: Unique-31
Subaddress: Unique - 00000 or 11111
Data Word Count: 1-32
T/R: Receive
Status
Word
Status
Response
**
Data
Word
Continued
below
Service Vector
Information
Service Request Bit Set to "U" (if no new service requests are
present)
Terminal Flag
Parity
Data
Word
**

Address: Unique Address of S/R
Subaddress: Unique Address of
Service Vector Information
T/R: Transmit
Status
Response
Reserved
20
1
Subsystem Flag
Remote
Terminal Address
14
3
Busy
Service Request
Command
Word
Instrumentation
Sync
11
Message Error
Status
Word
Data
Word
A periodic Information
Bus Controller
Returns to
Synchronous
Bus
List
Figure 6: Transmit Vector Word Transfer Format
(505) 875-0600
1-800-SBS-1553
Word Formats
Multiple Receivers
Active Bus Controller to Remote Terminals
Command
Data
Data
Word
Word
Word
Notes
** Response Time
# Intermessage Gap
Mode Code
Command

Address: Unique - 31 (11111)
Subaddress: 00000 or 11111
Mode Code: 00010

Address: 31 (11111)
T/R: Receive
11
Terminal Flag
Parity
Service Request
Reserved
20
1
Remote
Terminal Address
14
3
Subsystem Flag
Busy
Instrumentation
Sync
8
5
Message Error
Status
Word
**
19
Status
Response
Status Word Transmitted With

Bit Set
Figure 7: Broadcast Command Received Bit

15.9 Busy Bit
The status word bit at bit time 16 (see Figure 3) shall be reserved for the busy bit. The use of
this bit is optional. This bit, when used, shall indicate that the RT or subsystem is unable to
move data to or from the subsystem in compliance with the bus controller's command. A logic
one shall indicate the presence of a busy condition, and logic zero its absence. In the event the
busy bit is set in response to a transmit command, then the RT shall transmit its status word
only. If this function is not implemented, the bit shall be set to logic zero.
The busy bit in the status word (see Figure 8) is set to logic one to indicate to the
active bus controller that the remote terminal is unable to move data to or from the
subsystem in compliance with the bus controller's command. It should be noted that
allowing the system to become "busy" and thereby setting the busy bit should be
restricted to that of an exception basis e.g. periods of high loads in subsystems. Setting
the busy bit is not to be used as means of overcoming problems associated with slow
acting remote terminals.
The message format associated with a busy condition is shown in Figure 8. A busy
condition can exist within a remote terminal at any time causing it to be non-responsive
to a command to send data or to be unable to receive data. This condition can exist for
all message formats. In each case, except for broadcast message formats, the active bus
controller will be informed within the status response of the busy condition. In the case
of broadcast message formats, this information will not be made known unless the
receiving terminals are polled, after the broadcast message, requesting their status. If
the status word has the broadcast received bit set, the message was received and the
terminal was not busy.
15.10 Subsystem Flag Bit
The status word bit at bit time 17 (see Figure 3) shall be reserved for the subsystem flag bit.
The use of this bit is optional. This bit, when used, shall flag a subsystem fault condition and
alert the bus controller to potentially invalid data. Multiple subsystems, interfaced to a single
(505) 875-0600
1-800-SBS-1553
20
Single Receiver
Active Bus Controller to Remote Terminal
Command
Word
Status
Response
**

Address: - 31 (11111)
T/R: Transmit
11
Service Request
1
Parity
Instrumentation
Notes
** Response Time
# Intermessage Gap
Reserved
Terminal Flag
Remote
Terminal Address
Subsystem Flag
20
Busy
14
Message Error
Sync
Status
Word
Figure 8: Busy Bit
RT, which individually require a subsystem flag bit signal shall logically "OR" their
individual signals into a single status word bit. In the event that this logical "OR" is
performed, the designer must make provisions in a separate data word to identify the specific
reporting subsystem. A logic one shall indicate the presence of the flag, and logic zero its
absence. If not used, this bit shall be set to logic zero.
15.11 Dynamic Bus Control Acceptance Bit
The status word bit at bit time 18 (see Figure 3) shall be reserved for the acceptance of
dynamic bus control. This bit shall be used if the RT implements the optional dynamic bus
control function. This bit, when used, shall indicate acceptance or rejection of a dynamic bus
control offer as specified in clause 13.8.1. A logic one shall indicate acceptance of control,
and a logic zero shall indicate rejection of control. If this function is not used, this bit shall be
set to logic zero.
Discussion of the use of dynamic bus control is given in clause 13.8.1.

15.12 Terminal Flag Bit
The status word bit at bit time 19 (see Figure 3) shall be reserved for the terminal flag
function. The use of this bit is optional. This bit, when used shall flag an RT fault condition. A
logic one shall indicate the presence of the flag, and logic zero its absence. If not used, this
bit shall be set to logic zero.
15.13 Parity Bit
The least significant bit in the status word shall too be used for parity as specified in clause
13.7.
(505) 875-0600
1-800-SBS-1553
Message Formats
21
16. Status Word Reset

The status word bits, with the exception of the address, shall be set to logic zero after a valid
command word is received by the RT with the exceptions as specified in clause 13.8. If the
conditions which caused bits in the status word to set (e.g. terminal flag) continue after the
bits are reset to logic zero, then the affected status word bits shall be again set, and then
transmitted on the bus as required.
It is to be noted that:
1. Status is constructed on a message by message basis on receipt of each valid command
word. Remote terminals are required to store the status word between valid command
words so that it is available for interrogation using the transmit status word mode code.
2. It is recommended that the terminal flag bit and subsystem flag bit, having once been
set, should remain set until a reset remote terminal mode command is received or a
power-up initialization occurs.
3. The inhibit terminal flag mode code locally suppresses the terminal flag bit in the status
word so preventing failures of the RT from being reported in that way.
The above three facilities allow an orderly error handling and recovery approach to be
accomplished by the bus controller using the information associated with error analysis
data contained within the status word or other data associated with the RT (e.g. last
command word and BIT word).
(505) 875-0600
1-800-SBS-1553
22
Message Formats
17. Message Formats
The messages transmitted on the data bus shall be in accordance with the formats in Figure 9
and Figure 10. The maximum and minimum response times shall be as stated in clauses 25
and 26. No message formats, other than those defined below, shall be used on the bus.
The command/response protocol provides two types of message formats, i.e., control
BC to RT
Transfer
Receive
Command
Data Word
RT to BC
Transfer
Transmit
Command
**
RT to RT
Transfer
Receive
Command
Transmit
Command
Mode Command
without Data Word
Mode
Command
**
Status
Word
Mode Command with

Data Word (Transmit)
Mode
Command
**
Status
Word
Data Word
Next
Command
Word
Mode Command with

Data Word (Receive)
Mode
Command
Data Word
Status
Word
Next
Command
Word
...
Data Word
Status
Word
Data Word
Status
Word
Next
Command
Word
Data Word
Next
Command
Word
**
Data Word
Data Word
...
Status
Word
Data Word
Data Word
**
**
... Data Word
Status
Word
**
Next
Command
Word
Next
Command
Word
Notes
** response time
# intermessage gap
Figure 9: Information Transfer Formats

BC to RT(s) Receive
Data Word Data Word
Transfer Command
RT to RT(s) Receive
Transmit
Transfer Command Command
Mode
Mode Command
without Data Word Command
**
...
Status
Word
Data Word
Next
Command
Word
Data Word Data Word
...
Data Word
Next
Command
Word
Next
Command
Word
Mode
Mode Command with
Data Word
Data Word (Receive) Command
Next
Command
Word
** response time
# intermessage gap
Figure 10: Broadcast Information Transfer Formats
messages and data messages. Control messages are identified by the subaddress/mode
field in the command word being set to 31 (11111) or 32 (00000). (In this case, the
Standard defines decimal subaddress 32 to be equal to binary 00000 so that decimal 1
(505) 875-0600
1-800-SBS-1553
Message Formats
23
to 31 correspond to binary 00001 to 11111). All control messages originate with the
active bus controller and are received by a single receiver or by multiple receivers
(broadcast). A terminal address value of 31 (11111) in the command word indicates a
broadcast message, while any other terminal addresses are to identify unique messages
to a terminal on the bus. The mode command information is contained completely in
the mode code/word count field of the command word. More general discussion of the
use of mode commands is contained in clause 13.8.
The various legal mode commands with and without data word are illustrated in Figure
13.
18. Bus Controller to Remote Terminal Transfers
The bus controller shall issue a receive command followed by the specific number of data
words. The RT shall, after message validation, transmit a status word back to the bus
controller. The command and data words shall be transmitted in a contiguous fashion with no
interword gaps.
19. Remote Terminal to Bus Controller Transfers

The bus controller shall issue a transmit command to the RT. The RT shall, after command
verification, transmit a status word back to the bus controller, followed by the specified
number of data words. The status and data words shall be transmitted in a contiguous fashion
with no interword gaps.
20. Remote Terminal to Remote Terminal Transfers

The bus controller shall issue a receive command to RT A followed contiguously by a transmit
command to RT B. RT B shall, after command verification, transmit a status word followed by
the specified number of data words. The status and data words shall be transmitted in a
contiguous fashion with no interword gaps. At the conclusion of the data transmission by RT
B, RT A shall transmit a status word within the specified time period (see clause 26).
For the above three types of message transfers, it should be noted that successive
message transfers to or from the same RT causes a high throughput. It is preferred that
if the subsystem is unable to handle the required message rate, the busy bit should be
set as necessary to ensure data is not lost.
21. Mode Command without Data Word
The bus controller shall issue a transmit command to the RT using a mode code specified in
Table 1. The RT shall, after command validation, transmit a status word.
22. Mode Command with Data Word (Transmit)

The bus controller shall issue a transmit command to the RT using the mode code specified in
Table 1. The RT shall, after command word verification, transmit a status word followed by
one data word. The status word and data word shall be transmitted in a contiguous fashion
with no gap.
(505) 875-0600
1-800-SBS-1553
24
23. Mode Command with Data Word (Receive)

The bus controller shall issue a receive command to the RT using a mode code specified in
Table 1, followed by one data word. The command word and data word shall be transmitted in
a contiguous fashion with no gap. The RT shall, after command and data word validation,
transmit a status word back to the controller.
24. Optional Broadcast Command

This mode allows one transmission to be simultaneously received by more than one RT but no
status word reply will be made by any RT.
The broadcast mode provides a mechanism for transmitting information to multiple

users with a single message. The mechanism for accomplishing this is to reserve
address 31 (11111) for broadcast messages. When a broadcast message is transmitted,
the transmitting terminal uses address 31 rather than a unique terminal address. All
addresses other than 31 can be assigned to remote terminals. Since multiple users
receive a broadcast message, the responding status word must be suppressed. By
choosing the address method to accomplish the broadcast mode, all the other formats
of the command word are available for use. Broadcast messages can be used with
subaddresses and mode codes. The subaddress in a broadcast message can allow
multiple users with the broadcast reception capability to sort out specific broadcast
messages transmitted, if given this capability in hardware or software. Therefore,
multiple sets of broadcast messages can be defined. In addition, the broadcast format
can be used with some mode codes. This allows simultaneous reception of these mode
commands by terminals.
Designers must consider carefully discarding the command-response format, in which
all message completion failures are known to the bus controller, for the benefits of
using broadcast message transfers. Broadcast use may increase system operation
complexity since subaddresses of broadcast address and addressed terminal are not
likely to be the same. This requires additional sub addresses .
Proper use of the broadcast mode may yield benefits by allowing simultaneous
communication with remote terminals and may also reduce bus traffic.
24.1 Bus Controller to Remote Terminal(s) Transfer (Broadcast)
The bus controller shall issue a receive command word with 11111 in the RT address field
followed by the specified number of data words. The command words and data words shall be
transmitted in a contiguous fashion with no gap. The RT(s) with the broadcast options shall,
after necessary validation, set the broadcast command received bit in the status word as
specified in clause 15.8 and shall not transmit the status word.
24.2 Remote Terminal to Remote Terminal(s) Transfer (Broadcast)
The bus controller shall issue a receive command word with 11111 in the RT address field
followed by a transmit command to RTA using that RT's address. RTA shall, after command
verification, transmit a status word followed by the specified number of data words. The
status and data words shall be transmitted in a contiguous fashion with no gap. The RT(s)
with the broadcast option, excluding RT A, shall after message validation set the broadcast
(505) 875-0600
1-800-SBS-1553
Message Formats
25
received bit in the status word as specified in clause 15.8 and shall not transmit the status
word.
The single and broadcast receiver data message formats are shown on Figure 12 and
Figure 11.
Bus Controller to Remote Terminal
Command
Word
Data
Word
Data
Word
Status
Response
**

Address: Unique - 31
Subaddress: Unique - 31 and 32
Word Count: 1-32
T/R: Receive
Remote Terminal to Bus Controller

Command
Word
Status
Response
**
Data
Word

Address: Unique - 31
Word Count: 1-32
T/R: Transmit
Data
Word
Data
Word
Number of Data Words Required
Remote Terminal to Remote Terminal

Command
Word
Address: Unique (A) - 31
Subaddress: Unique - 31
and 32
Word Count: 1-32
T/R: Receive
Command
Word
Status
Response
**
Data
Word
Data
Word
**
Source: Receiver (B)

Address: Unique (B) - 31
and 32
Word Count: 1-32
T/R: Transmit
Status
Response
Source: Receiver (A)
Notes
** Response Time
# Intermessage Gap
Figure 12: Single Receiver Data Message Formats

Bus Controller to Remote Terminals
Command
Word
Data
Word
Data
Word
Data
Word
Status
Response
Data
Word

Address: 31 (11111)
Word Count: 1-32
T/R: Receive
Remote Terminal to Remote Terminals

Command
Word
Command
Word

Address:31 (11111)
and 32
Word Count: 1-32
T/R: Receive

Address: Unique (A) - 31
and 32
Word Count: 1-32
T/R: Transmit
**
Data
Word
Data
Word
Source: Receiver (A)
Notes
** Response Time
# Intermessage Gap
Figure 11: Multiple Receiver Data Message Formats
(505) 875-0600
1-800-SBS-1553
26
24.3 Mode Command Without Data Word (Broadcast)
The bus controller shall issue a transmit command word with 11111 in the RT address field
and a mode code specified in Table 1. The RT(s) with the broadcast option shall, after
message validation, set the broadcast received bit in the status word as specified in clause
15.8 and shall not transmit the status word.
24.4 Mode Command with Data Word (Broadcast)
The bus controller shall issue a receive command word with 11111 in the RT address field and
a mode code specified in Table 1, followed by one data word. The command word and data
word shall be transmitted in a contiguous fashion with no gap. The RT(s) with the broadcast
option shall, after message validation, set the broadcast received bit in the status word as
specified in clause 15.8 and shall not transmit the status word.
Mode command transfer formats are shown in Figure 13.

Mode Command without Data Word to a Single Receiver
Mode Code
Command
Status
Response
**
Transmit Mode Command with Data Word to a Single Receiver

Mode Code
Command
Status
Response
**
Data
Word
Mode Data Response
Receive Mode Command with Data Word to a Single Receiver

Mode Code
Command
Data
Word
Status
Response
**
Mode Data Word
Transmit Mode Command without Data Word to Multiple Receivers

Mode Code
Command
Transmit Mode Command with Data Word to a Multiple Receivers

Mode Code
Command
Data
Word
Mode Data Word
Notes
** Response Time
# Intermessage Gap
Figure 13: Mode Command Transfer Formats
25. Intermessage Gap

The bus controller shall provide a minimum gap time of 4.0 s between messages as shown in
Figure 9 and Figure 10. This time period, shown as T in Figure 14, is measured at point A of
the bus controller as shown in Figure 15 or Figure 16. The time is measured from the mid-bit
zero crossing of the last bit of the preceding message to the mid-zero crossing of the next
command word sync.
(505) 875-0600
1-800-SBS-1553
Message Formats
27
The purpose of this clause is to clearly identify that the bus controller shall not transmit
contiguous messages. There must be an intermessage gap so that any voltage build-up
can dissipate (see explanatory note for clause 36.1.4). There is not maximum gap time
specified. The bus controller may issue messages with gap time greater than or equal to
4 s.
26. Response Time
The RT shall respond, in accordance with clause 17 to a -valid command word within the time
period of 4.0 to 12.0 s. This time period, shown at T in Figure 14, is measured at point A of
the RT as shown in Figure 15 or Figure 16. The time is measured from the mid-bit zero
crossing of the last bit of the last word as specified in clause 17 and as shown in Figure 9 and
Figure 10 to the mid-zero crossing of the status word sync.
Bit Time
19
Bit Time
20
Parity Bit
Command/Status/Sync
+ Volts
0 Volts
- Volts
T
Note
T is the repsonse time of an RT (see clauses 26 and 27
Figure 14: Intermessage Gap and Response Time
The point of measurement of response time is identified on Figure 14 using the

previous mid-bit zero crossing and the next mid-bit crossing. Values of 4 and 12 s
would equate to 2 and 10 s, respectively of bus quiet time.
(505) 875-0600
1-800-SBS-1553
28
27. Minimum No-Response Timeout

The minimum time that a terminal shall wait before considering that a response as specified
in clause 26 has not occurred shall be 14.0 s. The time is measured from the mid-bit zero
crossing of the last bit of the last word to the mid-zero crossing of the expected status word
sync at point A of the terminal as shown on Figure 15 or Figure 16.
Bus Cable
Screen
Data Bus
Wire Pair
Isolation
Resistors
Screening
R = 0.75Zo + 2%
1:N
Coupling
Transformer
Stub of
Specified
Length
Isolation
Transformer
Transmitter/Receiver
Terminal
Figure 15: Data Bus Interface using Transformer Coupling
(505) 875-0600
1-800-SBS-1553
Message Formats
Bus Cable
Screen
Data Bus
Wire Pair
Screening
Stub of
Specified
Length
Isolation
Transformer
Transmitter/Receiver
Terminal
Figure 16: Data Bus Interface using Direct Coupling
(505) 875-0600
1-800-SBS-1553
29
30
The main intention of this clause is to specify the minimum time that a bus controller
shall wait after sending a command before concluding that the addressed remote
terminal (RT) is not going to respond before sending a subsequent command.
This clause can also be interpreted to apply to the receiving RT in a RT to RT transfer
to check for the correct response from the transmitting RT. This condition should, if
detected, prevent the receiving RT from remaining "open" to data from another source
if the transmitting RT does not respond to its command in time, and should cause the
RT to abort any operations associated with the first receive command.
Terminal Operation
28. Common Operation
Terminals shall have common operating capabilities as specified in the following clauses.
28.1 Word Validation
The terminal shall ensure that each word conforms to the following minimum criteria:
(a) The word begins with a valid sync field
(b) The bits are in a valid Manchester II code
(c) The information field has 16 bits plus parity
(d) The word parity is odd
When a word fails to conform to the preceding criteria, the word shall be considered invalid.
28.2 Transmission Continuity
The terminal shall verify that the message is contiguous as defined in Section E. Improperly
timed data syncs shall be considered a message error.
In this context, improperly timed data syncs relate to clauses 36.1.2 and 37.1.2 in
respect to the zero crossing accuracy expected for a transmitter.
For contiguous words, it is required that the time interval from the last zero crossing of
one word to the first zero crossing of the next word, measured at the transmitter into a
test load is 2 s + 25 ns. Given normal transmission characteristics, this will result in a
corresponding time interval at the receiver within 2 s + 150 ns. This interpretation is
based on the timing detail given in clauses 36.1.2 and 37.1.2.
28.3 Terminal Fail-Safe
The terminal shall contain a hardware implemented time-out to preclude a signal

transmission of greater than 800.0 s. This hardware shall not preclude a correct
transmission in response to a command. Reset of this time-out function shall be performed by
the reception of a valid command on the bus on which the time-out has occurred.
The above clauses describe the common operating capabilities that all terminals must
have whether operating as a bus monitor, remote terminal or bus controller. A time-out
function should be associated with each individual transmitter.
(505) 875-0600
1-800-SBS-1553
Terminal Operation
31
The purpose of the fail-safe timer is to stop a terminal from transmitting for longer than
800 s per message and hence protect the data bus. It should be noted that the fail-safe
timer under such transmitter fault conditions, will produce an 800 s transmission
every time the terminal receives a valid command. The Bus Controller must take
appropriate action to overcome this problem in these circumstances.
29. Bus Controller Operation
A terminal operating as a bus controller shall be responsible for sending data bus commands,
participating in data transfers, receiving status responses, and monitoring system status as
defined in this Standard. The bus controller function may be embodied as either a standalone
terminal whose sole function is to control the data bus(s), or contained within a subsystem.
Only one terminal shall be in active control of a data bus at any one time.
30. Remote Terminal

30.1 Operation
A remote terminal shall operate in response to valid commands received from the bus
controller. The remote terminal shall accept a command word as valid when the command
word meets the criteria of clause 28.1 and the word contains an address in the address field
which matches the remote terminal address, or, an address of 11111 if the RT has the
broadcast option.
30.2 Superseding Valid Commands
The RT shall be capable of receiving a command word on the data bus after the minimum
intermessage gap time as specified in clause 25 has been exceeded, when the RT is not in the
time period T as specified in clause 26 prior to the transmission of a status word, and when it
is not transmitting on that data bus. A second valid command word sent to an RT shall take
precedence over the previous command. The RT shall respond to the second valid command
as specified in clause 26.
The above clause is intended to clarify the superseding valid command requirement
particularly in respect of the gap time issue. If a bus controller fails to wait at least 12
s for an expected status word response from an RT, there is a possibility that a second
command transmitted by the bus controller would coincide with the status word.
Furthermore, if the controller should replace a data word in a contiguous message
(controller to RT transfer) with a valid command word to the receiving remote
terminal, the RT should ignore it and deem the message to have failed, i.e., suppress the
status word response.
The intended purpose for this requirement is to allow the bus controller to reissue an
identical transmission when an RT fails to respond to a command on that bus or issue a
new transmission in similar circumstances. The minimum no-response time-out
requirement is specified in clause 27. By insertion of the specified delay, the bus
controller is assured that the RT is not responding and thus a new command on the
same bus will not be corrupted.
The comments made above only relate to activity on the same bus, and it should be
noted that with dual or multi-bus configurations, clause 41.2 applies, which does not
(505) 875-0600
1-800-SBS-1553
32
require the controller to wait for activity to cease on the current bus before sending a
new command on a redundant bus.
30.3 Invalid Commands
A remote terminal shall not respond to a command word which fails to meet the criteria
specified in clause 30.1.
30.4 Illegal Command
An illegal command is a valid command as specified in clause 28 where the bits in the
subaddress/mode code field, word count/mode code field, and the transmit/receive bit indicate
a mode command, subaddress, and/or word count that has not been implemented in the RT. It
is the responsibility of the bus controller to ensure that no illegal commands are sent out. The
RT designer has the option of monitoring for illegal commands. If an RT that is designed with
this option detects an illegal command and the proper number of contiguous valid data words
as specified by the illegal command word, it shall respond with a status word only, setting the
message error bit, and not use the information received.
Illegal commands are command words which have passed the word validation test, but
do not comply with the systems capability. These include command words where the
subaddress/mode code field, data word/mode code field, or the T/R bit are set such that
they represent conditions not allowed in the system. These include both conditions not
allowed by the Standard and any additional conditions not allowed in a particular
system design. The remote terminal designer has the option to trap any or all these
illegal commands. The responsibility for not allowing illegal commands to be
transmitted is given to the bus controller. Since the bus controller is responsible for all
command/response message communications, it will be a design goal that the bus
controller shall not transmit an illegal command.
30.5 Valid Data Reception
The remote terminal shall respond with a status word when a valid command word and the
proper number of contiguous valid data words are received, or a single word associated with
a mode code is received. Each data word shall meet the criteria specified in clause 28.1.
This requirement identified that a status word is transmitted only if the command word
is valid, the data words are valid and contiguous and that the proper number of data
words are received. It should be noted that other message formats also produce a
status word response, e.g., mode code without data word transmitted to a specific RT
(not broadcast).
It must also be noted that when the broadcast command option is used, status word
response from RTs implementing this option are suppressed (see clause 24).
30.6 Invalid Data Reception
Any data word(s) associated with a valid receive command that does not meet the criteria
specified in clause 28.1 and 28.2, or an error in the data word count, shall cause the remote
terminal to set the message error bit in the status word to a logic one and suppress the
transmission of the status word. If a message error has occurred, then the entire message
shall be considered invalid.
(505) 875-0600
1-800-SBS-1553
Data Bus Characteristics
33
When considering RT validation procedures, it should be remembered that an RT is

always required to listen to the traffic on any bus to which it is connected except when
transmitting on that bus. Also, all command words must pass the validation criteria
described in clause 30.1 before an RT recognizes their existence. This includes mode
commands without data words. It is absolutely essential that an RT ignore invalid
commands. Once the command word has been validated, if one or more data words are
contained in the message, the RT must check such words for their validity as described
in clause 30.6.
In all cases except broadcast mode, suppression or non-return of the status word alerts
the bus controller of malfunction. The level of error recovery that must occur will
depend on the bus controllers message error algorithms. Options available might
include request for the RT status word or last valid command word.
It should be noted that a requirement of the Standard is that the entire message be
considered invalid in the event of any error being detected.
31. Bus Monitor Operation
A terminal operating as a monitor shall receive bus traffic and extract selected information.
While operating as a bus monitor, the terminal shall not respond to any message except one
containing its own unique address if one is assigned. All information obtained while acting as
a monitor shall be strictly used for off-line applications (e.g., flight test recording,
maintenance recording, or mission analysis) or to provide the back-up bus controller with
sufficient information to take over as the bus controller.
A terminal generally operates as a bus monitor either as a stand-alone unit taking no

active part in the bus operation, apart from listening, or as part of a remote terminal
performing a monitoring function for potential bus control in the event of bus controller
failure.
For further details of operation as a bus monitor, see the explanatory note for clause
15.5.

32. Cable
32.1 Cable Type
The cable used for the main bus and all stubs shall be a two conductor, twisted, screened,
overall insulated cable. The line-to-line distributed capacitance shall not exceed 30.3 pF/ft
(98.4 pF/m). The cable shall be formed with not less than four twists per foot (13 twists/m)
where a twist is defined as a 360 degree rotation of the wire pairs. The cable screen shall
provide a minimum of 75% coverage.
32.2 Characteristic Impedance
The nominal characteristic impedance of the cable (ZO) shall be within the range 70.0 ohms
to 85.0 ohms at a nominal sinusoidal frequency of 1.0 MHz.
(505) 875-0600
1-800-SBS-1553
34
32.3 Cable Attenuation
At the frequency of I MHz (see clause 32.2), the cable attenuation shall not exceed l .5
decibels (dB) / 100 ft (4.92 dB / 100 m).
32.4 Cable Termination
The two ends of the cable shall be terminated with a resistance equal to the selected cable
nominal characteristic impedance (ZO) + 2.0%.
The specification figures quoted in this part of the Standard represent worst cases and
therefore in most practical applications improvements should be sought wherever
possible.
33. Cable Stub Requirements
Stubbing is the method by which a separate cable is connected between the primary data bus
and a terminal. The two methods of connecting stubs to the data bus are as shown on Figure
15 and Figure 16. However, the preferred method of connecting stubs to the data bus is to use
transformer coupling as shown on Figure 15; this method provides increased dc isolation,
increased common mode protection and less mix-matching to the data bus.
Lengths of all stubs should be kept as short as possible.
The main data bus is terminated at each end in the cable characteristic impedance to
minimize reflections due to transmission line mismatch.
With no stubs attached, the main bus looks like an infinite length transmission line, and
thus there are no disturbing reflections. When stubs are added for connection of the
terminals, the bus is loaded locally and a mismatch occurs with resulting reflections.
The degree of mismatch and signal distortion due to reflections are a function of the
impedance (Z) presented by the stub and terminal input impedance. In order to
minimize signal distortion, it is desirable to maintain a high stub impedance reflected
back to the main bus. At the same time the impedance needs to be kept low so that
adequate signal power will be delivered to the receiver input. A trade-off and
compromise between these conflicting requirements is necessary to achieve the
specified signal to noise ratio and system error rate performance. Two methods for
coupling a terminal to the main bus are defined, i.e., transformer coupling and direct
coupling (see Figure 22).
Transformer coupling is usually used with long stubs (1 to 20 ft) and requires a coupler
box, separate from the terminal, incorporating the junction of the main bus and stub.
Direct coupling is usually limited to use with stubs of less than one foot. Fault isolation
resistors (r) are included to provide protection for the main bus in case of a short
circuit in the stub or terminal. The coupling transformer characteristics defined in
clause 34.2, provide a compromise for the signal level and distortion characteristics
delivered to the terminals. The coupling transformer turns ratio (2 to 1) provides
beneficial impedance transformation for both terminal reception and transmission. The
direct coupling option is provided for use in small and relatively simple systems where
the cost of using transformer coupling becomes significant; however, the technical
trade-offs in doing so must be considered.
(505) 875-0600
1-800-SBS-1553
35
A plot of the calculated first order magnitude stub impedance (Z) against stub length is
presented on Figure 17. From this it is evident that the stub impedance is significantly
increased by the use of the coupling transformer.
Terminal Input Impedance (Z I) = 1k Except Where Noted
Coupling Transformer 2:1 Turns Ratio
Isolation Resistors - 52.5
Cable Capacitance - 30 pF/Ft
2200
2000
1800
1600
Transformer Coupled
(Ideal Transformer)
1400
Stub Impedance
()
1200
Direct Coupled
(ZI = 2k)
1000
Transformer Coupled
(Transformer as in Clause 34.2)
800
600
400
Direct Coupled
(ZI = 1k)
(shown for comparison)
200
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Stub Length (feet)
Figure 17: Stub Impedance V Length Variation (Calculated)
The major differences between the requirements of transformer and direct coupled
stubs are the positioning of the isolation resistors for the direct coupled (short stub)
connection and the characterization of the coupling transformer in the long stub
(transformer coupled) connection. With the isolation resistors located in the terminal
for the direct coupled case, the need for a separate coupler box is eliminated as long as
a reliable, screened connection can be made. In most cases, the bus connections can be
spliced in the cable connector which mates with the terminal connector.
The coupling transformer characteristics are very important to the signal integrity and
noise performance of the data bus system. The purpose of this form of coupling is to:
1. Provide isolation of the main bus from fault conditions on the stub or in the terminal
2. Provide reduced signal distortion effects by increasing the effective stub impedance
3. Provide termination of the stub when transmitting from the terminal
(505) 875-0600
1-800-SBS-1553
36
4. Prevent common mode noise on the data bus from entering the stub so that the stub
transformer has only to reject locally induced common mode noise
The isolation resistors and the transformer turns ratio (2: 1) provide the benefits listed
above.
34. Transformer Coupled Stubs
34.1 Stub Length
The length of a transformer coupled stub should not exceed 20 ft (6.1m).

34.2 Coupling Transformer
A coupling transformer, as shown on Figure 15, shall be required. This transformer shall
have a turns ratio of 1:1.41 + 3% with the higher number of turns on the isolation resistor
side of the stub.
The use of transformers provides electrical isolation, impedance matching, and

rejection of common mode noise. Incorrectly designed transformers, however, can
cause considerable problems, e.g., signal distortion, line reflection, and high bit error
rate.
As indicated above, the 2:1 transformer provides termination of the stub for
transmission of signals from the terminal to the main bus when the impedance at point
B in Figure 22 looking into the stub ZB is:
1. ZB = (ZO/2) + 2R
Where R = 0.75 ZO
2. ZB = 0.5ZO + l.5ZO = 2ZO ohms
The reflected impedance, ZR, from the bus to the stub due to the transformer
impedance transformation is:
3. ZR = (ZB/22) = (2ZO/2) =ZO
Therefore, the coupling transformer specified provides the characteristics desired for
reducing reflections and maintaining signal levels for systems where long stubs are
required.
34.2.1 Transformer Input Impedance
The open circuit impedance as seen at point B on Figure 18 shall be greater than 3 kilohms
over the frequency range 75.0 kHz to 1.0 MHz, when measured with a nominal I V RMS sine
wave.
The transformer open circuit impedance (ZOC) is required to be greater than 3 kilohms.
The measurement is made looking into the higher turns winding with a 75 kHz to 1
MHz sine wave signal.
(505) 875-0600
1-800-SBS-1553
37
R = 360 + 5%
1 : 1.41
Output B
R
C
A
Percent Droop = C/D x 100
Figure 18: Coupling Transformer
The test amplitude at the transformer winding is adjusted to l V RMS. The critical
factors in achieving the 3 kilohms ZOC is the distributed capacitance of the windings and
the transformer primary inductance. The inductance of the transformer must be large
enough to provide the open circuit impedance at 75 k HZ while the distributed
capacitance should be small enough to maintain the open circuit impedance at the l
MHz test frequency. Note that because these transformers have a resonant point in the
frequency range 75 kHz to l MHz, at which input impedance peaks, it important to take
such measurements over the above frequency range. The inductance may obviously be
increased by increasing the number of turns on the transformer. This technique,
however, tends to increase the distributed capacitance, degrading high frequency
performance and therefore causing waveform integrity and common mode rejection to
suffer.
The transformer is a very important element in determining the transceiver
characteristics such as input impedance, signal waveform integrity, and common mode
rejection required by 1553. The considerations for transformer and associated
input/output circuit design are:
Provide the specified input impedance at high frequencies (terminal input impedance 1
kilohms or 2 kilohms at 1 MHz)
Maintain waveform integrity and low percentage droop for the lower frequency
conditions (less than 20% for 250 kHz square wave)
Design for low interwinding capacitance to help achieve the common mode rejection
figure specified for the receiver (45 dB CMR at + 10 V p, dc to 2 MHz)
These considerations are also directly applicable to the design of the transceiver
transformer. In addition to the transformer characteristics, other considerations for
maintaining the terminal input impedance specification are as follows:
(505) 875-0600
1-800-SBS-1553
38
Minimize stray capacitance of wiring from the external connector and on the circuit
card to the buffer amplifier (every 100 pF results in approximately 1.6 kilohms shunt
impedance at 1 MHz).
Maintain high impedance at the receiver limiter and filter circuit inputs and transmitter
driver outputs on the off state. This impedance must be maintained with the terminal
(transceiver) power off.
34.2.2 Transformer Waveform Integrity
The droop of the transformer using the test configuration shown on Figure 18 at point B,
shall not exceed 20.0%. Overshoot and ringing as measured at point B shall be less than +
1.0 V peak. For this test, R shall equal 360.0 ohms + 5% and the input A on Figure 18 shall
be a 250.0 kHz square wave, 27.0 V peak to peak, with neither rise nor fall time greater than
100 ns.
The ability of the coupler transformer to provide a satisfactory signal is specified in the
droop, overshoot and ringing requirements shown on Figure 18 and Figure 20. Droop
is specified at 20% maximum when driving the transformer with a 250 kHz, 27 V peak
to peak square wave about zero. The test for the droop characteristic is made by
driving the low turns winding through a 360 ohms resistor and measuring the signal at
the open circuited high side winding. The droop of the transformer is determined
mainly by the primary inductance. Since the primary inductance also provides the 3
kilohms open circuit impedance, the inductance should be made as high as possible
without degrading the high frequency performance of the transformer. Ringing and
overshoot on the transformer signal is also shown in Figure 20. The + 1 V limit on
these high frequency perturbations can be achieved through careful attention to leakage
inductance and transformer capacitance.
34.2.3 Transformer Common Mode Rejection
The coupling transformer shall have a common mode rejection ratio greater than 45.0 db at I
MHz.
Terminal
A
RL
Figure 19: Terminal Input/Output Characteristics for Transformer Coupled Stubs

and Direct Coupled Stubs
The common mode rejection of the isolation transformer is required to be greater than
45.0 dB. The common mode test shown in Figure 19 and Figure 21 consists of driving
(505) 875-0600
1-800-SBS-1553
39
the low turns winding with approximately 2 V while measuring the differential signal
across the high turns winding. Common mode rejection can be improved by minimizing
the interwinding capacitance and the core to winding capacitance.
360
27 V P.P
A
B Output
250 kHz
1 : 1.41
Transformer Under Test
Test Configuration
+ 1V M
ax
ED
Ep
Ep
ED
Note
% Droop =
+ 1V
x 100
Max
ED
Ep
Output Waveform
Figure 20: Waveform Test
34.3 Fault Isolation
An isolation resistor shall be place in series with each connection to the data bus cable. This
resistor shall have a value of 0.75 ZO ohms + 2%, where ZO is the selected cable nominal
characteristic impedance. The impedance placed across the data bus cable shall be no less
than 1.5 ZO ohms for any failure of the coupling transformer, cable stub, or terminal
transmitter/receiver.
(505) 875-0600
1-800-SBS-1553
40
Transformer Under Test
eo
1 : 1.41
1 MHz
ecm
Notes:
1. Common mode rejection (CMR) > 45 db
ecm
i.e., CMR = 20 log 10 e
0
2. Care should be taken in the layout of the wiring when carrying out this test
Figure 21: Common Mode Test

34.4 Cable Coupling
All coupling transformers and isolation resistors, as specified in clauses 34.2 and 34.3 shall
have a continuous screen which shall provide a minimum of 75% coverage. The isolation
resistors and coupling transformers shall be placed at the minimum possible distance from
the junction of the stub to the main bus.
34.5 Stub Voltage Requirements
Every data bus shall be designed such that all stubs at point A on Figure 15 shall have a line
to line voltage of peak to peak amplitude within the range 1.0 to 14.0 V for a transmission by
any terminal on the data bus. This shall include the maximum reduction of a data bus signal
amplitude in the event that one of the terminals has a fault which causes it to reflect a fault
impedance specified in clause 34.3 on the data bus. This shall also include the worst case
output voltage of the terminals as specified in clauses 36.1.1 and 37.1.1.
35. Direct Coupled Stubs

35.1 Stub Length
The length of a direct coupled stub should not exceed 1 ft (300 mm). The use of direct coupled
stubs should be avoided if possible (see clause 33).
35.2 Fault Isolation
An isolation resistor shall be placed in series with each connection to the data bus cable. This
resistor shall have a value of 55.0 ohms + 2%. The isolation resistors shall be placed within
the RT as shown on Figure 16.
35.3 Cable Coupling
All bus stub junctions shall have a continuous screen which must provide a minimum of 75%
coverage.
(505) 875-0600
1-800-SBS-1553
Terminal Characteristics
41
35.4 Stub Voltage Requirements
Every data bus shall be designed such that all stubs at point A on Figure 16 shall have a line
to line voltage of peak to peak amplitude within the range 1.4 to 20.0 V for a transmission by
any terminal on the data bus. This shall include the maximum reduction of a data bus single
amplitude in the event that one of the terminals has a fault which causes it to reflect a fault
impedance of 110 ohms on the data bus. This shall also include the worst case output voltage
of the terminals as specified in clauses 36.1.1 and 37.1.1.
See clause 33 for the explanatory detail on cable stubs and Figure 22 for diagrammatic
comparison of the two types of stub interface to the data bus.
Data Bus
Coupler
1.41 : 1
N:1
Direct Coupled Stub

Transformer Coupled Stub
R = Isolation Resistor
N = Transformer Turns Ratio
Figure 22: Stub Interfaces to the Data Bus
36. Terminals with Transformer Coupled Stubs
36.1 Terminal Output Characteristics
The following characteristics shall be measured with RL, as shown on Figure 19, equal to
70.0 ohms + 2.0%.
36.1.1 Output Levels
The terminal output voltage levels shall be measured using the test configuration shown in
Figure 19. The terminal line to line output voltage shall be between 18.0 and 27.0 V, peak to
peak, when measured at point A on Figure 19.
(505) 875-0600
1-800-SBS-1553
42
The driving requirements for both direct and transformer coupled configurations are so
arranged as to provide the same nominal bus voltage.
36.1.2 Output Waveform
The waveform, when measured at point A on Figure 19, shall have zero crossing deviations
which are equal to, or less than, 25.0 ns from the ideal crossing point, measured with respect
to the previous ideal zero crossing (i.e., 0.5 + 0.025 s, 1.0 + 0.025 s, 1.5 + 0.025 s and
2.0 + 0.025 s). The rise and fall time of this waveform ndividually shall be from 100.0 to
300.0 ns when measured from levels of 10% to 90% of the full line to line voltage waveform
as shown on Figure 23. Any distortion of the waveform including overshoot and ringing shall
not exceed + 900.00 mV peak, as a line to line voltage when measured at point A on Figure
19.
1 microsecond
+ Volts
90
0 Volts
50
- Volts
10
100-300 nanoseconds
Figure 23: Output Waveform

36.1.3 Output Noise
Any noise transmitted when the terminal is receiving or has power removed, shall not exceed
a line to line value of 14.0 mV RMS measured at point A on Figure 19.
Noise is normally specified as an RMS value since peak noise is difficult to measure.
the output RMS noise for the transformer coupled and direct coupled cases are
specified in clauses 36.1.3 and 37.1.3 and are consistent with the required system
performance and practical terminal hardware design. The requirement for low output
noise of either 14 mV RMS or 5 mV RMS when not transmitting also places significant
constraints on the length and routing of input/output wiring due to the induced power
supply and logic noise generated in the terminal.
(505) 875-0600
1-800-SBS-1553
43
36.1.4 Output Symmetry
From the time beginning 2.5 s after the mid-bit crossing of the parity bit of the last word
transmitted by a terminal, the maximum line to line voltage at point A on Figure 19 shall be
not greater than + 250.0 mV peak. This shall be tested with the terminal transmitting the
maximum number of words it is designed to transmit, up to 33. This test shall be run six times
with each word in a contiguous block of words having the same bit pattern. The six word
contents that shall be used are 800016, 7FFF16, 000016, FFFF16, 555516, and AAAA16.
The output of the terminal shall be as specified in clauses 36.1.1 and 36.1.2.
An ideal waveform is perfectly balanced so that the signal energy on both sides of zero
(off) level is identical. If the positive and negative energy are not equal, problems can
develop in the coupling transformers and the transmission line can acquire a charge
which appears as a tail with overshoot and ringing when transmission is terminated.
These considerations require that the symmetry of the transmitted waveform be
controlled as far as possible within practical limits. This is accomplished by specifying
the signal level from a time beginning 2.5 s after the mid-bit zero crossing of the
parity bit of the last word in a message transmitted by the terminal under test. The test
messages contain the maximum number of words and defined bit patters.
36.2 Terminal Input Characteristics
The following characteristics shall be measured independently.

36.2.1 Input Waveform Compatibility
The terminal shall be capable of receiving and operating with the incoming signals specified
below, and shall accept waveforms varying from a square wave to sine wave with a maximum
zero crossing deviation from the ideal with respect to the previous ideal zero crossing of +
150 ns (i.e., 2.0 + 0.15 s, 1.5 + 0.15 s, 1.0 + 0.15 s, 0.5 + 0.15 s). The terminal shall
respond to an input signal whose peak to peak amplitude, line to line is within the range 0.86
V to 14.0 V. The terminal shall not respond to an input signal whose peak to peak amplitude,
line to line is within the range 0.0 to 0.20 V. The voltages are measured at point A on Figure
15.
36.2.2 Common Mode Rejection
Any signals from direct current (dc) to 2.0 MHz with amplitudes equal to or less than + 10.0
V peak, line to ground, measured at point A on Figure 15, shall not degrade the performance
of the receiver.
The response/no response threshold levels chosen for a particular system should be
consistent with the noise environment for that system.
36.2.3 Input Impedance
The magnitude of the terminal input impedance, when the RT is not transmitting, or has
power removed, shall be a minimum of 1.0 kilohms within the frequency range 75.0 kHz to 1.0
MHz. This impedance is that measured line to line at point A on Figure 15.
As indicated in the data bus network requirement, input impedance is required to be

maintained at a reasonable level to reduce the signal distortion effects when terminals
(505) 875-0600
1-800-SBS-1553
44
are connected to the bus. Terminal input impedance is determined primarily by the
following:
1. Transformer impedance - maintains inductance required to support low frequency
component of signal while controlling interwinding capacitance for high frequencies.
2. Terminal wiring capacitance - controlling stray capacitance wiring from terminal
connector to receiver.
3. Secondary impedance transformation - for the transformer coupled case, a transformer
with a turns ratio of 1 to 2 is implied. The impedance at the secondary is reflected to
the terminal input reduced by a factor of 2.
The factor of 2 difference in the impedance specified for the transformer coupled and
direct coupled cases is based primarily on the effect of (3) above. The frequency range
was set with its lower limit of 75 kHz to provide assurance that adequate transformer
volt-time product (inductance) is available to support the lower frequencies of the
signal without approaching saturation.
36.2.4 Noise Rejection
The terminal shall exhibit a maximum word error rate of one in 107 on all words received by
the terminal, after validation checks as specified in clause 28, when operating in the presence
of additive white Gaussian noise distributed over a bandwidth of 1.0 kHz to 4.0 MHz at an
RMS amplitude of 140 mV. A word error shall include any fault which causes the message
error bit to be set in the terminals status word, or one which causes a terminal to not respond
to a valid command. The word error rate shall be measured with a line to line input of 2.1 V
peak to peak to the terminal as measured at point A on Figure 15. The noise tests shall be run
continuously until, for a particular number of failures, the number of words received by the
terminal, including both command and data words, exceeds the required number for
acceptance of the terminal, or is less than the required number for rejection of the terminal,
as shown on Table 2. All data words used in the tests shall contain random bit patterns. These
bit patterns shall be unique for each data word in a message, and shall change randomly
from message to message.
The specified test conditions of signal, and noise (measured at the half power points
i.e., 3 dB) were selected to produce a value of word error rate (WER) which is
sufficiently low (10-7) to permit performance verification of a terminal receiver within a
reasonable test period. The number of detected errors is to be measured using a test
configuration typical of that shown on Figure 24.
A diagrammatic representation of Table 2 showing the criteria for RT acceptance or
rejection for the noise test is given on Figure 25. Note that this is a physical test to
assess the quality of specific terminal hardware and is not an indication of system
performance. The noise rejection is a figure of merit test and can be performed in a
normal laboratory environment using the terminals data bus connection. In this case,
the number of no responses must be counted to give the number of detected error
events. For the purpose of the test, the message error condition can be accepted as the
number of word errors, since the probability of having 2 errors in any single message is
extremely low.
(505) 875-0600
1-800-SBS-1553
45
Signal
Monitor
Pattern
Generator
Signal +
Noise
Transmitter
Terminal Detector
Detected
Errors
Remote Terminal
Noise
Generator
Figure 24: Typical Noise Rejection Test Setup
37. Terminals with Direct Coupled Stubs

37.1 Terminal Output Characteristics
The following characteristics shall be measured with RL as shown on Figure 19, equal to
35.0 ohms + 2.0%.
37.1.1 Output Levels
The terminal output voltage levels shall be measured using the test configuration shown on
Figure 19. The terminal line to line output voltage shall be between 6.0 and 9.0 V peak to
peak when measured at point A on Figure 19.
37.1.2 Output Waveform
The waveform, when measured at point A on Figure 19, shall have zero crossing deviations
which are equal to, or less than 25.0 ns from the ideal crossing point, measured with respect
to the previous ideal zero crossing (i.e., 0.5 + 0.025 s, 1.05 + 0.025 s, 1.55 + 0.025 s,
and 2.05 + 0.025 s). The rise and fall time of this waveform individually shall be from 100.0
to 300.0 ns when measured from levels of 10% to 90% of the full line to line voltage waveform
as shown in Figure 23. Any distortion of the waveform including overshoot and ringing shall
not exceed + 300.0 mV peak, as a line to line voltage when measured at point A on Figure 19.
(505) 875-0600
1-800-SBS-1553
46
Not Applicable
40
35
Reject
Te
st
in
g
C
on
tin
ue
Total Number of Errors
30
25
20
15
Accept
10
12
15
18
21
24
27
30
33
Time on Test (Words 10 7)
Figure 25: Test Chart Showing Criteria for Acceptance or Rejection of a Remote
Terminal for the Noise Test
37.1.3 Output Noise
Any noise transmitted when the terminal is receiving, or has power removed, shall not exceed
a line to line value of 5.0 mV RMS measured at point A on Figure 19.
See clause 36.1.3 for explanatory detail.

37.1.4 Output Symmetry
From the time beginning 2.5 ms after the mid-bit crossing of the parity bit of the last word
transmitted by a terminal, the maximum line to line voltage at point A on Figure 19 shall be
no greater than + 90.0 mV peak. This shall be tested with the terminal transmitting the
maximum number of words it is designed to transmit, up to 33. This test shall be run six times
with each word in a contiguous block of words having the same bit pattern. The six word
contents than shall be used are 800016, 7FFF16, 000016, FFFF16, 555516, and AAAA16.
The output of the terminal shall be as specified in clauses 37.1.1 and 37.1.2.
(505) 875-0600
1-800-SBS-1553
47
37.2 Terminal Input Characteristics
The following characteristics shall be measured independently.

37.2.1 Input Waveform Compatibility
The terminal shall be capable of receiving and operating with the incoming signals specified
below, and shall accept waveforms varying from a square wave to a sine wave with a
maximum zero crossing deviation from the ideal with respect to the previous ideal zero
crossing of + 150 ns (i.e., 2.0 + 0.15 s, 1.50 + 0.15 s, 1.00 + 0.15 s, 050 + 0.15 s). The
terminal shall respond to an input signal whose peak to peak amplitude, line to line, is within
the range 1.2 to 20.0 V. The terminal shall not respond to an input signal whose peak to peak
amplitude, line to line, is within the range 0.0 to 0.28 V. The voltages are measured at point A
on Figure 16.
37.2.2 Common Mode Rejection
Any signals from dc to 2.0 MHz, with amplitude equal to or less than + 10.0 V peak, line to
ground, measured at point A on Figure 16, shall not degrade the performance of the receiver.

37.2.3 Input impedance
The magnitude of the terminal input impedance when the RT is not transmitting, or has power
removed, shall be a minimum of 2 kilohms within the frequency range 75.0 kHz to 1.0 MHz.
This impedance is that measured line to line at point A on Figure 16.
37.2.4 Noise Rejection
The terminal shall exhibit a maximum word error rate of one in 107 on all words received by
the terminal, after validation checks as specified in clause 28, when operating in the presence
of additive white Gaussian noise distributed over a bandwidth of 1.0 kHz to 4.0 MHz at an
RMS amplitude of 200 mV. A word error shall include any fault which causes the message
error bit to be set in the terminals status word, or one which causes a terminal to not respond
to a valid command. The word error rate shall be measured with a line to line input of 3.0 V
peak to peak to the terminal as measured at point A on Figure 16. The noise test shall be run
continuously until, for a particular number of failures, the number of words received by the
terminal, including both command and data words, exceeds the required number of
acceptance of the terminal, or is less than the required number of rejection of the terminal, as
shown on Table 2. All data words used in the tests shall contain random bit patterns. These
bit patterns shall be unique for each data word in a message, and shall change randomly
from message to message.
(505) 875-0600
1-800-SBS-1553
48
Table 2: Criteria for Acceptance or Rejection of a Terminal for the Noise

Rejection Test
Total Number of
Words Received
x107
No. of
Errors
(a)
Reject
(equal or
less)
(b)
Accept
(equal or
more)
(c)
Total Number of
Words Received
x107
No. of
Errors
(d)
Reject
(equal or
less)
(e)
Accept
(equal or
more
(f)
NIA
4.40
21
12.61
21.43
N/A
5.21
22
13.42
22.24
N/A
6.02
23
14.23
23.05
N/A
6.83
24
15.04
23.86
N/A
7.64
25
15.85
24.67
N/A
8.45
26
16.66
25.48
0.45
9.27
21
17.47
26.29
1 26
10.08
28
18.29
27.11
2 07
10.89
29
19.10
27.92
2.88
11.70
30
19.90
28.73
10
3.69
12.51
31
20.72
29.54
11
4.50
13.32
32
21.53
30.35
12
5.13
14.13
33
22.34
31.16
13
6 12
14.94
34
23.15
31.97
14
6 93
15.75
35
23.96
32.78
15
7.74
16.56
36
24.77
33.00
16
8.55
17.37
37
25.58
33.00
17
9.37
18.19
38
26.39
33.00
18
10.18
19.00
39
27.21
33.00
19
10.99
19.81
40
28.02
33.00
20
11.80
20.62
41
33.00
N/A
(505) 875-0600
1-800-SBS-1553
Notices to U.S. MIL-STD-1553B
49
Redundant Data Bus Requirements

38. General
If redundant data buses are used, the requirements as specified in clauses 39 and 40 below
shall apply to those data buses. One method of implementing a redundant data bus system is
defined in clause 41.
39. Electrical Isolation

All terminals shall have a minimum of 45 dB isolation between data buses. Isolation here
means the ratio in decibels between the output voltage on the active data bus and the output
voltage on the inactive data bus. This shall be measured using the test configuration specified
in clause 36.1 or 37.1 for each data bus. Each data bus shall in turn be activated, with all
measurements being taken at point A on Figure 19 for each data bus.
40. Single Event Failures

All buses shall be routed to minimize the likelihood that single event causes the loss of more
than one data bus.
Note: Both physical and electrical considerations should be taken into account.
41. Dual Standby Redundant Data Bus

If a dual standby redundant data bus is used, then it shall be as specified below.
41.1 Data Bus Activity
Only one data bus can be active at any given time except as specified in clause 41.2.
41.2 Reset Data Bus Transmitter
If, while operating on a command, a terminal receives another valid command from either
data bus, it shall reset and respond to the new command on the data bus on which the new
command is received. The terminal shall respond to the new command as specified in clause
26.
This clause allows the controller to interrupt activity to or from a remote terminal by
sending a valid command to the same remote terminal on a redundant bus. In this case
it does not have to meet the minimum no response time out requirement specified in
clause 27 in relation to superseding valid command on the same bus (clause 30.2).

42. General
Two notices to MIL-STD-1553B (Notice 1 and Notice 2) have been published. Notice
2 supersedes Notice 1. The main requirements of the notices are given below.
(505) 875-0600
1-800-SBS-1553
50
43. Notice 1
Notice 1 is specific to USAF and addresses the following areas:
The following Mode Commands not to be issued by bus controllers:
Dynamic Bus Control
Inhibit Terminal Flag
Override Inhibit Terminal Flag
Selected Transmitter Shutdown
Override Selected Transmitter Shutdown
Broadcast Commands not to be issued by bus controllers
Mode Indicators 00000 and 11111 both to be usable by bus controllers
Cable shielding to be 90% minimum
Shielding of cable coupling to be 90% minimum and continuous
Direct coupled stubs not allowed
All buses must be dual standby redundant
Actual bus impedance to be in range 70-85%
44. Notice 2
Notice 2 has US Tri-service applicability and revisits all these areas yet again but also
addresses:
Terminal addresses to be externally selectable
A minimum set of mode codes is specified
The reset remote terminal mode command not to require more than 5 milliseconds to
complete
All transmitted status words shall contain valid information (including on Power Up)
Status bit requirements defined more fully
Use of broadcast option restricted to mode codes but broadcast capability required in
bus controllers and optional in RTs
Data wraparound capability introduced
US Army and Air Force applications would not use direct coupled stubs
Power on/off noise restriction introduced
RT to RT message time-out introduced
(505) 875-0600
1-800-SBS-1553
51
Table 3: Cross Reference to U.S. MIL-STD-1553B
MIL-STD-1553B
Paragraph Number
1.
2.
3.
Introduction
Scope
Purpose
Definition of Terms
1.1
1.2
3
4.
5.
6.
7.
Test and Operating Requirements
Data Bus Operation
Data Form
Bit Priority
4
4.1
4.2
4.3.1
4.3.2
8.
9.
10.
11.
12.
Modulation
Data Code
Transmission Bit Rate
Word Size
Word Formats
4.3.3
4.3.3.1
4.3.3.2
4.3.3.3
4.3.3.4
4.3.3.5
13.
13.1
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.8.1
13.8.2
13.8.3
13.8.4
13.8.5
13.8.6
13.8.7.
13.8.8
13.8.9
13.8.10
13.8.11
13.8.12
13.8.13
13.8.14
13.8.15
13.8.16
13.8.17
Word Formats
Command Word
Content
Sync
Remote Terminal (RT) Address
Transmit/Receive
Subaddress/Mode
Data word count/Mode code
Parity
Optional mode control
Dynamic bus control
Synchronize (without data word)
Transmit status word
Initiate self test
Transmitter shutdown
Override transmitter shutdown
Inhibit Terminal Flag (T/F) bit
Override inhibit T/F bit
Reset remote terminal
Reserved mode codes (01001 to 0111)
Transmit vector word
Synchronize (with data word)
Transmit last command word
Transmit Built-in-Test (BIT) word
Selected transmitter shutdown
Override selected transmitter shutdown
Reserved mode codes (10110 to 11111)
4.3.3.5.1
4.3.3.5.1.1
4.3.3.5.1.2
4.3.3.5.1.3
4.3.3.5.1.4
4.3.3.5.1.5
4.3.3.5.1.6
4.3.3.5.1.7
4.3.3.5.1.7.1
4.3.3.5.1.7.2
4.3.3.5.1.7.3
4.3.3.5.1.7.4
4.3.3.5.1.7.5
4.3.3.5.1.7.6
4.3.3.5.1.7.7
4.3.3.5.1.7.8
4.3.3.5.1.7.9
4.3.3.5.1.7.10
4.3.3.5.1.7.11
4.3.3.5.1.7.12
4.3.3.5.1.7.13
4.3.3.5.1.7.14
4.3.3.5.1.7.15
4.3.3.5.1.7.16
4.3.3.5.1.7.17
(505) 875-0600
1-800-SBS-1553
52
MIL-STD-1553B
Paragraph Number
14.
14.1
14.2
14.3
14.4
Data Word
Content
Sync
Data
Parity
4.3.3.5.2
4.3.3.5.2.1
4.3.3.5.2.2
4.3.3.5.2.3
15.
15.1
15.2
15.3
15.4
15.5
15.6
15.7
15.8
15.9
15.10
15.11
15.12
15.13
Status Word
Content
Sync
RT address
Message error bit
Instrumentation bit
Service request bit
Reserved status bits
Broadcast command received bit
Busy bit
Subsystem flag bit
Dynamic bus control acceptance bit
Terminal flag bit
Parity bit
4.3.3.5.3
4.3.3.5.3.1
4.3.3.5.3.2
4.3.3.5.3.3
4.3.3.5.3.4
4.3.3.5.3.5
4.3.3.5.3.6
4.3.3.5.3.7
4.3.3.5.3.8
4.3.3.5.3.9
4.3.3.5.3.10
4.3.3.5.3.11
4.3.3.5.3.12
16.
Status Word Reset
4.3.3.5.4
17.
18.
19.
20.
21.
22.
23.
24.
24.1
24.2
24.3
24.4
Message Formats
Message Format
Bus Controller to Remote Terminal Transfers
Remote Terminal to Bus Controller Transfers
Remote Terminal to Remote Terminal
Mode Command without Data
Mode Command with Data Word (Transmit)
Mode Command with Data Word (Receive)
Optional Broadcast Command
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)
4.3.3.6
4.3.3.6.1
4.3.3.6.2
4.3.3.6.3
4.3.3.6.4
4.3.3.6.5
4.3.3.6.6
4.3.3.6.7
4.3.3.6.7.1
4.3.3.6.7.2
4.3.3.6.7.3
4.3.3.6.7.4
25.
26.
27.
Intermessage Gap
Response Time
Minimum No-Response Timeout
4.3.3.7
4.3.3.8
4.3.3.9
28.
28.1
28.2
28.3
Terminal Operation
Common Operation
Word Validation
Transmission continuity
Terminal fail-safe
4.4
4.4.1
4.4.1.1
4.4.1.2
4.4.1.3
(505) 875-0600
1-800-SBS-1553
53
MIL-STD-1553B
Paragraph Number
29.
Bus Controller Operation
4.4.2
30.
30.1
30.2
30.3
30.4
30.5
30.6
Remote Terminal
Operation
Superseding valid commands
Invalid commands
Illegal commands
Valid data reception
Invalid data reception
4.4.3
4.4.3.1
4.4.3.2
4.4.3.3
4.4.3.4
4.4.3.5
4.4.3.6
31
Bus Monitor Operation
4.4.4
32.
32.1
32.2
32.3
32.4

Cable
Cable type
Characteristic impedance
Cable attenuation
Cable termination
4.5.1
4.5.1.1
4.5.1.2
4.5.1.3
4.5.1.4
4.5.1.5
33.
Cable Stub Requirements
34.
34.1
34.2
34.2.1
34.2.2
34.2.3
34.3
34.4
34.5
Transformer Coupled Stubs

Stub length
Coupling transformer
Transformer input impedance
Transformer waveform integrity
Transformer common mode rejection
Fault isolation
Cable coupling
Stub voltage requirements
4.5.1.5.1
4.5.1.5.1.1
4.5.1.5.1.1.1
4.5.1.5.1.1.2
4.5.1.5.1.1.3
4.5.1.5.1.2
4.5.1.5.1.3
4.5.1.5.1.4
35.
35.1
35.2
35.3
35.4
Direct Coupled Stubs

Stub length
Fault isolation
Cable coupling
Stub voltage requirements
4.5.1.5.2
4.5.1.5.2.1
4.5.1.5.2.2
4.5.1.5.2.3
36.
36.1
36.1.1
36.1.2
36.1.3
36.2.1
36.2.2
36.2.3
Terminals with Transformer Coupled Stubs
Terminal output characteristics
Output levels
Output waveform
Output noise
Input waveform compatibility
Common mode rejection
Input impedance
4.5.2
4.5.2.1
4.5.2.1.1
4.5.2.1.1.1
4.5.2.1.1.2
4.5.2.1.1.3
4.5.2.1.2.1
4.5.2.1.2.2
4.5.2. 1.2.3
(505) 875-0600
1-800-SBS-1553
54
36.2.4
Noise rejection
MIL-STD-1553B
Paragraph Number
4.5.2.1.2.4
37.
37.1
37.1.1
37.1.2
37.1.3
37.1.4
37.2
37.2.1
37.2.2
37.2.3
37.2.4
Terminals with Direct Coupled Stubs

Terminal output characteristics
Output levels
Output waveform
Output noise
Output symmetry
Terminal input characteristics
Input waveform compatibility
Common mode rejection
Input impedance
Noise rejection
4.5.2.2
4.5.2.2.1
4.5.2.2.1.1
4.5.2.2.1.2
4.5.2.2.1.3
4.5.2.2.1.4
4.5.2.2.2
4.5.2.2.2.1
4.5.2.2.2.2
4.5.2.2.2.3
4.5.2.2.2.4
38
39
40
41
41.1
41.2
Redundant Data Bus Requirements

General
Electrical Isolation
Single Event Failures
Dual Standby Redundant Data Bus
Data bus activity
Reset data bus transmitter
4.6
4.6. 1
4.6.2
4.6.3
4.6.3.1
4.6.3.2
Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 10
Figure 14
Figure 15
Figure 16
Figure 18
Figure 19
Figure 23
Typical Data Bus Architecture

Data Encoding
Word Formats
Command and Status Sync Waveform
Data Sync Waveform
Transmit Vector Word Transfer Format
Broadcast Information Transfer Formats
Intermessage Gap and Response Time
Data Bus Interface using Transformer Coupling
Data Bus Interface using Direct Coupling
Coupling Transformer
Terminal Input/Output Characteristics for
Transformer Coupled Stubs and Direct Coupled Stubs
Output waveform
Fig 1
Fig 2
Fig 3
Fig 4
Fig 5
Fig 6
Fig 7
Fig 8
Fig 9
Fig 10
Fig 11
Fig 12
Assigned mode codes

Criteria for Acceptance or Rejection of a Terminal
for Noise Rejection Test
I
II
Fig 13
Tables
Table 1
Table 2
(505) 875-0600
1-800-SBS-1553

MIL STD 1553 Overview

Uploaded by

Copyright:

Available Formats

MIL STD 1553 Overview

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MIL STD 1553 Overview

Uploaded by

Copyright:

Available Formats

Overview

SBS Technologies, Inc

SBS Technologies, Inc

Figure 1: Typical Data Bus Architecture

SBS Technologies, Inc

Figure 2: Data Encoding

11. Word Size

12. Word Formats

SBS Technologies, Inc

Dynamic Bus Control Acceptance

Broadcast Command Received

Figure 3: Word Formats

A command word shall consist of a synchronization signal (sync), RT address,

Figure 4: Command and Status Sync Waveform

SBS Technologies, Inc

13.3 Remote Terminal (RT) Address

This field has two mutually exclusive functions:

SBS Technologies, Inc

SBS Technologies, Inc

Dynamic Bus Control

Override Transmitter Shutdown

Note to Table 1: *TBD - To Be Determined (see clause 13.8.10)

13.8.1 Dynamic Bus Control

13.8.2 Synchronize (without data word)

See clause 13.8.12 for explanatory note.

SBS Technologies, Inc

13.8.4 Initiate Self Test

SBS Technologies, Inc

13.8.8 Override Inhibit (T/F Bit)

SBS Technologies, Inc

SBS Technologies, Inc

Figure 5: Data Sync Waveform

The sync waveform shall be as specified in clause 13.2.

SBS Technologies, Inc

SBS Technologies, Inc

Single Receiver Only - Bus Controller to Remote Terminal

Service Request Bit Set to

Source: Bus Controller

Dynamic Bus Control Acceptance

Broadcast Command Received

Source: Single Receiver

Source: Bus Controller

Source: Single Receiver

Dynamic Bus Control Acceptance

Source: Bus Controller

Broadcast Command Received

Figure 6: Transmit Vector Word Transfer Format

SBS Technologies, Inc

Source: Bus Controller

Source: Bus Controller

Dynamic Bus Control Acceptance

Broadcast Command Received

Status Word Transmitted With

Figure 7: Broadcast Command Received Bit

Source: Bus Controller

Dynamic Bus Control Acceptance

Broadcast Command Received

Source: Single Receiver

Figure 8: Busy Bit