Serial Digital Communication Protocol for Aircraft Engine Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing serial digital communication protocols in aircraft applications are inflexible and require protocol changes when engine data varies, making it challenging to accommodate different types of engine data for transmission.
Innovation Solution
A method of formatting data sets for transmission using a header with a cyclic redundancy checksum, allowing for error detection and flexible communication of variable-length data sets, using a digital communication system with a transmitter and receiver that supports RS-422 UART protocol, enabling synchronization and integrity verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fixed communication protocol is used for engine data transmission, then the protocol structure is simple and stable, but it cannot accommodate variable types and lengths of engine data
Solution Approach 1:
The communication protocol is segmented into distinct functional fields: synchronization field (1 byte), data type field (1 byte), data length field (2 bytes), data field (variable), and checksum field (2 bytes). This segmentation allows each field to handle specific aspects of data transmission independently, enabling flexible accommodation of different data types and lengths while maintaining overall protocol structure.
Solution Approach 2:
The protocol incorporates dynamic fields that can adapt to different data requirements. The data length field (2 bytes) allows variable-length data transmission, and the data type field enables different interpretation of the data content. This dynamic structure resolves the contradiction by allowing the protocol to adapt to various engine data formats without requiring complete protocol redesign.
2Reliability
If error detection mechanisms are added to ensure data integrity, then data reliability improves, but transmission overhead increases
Solution Approach 1:
The protocol implements a 2-byte checksum mechanism that provides sufficient error detection capability for engine monitoring applications. This partial error detection approach balances reliability requirements with transmission efficiency, providing adequate protection without excessive overhead. The checksum covers the critical protocol structure fields and data type information, ensuring integrity where it matters most.
3Measurement precision
If synchronization mechanisms are implemented for variable-length data, then data alignment accuracy improves, but protocol complexity increases
Solution Approach 1:
The protocol places a synchronization field (1 byte with value 0x5A) at the beginning of each data frame, before the variable-length data content. This preliminary synchronization marker allows the receiving end to accurately identify the start of each data frame and properly align subsequent fields, regardless of variable data lengths. This simple preliminary action resolves synchronization issues without requiring complex mechanisms.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Provided is a method and an apparatus for formatting a data set (404) for transmission on a communication channel. The formatted data frame (400) comprises a header (402) and the data set (404) to be transmitted. The header (402) has a plurality of header fields (406 ... 420) comprising a redundancy field (408) having a checksum calculated on data in part of the header fields (406 ... 420) and on the data set (404).