Aero-engine testing method, device and electronic equipment

Abstract

The application relates to the field of aviation testing, in particular to an aviation engine testing method and device and electronic equipment. The method comprises the following steps: obtaining a testing instruction; determining a testing scheme corresponding to the testing instruction, wherein the testing scheme comprises at least one preconfigured state, sub-configurations in the state are independently configured, and the sub-configurations comprise at least one of the following: throttle configuration, oscillographic interpretation configuration, operation instruction configuration, parameter recording configuration, performance recording configuration and loading requirement configuration; and the testing scheme is sent to the aviation engine for testing, so as to obtain a testing result. The application can test the aviation engine.

Description

Technical Field

[0001] This application relates to the field of aviation testing, and more specifically, to an aircraft engine testing method, apparatus, and electronic equipment. Background Technology

[0002] Aero-engine testing is a core component of performance verification for aero-engine equipment. Current aero-engine testing processes rely on manual operation, exhibiting significant shortcomings in test reproducibility, data reliability, and operational safety. This fails to meet the high-precision, high-reliability type approval testing requirements of next-generation aero-engines. Therefore, it is necessary to design an automated aero-engine testing method to fill this technological gap. Summary of the Invention

[0003] This application provides a method, apparatus, and electronic equipment for testing aircraft engines, thereby automating the testing of aircraft engines.

[0004] According to a first aspect of the embodiments of this application, an aero-engine testing method is provided, comprising: acquiring a test command; determining a pre-set test scheme corresponding to the test command, wherein the test scheme includes at least one pre-configured state, wherein the sub-configurations in the state are independently configured, and the sub-configurations include at least one of the following: throttle configuration, oscilloscope interpretation configuration, operation command configuration, parameter recording configuration, performance admission configuration, and loading requirement configuration; and sending the test scheme to the aero-engine for testing to obtain test results.

[0005] Specifically, the test scheme includes at least one stage, each stage includes at least one program, each program includes at least one module, and each module includes at least one state.

[0006] Specifically, the basic elements selected during the configuration of the state are uniform and standardized, and the program switches in the basic elements are uniformly classified according to control category, loading category, oscilloscope interpretation category, and performance category.

[0007] Specifically, before configuring the state, if a historical configuration record is found to have a similarity to the state within a similarity threshold, then the sub-configuration in the historical state is copied as the sub-configuration of the state.

[0008] Specifically, the state is configured as a structure including a start timing expression, a state execution body, and an end timing expression.

[0009] Specifically, according to a second aspect of the embodiments of this application, an aero-engine testing apparatus is provided, comprising: a state configuration module for configuring states, the state module comprising a plurality of mutually independent sub-configuration units, the sub-configuration units comprising at least one of the following: a throttle configuration unit, an oscilloscope interpretation configuration unit, an operation command configuration unit, a parameter recording configuration unit, a performance acquisition configuration unit, and a loading requirement configuration unit; a hierarchical arrangement module for obtaining a test plan based on the states; and a state-driven execution module for performing tests according to the test plan.

[0010] Specifically, the hierarchical orchestration module is used to assemble the states into modules, assemble the modules into programs, assemble the programs into stages, and assemble the stages into the test plan.

[0011] Specifically, the device further includes an orchestration tree query and state copying module, which is used to query the hierarchy of the test scheme assembled by the hierarchical orchestration module, and is also used to copy the sub-configuration in the historical state as the sub-configuration of the state if a historical configuration record with a similarity threshold to the state is found before configuring the state.

[0012] Specifically, the device also includes a program modeling module, which is used to standardize the basic elements and classify the program switches according to control, loading, interpretation of oscilloscope and performance, so that the state configuration module can call the basic elements and the program switches to configure the state.

[0013] According to a third aspect of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores an aero-engine testing method, and the processor is used to employ the aero-engine testing method described above when executing the aero-engine testing method.

[0014] According to a fourth aspect of the embodiments of this application, a computer-readable storage medium is provided, storing a computer program that can be loaded by a processor and execute the methods described above.

