AVIONICS(AEB 401)

Module III-Avionic system Data buses Design and integration

TOPICS
▪ MIL STD 15553B
▪ ARINC 429
▪ ARINC 629
▪ CSDB
▪ AFDX
▪ Avionics system design Development and integration
▪ Simulation tools
▪ Stand alone & integrated Verification and Validation

1
 Introduction
• In computer architecture a bus is a communication system that
transfer the data between modules with in the computer or
between the computers
• Data bus: It provides a medium for exchange of data and
information between various avionics sub systems
• Protocols: Set of formal rules and convention governing the
flow of information among the systems
• Low level protocols: Define Physical and Electrical
Standards
• High level protocols: Deal with the data formatting
2
including the syntax of the messages and its formats
 MIL STD 1553B
• MIL 1553B standard uses Command and Response Protocols
• Elements of 1553B bus system
✓ Bus Controller
✓ Remote terminals
✓ Bus monitor
✓ Transmission media

3
 1553B MIL STD Specifications
• Data Rate 1 MHz
• Word Length 20 bits/word
• Data Bits/Word 16 bits
• Transmission Technique Half-duplex
• Operation Asynchronous, self-clocking waveform
• Encoding Manchester II bi-phase
• Bus Topology Linear multi-drop bus, with stub-coupled
terminals
• Bus Coupling Transformer or direct coupled
• Transmission Media Twisted-shielded-pair cable terminated
in its characteristic impedance
• Protocol Time-division, command/response
• Bus Control Single or multiple

4
MIL-STD-1553 Simple Multiplex
Architecture
Cable
Coupler

Optional
Redundant
Cables

Bus Remote Subsystem

Controller Terminal with
Embedded
Remote
Subsystem(s) Terminal

5
 Bus Topology Examples
Sensor A Sensor B Sensor C

Bus A
Single Level
Bus B Topology

Comp 1

Sensors
Controls and Bus A
Display Bus Bus B
Navigation Bus A
Bus Bus B
Single Level, Bus
with Functional Sensors
Controller
Separation
Stores Bus A
Bus Bus B

Sensors

6
 Transformer Coupled Bus Network
Terminal Terminal Terminal
1 2 N

Stubs

1 1 1

1.41 1.41 1.41

R R R R R R

Zo Main Bus Zo

R = 0.75 • Zo ohm

7
 Transmission Line Characteristics
1553 Requirement

• Cable Type Twisted-shielded-pair

• Capacitance 30 pFd./ft Max
• Characteristic 70 to 85 OHMS at 1 MHz, nominal
Impedance (actual, per notice 2)
• Attenuation 1.5 db/100 ft Max at 1MHz
• Bus Length Not specified in 1553B (300 ft suggested max)
• Stub Length Direct coupled - less than 1 ft
Transformer coupled - 20 ft (suggested max)
• Termination Ends terminated with resistors of Z0 +/-2%
• Cable Shielding 75% coverage (90% coverage, per notice 2)

NSBE Seminar 8
Bus Coupler Characteristics
Direct Transformer
Coupled Coupled
Shield
Data Bus
• Isolation resistors: R = 0.75 ZO 2%
• Isolation transformer: turns R R
ratio 1:1.41 3%
(1 – terminal winding) 1:1.41
(1.41 – bus winding)
ZOC > 3K at 75 kHz to 1 MHz
1V rms sine wave
At 27v
Droop: < 20% P-P 250-kHz 55 ohm 55 ohm
Overshooting/ringing: < 1Vsq wave 2% 2%
CMR: > 45 dB at 1 MHz
• Nominal characteristic impedance
of bus cable:
ZO = 70 to 85 at 1 MHz
Transceiver Transceiver

Terminal Terminal

9
 MIL-STD-1553 Data Encoding
One Bit Time

(+) –
1 MHz
Clock
(0) –

(+) –
NRZ
Data (0) –

1 0 1 1 0 0 0
(+) –

Manchester (0) –
II
Bi-Phase L
(-) –

10
MIL-STD-1553B Word Formats

• Command Word
• Command/status sync, 16 data bits, odd party
• Transmitted only by the active bus controller
• Contains unique address of RT or broadcast address (11111)
• Contains transmit or receive data indicator
• Contains subaddress (or mode code indicator)
• Contains word count of 1 to 32 (or mode code)
• Status Word
• Command/status sync, 16 data bits, odd party
• Transmitted only by the commanded remote terminal
• Contains own address and terminal health information
• Data Words
• Data word sync, 16 data bits, odd parity
• Transmitted or received by bus controllers or remote terminals
• Received by bus monitors

11
 MIL-STD-1553B Word Formats
Bit Times 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Command
Word 5 1 5 5 1

Sync Remote Terminal T/R Subaddress/ Data Word P

Address Mode Count/Mode Code

16 1
Data Word
Sync Data P

Status 5 1 1 1 3 1 1 1 1 1 1
Word

Acceptance
Dynamic Bus Control
Message Error

Instrumentation

Service Request

Subsystem Flag
Received
Broadcast Command

Parity
Terminal Flag
Busy
Sync Remote Terminal Reserved
Address

