Unit 3, Digital Avionics Architecture

Avionics system architectureData buses MILSTD 1553 BARINC 429ARINC 629.

1

Syllabus
Avionics system architecture Data buses MILSTD 1553 B ARINC 429 ARINC 629.

OSI Model Data unit Host Data layers Layer 7. Application 6. Presentation 5. Session Segment Media Packet layers Frame Bit 4. Transport 3. Network 2. Data Link 1. Physical Function Network process to application Data representation and encryption Interhost communication End-to-end connections and reliability Path determination and logical addressing Physical addressing Media, signal
3

Pave Pillar Architecture

An Hypothetical Architecture for an high performance Aircraft Which has the following performance requirement 1. Paying attention to take off and landing on flight controls 2. Having Two level maintenance & that has MTBF=70 Hrs & MTTR=1.25 hr 3.High percentage of Fault Detection & Fault Isolation=99 & 98%

Major Avionic Architecture

Types, features and comparison

Scheme of General Avionic Control System

Inputs from Sensor 1.Positional Data 2.Environmental data Sensors 3.Aircraaft State Data
ACS-Avionic Control System Effector To Displays For Pilot Alerting

ACS

Types
I.

II.

Federated Architecture= Dedicated & independent processing and communication system with no Data Sharing eg. Arinc 429 and Saras of NAL Integrated Modular Architecture- A real time computer system with data sharing between Sensors and Effectors integrated to flight control, landing gear, display control. - 1553 A/B eg. Airbus & Arinc 629 (partially IMA & Fed)

Features -Federated
1. 2.

3.

4.

Stand-alone independent system with sensors, processing units and Effectors No Data Sharing between sensors, effectors and processing units Each system having own interfaces (CPU, I/O) to sensors and actuators (Effectors) Functions partitioned Eg. ARINC 429
8

Federated Architecture Schematic

Components of Federated Architecture

User Interface for controlling the Effector 3 CPU-s each CPU for Sensor, Effectors, 5 I/O modules 4 Physical Communication Channel (1.User Interface to Effector, 2. UI to Sensor, 3.Sensor to Effector and 4. a Feedback from Sensor to UI)

10

Components of Federated Architecture contd

1. 2.

3. 4.

User interface = landing gear, processing unit, display and control Effector Used interface used for controlling the effector based upon feedback collected from a sensor Sensor 3 Units connected by dedicated communication channels.
11

Advantages of Federated Architecture

Each Function has its own fault tolerant computer and each box has a specific function, with specifically developed hardware and software Failure of one function has no effect on the other system Every system is a stand alone system

12

Disadvantages of Federated Architecture system

Developed from scratch, with the lack of technology re-use Suffering from obsolescence issues for hardware components Increased weight and power consumption Hence increasing the weight of the aircraft resulting in poor fuel efficiency this introduces dedicated communication channels and also

13

Integrated Modular Architecture

A real time computer airborne network system Core computer performing majority of avionics functions Distributed avionics functions are packaged into self-contained units IMA contain LRM ( Line Replacable Modules)

14

Integrated Modular Architecture

15

Features of IMA
1. 2.

3.

4.
5.

6. 7.

Sensor data shared between several systems In Core computer several modules identified performing a specific function like the flight control, landing gear, display control, etc. Multiple Federated application integrated into a single platform Strong Partitioning of Software & Two layer Software Architecture Inter partitioning of Communication Facility & Client Server inter partition Protocol Displaying of Status Messages Input/Output message handling by Message Handler and System Executive
16

Advantages of IMA

Each Avionic Computer has Open System Interface called Application Program Interface API with Plug and Play Flexible communication having a logical channel and communication channel Flexibility in Hardware Architecture All LRM lightening protected,EMC and environmentally protected Fault Tolerance in IMA Full Duplex Switched Ethernet
17

Disdvantages of IMA
Specific function for each LRM ( autopilot module, flight management module not interchangable) Modules not field replacable Multiple suppliers-not my problem