[0015] In this embodiment, the test plan is pre-set, and the test plan includes at least one pre-configured state. The sub-configurations in the state are independently configured, and the sub-configurations include at least one of the following: throttle configuration, oscilloscope interpretation configuration, operation command configuration, parameter recording configuration, performance admission configuration, and loading requirement configuration. The test plan is sent to the aero-engine for testing to obtain test results. By attaching six independent sub-configuration units under the state configuration module, the control semantics are decoupled, and the configuration is refined. Attached Figure Description

[0016] Figure 1This is a schematic diagram of the application environment of an aero-engine testing method in one embodiment.

[0017] Figure 2 This is a flowchart of an aircraft engine testing method in one embodiment.

[0018] Figure 3 This is a structural block diagram of an aero-engine testing device in one embodiment.

[0019] Figure 4 This is a flowchart illustrating the configuration and use of an aero-engine testing device in one embodiment.

[0020] Figure 5 This is a structural block diagram of an electronic device in one embodiment. Detailed Implementation

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0022] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0023] According to an embodiment of this application, an embodiment of an aircraft engine testing method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0024] The aircraft engine testing method provided in this application can be applied to, for example... Figure 1The application environment shown is illustrated. In this environment, test equipment 001, terminal equipment 002, and aircraft engine 003 communicate via wired or wireless communication methods, such as networks or Bluetooth. It should be understood that test equipment 001 generally refers to one of multiple test devices; this embodiment only uses test equipment 001 as an example.

[0025] Terminal device 002 can obtain test commands from test device 001, then find a pre-set test plan corresponding to the test command. The test plan includes at least one pre-configured state. The test plan is then sent to the aero-engine for testing to obtain test results. Optionally, test device 001 and terminal device 002 can be, but are not limited to, electronic devices such as smartphones, tablets, laptops, desktop computers, and smart control panels; no limitation is imposed here. Test device 001 can integrate the functions of terminal device 002, that is, after receiving test commands, test device 001 can generate a test plan locally and test the aero-engine.

[0026] This application provides a test method for an aircraft engine, which, for ease of understanding, is executed by the aforementioned terminal equipment, such as... Figure 2 As shown, the test methods for aero-engines include: S101, Obtain test instructions.

[0027] Test commands can be input by the user through the human-machine interface of the test equipment, or they can be automatically issued by the upper-level test management system. Test commands can include information required for the test, such as model information, test type information, and test target information.

[0028] Test instructions may include, but are not limited to, steady-state performance calibration instructions, dynamic transient state instructions, boundary and safety test instructions, and inspection, repeatability, and delivery instructions. Steady-state performance calibration instructions may include instructions for recording steady-state performance from idle to maximum, ground idle stability assessment instructions, intermediate power point steady-state performance calibration instructions, and rated maximum state steady-state performance test instructions. Dynamic transient state instructions may include instructions for testing acceleration performance from idle to maximum, instructions for testing deceleration performance from maximum to idle, instructions for assessing the acceleration on / off transition process, and instructions for testing throttle step response characteristics. Boundary and safety test instructions may include instructions for investigating compressor surge boundaries, instructions for verifying over-temperature boundaries, instructions for testing the anti-surge bleed valve's operational cycle, and instructions for bleed air loading simulation assessment. Inspection, repeatability, and delivery instructions may include instructions for cold start-up inspection, instructions for three-time repeatability performance comparison tests, instructions for factory delivery acceptance performance re-inspection, and instructions for measuring lubricating oil consumption during shutdown.

[0029] S102. Determine a pre-set test plan corresponding to the test command. The test plan includes at least one pre-configured state. The sub-configurations in the state are independently configured. The sub-configurations include at least one of the following: throttle configuration, oscilloscope interpretation configuration, operation command configuration, parameter recording configuration, performance acquisition configuration, and loading requirement configuration.

[0030] The six core test control logics—throttle operation, waveform interpretation, command triggering, data recording, performance acquisition, and load loading—are broken down into six independent sub-configurations. Iteration of any sub-configuration rule does not affect the operation of the other sub-configurations. It is compatible with various hardware execution carriers such as ground test benches, high-altitude simulation test benches, and complete machine delivery and acceptance test benches, and is suitable for testing various types of aero engines, including turbojet, turbofan, and turboprop engines.