12
 MIL-STD-1553B Terminal Block Diagram
1553B Data Bus 1553 Terminal

Internal
Buses Subsystem
Protocol Control

Computer
Encode
Transceiver
Decode
Subsystem Subsystem
I/F
Encode Memory
Transceiver
Decode

I/O
Power Supply Process
Subsystem

13
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
Overview of ARINC
▪ ARINC stands for Aeronautical Radio, Inc., a private corporation organized in 1929, and is
comprised of airlines, aircraft manufacturers and avionics equipment manufacturers as
corporate shareholders.
▪ ARINC was developed to produce specifications and standards for avionics equipment
outside the government for domestic and overseas manufacturer
ARINC Specifications are used to define

▪ Physical packaging and mounting of avionics equipment

▪ Data communications standards
▪ High level computer languages
▪ The ARINC 429 Specification, Mark 33 Digital Information Transfer System falls under
the Specification document category.
14
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

ARINC 429 Specification, first released as ARINC 429-1 in April 1978, and currently exists
as ARINC 429-15. ARINC 429-15 was adopted by the AEEC in 1995 and is comprised of 3
parts:

▪ Part 1 addresses the buses physical parameters, label and address assignments, and
word formats.

▪ Part 2 defines the formats of words with discrete word bit assignments.

▪ Part 3 defines link layer file data transfer protocol for data block and file transfers.

15
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
▪ ARINC 429 utilizes the simplex, twisted shielded pair data bus standard Mark 33 Digital
Information Transfer System bus. ARINC 429 defines both the hardware and data formats
required for bus transmission.
▪ Hardware consists of a single transmitter – or source – connected to from 1-20 receivers –
or sinks – on one twisted wire pair.
▪ Data can be transmitted in one direction only – simplex communication – with bi-
directional transmission requiring two channels or buses.
▪ The devices, line replaceable units or LRUs, are most commonly configured in a star or
bus-drop topology.
▪ Each LRU may contain multiple transmitters and receivers communicating on different
buses.
▪ This simple architecture, almost point-to-point wiring, provides a highly reliable transfer
of data.
16
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

17
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

▪ transmitter may ‘talk only’ to a number of receivers on the bus, up to 20 on one wire pair, with each
receiver continually monitoring for its applicable data, but does not acknowledge receipt of the data.

▪ A transmitter may require acknowledgement from a receiver when large amounts of data have been
transferred..

▪ Transmission from the source LRU is comprised of 32 bit words containing a 24 bit data portion
containing the actual information, and an 8 bit label describing the data itself.

▪ LRUs have no address assigned through ARINC 429, but rather have Equipment ID numbers which
allow grouping equipment into systems, which facilitates system management and file transfers.

▪ Sequential words are separated by at least 4 bit times of null or zero voltage. By utilizing this null
gap between words, a separate clock signal is unnecessary. Transmission rates may be at either a
low speed – 12.5 kHz – or a high speed – 100kHz.
18
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

19
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
Transmission signal Characteristics
Data is transmitted in a bipolar, Return-to-Zero format. This is a tri-state modulation consisting of HIGH, NULL and
LOW states.

TRANSMIT STATE RECEIVE

+10.0 V  1.0 V HIGH +6.5 to 13 V
0 V  0.5V NULL +2.5 to -2.5 V
-10.0 V  1.0 V LOW -6.5 to -13 V

20
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

21
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

22
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

23
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

24
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
ARINC 629
➢ Source transmits either broadcast or address specific message to all or specific
receiver or sinks
➢ If the sinks equipment needs to reply, each will need to be fitted with own
transmitter and a specific physical bus

25
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

26
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

27
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

28
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

29
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

30
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

31
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
Commercial Standard Digital Bus(CSDB):
▪ is an asynchronous linear broadcast bus, specifying the use of a twisted, shielded pair
cable for device interconnection.

▪ Two bus speeds are defined in the CSDB specification. A low-speed bus operates
at 12,500 bits per second (bps) and a high-speed bus operates at 50,000 bps.

▪ The bus uses twisted, unterminated, shielded pair cable and has been tested to lengths
of 50 m.

▪ The CSDB standard also defines other physical characteristics such as modulation
technique, voltage levels, load capacitance, and signal rise and fall times.

▪ Fault protection for short-circuits of the bus conductors to both 28 VDC and 115 VAC is
defined by the standard. 32
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

33
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
Basic Bus Operation of CSDB
In CSDB standard, three types of transmission are defined:
• Continuous repetition,
• Noncontinuous repetition, and
• “Burst” transmissions
Continuous repetition transmission refers to the periodic updates of certain bus messages.
Some messages on CSDB are transmitted at a greater repetition rate than others. The CSDB
standard lists these requirements
update rates, along with the message address and message block description.
Noncontinuous repetition is used for parameters that are not always valid, or available,
such as mode or test data. When noncontinuous repetition transmission is in use, it
operates the same as continuous repetition. Burst transmission initiates an action (such
as radio tuning), or may be used to announce a specific event. Operation in this mode
initiates 16 repetitions of the action in each of 16 successive frames up date rate:20/see
34
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

