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
ARINC, 1553 1773

23

Aeronautical Standards
ARINC-Aeronautical Radio IncorporatedArinc 400 series and Arinc 600,700 and 800 series, used by Boeing MIL Military, MIL 1553 standard Airbus

24

ARINC 429

25

ARINC 429 in brief

An Old, Simplex, Dedicated I/O Open system Point to Multipoint, Asynchronous system Operate on both discrete and analog signals Sub Systems include FMS,ILS, VHF,Display system

26

ARINC-429
Unidirectional Bus operating at either 12.5 14.5 kbps or 100 kbps A Simplex Bus ( one TX and many Receivers) No Bus Controller, RT, or Bus Monitor contrary to 1553 ARINC use 32 Bit word with Odd Parity Waveform for ARINC is RTZ Bipolar

27

RTZ Bipolar Format

28

ARINC Avionic Data Bus in Boeing

29

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

30

ARINC 429 Architecture

31

ARINC 429 INTERFACE thru RS232

32

Word Format for Arinc 429

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

33

Arinc Word Format

32 BIT Format 1-8 for Label (type of Data-BCD) 9 & 10 for SDI ( Source Destination Identifier)-1 TX and 20 RX 11 to 29 Data 30 & 31 for SSM( Sign/Status Matrix) 32 for Parity

34

Word Format for Arinc 429

10

30

31 32

0-32 bits for Arinc 429 1-8 bit for Label Bit 9 & 10 Station Identifier 11-29 for Data 30 & 31 bit =Sign and Status Bit Bit 32 for Parity
35

Arinc 429 Word Format

36

Other ARINC Protocols

1.

2.
3. 4. 5.

Arinc Arinc Arinc Arinc Arinc

419 453 in Inertial Navigation system 568 in Flight Recorder 619 629 used in Boeing 777

37

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

38

General Features of ARINC 629

1.

2.

3. 4. 5. 6. 7.

8.

ARINC629- Multi transmitter to Multi receivers ARINC 629 = two independent MAC protocols for communications across a 20 Mbps Serial data bus High Speed Bi directional Bus (used in latest Boeing 777) ARINC 629- periodic and a-periodic transmissions 2 Protocols-Basic Protocol and Combined protocol; Basic protocol for flight controls, Combined protocol for flight management system No bus Controller required

39

4 Protocol Layers of 629

40

4 Protocol layers of Arinc 629

1.Physical layer- Layer-Main computational component interacting with shared memory, using 2 Mbps Serial Data Transmission on Twister pair cable Multiple timers and circuitry employed for collision avoidance on twisted pair cable with 20 Mbps serial data 2.Data Link Layer-dealing with single source to many terminals for data Using TDMA Has Basic Protocol and Combined protocol existing individually in the same bus due to their differences. Using Collision Avoidance logic, for accessing a channel across all terminals 3. Network Layer-dealing with networks for 20 bit words upto 256 data words 4.Upper Layer-presenting application, session, 41 presentation and transport layer

Basic Protocol-BP ( for Flight control)

CSMA/CA scheme defined in BP Operate either on periodic or aperidic, but not simultaneously Variable 31 Word Strings Used in Flight control long messages driving the bus from periodic to aperiodic mode

42

Protocol Layer-contd

Basic Protocol (DL):All transmissions fixed for periodic mode and individual transmissions vary for a-periodic modehave Terminal Gap, Synchronization gap

43

Combined Protocol-CP ( FMS system)

CAMA/CA defined in CP Shortfalls in BP for Periodic and Sporadic data transmissions. Sporadic data serviced when all periodic data have been completed Unique TG pre-assigned Periodic Data compressed into Burst, separated by TG

44

Difference between BP & CP

BP
Transmitting either Periodic or aperiodic Terminals transmit at const speed, if there is no overload If there is overload, data switched to aperiodic mode

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

ARINC 629 card

46

Arinc 629 Interface

47

Word Format for ARINC 629

20 bit word using CSMA/CA protocol 11 bits as Label 1 Bit for Parity 4 bits for CID 4 Bits for Synchronization(High Low Synchronization)

48

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

49

Channel Identification CID

629 messages -series of word strings Label- the First word in a string (111)marked in reverse Channel identification-the word string after a Label (12-15) CID-to identify a unit in a word string

50

Label Word
16 Bits assigned between Synchronization bits and parity bit- are Labels Synchronization bits to identify a Label Word Label bits numbered in reverse

51

