Browse Topic: Integrated modular avionics
In the early days of quality management, prior to 1980s, the focus seemed to be on "Quality Control" or "Quality Assurance". Emphasis was placed on inspection and testing. Quality was about conformance to specification. Non-Conformance Reports were representative of quality control. Our understanding of quality management has evolved, largely based on the Toyota Quality and Concurrent Engineering Approach of moving it off the production line for Integrated Product and Process Development (IPPD) [1]. In the late 1980s industry experienced similar difficulties in understanding and adopting quality management. The ideas behind managing quality are quite abstract. Quality is primarily about understanding and satisfying a customer's expectations. This includes implicit expectations, as well as explicit expectations. The techniques of specification, inspection and testing only make sense in that wider context. Formal risk management was developed in the late 1980s and throughout the 1990s
ABSTRACT Advanced Integrated Modular Avionics (A-IMA) will drive new focus and challenges for Model Based Engineering (MBE). First, there is the need to bridge MBE to legacy system elements that were developed without MBE along with the need to handle hybrid Open System Architecture / Integrated Modular Avionics (OSA/IMA) based architectures. Second, there is the need for MBE to be reusable and interoperable across product development cycles as technology insertions occur. Third, there is the need for integration of MBE into synthesizable descriptions that can also be effectively validated for mixed general purpose, safety, and secure computing and networking environments. Fourth is the need for effective application of MBE in hybrid waterfall and agile development environments where target infrastructure is scalable in capability and cost. Fifth is the need for MBE to support partitioned roles across companies, government, and universities where one entity does requirements, one does
ABSTRACT By adopting the latest developments from other critical (e.g. integrated modular avionics) and high-volume automotive industries with safety requirements (ADAS and autonomous driving), the rotorcraft industry could reduce system lifecycle costs and gain new integrated platform capabilities which support incremental modernization, simplify upgrades and modifications for different missions or rotorcraft platforms. A specific set of architecture design patterns and computational models, used in integrated modular architectures, enables the design of less complex integrated systems which can collect and process all system sensor data in (hard) real-time, supports seamless sensor data fusion for IVHM, and enables the integration of critical and non-critical functions. Accompanied with robust system engineering, RTCA DO-254 / DO-178C DAL A/B design assurance and extended use of ASIL-D-compliant (automotive) components, novel integrated architectures for rotorcraft can be designed to
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.
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).
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.
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.
This paper describes recent results from the Georgia Institute of Technology to develop, improve, and flight test a multi-aircraft collaborative architecture, focused on decentralized autonomous decision-making. The architecture includes a search coverage algorithm, behavior estimation, and a pursuit algorithm designed to solve a scenario-driven challenge problem. The architecture was implemented on a pair of Yamaha RMAX helicopters outfitted with modular avionics, as well as an associated set of simulation tools. Simulation and flight test results for single- and multiple-aircraft scenarios are presented. Further work suggested includes identification and development of more sophisticated methods that can replace the simpler elements in modular fashion.
Items per page:
50
1 – 50 of 90