Flight parameter diagnosis rule dynamic compiling method

Abstract

The invention belongs to the field of aircraft fault diagnosis and maintenance guarantee, and particularly relates to a flight parameter diagnosis rule dynamic compiling method. According to the method, codes required by the criterion, the blank-leaving criterion formula and the associated parameters are designed in advance according to the criterion function, the criterion formula and the associated parameters are filled after the criterion formula is analyzed, the to-be-compiled criterion file is generated, and finally the to-be-compiled file is compiled into the executable program capable of being linked to the main program through the compiling tool chain. And thus, the criterion is dynamically compiled into an executable program. The time for converting the criterion into the executable program is greatly shortened, the software development process is guaranteed to a great extent, and the guarantee efficiency is greatly improved.

Description

Technical Field

[0001] The invention belongs to the field of aircraft fault diagnosis and maintenance, and in particular relates to a method for dynamically compiling flight parameter diagnosis rules. Background Art

[0002] With the continuous development of aviation, the safety and reliability of aircraft have attracted more and more attention. Once an aircraft fails, it will affect the performance of the aircraft at the least, and even cause the aircraft to be destroyed and people to die. The data generated by each flight of the aircraft largely reflects the performance and safety of each component of the aircraft. How to troubleshoot the failure of the aircraft-related components from these data is the core work of ground staff and support personnel. Aircraft and engine manufacturers have very mature methods to use these data to troubleshoot faults, but the specific working environment of the aircraft is different, especially military aircraft work in various extreme environments for a long time. The judgment criteria and interpretation software provided by aircraft and engine manufacturers can only interpret the existing compiled diagnostic rules, referred to as judgment criteria. In the long-term support process, ground staff and support personnel have also generated many judgment criteria independent of aircraft and engine manufacturers. These judgment criteria are the crystallization of the wisdom of support personnel of all generations. However, in the actual use process, these judgment criteria cannot be converted into efficient software due to the lack of support from aircraft and engine manufacturers. Ultimately, when the data of each flight reaches the support department, the support personnel need to check the faults one by one according to the judgment criteria combined with the flight parameter data, which greatly reduces the support efficiency.

[0003] At present, there are several methods for interpreting flight parameters:

[0004] 1) Method based on interpretation software provided by the manufacturer.

[0005] This method mainly relies on the interpretation software provided by the aircraft and engine manufacturers. The interpretation software is used to interpret the flight parameter data of each flight and to troubleshoot the compiled faults provided by the aircraft and engine manufacturers.

[0006] 2) A method based on ground crew members observing flight parameter data with the naked eye.

[0007] This method is based on various custom criteria summarized by previous ground crews, combined with the flight data of each flight, and visually observes the data to troubleshoot possible faults. This is often extremely dependent on the observation and understanding of the criteria by flight support personnel, which takes a long time and is extremely inefficient.

[0008] The first method only supports the criteria that have been developed by aircraft and engine manufacturers. For the empirical criteria summarized by ground support personnel based on support experience, only the second method can be used. However, from design to use, each criterion needs to go through theoretical calculation, experimental verification, summary release, development testing and field application. Currently, the development of each criterion requires manual code development in combination with the manual, which has a long development cycle and low efficiency, and inevitably reduces the scalability of the development method.

[0009] Based on the above discussion, the present invention aims to design a dynamic compilation method for flight parameter criteria, striving to greatly improve the efficiency of criterion development while meeting the needs of support personnel to the greatest extent, thereby improving support efficiency. Summary of the invention

[0010] Aiming at the problems that the current flight parameter criterion development technology is inefficient and the development method is poorly scalable, resulting in low interpretation and guarantee efficiency, the present invention designs a method for dynamically compiling aircraft flight parameter criterion, which automatically compiles the criteria of ground crew into an executable program that can be linked to the main program, and supports custom input to ensure that if subsequent ground crew have new criteria, they can input them by themselves and automatically compile them into executable programs.

