1553B DATA BUS MANAGEMENT

1
 INTRODUCTION

The 1553B data bus has to follow some general rules for data bus management and
monitoring during initialization, normal operation and failure situations of LCA avionics
systems.
Reference is made to the following documents during preparation :
MIL-STD-1553B: Aircraft internal time division command/response multiplex data bus.
MIL-STD-153 : Multiplex application handbook.

 LCA AVIONICS HARDWARE ARCHITECTURE

LCA avionics hardware architecture is a functionally interconnected multiple level data

bus architecture. This architecture includes 3 1553B buses. Equipments are connected to
one of the 3 buses based on their functions. The Open Architecture Computer(OAC1)
houses 3 bus controllers BC1,BC2 and BC3 controlling the buses B1,B2 and B3
respectively. OAC2 has also 3 bus controllers for buses B1,B2 and B3. Only in the event
of OAC1 failure it’s associated bus controller failure the OAC2 bus controllers(BC1,BC2
and BC3) must be activated.

 INITIALIZATION OF LCA AVIONICS SYSTEM

The various stages of initialization are :

• Equipment identification
• Verification of each equipment identification message
• Data downloading to equipments during initialization
2
 Equipment Identification

After the OAC1 initialization is over , the various LRU equipments will be ready to
communicate through the bus and the identification messages are inserted. The OAC1
reads on the data bus the identification messages of equipments in order to compare
equipment references with its reference list.
In case of identification problem the general procedure to be followed common to all
equipment can be referred in GLOBAL SPECIFICATIONS OF INITIALISATION for PV2.

 Identification message format

• Single LRU equipment : The identification message comprises of the following fields :

 Equipment identification
 Manufacturer code
 Software version (software standard)
 Equipment type(hardware standard )
 Equipment serial number

• Multi LRU equipments :

There will be as many number of identification messages as the sub-equipments or

stores dependent on the LRU linked to the bus. These messages will be of the same
structure as that of the single LRU equipment.

The data downloading to equipments is done in terms of data blocks .

3
 MANAGEMENT OF DATA BUS

The multiplex bus controller software manages the multiplex elements. A summary of bus
controller functions are given below :

• Initialization of the bus

• Synchronization of the equipments on a bus
• Effecting the transmission of messages
• Setting up of proper output message sequences
• Timing for periodic message sequences
• Aperiodic message set up , transmission and/or reception
• Communication of time event or message event (arrival) to an application task controller
or to the recipient task.
• Reconfiguration according to the mission modes.
• Handling transmission errors
• Responses to failure of equipments on the bus
• Reconfiguration because of failure.

 Data Transfer Management

• The type of data transfers that are possible on the 1553B data buses of LCA Avionics
system are :
1. REMOTE TERMINAL TO BUS CONTROLLER data transfer
2. BUS CONTROLLER TO REMOTE TERMINAL data transfer
3. REMOTE TERMINAL TO REMOTE TERMINAL data transfer 4
4. Mode command

i. Without data word

ii. With data word
5. Broadcast Mode command

i. Without data word

ii. With data word
6. Broadcast BUS CONTROLLER TO REMOTE TERMINAL(S)
7. Broadcast REMOTE TERMINAL TO REMOTE TERMINAL(S)

Each remote terminal has :

30 different transmission sub addresses to send data blocks
30 different receive sub addresses to receive data blocks
30 different sub addresses for implicit(broadcast) reception of data blocks.

The number of available sub-addresses for data block identification in a remote terminal can
be extended by adding an additional sub-addressing information index . This must be
used only when the number of addresses > 30 sub-addresses.

The message transfer over the bus is classified into two types :
Periodic and aperiodic messages
A periodic message is transmitted over the bus continuously and cyclically.
An aperiodic message transfer is automatically activated by the bus controller, but in a non-
cyclic way.
5
 When the data is broadcast , all the remote terminals will receive the data. Data can be
transmitted to a set of selected remote terminals connected to a bus, by the use of
selective broadcast.

 Service Request