[0031] The state is configured with a structure including a start timing expression, a state execution body, and an end timing expression. If the conditions are met according to the timing expression, the system will automatically start and stop, and the sub-configurations will be executed synchronously. Throughout the process, no real-time intervention from operators is required for throttle operation and data acquisition, eliminating the interference of human operation techniques on the test results. The same test plan can achieve a highly consistent test process when executed on different test benches and on different shifts, meeting the repeatability assessment requirements of aero-engines.

[0032] Throttle configuration configures throttle operation nodes according to status, driving throttle operation according to timing expressions and action expressions; Oscilloscope interpretation configuration configures oscilloscope groups and oscilloscope items according to status, acquiring and interpreting waveforms according to the timing expressions of the oscilloscope groups; Operation command configuration configures control command operation items according to status, triggering control command buttons according to timing expressions; Parameter recording configuration configures parameter recording groups according to status, recording parameters according to timing expressions, recording symbols, and recording duration; Performance admission configuration configures performance admission items according to status, admitting performance data according to timing expressions and recording duration; In steady-state step type states, performance admission is also configured with steady-state judgment logic, that is, first judging whether the time has reached the time threshold, then judging whether the fluctuation is less than the fluctuation threshold, and only when both are met is performance admission triggered; Loading requirement configuration configures loading items according to status, executing loading according to timing expressions, channels, loading types, and loading amounts.

[0033] The test plan includes at least one phase, each phase includes at least one program, each program includes at least one module, and each module includes at least one state. States are configured by calling basic elements. In other words, the test plan is organized using a seven-level hierarchical orchestration structure, from bottom to top: program model layer, state layer, six types of sub-configurations layer, module layer, program layer, phase layer, and test plan layer. The program model layer is used to set the basic elements. After the states and their sub-configurations are configured, the hierarchical orchestration module assembles the states into modules, the modules into programs, the programs into phases, and the phases into the test plan, forming a complete orchestration tree structure of "test plan, phase, program, module, state, and six types of sub-configurations." The complete orchestration tree can be queried by device model and test type, and the orchestration results can be queried and reused. The orchestration tree can be queried through the orchestration tree management module.

[0034] Specifically, before configuring the state, the system first establishes the basic elements of the experimental program's model layer through the program modeling module, ensuring that the basic elements selected during state configuration are uniform and standardized. These basic elements include program symbols, program formulas, program switches, and spectrum analysis configurations, all uniformly mounted under the program model. Program symbols serve as the basic reference elements for formulas and judgment conditions, containing identifiers for internal program reference; program formulas reference predefined symbols for expression calculation; program switches carry usage classification and execution unit information, uniformly categorized by usage, including four categories: control, loading, oscilloscope interpretation, and performance, used for program control logic judgments so that the state is referenced according to its usage category during configuration; the spectrum analysis configuration defines the correspondence between throttle lever angle and speed parameters for oscilloscope interpretation reference.

[0035] Before configuring the state, if a historical configuration record is found with a similarity threshold of less than 85%, the sub-configurations from that historical state are copied as sub-configurations for the new state. This enables cascading copying of states, allowing the copying of a state and all six types of sub-configurations. After copying, the state name is automatically appended with a suffix to avoid naming conflicts. The similarity threshold can be set as needed. Based on the standardized basic element library of the program model layer and the complete cascading copying function, repeatable tests of the same engine model and tests of derivative models in the same series can directly reuse historical mature state configurations. Only minor modifications to the timing expressions and judgment thresholds are needed to generate new test plans. Compared to manually writing test programs line by line, the configuration workload is greatly reduced, while avoiding logical errors caused by manual input. For example, for multiple steady-state tests of the same engine model, the verified "maximum steady-state admission state" can be directly copied, requiring only modification of the adaptation batch number for reuse. For engines of the same type but different bypass ratios, if the similarity is higher than 85%, the entire set of sub-configurations can be cascaded and copied, requiring only minor adjustments to the throttle action expression.

[0036] In some implementations, the formula for calculating similarity can be: , , Where S represents the similarity between the two states, and i represents the number corresponding to the six sub-configurations. The weights configured for each sub-sub. Similarity for a single sub-configuration It is the local weight of the j-th parameter within the i-th sub-configuration. For continuous numerical aero-engine parameters, such as speed, temperature, flow rate, and load power, which allow for errors, a relative error comparison is used. ,in, To set the allowable error threshold, a full consistency check is applied to logic and enumeration-type configuration parameters, such as startup timing, surge protection logic, and measurement point selection, where errors are not allowed. .