[0011] In order to realize the above functions and related functions, the present invention provides a method for dynamically compiling flight parameter criteria.

[0012] The technical solution of the present invention is as follows:

[0013] A method for dynamically compiling flight parameter diagnosis rules, the steps are as follows:

[0014] Step 1: Flight parameter ID management, that is, bind the flight parameter to a flight parameter ID consisting of four ASCII characters; specifically, first, classify the flight parameter data according to the system to which it belongs to obtain no less than 20 types of system parameters, and then divide the system parameters into switch quantity (D) and analog quantity (A). Then, number the classified parameters in turn (00-zz), and number the systems to which they belong in turn (AZ, az). Finally, combine the system to which it belongs, the data type and the parameter number to obtain a parameter ID that corresponds to the parameter one by one.

[0015] Step 2: Formula management of flight parameter criteria, i.e., converting the flight parameter criteria into a formula that performs arithmetic and logical operations on at least one parameter ID converted in step 1 (the parameter ID uniquely corresponds to the parameter and can completely refer to the parameter) and adds the duration;

[0016] Step 2-1: Write the conditional expression of all parameters in the criterion according to the text description. Each condition consists of at least one parameter, and undergoes arithmetic and logical operations and adds a duration. There must be at least one arithmetic operation and a logical operation, but not necessarily a duration. The resulting primary condition n (n=1, 2, 3...) is required. It should be noted that each criterion consists of at least one initial condition, so there may be multiple initial conditions. The n here is only used to distinguish the primary conditions and has no actual meaning.

[0017] Step 2-2: Based on the criterion text description, write out the combination condition m (m = I, II, III…) obtained by logical operation of the initial condition in step 2-1 and adding the duration (not necessarily required).

[0018] In step 2-3, according to the text description of the criterion, the initial conditions in step 2-1 that have not been combined in step 2-2 and the combined conditions generated by step 2-2 (in the process of converting some criteria, the same initial conditions may be used not only in step 2-3 but also in step 2-2 to form combined conditions, which requires flexible handling in actual use) are subjected to logical operations and the duration is added to obtain the original formula of the criterion.

[0019] Step 2-4 replaces the parameters in the original formula with the parameter ID converted in step 1, converts all durations into seconds, adds "," before the time to distinguish it from the conditional expression, and adds specific separators for each condition or combination of conditions that needs to add a duration (such as: "[]", it should be noted that the specific separators here refer to paired separators other than logical operations and arithmetic operations. The example of the present invention uses "[]", if other separators are used, formula 1.1 in step 3-2 needs to be modified synchronously) to obtain the criterion formula.

[0020] It should be noted that the form of the judgment formula is "[conditional expression, duration]", where the duration must be greater than or equal to 0. If it is equal to 0, it means that the fault is judged as the moment the conditional expression is established (in actual use, since the data packet cannot be accurately determined to the moment, it can be accurately determined to be a certain frame of data. When the conditional expression is established, a fault is immediately judged).

[0021] Step 3: Parse the criterion formula and convert it into the required code, and generate the file to be compiled;

[0022] Step 3-1: Pre-design the criterion code file according to the functional requirements, and leave the associated parameters and formulas blank. Change the suffix of the designed code file to ".bin" and compile it into the main program;

[0023] Step 3-2 uses the regular expression parsing criterion formula of formula 1.1 to extract the content inside each delimiter. After the extraction is completed, the content inside the delimiter should be in the form of "conditional expression, duration";

[0024] \[(.*)\](0.1)

[0025] Step 3-3 uses the regular expression of formula 1.2 to parse the contents inside the delimiter extracted in step 3-2 in sequence, and obtains the conditional expression (before) and duration (after) before and after ",";

[0026] (.*(?=,)),(\d*\.?\d*)(0.2) Among them: (.*(?=,)) is used to match anything before the comma. The ".*" inside means matching any character (as many as possible, greedy mode); (?=,) means positive lookahead, ensuring that the matched content is followed by a comma, but not including the comma itself. The "," following (.*(?=,)) means matching the comma directly. (\\d*\\.?\\d*) is used to match a number, supporting integers or decimals. The first \d* from left to right inside means matching any number of digits (including 0); \.? means matching a decimal point (optional); the second \d* that follows means matching any number of digits again (including the decimal part).

