Test management and control system and method for liquid rocket engine

Abstract

The invention relates to a test management and control system and a test management and control method for a liquid-propellant rocket engine, and aims to solve the technical problems that an existing test process is easy to make mistakes and the test efficiency is relatively low. By constructing a data model management unit, a task modeling and instantiation engine unit, a resource management and monitoring unit and a plan generation and process driving unit, the system can automatically trigger resource matching and plan generation based on a test task and drive a workflow engine to execute, and a data service unit is used for providing data for the test task. And the integrity and traceability of data in the test process are ensured.

Description

Technical Field

[0001] This invention relates to liquid rocket engine testing, specifically to a test control system and method for liquid rocket engines. Background Technology

[0002] As the core of aerospace propulsion systems, the ground ignition test of liquid rocket engines is a crucial step in verifying the correctness of engine design and assessing product performance and reliability. The test process is highly complex, involving not only in-depth testing of liquid rocket engines as a multi-system coupled product, but also collaboration among design units, testing units, and overall units, and relying on scarce resources such as dedicated test stands and telemetry and control systems.

[0003] Currently, the test control process for liquid rocket engines is relatively discrete. When a test mission is issued, the person in charge needs to manually match suitable test resources and transmit the test subject, i.e., engine information and verification requirements, to the relevant responsible department in paper form before the test is carried out. At the same time, the generated test site data needs to be manually burned onto a disc for delivery.

[0004] Because of the lack of a structured and unified system to link the core elements of the test process, namely the test object (engine and specific verification requirements), required resources (test bench capabilities), execution plan, process data and output documents, the computer cannot recognize the test process as a complete entity that can be processed as a whole and whose status is traceable. This makes it difficult to coordinate the test process, difficult to connect data, and results in low test efficiency.

[0005] Furthermore, there are multiple manual breakpoints in the experimental data stream during the experiment. Key parameters in the test task book (unstructured document) issued by the design unit need to be manually interpreted and re-entered into the test outline. The massive amount of raw data (time series data, video materials, image materials, and measurement point data) generated during the test run lacks automatic association with tasks and resources, requiring manual sorting, naming, and archiving. This is extremely easy to confuse and lose context. Report preparation requires manually extracting information from the scattered data again, making the entire test process prone to errors and with low test efficiency. Summary of the Invention

[0006] To address the technical problems of error-prone and inefficient testing processes in existing testing procedures, this invention provides a test control system and method for liquid rocket engines.

[0007] To achieve the above objectives, the present invention adopts the following technical solution: A test control system for a liquid rocket engine is characterized by comprising a mission modeling and instantiation engine unit, a resource management and monitoring unit, a plan generation and process driving unit, and a data model management unit; the data model management unit includes a test item module, a test resource module, and a test plan item module. The task modeling and instantiation engine unit is used to call up the test item module and instantiate it according to the test task after receiving the test task sent by the external system, so as to obtain the test item instance. The test item instance includes the verification requirements and component parameters of the engine to be tested. The data output end of the task modeling and instantiation engine unit is connected to the data input end of the resource management and monitoring unit and the plan generation and process driving unit, respectively, and is used to send the verification requirements and component parameters to the resource management and monitoring unit and the plan generation and process driving unit, respectively. The request output end of the task modeling and instantiation engine unit is connected to the request input end of the resource management and monitoring unit to send resource matching requests. After receiving the resource matching request, the resource management and monitoring unit determines the matching test bench resources according to the verification requirements, and calls the test resource module to instantiate the test bench resources to obtain test resource instances. The data output terminal and request output terminal of the resource management and monitoring unit are respectively connected to the data input terminal and request input terminal of the planning generation and process driving unit, and are used to send test resource instances and task execution requests; After receiving a task execution request, the plan generation and process driving unit determines a plan template based on component parameters and test resource instances, and retrieves the test plan item module. It then instantiates the test plan item instance based on the plan template to obtain a test plan item instance, which includes a test execution logic network. The plan generation and process driving unit drives the test execution logic network to conduct tests on the engine under test.

[0008] Furthermore, it also includes a data service unit, and the data model management unit further includes an experimental document module; The data input terminal of the data service unit is connected to the data output terminal of the task modeling and instantiation engine unit. After receiving the test task sent by the task modeling and instantiation engine unit, the test document module is retrieved and instantiated according to the test task to obtain the test document instance. The plan generation and process driving unit's data output terminal and the data service unit's data input terminal are connected. The plan generation and process driving unit's data output terminal is connected to the data service unit to send the received work instruction documents sent by the external system to the data service unit. The data service unit then retrieves and updates the test document instance based on the work instruction documents.

