Airborne software abnormity tracing method based on telemetering coding

Abstract

The invention belongs to the technical field of aviation, and particularly relates to an airborne software exception tracing method based on telemetry coding, which comprises the following steps: after an aircraft has an exception response, each airborne system generates an exception response code in a specified format aiming at a reason causing the exception, and downloads the exception response code to a ground station through a telemetry data packet; and after the ground station receives the downloaded data packet, a user is prompted at the ground station according to the definition analysis reason, the abnormal response reason can be directly positioned, the troubleshooting efficiency is greatly improved, and the airplane dispatching efficiency is improved. And the method has the advantage of saving link transmission resources and airborne software resources in transmission.

Description

Technical Field

[0001] The present invention belongs to the field of aviation technology, and in particular relates to an airborne software anomaly tracing method based on telemetry coding. Background Art

[0002] In the current model design, the onboard system needs to transmit the faults monitored on board. The onboard system does not have the function of monitoring the abnormal response status of the aircraft and analyzing the cause, which makes the aircraft status opaque to the pilot, affects the subsequent flight handling, and reduces the efficiency of aircraft dispatch.

[0003] Moreover, in the current method of analyzing the cause of the fault, the common implementation method is: define corresponding state variables for each airborne finished product state / system state, and each bit of the variable represents a fault cause. All state variables are telemetered and transmitted through telemetry downlink. After receiving the variables, the ground station analyzes them and displays them at the ground station to prompt the user. However, this transmission method will occupy a large amount of telemetry downlink resources. In actual applications, due to limited telemetry resources, all fault states may not be uploaded. Summary of the invention

[0004] Purpose of the present invention:

[0005] When the drone is performing a mission in real time, the aircraft may experience an abnormal response interruption, which may be considered as an abnormal response of the onboard system. At this time, it is necessary to prompt the abnormal response phenomenon and trace its cause, transmit key information to ground operators or friendly forces as needed, establish event-responsive data transmission specifications, and support the system to quickly and accurately generate effective data.

[0006] The present invention aims to propose an airborne software anomaly tracing method based on telemetry coding, which can directly locate the cause of abnormal response, greatly improve troubleshooting efficiency, and improve aircraft dispatch efficiency. In addition, this method has the advantage of saving link transmission resources and airborne software resources in transmission.

[0007] The technical solution of the present invention:

[0008] A method for tracing the source of airborne software anomalies based on telemetry coding. After an aircraft has an abnormal response, each airborne system generates an abnormal response code in a specified format according to the cause of the anomaly, and transmits it to a ground station through a telemetry data packet. After the ground station receives the transmitted data packet, it parses the cause according to the definition and prompts the user at the ground station.

[0009] Furthermore, the abnormal responses of the aircraft include:

[0010] a) Press the remote control switch, but the switch is not turned on;

[0011] b) The aircraft does not respond when operating the remote control command;

[0012] c) During the execution of the task, non-human task termination occurs;

[0013] d) Autonomous emergency response, including emergency energy on / off, automatic emergency slow-down, and automatic emergency parking.

[0014] Furthermore, the generation format of the exception response code is a 32-bit code, including an 8-bit professional code, an 8-bit exception type code and a 16-bit reason number.

[0015] Furthermore, the generation format of the abnormal response code is shown in Table 1:

[0016] Table 1

[0017]

[0018] The exception response code is a 32-bit code, where:

[0019] Professional code: bit24~bit31, describes the system according to the aircraft system subsystem specification;

[0020] Class number: bit16 to bit23, describing the type of abnormal response that occurred, each bit represents a type;

[0021] Cause code: bit0 to bit15, describing the cause of this type of abnormal response, each bit represents a cause.

[0022] Furthermore, the airborne system determines whether a system response abnormality occurs by obtaining ground operations and current aircraft status parameters. If an abnormality occurs, an abnormal response code is generated, and the abnormal response code is used to identify the direct cause of the abnormal response.

[0023] Furthermore, after the abnormal response code is generated, an abnormal response code telemetry package is formed and telemetered down to the ground station.

[0024] Furthermore, the abnormal response code telemetry package definition is shown in Table 2

[0025] Table 2 Abnormal response code telemetry package definition requirements

[0026]

[0027]

[0028] in,

[0029] a) If 6 or more abnormal responses occur at the same time and cannot be transmitted in one frame, they need to be transmitted in time division;

[0030] b) Exception response: Fill in the professional code and class number in the corresponding exception response code, that is, bit 16 to bit 31 in the exception response code; fill in the exception response code only if an exception response occurs, otherwise fill in 0;

[0031] c) Cause of abnormal response: Fill in the cause number in the corresponding abnormal response code, that is, bit 0 to bit 16 in the abnormal response code; fill in the abnormal response code only if an abnormal response occurs, otherwise fill in 0.

[0032] Furthermore, after receiving the abnormal response code telemetry package, the ground station only parses and determines the abnormal response code for the bytes whose values ​​are not 0, and generates an abnormal response reason prompt based on the pre-defined abnormal response code and displays it on the ground station.