[0027] Step 3-4 uses the regular expression of formula 1.3 to parse the parameter ID used in the conditional expression;

[0028] \b[a-zA-Z]{2}[0-9A-Za-Z]{2}\b(0.3) Among them: \b is used to match word boundaries to ensure that the matched content is a complete word. The word boundary refers to the boundary between a word and a space, punctuation, or other non-word characters; [a-zA-Z]{2} is used to match the first two consecutive English letters from left to right (can be uppercase or lowercase); [0-9A-Za-Z]{2} is used to match the last two consecutive letters or numbers (can be uppercase or lowercase English letters or numbers).

[0029] Step 3-5 uses the regular expression of formula 1.4 to parse the numeric parameters used in the logical comparison (>, <, ==, <=, >=, !=, etc.) contained in the conditional expression extracted in step 3-4;

[0030] [<=>](-?\d+\.?\d*)(0.4) where: [<=>] is used to match one of the characters '<', '=' or '>'; (-?\d+\.?\d*) is used to match a floating point number (with or without a decimal part), -? means matching an optional minus sign, \d+ means matching one or more digits (integer part), \.? means matching an optional decimal point (.), and \d* means matching a decimal part, which can have 0 or more digits (such as '.0', '.12' or no decimal part).

[0031] Step 3-6 extracts the remaining part of the criterion formula, that is, the remaining part of the criterion formula except the parameter ID, the digital parameter used in the logical comparison operation and the duration (generally the symbols of logical operations and arithmetic operations, which can be specifically referred to the explanation of terms and terms in the specific implementation mode). <3> and <4> ).

[0032] Step 3-7 loads the pre-designed criterion code, removes duplicates from the parameter ID extracted in step 3-4 and fills it in the location of the associated parameter, composes a code block with the parsed parameter ID, logical operation, arithmetic operation and duration, fills it in the part where the formula is located and generates a file to be compiled.

[0033] Step 4: Compile the file to be compiled into a linkable executable program.

[0034] Step 4-1 compiles the resource files required to implement other functions in the file to be compiled, and generates a linkable target resource file;

[0035] Step 4-2 compiles the criteria file to be compiled, and links the target resource file generated in step 4-1 to generate a criteria target file that can be linked to the main program.

[0036] As described above, the present invention is a method for dynamically compiling flight parameter criteria into a linkable executable program, having the following

[0037] Beneficial effects:

[0038] The present invention pre-designs the code required for the criterion according to the criterion function, leaves blank the criterion formula and associated parameters, fills the criterion formula and associated parameters after the criterion formula is parsed, generates a criterion file to be compiled, and finally compiles the file to be compiled into an executable program that can be linked to the main program through a compilation tool chain, thereby realizing dynamic compilation of the criterion into an executable program. This greatly shortens the time for converting the criterion into an executable program, greatly speeds up the security software development process, and greatly improves the security efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic diagram of parameter ID design of the present invention;

[0040] Figure 2 It is a schematic diagram of the criterion formula expression method of the present invention;

[0041] Figure 3 It is a criterion-formula conversion step diagram of the present invention;

[0042] Figure 4 It is a diagram of the analytical steps of the criterion formula of the present invention;

[0043] Figure 5 It is the dynamic compilation flow chart of the present invention. DETAILED DESCRIPTION

[0044] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand the advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented and applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0045] It should be noted that in the following description, reference is made to the accompanying drawings, which describe several implementation examples and issuance processes of the present invention and should be understood.

