A fault analysis method and device based on cross-file flight test data

Abstract

The application provides a fault analysis method and device based on cross-file flight test data, comprising: receiving a fault analysis request sent by a client, and calling flight test data to be analyzed from a flight test database according to the fault analysis request; performing cross-file data merging processing on multiple flight test data files of different specialties and different frequencies of the same flight, to obtain multiple sampling records corresponding to each flight test parameter after merging; obtaining a corresponding target fault analysis strategy according to a fault category indicated in the fault analysis request; sending the target fault analysis strategy to the client, and obtaining multiple target criteria fed back by the client; performing fault analysis on the multiple sampling records corresponding to each flight test parameter after merging by using the multiple target criteria, determining a fault analysis result, and feeding back the fault analysis result to the client. The application guarantees the coherence between data and improves the fault analysis efficiency by performing cross-file merging processing on the flight test data.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a fault analysis method and apparatus based on cross-file flight test data. Background Technology

[0002] The basis for diagnosing test machine malfunctions comes from flight test data, which contains a large amount of process information for test subjects and the operational status information of various systems of the test machine.

[0003] Currently, data preprocessing and fault diagnosis tools can only process single files, requiring manual import of data files and manual setting of criteria, resulting in low data processing efficiency. Specifically, flight test engineers currently mainly import flight test data manually through local software at the flight test site, which cannot ensure the continuity and traceability between data. Furthermore, due to the characteristics of flight test data, such as numerous parameters, many files, and large data volume, the performance of the user's local computer affects the efficiency of data analysis. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide at least one method and apparatus for fault analysis based on cross-file flight test data. This application ensures the continuity between data and improves the efficiency of fault analysis by performing cross-file merging processing on flight test data.

[0005] This application mainly includes the following aspects:

[0006] In a first aspect, embodiments of this application provide a fault analysis method based on cross-file flight test data, applied to a server. The method includes: receiving a fault analysis request sent by a client, the fault analysis request indicating a fault category and a flight test mission number; retrieving flight test data to be analyzed from a flight test database according to the flight test mission number, the flight test data to be analyzed including multiple flight test data files, each flight test data file including at least one flight test parameter and multiple sampling records corresponding to each flight test parameter; performing cross-file data merging processing on the multiple flight test data files to obtain a merged target merged file, the target merged file including multiple sampling records corresponding to each flight test parameter after merging; obtaining a corresponding target fault analysis strategy according to the fault category indicated in the fault analysis request, the fault analysis strategy including multiple fault criteria under the same fault category, each fault criterion indicating a fault judgment rule; sending the target fault analysis strategy to the client and obtaining multiple target criteria fed back by the client; using the multiple target criteria to perform fault analysis on the multiple sampling records corresponding to each flight test parameter after merging, determining the fault analysis result, and feeding back the fault analysis result to the client.

[0007] In one possible implementation, the target merge file is determined as follows: Based on the sampling duration and sampling rate corresponding to each flight test data file, a merged baseline file is determined from multiple flight test data files. The merged baseline file indicates the highest sampling rate and maximum sampling duration among the multiple flight test data files. For each flight test data file, the sampling rate corresponding to that flight test data file is compared with the sampling rate corresponding to the merged baseline file. Based on the comparison results of the sampling rates corresponding to each flight test data file, the multiple flight test data files are merged with the merged baseline file. For the multiple sampling records corresponding to each flight test parameter in the merged baseline file, a preset interpolation strategy corresponding to the flight test parameter type is used to fill in the sampling records with missing sampling values. Based on the multiple sampling records corresponding to each flight test parameter after the filling process, a data change graph corresponding to each flight test parameter is generated. The data change graph indicates the change of each flight test parameter and its corresponding multiple feature values. The merged baseline file after the filling process is determined as the target merge file.

[0008] In one possible implementation, the merged benchmark file is determined by: calculating the sampling rate and sampling duration corresponding to each flight test data file; determining the flight test data file corresponding to the highest sampling rate and the maximum sampling duration; combining the maximum sampling duration, performing patching processing on multiple sampling records corresponding to each flight test parameter in the flight test data file corresponding to the highest sampling rate; and determining the flight test data file corresponding to the highest sampling rate after patching processing as the merged benchmark file.

[0009] In one possible implementation, the sampling rate comparison results include those with the same sampling rate and those with different sampling rates. The step of sequentially merging each flight test data file with the merging baseline file based on the sampling rate comparison results corresponding to each flight test data file includes:

[0010] (A) Extract one flight test data file from multiple flight test data files, and decrease the number of flight test data files to be merged by 1; (B) Based on the sampling rate comparison results corresponding to the extracted flight test data file, complete the merging between the flight test data file and the merging reference file; (C) Refresh the merging reference file; (D) Determine whether the number of flight test data files to be merged is zero; (E) If the number of flight test data files to be merged is zero, complete the merging between multiple flight test data files and the merging reference file; (F) If the number of flight test data files to be merged is not zero, return to step (A).

[0011] In one possible implementation, step (B) includes: for each flight test parameter in the flight test data file: determining whether the flight test parameter exists in the merged benchmark file; if the flight test parameter exists in the merged benchmark file, then abandoning the merging of multiple sampling records corresponding to the flight test parameter in the flight test data file into the merged benchmark file; if the flight test parameter does not exist in the merged benchmark file, then obtaining the sampling rate comparison result; if the sampling rate comparison result is the same, according to the number of sampling records corresponding to the flight test parameter in the merged benchmark file, performing point interpolation processing on the multiple sampling records corresponding to the flight test parameter, and merging the multiple sampling records corresponding to the flight test data file after point interpolation processing into the merged benchmark file; if the sampling rate comparison result is different, according to the merged benchmark time and the number of sampling records corresponding to the flight test parameter in the merged benchmark file, performing point interpolation processing on the multiple sampling records corresponding to the flight test parameter; merging the multiple sampling records corresponding to the flight test data file after point interpolation processing into the merged benchmark file.

