Airbus flight control system

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.
Advertisements

September 18, A device for storing and retrieving digital information It consists of one or more rigid ("hard") rapidly rotating discs (platters)
Configuration management
Software change management
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Distributed Systems Architectures Slide 1 1 Chapter 9 Distributed Systems Architectures.
Full Authority Digital Engine Control
Distributed and Reconfigurable Architecture for Flight Control System EEL Embedded Systems Dept. of Electrical and Computer Engineering University.
NERC Lessons Learned Summary December NERC lessons learned published in December 2014 Three NERC lessons learned (LL) were published in December.
Rexroth IndraDrive Integrated Safety Technology
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development.
©Ian Sommerville 2000CS 365 Ariane 5 launcher failureSlide 1 The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its.
Software Evolution Managing the processes of software system change
©Ian Sommerville 2000Software Engineering, 6th edition Slide 1 Introduction l Getting started with software engineering l Objectives To introduce software.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
2. Introduction to Redundancy Techniques Redundancy Implies the use of hardware, software, information, or time beyond what is needed for normal system.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented design 2.
REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Basic Input/Output Operations
7. Fault Tolerance Through Dynamic or Standby Redundancy 7.5 Forward Recovery Systems Upon the detection of a failure, the system discards the current.
16: Distributed Systems1 DISTRIBUTED SYSTEM STRUCTURES NETWORK OPERATING SYSTEMS The users are aware of the physical structure of the network. Each site.
What is adaptive web technology?  There is an increasingly large demand for software systems which are able to operate effectively in dynamic environments.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 10 Slide 1 Formal Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Insulin Pump Slide 1 An automated insulin pump.
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
EMBEDDED SOFTWARE Team victorious Team Victorious.
Distributed Control Systems Emad Ali Chemical Engineering Department King SAUD University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Formal Specification.
©Ian Sommerville 2004Software Engineering Case Studies Slide 1 The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its.
Flight Control Systems and Actuators
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Airbus flight control system  The organisation of the Airbus A330/340 flight control system 1Airbus FCS Overview.
Unit 3a Industrial Control Systems
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 15 Slide 1 Real-time Systems 1.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 1.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering 2.
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
1 Fault Tolerance in the Nonstop Cyclone System By Scott Chan Robert Jardine Presented by Phuc Nguyen.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
Aerospace Fly-by-Wire History and Challenges 3 March, 2003 Don C. Winter Director – Research & Development Boeing Phantom Works.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
SUBMITTED BY PRAMOD H S DEPT OF MECHATRONICS JSS POLYTECHNIC NANJANGUD.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 3 Slide 1 Critical Systems 1.
 Chapter 13 – Dependability Engineering 1 Chapter 12 Dependability and Security Specification 1.
Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Pilot Training Minimum Equipment List. Overview The MEL has a lot of information helpful to pilots. To familiarize you with the MEL we will look at: ◦MEL.
CprE 458/558: Real-Time Systems
Idaho RISE System Reliability and Designing to Reduce Failure ENGR Sept 2005.
NCAF_May03.ppt Slide - 1 CSE International Ltd Data Integrity: The use of data by safety-related systems Alastair Faulkner CEng CSE International Ltd Tel:
©Ian Sommerville 2000Dependability Slide 1 Chapter 16 Dependability.
A new fail-safe principle for railway signaling
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter2: Systems Engineering l Designing, implementing, deploying and operating.
Week#3 Software Quality Engineering.
Transaction processing systems
FBW – Introduction The FBW architecture was developed in 1970’s
Engine Control Systems
FAULT TOLERANCE TECHNIQUE USED IN SEAWOLF SUBMARINE
Fault Tolerance Distributed Web-based Systems
Fault Tolerance Techniques of The Boeing 777
Presentation transcript:

Airbus flight control system The organisation of the Airbus A330/340 flight control system

“Fly by wire” control Conventional aircraft control systems rely on mechanical and hydraulic links between the aircraft’s controls and the flight surfaces on the wings and tail. The controls and flight surfaces are directly connected. Mechanical links are also used for the engine control. In fly-by-wire systems, the cockpit controls generate electronic signals that are interpreted by a computer system and are then converted into outputs that drive the hydraulic system connected to the flight surfaces. Engine control is also mediated by the FCS computers.

Advantages of ‘fly-by-wire’ Pilot workload reduction The fly-by-wire system provides a more usable interface and takes over some computations that previously would have to be carried out by the pilots. Airframe safety By mediating the control commands, the system can ensure that the pilot cannot put the aircraft into a state that stresses the airframe or stalls the aircraft. Weight reduction By reducing the mechanical linkages, a significant amount of weight (and hence fuel) is saved.

Fault tolerance Fly-by-wire systems must be fault tolerant as there is no ‘fail-safe’ state when the aircraft is in operation. In the Airbus, this is achieved by replicating sensors, computers and actuators and providing ‘graceful degradation’ in the event of a system failure. In a degraded state, essential facilities remain available allowing the pilot to fly and land the plane.

Hardware organisation Three primary flight control computers Responsible for calculations concerned with aircraft control and with sending signals to the actuators associated with the control surfaces and engines. Two secondary flight control computers Backup systems for the flight control computers. Control switches automatically to these systems if the primary computers are unavailable. Only one computer is required for flight control. Therefore, quintuple redundancy is supported. All operational computers operate in parallel so there is no switching delay. Two data concentrator computers Gather information from the flight control system and pass this to warning and display systems, flight data recorders and maintenance systems.

Hardware diversity The primary and secondary flight control computers use different processors. The primary and secondary flight control computers are designed and supplied by different companies. The processor chips for the different computers are supplied by different manufacturers. All of this reduces the probability of common errors in the hardware causing system failure.

Computer organisation Command unit Splitter Comparator Output Input Monitor unit Flight control computer

Computer organisation The command unit and the monitor unit are separate channels within a single computer. Each channel has separate hardware and different software. If the results of the channels disagree (as checked by the comparator) or are not produced at the same time then an error is assumed and control switches to another machine.

Software diversity The software for the different channels in each computer has been developed by different teams using different programming languages. The software for the primary and secondary flight control computers has been developed by different teams. For the secondary computers, different languages are again used for the different channels in each machine.

Dynamic reconfiguration The FCS may be reconfigured dynamically to cope with a loss of system resources. Dynamic reconfiguration involves switching to alternative control software while maintaining system availability. Three operational modes are supported Normal - control plus reduction of workload; Alternate - minimal computer-mediated control; Direct - no computer-mediation of pilot commands. At least 2 failures must occur before normal operation is lost.

Control diversity The linkages between the flight control computers and the flight surfaces are arranged so that each surface is controlled by multiple independent actuators. Each actuator is controlled by different computers so loss of a single actuator or computer will not mean loss of control of that surface. The hydraulic system is 3-way replicated and these take different routes through the plane.

Airbus FCS problems There have been a number of Airbus accidents that may be related to problems with the FCS. One accident (Warsaw runway overrun) has been clearly identified as a problem with the specification and not with the system itself. There is no evidence of any failures of the FCS hardware or software. However, the pilots may misinterpret how the system operates and hence make errors that it can’t cope with. Most likely when the system was newly introduced.