[0033] Beneficial effects of the present invention:

[0034] At present, the onboard system mainly prompts the cause of the finished product failure that occurs on the aircraft, and there is no function to analyze the cause of the abnormal aircraft status. In addition, in the current analysis method of the cause of the failure, a fault variable is generally defined, and the value of the variable represents different causes of the failure. According to the existing method, all defined fault variables need to be telemetered and transmitted (regardless of whether the fault occurs), and the analysis of the variable value at the ground station will occupy a large amount of telemetry transmission resources.

[0035] The present invention proposes an airborne software anomaly tracing method based on telemetry coding. According to the method proposed by the present invention, there is no need to design separate variables for the anomalies that occur. After the anomaly occurs, the cause code that causes the anomaly is directly transmitted, saving link transmission resources and airborne software resources.

[0036] At the same time, the cause of the abnormal response is transmitted downward, which can directly locate the cause of the abnormal response, reduce the work of downloading and analyzing flight parameters, greatly improve the efficiency of troubleshooting, and improve the efficiency of aircraft dispatch. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 This is the schematic diagram of the airborne software anomaly tracing method. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0039] One embodiment of the present invention is to propose an airborne software anomaly tracing method based on telemetry coding. After an abnormal response occurs in the aircraft, each airborne system needs to generate an abnormal response code in a specified format according to the cause of the anomaly, and transmit it to a ground station via a telemetry data packet; after the ground station receives the transmitted data packet, it parses the cause according to the definition and prompts the user at the ground station.

[0040] During the flight, the aircraft may have unexpected responses due to special circumstances, which may be considered as abnormal responses of the system, including but not limited to the following:

[0041] a) Press the remote control switch, but the switch is not turned on;

[0042] b) The aircraft does not respond when operating the remote control command;

[0043] c) During the execution of the task, non-human task termination occurs;

[0044] d) Autonomous emergency response (including emergency energy on / off, automatic emergency slow-down, automatic emergency parking, etc.).

[0045] The abnormal response code is used by ground station operators and ground maintenance personnel. The occurrence of this abnormal response is not necessarily due to an aircraft failure. It may be due to the flight phase, finished product status, etc. not meeting the use conditions of the current instructions, resulting in unexpected aircraft responses. Therefore, it is necessary to accurately locate each state that causes the abnormal response and generate an abnormal response code, so that operators and ground maintenance personnel can understand the current state of the aircraft, skip the flight parameter interpretation link, and save troubleshooting time; the whole aircraft abnormal response code should support display in the ground station or ground maintenance equipment screen.

[0046] The aircraft's abnormal response code consists of 32 bits in total, including 8 bits of professional code, 8 bits of abnormal type code and 16 bits of reason number.

[0047] The onboard software determines whether a system response abnormality occurs by obtaining ground operations and current aircraft status parameters, and identifies the direct cause of the abnormal response. The aircraft system abnormal response code is generated by each onboard system based on its own abnormal response, forming an abnormal response code telemetry package that is telemetered down to the ground station.

[0048] After receiving the abnormal response code telemetry packet, the ground station only parses and judges the abnormal response code for the bytes whose values ​​are not 0. The abnormal response reason prompt is generated according to the abnormal response code defined by the implementation and displayed on the ground station.

[0049] The requirements for writing exception response codes are shown in Table 1.

[0050] Table 1 Exception response code encoding requirements

[0051]

[0052] The exception response code is a 32-bit code, where:

[0053] Professional code: bit24~bit31, describes the system according to the aircraft system subsystem specification;

[0054] Class number: bit16 to bit23, describing the type of abnormal response that occurred, each bit represents a type;

[0055] Cause code: bit0 to bit15, describing the cause of this type of abnormal response, each bit represents a cause.

[0056] The requirements for the abnormal response code telemetry package are shown in Table 2.

[0057] Table 2 Abnormal response code telemetry package definition requirements

[0058]

[0059]

[0060] in:

[0061] a) If multiple (>5) abnormal responses occur at the same time and cannot be transmitted in one frame, they need to be transmitted in time division; b) Abnormal response that occurs: fill in the professional code and class number in the corresponding abnormal response code, that is, bit16 to bit31 in the abnormal response code. Fill in the abnormal response code only when an abnormal response occurs, otherwise fill in 0;

[0062] c) Reason for abnormal response: Fill in the reason number in the corresponding abnormal response code, that is, bit 0 to bit 16 in the abnormal response code. Fill in the abnormal response code only if an abnormal response occurs, otherwise fill in 0.

[0063] The second embodiment of the present invention is:

[0064] The flow chart of the method for tracing the source of anomalies in airborne software based on telemetry coding in this method is as follows: Figure 1 Take the example of "the pilot pressed the release switch, but the aircraft failed to be released due to the side deviation of the aircraft."

[0065] First, define the abnormal response code. In this example, two types of abnormal responses are used: takeoff termination and mission termination. Since the above two types of abnormal responses are judged by the flight control system, the corresponding professional code is 0x001; takeoff termination corresponds to type code 0x1, and mission termination corresponds to type code 0x2; the cause number of each abnormal response corresponds to the lower 16 bits. As shown in the following table.