[0012] In one possible implementation, the flight test parameter types include continuous quantities, discrete quantities, and digital quantities. The preset interpolation strategies include linear interpolation strategies and nonlinear interpolation strategies corresponding to continuous / discrete quantities, and a previous bit supplementation strategy corresponding to digital quantities. The step of filling in sampling records with missing sampling values ​​using the preset interpolation strategy corresponding to the flight test parameter type includes: if the flight test parameter type is a continuous or discrete quantity, then the linear interpolation strategy / nonlinear interpolation strategy is used to perform linear interpolation calculation on the sampling value, and the sampling value in the sampling record is re-determined to complete the filling process of the sampling record; if the flight test parameter type is a digital quantity, then the previous bit supplementation strategy is used to supplement the sampling value, and the sampling value in the sampling record is re-determined to complete the filling process of the sampling record.

[0013] In one possible implementation, each fault criterion includes a fault object, a criterion condition for the fault object, and a criterion time. The criterion condition is a judgment rule formed by flight test parameters and logical operations. The step of using multiple target criteria to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter and determining the fault analysis result includes: for each fault criterion, using the criterion condition and criterion time corresponding to the fault criterion to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter and determining the fault judgment result for the fault object; and forming the fault analysis result from the fault judgment results corresponding to each fault criterion.

[0014] In a preferred embodiment, each fault criterion includes a fault object, a criterion condition for the fault object, and a criterion time. The criterion condition is a judgment rule formed by flight test parameters and logical operations. The step of using multiple target criteria to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter and determining the fault analysis result includes: for each fault criterion, using the criterion condition and criterion time corresponding to the fault criterion to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter and determining the fault judgment result for the fault object; and forming the fault analysis result from the fault judgment results corresponding to each fault criterion.

[0015] In a preferred embodiment, the fault determination result includes the presence of a faulty object and the absence of a faulty object. The fault determination result for each fault criterion is determined as follows: It is determined whether the multiple sampling records corresponding to the merged flight test parameters meet the criteria for the criterion to be valid. If the multiple sampling records corresponding to the merged flight test parameters do not meet the criteria for the criterion to be valid, then the fault criterion is determined to be invalid, and the fault determination result is determined to be the absence of a faulty object. If the multiple sampling records corresponding to the merged flight test parameters meet the criteria for the criterion to be valid, then the duration for which the multiple sampling records corresponding to the merged flight test parameters meet the criteria for the criterion to be valid is monitored. If the duration reaches the criteria validity period, then the fault criterion is determined to be valid, and the fault determination result is determined to be the presence of a faulty object. If the duration does not reach the criteria validity period, then the fault criterion is determined to be invalid, and the fault determination result is determined to be the absence of a faulty object.

[0016] Secondly, this application provides a fault analysis method based on cross-file flight test data, applied to a client. The method includes: in response to a fault analysis creation request, displaying a flight test fault analysis interface, the flight test fault analysis interface including a fault analysis request configuration area and a criterion configuration area, the fault analysis request configuration area including fault analysis object configuration items and a request generation control, and the criterion configuration area including criterion configuration items; in response to a configuration operation performed on the fault analysis object, determining the input flight test mission number; in response to a selection operation performed on the request generation control, forming a corresponding fault analysis request from the flight test mission number and sending the fault analysis request to the server; in response to a selection operation performed on the criterion configuration items, displaying multiple criteria obtained from the server corresponding to the aircraft model; and in response to a selection operation performed on multiple target criteria, feeding back the target criteria to the server.

[0017] Thirdly, this application also provides a fault analysis device based on cross-file flight test data, applied on a server side. The device includes: a receiving module for receiving a fault analysis request sent by a client, the fault analysis request indicating a fault category and a flight test mission number; a retrieval module for retrieving flight test data to be analyzed from a flight test database according to the flight test mission number, the flight test data to be analyzed including multiple flight test data files, each flight test data file including at least one flight test parameter and multiple sampling records corresponding to each flight test parameter; and a merging module for performing cross-file data merging processing on the multiple flight test data files to obtain a merged target file. The target merged file includes multiple sampling records corresponding to each flight test parameter after merging; the fault analysis strategy acquisition module is used to acquire the corresponding target fault analysis strategy according to the fault category indicated in the fault analysis request. The fault analysis strategy includes multiple fault criteria under the same fault category, and each fault criterion indicates a fault judgment rule; the criterion acquisition module is used to send the target fault analysis strategy to the client and acquire multiple target criteria fed back by the client; the analysis module is used to perform fault analysis on the multiple sampling records corresponding to each flight test parameter after merging using the multiple target criteria, determine the fault analysis result, and feed back the fault analysis result to the client.

