Avionics Software Trace Initiation via Aeronautical Datalink
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current avionic devices require manual initiation of software traces on the ground after data collection, which can delay software debugging and maintenance, as they cannot initiate software traces remotely while airborne.
Innovation Solution
A method to remotely initiate software tracing on avionics devices using messages sent over an aeronautical datalink, allowing on-demand tracing during flight, with trace data stored on a memory device for later analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If software traces are initiated manually on the ground after data collection, then software debugging can be performed, but time is lost due to the inability to initiate traces remotely while airborne
Solution Approach 1:
The avionic device is equipped with self-service capabilities through built-in debug utilities and trace functionality that can be activated remotely. The device can autonomously collect software trace data and store it in memory devices when commanded, eliminating the need for manual ground-based initiation and enabling self-diagnostic operations during flight.
Solution Approach 2:
A ground station serves as an intermediary between the operator and the airborne avionic device. The ground station sends commands via aeronautical datalink to remotely initiate software traces on the avionic device while airborne, and receives the collected trace data for analysis, thereby enabling remote operation without requiring manual presence on the ground.
2Adaptability or versatility
If remote tracing is implemented using aeronautical datalink messages, then software traces can be initiated while airborne, but the system complexity increases due to protocol interpretation and command processing
Solution Approach 1:
The avionic device's message processing system is designed to handle multiple functions through a universal interface. The same communication infrastructure and protocol interpretation mechanisms used for normal operational commands are also utilized for initiating software traces, eliminating the need for separate dedicated hardware or complex specialized processing paths.
Solution Approach 2:
The software trace initiation functionality is merged with the existing debug utilities and message processing systems of the avionic device. The trace commands are integrated into the standard aeronautical datalink message format, and the trace data collection is combined with the device's existing data storage capabilities in memory devices, reducing overall system complexity.
Data Source
AI summary
In one embodiment, a method for remotely initiating a software trace on an avionics device operating on an aircraft is provided. The method includes at the avionics device, receiving one or more messages sent from a ground station over an aeronautical datalink to the aircraft, wherein the one or more messages conform to a protocol of the aeronautical datalink. The one or more messages are interpreted to identify any commands for the avionic device therein. If the one or more messages include one or more commands for tracing software on the avionic device, the software on the avionic device is traced in response to the one or more commands. Trace data obtained from tracing the software can be sent to a memory device for storage.


