Avionics Data Converter for Electronic Flight Bag Universal Format
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current avionics systems face challenges in data communication due to different data formats used by various aircraft systems, requiring recompilation and redevelopment of software when interacting with systems having distinct data formatting, which is time-consuming and costly.
Innovation Solution
An Electronic Flight Bag (EFB) with a data converter module that adapts data from diverse avionics systems to a universal format using a configuration data file, allowing seamless interaction with different Flight Management Systems (FMS) without the need for recompilation, by converting and modifying data into a common format for use by the application module.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data converters are customized for each specific avionics system data format, then data communication reliability is improved, but device complexity and development costs increase
Solution Approach 1:
The patent implements a universal data converter that can handle multiple avionics data formats (ARINC 429, ARINC 664, SDI, etc.) through a single standardized interface. The converter uses configurable parameters and lookup tables to adapt to different formats without requiring separate custom software for each system, thereby reducing complexity while maintaining reliable communication across diverse avionics platforms
Solution Approach 2:
The patent introduces an intermediary standardized data interface between the avionics systems and the flight management system. This intermediary layer translates various proprietary formats into a common standardized format, allowing the flight management system to interact with different avionics systems through a uniform interface without direct customization for each system
2Adaptability or versatility
If software is recompiled and redeveloped for each avionics system format, then data compatibility is improved, but development time and costs increase
Solution Approach 1:
The patent pre-defines multiple avionics data format configurations within the data converter, including ARINC 429, ARINC 664, SDI, and other specialized formats. These formats are pre-configured with their specific protocols, data structures, and translation rules, allowing the system to immediately adapt to different avionics systems without requiring recompilation or redevelopment of software
Solution Approach 2:
The patent enables adaptation to different avionics systems by changing configurable parameters within the data converter, such as data format selectors, protocol versions, and translation tables. Instead of recompiling software, the system dynamically adjusts parameters to match the target avionics system, significantly reducing development time while maintaining full compatibility
3Adaptability or versatility
If multiple specialized data networks are used for different aircraft systems, then system specificity is improved, but system complexity increases
Solution Approach 1:
The patent merges multiple specialized data networks (ARINC 429, ARINC 664, SDI, Ethernet, etc.) into a single standardized communication interface through the data converter. Instead of maintaining separate network infrastructure for each protocol, the converter consolidates these specialized networks into one unified interface that the flight management system can access uniformly, reducing network complexity while preserving support for all specialized formats
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An Electronic Flight Bag (EFB) (20) includes memory storing a configuration data file (48) defining a set of data format definitions associated with a corresponding set of avionics systems, the set of data format definitions different from one another, an application module (52) configured to utilize a set of universal format data (54), and a data converter module (50) configured to receive data from any of the set of avionics systems, to adapt the received data to the set of universal format data (54) based on the configuration data file (48), and to provide the set of universal format data (54) to the application module (52).