Design considerations in Boeing 777 fly-by-wire computers
- 27 November 2002
- proceedings article
- Published by Institute of Electrical and Electronics Engineers (IEEE)
Abstract
The new technologies in flight control avionics systems selected for the Boeing 777 airplane program consist of the following: Fly-By-Wire (FBW), ARINC 629 Data Bus, and Deferred Maintenance.The FBW must meet extremely high levels of functional integrity and availability. The heart of the FBW concept is the use of triple redundancy for all hardware resources: computing system, airplane electrical power, hydraulic power and communication paths.The multiple redundant hardware are required to meet the numerical safety requirements. Hardware redundancy can be relied upon only if hardware faults can be contained; fail-passive electronics are necessary building blocks for the FBW systems. In addition, FBW computer architecture must consider other fault tolerance issues: generic errors, common mode faults, near-coincidence faults and dissimilarity.Keywords
This publication has 13 references indexed in Scilit:
- SAFEbusPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2003
- Triple-triple redundant 777 primary flight computerPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- MAFT - An architecture for reliable fly-by-wire flight controlPublished by American Institute of Aeronautics and Astronautics (AIAA) ,1988
- Commercial jet transport fly-by-wire architecture considerationsPublished by American Institute of Aeronautics and Astronautics (AIAA) ,1988
- An air data inertial reference system for future commercial airplanesPublished by American Institute of Aeronautics and Astronautics (AIAA) ,1988
- Fault tolerant avionicsPublished by American Institute of Aeronautics and Astronautics (AIAA) ,1988
- In search of effective diversity: a six-language study of fault-tolerant flight control softwarePublished by Institute of Electrical and Electronics Engineers (IEEE) ,1988
- An experimental evaluation of the assumption of independence in multiversion programmingIEEE Transactions on Software Engineering, 1986
- Generic Faults and Architecture Design Considerations in Flight-Critical SystemsJournal of Guidance, Control, and Dynamics, 1983
- The Byzantine Generals ProblemACM Transactions on Programming Languages and Systems, 1982