18

Air crtafts using IMA

1.

2.
3. 4.

F22 Raptor Airbus 380 & Airbus A400 Boeing 787 Sukhoi Super Jet 100

19

Two layer Software Architecture

20

Examples of IMA architecture

Airbus A350 Airbus A380 Boeing 787 Dassault Falcon 900

21

Comparison between IMA & Fed

1. 2. 3. 4.

5.

Open System architecture with P&P Fully Duplex Only One Core Computer Field Replacable (LRM)except FM and Autopilot Highly fuel efficient and light weight

1.

2. 3. 4. 5.

Closed System architecture with no P& P Not Duplex Many Distributed Computers Not Field Replacable Poor Fuel efficient and Bulky.

22

Aeronautical Standards
ARINC429,629 & 1553 1773

23

Aeronautical Standards
ARINC-Aeronautical Radio IncorporatedArinc 429 series Arinc 629, used by Boeing MIL std Military, MIL 1553 standard Airbus

24

ARINC 429
In brief,

25

General
A physical and electrical interface of a two-wire data bus in most of the commercial and transport aircrafts One pair for TX and another pair for RX A data protocol to support an aircraft's avionics local area network. Use Star/Bus/Multiple bus topology

26

ARINC 429

27

In A NUTSHELL

Open Standard, with 32 bit word Transmission. A Simplex (TX & Rx on diff. ports) , Dedicated I/O with Point to Point, synchronous communication with 2 wire Operate on both discrete and analog signals Max 20 Receivers can be connected to the 2 wire. Sub Systems include FMS,ILS, VHF, Display system
28

FEATURES
An Unidirectional Bus operating 12.5 or 14.5 or 100 kbps Use 32 Bit word with Odd Parity for error detection Waveform is RTZ bipolar It is Simplex Bus ,having RT, or Bus Monitor with no bus controller

29

30

RTZ Bipolar Format

31

ARINC Avionic Data Bus in Boeing

32

Features of ARINC 429

A standard that communicates between avionics equipment and systems connected with Twisted Pair wires Employs a Unidirectional Data Bus Standard called Mark 33 Digital Information system Data speed =12.5 or 100 kbps Transmission and reception on separate ports so that many wires required

33

Point to Point structure

34

Components of Arinc 429

1.

2.
3. 4.

429 Transmitter- 2 transmit channels 429 Receiver-20 incoming channels Software Interface Graphical user Interface GUI

35

ARINC 429 Architecture

36

ARINC 429 INTERFACE thru RS232

37

Word Format Characterestic

32 bit word by two wire transmission containing 5 fields Protocol= Point to Multi- Point Protocol Has both low speed and high speed Parity Bit = MSB Five fields ; 2 for numerical data, 1 for discrete data, 2 for alphanumeric data Data = BCD

38

Word Format

39

Word Format

32 BIT Format 1-8 for Label (for maintenance purpose) 9 & 10 for SDI ( Source Destination Identifier)-1 TX and 20 RX 11 to 29 Data both discrete and Numerical data 30 & 31 for SSM( Sign/Status Matrix) for reporting repair/fault on hardware status of en equiment 32 for Parity for error detection and correction.
40

ARINC 629
General Features,Protocol Layer,Timing Diagram (Periodic and Aperiodic) Comparison between 429 & 629

41

Schematic of Basic Protocol for Flight control

42

General Features of ARINC 629

A Multipoint system- one transmitter to Multi receivers Has two independent MAC protocols for communications across a 2 Mbps Serial data bus Use High Speed Bi directional Bus Duplex Has periodic and a-periodic transmissions Has 2 Protocols-Basic Protocol and Combined protocol; Basic protocol for flight controls, Combined protocol for flight management system No bus Controller required

43

Combined Protocol Layer

4

2 2

1
44

4 Protocol layers of Arinc 629