The remote terminal will set the service request bit in the status word and the
corresponding service will be indicated in the vector word. This request is sent to the
bus controller when the bus controller scans the remote terminal. This can be done in
two different ways :
1. On detection of the service request bit.
This can be used for remote terminals, which are contacted quite frequently by the bus
controller
2. Cyclically : The bus control scans the remote terminal cyclically, using ‘Transmit’ status
word’ mode command periodically(once in 160 msec).
The second method of periodically polling remote terminals and acquiring the service
requests is selected for LCA PV2 aircraft.

 Synchronisation of Buses
Synchronisation of buses is achieved using a common clock for all the three bus
controllers inside the OAC1. Similarly the three bus controllers inside the OAC2 also
should be synchronized. Interbus messages are intended to serve data transfer among
various equipments connected to different buses.
6
 Dating Information

The avionics system is synchronized with GPS time. The avionics system is coded over 32
bits in the message using two data words, either using clock or using GPS time. The
current system time is broadcast to all the equipments connected to the bus once in a
major cycle, by the bus controller.

 Data Exchanges
Definition of frames :
A ‘minor cycle’ is the duration corresponding to the fastest frequency at which the
messages are transmitted over the bus ( 5 msec)
A ‘major cycle’ is the duration corresponding to the slowest frequency at which the
messages are transmitted over the bus ( 160 msec)
A frame comprises all the messages that are likely to be transmitted over the bus.

 Formation of frames :
For LCA, a static frame defines the activation of message transfers.
Separate frames will be made for various aircraft mission modes :
Initialisation mode :
- Normal initialisation Frame
Operational normal mode
- Basic frame
- BVR (Beyond Visual Range missile)
7
• LGB (Laser Guided Bombs )
• LDB (Low Drag bomb)
• HDB (High Drag bomb)
• ASM( Air to surface missile)
• RKT (Rocket)

Ground Supplementary maintenance mode

- Flight Line Maintenance Frame
- Maintenance frame

During aircraft initialization, each sortie of the aircraft will be having an initialization frame
and operational frame. Each of the operational frames will contain :
Basic messages which are to be transferred through out the flight of the aircraft
Messages specific to the weapon / sensor configuration selected for the sortie.

- The stores messages are only sent to the active stores interface box(SIB). In case any
SIB fails, the entire stores messages are switched over to other serviceable SIB( SIBs
are identified by their external remote terminal address ).
- Each message transfer is initiated by the bus controller by transmitting a command
word(s) on the bus. The command word will contain the address of the remote terminal
to be contacted; remote terminal sub address/mode command and the word count/mode
code. 8
 If there are any errors in message transfer, error identification is the responsibility of all the
terminals connected to the data bus, while error determination and recovery procedures
are the responsibility of the bus controller.
 1553B validation requirements
Terminal word validation

• Each word should have correct sync. Command and status words should have a sync of
1.5 bits duration positive pulse followed by a negative pulse of the same duration.
 All the bits in a word except the sync should be in the valid Manchester encoded form.
 The last bit(parity bit) should be set for odd parity
 The bit count must be correct 16 bits + one parity bit
 Bit length(1 microsecnd) and word length (20 microsecond) should be checked for the
correct value.
 Data words should be transmitted without any time gap in between.

Message errors

Detected message completion failures( Message errors) can be :

 Invalid word
 Transmission discontinuity
 Improperly timed sync
 Invalid message
 Word count error
The word count indicated in the command word and the actual number of the data words
received should be the same. If a message error has occurred, the entire message shall
be considered invalid.
9
 Error monitoring in a remote terminal

If the command word is an invalid word all remote terminals must ignore that
command word and must wait for another valid command word. A command word is
considered illegal if it contains illegal mode commands, undefined data blocks or T/R
bit error, illegal mode command shall include :
 Unimplemented mode codes
 Reserved mode codes
 Mode codes whose utilisation in broadcast mode is not allowed by 1553B standard,
but used in broadcast mode.

 Error recovery procedures