[0046] The present invention provides a method for dynamically compiling a flight parameter criterion, by pre-designing the code required for the criterion, leaving blanks for the criterion formula and associated parameters, filling the criterion formula and associated parameters after the criterion formula is parsed, and generating a criterion file to be compiled, and finally compiling the file to be compiled into an executable program that can be linked to a main program through a compilation tool chain, thereby realizing dynamic compilation of the criterion into an executable program. The time for converting the criterion into an executable program is greatly shortened, the security software development process is greatly accelerated, and the security efficiency is greatly improved.

[0047] Before further describing the present invention in detail, the nouns and terms involved in the embodiments of the present invention are explained. The nouns and terms involved in the embodiments of the present invention are applicable to the following interpretations:

[0048] <1> Flight parameters: refers to the parameters used to monitor various operating indicators and safety status of the aircraft during flight.

[0049] <2> Criteria: refers to the digital basis for judging whether there is a problem with the aircraft by making a unified judgment on one or more flight parameters, referring to expert experience and design indicators. It should be noted that the criteria and criterion formulas used in the subsequent description have no specific meaning and are only used as examples to illustrate the implementation method of the present invention.

[0050] <3> Arithmetic operations: C++ supports addition ("+"), subtraction ("-"), multiplication ("*"), division (" / "), root extraction, exponential, logarithm, and bitwise operations (bitwise AND, bitwise OR, bitwise XOR, and bitwise XOR).

[0051] <4> Logical operations: C++ supports AND (“&&”), OR (“||”) and NOT (“!”).

[0052] <5> Compilation: The process of converting source code into an executable program.

[0053] The following is a detailed description of the embodiments of the present invention with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention. The present invention can be embodied in many different forms and is not limited to the implementation examples described here.

[0054] Figure 1 What is shown is a method for defining a flight parameter ID in the implementation of the present invention. The method includes: the parameter ID is composed of 4 ASCII characters, the first character indicates the system to which the parameter belongs, the second character indicates the type of the parameter, "A" indicates analog quantity, "D" indicates switch quantity, and the last two characters are numbers (numbered in sequence from 00 to 99 to 0A to ZZ to 0a to zz), for example, parameter AA01 indicates analog quantity No. 01 of system A. During the use of the program, the ID is not directly called, but the ID is converted into a 32-bit number formed by ASCII codes of 4 ASCII characters and sequentially spliced, which is convenient for storage and comparison.

[0055] Figure 2 What is shown is a formulaic expression method of a criterion designed by us. The general form of the criterion is "[conditional expression, duration]". The criterion usually involves at least one parameter. After arithmetic and logical operations are performed on these parameters, at least one initial condition is obtained. The logical value obtained by the initial condition after logical operation satisfies the condition of being equal to 1 or equal to 0 and lasts for a period of time, thereby obtaining the judgment conclusion of the criterion in the corresponding time period ("normal", "fault" and the duration of the fault start and end time). The conversion method is as follows Figure 3 As shown, the steps include:

[0056] Step S21: List the various conditions in the criterion separately, where the conditions may involve arithmetic and logical operations of a single parameter and last for a period of time, such as: "PLA-5.3>PLA min " means PLA (throttle stick angle) minus 5.3 is greater than PLA min (the minimum throttle lever angle design value), as the initial condition 1; "n 2 >=65&&n 2 <=85” means n 2The high pressure rotor speed is between 65 and 85, which is used as the initial condition 2; "D 1-1 = = 1 for 2 seconds" means D 1-1 (Landing gear retraction signal) exists and lasts for 2 seconds, as initial condition 3.

[0057] Step S22: If necessary, perform logical operations on the initial conditions (some of which may involve a period of time) to obtain the combined conditions. If not necessary, go to step S3. For example, if initial conditions 2 and 3 are both met and last for 3 seconds, the combined condition I shown in formula 1.5 can be obtained:

[0058] "n 2 >=65&&n 2 <=85” and “D 1-1 ==1 lasts for 2 seconds" lasts for 3 seconds (0.5)

[0059] Step S23: Perform logical operations on the remaining initial conditions and combined conditions and accumulate the duration to obtain the judgment formula. For example, if the combined condition I and the initial condition 1 are both met for 1 second, it can be concluded that the throttle lever angle is too small in this time period. The obtained formula is shown in Formula 1.6, where the redundant duration is deleted.