Physical layer- 2 Mbps Serial Data Transmission on Twister pair cable for collision avoidance 2. Data Link Layer- single source to many terminals for using TDMA Having Basic Protocol and Combined protocol existing in the same bus 3. Network Layer- 20 bit words upto 256 data words 4. Upper Layer-presenting application, session, presentation and transport layer for IMA architecture
1.
45

Basic Protocol features-in flight control

1.

2.
3.

Transmitting only at aperiodic mode Normally Terminals transmit on periodic mode on no overload Even if there is overload, it is transmitting on aperiodic mode

46

Combined Protocol-CP - FMS system

Shortfalls in BP for Periodic and Sporadic data transmissions corrected Transmitting both on periodic and aperiodic mode Terminals given equal opportunity to switch when there is overload Periodic Data compressed into Burst, separated by Transmit Internal T1

47

Difference between BP & CP

BP
Transmitting either Periodic or aperiodic Terminals transmit at periodic only when there is no overload Terminals not given equal opportunity for overload

CP
Transmitting both periodic and aperiodic Terminals transmit at periodic mode even if there is overload Terminals given equal opportunity to switch for overload
48

Difference between Periodic & Aperiodic Mode

Periodic Mode:All transmission times are fixed in each cycle Aperiodic Mode: Individual Transmission times vary between cycles

49

Timers used
1.

2.
3. 4.

Timer 1 for Transmit Internal T1 Timer 2 for Synchronisation Gap SG Timer 3 for Terminal Gap TG These 3 timers work both on Periodic and Aperiodic mode

50

Timing Status
1.

2.

3.

TG-Terminal Gap An unique timer assigned to the terminal for waiting after a bus activity. TG begins when SG is elapsed. SG-Synchronization gap- A quiet time condition SG-starts the moment the terminal is quiet; TG & SG cannot overlap;SG starts when the bus is quiet. Transit timing condition T1- Transmit Timer starts the moment the terminal starts transmitting51

Timing diagram-Periodic modeConstant T1

When terminal starts Transmitting, T1 timer starts when the Bus is quiet SG timer starts when SG has finished, TG timer starts T1-TG-SG

52

Timing diagram-Periodic modeConstant T1

T1
Delay until T1 elapse

TG

SG

T1

TG2

T2

Tn

SG

Constant T1

53

Timing Diagram-Aperiodic ModeVariable T1

Each terminal has an unique preassigned TG Transmit Terminal T1 is applicable to the first transmission. For all other terminals T1 overrides and TG starts For Aperiodic SG starts when the Bus is quiet.

54

Timing Diagram-Aperiodic ModeVariable T1

start

T1

T2

Tn

stop

SG TG1 TG2 TGn

Variable T1
55

ARINC 629 card

56

Arinc 629 Interface

57

Word Format
1.

20 bit word using CSMA/CA protocol 16 Bit Data Word; 16 Bits assigned between Synchronization bits and parity bit- are Labels 1 Bit for Parity 3 Bit for Synchronization HI to LO

58

Word Format in Arinc 629

0 for Parity

12-15 for Channel Identification CID 11 12 15 16 19

11 to 1 Labels (numbered in reverse)

16-19-4 bits for sync

59

Comparison between 429 & 629

No
1 2

Parameter
Architecture Data Flow

ARINC 429

ARINC 629

3 4 5

Word Size Protocol & Timing Speed

Federated F + IMA Uni Bi Directional directional Duplex Simplex 32 bit in RTZ 20 bit word P-P P-MP Asynch. Sync & Async 12.5 Kbps to 2 Mbps Serial 100 kbps
60

1553 B
Salient features, A and B, Data Encoding, Architecture, Components, Word format
61

1553 A & 1553 B

1553 A a MIL std ( not fully defined from the user point) 1553 B A fully defined from the user point of view for hardware and software Has 2 types of Coupling (STP and Transformer) to the data bus

62

Features
1. 2. 3. 4. 5. 6. 7. 8.