35
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
CSDB Bus Cap
▪ Data are sent as frames consisting of a synchronization block followed by a number of
message blocks. A particular frame is defined from the start of one synchronization block
to the start of the next synchronization block. A message block contains an address byte, a
status byte, and a variable number of data bytes. The typical byte consists of one start bit,
eight data bits, a parity bit, and a stop bit.
▪ The theoretical bus data rate for a data bus operating at 50,000 bps with an 11-bit data
byte, is 4545 bytes per second. For

▪ The CSDB Interblock and Interbyte times also reduce bus throughput. According to the
specification, there are no restrictions on these idle times for the data bus. These values,
however, are restrained by the defined update rate chosen by the designer. If the update
rate needs to be faster, the Interblock time andthe Interbyte time can be reduced as
required, until bus utilization reaches a maximum .
36
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
CSDB Error Detection and Correction
▪ Two methods of error detection are referenced in the standard. They are the use of
parity and checksums.
▪ A parity bit is appended after each byte of data in a CSDB transmission.
▪ The “burst” transmission makes use of the checksum for error detection. As the General
Aviation Manufacturers Association (GAMA) specification states:
▪ It is expected that the receiving unit will accept as a valid message the first message
block which contains a verifiable checksum. (GAMA CSDB 1986.)
Bus User Monitoring
Although many parameters are defined in the CSDB specification, there is no suggestion
that they be monitored by receivers. The bus frame, consisting of the synchronization block
and message block, may be checked for proper format

37
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

38
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
INTRODUCTION FOR AFDX(Avionics Full Duplex switched ethernet)

▪ In modern aircraft — inertial platforms, communication systems, a demand high-

reliability, high-speed communications, as well. Control systems and avionics in
particular, rely on having complete and up-to-date data delivered from source to
receiver in a timely fashion. For safety-critical systems, reliable real-time
communications links are essential.
▪ Solution for the above demand Initiated by Airbus in the evolution of its A380
Aircraft, they coined the term, AFDX, for Avionics Full-DupleX, switched Ethernet.

▪ AFDX brings a number of improvements such as higher-speed data transfer — and

with regard to the host airframe — significantly less wiring, thereby reducing wire
runs and A/c weight
39
Key features of AFDX
• AFDX is the Common communication system used for modular avionics
architecture.
• It is compliant with the Following design key factures:
• It is based on Open Standard
• as required by cost and commercial standard reuse objective
• It provides "Resource Sharing"
• as required by modularity, reuse, and cost objective
• It provides "Robust Partitioning"
• as required by resource sharing and safety, certification constraints
• It provides "Determinism" and "Availability"
• as required by safety, certification constraints

• The AFDX key features are mainly concentrated on the Data

Link layer.
FLS/04/005609 IR 00 Aerospace
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
▪ “Avionic Full-Duplex Switched Ethernet” (AFDX), designated ARINC 664, is a specification
for a deterministic aircraft data
▪ network bus for aeronautical, railway and military systems.
▪ The network is based on standard IEEE 802.3 Ethernet technology.
▪ The benefits from using commercial-off-the-shelf (COTS) Ethernet components include
reduced overall costs, faster system development and less-costly maintenance for the
system network.
▪ AFDX extends the Ethernet standard by adding Quality of Service (QoS) and deterministic
behavior with a guaranteed dedicated bandwidth.
▪ AFDX™ is currently used in the Airbus A380 and A400M as well as in the Boeing 787
Dreamliner
▪ Reliable packet transport and fixed latency are main requirements for AFDX

41
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

42
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

AFDX INTERCONNECT
43
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
Two of the three End Systems provide communication interfaces for avionics subsystems
and the third End System supplies an interface for a Gateway application. It, in turn,
provides a communications path between the Avionics Subsystems and the external IP
network and, typically, is used for data loading and logging .

▪ AFDX switch forwards packets according to a static table.

▪ A general policy in this network to statically define all LRUs and their respective
network addresses.
▪ There is no address resolution protocol (ARP) necessary to resolve MAC addresses from
IP addresses.
▪ To increase availability of the network, redundancy is introduced on the physical
layer. Each packet is transmitted simultaneously by two Ethernet controllers onto
separate wires, via physically separate switches to the destination system.
44
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration
▪ AFDX – at the application level – is intended to replace ARINC-429 connections..
▪ The point-to-point and point-to-multipoint connections are represented by virtual links
(VL).
▪ A single VL may connect exactly two End Systems, in which case it represents a point-to-
point connection.
▪ It may also connect one sending End System with multiply reading End Systems, in which
case it represents a point-to-multipoint(multicast) connection.
▪ The advantages of this architecture lie in the fact that AFDX presents itself compatible at
the application level and saves a large amount of cable runs by multiplexing many
individual VLs onto a single wire connection utilizing the increased bandwidth of a
100Mbit Ethernet connection.
▪ The VL-bundle is demultiplexed at the destination switch and forwarded to the
appropriate End Systems .
45
 AVIONICS(AEB 401)
Module III-Avionic system Data buses Design and integration

46