[0060] “““n 2 >=65&&n 2 <=85” and “D 1-1 ==1 lasts for 2 seconds, 3 seconds and PLA-5.3>PLA min 1 second (0.6)

[0061] Step S24: Change the parameters used in the obtained formula to ID, remove the quotation marks used for segmentation, replace the "and" used between conditions with "&&", and replace the "or" with "||". For conditions or combined conditions with duration, use "[]" to segment, and convert the duration into the form of "[conditional expression, duration]", and obtain the final criterion formula expression. Assumption: The parameter ID of the throttle lever angle PLA is MA01, and the throttle lever angle design minimum value PLA min The parameter ID is sA01, the high pressure rotor speed n 2 The parameter ID is MA02, landing gear retraction signal D 1-1 The parameter ID is ND01, then the formula expression after conversion of formula 1.6 is shown in formula 1.7:

[0062] [[MA02>=65&&MA02<=85&&[ND01==1,2],3]&&MA01-5.3>sA01,1](0.7)By repeating the above process, all criteria can be converted into a formulaic expression. It should be noted that the formula obtained in the above conversion process can repeat steps 23 and 24 multiple times, as long as the outermost layer of the obtained formula satisfies "[condition, duration]", where "condition" can also include conditions in the form of "[condition, duration]". For example, [MA02>=65&&MA02<=85&&[ND01==1,2],3] in formula 1.7 includes a condition of [ND01==1,2], so the formula finally obtained by the present invention can be very complex.

[0063] After the conversion of the criterion formula expression is completed, we provide a method for parsing the criterion expressed in the formula and a method for generating a file to be compiled. The parsing steps are as follows: Figure 4 As shown, the method includes:

[0064] Step S31: Design the code to be compiled in advance according to the specific functions required for executing the criterion, and leave blank or use special characters (such as "@") to mark the places where the criterion formula and criterion-related parameters are needed. After the design is completed, change the suffix of the file (which may include other function code files) to a binary .bin file and compile it into the main program.

[0065] Step S32: Use formula 1.1 to match the contents enclosed by square brackets “[]” to extract the formula and the conditions or combination conditions in the form of formulas nested inside the formulas.

[0066] Step S33: Recycle the content extracted in step S32 and use formula 1.2 to extract the parameters before and after the comma from the character string, that is, the conditional expression and duration, to obtain the duration and conditional expression of the outermost formula.

[0067] Step S34: Use formula 1.3 to parse the formula expression, match a string that starts with two letters and is followed by two letters or numbers (the length is fixed to 4 ASCII characters), and require that the string is complete content within the word boundary, and obtain the parameter ID used in the expression.

[0068] Step S35: Use formula 1.4 to match a segment of numbers before and after a logical comparison operator (such as '<', '=' or '>'), which can be an integer or a floating point number (negative numbers are supported), to resolve the part involving numbers in the comparison operation.

[0069] Step S36: Copy the remaining parts, mainly the logical operators and arithmetic operators, to complete the parsing of the formula.

[0070] Taking the formula of formula 1.7 as an example, after the analysis of formula 1.1, the formula and the various sub-formulas in the formula form inside the formula will be obtained, [MA02>=65&&MA02<=85&&[ND01==1,2],3]&&MA01-5.3>sA01,1, MA02>=65&&MA02<=85&&[ND01==1,2],3 and ND01==1,2. Then the three sub-formulas are analyzed by calling formula 1.2 in turn. The first formula is [MA02>=65&&MA02<=85&&[ND01==1,2],3]&&MA01-5.3>sA01 and duration 1 second, the second formula is MA02>=65&&MA02<=85&&[ND01==1,2] and 3 seconds, and the third formula is ND01==1 and 2 seconds. Then use formula 1.3 to parse the conditional expression to get the designed parameter ID. For formula 1.7, there are 4 associated parameters: MA01, MA02, ND01, sA01. Then call formula 1.4 to parse the numbers involved in the comparison operator to complete the parsing of the formula.