[0066]

[0067] According to the above, the exception code caused by takeoff termination due to flight control system failure is: 0x001 010001.

[0068] Then, during the entire flight process (from flight preparation to flight completion), the onboard software determines whether a system response abnormality occurs by obtaining ground operations and current aircraft status parameters, and identifies the direct cause of the abnormal response.

[0069] The pilot presses the "release" switch at the ground station to prepare for release.

[0070] 1) The ground station uploads the “release switch” to the onboard software through the link;

[0071] 2) The onboard software performs comprehensive calculations based on the current onboard data to determine the launch conditions;

[0072] 3) If the current lateral deviation of the aircraft is greater than 10m, takeoff is terminated and an 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] Response data packet:

[0075]

[0076] 5) Parse the data packet: Only one abnormal response occurred, and its abnormal response code is 0x001 10004. According to the definition in Table 2, parse it and generate a prompt at the ground station: an abnormal response of takeoff termination occurred, and the abnormal reason was that the side deviation was greater than 10m.

[0077] The present invention proposes an airborne software anomaly tracing method based on telemetry coding. According to the method proposed by the present invention, there is no need to design separate variables for the anomalies that occur. After the anomaly occurs, the cause code that causes the anomaly is directly transmitted, saving link transmission resources and airborne software resources.

[0078] At the same time, the cause of the abnormal response is transmitted downward, which can directly locate the cause of the abnormal response, reduce the work of downloading and analyzing flight parameters, greatly improve the efficiency of troubleshooting, and improve the efficiency of aircraft dispatch.

[0079] The above is only a specific embodiment of the present invention, and the present invention is described in detail. The unexplained part is a conventional technology. However, the protection scope of the present invention is not limited to this. Any changes or substitutions that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. The protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A method for tracing the source of airborne software anomalies based on telemetry coding, characterized in that: After the aircraft has an abnormal response, each airborne system generates an abnormal response code in a specified format according to the cause of the abnormality, and transmits it to the ground station via a telemetry data packet; after the ground station receives the transmitted data packet, it analyzes the cause according to the definition and prompts the user at the ground station.

2. According to claim 1, a method for tracing the source of airborne software anomalies based on telemetry coding is characterized in that: Abnormal responses from the aircraft include: a) Press the remote control switch, but the switch is not turned on; b) The aircraft does not respond when operating the remote control command; c) During the execution of the task, non-human task termination occurs; d) Autonomous emergency response, including emergency energy on / off, automatic emergency slow-down, and automatic emergency parking.

3. The method for tracing the source of anomalies of airborne software based on telemetry coding according to claim 2 is characterized in that: The generation format of the exception response code is a 32-bit code, including an 8-bit professional code, an 8-bit exception type code, and a 16-bit reason number.

4. The method for tracing the source of airborne software anomalies based on telemetry coding according to claim 3 is characterized in that: The generation format of the exception response code is shown in Table 1: Table 1 The exception response code is a 32-bit code, where: Professional code: bit24~bit31, describes the system according to the aircraft system subsystem specification; Class number: bit16 to bit23, describing the type of abnormal response that occurred, each bit represents a type; Cause code: bit0 to bit15, describing the cause of this type of abnormal response, each bit represents a cause.

5. The method for tracing the source of airborne software anomalies based on telemetry coding according to claim 4 is characterized in that: The airborne system determines whether a system response abnormality occurs by obtaining ground operations and current aircraft status parameters. If an abnormality occurs, an abnormal response code is generated and the direct cause of the abnormal response is identified using the abnormal response code.

6. The method for tracing the source of airborne software anomalies based on telemetry coding according to claim 5 is characterized in that: After the abnormal response code is generated, an abnormal response code telemetry package is formed and telemetered down to the ground station.

7. The method for tracing the source of airborne software anomalies based on telemetry coding according to claim 6 is characterized in that: The definition of the abnormal response code telemetry package is shown in Table 2 Table 2 Abnormal response code telemetry package definition requirements in, a) If 6 or more abnormal responses occur at the same time and cannot be transmitted in one frame, they need to be transmitted in time division; b) Exception response: Fill in the professional code and class number in the corresponding exception response code, that is, bit 16 to bit 31 in the exception response code; fill in the exception response code only if an exception response occurs, otherwise fill in 0; c) Reason for abnormal response: Fill in the reason number in the corresponding abnormal response code, that is, bit 0 to bit 16 in the abnormal response code; fill in the abnormal response code only if an abnormal response occurs, otherwise fill in 0.

8. The method for tracing the source of anomalies of airborne software based on telemetry coding according to claim 7 is characterized in that: After receiving the telemetry packet with the abnormal response code, the ground station only parses and determines the abnormal response code for the bytes whose values ​​are not 0, and generates an abnormal response reason prompt based on the abnormal response code defined in advance and displays it on the ground station.

Images