[0018] This application provides a fault analysis method and apparatus based on cross-file flight test data, comprising: receiving a fault analysis request sent by a client; retrieving flight test data to be analyzed from a flight test database according to the fault analysis request; performing cross-file data merging processing on multiple flight test data files to obtain multiple sampling records corresponding to each merged flight test parameter; obtaining a corresponding fault analysis strategy according to the flight test mission number; sending the fault analysis strategy corresponding to the flight test mission number to the client and obtaining multiple target criteria fed back by the client; performing fault analysis on the multiple sampling records corresponding to each merged flight test parameter using the multiple target criteria, determining the fault analysis result, and feeding back the fault analysis result to the client. This application ensures the continuity between data and improves the efficiency of fault analysis by performing cross-file merging processing on flight test data.

[0019] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A flowchart of a fault analysis method based on cross-file flight test data provided in an embodiment of this application is shown;

[0022] Figure 2 This illustration shows a schematic diagram of an interaction structure provided in an embodiment of this application;

[0023] Figure 3 This document illustrates a flowchart of merging multiple flight test data files according to an embodiment of this application.

[0024] Figure 4 This application illustrates another fault screening method based on cross-file flight test data provided by an embodiment of the present application;

[0025] Figure 5 This illustration shows a functional block diagram of a fault analysis device based on cross-file flight test data provided in an embodiment of this application;

[0026] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0028] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0029] Currently, data preprocessing and fault diagnosis tools can only process single files. Flight data itself is very large, requiring manual import of data files and manual merging and calculation. Due to the characteristics of flight test data, such as many parameters, many files, and large data volume, the performance of the user's local computer affects the efficiency of data analysis.

[0030] Currently, flight test engineers mainly import flight test data manually through local software at the flight test site, and each specialty manually sets judgment criteria according to the judgment rules, which cannot ensure the consistency and traceability between data.

[0031] Based on this, this application provides a fault analysis method based on cross-file flight test data. The method performs cross-file merging processing on the flight test data to ensure data consistency and improve fault analysis efficiency. The specific details are as follows:

[0032] Please see Figure 1 , Figure 1 A flowchart illustrating a fault analysis method based on cross-file flight test data provided in an embodiment of this application is shown. Please refer to... Figure 2 , Figure 2 A schematic diagram of an interaction structure provided in an embodiment of this application is shown. For example... Figure 1 As shown and Figure 2 As shown, this method is applied to the server side and includes the following steps:

[0033] S100: Receive a fault analysis request sent by the client.

[0034] In this application, the client and server adopt an edge-cloud collaborative integrated approach to jointly support fault analysis at the test flight site. The server adopts an open-source cloud-native architecture to meet the needs of daily test flight data management and analysis in a network environment. The client can be deployed on a high-performance portable laptop to provide offline functional support for the test aircraft's field test flights, allowing test flight engineers and maintenance personnel to complete fault analysis work on-site.

[0035] In a preferred embodiment, the fault analysis request includes authorization verification information. Before retrieving the flight test data to be analyzed from the flight test database according to the fault analysis request, the method includes:

[0036] The permission verification information is verified. If the verification result is that the permission verification is successful, the flight test data to be analyzed is allowed to be retrieved from the flight test database for fault analysis. If the verification result is that the fault analysis request is not responded to, and a relevant prompt indicating that the permission verification failed is returned to the client.

[0037] In a preferred embodiment, the server can manage user permission data. That is, the server records different permissions corresponding to different users. Therefore, when the server receives a fault analysis request, it will verify the permission information based on the recorded user permission data according to the permission verification information indicated by the fault analysis request, and then send the verification result back to the corresponding client.

[0038] S110. Retrieve the flight test data to be analyzed from the flight test database according to the flight test mission number.

[0039] The fault analysis request also includes the flight test mission number. After the permission verification is passed, the flight test data to be analyzed can be retrieved from the flight test database using the flight test mission number. The flight test data to be analyzed includes multiple flight test data files. The flight test data files are the basis for the test aircraft to make fault judgments. Each flight test data file includes at least one flight test parameter and multiple sampling records corresponding to each flight test parameter. The multiple sampling records corresponding to the flight test parameter are collected by the test aircraft through the bus set on it and multiple different types of sensor devices. In each flight test data file, the multiple sampling records corresponding to each flight test parameter will form a two-dimensional matrix. In the two-dimensional matrix, the horizontal axis can be the flight test parameter, and the numerical axis can be the sampling time.

[0040] In a preferred embodiment, this application can uniformly manage flight test data through a server, that is, it can uniformly store and manage flight test data generated at the test site of the experimental aircraft, thereby providing data support for fault analysis. Specifically, after obtaining the flight test data generated by the experimental aircraft at the test site, it is uploaded to the server. The server will establish a series of association relationships between the uploaded flight test data, such as flight information, flight test data, data classification, flight test parameters, and flight test data processing results, based on the relevant information of the uploaded flight test data, thereby ensuring the continuity and traceability of the data.

[0041] In one specific embodiment, each test flight mission of the test aircraft has a corresponding test flight mission number. The test flight mission number indicates the aircraft model, test flight time, and test flight serial number, etc. After the test aircraft completes each test flight mission, it adds the test flight mission number to the multiple test flight data files generated during each test flight and encapsulates them into corresponding test flight data. It then uploads them to the FTP server. The FTP server will synchronously store the multiple test flight data files to the test flight database. Alternatively, the test flight database can actively and periodically read newly added test flight data from the FTP server. In other words, the server's management of test flight data covers the management function of test flight data import.

[0042] S120: Perform cross-file data merging processing on multiple flight test data files to obtain the target merged file.

[0043] The target merge file includes multiple sampling records corresponding to each flight test parameter after merging.