The actions to be taken when the various bits in the status word are given below :

 Message error bit : Once a message error is detected, the remote terminal must set
the message error bit in the status word and the status word must be suppressed.
Suppression of status word can be taken as a message error and message can be
retried for explicit message transfer on the alternate bus.
 Instrumentation bit : The instrumentation bit should be always set to 0.
 Service request :
 Broadcast command received bit : This bit is set to 1 when the remote terminal
receives a broadcast command and the status word is suppressed. If this bit is set for
a command other than ‘Transmit last command word’ or ‘Transmit status word, this
indicates an abnormal bit setting.
 Busy Bit : This bit is set to 1 if the addressed remote terminal ( Remote terminal
and/or equipment) is unable to transmit or receive data at that time.
10
 Subsystem flag :
This bit is used to indicate the status of the associated equipment of the remote
terminal. This bit is set due to one of the following reasons :
1. A failure has been self-detected in the equipment by its self-tests. In this case the
subsystem bit is set to 1.
2. The equipment is being good. In this case the subsystem bit is set to 0.
• Dynamic bus control acceptance bit
This bit should always be set to 0.
• Terminal flag :
This bit is used to indicate the status of the remote terminal unit. This bit is set due to
one of the following reasons :
1. A failure has been self-detected in the terminal. In this case terminal bit is set to 1.
2. The terminal is being is reset (good). In this case the terminal bit is set to 0.
 Broadcast bit :
If the command is not defined as a broadcast command, error condition is indicated.
 Invalid status word :
If the bus controller receives an invalid status word (invalid word or abnormal bit
setting), it can be taken as a message error and message can be retried on the same
line.
 No response
• Bus controller no response time out
The bus controller shall wait a minimum time( 14 microseconds) before concluding
that the remote terminal is not going to respond as requested.
• Terminal fail safe
The terminal shall contain a hardware-implemented time out to preclude a signal
transmission of greater than 800 microseconds
11
 Implications of error recovery procedures

If the remote terminal receives the data correctly and transmits an invalid status word, the
bus controller will retry the message resukting in the remote terminal receiving the same
data again.
When the primary bus controller fails, a standby bus controller should take over the bus
management function . When the primary bus controller functions properly, the standby
BC will be working as a remote terminal on the bus.
Before initiating actual data transfer on the bus, the correct operation of all the remote
terminal bus interface unit/ equipment has to be ensured. This can be done by the
methods :
• Polling
• Loop Test
• Polling
Polling is made to ensure satisfactory communication with a remote terminal. Polling shall
be made once per major cycle on both the buses to all the equipments ( once in 160
msec) using the ‘transmit status word’ mode command. If the equipment responds to the
poll command, then communication with that equipment is established on the main line. If
the equipment fails to respond to 2 consecutive poll commands on both the buses, then
Poll failure is said to have occurred for that equipment.
• Loop Test :
This test is made to ascertain the health of Host processor-remote terminal bus interface
unit . Loop test is made once in every major cycle( once in 160 msec). It is made for all
equipments connected on the bus. The Loop test procedure is as follows :
The bus controller sends a data word to the equipment in the beginning of major cycle.
The data word is transferred from the receiver buffer to the transmit buffer by the host
CPU. The equipment sends the data word back to the bus controller at the end of major
cycle, where the integrity of the data is checked to ascertain the success of the loop test.
12
 The data words to be used for loop test are time broadcast data(second word). At the
receiver user the loop test word must be moved from the receive buffer to the transmit
buffer within 100 msec.
For each equipment, the bus controller shall have a counter, which is initialized to 5.
When a loop test fails this counter is decremented by 2 and on loop test success it is
incremented by 1. The counter can take a maximum of 5 and a minimum value to 0.
When the counter value has become 0, then the equipment is said to have failed.
The loop test, polling results and the BIT results of an equipment are used to determine
the equipment failure. The messages of that equipment which has failed are deleted
from the bus controller’s command table(frame) and on subsequent pass, they are
added back to the command table.
Selection of the bus lines : One of the two lines will be assigned as the active
line(predefined), when the bus controller is switched on. The bus line is selected for
each remote terminal , based on the health of the line. For eg., if the remote
terminal(RT) fail is declared on channel A bu poll test, the channel selected for that
remote terminal will be channel B and vice-versa.
There are some standardised messages common to all the remote terminals connected
to the bus :
1. Broadcasting of system time
2. Transmission of the loop test word to all the remote terminals on a bus

 DETECTION OF BUS CONTROLLER FAILURES