[0009] Furthermore, the data model management unit also includes an experimental data module; The request output terminal of the plan generation and process driving unit and the request input terminal of the data service unit are connected to send a collection request. After receiving the collection request, the data service unit collects the data during the experiment, retrieves the experimental data module, and instantiates the experimental data module based on the collected data to obtain an experimental data instance. The data service unit updates the test document instance based on the test data instance.

[0010] Furthermore, the resource management and monitoring unit includes a resource matching engine module and a resource capability database module; The data input terminal and request input terminal of the resource matching engine module are connected to the data output terminal and request output terminal of the task modeling and instantiation engine unit, respectively, and are used to receive verification requirements and resource matching requests. The request output end of the resource matching engine module is connected to the request input end of the resource capability database module. After receiving a resource matching request, the module sends a resource query request to the resource capability database module using the received verification requirements as query conditions. The data output end of the resource capability database module and the data input end of the resource matching engine module are connected. The database module is used to query the test bench resources that meet the test capability requirements according to the resource query request and send them to the resource matching engine module. The resource matching engine module is used to call the test resource module after receiving the test bench resource, and instantiate it according to the test bench resource to obtain the test resource instance.

[0011] Furthermore, the plan generation and process driving unit includes a workflow engine module and a plan template library module; The data input terminal of the workflow engine module is connected to the data output terminals of the task modeling and instantiation engine unit and the resource matching engine module, respectively, and is used to receive component parameters and test resource instances. The request input end of the workflow engine module and the request output end of the resource matching engine module are connected to receive task execution requests; The workflow engine module's request output end and the plan template library module's request input end are connected. After receiving a task execution request, the module sends a plan query request to the plan template library module using the received component parameters and test resource instances as query conditions. The data output end of the plan template library module is connected to the data input end of the workflow engine module, and is used to query the matching plan template according to the plan query request and send it to the workflow engine module; After receiving the plan template, the workflow engine module calls the test plan item module and instantiates it according to the plan template to obtain the test execution logic network; and drives the test execution logic network to test the engine to be tested.

[0012] Meanwhile, this invention also provides a test control method for a liquid rocket engine, employing the aforementioned test control system for a liquid rocket engine, characterized by the following steps: S1. After receiving the test task sent by the external system, the task modeling and instantiation engine unit extracts the data parameters of the engine to be tested from the test task, calls the test item module, and instantiates it according to the data parameters to obtain the test item instance. The test item instance contains the verification requirements and component parameters of the engine to be tested. S2, the task modeling and instantiation engine unit sends component parameters to the plan generation and process driving unit, sends verification requirements to the resource management and monitoring unit, and then initiates a resource matching request to the resource management and monitoring unit; S3. After receiving the resource matching request, the resource management and monitoring unit determines the matching test bench resource according to the verification requirements, and calls the test resource module to instantiate the test bench resource. After obtaining the test resource instance, the test resource instance is sent to the planning generation and process driving unit, and a task execution request is sent to it at the same time. S4. After receiving the task execution request, the plan generation and process driving unit determines the plan template based on the component parameters and test resource instance, and calls the test plan item module to instantiate it according to the plan template to obtain the test plan item instance. The test plan item instance includes the test execution logic network. The plan generation and process driving unit drives the test execution logic network to test the engine under test.

[0013] Furthermore, step S3 specifically includes: S3.1 After receiving a resource matching request, the resource matching engine module sends a resource query request to the resource capability database module, using the received verification requirements as the query conditions. S3.2 The resource capability database module queries the test bench resources that meet the test capability requirements according to the resource query request, and sends them to the resource matching engine module. S3.3 After receiving the test bench resources, the resource matching engine module calls the test resource module and instantiates them according to the test bench resources to obtain test resource instances; S3.4 The resource matching engine module sends the test resource instance to the plan generation and process driving unit, and at the same time sends a task execution request to it.

[0014] Furthermore, step S4 specifically includes: S4.1 After receiving the task execution request, the workflow engine module sends a plan query request to the plan template library module using the received component parameters and test resource instances as query conditions. S4.2 The plan template library module retrieves a matching plan template based on the plan query request and sends it to the workflow engine module; S4.3 After receiving the plan template, the workflow engine module calls the test plan item module and instantiates it according to the plan template to obtain the test execution logic network. S4.4 The workflow engine module drives the test execution logic network to test the engine under test.