[0044] Because fault analysis and interpretation tools can only process single files, but each flight test generates a large number of flight test data files, and each flight test file contains a large number of flight test parameters, the amount of data is particularly large. Analyzing the data on the local client reduces the efficiency of data processing and interpretation. Furthermore, in multiple flight test data files, due to the influence of factors such as the electromagnetic environment of the test aircraft and the accuracy of its own acquisition, some anomalies and sampling rate differences will occur when recording the acquired data by each sensor.

[0045] Based on this, under normal network connectivity, this application enables cross-file data merging of multiple flight test data files on the server to form a single target data file, thereby reducing the computational burden on the local client and improving the efficiency of data analysis and fault analysis.

[0046] Specifically, the target merge file is determined in the following way:

[0047] Based on the sampling duration and sampling rate corresponding to each flight test data file, a merged baseline file is determined from multiple flight test data files. The merged baseline file indicates the highest sampling rate and the maximum sampling duration among the multiple flight test data files.

[0048] Specifically, the basis principle for merging multiple flight test data files in this application is the maximum sampling time and the highest sampling rate, that is, the maximum sampling time and the highest sampling rate contained in the multiple flight test data files are used for merging.

[0049] In a preferred embodiment, the merging baseline file is determined in the following manner:

[0050] Calculate the sampling rate and sampling duration for each test flight data file, determine the test flight data file corresponding to the highest sampling rate and the maximum sampling duration, and combine the maximum sampling duration to perform supplementary processing on multiple sampling records corresponding to each test flight parameter in the test flight data file corresponding to the highest sampling rate. The test flight data file corresponding to the highest sampling rate after supplementary processing is determined as the merged reference file.

[0051] Specifically, if there are multiple test flight data files corresponding to the highest sampling rate, the one with the most test flight parameters is selected for subsequent supplementary data processing based on the maximum sampling duration. For example, if a test flight data file corresponding to a certain highest sampling rate has a sampling duration of 3 minutes and a highest sampling rate of 1 / 64 Hz, then further data processing is required if the maximum sampling duration is 5 minutes.

[0052] For each test flight data file, obtain the sampling rate corresponding to that test flight data file and the sampling rate corresponding to the merged benchmark file. Based on the comparison results of the sampling rates corresponding to each test flight data file, complete the merging of multiple test flight data files and the merged benchmark file.

[0053] In a preferred embodiment, please refer to Figure 3 , Figure 3 This document illustrates a flowchart of merging multiple flight test data files according to an embodiment of this application. Figure 3 As shown, based on the sampling rate comparison results corresponding to each flight test data file, the steps for merging each flight test data file with the merged baseline file include:

[0054] (A) Extract one test flight data file from multiple test flight data files, and reduce the number of test flight data files to be merged by 1.

[0055] For example, there are 100 test flight data files. The initial number of test flight data files to be merged is 100. These 100 test flight data files need to be merged into the merge base file one by one. Therefore, the merge base file needs to be saved and refreshed each time the merge is performed. In addition, the number of test flight data files to be merged will decrease by 1 each time the merge is performed.

[0056] (B) Based on the sampling rate comparison results corresponding to the extracted flight test data file, complete the merging between the flight test data file and the merged benchmark file.

[0057] In one specific embodiment, the sampling rate comparison results include the same sampling rate and different sampling rates.

[0058] Step (B) includes: for each flight test parameter in the flight test data file:

[0059] Determine if the flight test parameter exists in the merged benchmark file. If the flight test parameter exists in the merged benchmark file, then discard the merging of multiple sampling records corresponding to the flight test parameter in the flight test data file into the merged benchmark file.

[0060] Specifically, if the parameter names corresponding to the test flight parameters are the same, they are considered to belong to the same test flight parameter; if the parameter names are different, they are considered to be different test flight parameters. Taking flight altitude as an example, since the merged reference file corresponds to the highest sampling rate and the maximum sampling duration, if the merged reference file contains sampling records corresponding to flight altitude, then the sampling records corresponding to flight altitude in the test flight data file can be abandoned from being merged into the merged reference file.

[0061] If the flight test parameter is not present in the merged baseline file, the sampling rate comparison result is obtained.

[0062] If the sampling rate comparison results are the same, according to the number of sampling records corresponding to the flight test parameter in the merged benchmark file, the multiple sampling records corresponding to the flight test parameter are interpolated and then the multiple sampling records corresponding to the flight test data file after the interpolation are processed are merged into the merged benchmark file.

[0063] Specifically, if the merged baseline file includes two flight test parameters, flight altitude and flight speed, and the flight test data file records multiple sampling records corresponding to engine temperature, and the sampling rate is the same as that of the merged baseline file, then since the merged baseline file does not contain engine temperature, it is necessary to merge the multiple sampling records corresponding to engine temperature into the merged baseline file. Although the sampling rate is the same, the sampling duration or the number of sampling records may be different. Therefore, it is necessary to supplement the sampling records of engine temperature according to the number of sampling records corresponding to the merged baseline file.

[0064] If the sampling rate comparison results are different, then according to the merging benchmark time and number of sampling records corresponding to the flight test parameter in the merging benchmark file, the multiple sampling records corresponding to the flight test parameter are subjected to interpolation processing, and the multiple sampling records corresponding to the flight test data file after interpolation processing are merged into the merging benchmark file.

[0065] In one specific embodiment, it is first determined whether the fault analysis request carries a merging reference time. The merging time includes the merging start time. For example, if the merging start time is 14:00, it means that the merging of multiple flight test documents starts from 14:00. If the fault analysis request does not carry a merging reference time, the sampling time corresponding to the first sampling record in the merging reference file is used as the merging reference time.