A Serial dual redundant Duplex bus on 1 Mbps Manchestor Data Encoding 16 Bit word Size Data Modulation by PCM Using both Twisted Pair and Transformer for coupling BC,RT & BM connected to the bus, RT-stand alone Unit Can connect 31 RT-s remote terminals
63

1553 B STP coupling in an Aircraft

64

Manchestor Data Encoding

65

1553B Transformer coupling in an Aircraft

66

Transformer or Direct Coupling

67

Architecture of 1553B

68

Architecture of 1553 B
B U S C O N Channel A Channel B

Remote Terminal 1

Remote Terminal 2

Remote Terminal 3

Bus Monitor

69

1553 Bus Structure

70

Remote Terminal

71

Remote Terminal

72

Bus controller

73

Bus Monitor

74

Architecture
A dual-redundant bus 2. A Bus Controller responsible for communication over the bus, and for detecting and correcting errors 3. 3 Remote Terminals Responsible for acquiring data from one Subsystem and transferring to another subsystem 4. A Bus Monitor-For monitoring all transactions over the bus and storing the data.BM does not transmit
1.
75

Functions of the components

1) 2) 3)

Bus controller- responsible for directing the flow of data into the bus Remote Terminal-responsible for receiving the data and storing the data Bus Monitor-Responding to the commands addressed to Bus Monitor where 31 RT-s connected, but cannot transmit data
76

1553 In field

77

Industry MIL Standard 1553 B

78

Bus Controller
Supporting 128 kBytes memory Synchronous or Asynchronous interface Clock rate 12, 14, 16 or 24 MHz Verilog Source Code Use Ma nchestor Encoding

79

Word format

80

Word Format of 1553B

1.

2.
3.

3 Types of Words-CW,SW and DW in 1553 B Word Size 20 bits 3 bits for synchronization, 16 bits data and 1 bit for parity Command Word CW transmitted by BC Status Words SW transmitted by RT Data Word DW transmitted by BC or RT
81

1553 B Bus Word Format

82

3 Types of Data Transfers

1. 2. 3.

BC to RT -Bus Controller to Remote Terminal RT to BC Remote Terminal to Bus Controller RT to RT-Remote Terminal to Remote Terminal

83

Status Word-RT to RT
Transmitted by RT from BC 3 bit-time sync pattern (same as for a command word) 16 bits for Data in Status 1 parity check bit.

84

Status Word=20 bits

3
Sync

16
Data One word=20 Bits

1
Parity

85

Command Word-BC to RT

20 bit word Transmitted by Bus Controller of which (no BC address) 3 bits for sync using Manchestor coding 5 bits for address of RT 1bit Transmit/Receive (T/R) indicating data direction (T means Data recd by RT) 5 bits for sub address under RT address to memory etc 5 bit for data word count,indicating the word count after the sub address. 1 bit for parity check (using Odd parity)
86

Command Word ( Transmitted by BC)

3 Sync

5
RT Address

1
T/R

5
Sub address

Word Count Parity

One Command word=20 Bits

87

Data Word RT to BC
20 bit Data Word transmitted by RT or BC against a BC request 3 bits for sync pattern (opposite in polarity from command and status words) 16 bit for data field 1 bit for parity check bit.

88

Data Word RT to BC)

16
Data

1
Parity

Sync

89

Mode Codes for BC for Data Base management

1.

2.
3. 4. 5.

00000 Dynamic Bus Control 00001 or 10000 Synchronise 00010 Transmit Status 00100 Transmit Shut down 01000 Reset Remote Terminal

90

Comparison between 629 & 1553

No Description 629 1553

1
2

Architecture
Signal Format and Parity Data Bus Terminals Coupling
Data System & speed

IMA+Fed RTZ Odd

2 RT One BM

IMA
Manchestor Odd
3RT, One BC &BM STP &Transformer

3
4 5

STP Duplex 2 Mbps

Multiplex 1 Mbps

91