[0015] Furthermore, step S1 also includes the following process: The task modeling and instantiation engine unit will receive the test task and send it to the data service unit. After receiving the test task, the data service unit will retrieve the test document module and instantiate it according to the test task to obtain the test document instance. Step S4.1 also includes the following process: The workflow engine module sends the received work instruction documents from the external system to the data service unit, which then retrieves and updates the test document instance based on the work instruction documents.

[0016] Furthermore, in step S4.4, during the testing of the engine under test, test data is collected at preset acquisition nodes. The specific steps are as follows: a. At the preset data collection node, the workflow engine module sends a data collection request to the data service unit; b. After receiving the data collection request, the data service unit collects the data during the experiment, retrieves the experimental data module, and instantiates the experimental data module based on the collected data to obtain the experimental data instance. c. The data service unit retrieves and updates the test document instance based on the test data instance.

[0017] The beneficial effects of this invention are: 1. The present invention provides a test control system for liquid rocket engines. By constructing a complete test control system for liquid rocket engine tests, it solves the fundamental problem of scattered and heterogeneous test information that cannot be uniformly understood by computers in the traditional mode. It transforms the test process from a vague business concept into a precise, calculable, and traceable digital mapping, laying a unique and reliable data foundation for full-process automation and solving the technical problems of error-prone and low test efficiency in the existing test process. 2. The present invention provides a test control system for a liquid rocket engine, which can automatically trigger resource matching and plan generation based on the test mission and drive the workflow engine to execute. This changes the traditional mode that relies on manual transmission, coordination and promotion, shortens the test preparation and scheduling time from the traditional several days to the hour level, and avoids process errors or resource conflicts caused by human oversight, significantly improving the plan achievement rate of complex tests. 3. The present invention provides a test control method for liquid rocket engines, which constructs an end-to-end data pipeline. From field data acquisition, standardized packaging and reliable transmission to structured analysis, extraction and analysis on the system side, it realizes full-link automated processing of test data, ensures the integrity and traceability of data, and enables design, testing and overall units to collaborate on the same high-quality, structured data, solving the core pain points of repeated data interpretation and transmission distortion. Attached Figure Description

[0018] Figure 1 This is a structural block diagram of an embodiment of a test control system for a liquid rocket engine according to the present invention; Figure 2 This is a flowchart illustrating an embodiment of a test control method for a liquid rocket engine according to the present invention; Figure 3 This is a structure tree diagram of test items, test resources, test plan items, test data, and test documents in an embodiment of a test control system for a liquid rocket engine according to the present invention; Figure 4 This is a template diagram of a type II test plan in an embodiment of a test control method for a liquid rocket engine according to the present invention. Detailed Implementation

[0019] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0020] This embodiment provides a test control system for a liquid rocket engine, which constructs a complete structured mapping of the test process in the digital space. Based on the concept of systems engineering, it decomposes the test into five major modules: test items, test resources, test plan items, test documents, and test data, which respectively represent the test's verification objectives, material basis, execution blueprint, knowledge carrier, and test results. The structure of the five major modules is as follows Figure 3As shown, the test module characterizes the engine's structure and test verification requirements. It digitally models the composition relationships at the engine system, component, and part levels using a product BOM tree structure. The structure includes basic attribute units, engine structure units, and test verification requirement units. The engine structure includes basic engine attributes, component information, and part information. The test verification requirements include test types, measurement parameters, and evaluation indicators. A complete configuration baseline is established, including model specifications, technical parameters, and design drawing indexes. Additionally, test verification requirements are included, including test types, evaluation indicators, and a measurement parameter system. The test resource module represents the physical entities involved in engine ignition testing. Its structure includes basic attribute units and resource category units. The basic attributes include resource name, model specifications, status, test bench and location coordinates. Resource categories include generator hot test equipment, civil engineering system, process system, measurement and control system, etc. At the same time, a hierarchical data model is used to decompose the top-level resources, modeling the type as a parent resource node, with a list of associated subsystems under it. Each subsystem is further associated with its core component model, and digital drawings and indexes are associated with each resource instance. The test plan module represents the execution steps of the entire engine ignition test process. Its structure includes a basic attribute unit and a plan template library unit. The basic attributes define the plan item name, number, type, status, responsible person, and time node, etc. The plan template library includes three types of test plans: Type 1, Type 2, and Type 3. Logical dependencies between plan items are constructed based on the template library. The test document module represents the document entities involved in the engine ignition test. Its structure includes basic document attribute units and document category units. The basic attributes include document name, number, version number, test bench to which it belongs, and test task to which it belongs. The categories include Class I files, Class II files, and Class III files. The test data module characterizes the test data generated after engine ignition and testing. Its structure consists of a basic attribute unit, a data category unit, and a parsing result set unit. The basic attribute unit establishes a unique identifier for the data through data such as number, test code, status, and the test bench to which it belongs. The data category unit classifies the data into multiple dimensions according to process data, test data, raw data, and process data. The process data is further standardized into standard types such as P6000 (process parameter set) and T6000 (time series dataset). The parsing result set unit mainly includes the parsing results of key indicators such as pressure, temperature, propellant environmental parameters, and fuel usage parameters.