[0071] Step S37: Load the criterion file designed in advance in step S31, combine the parameter ID parsed in step S33 and the extracted arithmetic and logical operators into a code block, fill the code block into the formula position, remove the duplicate parameter ID and fill it into the associated parameter position, and write the completed file to the specified path on the disk to complete the generation of the criterion to be compiled.

[0072] After the generation of the files to be compiled is completed, the pre-configured compilation tool chain needs to be called for compilation. The overall flow chart is as follows: Figure 5 As shown. ① If you are in a Windows environment, you need to call MINGW / LLVM / CLANG to compile the file. Since the functions of the criteria are different, it is necessary to compile other required resources in advance. After compiling them into linkable resource files, call the G++ compiler to compile the ".cpp" source file, and link the linkable resource file to the generated ".dll" dynamic link library. The calling process can be started through a Windows batch program or in a C++ application using the Windows operating system API function CreateProcess to start a command line process for compilation. ② If you are in a Linux (Unix) environment, directly call the G++ compiler or use the written Makefile to compile the file to be compiled to generate a ".so" shared library. It should be noted that the specific compilation command is related to the running operating system, the compilation tool chain used, and the required functions.

[0073] In summary, a method for dynamically compiling flight parameter criteria of the present invention pre-designs the code required for the criteria, leaves blank the criteria formula and associated parameters, fills in the criteria formula and associated parameters after the criteria formula is parsed, generates a criterion file to be compiled, and finally compiles the file to be compiled into an executable program that can be linked to the main program through a compilation tool chain, thereby realizing dynamic compilation of the criteria into an executable program. Compared with the original system and development process, the time for converting the criteria into an executable program is greatly shortened, the software development process is greatly accelerated, and the efficiency of the guarantee is greatly improved. In addition, the present invention also additionally supports the ground support personnel to customize the input and summary of the criteria, which greatly improves the utilization rate of the ground support personnel's experience criteria. Due to the full utilization of the experience criteria, the guarantee time can be greatly reduced and the release efficiency can be improved.

Claims

1. A method for dynamically compiling flight parameter diagnosis rules, characterized in that: Here are the steps: Step 1: Manage the flight parameter ID by binding the flight parameter to the flight parameter ID consisting of four ASCII characters; The specific operation is as follows: First, the flight parameter data is classified according to the system to which it belongs to obtain no less than 20 types of system parameters, and then the system parameters are divided into switch quantity (D) and analog quantity (A); then, the classified parameters are numbered in sequence (00-zz), and the systems to which they belong are numbered in sequence (AZ, az); finally, the system to which it belongs, the data type and the parameter number are combined to obtain the parameter ID corresponding to each parameter; Step 2: Formula management of flight parameter criteria, i.e., converting the flight parameter criteria into a formula that performs arithmetic and logical operations on at least one parameter ID converted in step 1 and adds a duration; wherein the parameter ID uniquely corresponds to the parameter and can refer to the parameter; The specific operations are as follows: Step 2-1: Based on the text description of the criterion, write out the conditional expression of all parameters in the criterion. Each condition is composed of at least one parameter, and then undergoes arithmetic and logical operations and adds a duration. There must be at least one arithmetic operation and a logical operation, but the duration may not be required. The obtained primary condition n, n = 1, 2, 3…; Step 2-2: Based on the text description of the criterion, write out the combination condition m obtained by logical operation and adding the duration of the initial condition in step 2-1, where m = I, II, III…; Step 2-3: Based on the text description of the criterion, the initial conditions in step 2-1 that have not been combined in step 2-2 and the combined conditions generated in step 2-2 are subjected to logical operations and the duration is added to obtain the original formula of the criterion; Step 2-4: Replace the parameters in the original formula with the parameter ID converted in step 1, convert all durations to seconds, add "," before the time to distinguish it from the conditional expression, and add specific segmentation for each condition or combination of conditions that needs to add duration to obtain the criterion formula; Step 3: Parse the criterion formula and convert it into the required code, and generate the file to be compiled; Step 4: Compile the file to be compiled into a linkable executable program.

