An airborne software anomaly tracing method based on telemetry coding
By generating abnormal response codes and transmitting them to the ground station for parsing, the problem of lack of abnormal response monitoring in airborne systems was solved, resulting in resource savings and improved aircraft efficiency.
Patent Information
- Application Number
- CN202411913477.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-24
- Publication Date
- 2026-01-16
- Estimated Expiration
- 2044-12-24
AI Technical Summary
The lack of monitoring and cause analysis capabilities for abnormal aircraft status responses in the airborne system makes it impossible for pilots to accurately understand the aircraft status, affecting flight efficiency. Furthermore, the limited existing telemetry resources cannot effectively transmit all fault statuses.
An airborne software anomaly tracing method based on telemetry coding is adopted to generate an anomaly response code in a specified format, which is then transmitted to the ground station via telemetry data packets. The ground station parses and provides prompts to directly locate the cause of the anomaly response.
It saves telemetry and airborne software resources, improves troubleshooting efficiency, increases aircraft sortie efficiency, and reduces flight parameter download and analysis work.
Smart Images

Figure CN119888886B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The application belongs to the field of aviation technology, and particularly relates to an airborne software abnormality tracing method based on telemetry coding. BACKGROUND
[0002] In the current model design, the airborne system needs to transmit the monitored faults on the plane. The airborne system has no function of monitoring the abnormal response state of the aircraft state and analyzing the causes, which leads to the aircraft state being opaque to the pilot, affects the subsequent flight disposal, and reduces the aircraft operation efficiency.
[0003] In addition, in the current fault cause analysis method, the general implementation manner is that corresponding state variables are defined for each airborne product state / system state, and each bit of the variable represents a fault cause. All the state variables are transmitted by telemetry transmission, the ground station analyzes the variables after receiving the variables, and displays on the ground station to prompt the user, and the transmission mode occupies a large amount of telemetry transmission resources. In actual application, due to limited telemetry resources, all fault states cannot be transmitted. SUMMARY
[0004] Objectives of the application:
[0005] During the real-time execution of the task of the unmanned aerial vehicle, the aircraft may appear abnormal response interruption, considering that the airborne system appears abnormal response. At this time, the phenomenon of the abnormal response needs to be prompted, and the cause needs to be traced, key information is transmitted to the ground operator or friendly forces according to the demand, the event response type data transmission specification is established, and the system supports fast and accurate generation of effective data.
[0006] The application aims to provide an airborne software abnormality tracing method based on telemetry coding, which can directly locate the cause of the abnormal response, greatly improves the fault removal efficiency, and improves the aircraft operation efficiency. The method has the advantages of saving link transmission resources and airborne software resources in transmission.
[0007] Technical scheme of the application:
[0008] An airborne software abnormality tracing method based on telemetry coding, after the aircraft appears abnormal response, each airborne system generates an abnormal response code in a specified format for the cause leading to the abnormality, and transmits the abnormal response code to the ground station through a telemetry data packet; after the ground station receives the transmitted data packet, the ground station analyzes the cause according to the definition and prompts the user on the ground station.
[0009] Further, the abnormal response of the aircraft includes:
[0010] a) pressing the remote control switch, and the switch is not connected;
[0011] b) The aircraft does not respond to the remote control command;
[0012] c) Non-manual task termination occurs during task execution;
[0013] d) Autonomous emergency handling, including emergency power on / off, automatic connection of emergency slow speed, automatic connection of emergency parking.
[0014] Further, the abnormal response code is generated in the format of 32-bit code, wherein 8-bit professional code, 8-bit abnormal type code and 16-bit reason number.
[0015] Further, the abnormal response code is generated in the format as shown in Table 1:
[0016] Table 1
[0017]
[0018] The abnormal response code is 32-bit code, wherein:
[0019] Professional code: bit24~bit31, according to the specification of the aircraft system subsystem to describe the system;
[0020] Class number: bit16~bit23, describe the type of abnormal response, each bit represents a type;
[0021] Reason code: bit0~bit15, describe the reason for the type of abnormal response, each bit represents a reason.
[0022] Further, the onboard system judges whether the system response abnormality occurs by obtaining the ground operation and the current aircraft state parameter, and if the abnormality occurs, generates the abnormal response code, and uses the abnormal response code to identify the direct reason for the abnormal response.
[0023] Further, after the abnormal response code is generated, the abnormal response code telemetry package is formed and transmitted to the ground station.
[0024] Further, the abnormal response code telemetry package definition is as shown in Table 2
[0025] Table 2 Abnormal response code telemetry package definition requirements
[0026]
[0027]
[0028] Among them,
[0029] a) If 6 or more abnormal responses occur at the same time, which cannot be transmitted in one frame, time division transmission is required;
[0030] b) Occurred abnormal response: fill in the professional code and class number in the corresponding abnormal response code, i.e. bit16~bit31 in the abnormal response code; only fill in the abnormal response code when abnormal response occurs, and fill 0 when it does not occur;
[0031] c) Cause of abnormal response: fill in the cause number in the corresponding abnormal response code, i.e. bit0~bit16 in the abnormal response code; only fill in the abnormal response code when abnormal response occurs, and fill 0 when it does not occur.
[0032] Further, after the ground station receives the abnormal response code telemetry package, only the bytes with values other than 0 are subjected to abnormal response code analysis and judgment, and the abnormal response cause prompt is displayed on the ground station according to the abnormal response code defined in advance.
[0033] The beneficial effects of the present application are:
[0034] At present, the airborne system mainly provides fault cause prompts for the finished product faults on the aircraft, and there is no function of analyzing the causes of abnormal aircraft states. In the current fault cause analysis method, a fault variable is generally defined, and the value of the variable represents different fault causes. According to the existing method, all defined fault variables need to be telemetered and downloaded (regardless of whether the fault occurs or not), and the variable values are analyzed on the ground station, which occupies a large amount of telemetry download resources.
[0035] The present application proposes an airborne software abnormality tracing method based on telemetry coding. According to the method proposed in the present application, no separate variable design is needed for the occurred abnormality, and the cause code leading to the abnormality is directly downloaded after the abnormality occurs, thereby saving link transmission resources and airborne software resources.
[0036] At the same time, the abnormal response cause is downloaded and prompted, which can directly locate the abnormal response cause, reduce the work of flight parameter download analysis, greatly improve the fault elimination efficiency, and improve the aircraft operation efficiency. BRIEF DESCRIPTION OF DRAWINGS
[0037] Figure 1 The figure is a schematic diagram of the airborne software abnormality tracing method. DETAILED DESCRIPTION
[0038] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.
[0039] One embodiment of the present application is to propose a telemetry coding-based airborne software anomaly tracing method. After the aircraft appears an abnormal response, each airborne system needs to generate an abnormal response code in a specified format for the cause of the abnormality, and transmit it to the ground station through telemetry data packets. After the ground station receives the downlink data packet, it prompts the user on the ground station according to the defined analysis reason.
[0040] During flight, the aircraft may have an unexpected response due to special circumstances, which is considered an abnormal system response, including but not limited to the following situations:
[0041] a) Press the remote control switch, and the switch is not connected;
[0042] b) When operating the remote control command, the aircraft does not respond;
[0043] c) During task execution, non-manual task termination occurs;
[0044] d) Autonomous emergency handling (including emergency power on / off, automatic connection of emergency slow speed, automatic connection of emergency stop, etc.).
[0045] The abnormal response code is intended for ground station operators and ground maintenance personnel. The occurrence of the abnormal response may not be due to aircraft failure, but may be due to the fact that the flight phase, product state, etc. do not meet the current command usage conditions, resulting in unexpected aircraft response. Therefore, it is necessary to accurately locate each state that leads to abnormal response and generate an abnormal response code to facilitate operators and ground maintenance personnel to master the current state of the aircraft, skip the flight parameter interpretation link, and save troubleshooting time; The entire machine abnormal response code should be displayed on the ground station or ground maintenance device screen.
[0046] The abnormal response code of the aircraft is 32 bits, including 8-bit professional code, 8-bit abnormal type code, and 16-bit reason number.
[0047] The airborne software determines whether a system response anomaly has occurred by obtaining ground operation and current aircraft state parameters, and identifies the direct cause of the abnormal response. The aircraft system abnormal response code is generated by each airborne system according to its own abnormal response, forming an abnormal response code telemetry package that is telemetered down to the ground station.
[0048] After the ground station receives the abnormal response code telemetry package, it only analyzes and judges the abnormal response code for the bytes with a value other than 0. According to the defined abnormal response code, the abnormal response reason prompt is displayed on the ground station.
[0049] The abnormal response code writing requirements are shown in Table 1.
[0050] Table 1 Abnormal response code coding requirements
[0051]
[0052] The abnormal response code is 32-bit code, wherein:
[0053] Professional code: bit24~bit31, according to the aircraft system subsystem specification to describe the system;
[0054] Class number: bit16~bit23, describe the type of abnormal response, each bit represents a type,
[0055] Reason code: bit0~bit15, describe the reason for the type of abnormal response, each bit represents a reason.
[0056] The abnormal response code telemetry packet requirements are shown in Table 2.
[0057] Table 2 Abnormal response code telemetry packet definition requirements
[0058]
[0059]
[0060] Wherein:
[0061] a) If multiple (>5) abnormal responses occur at the same time, which cannot be transmitted in one frame, time-sharing download is required; b) Abnormal response: fill in the professional code and class number in the corresponding abnormal response code, i.e. bit16~bit31 in the abnormal response code. Only when the abnormal response occurs, fill in the abnormal response code, otherwise fill 0;
[0062] c) Cause of abnormal response: fill in the reason number in the corresponding abnormal response code, i.e. bit0~bit16 in the abnormal response code. Only when the abnormal response occurs, fill in the abnormal response code, otherwise fill 0.
[0063] The second embodiment of the application is:
[0064] The flow chart of the abnormal response tracing method based on telemetry coding in the method is shown in the figure. Figure 1 Taking "pilot presses the release switch, and the aircraft release is unsuccessful due to aircraft side slip" as an example.
[0065] First, define the abnormal response code. In this example, two types of abnormal responses are taken as examples: takeoff termination and task termination. Since the above two types of abnormal responses are judged by the flight control system professional, the corresponding professional code is 0x001; takeoff termination corresponds to type code 0x1, and task termination corresponds to type code 0x2; the reason number causing each abnormal response corresponds to the low 16 bits. As shown in the following table.
[0066]
[0067] According to the above, the abnormal code formed due to the flight control system failure resulting in the take-off termination is: 0x001 010001.
[0068] Then, during the whole flight (from flight preparation to flight end). The on-board software judges whether the system response abnormality occurs by acquiring the ground operation and the current aircraft state parameters, and identifies the direct cause leading to the abnormal response at the same time.
[0069] The pilot presses the "release" switch at the ground station to prepare for release. At this time,
[0070] 1) The ground station transmits the "release switch" to the on-board software through the link;
[0071] 2) The on-board software performs comprehensive calculation through the current on-board data to make the release condition judgment;
[0072] 3) The current aircraft side deviation is greater than 10m, the take-off is terminated, and the abnormal response code is generated;
[0073] 4) The abnormal response code is transmitted to the ground station through telemetry, at this time, the ground station receives the following abnormal response
[0074] data packet:
[0075]
[0076] 5) The data packet is parsed: only one abnormal response occurs, the abnormal response code is 0x001 10004, according to the definition of table 2, the prompt is generated at the ground station: the abnormal response of take-off termination occurs, and the abnormal reason is that the side deviation is greater than 10m.
[0077] The present application proposes an on-board software abnormality tracing method based on telemetry coding, according to the method proposed by the present application, without separate variable design for the abnormality, the reason code leading to the abnormality is directly transmitted after the abnormality occurs, the link transmission resource and the on-board software resource are saved.
[0078] At the same time, the abnormal response reason is transmitted and prompted, the abnormal response reason can be directly located, the work of flight parameter download analysis is reduced, the troubleshooting efficiency is greatly improved, and the aircraft operation efficiency is improved.
[0079] The above is only a specific embodiment of the present application, which is described in detail, and the part not described in detail is the conventional technology. However, the protection scope of the present application is not limited to this, any change or replacement easily thought by those skilled in the art within the technical range disclosed by the present application should be covered in the protection scope of the present application. The protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A method for on-board software anomaly root cause based on telemetry encoding, characterized in that, After the aircraft appears abnormal response, each airborne system generates abnormal response code in specified format aiming at the cause of the abnormality, and transmits it to the ground station through abnormal response code telemetry package; after the ground station receives the abnormal response code telemetry package, it analyzes the cause according to the definition and prompts the user on the ground station; The generation format of abnormal response code is 32-bit code, including 8-bit professional code, 8-bit abnormal type code and 16-bit cause number; the generation format of abnormal response code is shown in Table 1: Table 1 ; Among them: Professional code: bit24~bit31, according to the specification of aircraft system subsystem, describe the system; Class number: bit16~bit23, describe the type of abnormal response, each bit represents a type; Cause code: bit0~bit15, describe the cause of the type of abnormal response, each bit represents a cause; The definition of abnormal response code telemetry package is shown in Table 2: Table 2 Definition of abnormal response code telemetry package ; Among them, a) If 6 or more abnormal responses occur at the same time, they cannot be transmitted in one frame, and need to be transmitted in time; b) Abnormal response: fill in the professional code and class number in the corresponding abnormal response code, i.e. bit16~bit31 in abnormal response code; only fill in abnormal response code when abnormal response occurs, otherwise fill 0; c) Cause of abnormal response: fill in the cause number in the corresponding abnormal response code, i.e. bit0~bit16 in abnormal response code; only fill in abnormal response code when abnormal response occurs, otherwise fill 0; After receiving the abnormal response code telemetry package, the ground station only analyzes the abnormal response code for the bytes with value not equal to 0, and displays the abnormal response cause prompt according to the pre-defined abnormal response code on the ground station.
2. The method of claim 1, wherein, The abnormal response of the aircraft includes: a) Press the remote control switch, the switch is not connected; b) When operating the remote control command, the aircraft does not respond; c) During task execution, non-manual task termination occurs; d) Autonomous emergency disposal, including emergency energy on / off, automatic connection of emergency slow speed, automatic connection of emergency stop.
3. The method of claim 2, wherein, The airborne system judges whether the system response abnormality occurs by obtaining the ground operation and the current aircraft state parameter, and if the abnormality occurs, generates abnormal response code to identify the direct cause of the abnormal response.
4. The method of claim 3, wherein the method further comprises: After the abnormal response code is generated, abnormal response code telemetry package is formed and transmitted to the ground station.
Citation Information
Patent Citations
Fault remote-measurement and control device for electric vehicle
CN101059698A
Method and system for managing equipment defects by fault codes
CN103500378A