[0021] An experimental control system for a liquid rocket engine, such as Figure 1 As shown, it includes a data model management unit, a task modeling and instantiation engine unit, a resource management and monitoring unit, a plan generation and process driving unit, and a data service unit; The data model management unit includes a test item module, a test resource module, a test plan module, a test document module, and a test data module. It is used to maintain the metadata definitions and relationships of the five modules: test item module, test resource module, test plan module, test document module, and test data module.

[0022] The task modeling and instantiation engine unit is used to parse the test task after receiving the test task sent by the external system, retrieve the test item module according to the parsing result and instantiate it to obtain the test item instance. The test item instance includes the verification requirements and component parameters of the engine to be tested.

[0023] The data output of the task modeling and instantiation engine unit is connected to the data input of the resource management and monitoring unit and the plan generation and process driving unit, respectively, to send the verification requirements and component parameters to the resource management and monitoring unit and the plan generation and process driving unit, respectively.

[0024] The request output end of the task modeling and instantiation engine unit is connected to the request input end of the resource management and monitoring unit to send resource matching requests. After receiving the resource matching request, the resource management and monitoring unit determines the matching test bench resources according to the verification requirements, calls the test resource module, and instantiates the test bench resources to obtain test resource instances. The resource management and monitoring unit includes a resource matching engine module and a resource capability database module. The resource capability database module uses OWL semantics to define resource functions, performance constraints, and interface characteristics. The resource matching engine module executes a multi-dimensional resource evaluation algorithm to match test bench resources. The data input and request input terminals of the resource matching engine module are connected to the data output and request output terminals of the task modeling and instantiation engine unit, respectively, and are used to receive verification requirements and resource matching requests. The request output end of the resource matching engine module is connected to the request input end of the resource capability database module. After receiving a resource matching request, the module sends a resource query request to the resource capability database module using the received verification requirements as query conditions. The data output end of the resource capability database module is connected to the data input end of the resource matching engine module. It is used to query the test bench resources that meet the test capability requirements according to the resource query request and send them to the resource matching engine module. The resource matching engine module is used to call the test resource module after receiving the test bench resource, instantiate it according to the test bench resource, obtain the test resource instance, and monitor the real-time status of the resource.

[0025] The data output and request output terminals of the resource management and monitoring unit are connected to the data input and request input terminals of the planning generation and process driving unit, respectively, and are used to send test resource instances and task execution requests.

[0026] After receiving a task execution request, the planning generation and process driving unit determines a plan template based on component parameters and test resource instances, and retrieves the test plan item module. It then instantiates the plan template to obtain a test plan item instance, which includes a test execution logic network. The planning generation and process driving unit drives the test execution logic network to perform the test on the engine under test. The plan generation and process-driven unit includes a workflow engine module and a plan template library module; the plan template library module defines the standard processes, task dependencies and deliverables for different types of trials according to the BPMN 2.0 standard. The data input end of the workflow engine module is connected to the data output end of the task modeling and instantiation engine unit and the resource matching engine module, respectively, to receive component parameters and test resource instances; The workflow engine module's request input end and the resource matching engine module's request output end are connected to receive task execution requests; The workflow engine module's request output end and the plan template library module's request input end are connected. After receiving a task execution request, the module sends a plan query request to the plan template library module using the received component parameters and test resource instances as query conditions. The data output end of the plan template library module is connected to the data input end of the workflow engine module. It is used to query the matching plan template according to the plan query request and send it to the workflow engine module. After receiving the plan template, the workflow engine module calls the test plan item module and instantiates it according to the plan template to obtain the test execution logic network; and drives the test execution logic network to test the engine to be tested.