3 Timing Conditions of ARINC 629 to access a terminal

1.

2.

3.

Transit timing condition T1- the moment the terminal starts transmittingT1 starts Synchronization gap-SG condition SG-starts the moment the terminal is quiet Terminal Gap condition TG-an unique timer assigned to the terminal; TG begins when SG is elapsed. TG & SG cannot overlap
52

Timing diagram-Periodic mode

Delay until T1 elapse

T1

TG2

T2

Tn

SG

Constant T1

53

Timing diagram-Periodic mode

When terminal starts Transmission, T1 timer starts SG timer starts when the Bus is quiet TG timer starts when SG has elapsed

54

Timing Diagram-Aperiodic Mode

T1 stop

start

T2

Tn

SG TG1 TG2 TGn

Variable T1
55

Comparison between 429 & 629

N o
1 2

Parameter
Architecture Flow of Data

ARINC 429
On Federated Uni directional Simplex 32 bit in RTZ SP-MP Asynch.

ARINC 629
On IMA Bi Directional Duplex 20 bit word Basic & Combined MP-MP Sync & Async 2 Mbps Serial
56

3 4

Word Size Protocol

Transmission Speed

12.5 Kbps or 100 kbps

1553 B

57

1553 B Salient Features

A Serial TDMA 1 Mbps Data Bus commonly used in Civil Aircrafts, ships, submarines Using both Twisted Pair and Transformer for coupling 3 Devices ( BC,RT & BM) to the bus, RT-stand alone Unit A dual redundant Balanced physical layer, Differential Network Interface, TDM, Half-duplex command/response protocol witho 31 remote terminals

58

1553 A & 1553 B

1553 A MIL std, not fully defined from the user point 1553 B fully defined from the user point of view for both hardware and softwaretwo types of Coupling (STP and Transformer) to the data bus

59

1553 Block diagram

60

1553 B in an Aircraft

61

1553 Architecture

62

1553 Bus Structure

63

Architecture of 1553 B
Bus controller- the Master Device responsible for directing the flow of data into the bus 2) Remote Terminal-responsible for receiving the data and storing the data for flight test, maintenance and mission analysis 3) Bus Monitor-Responding to the commands addressed to Bus Monitor where 31 RT-s connected, but cannot transmit data
1)

64

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

65

Data Encoding in 1553 BManchestor

66

Industry MIL Standard 1553 B

67

Components of 1553 B
A dual-redundant MIL-STD-1553B bus A Bus Controller responsible for initiating message communication over the bus, detecting and correcting errors Three Remote Terminals Responsible for acquiring data from one Subsystem and transferring to another subsystem(eg, data from inertial navigation to cockpit display) A Bus Monitor-Responsible for monitoring all transactions over the bus and storing the data for later analysis, but does not transmit

68

Technical Features of 1553 B

Data Speed 1 Mbps Data Encoding by Manchestor Modulation of data by PCM Access by TDMA Data Size=16 bit word 3 types of data transfers between RT and BC

69

Types of Data Transfer in 1553 B

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

70

71

1553 B Bus Controller Summary

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

72

Components of 1553B
1.

2. 3.

4.

Encoder/Decodeer-input serial data using Manchestor coding with 12,16 or 24 Mhz clock Protocol Controller for message sequencing and error control CPU access the Block controller within the system Backend interface enabling the connection to a memory device
73

Simple Remote Terminal ( Redundant Bus)

74

Word Format of 1553B

1. 2. 3.

3 Types of Words in 1553 B of 20 bits with 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

75

1553 B Bus Word Format

76

Status Word=20 bits(Tx by BC)

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.

77

Status Word=20 bits

3
Sync

16
Data One word=20 Bits

1
Parity

78

Command Word ( Tx by BC)

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)
79

Command Word ( Transmitted by BC)

3 Sync

5
RT Address

1
T/R

5
Sub address

Word Count Parity

One Command word=20 Bits

80

Data Word (by RT/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.

81

Data Word ( Tx by RT/BC)

16
Data

1
Parity

Sync

82

Distinction between 629 & 1553

No Description 629 1553 1 2 3 4 5 6 Architecture Word Format in Sync & Parity Terminals on Data Bus Coupling by Data System & speed Data Word Size IMA RTZ Odd 2(RT & BM) STP Multiplex 2 Mbps 20 Bit IMA Manchestor Odd 3 (RT,BC,BM) STP &Transformer Multiplex 1 Mbps 16 bit
83