2. A method for dynamically compiling flight parameter diagnosis rules as claimed in claim 1, characterized in that: The specific operations of step 3 are as follows: Step 3-1: Pre-design the criterion code file according to the functional requirements, and leave the associated parameters and formula parts blank; change the suffix of the designed code file to ".bin" and compile it into the main program; Step 3-2 uses the regular expression parsing criterion formula of formula 1.1 to extract the content inside each delimiter. After the extraction is completed, the content inside the delimiter should be in the form of "conditional expression, duration"; \[(.*)\](0.1) Step 3-3 uses the regular expression of formula 1.2 to parse the contents inside the delimiter extracted in step 3-2 in sequence, and obtain the conditional expression (before) and duration (after) before and after ","; (.*(?=,)),(\d*\.?\d*)(0.2) Among them: (.*(?=,)) is used to match any content before the comma; the ".*" inside means matching any character; (?=,) means positive lookahead, ensuring that the matched content is followed by a comma, but not including the comma itself; the "," following (.*(?=,)) means directly matching the comma; (\\d*\\.?\\d*) is used to match a number, supporting integers or decimals; the first \d* from left to right inside means matching any number of numbers; \.? means matching a decimal point; the second \d* means matching any number of numbers again; Step 3-4 uses the regular expression of formula 1.3 to parse the parameter ID used in the conditional expression; \b[a-zA-Z]{2}[0-9A-Za-Z]{2}\b(0.3) where: \b is used to match word boundaries to ensure that the matched content is a complete word. A word boundary refers to the boundary between a word and a space, punctuation, or other non-word character; [a-zA-Z]{2} is used to match the first two consecutive English letters from left to right; [0-9A-Za-Z]{2} is used to match the last two consecutive letters or numbers; Step 3-5 uses the regular expression of formula 1.4 to parse the numeric parameter used in the logical comparison contained in the conditional expression extracted in step 3-4; [<=>](-?\d+\.?\d*)(0.4) where: [<=>] is used to match one of the characters '<', '=' or '>'; (-?\d+\.?\d*) is used to match a floating point number, -? means matching an optional minus sign, \d+ means matching one or more digits, \.? means matching an optional decimal point (.), and \d* means matching the decimal part, which has 0 or more digits; Step 3-6 extracts the remaining part of the criterion formula, that is, the remaining part of the criterion formula except the parameter ID, the digital parameter used in the logical comparison operation and the duration; Step 3-7 loads the pre-designed criterion code, removes duplicates from the parameter ID extracted in step 3-4 and fills it in the location of the associated parameter, composes a code block with the parsed parameter ID, logical operation, arithmetic operation and duration, fills it in the part where the formula is located and generates a file to be compiled.

3. A method for dynamically compiling flight parameter diagnosis rules as claimed in claim 2, characterized in that: In the steps 3-5, the logic comparison includes >, <, ==, <=, >=, !=.

4. A method for dynamically compiling flight parameter diagnosis rules as claimed in claim 1, characterized in that: In the steps 2-4, the form of the judgment formula is "[conditional expression, duration]", where the duration must be greater than or equal to 0, and equal to 0 means that the moment the conditional expression is established, a fault is determined.

5. A method for dynamically compiling flight parameter diagnosis rules as claimed in claim 1, characterized in that: In the steps 2-4, the specific segmentation uses "[]".

6. A method for dynamically compiling flight parameter diagnosis rules as claimed in claim 1, characterized in that: In the steps 2-4, the specific operation of step 4 is as follows: Step 4-1 compiles the resource files required to implement other functions in the file to be compiled, and generates a linkable target resource file; Step 4-2 compiles the criteria file to be compiled, and links the target resource file generated in step 4-1 to generate a criteria target file that can be linked to the main program.

Images