[0027] The data service unit includes a unified data access service, a data parsing engine, and a report generation engine, used to receive and parse test data and assist in generating test reports; it receives structured data packets through a RESTful API; the data service unit includes an information module, a data classification module, and a parsing result set module. The data classification module categorizes data into process data, commissioning data, raw data, and process data; the parsing result set module contains key performance indicators parsed from the raw data. The data input end of the data service unit is connected to the data output end of the task modeling and instantiation engine unit. After receiving the test task sent by the task modeling and instantiation engine unit, it retrieves the test document module and instantiates it according to the test task to obtain the test document instance. The plan generates a connection between the data output terminal of the process-driven unit and the data input terminal of the data service unit. This connection is used to send the received work instruction documents from the external system to the data service unit. The data service unit then retrieves and updates the test document instance based on the work instruction document. The system connects the request output of the planning and process-driven unit and the request input of the data service unit to send collection requests. After receiving the collection request, the data service unit collects data during the experiment and retrieves the experimental data module. Based on the collected data, it instantiates the experimental data module to obtain an experimental data instance. Based on the experimental data instance, the data service unit retrieves the experimental document instance and updates it.

[0028] The data service unit also includes a report generation engine module, which automatically generates a draft of the test report based on a predefined document template and through a data binding service.

[0029] This embodiment provides a test control method for a liquid rocket engine, employing the aforementioned test control system for a liquid rocket engine, such as... Figure 2 As shown, it includes the following steps: S1. After receiving the test task sent by the external system, the task modeling and instantiation engine unit extracts the data parameters of the engine to be tested from the test task, calls the test item module, and instantiates it according to the data parameters to obtain a test item instance. The test item instance includes the verification requirements and component parameters of the engine to be tested, and also includes the following processes: The task modeling and instantiation engine unit will receive the test task and send it to the data service unit. After receiving the test task, the data service unit will retrieve the test document module and instantiate it according to the test task to obtain the test document instance. The test document instance is used to associate and manage the task book, outline and final report documents related to the test task. When a test task is issued, it includes a test task description and engine data parameters. The engine data parameters are instantiated into a test item model associated with the test task, including the engine BOM structure tree, component model and technical specifications. At the same time, the test verification requirements are parsed from the test task description.

[0030] S2, the task modeling and instantiation engine unit sends component parameters to the plan generation and process driving unit, sends verification requirements to the resource management and monitoring unit, and then initiates a resource matching request to the resource management and monitoring unit.

[0031] S3. After receiving the resource matching request, the resource management and monitoring unit determines the matching test bench resource according to the verification requirements, retrieves the test resource module, instantiates the test bench resource, and sends the test resource instance to the planning generation and process driving unit, while simultaneously sending a task execution request to it. The specific process is as follows: S3.1 After receiving a resource matching request, the resource matching engine module sends a resource query request to the resource capability database module, using the received verification requirements as the query conditions. S3.2 The resource capability database module executes a matching algorithm based on the resource query request, retrieves test bench resources that meet the test capability requirements, and sends them to the resource matching engine module. S3.3 After receiving the test bench resources, the resource matching engine module calls the test resource module and instantiates the test resource module according to the test bench resources and their status data to obtain the test resource instance; the test resource instance also obtains the real-time operating status, occupancy status and health indicators of the key resources from the field monitoring system through the MQTT protocol. S3.4 The resource matching engine module sends the test resource instance to the plan generation and process driving unit, and at the same time sends a task execution request to it.

[0032] S4. After receiving the task execution request, the plan generation and process driving unit determines the plan template based on the component parameters and test resource instance, and calls the test plan item module to instantiate it according to the plan template to obtain a test plan item instance. The test plan item instance includes a test execution logic network. The plan generation and process driving unit drives the test execution logic network to test the engine under test. The test execution logic network includes the plan sequence, deliverables, time constraints, and responsibility allocation. The specific process of step S4 is as follows: S4.1 After receiving the task execution request, the workflow engine module sends a plan query request to the plan template library module using the received component parameters and test resource instances as query conditions. At the same time, the plan generation and process driving unit sends the received work instruction documents from the external system to the data service unit, and the data service unit retrieves the test document instances based on the work instruction documents to update them. S4.2 The plan template library module retrieves a matching plan template based on the plan query request and sends it to the workflow engine module; S4.3 After receiving the plan template, the workflow engine module calls the test plan item module and instantiates it according to the plan template to obtain the test execution logic network. S4.4 The workflow engine module drives the test execution logic network to test the engine under test. That is, the workflow engine deploys the test execution logic network as a runnable workflow instance, which is responsible for driving the task status transition, assigning work items to people and the system, and listening for execution feedback.

