By introducing a separation between graphics and logic, an interpreted runtime architecture and a defined communication protocol, the ARINC 661 Standard was designed to address many of the concerns that aircraft manufacturers face today when creating cockpit avionics displays. Before starting a project using this technology, it is important to understand all of the elements introduced by the standard, along with the benefits and occasional drawbacks.
Avionics HMI developers depend on both inhouse and COTS HMI tools in their day-to-day work. Unfortunately, many of these solutions support only a narrow set of embedded computing platforms or do not meet the performance requirements that a program defines. This means that engineering choices can be limited for HMI software and hardware combinations at the initial design phase and that seemingly straightforward hardware upgrades during an aircraft's lifecycle can become problematic.Beyond these hardware constraints, HMI designers often have to deal with a disjunction between groups developing the prototypes and those deploying to the target platform whereby applications are frequently completely re-coded for the final environment, resulting in little opportunity for re-use from prototyping to production. This type of sequential re-development of a display makes it very difficult to make any changes to the design late in the development cycle or even to be able to evaluate a display iteratively in its production environment.To overcome these restrictions and inefficiencies, engineers can invest in vendoragnostic COTS HMI tools, such as VAPS XT from Presagis. By grouping all function calls that are specific to an operating system or a graphic library, the porting layer acts as a bridge between the HMI design and embedded computing platforms.There are many benefits to using a tool based around a porting layer, including:• increase design flexibility • enabling HMI designers to keep refining their displays until the very end of a project cycle • facilitate avionics updates after initial program deployment • deployment on multiple embedded platforms • injection of new features through product upgrades during the development cycle Whether customized in-house or by a thirdparty service, the porting layer eliminates the constraints associated with choosing COTS embedded software and hardware based solely on existing interoperability.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.