[0037] The weights of each sub-configuration are set as needed, with the throttle configuration having the highest weight, the oscilloscope interpretation configuration having the second highest weight, and the load requirement configuration having the lowest weight. Since the throttle directly determines the engine's operating point, any deviation from this condition can completely alter the engine's thermodynamic cycle, blade load, and stress level, potentially even causing over-revving damage. The safety and effectiveness of the test run are entirely determined by the throttle state, therefore it is given the highest weight to ensure that operating condition similarity plays a decisive role in similarity assessment. Oscilloscope interpretation serves as a safety safety net for the test run, including surge threshold, exhaust over-temperature threshold, rotor vibration alarm, and intake distortion protection logic. Engine testing is a high-risk, destructive test; inconsistent interpretation rules can lead to situations where the engine should be shut down but continues to operate, causing major equipment accidents such as compressor stall and turbine ablation. Safety constraints have the second highest priority after operating conditions, hence their second-highest weight. Load requirement configurations, including bleed air extraction, power extraction, exhaust back pressure, and bench load, are additional boundary simulation conditions and constitute additional disturbances to the operating conditions. Even with slight differences in loading conditions, the engine core speed, temperature, and protection threshold remain unchanged, making the test highly relevant. Since it's merely an additional element in environmental simulation, its weight is the lowest. The aforementioned similarity calculation method employs a two-level weighted similarity calculation, assigning weights to the differences in the six sub-configurations. Different calculation methods are used for parameters within each sub-configuration based on whether error is permissible. The weights of each parameter within a sub-configuration are set as needed, making the similarity calculation results more accurate and reliable. In other implementations, S= Assigning the same weight to each sub-configuration simplifies the calculation process.

[0038] S103. Conduct the test according to the test plan to obtain the test results.

[0039] After obtaining the test plan, the configured test plan is first converted into an executable program and distributed to the test equipment. The test equipment receives and loads the executable program through the program loading module, and breaks down the test plan according to "stage—program—module—state" to obtain a state sequence. The state-driven execution module drives execution according to the state sequence. When entering each state, it parses the start timing expression of that state to trigger execution, schedules the execution of the six types of sub-configurations in that state in sequence or in parallel, parses the end timing expression to end that state, and then enters the next state, until the state sequence is completed. After the test, execution and recording data are generated as the test results.

[0040] When triggered, the configuration that needs to be executed by the aircraft engine is converted into electrical control commands and sent to the aircraft engine for execution. The configuration that does not need to be executed by the aircraft engine is executed by the test equipment. The test results are obtained through the cooperation of the aircraft engine and the test equipment.

[0041] Based on the above, a seven-level hierarchical orchestration structure with states as the core execution unit is constructed, setting the test program as a structured, reusable, and deployable hierarchical system. By attaching six independent control semantic sub-configurations to states, control semantics such as throttle, oscilloscope interpretation, operation commands, parameter recording, performance recording, and loading requirements are decoupled, achieving refined configuration and independent reuse of control semantics. The program model layer uniformly models basic elements and references them according to their purpose, ensuring consistency in cross-state references and high element reuse rates. A state cascading replication mechanism allows for rapid generation of similar states without requiring item-by-item reconfiguration. A state-driven automatic execution mechanism forms a configuration-execution closed loop, effectively reducing human error. This achieves the technical effects of structured program configuration, significantly improved configuration efficiency, low maintenance costs, high configuration consistency, and improved efficiency and consistency during the test run.

[0042] This application also provides an aero-engine testing device, such as... Figure 3 As shown, it includes: a receiving module, a program configuration side, and an execution side. The receiving module is used to receive test commands. The program configuration side includes a status configuration module for configuring the status. The status module includes multiple independent sub-configuration units, each of which includes at least one of the following: a throttle configuration unit, an oscilloscope interpretation configuration unit, an operation command configuration unit, a parameter recording configuration unit, a performance acquisition configuration unit, and a loading requirement configuration unit. The program configuration side also includes a hierarchical orchestration module for obtaining a test plan based on the status. The execution side includes a status-driven execution module for performing tests according to the test plan.