[0033] During the experiment, experimental data was collected at preset acquisition nodes. The specific steps are as follows: a. At the preset data collection node, the workflow engine module sends a data collection request to the data service unit; b. After receiving the collection request, the data service unit collects the data during the experiment, compiles the collected data into a structured dataset, and retrieves the experimental data module. Based on the structured dataset, the experimental data module is instantiated to obtain the experimental data instance, that is, the structured dataset is attached to the experimental task and plan node corresponding to the experimental data module. c. The data service unit retrieves and updates the test document instance based on the test data instance, that is, it assists in generating a structured test data report and completing the archiving based on the structured data in the attached test data module.

[0034] By constructing a structured mapping for liquid rocket engine ignition test missions, and through the collaborative modeling and dynamic association of five core modules—test resources, test documents, test plan items, test data, and test items—structured representation and systematic control of all elements of the test mission are achieved. The entire chain of the test mission, from requirement proposal, resource preparation, plan execution to data acquisition, is digitally connected and standardized. Through predefined engineering semantic relationships, a dynamic processing network with automatic data flow and collaborative state evolution is formed, thereby completing the control of the entire test process of the liquid rocket engine.

[0035] This embodiment takes the rated operating condition hot test of a liquid oxygen-kerosene engine as an example to explain the implementation process in detail: First, a hierarchical digital model of the experimental task was constructed. This model uses 'experimental task' as the top-level entity, which is linked to five core domain models, forming a complete mapping of the experimental task in the digital space. The specific experimental process is as follows: Step 1: Receiving Experimental Tasks and Instantiating Modules Step 1.1: The overall design unit issues a structured test task instruction through the interface of the digital test management platform. This instruction is encapsulated in XML format and includes the task code "RS-Test-2023-015", the engine product code, and key engine parameter information; Step 1.2: Task Modeling and Instantiation. The engine unit automatically parses the instruction. First, a test task model with the root node "RS-Test-2023-015" is created. Then, based on the engine's key parameter information, the engine instantiates a test item module under the task. This module accurately reflects the engine configuration and includes the verification requirements parsed from the test task statement: Test type = "rated operating condition test", assessment indicators = ["rated thrust 930kN", "ignition time 50s"], measurement parameters = ["combustion chamber pressure MPa", "turbo pump speed r / min", "fuel flow rate kg / s"], etc. Step 1.3: Simultaneously, the data service unit instantiates a test document model, named "RS-Test-2023-015 Task Document Set". The system uploads the issued original task book as a PDF file and associates it with this model, and pre-associates a standard Word template named "Liquid Oxygen Kerosene Engine Hot Test Data Report".

[0036] Step 2: Experimental resource matching and dynamic binding Step 2.1: The task modeling and instantiation engine unit sends a resource matching request to the resource management and monitoring unit. The request parameters include, in a structured manner, requirements such as thrust range, medium type, and number of measurement points required. Step 2.2: The resource matching engine module queries the resource capability database (which defines the capabilities of each test bench in a semantic manner). Step 2.3: Through multi-dimensional evaluation, automatically match and select "Test Stand A" and its supporting "Measurement and Control System X" and "Process System Y". Dynamically bind resource instances such as "Test Stand A" to this test task. At the same time, through the MQTT protocol, the platform begins to receive and display real-time status data of "Test Stand A", such as liquid oxygen tank pressure and kerosene supply pipeline valve position status, to ensure resource availability.

[0037] Step 3: Automatic generation and driving of the test plan Step 3.1: The plan generation and process driving unit takes the bound test item instance and test resource instance as input and calls the "Standard Process for Hot Test of Liquid Oxygen Kerosene Engine" template from the plan template library module. Step 3.2: The workflow engine module instantiates a test plan item instance, such as... Figure 4 As shown, the execution diagram contains a series of dependent planning nodes, and the execution steps include "Outline Preparation" -> "Trial Preparation" -> "Trial" -> "Product Delivery" -> "Submission of Data Report". Each node clearly defines the responsible person, estimated working hours, and deliverables (e.g., "Trial Outline" needs to be associated with the test document model). Step 3.3: The workflow engine module is deployed as an executable process. When the front-end task "Test Run Preparation" is completed, the person in charge confirms it at the test site and uploads the preparation work instructions document. The system automatically associates the report with the corresponding test document model instance and automatically triggers the task assignment of the next node "Test Run" to the responsible person.

