Avionics Data Access via Loadable Configuration Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current avionics systems require rigid, compile-time defined interfaces for accessing internal data, making it costly and difficult to change or alter these interfaces due to certification and safety concerns, limiting flexibility and efficiency in data access.
Innovation Solution
A method and system that utilize a Configuration Tool to generate a Loadable Configuration File, allowing users to select and customize data access at runtime, enabling flexible access to internal data through a Data Access Component and Receiving Component, which subscribe to and output data based on user-defined selections, structure, and platform information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a compile-time defined interface is used for accessing internal data, then safety and certification requirements are met, but flexibility and ease of changing interfaces are worsened
Solution Approach 1:
The patent implements a dynamic data access mechanism where the interface is no longer fixed at compile time but can be configured at runtime through a configuration file. The Data Access Component reads the configuration file to determine which data topics to access, allowing the interface to adapt dynamically while maintaining safety through structured configuration rather than arbitrary code changes.
Solution Approach 2:
The invention changes the parameter of interface definition from static (compile-time) to dynamic (runtime configuration). By using a configuration file that specifies data topics, offsets, and sizes, the system allows parameter changes without recompilation, resolving the contradiction between safety and flexibility.
2Adaptability or versatility
If the access interface is changed to adapt to new requirements, then adaptability is improved, but time and cost for testing and recertification increase
Solution Approach 1:
The configuration file is prepared in advance with all necessary data access parameters (topics, offsets, sizes) before the system needs to access the data. This preliminary configuration eliminates the need for runtime testing and recertification when changing data access requirements, as the configuration can be updated without executing new code.
Solution Approach 2:
Instead of modifying the core access interface code, the system creates a copy of the configuration parameters in a separate configuration file. This allows changes to be made by copying new configuration values without touching the original verified code, thereby avoiding recertification requirements.
3Stability of the object's composition
If a rigid compile-time interface is used, then system stability is maintained, but ease of operation and customization are worsened
Solution Approach 1:
The configuration file serves as an intermediary between the user's customization needs and the stable, verified access interface code. Users interact with the configuration file for customization, while the core system code remains stable and unchanged. The Data Access Component acts as a mediator that reads the configuration and translates it into stable data access operations.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure provides systems 100 and methods that enable flexible access of internal data of an avionics system 102 (e.g., a Flight Management System). Aspects of the present disclosure enable enhanced, flexible and robust recording of flight test data, testing, debugging, and analyzing in-service problems. One example system includes a Configuration Tool 108 that generates a Loadable Configuration File 106 and a Configuration File based on user selections, structure of data in Data Stores 110, platform information, processor information, and Receiving Component requirements; a Data Access Component 104 that subscribes to data in the Data Stores based on the Loadable Configuration File and outputs the data; and a Receiving Component 116 receives the data, and decodes the data based at least in part on the Configuration File. Aspects of the present disclosure provide the ability to change which data gets output by the avionics system without the need to recompile and recertify the avionics system software.