In case of self-detection of a failure by the OAC1, it is indicated to the OAC2 and OAC2
takes over as the bus controller. When a failure of the CPU(MP,DP1,DP2,DP3) and its
associated memories is self-detected by the OAC1 and this failure is confirmed. The
OAC1 transmits a discrete ‘LOW’ signal to OAC2. In case OAC1 failure is detected
during initialization, the error has to be fixed, otherwise mission must be aborted.
13
 Bus controller failures are categorized under hardware failures. By extensive self-test
coverage (to the order of 95%), the failures could be detected and appropriate
reconfiguration management could be implemented. The OAC1/OAC2 are also covered by
extensive self-test coverage. Hence either the bus controller failures or computer failures
can be detected and identified.
There are dedicated links between OAC1 and OAC2. The status of bus controller and
health of OAC1 are checked indicated to the OAC2 through a dedicated link ‘OAC1
STATUS’ . If this link is in a logic level ‘1’ it indicates that OAC1 and the associated bus
controllers are working properly. If this dedicated link is in a logic level ‘0’ or it is left
floating, this indicates the OAC1 failure. OAC2 takes over the control of the buses B1,B2
and B3. Once the OAC2 detects the OAC1 failure, it should disable the OAC1 before it
starts acting as the bus contoller, through a dedicated link ‘DISABLE OAC1’.

 Reconfigured mode of operation

The avionics system goes into reconfigured mode of operation when OAC1 has failed. The
OAC2 then takes over and performs all the OAC1 functions. These functions are
performed through 1553B buses, namely B1,B2 and B3 and through RS-422 lines with
MF-UFCP,FSP and SSP. In order to take over the control and management functions of
OAC1 , the OAC2 first receives input ‘OAC1 STATUS’ from the OAC1 which indicates that
OAC1 has failed. The OAC2 commands the bus silence by sending a discrete signal
‘DISABLE OAC2’ to OAC1 after two minor cycles( 40 msec).
The OAC2 goes through initialization phase after take over from OAC1. OAC1 must inform
OAC2 whether the initialization process is completed or not. The standby mode operation
14
 would therefore commence only when OAC1 fails after the successful completion of the
initialization phase in OAC1. In the event OAC2 fails to take over after OAC1 fails, the
avionics system is not available for use, except the SSDU system.

The initialization process in OAC2 would adopt the following steps :

• It reconfigures the 1553B hardware to BC mode
• Sends OAC1 failure message with time tag to VDR for storage
• Loads the reconfigured mode operational software
• Loads op-mode frame sent by OAC1 to BC on successful completion of software loading
Failure of any one of the bus controllers or the failure of the computer is considered as the
total OAC1 failure. OAC2 takes over from OAC1 once OAC1 is failed. The back-up bus
control function for B1,B2 and B3 is assumed by OAC2.

OAC1 failure conditions :

• CPU(MP,DP1,DP2,DP3) and its associated memories

• One of the Bus controllers
• Discrete I/O card failure
• Video Switching Module(VSM) failure
• Overall failure as detected by the MP

15
 MODE COMMANDS IMPLEMENTATION

The following are the mode codes to be implemented :

EXPLICITLY OR IMPLICITLY
1. Synchronize
2. Transmitter shut down
3. Override transmitter shut down
4. Reset remote terminal
5. Synchronize with data
6. Initiate self-test

EXPLICITLY ONLY
1. Transmit status word
2. Transmit BIT word
3. Transmit last command word
4. Transmit vector word

16