[0066] Specifically, if the merged baseline file includes two flight test parameters, flight altitude and flight speed, and the flight test data file records multiple sampling records corresponding to engine temperature, and the sampling rate is different from that of the merged baseline file, then since the merged baseline file does not contain engine temperature, it is necessary to merge the multiple sampling records corresponding to engine temperature into the merged baseline file. However, due to the different sampling rates, it is necessary to first use the merged baseline time as the benchmark, then interpolate and fill the multiple sampling records corresponding to engine temperature to the highest sampling rate, and then perform further interpolation and filling based on the number of sampling records corresponding to the merged baseline file.

[0067] (C) Refresh the merged baseline file.

[0068] (D) Determine if the number of test flight data files to be merged is zero. If the number of test flight data files to be merged is not zero, return to step (A).

[0069] (E) If the number of test flight data files to be merged is zero, then the merging of multiple test flight data files with the merging reference file is completed.

[0070] For each flight test parameter in the merged baseline file, multiple sampling records are filled in using a preset interpolation strategy corresponding to the flight test parameter type.

[0071] In a preferred embodiment, the flight test parameter types include continuous quantities, discrete quantities, and digital quantities. The preset interpolation strategies include linear interpolation strategies and nonlinear interpolation strategies corresponding to continuous quantities, and a previous bit supplementation strategy corresponding to digital quantities. The step of filling in sampling records with missing sampling values ​​using the preset interpolation strategy corresponding to the flight test parameter type includes:

[0072] If the test flight parameter type is a continuous or discrete quantity, a linear interpolation strategy / nonlinear interpolation strategy is used to perform linear interpolation calculation on the sampled value, and the sampled value in the sampled record is re-determined to complete the filling process of the sampled record.

[0073] Specifically, nonlinear interpolation strategies can include Newton interpolation, etc.

[0074] In one specific embodiment, the linear interpolation strategy is an interpolation method for one-dimensional data. In this application, the filling can be performed based on the sampled values ​​indicated by two adjacent sampled records that are adjacent to the sampled record that needs to be filled. For example, if the flight test parameters are analog quantities, the average of the sampled values ​​indicated by two adjacent sampled records can be used as the filling value.

[0075] If the test flight parameter type is digital, the previous bit supplementation strategy is used to supplement the sampled value, and the sampled value in the sampled record is re-determined to complete the filling process of the sampled record.

[0076] Specifically, if the flight test parameters are digital, they can be filled using the sampled value indicated by the previous sampled record corresponding to the sampled record to be filled.

[0077] Based on the multiple sampling records corresponding to each flight test parameter after filling, a data change graph corresponding to each flight test parameter is generated. The data change graph indicates the change of each flight test parameter and its corresponding multiple characteristic values.

[0078] In one specific embodiment, the multiple feature values ​​corresponding to each flight test parameter include, but are not limited to, at least one of the following: maximum value, minimum value, average value, variance value, Y difference value, number of data, and key domain maximum value, key domain minimum value, key domain average value, key domain variance value, key domain Y difference value, and key domain number of data.

[0079] The merged baseline file after the filling process is selected as the target merge file.

[0080] return Figure 1 S130. Obtain the corresponding target fault analysis strategy according to the fault category indicated in the fault analysis request.

[0081] The flight test database also stores pre-created fault analysis strategies corresponding to different fault categories. The fault analysis strategies include multiple fault criteria under the same fault category, and each fault criterion indicates the fault judgment rule.

[0082] S140. Send the target fault analysis strategy to the client and obtain multiple target criteria fed back by the client.

[0083] S150 uses multiple target criteria to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter, determines the fault analysis results, and feeds the fault analysis results back to the client.

[0084] Each fault criterion includes the fault object, the conditions for the criterion to be established for the fault object, the time when the criterion is established, the handling recommendation, and the flight release recommendation. The conditions for the criterion to be established are the judgment rules formed by test flight parameters and logical operations. The logical operations include, but are not limited to, greater than, equal to, less than, AND, OR, and S, as well as the four arithmetic operations of addition, subtraction, multiplication, and division. The criterion name indicates the fault object, such as abnormal engine temperature or abnormal flight altitude. The handling recommendation is the corresponding handling method when the fault determination result indicates that there is a fault object. The flight release recommendation includes allowing flight, not allowing flight, and conditionally allowing flight.

[0085] The steps involved in performing fault analysis on multiple sampling records corresponding to each merged flight test parameter using multiple target criteria, and determining the fault analysis results, include:

[0086] For each fault criterion, the fault analysis of the target data file is performed using the corresponding criterion establishment conditions and criterion establishment time, and the fault judgment result for the fault object is determined. The fault analysis result is formed by the fault judgment result corresponding to each fault criterion.

[0087] In a preferred embodiment, the fault determination result includes the presence of a faulty object and the absence of a faulty object, wherein the fault determination result corresponding to each fault criterion is determined by the following method:

[0088] The system determines whether the multiple sampling records corresponding to the merged flight test parameters meet the criteria for the validity of the fault. If the multiple sampling records corresponding to the merged flight test parameters do not meet the criteria for the validity of the fault, the fault criterion is determined to be invalid, and the fault determination result is determined to be that there is no fault object. If the multiple sampling records corresponding to the merged flight test parameters meet the criteria for the validity of the fault, the system monitors the duration for which the multiple sampling records corresponding to the merged flight test parameters meet the criteria for the validity of the fault. If the duration reaches the criteria validity time, the fault criterion is determined to be valid, and the fault determination result is determined to be that there is a fault object. If the duration does not reach the criteria validity time, the fault criterion is determined to be invalid, and the fault determination result is determined to be that there is no fault object.