[0038] Step 4: Experimental Data Acquisition and Structured Processing Step 4.1: When the "Test Run" node is executed, the workflow engine module sends a structured data acquisition instruction to the data service unit of the test stand. The instruction contains the test code, engine serial number and a list of specific parameters to be acquired. Step 4.2: After the test run is completed, the data service unit will upload the raw data packet via the standard API; Step 4.3: The data service unit decomposes the data according to the architecture of the experimental data model to form data categories. The data parsing engine runs automatically, parsing the key indicators such as combustion chamber pressure Pc_max=17.95MPa, turbopump speed N_steady=14865rpm, and measured thrust F_avg=937kN from the time series data. Step 4.4: The data service unit instantiates a test data instance, mounts temporary data, process data, test run data and process data, parsing result set and basic information, and precisely mounts it under the "RS-Test-2023-015" test task and the "ignition test" plan node.

[0039] Step 5: Assisting in the generation and archiving of test reports Step 5.1: After the experimental data module is instantiated, the report generation engine is triggered, and the engine calls the previously associated Word report template; Step 5.2: The data binding service automatically extracts key data, such as F_avg=937kN and Pc_max=17.95MPa, from the parsed results of the experimental data instances and fills them into predefined fields in the template. Simultaneously, it extracts assessment indicators from the experimental item instances and automatically generates comparative analysis paragraphs. Step 5.3: The data service unit generates a pre-compiled draft of the experimental data report, including data tables and graphs. Engineers only need to write the conclusions, significantly reducing report preparation time. After the report is finalized, it is reviewed and approved before being archived.

Claims

1. A test control system for a liquid rocket engine, characterized in that: It includes a task modeling and instantiation engine unit, a resource management and monitoring unit, a plan generation and process driving unit, and a data model management unit; The data model management unit includes a test item module, a test resource module, and a test plan item module; The task modeling and instantiation engine unit is used to call up the test item module and instantiate it according to the test task after receiving the test task sent by the external system, so as to obtain the test item instance. The test item instance includes the verification requirements and component parameters of the engine to be tested. The data output end of the task modeling and instantiation engine unit is connected to the data input end of the resource management and monitoring unit and the plan generation and process driving unit, respectively, and is used to send the verification requirements and component parameters to the resource management and monitoring unit and the plan generation and process driving unit, respectively. The request output end of the task modeling and instantiation engine unit is connected to the request input end of the resource management and monitoring unit to send resource matching requests. After receiving the resource matching request, the resource management and monitoring unit determines the matching test bench resources according to the verification requirements, and calls the test resource module to instantiate the test bench resources to obtain test resource instances. The data output terminal and request output terminal of the resource management and monitoring unit are respectively connected to the data input terminal and request input terminal of the planning generation and process driving unit, and are used to send test resource instances and task execution requests; After receiving a task execution request, the plan generation and process driving unit determines a plan template based on component parameters and test resource instances, and retrieves the test plan item module. It then instantiates the test plan item instance based on the plan template to obtain a test plan item instance, which includes a test execution logic network. The plan generation and process driving unit drives the test execution logic network to conduct tests on the engine under test.

2. The test control system for a liquid rocket engine according to claim 1, characterized in that: It also includes a data service unit, and the data model management unit further includes an experimental document module; The data input terminal of the data service unit is connected to the data output terminal of the task modeling and instantiation engine unit. After receiving the test task sent by the task modeling and instantiation engine unit, the test document module is retrieved and instantiated according to the test task to obtain the test document instance. The plan generation and process driving unit's data output terminal and the data service unit's data input terminal are connected. The plan generation and process driving unit's data output terminal is connected to the data service unit to send the received work instruction documents sent by the external system to the data service unit. The data service unit then retrieves and updates the test document instance based on the work instruction documents.

3. The test control system for a liquid rocket engine according to claim 2, characterized in that: The data model management unit also includes an experimental data module; The request output terminal of the plan generation and process driving unit and the request input terminal of the data service unit are connected to send collection requests; After receiving the data collection request, the data service unit collects the data during the experiment, retrieves the experimental data module, and instantiates the experimental data module based on the collected data to obtain the experimental data instance. The data service unit updates the test document instance based on the test data instance.

4. The test control system for a liquid rocket engine according to claim 3, characterized in that: The resource management and monitoring unit includes a resource matching engine module and a resource capability database module; The data input terminal and request input terminal of the resource matching engine module are connected to the data output terminal and request output terminal of the task modeling and instantiation engine unit, respectively, and are used to receive verification requirements and resource matching requests. The request output end of the resource matching engine module is connected to the request input end of the resource capability database module. After receiving a resource matching request, the module sends a resource query request to the resource capability database module using the received verification requirements as query conditions. The data output end of the resource capability database module and the data input end of the resource matching engine module are connected. The database module is used to query the test bench resources that meet the test capability requirements according to the resource query request and send them to the resource matching engine module. The resource matching engine module is used to call the test resource module after receiving the test bench resource, and instantiate it according to the test bench resource to obtain the test resource instance.