[0043] The state-driven execution module breaks down the test plan into states ordered by a state sequence, and then executes each state sequentially. Upon entering each state, it parses the start time expression for that state to trigger execution, traverses the six sub-configurations under that state to execute each sub-configuration separately, parses the end time expression to end that state, and then enters the next state, until the state sequence has been completed.

[0044] Specifically, the hierarchical orchestration module assembles states into modules, modules into programs, programs into stages, and stages into test plans, constructing a seven-level hierarchical orchestration structure with states as the core execution unit. This sets the test programs as a structured, reusable, and deployable hierarchical system. The entire test plan is stored and archived in a tree-like orchestration structure, supporting retrieval and recall by machine type and test type, overall export and distribution, and version retention and comparison. This facilitates test outline version control, fault reproduction program backtracking, and cross-test bench program porting, resulting in lower long-term maintenance costs.

[0045] Specifically, the program configuration side also includes an orchestration tree query and status copy module, which is used to query the hierarchy of test schemes assembled by hierarchical orchestration modules. Specifically, the orchestration tree query and status copy module returns a complete orchestration tree structure of "stage, program, module, status, and six sub-configurations" according to the machine model and test type.

[0046] It is also used to copy the sub-configuration in the historical state as the sub-configuration of the current state if a historical configuration record with a similarity threshold is found before the current state is configured. The calculation method of similarity refers to the test method of aero-engine, which will not be repeated here.

[0047] The similarity threshold can be set to 80%~90%. For steady-state admissions where only the duration and temperature thresholds are slightly modified, six sub-configurations can be cascaded and copied with one click, without having to build each configuration rule repeatedly.

[0048] The program configuration side also includes a program modeling module. The basic elements established by this module include program symbols, program formulas, program switches, and spectrum analysis configurations, all uniformly mounted under the program model. Program symbols are various measurement parameters collected from sensors, serving as the basic reference elements for formulas and judgment conditions. Program formulas reference predefined symbols for expression calculations, used to write steady-state fluctuation judgment calculation formulas. Program switches carry application classification and execution unit information, used for steady-state acquisition enable, oscilloscope storage enable logic control, with application classifications including control, loading, oscilloscope interpretation, and performance. The spectrum analysis configuration defines the correspondence between throttle lever angle and speed parameters.

[0049] The program modeling module also includes a program distribution module, and the execution side also includes a program loading module. The program distribution module is used to convert the configured test plan into an executable program and distribute it to the program loading module. The program loading module is used to receive and load the distributed executable program and organize the execution queue according to the sequence of "stage - program - module - status".

[0050] Based on the above, the aero-engine testing device provided in this application organizes the test program into a structured hierarchical system through a seven-level hierarchical orchestration module, realizing the structured, reusable, and deployable nature of the program; it decouples control semantics by attaching six independent sub-configuration units under the state configuration module, achieving refined and low-coupling configuration; it improves element reuse rate and configuration consistency by uniformly modeling basic elements and classifying and referencing them according to their uses through the program model modeling module; it significantly improves configuration efficiency and supports cross-bench program reuse by realizing state cascade replication and overall orchestration tree query and deployment through the orchestration tree query and state copying module; and it automatically drives execution according to state sequence and timing expression through the state-driven execution module, forming a configuration-execution closed loop, reducing human operation errors, and improving the efficiency and consistency of the test process.

[0051] Figure 4 The configuration and usage process of the aircraft engine testing device according to the embodiments of this application are as follows: Figure 4 As shown, the overall process is divided into two main stages: configuration modeling and online test execution. First, program modeling is performed, defining program symbols, formulas, switch quantities, and spectrum-related configurations. Then, state configuration is carried out, defining the basic attributes of each operating state and binding six sub-configurations: throttle, oscilloscope, command, record, performance, and load. After completing the basic element configuration, hierarchical orchestration is executed, assembling modules, programs, stages, and test plans from top to bottom to build a complete orchestration tree. The system supports orchestration tree querying and state cascading copying functions, allowing for rapid reuse of existing test configurations. After configuration is complete, the standardized executable program is distributed to the test execution side.