[0089] In one specific embodiment, if the criterion condition is that the engine temperature is greater than 35 degrees and the criterion condition is established for 30 seconds, then once it is monitored that the sampled record value corresponding to the engine temperature is above 35 degrees for a continuous period of 30 seconds, it indicates that the criterion is established and the aircraft has an abnormal engine temperature.

[0090] Please see Figure 4 , Figure 4 This application illustrates another fault screening method based on cross-file flight test data, as provided in an embodiment of this application. For example... Figure 4 As shown, the method is applied to the client and includes:

[0091] S200: In response to the fault analysis creation request, the flight test fault analysis interface is displayed.

[0092] The client provides a user login interface, where users can log in to the flight test fault analysis system mounted on the server by entering their corresponding user identity information. The flight test fault analysis system provides a flight test fault analysis interface, which includes online fault analysis creation identifiers and offline fault analysis creation identifiers.

[0093] S201. In response to the selection operation performed for creating an identifier for online fault analysis, the online fault analysis configuration interface is displayed.

[0094] The online fault analysis configuration interface includes a fault analysis request configuration area and a criterion configuration area. The fault analysis request configuration area includes fault analysis object configuration items, merging time configuration items, and request generation controls. The criterion configuration area includes criterion configuration items.

[0095] S202. In response to the configuration operation performed on the fault analysis object, determine the input flight test mission number.

[0096] S203. In response to the selection operation performed on the request generation control, a corresponding fault analysis request is generated based on the flight test mission number, and the fault analysis request is sent to the server.

[0097] S204. In response to the selection operation performed on the criterion configuration item, display multiple criteria corresponding to the aircraft model obtained from the server.

[0098] S205. In response to the selection operation performed on multiple target criteria, the target criteria are fed back to the server.

[0099] In practical implementation, the criterion configuration area also includes a criterion creation identifier. In response to the selection operation performed on the criterion creation identifier, a criterion creation interface is generated. The criterion creation interface includes criterion name configuration items, disposal suggestion configuration items, flight release suggestion configuration items, criterion establishment condition configuration items, criterion establishment time configuration items, and criterion activation status configuration items. In response to the configuration operations performed on the criterion name configuration items, disposal suggestion configuration items, flight release suggestion configuration items, criterion establishment condition configuration items, criterion establishment time configuration items, and criterion activation status configuration items, the criterion name, disposal suggestion, flight release suggestion, criterion establishment condition, criterion establishment time, and criterion activation status are determined, respectively. In response to the selection operation performed on the criterion generation control, the criterion is generated, and the creation of the criterion is completed. If the criterion activation status is enabled, the created criterion is sent to the server as the target criterion for fault analysis. The server will also save the newly created criterion to the corresponding fault analysis strategy in the flight test database to complete the saving and updating of the criterion.

[0100] In a preferred embodiment of this application, after the client obtains the fault analysis results, it generates and displays a corresponding interpretation report. The online fault analysis configuration interface also includes a flight test parameter analysis identifier. In response to the selection operation performed on the flight test parameter analysis identifier, the flight test parameter analysis interface is displayed. The flight test parameter analysis interface includes multiple flight test parameter identifiers. In response to the selection operation performed on the target flight test parameter identifier, the data change graph corresponding to the flight test parameter is displayed.

[0101] Based on the same application concept, this application also provides a fault analysis device based on cross-file flight test data, which corresponds to the fault analysis method based on cross-file flight test data provided in the above embodiments. Since the principle of the device in this application is similar to the fault analysis method based on cross-file flight test data in the above embodiments, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0102] Please see Figure 5 , Figure 5 This diagram illustrates a functional block diagram of a fault analysis device based on cross-file flight test data provided in an embodiment of this application. Figure 5 As shown, the device includes:

[0103] The receiving module 300 is used to receive fault analysis requests sent by the client. The fault analysis requests indicate the fault category and the flight test mission number.

[0104] The retrieval module 310 is used to retrieve the flight test data to be analyzed from the flight test database according to the fault analysis request. The flight test data to be analyzed includes multiple flight test data files, each flight test data file includes at least one flight test parameter and multiple sampling records corresponding to each flight test parameter.

[0105] The merging module 320 is used to perform cross-file data merging processing on multiple flight test data files to obtain a merged target file. The merged target file includes multiple sampling records corresponding to each flight test parameter after merging.

[0106] The fault analysis strategy acquisition module 330 is used to acquire the corresponding target fault analysis strategy according to the fault category indicated in the fault analysis request. The fault analysis strategy includes multiple fault criteria under the same fault category, and each fault criterion indicates the fault judgment rule.

[0107] The criterion acquisition module 340 is used to send the target fault analysis strategy to the client and acquire multiple target criteria fed back by the client.

[0108] The analysis module 350 is used to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter using multiple target criteria, determine the fault analysis results, and feed the fault analysis results back to the client.

