Aircraft Asynchronous Computer Data Synchronization Using Sequencing Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Asynchronous computers in aircraft, such as the engine control and monitoring systems, face challenges in synchronizing data due to lack of time and frequency information, leading to incorrect association of parameters and inefficient communication data rates, especially with RS422 interfaces.
Innovation Solution
A method involving the creation of a sequencing table to determine valid windows for parameter updates and a send table to distribute the load, allowing the first computer to instruct the second computer on parameter refresh frequencies without requiring additional information or hardware modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If time-stamp information is added to parameters to enable proper time context organization, then data synchronization is improved, but communication data rate capacity is exceeded with RS422 interfaces
Solution Approach 1:
The patent extracts time-stamping functionality from the communication protocol level and implements it at the application level using sequential counters. This removes the need to transmit actual time-stamp data over the communication interface, extracting only the essential synchronization information (sequential numbers) while keeping the communication load within RS422 capacity limits.
Solution Approach 2:
Instead of transmitting actual time-stamp values, the system uses sequential counter copies that represent time context. The receiving computer generates corresponding sequential counters locally, creating a simplified representation that maintains synchronization without requiring high-bandwidth time-stamp transmission.
2Speed
If all parameters are sent immediately when prepared, then data freshness is improved, but communication interface capacity is exceeded
Solution Approach 1:
The patent implements periodic transmission based on parameter update frequencies rather than immediate transmission. Each parameter is transmitted at its required update rate (e.g., every 10ms, 100ms) as defined in the sequencing table, creating a structured periodic communication pattern that fits within RS422 capacity while maintaining data freshness requirements.
Solution Approach 2:
The receiving computer preliminarily organizes the communication schedule by creating a sequencing table that defines when each parameter should be transmitted. This preliminary planning allows the system to prepare transmission slots in advance, ensuring that parameters are sent at the correct intervals without requiring high-speed immediate transmission.
3Reliability
If computers are designed with knowledge of each other's operations, then data organization is improved, but system adaptability and life cycle flexibility are reduced
Solution Approach 1:
The patent introduces sequential counters as an intermediary mechanism that enables data organization without requiring direct knowledge of each computer's internal operations. The counters serve as a neutral mediator that both computers can use to synchronize data context independently, maintaining flexibility while achieving proper data organization.
Solution Approach 2:
Each computer independently generates and manages its own sequential counters without requiring the other computer to know its internal timing or operation details. The receiving computer self-services by generating local counters that correspond to transmitted parameters, while the transmitting computer independently increments its counters. This self-service approach maintains adaptability while achieving synchronization.
Data Source
AI summary
A method of synchronizing data for algorithms of asynchronous computers in an aircraft, the method comprising the steps consisting in:a) generating a sequencing table for each algorithm and, in said table, identifying the number of valid windows for each of which all of the parameters for input to the algorithm are updated at least once;b) distributing the load corresponding to updating the parameters for each algorithm in a send table; andc) instructing the first computer to use the send table.