5. The test control system for a liquid rocket engine according to claim 4, characterized in that: The plan generation and process driving unit includes a workflow engine module and a plan template library module; The data input terminal of the workflow engine module is connected to the data output terminals of the task modeling and instantiation engine unit and the resource matching engine module, respectively, and is used to receive component parameters and test resource instances. The request input end of the workflow engine module and the request output end of the resource matching engine module are connected to receive task execution requests; The workflow engine module's request output end and the plan template library module's request input end are connected. After receiving a task execution request, the module sends a plan query request to the plan template library module using the received component parameters and test resource instances as query conditions. The data output end of the plan template library module is connected to the data input end of the workflow engine module, and is used to query the matching plan template according to the plan query request and send it to the workflow engine module; After receiving the plan template, the workflow engine module calls the test plan item module and instantiates it according to the plan template to obtain the test execution logic network; and drives the test execution logic network to test the engine to be tested.

6. A test control method for a liquid rocket engine, employing the test control system for a liquid rocket engine as described in any one of claims 1-5, characterized in that, Includes the following steps: S1. After receiving the test task sent by the external system, the task modeling and instantiation engine unit extracts the data parameters of the engine to be tested from the test task, calls the test item module, and instantiates it according to the data parameters to obtain the test item instance. The test item instance contains the verification requirements and component parameters of the engine to be tested. S2, the task modeling and instantiation engine unit sends component parameters to the plan generation and process driving unit, sends verification requirements to the resource management and monitoring unit, and then initiates a resource matching request to the resource management and monitoring unit; S3. After receiving the resource matching request, the resource management and monitoring unit determines the matching test bench resource according to the verification requirements, and calls the test resource module to instantiate the test bench resource. After obtaining the test resource instance, the test resource instance is sent to the planning generation and process driving unit, and a task execution request is sent to it at the same time. S4. After receiving the task execution request, the plan generation and process driving unit determines the plan template based on the component parameters and test resource instance, and calls the test plan item module to instantiate it according to the plan template to obtain the test plan item instance. The test plan item instance includes the test execution logic network. The plan generation and process driving unit drives the test execution logic network to test the engine under test.

7. The test control method for a liquid rocket engine according to claim 6, characterized in that, Step S3 is as follows: S3.1 After receiving a resource matching request, the resource matching engine module sends a resource query request to the resource capability database module, using the received verification requirements as the query conditions. S3.2 The resource capability database module queries the test bench resources that meet the test capability requirements according to the resource query request, and sends them to the resource matching engine module. S3.3 After receiving the test bench resources, the resource matching engine module calls the test resource module and instantiates them according to the test bench resources to obtain test resource instances; S3.4 The resource matching engine module sends the test resource instance to the plan generation and process driving unit, and at the same time sends a task execution request to it.

8. The test control method for a liquid rocket engine according to claim 7, characterized in that, Step S4 is as follows: S4.1 After receiving the task execution request, the workflow engine module sends a plan query request to the plan template library module using the received component parameters and test resource instances as query conditions. S4.2 The plan template library module retrieves a matching plan template based on the plan query request and sends it to the workflow engine module; S4.3 After receiving the plan template, the workflow engine module calls the test plan item module and instantiates it according to the plan template to obtain the test execution logic network. S4.4 The workflow engine module drives the test execution logic network to test the engine under test.

9. The test control method for a liquid rocket engine according to claim 8, characterized in that: Step S1 also includes the following process: The task modeling and instantiation engine unit will receive the test task and send it to the data service unit. After receiving the test task, the data service unit will retrieve the test document module and instantiate it according to the test task to obtain the test document instance. Step S4.1 also includes the following process: The workflow engine module sends the received work instruction documents from the external system to the data service unit, which then retrieves and updates the test document instance based on the work instruction documents.

10. The test control method for a liquid rocket engine according to claim 9, characterized in that: In step S4.4, during the testing of the engine under test, test data is collected at preset acquisition nodes. The specific steps are as follows: a. At the preset data collection node, the workflow engine module sends a data collection request to the data service unit; b. After receiving the data collection request, the data service unit collects the data during the experiment, retrieves the experimental data module, and instantiates the experimental data module based on the collected data to obtain the experimental data instance. c. The data service unit retrieves and updates the test document instance based on the test data instance.

Images