[0109] Based on the same application concept, please refer to Figure 6 , Figure 6 A schematic diagram of an electronic device provided in an embodiment of this application is shown. The electronic device 400 includes a processor 410, a memory 420, and a bus 430. The memory 420 stores machine-readable instructions executable by the processor 410. When the electronic device 400 is running, the processor 410 and the memory 420 communicate through the bus 430. When the machine-readable instructions are executed by the processor 410, they perform the steps of the fault analysis method based on cross-file flight test data as described in any of the above embodiments.

[0110] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the fault analysis method based on cross-file flight test data provided in the above embodiments.

[0111] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0112] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0113] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0114] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0115] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A fault analysis method based on cross-file flight test data, applied to the server side, characterized in that, The method includes: Receive a fault analysis request sent by the client, the fault analysis request indicating the fault type and flight test mission number; According to the flight test mission number, retrieve the flight test data to be analyzed from the flight test database. The flight test data to be analyzed includes multiple flight test data files. Each flight test data file includes at least one flight test parameter and multiple sampling records corresponding to each flight test parameter. Multiple flight test data files are merged across files to obtain a target merged file, which includes multiple sampling records corresponding to each flight test parameter after merging. Based on the fault category indicated in the fault analysis request, the corresponding target fault analysis strategy is obtained. The fault analysis strategy includes multiple fault criteria under the same fault category, and each fault criterion indicates a fault judgment rule. The target fault analysis strategy is sent to the client, and multiple target criteria are obtained from the client's feedback. The multiple target criteria are used to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter, determine the fault analysis results, and feed the fault analysis results back to the client. The target merged file is determined in the following way: Based on the sampling duration and sampling rate corresponding to each flight test data file, a merged baseline file is determined from multiple flight test data files. The merged baseline file indicates the highest sampling rate and the maximum sampling duration among the multiple flight test data files. For each flight test data file, obtain the sampling rate corresponding to that flight test data file and the sampling rate corresponding to the merged reference file; Based on the sampling rate comparison results corresponding to each flight test data file, the merging of multiple flight test data files with the merging baseline file is completed. For each flight test parameter in the merged benchmark file, multiple sampling records are filled with missing sampling values ​​using a preset interpolation strategy corresponding to the flight test parameter type. Based on the multiple sampling records corresponding to each flight test parameter after filling, a data change graph corresponding to each flight test parameter is generated. The data change graph indicates the change of each flight test parameter and its corresponding multiple feature values. The merged baseline file after the filling process is selected as the target merge file.

2. The method according to claim 1, characterized in that, The merge baseline file is determined in the following manner: Calculate the sampling rate and sampling duration for each flight test data file; Determine the flight test data file corresponding to the highest sampling rate and the maximum sampling duration; Based on the maximum sampling duration, multiple sampling records corresponding to each flight test parameter in the flight test data file corresponding to the highest sampling rate are supplemented. The flight test data file corresponding to the highest sampling rate after the data point supplementation process is determined as the merged baseline file.

3. The method according to claim 1, characterized in that, Based on the sampling rate comparison results corresponding to each flight test data file, the steps for merging each flight test data file with the merged baseline file include: (A) Extract one test flight data file from multiple test flight data files, and decrease the number of test flight data files to be merged by 1; (B) Based on the sampling rate comparison results corresponding to the extracted flight test data file, complete the merging between the flight test data file and the merged benchmark file; (C) Refresh the merged baseline file; (D) Determine whether the number of test flight data files to be merged is zero; (E) If the number of test flight data files to be merged is zero, then the merging of multiple test flight data files with the merging reference file is completed; (F) If the number of test flight data files to be merged is not zero, return to step (A).

4. The method according to claim 3, characterized in that, The sampling rate comparison results include those with the same sampling rate and those with different sampling rates. Step (B) includes: For each flight test parameter in this flight test data file: Determine whether the flight test parameter exists in the merged benchmark file; If the test flight parameter exists in the merged benchmark file, then the multiple sampling records corresponding to the test flight parameter in the test flight data file will not be merged into the merged benchmark file. If the flight test parameter is not present in the merged benchmark file, then the sampling rate comparison result is obtained; If the sampling rate comparison results are the same, according to the number of sampling records corresponding to the flight test parameter in the merged benchmark file, the multiple sampling records corresponding to the flight test parameter are interpolated by adding points, and the multiple sampling records corresponding to the flight test data file after the point interpolation are processed are merged into the merged benchmark file. If the sampling rate comparison results are different, then according to the merging benchmark time and number of sampling records corresponding to the flight test parameter in the merging benchmark file, the multiple sampling records corresponding to the flight test parameter are subjected to interpolation processing, and the multiple sampling records corresponding to the flight test data file after interpolation processing are merged into the merging benchmark file.

5. The method according to claim 1, characterized in that, Flight test parameter types include continuous, discrete, and digital quantities. Preset interpolation strategies include linear and nonlinear interpolation strategies corresponding to continuous / discrete quantities, and a previous bit supplementation strategy corresponding to digital quantities. The step of filling in sampling records with missing sample values ​​using a preset interpolation strategy corresponding to the flight test parameter type includes: If the test flight parameter type is a continuous quantity or a discrete quantity, then the linear interpolation strategy / nonlinear interpolation strategy is used to perform linear interpolation calculation on the sampled value, and the sampled value in the sampled record is re-determined to complete the filling process of the sampled record; If the test flight parameter type is a digital quantity, the sampling value is supplemented using the previous bit supplementation strategy, and the sampling value in the sampling record is re-determined to complete the filling process of the sampling record.

