Engine fault model generation method, analysis method, device, equipment and medium
By constructing a diesel engine fault model using the Modelica language, the problems of single physical domain modeling and single fault type in existing technologies are solved. This enables multi-system coupling and flexible injection of fault models, improving simulation accuracy and applicability.
Patent Information
- Application Number
- CN202610098082.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-26
- Publication Date
- 2026-05-15
AI Technical Summary
Existing diesel engine fault injection simulation methods suffer from limitations such as modeling being confined to a single physical domain, single fault types, rigid injection methods, difficulty in reflecting the coupling characteristics of multiple subsystems, and lack of dynamic fault simulation and multi-fault collaborative simulation capabilities.
A normal system model of the engine is constructed using the Modelica language. A fault mode library is built based on this model. Fault injection simulation models are generated by fault selection rules, injection triggering conditions and methods, supporting multi-system coupling and fault model extension and reuse.
It realizes fault simulation of multi-system coupling, supports flexible injection of different fault types, improves simulation accuracy and reliability, and is suitable for fault simulation analysis under different working conditions and scenarios.
Smart Images
Figure CN122043992A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of engine fault detection technology, specifically to an engine fault model generation method, analysis method, device, equipment, and medium. Background Technology
[0002] Diesel engines, as the core power source of machinery, are widely used in ships, construction machinery, generator sets, and other fields, and their reliability directly affects the safe operation of equipment. Fault injection simulation is a key means to verify diesel engine fault diagnosis algorithms and optimize fault-tolerant control strategies. By simulating real faults in simulation models, it can replace costly bench fault tests.
[0003] Existing diesel engine fault injection simulation methods have the following drawbacks: 1. Modeling is limited to a single physical domain and relies heavily on dedicated simulation tools such as GT-Power and Amesim. It only considers a single subsystem of fuel supply or combustion, and the overall modeling cycle is long and the compatibility is poor. It is difficult to reflect the coupling characteristics of multiple subsystems of diesel engines, resulting in low accuracy of fault simulation. 2. The fault types are limited, mostly involving fixed parameter modifications, such as reduced injection pressure; dynamic fault simulation is lacking, such as faults that change over time or with different operating conditions; and the ability to simulate multiple faults in tandem is lacking, such as the inability to simultaneously inject into the turbocharger or EGR valve sticking. 3. The fault injection method is rigid, requiring manual modification of model code or parameters. It cannot flexibly configure fault triggering conditions and evolution rules, and does not support the extension and reuse of fault models. Summary of the Invention
[0004] This invention addresses the technical problems existing in the prior art by providing a method, analysis method, apparatus, equipment, and medium for generating engine fault models.
[0005] The technical solution of the present invention to solve the above-mentioned technical problems is as follows: A method for generating an engine fault model, comprising: A normal engine system model was constructed using the Modelica language. An engine fault mode library is constructed based on the normal system model, and the engine fault mode library includes at least one fault model corresponding to a fault type. Select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; The target fault model is integrated into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model.
[0006] The beneficial effects of this invention are as follows: Modelica, as an object-oriented, multi-physics domain unified modeling language, supports modular modeling and component reuse of complex systems. Its connector mechanism enables coupling of multiple subsystems, offering good compatibility and allowing coupling of various types of subsystems. Based on the fusion of multiple subsystems, which correspond to diverse fault types, fault injection simulation models for detecting different fault types can be generated according to requirements, supporting the extension and reuse of fault models. Furthermore, fault injection strategies can be arbitrarily preset according to testing requirements, enabling fault simulation analysis under different operating conditions and scenarios.
[0007] Furthermore, the construction of the normal engine system model based on the Modelica language includes: Based on Modelica's unified language rules, non-causal chain modeling, and component-based design, component models of each subsystem of the engine are constructed. Based on the connector interface of Modelica, the component models of each subsystem are physically coupled to obtain the normal system model.
[0008] Furthermore, the construction of the engine fault mode library based on the normal system model includes: Based on the preset fault type, adjust the component characteristic parameters of the component model in the normal system model or reconstruct the component physical model of the subsystem to obtain the fault model corresponding to the preset fault type, and construct the engine fault mode library.
[0009] Furthermore, the fault injection strategy includes fault selection rules, injection triggering conditions, and injection methods. The fault selection rules are set to select based on the fault tree. The injection triggering conditions include time-triggered and event-triggered methods. The injection methods include static injection, dynamic injection, and multi-fault collaborative injection.
[0010] Furthermore, the method includes: Fault events are generated based on each fault model in the engine fault mode library; The fault tree is generated based on the fault events; The step of selecting the target fault model corresponding to the fault type to be analyzed from the engine fault mode library includes: Click on the fault tree to select one or more target fault models corresponding to the fault type to be analyzed.
[0011] Furthermore, the step of integrating the target fault model into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model includes: Determine the target component model in the normal system model that corresponds to the target fault model; By using Modelica's conditional branching statements and redeclaration reuse, the target component model in the normal system model is replaced with the target fault model, thereby generating a fault injection simulation model.
[0012] An engine fault model analysis method is applied to a fault injection simulation model generated by any of the engine fault model generation methods described above, the method comprising: The fault injection simulation model was solved using the Modelica simulation tool Sysplorer software, and system performance parameters were collected. A fault analysis report is obtained by performing fault analysis on the engine system based on the system performance parameters.
[0013] An engine fault model generation device, comprising: The normal model building module is used to build normal system models of engines based on the Modelica language; The fault model construction module is used to construct an engine fault mode library based on the normal system model. The engine fault mode library includes at least one fault model corresponding to a fault type. The fault model selection module is used to select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; The simulation model generation module is used to integrate the target fault model into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model.
[0014] An electronic device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, the processor performing the steps of the engine fault model generation method described in any of the preceding claims.
[0015] A computer-readable storage medium storing a plurality of instructions for execution by a controller to implement the engine fault model generation method described in any of the preceding claims. Attached Figure Description
[0016] Figure 1 This is a flowchart illustrating the engine fault model generation method provided in the embodiments of this application; Figure 2 This is a flowchart illustrating the engine fault model generation method provided in the embodiments of this application; Figure 3 This is a schematic diagram of the structure of the engine fault mode library provided in the embodiments of this application; Figure 4 This is a schematic diagram of the fault injection strategy provided in the embodiments of this application; Figure 5 This is a schematic diagram illustrating how the target component model in the normal system model is replaced with the target fault model through the conditional branching statement and redeclaration reuse provided in the embodiments of this application; Figure 6 This is a schematic diagram comparing the output speed parameter results of a fault simulation in one embodiment of this application. Figure 7 This is a schematic diagram of the engine fault model generation device provided in the embodiments of this application; Figure 8 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation
[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0018] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.
[0019] In the description of this application, it should also be noted that, unless otherwise expressly specified and limited, the terms "set up," "install," "connect," and "link" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this technology based on the specific circumstances.
[0020] In the description of this application, spatial relation terms such as "below," "under," "below," "below," "above," "over," etc., are used herein to describe the relationship between one element or feature shown in the figures and other elements or features. It should be understood that, in addition to the orientation shown in the figures, spatial relation terms also include different orientations of the device in use and operation. For example, if the device in the figures is flipped, an element or feature described as "below" or "under" or "below" of other elements or features will be oriented "above" other elements or features. Therefore, the exemplary terms "below" and "under" can include both upper and lower orientations. Furthermore, the device may also include other orientations (e.g., rotated 90 degrees or other orientations), and the spatial descriptive terms used herein are interpreted accordingly.
[0021] In the description of this application, the term "for example" is used to mean "used as an example, illustration, or description." Any embodiment described as "for example" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.
[0022] Example 1 Figure 1 A schematic flowchart of an engine fault model generation method provided in this application is shown. The engine fault model generation method includes at least the following steps: S110. Constructing a normal engine system model based on the Modelica language; S120. Construct an engine fault mode library based on the normal system model, wherein the engine fault mode library includes at least one fault model corresponding to a fault type. S130. Select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; S140. Integrate the target fault model into the normal system model according to the preset fault injection strategy to generate a fault injection simulation model.
[0023] Specifically, such as Figure 2As shown, the construction of the normal system model of a diesel engine in the multi-physics domain includes the combustion subsystem, intake and exhaust turbocharging subsystem, gear transmission subsystem, control subsystem, fuel supply subsystem, lubrication and cooling subsystem, energy subsystem, and motion mechanism subsystem. Each subsystem achieves physical quantity coupling through the Modelica standard connector. The subsystem construction can rely on the Sysplorer software in the MWORKS platform to achieve the coupling of the engine system model and construct the normal system model of the engine. Furthermore, the normal system model can add or remove subsystems based on requirements.
[0024] An engine fault mode library is constructed based on a normal system model. This library includes fault models corresponding to at least one fault type. Each fault model is a faulty model corresponding to one in the normal system model, including but not limited to abnormal parameters, structural anomalies, and abnormal connectivity. For example... Figure 3 As shown, corresponding to the subsystem types included in the normal system model, the engine fault mode library includes combustion subsystem fault models, intake and exhaust turbocharging subsystem fault models, gear transmission subsystem fault models, control subsystem fault models, fuel supply subsystem fault models, lubrication and cooling subsystem fault models, energy subsystem fault models, and motion mechanism subsystem fault models.
[0025] Select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library. The fault type to be analyzed is the type of fault that the engine fault model to be generated is intended to analyze. For example, if the engine fault model is analyzing a combustion subsystem fault, then the target fault model is the combustion subsystem fault model. The target fault model can be any one or more fault models in the engine fault mode library.
[0026] The target fault model is integrated into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model. The fault injection strategy is the way the fault type corresponding to the preset target fault model occurs in the engine, and can be set according to testing needs. The generated fault injection simulation model can then be used to test the impact of the fault type to be analyzed on the engine based on the target fault model.
[0027] In this embodiment, Modelica, as an object-oriented, multi-physics domain unified modeling language, supports modular modeling and component reuse of complex systems. Its connector mechanism enables coupling of multiple subsystems, offering good compatibility and allowing coupling of various types of subsystems. Based on the fused multiple subsystems, which correspond to diverse fault types, fault injection simulation models for detecting different fault types can be generated according to requirements, supporting the extension and reuse of fault models. Furthermore, fault injection strategies can be arbitrarily preset according to testing needs, enabling fault simulation analysis under different operating conditions and scenarios.
[0028] Example 2 Step S110: Constructing a normal system model of the engine based on the Modelica language, including: constructing component models of each subsystem of the engine based on Modelica's unified language rules, non-causal chain modeling, and component-based design; and coupling the component models of each subsystem with physical quantities based on Modelica's connector interface to obtain the normal system model.
[0029] Specifically, such as Figure 2 As shown, each subsystem is further subdivided into component models. The combustion subsystem includes components such as the intake manifold, intake valves, cylinders, exhaust valves, and exhaust pipes; the intake and exhaust supercharging subsystem includes components such as the low-pressure compressor, high-pressure compressor, low-pressure turbine, high-pressure turbine, and air pipes; the gear transmission subsystem includes components such as the large gear, small gear, and bearings; the control subsystem includes components such as PID (proportion integration differentiation) control; the fuel supply subsystem includes components such as the low-pressure fuel pump, high-pressure fuel pump, filter, fuel distributor, and fuel rail; the lubrication and cooling subsystem includes components such as the interstage intercooler, high-pressure intercooler, high-temperature radiator, low-temperature radiator, and oil cooler; the energy subsystem includes components such as the generator and battery; and the motion mechanism subsystem includes components such as the crankshaft and connecting rod. It should be noted that, due to structural differences, the structural components included in each subsystem also vary.
[0030] Based on Modelica's unified language rules, non-causal chain modeling, component-based design, and connector interfaces, component models of each subsystem of the engine are constructed. The component models of each subsystem are then physically coupled using Modelica's standard connectors to obtain the normal system model.
[0031] This embodiment uses Modelica's connector mechanism to achieve coupling of multi-system and multi-component models, resulting in good compatibility.
[0032] Example 3 Step S120: Construct an engine fault mode library based on the normal system model. The engine fault mode library includes at least one fault model corresponding to a fault type, including: adjusting the component characteristic parameters in the component model of the normal system model or reconstructing the component physical model of the subsystem based on a preset fault type to obtain a fault model corresponding to the preset fault type, and constructing the engine fault mode library.
[0033] Specifically, such as Figure 3As shown, the fault models for the combustion subsystem mainly refer to fault models such as injection advance angle deviation and in-cylinder air-fuel ratio mismatch; the fault models for the intake and exhaust turbocharging subsystem mainly refer to fault models such as turbocharger efficiency decline and EGR valve opening abnormality; the fault models for the gear transmission subsystem mainly refer to fault models such as increased gear meshing clearance and decreased transmission efficiency; the fault models for the control subsystem mainly refer to fault models such as PID controller gain offset and sensor measurement deviation; the fault models for the fuel supply subsystem mainly refer to fault models such as fuel pump supply pressure mismatch and poor injector atomization; the fault models for the lubrication and cooling subsystem mainly refer to fault models such as decreased intercooler heat exchange efficiency and decreased lubricating oil pressure; the fault models for the energy subsystem mainly refer to fault models such as battery capacity decline and increased battery internal resistance; the fault models for the motion mechanism subsystem mainly refer to fault models such as increased connecting rod bearing clearance and poor piston ring sealing. The fault models are mainly obtained by modifying the component characteristic parameters of the normal system model or reconstructing the component physical model, such as modifying the valve port diameter and valve seat cone angle of the combustion subsystem or reconstructing the motion mechanism subsystem. It should be noted that, due to differences in structure and operating mode, the faults included in the fault models of each subsystem also differ.
[0034] The preset fault types are the possible fault types that may occur in the component models of each subsystem, such as parameter anomalies and structural anomalies (including anomalies in the structure itself and anomalies in the connection relationships between structures). If it is a parameter-related anomaly, the component characteristic parameters of the corresponding component model in the normal system model are adjusted; if it is a structural anomaly, the component physical model of the corresponding component model in the normal system model is reconstructed, thereby obtaining the fault model corresponding to the preset fault type, and finally constructing an engine fault mode library. For example, modifying parameters such as valve port diameter and valve seat cone angle of the combustion subsystem, or reconstructing the motion mechanism subsystem, yields the corresponding fault model.
[0035] This embodiment can expand the engine fault mode library based on structural and simulation requirements, making the generated fault injection simulation model applicable to more fault scenarios.
[0036] Example 4 The fault injection strategy includes fault selection rules, injection triggering conditions, and injection methods. The fault selection rules are set to be based on a fault tree. The injection triggering conditions include time-triggered and event-triggered methods. The injection methods include static injection, dynamic injection, and multi-fault collaborative injection. The method includes: generating fault events based on each fault model in the engine fault mode library; generating the fault tree based on the fault events; and selecting the target fault model corresponding to the fault type to be analyzed from the engine fault mode library, including: clicking on the fault tree to select one or more target fault models corresponding to the fault type to be analyzed.
[0037] Specifically, such as Figure 4As shown, the injection triggering conditions include time triggering and event triggering. Time triggering allows for setting the simulation time for fault injection, while event triggering allows for fault injection based on conditions such as engine speed or load reaching a threshold.
[0038] Injection methods include static injection, dynamic injection, and multi-fault collaborative injection. Static injection involves fixed, unmodifiable fault parameters; dynamic injection allows fault parameters to evolve linearly or non-linearly over time or under varying operating conditions; and multi-fault collaborative injection allows the system model to be injected with multiple faults simultaneously. It should be noted that the injection trigger conditions and injection methods for each fault model can be set based on the requirements of fault simulation analysis, which will not be elaborated upon in this embodiment.
[0039] like Figure 3 As shown, the fault selection rule is based on the fault tree for selection. Its operation process is as follows: generate fault events according to each fault model in the constructed engine fault mode library, generate a fault tree according to the fault events, click on the fault tree to select faults, and determine the target fault model corresponding to the fault type to be analyzed.
[0040] This embodiment allows for the arbitrary preset of fault injection strategies based on testing requirements, making fault injection flexible and controllable, and enabling fault simulation analysis under different working conditions and scenarios.
[0041] Example 5 Step S140: Integrate the target fault model into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model, including: determining the target component model in the normal system model that corresponds to the target fault model; replacing the target component model in the normal system model with the target fault model through Modelica's conditional branching statements and redeclaration reuse to generate a fault injection simulation model.
[0042] Specifically, the target component model corresponding to the target fault model in the normal system model is determined. If the target fault model is an energy subsystem fault model, then the target component model corresponding to the target fault model in the normal system model is the energy subsystem model. For example... Figure 5 As shown, Modelica uses conditional branching statements and redeclaration reuse to replace the target component model in the normal system model with the target fault model. In other words, it replaces the normal model with the same function in the normal system model with the fault model without modifying the core structure of the normal system model.
[0043] Example 6 Figure 1 A schematic flowchart of an engine fault model generation method provided in this application is shown. The engine fault model generation method includes at least the following steps: S110. Constructing a normal engine system model based on the Modelica language; S120. Construct an engine fault mode library based on the normal system model, wherein the engine fault mode library includes at least one fault model corresponding to a fault type. S130. Select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; S140. Integrate the target fault model into the normal system model according to the preset fault injection strategy to generate a fault injection simulation model. S150. Solve the fault injection simulation model using the Modelica simulation tool Sysplorer software and collect system performance parameters. S160. Based on the system performance parameters, perform fault analysis on the engine system to obtain a fault analysis report.
[0044] Specifically, after generating the fault injection simulation model, the Modelica simulation tool Sysplorer software is used to solve the model. After the simulation is completed, a fault analysis report is obtained by performing fault analysis on the engine system based on the collected system performance parameters. System performance parameters reflect engine performance and can evaluate engine performance indicators. These parameters include, but are not limited to, engine output speed, output torque, fuel consumption rate, exhaust temperature, cylinder pressure, and flow and pressure parameters of each subsystem. Based on these parameters, the impact of the fault on the engine system is analyzed, i.e., the changes in diesel engine performance caused by the input fault are analyzed, providing a basis for fault correction and completing the fault analysis. Figure 6 The figure shows a comparison of the output speed parameters from the fault simulation. As can be seen from the output speed curve in the figure, the fault speed is significantly increased compared to the normal speed after the fault parameters are injected.
[0045] This embodiment addresses the problems of traditional fault injection simulations, such as reliance on a single physical domain, incomplete fault type coverage, rigid injection methods, and difficulty in reproducing multi-fault coupled scenarios. It is compatible with the coupling characteristics of multiple engine subsystems, offering flexible and controllable fault injection, accurate and reproducible simulation results, and providing efficient simulation support for engine reliability analysis, fault diagnosis, and fault-tolerant control system design.
[0046] Figure 7 The diagram shows a structural schematic of an engine fault model generation device provided in some embodiments of this application. The device includes: The normal model building module is used to build normal system models of engines based on the Modelica language; The fault model construction module is used to construct an engine fault mode library based on the normal system model. The engine fault mode library includes at least one fault model corresponding to a fault type. The fault model selection module is used to select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; The simulation model generation module is used to integrate the target fault model into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model.
[0047] In some embodiments, the normal model building module is also used to build component models of each subsystem of the engine based on Modelica's unified language rules, non-causal chain modeling, and component-based design; and to couple the component models of each subsystem with physical quantities based on Modelica's connector interface to obtain the normal system model.
[0048] The fault model construction module is also used to adjust the component characteristic parameters of the component model in the normal system model or reconstruct the component physical model of the subsystem based on the preset fault type, so as to obtain the fault model corresponding to the preset fault type and construct the engine fault mode library.
[0049] Furthermore, the fault injection strategy includes fault selection rules, injection triggering conditions, and injection methods. The fault selection rules are set to select based on the fault tree. The injection triggering conditions include time-triggered and event-triggered methods. The injection methods include static injection, dynamic injection, and multi-fault collaborative injection.
[0050] Furthermore, the fault model selection module is also used to generate fault events based on each fault model in the engine fault mode library; generate the fault tree based on the fault events; and select one or more target fault models corresponding to the fault type to be analyzed by clicking on the fault tree.
[0051] Furthermore, the simulation model generation module is also used to determine the target component model in the normal system model that corresponds to the target fault model; and to replace the target component model in the normal system model with the target fault model through Modelica's conditional branching statements and redeclaration reuse, thereby generating a fault injection simulation model.
[0052] In some embodiments of this application, the engine fault model generation device can be implemented as a computer program, and the computer program can be implemented in, for example... Figure 8 The device operates on the electronic device shown. The memory of the electronic device can store various program modules that make up the engine fault model generation device. The computer program composed of these program modules causes the processor to execute the steps in the image detection methods of the various embodiments of this application described in this specification.
[0053] The electronic device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external electronic devices via a network connection. When the computer program is executed by the processor, it implements an engine fault model generation method.
[0054] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.
[0055] Accordingly, this application also provides an electronic device, which can be a terminal, such as a smartphone, tablet computer, laptop computer, touch screen, game console, personal computer (PC), personal digital assistant (PDA), or other terminal device. Alternatively, the electronic device can be a server.
[0056] The electronic device includes one or more processors; a memory; and one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processors of the steps of the multi-sensor-based monitoring method described above. The steps of the multi-sensor-based monitoring method described here can be steps from the engine fault model generation method of the various embodiments described above.
[0057] In some embodiments of this application, a computer-readable storage medium is provided, storing a computer program that is loaded by a processor, causing the processor to execute the steps of the engine fault model generation method described above. The steps of the engine fault model generation method here can be steps from the multi-sensor-based monitoring methods described in the various embodiments above.
[0058] While embodiments or examples of this disclosure have been described with reference to the accompanying drawings, it should be understood that the above embodiments are merely exemplary embodiments or examples, and the scope of the invention is not limited by these embodiments or examples, but only by the granted claims and their equivalents. Various elements in the embodiments or examples may be omitted or replaced by their equivalents. Furthermore, the steps may be performed in a different order than that described in this disclosure. Further, various elements in the embodiments or examples may be combined in various ways. Importantly, as the technology evolves, many elements described herein can be replaced by equivalents that appear after this disclosure.
Claims
1. A method for generating an engine fault model, characterized in that, include: A normal engine system model was constructed using the Modelica language. An engine fault mode library is constructed based on the normal system model, and the engine fault mode library includes at least one fault model corresponding to a fault type. Select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; The target fault model is integrated into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model.
2. The engine fault model generation method according to claim 1, characterized in that, The construction of the normal engine system model based on the Modelica language includes: Based on Modelica's unified language rules, non-causal chain modeling, and component-based design, component models of each subsystem of the engine are constructed. Based on the connector interface of Modelica, the component models of each subsystem are physically coupled to obtain the normal system model.
3. The engine fault model generation method according to claim 2, characterized in that, The construction of the engine fault mode library based on the normal system model includes: Based on the preset fault type, adjust the component characteristic parameters in the component model of the normal system model or reconstruct the component physical model of the subsystem to obtain the fault model corresponding to the preset fault type, and construct the engine fault mode library.
4. The engine fault model generation method according to claim 1, characterized in that, The fault injection strategy includes fault selection rules, injection triggering conditions, and injection methods. The fault selection rules are set to select based on the fault tree. The injection triggering conditions include time-triggered and event-triggered. The injection methods include static injection, dynamic injection, and multi-fault collaborative injection.
5. The engine fault model generation method according to claim 4, characterized in that, The method includes: Fault events are generated based on each fault model in the engine fault mode library; The fault tree is generated based on the fault events; The step of selecting the target fault model corresponding to the fault type to be analyzed from the engine fault mode library includes: Click on the fault tree to select one or more target fault models corresponding to the fault type to be analyzed.
6. The engine fault model generation method according to claim 1, characterized in that, The step of integrating the target fault model into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model includes: Determine the target component model in the normal system model that corresponds to the target fault model; By using Modelica's conditional branching statements and redeclaration reuse, the target component model in the normal system model is replaced with the target fault model, thereby generating a fault injection simulation model.
7. An engine fault model analysis method, characterized in that, A fault injection simulation model is applied to the engine fault model generation method according to any one of claims 1 to 6, the method comprising: The fault injection simulation model was solved using the Modelica simulation tool Sysplorer software, and system performance parameters were collected. A fault analysis report is obtained by performing fault analysis on the engine system based on the system performance parameters.
8. An engine fault model generation device, characterized in that, include: The normal model building module is used to build normal system models of engines based on the Modelica language; The fault model construction module is used to construct an engine fault mode library based on the normal system model. The engine fault mode library includes at least one fault model corresponding to a fault type. The fault model selection module is used to select the target fault model corresponding to the fault type to be analyzed from the engine fault mode library; The simulation model generation module is used to integrate the target fault model into the normal system model according to a preset fault injection strategy to generate a fault injection simulation model.
9. An electronic device, characterized in that, The electronic device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the steps in the engine fault model generation method according to any one of claims 1 to 7.
10. A computer-readable storage medium storing a plurality of instructions, characterized in that, The instructions are for execution by the controller to implement the engine fault model generation method as described in any one of claims 1 to 7.