Browse Topic: Integrated modular avionics

Items (61)
Find
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-3 (Current)11/15/2021
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Part 0 has been adjusted to reflect technical changes made in Supplements to Parts 1 through 5 in conjunction with the technical changes made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 – Overview of ARINC 653 Part 1 – Required Services Part 2 – Extended Services Part 3A – Conformity Test Specification for ARINC 653 Required Services Part 3B – Conformity Test Specification for ARINC 653 Extended Services Part 4 – Subset Services Part 5 – Core Software Recommended Capabilities The term “this document” refers to Part 0 only, while the term “ARINC 653” or “the Specification” refers to the whole set of ARINC 653 documents, currently Parts 0 to 5. The primary objective of ARINC 653 is to define a general-purpose APplication/EXecutive (APEX) interface (API = Application Program Interface) between the Core Software
Airlines Electronic Engineering Committee
Specification
Mathematical Programming for Optimization of Integrated Modular Avionics2021-01-000903/02/2021
Every state-of-art aircraft has a complex distributed systems of avionics Line Replaceable Units/Modules (LRUs/LRMs), networked by several Data buses. These LRUs are becoming more complex because of an increasing number of new functions need to be integrated into avionics architecture. Moreover, the complexity of the overall avionics architecture and its impact on cable length, weight, power consumption, reliability and maintainability of avionics systems encouraged manufacturers to incorporate efficient avionics architectures in their aircraft design process. The evolution of avionics data buses and architectures have moved from distributed analog and federated architecture to digital integrated modular avionics (IMA). IMA architecture allows suppliers to develop their own LRUs/LRMs capable of specific features that can then be offered to Original Equipment Manufacturers (OEMs) as Commercial-Off-The-Shelf (COTS) products. In the meantime, the aerospace industry has been investigating
Radaei, Mohammad
Technical Paper
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICESARINC653P2-4 (Current)12/23/2019
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 4 adds optional multicore services capabilities.
Airlines Electronic Engineering Committee
Specification
The Research on Validation and Verification Method of Configuration Data for IMA Resources Allocation2019-01-185009/16/2019
Integrated Modular Avionics (IMA) system comprises IMA platform and hosted applications. The IMA platform provides the hosted applications with shared resources, e.g. computing, memory, communication, health monitoring resources. As a bridge between them, the IMA configuration data specifies how these shared resources are allocated to each hosted application. The IMA configuration data, which is different from real hardware and software code, should be validated and verified as an important portion of IMA system. After a brief introduction of IMA system, development processes, and general means of compliance for certification, this paper proposed an Architecture Analysis and Design Language (AADL) model of IMA configuration based on a case study of airborne datalink system. Based on the model, the IMA configuration data is abstracted and categorized into several types, with the correspondent means of compliance identified for each type. Furthermore, the associated roles and
Wang, Yunsheng, Li, Yan-xiao
Technical Paper
Collins Aerospace provides avionics for C-130H modernization programSAE-MA-0000209/03/2019
The Lockheed C-130H Hercules fleet operated by the Air National Guard and U.S. Air Force Reserve is getting new Collins Aerospace Systems avionics that will help extend the life of the legacy aircraft by 20 years.
Kucinski, William
Magazine
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 5 CORE SOFTWARE RECOMMENDED CAPABILITIESARINC653P5-1 (Current)08/07/2019
Part 5 defines additional ARINC 653 core software capabilities to ease integration on a variety of Integrated Modular Avionics (IMA) hardware platforms by allowing platform suppliers to extend and customize it for use with their unique hardware platform. Supplement 1 expands the guidance provided on resource profiling and execution profiling pertinent to the use of mulicore processors in avionics.
Airlines Electronic Engineering Committee
Specification
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-2 (Current)08/07/2019
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Part 0 will be made more consistent with Parts 1 through 5 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.
Airlines Electronic Engineering Committee
Specification
An Open Source Domain-Specific Avionics System Architecture Model for the Design Phase and Self-Organizing Avionics2019-01-138303/19/2019
State-of-the-art avionics systems are standardized, e.g. the computing system of the flying vehicle is composed of pre-defined and pre-qualified modules of a standardized avionics platform. Integrated Modular Avionics (IMA) is the most popular representative, but not the only one. Two challenges of standardized avionics platform are system design and configuration. Since the high numbers of functions, modules, and constraints for modern air vehicles, bringing up the optimal system architecture is a difficult job if carried out manually. The subsequent process of creating millions of configuration parameters is time consuming and error prone. Both issues are similar and are, in general, processable by algorithms. Algorithms proved to provide significant support for current system design issues and might be mandatory in future, when avionics become self-organizing and the design and configuration are derived by the platform itself. Automated design already proved its advantages and self
Annighoefer, Bjoern
Journal Article
SAE Architecture Analysis and Design Language (AADL) Annex Volume 2:Annex B: Data Modeling AnnexAnnex D: Behavior Model AnnexAnnex F: ARINC653 AnnexAS5506/2 (Current)02/18/2019
AS-2C Architecture Analysis and Design Language
Technical Standard
Anomaly Based Intrusion Detection for an Avionic Embedded System2018-01-194110/30/2018
This paper firstly describes the challenges raised by the introduction of Intrusion Detection Systems (IDS) in avionic systems. In particular, we discuss some specific characteristics of such systems and the advantages and limitations of signature-based and anomaly-based techniques in an avionics context. Based on this analysis, a framework is proposed to integrate a Host-based Intrusion Detection System (HIDS) in the general Integrated Modular Avionics (IMA) development process, which fits avionic systems constraints. The proposed HIDS architecture is composed of three modules: anomaly detection, attack confirmation, and alert sending. To demonstrate the efficiency of this HIDS, an attack injection module has also been developed. The overall approach is implemented on an IMA platform running a cockpit display function, to be representative of embedded avionic systems.
Damien, Alienor, Fumey, Marc, Alata, Eric, Kaâniche, Mohamed, Nicomette, Vincent
Technical Paper
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3A CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 REQUIRED SERVICESARINC653P3A-1 (Current)09/07/2018
ARINC 653, Part 3A is the Compliance Test Specification for ARINC 653 Required Services presently defined in ARINC 653 Part 1. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 1.
Airlines Electronic Engineering Committee
Technical Standard
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3B CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 EXTENDED SERVICESARINC653P3B (Current)09/07/2018
ARINC 653, Part 3B is the Compliance Test Specification for ARINC 653 Extended Services presently defined in ARINC 653 Part 2. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 2.
Airlines Electronic Engineering Committee
Technical Standard
ADVANCED FLIGHT MANAGEMENT COMPUTER SYSTEMARINC702A-5 (Current)08/28/2018
The Advanced FMCS provides expanded functions beyond that defined in ARINC 702 to support the anticipated requirements for operation in the CNS/ATM operating environment. GNSS and RNP based navigation, air-to-ground data link for communications and surveillance, and the associated crew interface control/display definitions are included. The NextGen/SESAR concepts and their relative effects on the FMS are addressed in this document. The functional requirements also apply to a Flight Management Function (FMF) in an Integrated Modular Avionics (IMA) architecture with software partitions.
Airlines Electronic Engineering Committee
Characteristic
In-Flight Real-Time Avionics AdaptationTBMG-3273408/01/2018
Avionics is a very restricting domain for obvious safety reasons. Along with miniaturization comes the idea of integration. More functionality on one spot requires a good management of privacy and congestion on shared platforms. This is why determinism is one of the keywords of avionics works. This led to protocols like ARINC653[1] assuring that multitask embedded programs respect a predictable policy applied by the operating system (OS). Another key protocol is ARINC664, which guarantees that multiple communicating systems efficiently share the network. These two protocols are pillars of the Integrated Modular Architecture (IMA) concept[2].
Magazine Article
Affordable Vehicle Avionics (AVA)TBMG-2903806/01/2018
NASA Ames Research Center has developed a novel, low-cost, self-contained guidance system for small payload operators. Small satellites are becoming ever more capable of performing valuable missions for both government and commercial customers; however, currently these satellites can only be launched affordably as secondary payloads, which makes it difficult for the small satellite mission to launch when needed, to the desired orbit, and with acceptable risk.
Magazine Article
In Flight Real-Time Adaptation2017-01-216909/19/2017
Avionics is one kind of domain where prevention prevails. Nonetheless fails occur. Sometimes due to pilot misreacting, flooded in information. Sometimes information itself would be better verified than trusted. To avoid some kind of failure, it has been thought to add an new kind of embedded monitoring that enable adaptation.
Granado, Bertrand, Gatti, Marc, Denoulet PhD, Julien, Rayrole, Martin
Technical Paper
Evaluating Key Certification Aspects of Multicore Platforms for Safety Critical Avionics ApplicationsTBMG-2643802/01/2017
High performance, low power consumption and small footprint requirements imposed by the embedded market on the processor industry is causing a definite move away from single-core processors to multicore processors. Multicore processors have been deemed as the future of Size, Weight, and Power (SWaP) constrained applications like military and avionics. They provide higher performance (MHz/W) at lower power. They also allow consolidation of multiple functions/ applications onto a single platform.
Magazine Article
Evaluating Key Certification Aspects of Multicore Platforms for Safety Critical Avionics Applications17AERP02_0302/01/2017
High performance, low power consumption and small footprint requirements imposed by the embedded market on the processor industry is causing a definite move away from single-core processors to multicore processors. Multicore processors have been deemed as the future of Size, Weight, and Power (SWaP) constrained applications like military and avionics. They provide higher performance (MHz/W) at lower power. They also allow consolidation of multiple functions/applications onto a single platform.
Magazine Article
Embedded Real-Time Monitoring Using SystemC in IMA Network2016-01-206909/20/2016
Avionics is one kind of domain where prevention prevails. Nonetheless failures occur, sometimes due to pilot misreacting, flooded in information. Sometimes information itself would be better verified than trusted. To avoid some kind of failure, it has been thought to add,in midst of the ARINC664 aircraft data network, a new kind of monitoring.
Aloui, Zied, Ahamada, Nawfal, Denoulet, Julien, Rayrole, Martin, Pierre, Francine, Gatti, Marc
Technical Paper
An Adaptive Software Architecture for Future CMS2015-01-254509/15/2015
Aircraft cabin systems, especially cabin management systems (CMS) have to cope with frequent cabin changes during their lifecycle. This includes not only layout rearrangements and technological upgrades during the service, but also extensive CMS customizations and product variations before aircraft delivery. Therefore it is inevitable for the CMS to be highly changeable and offer an easy and agile change process. Today's CMS solutions face this challenge with configurable system architectures. Although such architectures offer a vast change domain, they usually come with time consuming and error prone change processes. This paper introduces an adaptive avionics software architecture that enables the CMS to cope with cabin changes highly automatically and with minimal human interactions. The adaptation is performed during an on ground organization phase, in which system changes are detected and evaluated by the CMS itself. Consequently the CMS instantiates and adapts the software within
Ahmadi, Reza, Marquardt, Oliver, Riedlinger, Marc, Reichel, Reinhard
Journal Article
Model-based Method to Automate the Design of IMA Avionics System Based on Cosimulation2015-01-253109/15/2015
In the aerospace industry, as the modern avionics systems became more and more complex, the Integrated Modular Avionics (IMA) architecture has been proposed as a replacement of the federated architecture, in order to offer better solutions on SWaP constraints (Size, Weigh and Power). However, the development process of IMA avionics systems is much more difficult. This paper aims to propose to the aerospace industry a set of time-effective and cost-effective solutions for the integration and functional validation of IMA systems. Based on MBE methodology, which is considered as an interesting solution for the IMA systems development [8], this paper proposes a design flow, that integrates three steps of refinement, for the configuration and the validation of IMA platforms. In the first step of the design flow, the modeling language AADL is used to describe the IMA architecture. The AADL modeling environment OCARINA, a code generator initially designed for the real-time operating system
Bao, Lin, Bois, Guy, Boland, Jean-François, Savard, Julien
Journal Article
Evaluation of Key Certification Aspects of Multi Core Platforms for Safety Critical Applications in Avionics Industry2015-01-252409/15/2015
Multi core platforms offer high performance at low power and have been deemed as future of size, weight and power constrained applications like avionics safety critical applications. Multi core platforms are widely used in non-real time systems where the average case performance is desired like in consumer electronics, telecom domains. Despite these advantages, multi core platforms (hardware and software) pose significant certification challenges for safety critical applications and hence there has been limited usage in avionics and other safety critical applications. Many multicore platform solutions which can be certified to DO-254 & DO 178B Level A are commercially available. There is a need to evaluate these platforms w.r.t certification requirements before deploying them in the safety critical systems thereby reducing the program risks. This paper discusses the advantages of multi core platforms in terms of performance, power consumption and weight/size. Certification challenges
Gampa, Srikanth
Technical Paper
Integration and Performances Analysis of a Data Distribution Service Middleware in Avionics2015-01-255409/15/2015
The amount of functionalities in modern aircrafts is increasing to satisfy performance, safety and economic benefits. Therefore, the communication needs of avionic systems are growing. Furthermore, the portability and reusability of applications are current challenges of the aerospace industry. The use of the Data Distribution Service (DDS) middleware technology would reduce the complexity of communications and ease the portability and reusability of applications with its standardised interface. Few previous works used a DDS middleware within the aerospace industry and those didn't take into account the impact of this technology on the applications performances. Therefore, this paper presents an impact evaluation of using a DDS middleware on the performances of avionic applications. To do so, a design methodology was proposed to design an automatic flight control system (AFCS) from a high abstraction level representation of a control loop to a low-level implementation on a development
Landry, Kevin, Boland, Jean-François, Bois, Guy
Technical Paper
AVIONCS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICESARINC653P2-3 (Current)08/21/2015
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 3 adds optional multicore services capabilities.
Airlines Electronic Engineering Committee
Technical Standard
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-1 (Current)08/03/2015
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Parts 1 through 5 will be made more consistent with Part 0 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.
Airlines Electronic Engineering Committee
Technical Standard
Core Flight System (cFS) Software Bus Network Application Version 1.0TBMG-2202605/01/2015
The Software Bus Network (SBN) is a plug-in component developed for the Core Flight System (cFS) framework that extends the core Flight Executive (cFE) Software Bus (SB) publish/subscribe messaging service across partitions, processes, processors, and networks. This extension is done transparently for cFS software components, such that cFS software components remain unchanged and are unaware of source or destination(s) location.
Magazine Article
Habitat Demonstration Unit Core Avionics SoftwareTBMG-2142002/01/2015
The Habitat Demonstration Unit Core Avionics Software (HDU-CAS) is designed to provide the required functionality for an engineering prototype of a highly autonomous space habitat element, and to provide an opportunity for new software technologies to be tested in an environment that provides that functionality. The HDU itself must provide basic environmental and infrastructure services, while also supporting a variety of integrated subsystems that aid in the fulfillment of space mission operations. The HDU-CAS must then provide complete command and data handling, and intelligent autonomous operations functions of these needed subsystems in all appropriate circumstances (nominal and off-nominal).
Magazine Article
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 5 CORE SOFTWARE RECOMMENDED CAPABILITIESARINC653P5 (Current)12/01/2014
The objective of this part is to define additional ARINC 653 core software capabilities to ease integration on a variety of Integrated Modular Avionics (IMA) hardware platforms by allowing platform suppliers to extend and customize it for use with their unique hardware platform. The objective of Part 5 is to define additional recommended capabilities when implementing ARINC 653 core software using a Commercial off the Shelf (COTS) ARINC 653 Operating System (O/S).
Airlines Electronic Engineering Committee
Technical Standard
Technological Changes and Competitive Advantage: The New Deal for Avionics Firms2014-01-217309/16/2014
Since 2000, avionics is facing several changes, mostly driven by technological improvements in the electronics industry and innovation requirements from aircraft manufacturers. First, it has progressively lost its technological leadership over innovation processes. Second, the explosion of the electronics consumer industry has contributed to shorten even more its technology life cycles, and promoted the use of COTS. Third, the increasing complexity of avionics systems, which integrate more and more functions, have encouraged new players to enter the market. The aim of this article is to analyze how technological changes can affect the competitiveness of avionics firms. We refer to criticality levels as a determinant of the market competitiveness. Certification processes and costs could stop new comers to bring innovations from the consumer electronics industry and protects traditional players. The study will compare three avionics systems regarding their patent dynamics since 1980
Beaugency, Aurelie, Gatti, Marc, Regis, Didier
Technical Paper
ECOA - A New Architecture Concept for Complex Military Software Systems2014-01-222709/16/2014
ECOA is an active software architecture research programme conducted by the French Republic and United Kingdom. It is one product of the recent Defence and Security Co-operation Treaty signed between the two nations. This paper provides an overview of the programme goals and progress as well as an introduction to the technology being developed and comparison to related initiatives. The goal of the ECOA programme is to define an open software architecture that enables collaborative development of mission system software. The ECOA programme is needed to reduce development and lifecycle costs of future military air programmes. For this reason the programme has a specific focus on combat-air mission systems but the underlying technology is general purpose, applying to multiple military and civil domains. At present, the programme has defined a concept, delivered a set of initial technical standards and produced a joint demonstrator to validate the technology developed.
Cornilleau, Thierry, Linard, Pierre, Moxon, Paul, Nicholas, Christopher
Journal Article
Fully Configurable Interrupt ControllerTBMG-2055809/01/2014
An interrupt is a signal in an interrupt controller (IC) that pulses to indicate an event or error. The IC is responsible for processing multiple internal interrupts and making these interrupts available to a host computer via a data bus or external output pins. Since there exist numerous interrupts, a method must be developed for routing the interrupts to the external output pins.
Magazine Article
Method for Authorizing Critical Effector Commands in a Space-Based Integrated Modular Avionics SystemTBMG-2055709/01/2014
An Integrated Modular Avionics (IMA) architecture provides a common platform for software partitions with shared processing and input/output (I/O) resources. A key feature of the IMA architecture is I/O partitioning. An IMA system will prevent one software partition from changing an I/O resource that is owned by another software partition. This prevents one software partition from controlling the outputs of another due to hardware fault or software error. The IMA system must have protection mechanisms in place to enforce the I/O partitioning.
Magazine Article
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE, PART 3A, CONFORMITY TEST SPECIFICATION FOR ARINC 653 REQUIRED SERVICESARINC653P3A (Current)01/13/2014
The scope of this Compliance Test Specification is to define test procedures to demonstrate compliance of the API behavior only. This does not include performance tests (e.g., benchmark tests), nor demonstration of capability of the operating systems to manage combinations of configuration parameters.
Airlines Electronic Engineering Committee
Technical Standard
Model-Based Design Flow Driven by Integrated Modular Avionic Simulations2013-01-221109/17/2013
The Integrated Modular Avionics (IMA) architecture has been a crucial concern for the aerospace industry in developing more complex systems, while seeking to reduce space, weight and power (SWaP), as well as development, certification and production time. From a software perspective, that objective pushes developers to migrate toward safety critical space and time partitioning environment. However, mainstream commercial real-time operating systems (RTOS) offering such partitioning can be restrictive in early development due to very high licensing costs. That situation is even more striking when considering that low-cost alternatives could instead be used for system modeling and early simulation before acquisition of a target platform. This paper reviews existing low-cost and open-source development environments to propose a novel design flow. The proposed methodology starts with model-based analysis in the AADL modeling language. Then, configuration files and software integration code
Savard, Julien, Bao, Lin, Bois, Guy, Boland, Jean-François
Technical Paper
A System Architecture for Smart Sensors Integration in Avionics Applications2012-01-212510/22/2012
With the next generation of avionics systems, more sensors and actuators will be required for an ever increasing number of functions. In this paper, we propose a system architecture based on several enhancements to the IEEE 1451 standard, granting it a wider application range, improved resource efficiency and a generic and reusable character. This architecture facilitates the integration of next generation smart sensors with a wide range of avionics data communication networks and allows the specification of generic features to be respected. In order to meet the requirements of avionics applications, this architecture that provides a design framework offers customization of features such as bandwidth, reliability, resources utilization and compatibility with different types of transducers, especially smart sensors. The resulting resource utilization and reliability are analyzed for several configurations that provide a basis for comparison. To validate the proposed architecture and the
Tremblay, José-Philippe, Savaria, Yvon, Zhu, Guchuan, Thibeault, Claude, Bouanen, Safwen
Journal Article
AADL-Based Toolset for IMA System Design and Integration2012-01-214610/22/2012
The paper presents an AADL-based toolset for Integrated Modular Avionics (IMA) design and integration. It describes activities of IMA system designer and system integrator that are supported by the toolset as well as its current architecture and future directions of development.
Khoroshilov, Alexey, Albitskiy, Dmitry, Koverninskiy, Igor, Olshanskiy, Mikhail, Petrenko, Alexander, Ugnenko, Alexander
Journal Article
Integrating System and Software Engineering Activities for Integrated Modular Avionics Applications2012-01-213910/22/2012
Avionics systems are complex systems that integrate hardware, communication media, have many interactions with other subsystems, within or outside of the aircraft, and for the system discussed in this presentation, integrate software that must be developed according to DO-178B guidelines. System engineering and software engineering are two engineering disciplines that are historically handled by teams with different cultures, and when their engineering processes are supported by tools, use different and incompatible tools. This often leads to a difficult collaboration, with at some point, redundant information and inconsistencies. This presentation introduces a solution, based on the SysML standard for system modeling, and on the SCADE Suite product from Esterel Technologies for the development of DO-178B certified software components. This solution, named SCADE System, allows system and software engineers to work with the right formalism for their respective domains while improving
LeSergent, Thierry, Romeas, Frederic, TOURILLION, Olivier
Journal Article
Efficient Certification of Highly Integrated and Complex Aircraft Systems, Such as Integrated Modular Avionics2012-01-214310/22/2012
There are several relatively new certification standards related to Integrated Modular Avionics (IMA) certification that have recently been invoked by the certification authorities. These standards include SAE ARP-4754A, Guidelines for Development of Civil Aircraft and Systems, RTCA DO-297, Integrated Modular Avionics (IMA) Development Guidance and Certification Considerations, and RTCA DO-178C, Software Considerations in Airborne Systems and Equipment Certification. RTCA DO-254, Design Assurance Guidance for Airborne Electronic Hardware, and TSO C153, Integrated Modular Avionics Hardware Elements, are also applicable to IMA certification. As many of these standards have only recently been invoked in Advisory Circulars by the Certification Authorities, the industry has little experience in complying with them individually, and even less experience complying with them collectively. With the current trend of increased integration, and the application of IMA architectures to systems that
Gasiorowski, Marty
Journal Article
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 4-SUBSET SERVICESARINC653P4 (Current)06/28/2012
ARINC Specification 653 Part 4 was prepared to support controllers and relatively simple avionics. Part 4 is true subset of services specified in ARINC 653 Part 1. In the Subset Services, partition scheduling is restricted to only one partition time window within the partition's period. This simplifies the management of process release points. Process management uses a dual-process model with at most two processes within a partition, for example, foreground and background.
Airlines Electronic Engineering Committee
Specification
Braking Systems with New IMA Generation2011-01-266210/18/2011
First generation of Integrated Modular Avionics (IMA), currently onboard in aircraft type Airbus A380, A400M, or designed for Airbus A350, and whose principle was initially to introduce some common processing resources, had been developed in such a way to reduce the quantity of embedded equipment part number, and to harmonize the nature of the avionic units by minimizing the specificity of electronic equipment: thus, for instance, the number of processing units in the A380 is half that of previous LRU-based avionic generations. This type of architecture had already much interest at aircraft level; nevertheless, some of the designed electronic components were not able to support some performance requirements of the function suppliers, such as Messier-Bugatti-Dowty, which had to limit the deployment of the functions to implement in IMA; For this reason, it was still necessary to execute the fast control loops, as the antiskid algorithms, in specific remote electronics (RDC, RBCU
Bernard, Stephane, Garcia, Jean-Pierre
Technical Paper
ARP4754A/ ED-79A - Guidelines for Development of Civil Aircraft and Systems - Enhancements, Novelties and Key Topics2011-01-256410/18/2011
ARP4754A/ED-79A guidelines addresse the development cycle for aircraft and systems that implement aircraft functions. The current trend in system design is an increasing level of integration between aircraft functions and the systems that implement them. While there can be considerable value gained when integrating systems with other systems, the increased complexity yields increased possibilities for errors, particularly with functions that are performed jointly across multiple systems. Following the Aviation Rulemaking Advisory Committee (ARAC) recommendations to respond to this increased integration which referenced ARP4754/ED-79 in advisory materials for compliance to 14CFR/CS 25.1309 (see AMC 25.1309, published in 2002 and AC25.1309-Arsenal draft) the use of ARP4754A/ED79A in aircraft certification has become increasingly widespread. This presentation constitutes a comparison between the documents SAE [1] / EUROCAE [2] and SAE [3] / EUROCAE [4]; it highlights ARP4754A/ED79A
Landi, Alessandro, Nicholson, Mark
Journal Article
A Discussion on the Use of an Integrated Modular Avionics (IMA) Architecture to Simulate an Aerospace Control System2011-36-018210/04/2011
The use of control architectures with the Integrated Modular Avionics (IMA) concept (“IMA architectures”) in aerospace and the Integrated Modular Electronics (IME) concept (“IME architectures”) in automotive applications is growing due to its reduced number of hardware such as processors, Line Replaceable Units (LRUs) and Electronic Control Units (ECUs), thereby reducing weight and costs. Furthermore, IMA architectures can perform complex reconfigurations in the case of failures and adapt themselves to changes in network functioning or operating modes, which make a control system very robust. The objective of this work is to discuss the use of an IMA architecture to simulate an aerospace control system responsible for maintaining a vehicle in a predetermined trajectory. To do that, we review the current literature related to IMA architectures and give an overview of their characteristics. Then, we choose an aerospace control system and discuss its simulation using an IMA platform. The
Tagawa, Gitsuzo B. S., Souza, Marcelo L. O.
Technical Paper
Comparison of CAN, FlexRay, and Ethernet Architectures for the Design of ABS Systems2011-01-045304/12/2011
The rapid increase of networked electronic control units in airplanes (Line Replaceable Units or Modules, LRUs/LRMs) and automobiles (ECUs) requires to move from CAN buses to higher performance buses. In aircraft the number of LRUs exceeded 100 in 1990 (B777) and is now ≻5000 (A380). Today, the number of ECUs in some automobiles also exceeds 100. Aircraft industry developed solutions based on standard switched Ethernet (AFDX) and standardized ECUs, called Integrated Modular Avionic units (IMA units) and common remote data concentrators (cRDCs) that are now flying in the Airbus A380 and A400M, the Boeing B787, and are being used in the design of future civil and military aircraft. During the last decade, automotive industry has been pursuing the development of specialized FlexRay bus solutions for automotive control and specialized MOST bus solutions for comfort electronics. However, some automotive companies are now also looking at Ethernet-based solutions. This paper describes some of
Salzwedel, Horst
Technical Paper
Toward cockpit 3.010AEMD1027_0110/27/2010
Avionics developments further revolutionize the commercial cockpit environment. Looking up into the skies near any major international airport, it is often difficult to immediately identify different aircraft types. Today's Airbus A340 has almost exactly the same proportions and configuration as a Boeing 707 of 50 years ago, but it is on the inside of the aircraft, and in particular in the cockpit, where the greatest changes have taken place in recent decades and where the next big stepping stone toward fully automated commercial flight will emerge. When the civil jet age dawned, there were usually four crew members to be found at the front of an airliner. As digital flight controls and computerized avionics technology emerged in the 1980s, it became possible for airliner flight deck crews to shrink to just two, without any loss of safety or reduction in passenger confidence.
Gardner, Richard
Magazine Article
FAILSAFE Health Management for Embedded SystemsTBMG-843009/01/2010
The FAILSAFE project is developing concepts and prototype implementations for software health management in mission-critical, real-time embedded systems. The project unites features of the industry-standard ARINC 653 Avionics Application Software Standard Interface and JPL’s Mission Data System (MDS) technology (see figure). The ARINC 653 standard establishes requirements for the services provided by partitioned, real-time operating systems. The MDS technology provides a state analysis method, canonical architecture, and software framework that facilitates the design and implementation of software-intensive complex systems. The MDS technology has been used to provide the health management function for an ARINC 653 application implementation. In particular, the focus is on showing how this combination enables reasoning about, and recovering from, application software problems.
Magazine Article
Avionics System Architecture for the NASA Orion Vehicle2009-01-327611/10/2009
It has been 30 years since the National Aeronautics and Space Administration (NASA) last developed a crewed spacecraft capable of launch, on-orbit operations, and landing. During that time, aerospace avionics technologies have greatly advanced in capability, and these technologies have enabled integrated avionics architectures for aerospace applications. The inception of NASA's Orion Crew Exploration Vehicle (CEV) spacecraft offers the opportunity to leverage the latest integrated avionics technologies into crewed space vehicle architecture. The outstanding question is to what extent to implement these advances in avionics while still meeting the unique crewed spaceflight requirements for safety, reliability and maintainability. Historically, aircraft and spacecraft have very similar avionics requirements. Both aircraft and spacecraft must have high reliability. They also must have as much computing power as possible and provide low latency between user control and effecter response
Baggerman, Clint, McCabe, Mary, Verma, Dinesh
Technical Paper
A Multi-Core Platform for Integrated Modular Avionics Derived from a Cross-Domain Embedded System Architecture2009-01-326211/10/2009
In a European research project, a cross-domain embedded system architecture called GENESYS has been developed in order to take full advantage of the economies of scale of the semiconductor industry. The GENESYS system architecture defines a novel Multi-Processor System-on-a-Chip (MPSoC) as a basis for avionic, automotive, industrial control and medical applications. This paper shows how Integrated Modular Avionics (IMA) systems can be realized using this MPSoC platform. Middleware within the IP cores of the MPSoC establishes the services of the APplication EXecutive (APEX). Also, the economic and technical benefits of the MPSoC-based architecture are discussed. The cross-domain MPSoC allows to leverage the economics of scale, while also improving fault isolation, composability and predictability.
Obermaisser, R., Huber, B.
Technical Paper
Buses and Networks for Contemporary Avionics2007-01-380109/17/2007
MIL-STD-1553 has served the needs of military system integrators for over 30 years, particularly in the area of command and control applications. Nevertheless, contemporary applications such as high-speed digitized sensors, file transfers, processor clusters, and displays require much higher data rates than 1553's 1 Mb/s. For some environments, particularly for legacy aircraft, the optimal solution is to transmit faster data rates over existing 1553 buses. However, there are other applications that can accommodate and benefit by the deployment of gigabit or multi-gigabit copper or optical switched fabric networks. In addition to MIL-STD-1553, this paper presents and comments about several avionics networking technologies including High-Speed 1553, Fibre Channel, Gigabit Ethernet, and ARINC 664, a form of profiled Ethernet.
Glass, Mike
Technical Paper
Integration of Predictable and Flexible In-Vehicle Communication using Time-Triggered Ethernet2006-01-105504/03/2006
This paper presents a novel communication architecture denoted as time-triggered (TT) Ethernet that integrates real-time and non-real-time traffic into a single communication architecture. TT Ethernet supports applications of different levels of criticality, from simple data acquisition systems, to multimedia systems up to the most demanding fault-tolerant real-time control systems. The event triggered traffic in TT Ethernet is handled in conformance with the existing Ethernet standards of the IEEE. The architecture deploys a TT Ethernet switch, which distinguishes between event-triggered (ET) and time-triggered (TT) Ethernet traffic. Time-triggered traffic is transmitted with a predictable transmission delay, whereas event-triggered traffic is transmitted on a best-effort basis. The paper elaborates on the usage of TT Ethernet for in-vehicle communication in order to integrate different in-vehicle communication subsystems into a single communication architecture.
Ademaj, Astrit, Kopetz, Hermann, Grillinger, Petr, Steinhammer, Klaus, Prammer, Manfred
Technical Paper
HEAD-UP DISPLAY (HUD) SYSTEMARINC764 (Current)07/08/2005
This document defines a Head-Up Display (HUD) system intended for installation in all types of aircraft. It describes the physical form factors, fit dimensions, electrical interface definition and typical HUD functions, including the display of navigation and guidance information in the flight crew's forward field of view. The HUD accomplishes this by projecting images onto a combiner with symbology that conforms to the outside world view. Guidance for HUD architectures include single, twin, dual and HUD integrated with Primary Flight Display (PFD). This document is an practical guide for the design of federated equipment and integrated modular avionics.
Airlines Electronic Engineering Committee
Characteristic
Items per page:
1 – 50 of 61