6. The method according to claim 1, characterized in that, Each fault criterion includes the fault object, the criteria for the fault object, and the time when the criteria are met. The criteria for the fault object are judgment rules formed by flight test parameters and logical operations. The steps for performing fault analysis on multiple sampling records corresponding to each merged flight test parameter using the multiple target criteria, and determining the fault analysis results, include: For each fault criterion, the fault analysis is performed on multiple sampling records corresponding to each merged flight test parameter using the corresponding criterion establishment conditions and criterion establishment time, and the fault judgment result for the fault object is determined. The fault analysis results are formed from the fault determination results corresponding to each fault criterion.

7. The method according to claim 6, characterized in that, The fault determination result includes whether a faulty object exists or not. The fault determination result corresponding to each fault criterion is determined in the following way: Determine whether the multiple sampling records corresponding to the merged flight test parameters meet the criteria for validity. If the multiple sampling records corresponding to the merged flight test parameters do not meet the criteria for the condition to be met, then the fault criterion is determined to be invalid, and the fault determination result is determined to be that there is no fault object. If the multiple sampling records corresponding to each of the merged flight test parameters meet the criteria, then monitor the duration for which the multiple sampling records corresponding to each of the merged flight test parameters meet the criteria. If the duration reaches the time when the criterion is met, the fault criterion is determined to be met, and the fault determination result is determined to be a faulty object. If the duration does not reach the time required for the criterion to be established, the fault criterion is determined to be invalid, and the fault determination result is determined to be that there is no faulty object.

8. A fault analysis method based on cross-file flight test data, applied to the client side, characterized in that, The method includes: In response to a fault analysis creation request, a flight test fault analysis interface is displayed. The flight test fault analysis interface includes a fault analysis request configuration area and a criterion configuration area. The fault analysis request configuration area includes fault analysis object configuration items and a request generation control. The criterion configuration area includes criterion configuration items. In response to the configuration operation performed on the fault analysis object, determine the input flight test mission number; In response to the selection operation performed on the request generation control, a corresponding fault analysis request is generated based on the flight test mission number and sent to the server; In response to a selection operation performed on a criterion configuration item, multiple criteria corresponding to the aircraft model are displayed, retrieved from the server. In response to a selection operation performed on multiple target criteria, the target criteria are fed back to the server; The server is used for: According to the flight test mission number, retrieve the flight test data to be analyzed from the flight test database. The flight test data to be analyzed includes multiple flight test data files. Each flight test data file includes at least one flight test parameter and multiple sampling records corresponding to each flight test parameter. Multiple flight test data files are merged across files to obtain a target merged file, which includes multiple sampling records corresponding to each flight test parameter after merging. The target merged file is determined in the following way: Based on the sampling duration and sampling rate corresponding to each flight test data file, a merged baseline file is determined from multiple flight test data files. The merged baseline file indicates the highest sampling rate and the maximum sampling duration among the multiple flight test data files. For each flight test data file, obtain the sampling rate corresponding to that flight test data file and the sampling rate corresponding to the merged reference file; Based on the sampling rate comparison results corresponding to each flight test data file, the merging of multiple flight test data files with the merging baseline file is completed. For each flight test parameter in the merged benchmark file, multiple sampling records are filled with missing sampling values ​​using a preset interpolation strategy corresponding to the flight test parameter type. Based on the multiple sampling records corresponding to each flight test parameter after filling, a data change graph corresponding to each flight test parameter is generated. The data change graph indicates the change of each flight test parameter and its corresponding multiple feature values. The merged baseline file after the filling process is selected as the target merge file.

9. A fault analysis device based on cross-file flight test data, applied to a server, characterized in that, The device includes: The receiving module is used to receive fault analysis requests sent by the client, the fault analysis requests indicating the fault category and flight test mission number; The retrieval module is used to retrieve the flight test data to be analyzed from the flight test database according to the flight test mission number. The flight test data to be analyzed includes multiple flight test data files, and each flight test data file includes at least one flight test parameter and multiple sampling records corresponding to each flight test parameter. The merging module is used to perform cross-file data merging processing on multiple flight test data files to obtain a merged target file. The merged target file includes multiple sampling records corresponding to each flight test parameter after merging. The fault analysis strategy acquisition module is used to acquire the corresponding target fault analysis strategy according to the fault category indicated in the fault analysis request. The fault analysis strategy includes multiple fault criteria under the same fault category, and each fault criterion indicates a fault judgment rule. The criterion acquisition module is used to send the target fault analysis strategy to the client and acquire multiple target criteria fed back by the client. The analysis module is used to perform fault analysis on multiple sampling records corresponding to each merged flight test parameter using the multiple target criteria, determine the fault analysis results, and feed the fault analysis results back to the client. The merging module is used for: Based on the sampling duration and sampling rate corresponding to each flight test data file, a merged baseline file is determined from multiple flight test data files. The merged baseline file indicates the highest sampling rate and the maximum sampling duration among the multiple flight test data files. For each flight test data file, obtain the sampling rate corresponding to that flight test data file and the sampling rate corresponding to the merged reference file; Based on the sampling rate comparison results corresponding to each flight test data file, the merging of multiple flight test data files with the merging baseline file is completed. For each flight test parameter in the merged benchmark file, multiple sampling records are filled with missing sampling values ​​using a preset interpolation strategy corresponding to the flight test parameter type. Based on the multiple sampling records corresponding to each flight test parameter after filling, a data change graph corresponding to each flight test parameter is generated. The data change graph indicates the change of each flight test parameter and its corresponding multiple feature values. The merged baseline file after the filling process is selected as the target merge file.

Images