[0052] After the execution side receives the program, it loads the experimental logic sequentially according to the hierarchical sequence of stages, programs, modules, and states. When entering a single state, the system parses the state start timing expression. Once the condition is met, the six types of sub-configurations bound to that state are executed synchronously. During execution, the system continuously parses the end timing expression. If the exit condition is met, the current state ends. Then, it checks whether the state sequence has not been completed: if there are subsequent states, it jumps to the next state and executes it in a loop; if all states have been completed, the experiment ends, and the entire process execution log and experimental data collection records are summarized and output.

[0053] This application also provides an electronic device, including a memory and a processor. The memory stores an aero-engine testing method, and the processor is used to employ the aero-engine testing method described above when executing the aero-engine testing method.

[0054] Specifically, such as Figure 5 As shown, the electronic device includes a processor 100, at least one communication bus 200, a user interface 300, at least one external communication interface 400, and a memory 500. The communication bus 200 is configured to enable communication between these components. The user interface 300 may include a display screen, and the external communication interface 400 may include standard wired and wireless interfaces. The memory 500 stores aero-engine testing methods. The processor 100 is used to employ the aforementioned methods when executing the aero-engine testing methods stored in the memory 500.

[0055] This application also provides a computer-readable storage medium storing a computer program that can be loaded by a processor and execute the methods described above.

[0056] The above description of the embodiments applied to electronic devices and storage media is similar to the description of the method embodiments described above, and has similar beneficial effects. For technical details not disclosed in the embodiments of electronic devices and storage media of this application, please refer to the description of the method embodiments of this application for understanding.

[0057] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0058] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0059] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0060] 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 units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0061] Furthermore, 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. The integrated unit can be implemented in hardware or as a software functional unit.

[0062] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a 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 all or 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 a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0063] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A test method for an aero-engine, characterized in that, include: Get test commands; A pre-set test plan corresponding to the test command is determined. The test plan includes at least one pre-configured state. The sub-configurations in the state are configured independently of each other. The sub-configurations include at least one of the following: throttle configuration, oscilloscope interpretation configuration, operation command configuration, parameter recording configuration, performance acquisition configuration, and loading requirement configuration. The test plan is sent to the aircraft engine for testing to obtain test results.

2. The aero-engine testing method according to claim 1, characterized in that, The test scheme includes at least one stage, each stage includes at least one program, each program includes at least one module, and each module includes at least one state.

3. The aero-engine testing method according to claim 1, characterized in that, The basic elements selected during the configuration of the state are uniform and standardized, and the program switches in the basic elements are uniformly classified according to control category, loading category, oscilloscope interpretation category, and performance category.

4. The aero-engine testing method according to claim 1, characterized in that, Before configuring the state, if a historical configuration record is found to have a similarity to the state within a similarity threshold, then the sub-configuration in the historical state is copied as the sub-configuration of the state.

5. The aero-engine testing method according to claim 1, characterized in that, The state is configured as a structure including a start timing expression, a state execution body, and an end timing expression.

6. An aircraft engine testing device, characterized in that, include: A status configuration module is used to configure the status. The status module includes multiple independent sub-configuration units, and each sub-configuration unit includes at least one of the following: throttle configuration unit, oscilloscope reading configuration unit, operation instruction configuration unit, parameter recording configuration unit, performance acquisition configuration unit, and loading requirement configuration unit. A hierarchical orchestration module is used to obtain a test plan based on the stated state; State-driven execution module: used to perform tests according to the test plan.

7. The aero-engine testing apparatus according to claim 6, characterized in that, The hierarchical orchestration module is used to assemble the states into modules, assemble the modules into programs, assemble the programs into stages, and assemble the stages into the test plan.

8. The aero-engine testing apparatus according to claim 7, characterized in that, Also includes: The orchestration tree query and state copying module is used to query the hierarchy of the test scheme assembled by the hierarchical orchestration module. It is also used to copy the sub-configuration in the historical state as the sub-configuration of the state if a historical configuration record with a similarity threshold to the state is found before configuring the state.

9. The aero-engine testing apparatus according to claim 6, characterized in that, Also includes: The program modeling module is used to standardize the basic elements and classify the program switches according to control, loading, oscilloscope interpretation and performance, so that the state configuration module can call the basic elements and program switches to configure the state.

10. An electronic device, characterized in that, The device includes a memory and a processor, wherein the memory stores an aero-engine testing method, and the processor is used to employ the aero-engine testing method according to any one of claims 1-5 when executing the aero-engine testing method.

Images