Aircraft fault diagnosis method, system and equipment

Abstract

The invention relates to the technical field of fault diagnosis, and discloses an aircraft fault diagnosis method, system and device, and the method comprises the steps: obtaining a fault tree model and a fault code knowledge base of a target aircraft; the fault tree model represents the logic relationship of each fault in the airborne equipment of the aircraft; the fault code knowledge base represents each piece of fault code information in the aircraft airborne equipment; based on the fault tree model and the fault code knowledge base of the target aircraft, performing fault simulation on airborne equipment of the target aircraft according to layers to obtain a fault simulation result; the layers comprise at least one of an application layer, a physical layer, a protocol layer and an electrical layer; and performing fault real-time positioning and diagnosis based on the fault simulation result to obtain a fault diagnosis result. According to the invention, comprehensive and efficient aircraft fault simulation diagnosis and knowledge base management functions are provided, and the safety and reliability of the aircraft are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of fault diagnosis, and in particular to an aircraft fault diagnosis method, system and equipment. Background Art

[0002] With the continuous development of the global aviation industry, the safety and reliability of aircraft have become the focus of the industry. As an important means to ensure the safe operation of aircraft, the research and development of aircraft fault diagnosis technology is of great significance. Through real-time monitoring, detection and analysis of the aircraft's operating status, this technology can timely detect and locate faults, thereby effectively preventing accidents and extending the service life of the aircraft.

[0003] Traditional airborne system fault diagnosis research systems have problems such as few fault types, heavy reliance on hardware and mechanical equipment to cause faults, and cumbersome operations; fault tests are difficult to carry out and are time-consuming and labor-intensive, fault diagnosis results are difficult to manage, and diagnostic equipment has low versatility. In addition, during the operation of the aircraft, any minor fault may expand rapidly and lead to serious consequences. Traditional fault signals are difficult to simulate and quickly inject into the airborne system. Summary of the invention

[0004] In view of this, the present invention provides an aircraft fault diagnosis method, system and device to provide comprehensive and efficient aircraft fault simulation diagnosis and knowledge base management functions, thereby improving the safety and reliability of the aircraft.

[0005] In a first aspect, the present invention provides an aircraft fault diagnosis method, the method comprising: obtaining a fault tree model and a fault code knowledge base of a target aircraft; the fault tree model characterizes the logical relationship between each fault in the aircraft's onboard equipment; the fault code knowledge base characterizes the information of each fault code in the aircraft's onboard equipment; based on the fault tree model and the fault code knowledge base of the target aircraft, performing fault simulation on the target aircraft's onboard equipment in a hierarchical manner to obtain a fault simulation result; the hierarchical manner includes at least one of an application layer, a physical layer, a protocol layer and an electrical layer; based on the fault simulation result, performing real-time fault location and diagnosis to obtain a fault diagnosis result.

[0006] In an optional implementation, based on the fault tree model and fault code knowledge base of the target aircraft, fault simulation is performed on the target aircraft's onboard equipment in a hierarchical manner. After the fault simulation results are obtained, it also includes: injecting the fault simulation results into a fault diagnosis prototype through hardware interface resources and hardware fault injection adapter equipment; the fault diagnosis prototype is used to simulate the aircraft's onboard equipment.

[0007] In an optional implementation, the method further includes: updating the fault tree model and the fault code knowledge base based on the fault diagnosis result.

[0008] In an optional embodiment, the steps of performing fault simulation by layer include: at the application layer, establishing an application layer fault model and performing fault simulation; the application layer fault model includes combined navigation sensor failure, flight control system failure and servo failure; at the physical layer, establishing a physical layer fault model and performing fault simulation; the physical layer fault model includes signal short circuit to power supply, signal short circuit to ground and open circuit; at the protocol layer, establishing a protocol layer fault model and performing fault simulation; the protocol layer fault model includes serial communication bus electrical failure; at the electrical layer, establishing an electrical layer fault model and performing fault simulation; the electrical layer fault model includes power supply abnormality and signal fluctuation.

[0009] In an optional implementation, the fault diagnosis result includes at least one of a fault code, a fault location, a fault occurrence time, a fault type, and a fault handling measure.

[0010] In an optional embodiment, establishing a fault tree model for an aircraft includes: determining top events, intermediate events, and basic faults; the top event is a major fault event of the aircraft's onboard equipment; the intermediate event is a specific fault event that causes the top event; the basic fault is a basic fault that causes the intermediate event; and generating a fault tree model based on the logical relationship between the top event, the intermediate event, and the basic fault.

[0011] In a second aspect, the present invention provides an aircraft fault diagnosis system, the system comprising: a fault expert knowledge base module, used to obtain a fault tree model and a fault code knowledge base of a target aircraft; the fault tree model characterizes the logical relationship between each fault in the aircraft's onboard equipment; the fault code knowledge base characterizes the information of each fault code in the aircraft's onboard equipment; a fault simulation and injection module, used to perform fault simulation on the target aircraft's onboard equipment in a hierarchical manner based on the fault tree model and the fault code knowledge base of the target aircraft, and obtain fault simulation results; the hierarchical layers include at least one of an application layer, a physical layer, a protocol layer, and an electrical layer; a fault diagnosis prototype module, used to perform real-time fault location and diagnosis based on the fault simulation results, and obtain fault diagnosis results.

[0012] In an optional implementation, the fault simulation and injection module is also used to inject the fault simulation results into the fault diagnosis prototype through hardware interface resources and hardware fault injection adapter equipment; the fault diagnosis prototype is used to simulate aircraft onboard equipment.

[0013] In an optional implementation, the fault expert knowledge base module is further used to update the fault tree model and the fault code knowledge base based on the fault diagnosis result.

[0014] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to execute an aircraft fault diagnosis method according to the first aspect or any corresponding embodiment thereof.

[0015] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute an aircraft fault diagnosis method according to the first aspect or any corresponding embodiment thereof.

[0016] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute an aircraft fault diagnosis method according to the first aspect or any corresponding embodiment thereof.

[0017] The technical solution provided by the present invention may include the following beneficial effects:

[0018] The fault tree model and fault code knowledge base provide the logical relationship and code information of the faults in the aircraft's onboard equipment, which are the basis for subsequent fault simulation. Through the fault simulation of the application layer, physical layer, protocol layer and electrical layer, it is possible to comprehensively understand the various fault conditions that the aircraft's onboard equipment may encounter during actual operation. Based on the fault simulation results, combined with the fault diagnosis model and positioning algorithm, the fault can be quickly and accurately located and diagnosed. The above scheme provides comprehensive and efficient aircraft fault simulation diagnosis and knowledge base management functions by obtaining the fault tree model and fault code knowledge base, performing multi-level fault simulation, and real-time fault location and diagnosis, thereby improving the safety and reliability of the aircraft. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 is a flow chart of an aircraft fault diagnosis method according to an embodiment of the present invention;

[0021] Figure 2 is a schematic diagram of aircraft fault diagnosis according to an embodiment of the present invention;

[0022] Figure 3 is a structural block diagram of an aircraft fault diagnosis device according to an embodiment of the present invention;

[0023] Figure 4 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0025] According to an embodiment of the present invention, an embodiment of an aircraft fault diagnosis method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] In this embodiment, a method for diagnosing aircraft faults is provided. Figure 1 is a flow chart of an aircraft fault diagnosis method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0027] Step S101, obtaining a fault tree model and a fault code knowledge base of a target aircraft; the fault tree model represents the logical relationship of each fault in the aircraft's onboard equipment; the fault code knowledge base represents the information of each fault code in the aircraft's onboard equipment.

[0028] Fault tree is a method for identifying and analyzing aircraft onboard equipment faults. It can realize fault prediction and fault cause analysis, and can display fault logical relationships through graphics. The fault tree structure is divided into a primitive fault tree and a logical calculation fault tree. The primitive fault tree is used for fault tree model editing and fault tree engineering file management. The logical calculation fault tree is generated by the primitive fault tree and is mainly used for fault tree analysis and detection. It has the functions of analysis, modeling, configuration of basic event parameters, export of model tree images and data, engineering file management, and design of workflow. In the present invention, the fault tree model connects various basic fault events through logic gates (such as AND gates, OR gates, etc.) to form a tree structure, showing the cause-effect relationship between each fault event. The fault tree model provides fault logical relationships for subsequent fault simulations.

[0029] The fault code knowledge base is a database that stores various fault codes and their corresponding fault information in aircraft onboard equipment. According to the fault code knowledge base, fault scenarios, fault location judgments, and possible fault states can be queried. The fault code knowledge base provides fault code information for subsequent fault simulations.

[0030] Step S102, based on the fault tree model and fault code knowledge base of the target aircraft, fault simulation is performed on the target aircraft's onboard equipment in layers to obtain fault simulation results; the layers include at least one of the application layer, physical layer, protocol layer and electrical layer.

[0031] Fault simulation is to simulate various possible fault scenarios of aircraft onboard equipment to predict and evaluate the impact of these faults on equipment performance. Typical fault simulation based on aircraft mainly includes two types of faults. One is the component function fault model integrated in the flight model library, which is implemented based on the model fault data simulation and provides application layer fault simulation; the other is the fault of program-controlled hardware, which is implemented based on the control of hardware equipment, including protocol layer fault, electrical layer fault and physical layer fault. Each layer represents different components and functional characteristics of the equipment. Among them, the application layer is the level in the software architecture that directly interacts with the user, responsible for processing various application functions and data processing directly related to the flight mission; the physical layer is the hardware equipment part of the aircraft, responsible for the physical connection and transmission of hardware interfaces, electrical signals, etc.; the protocol layer is responsible for communication and data exchange between devices; the electrical layer is responsible for the transmission and distribution of electrical signals. The fault simulation results obtained by fault simulation according to the level can cover the typical faults of the aircraft during the test mission or flight process, and provide support for the real-time location and diagnosis of subsequent faults.

[0032] Step S103: Based on the fault simulation result, real-time fault location and diagnosis are performed to obtain a fault diagnosis result.

[0033] The fault diagnosis model is used to solve and analyze the fault simulation results, identify the fault type, and locate the fault source. The fault diagnosis model is a mathematical model built based on a certain algorithm or rule, which is used to monitor and diagnose the fault of its onboard equipment in real time during the operation of the aircraft. After real-time positioning and diagnosis, the fault diagnosis results are obtained. Based on the fault diagnosis results, a detailed fault report can be generated to perform fault analysis and system optimization on the aircraft's onboard equipment. At the same time, the fault diagnosis model runs in a real-time environment and can quickly respond to and handle faults in real time, so that when a fault occurs, measures can be taken quickly without affecting the flight results.

[0034] In summary, by obtaining fault tree models and fault code knowledge bases, conducting multi-level fault simulations, and real-time fault location and diagnosis, a comprehensive and efficient aircraft fault simulation diagnosis and knowledge base management function is provided, thereby improving the safety and reliability of the aircraft.

[0035] In an optional implementation, the fault simulation results are injected into a fault diagnosis prototype through hardware interface resources and a hardware fault injection adapter; the fault diagnosis prototype is used to simulate aircraft onboard equipment.

[0036] Hardware interface resources are various physical interfaces for connection and communication, which are used for data transmission and signal exchange between different hardware devices. In the present invention, hardware interface resources include serial communication interface, Ethernet interface, analog signal interface, and digital signal interface. The hardware interface enables the fault simulation device to be connected to the fault diagnosis prototype and other hardware components. The hardware fault injection adapter is used to convert the fault simulation results into a form suitable for reception by the fault diagnosis prototype, including signal conditioning circuits, interface conversion circuits, and control logic. By simulating fault signals through real hardware interfaces and fault injection devices, the authenticity of the fault simulation is improved, making the test results more reliable.

[0037] The fault diagnosis prototype is a device that simulates the functions and interfaces of aircraft onboard equipment. It has a hardware and software architecture similar to that of real airborne equipment, can simulate the actual operation of the aircraft in the ground environment, and receive fault injection signals including fault simulation results. By running the fault diagnosis model, the fault diagnosis prototype can locate and diagnose the fault simulation results in real time. The fault diagnosis prototype supports the rapid verification of the design of fault diagnosis algorithms in the early stage of design, and realizes the verification of fault diagnosis and fault handling functions. Optionally, it also supports the replacement of real airborne fault diagnosis equipment to the test environment at a later stage, and supports the verification of the ability of airborne fault diagnosis equipment to quickly diagnose and handle faults.

[0038] The fault diagnosis prototype provides an operating environment for fault testing and a wealth of fault test application scenarios. It fully verifies the fault diagnosis function of the airborne system through test design on the ground, improves the system's ability to quickly diagnose and respond to faults, and enhances the safety of flight design.

[0039] In an optional implementation, an aircraft fault diagnosis method further includes:

[0040] Based on the fault diagnosis results, the fault tree model and fault code knowledge base are updated.

[0041] When the fault diagnosis results indicate a new fault type or fault path, they are fed back to the fault tree model to update the fault logic relationship. Based on the fault diagnosis results, new fault codes and their corresponding fault information are obtained and added to the fault code knowledge base. By continuously updating the fault tree model and fault code knowledge base, the fault diagnosis performance can be improved, and various faults can be located and diagnosed more accurately.

[0042] In an optional implementation, the fault simulation by level in the above step S102 includes:

[0043] Step a11, at the application layer, establish an application layer fault model and perform fault simulation; the application layer fault model includes a combined navigation sensor fault, a flight control system fault, and a steering gear fault.

[0044] The application layer fault model simulates typical fault conditions in the upper layer applications of the aircraft, including integrated navigation sensor failure, flight control system failure, and servo failure. Application layer failures can reflect software or configuration problems that may occur during actual flight.

[0045] Specifically, application layer failures are mainly realized through fault simulation models, and a typical aircraft application layer failure model library is provided, which mainly includes a combination of navigation sensor failures, flight control system failures, and servo failures, etc., which are integrated into the Matlab / Simulink development environment.

[0046] The fault model library includes the fault model library of combined navigation sensor fault, flight control system fault and servo fault, as follows:

[0047] 1) Combined navigation fault model library: including GPS navigation fault model and inertial navigation fault model.

[0048] 2) Flight control system fault model library: including control unit fault model, power supply fault model and communication fault model.

[0049] 3) Servo fault model library: including communication fault model, motor fault model, position sensor fault model and rudder mechanical fault model.

[0050] It supports user-defined application fault model extension and loads it into the application layer fault model library. It can be easily dragged into the test model as a library module to realize the injection of customized model data.

[0051] Step a12, at the physical layer, establish a physical layer fault model and perform fault simulation; the physical layer fault model includes signal short circuit to power supply, signal short circuit to ground, and open circuit.

[0052] The physical layer fault model simulates the fault conditions in the physical connection and transmission of hardware interfaces and electrical signals, including signal short circuit to power supply, signal short circuit to ground, and open circuit faults. Physical layer faults directly affect the physical transmission of electrical signals. Use physical layer fault injection equipment to simulate these physical layer faults through hardware means (such as physical connection errors, short circuit boards, etc.), or use control software to simulate short circuit, open circuit and other conditions.

[0053] Step a13, at the protocol layer, a protocol layer fault model is established and a fault simulation is performed; the protocol layer fault model includes an electrical fault of the serial communication bus.

[0054] The protocol layer fault model simulates faults that occur during communication and data exchange, including electrical faults on the serial communication bus (such as voltage deviation, improper common-mode voltage regulation, signal delay, and data bit inversion). These faults affect the accuracy and integrity of data transmission. Protocol layer faults affect the accuracy and integrity of data transmission. Use electrical layer / protocol layer fault injection equipment to simulate protocol layer faults by modifying communication signals or protocol parameters.

[0055] Step a14, at the electrical layer, establish an electrical layer fault model and perform fault simulation; the electrical layer fault model includes power supply anomalies and signal fluctuations.

[0056] The electrical layer fault model simulates power supply and signal transmission problems in the electrical system, including power supply anomalies (such as voltage instability, power failure) and signal fluctuations (such as noise interference, signal attenuation). Electrical layer faults affect the stability and reliability of the electrical system. Power supply anomalies are simulated by electrical test equipment (such as power supplies, signal generators), and signal fluctuations are simulated using signal analyzers or oscilloscopes.

[0057] In addition, the real-time hardware I / O interface driver mainly provides real-time simulation of hardware fault signals, provides hardware interface board drivers, and realizes fault injection control functions for airborne devices, and realizes driver management and real-time calling functions of real-time fault injection hardware interface resources.

[0058] Optionally, the fault diagnosis result includes at least one of a fault code, a fault location, a fault occurrence time, a fault type, and a fault handling measure.

[0059] A fault code is a code or number that uniquely identifies a specific fault. Each fault is assigned a code. The fault location refers to the specific device or system of the aircraft where the fault occurs. For example, the fault occurs in the integrated navigation system, flight control system, servo, or other onboard equipment. The fault occurrence time records the specific time point when the fault was first detected and is used to determine the operating stage when the fault occurred. The fault type characterizes the nature of the fault, such as hardware failure, software failure, and configuration error. Fault handling measures are countermeasures for the fault, including replacing the faulty component, reconfiguring system parameters, and updating software or firmware. The fault diagnosis results provide comprehensive information about the fault, which helps to quickly locate the fault and take appropriate handling measures.

[0060] In an optional implementation, obtaining the fault tree model of the aircraft in the above step S101 includes:

[0061] Step b11, determine the top event, intermediate event and basic fault; the top event is the main fault event of the aircraft onboard equipment; the intermediate event is the specific fault event that causes the top event; the basic fault is the basic fault that causes the intermediate event.

[0062] The top event is the main fault event of the aircraft's onboard equipment, such as failure of the aircraft's onboard system, the aircraft's non-response to manipulation, etc., and is the target of the entire fault tree analysis. The intermediate event is the specific fault event that causes the top event to occur. In the fault tree, they are located between the top event and the basic fault, serving as a bridge connecting the two. The intermediate event may be a failure of one or more subsystems, such as "flight control computer failure" or "sensor data abnormality". The intermediate events of the present invention include combined navigation sensor failure, flight control computer failure, and steering gear failure failure. In the aircraft onboard system failure fault tree model, rectangular modules are used to define intermediate events, and the steering gear failure model consists of four basic intermediate faults, namely communication failure, motor failure, position sensor failure, and control surface mechanical failure. The basic fault is the lowest and most basic cause of the intermediate event, usually an indivisible hardware or software fault, such as "power module damage", "software logic error", etc. The basic fault is located at the bottom of the fault tree and can be composed of a single or multiple basic faults. In the aircraft onboard system failure fault tree model, a circular module is used to define the basic fault, and the intermediate event occurs through logic gate operations. Basic fault composition diagram of motor fault. The basic fault of motor fault is composed of control unit, power supply and mechanical fault. Users can customize the probability of fault occurrence in the circular basic fault module. All basic faults conform to the exponential distribution probability.

[0063] Step b12, generating a fault tree model according to the logical relationship between the top event, the intermediate event and the basic fault.

[0064] After determining the top event, intermediate event, and basic fault, a fault tree model is generated based on the logical relationship between them. In the fault tree, different events are connected through logic gates (such as AND gates and OR gates) to express the logical relationship between events. For example, if two intermediate events must occur at the same time to cause the top event to occur, then the two intermediate events and the top event should be connected through an AND gate.

[0065] Specifically, the design process of the fault tree model is:

[0066] (1) Determine the top event;

[0067] (2) Identify intermediate events;

[0068] (3) Determine the basic fault;

[0069] (4) Draw a tree diagram: Use FTA software to design the logical relationship in the fault tree. For example, use an AND gate to indicate that multiple basic events must occur simultaneously to cause the top event, and use an OR gate to indicate that any event can cause the top event. Connect each basic event with an appropriate logic gate to reflect the fault propagation path in the system.

[0070] (5) Results and Analysis: Run FTA to calculate and analyze the results to determine the probability of the top event and the main fault path that leads to the top event. The probability of the top event is calculated by combining the probability and the truth table of the logic gate. It can help users determine the overall reliability of the aircraft's onboard system. Based on the analysis results, the reliability of the aircraft's onboard system is evaluated, and then improvement suggestions are made to take measures to reduce the probability of failure and enhance the system's fault tolerance.

[0071] In the implementation of the present invention, Figure 2 As shown, the present invention consists of a fault simulation and injection part, a fault diagnosis prototype part, and a fault expert knowledge base part. The fault expert knowledge base includes a typical fault tree and fault code knowledge base of an aircraft. Based on the method of identifying and analyzing the faults of the aircraft's onboard systems, it provides common fault types and fault occurrence probabilities, and provides a reference for fault injection. The fault expert knowledge base has the functions of fault warning display and expert knowledge base driving and management. It analyzes and predicts the faulty system in the test, has the function of fault tree analysis, can realize fault prediction and cause analysis, and comprehensively utilizes test data and system model knowledge to complete the health management of the aircraft.

[0072] The fault simulation and injection part provides fault simulation of the aircraft during the test or flight. It can provide multi-layer fault simulation such as application layer, protocol layer, physical layer, electrical layer, etc. based on the fault tree analysis fault input, and realize the fault injection function of the airborne equipment through hardware interface resources and hardware fault injection adapter equipment; the fault diagnosis subsystem provides a fault diagnosis prototype machine to simulate the fault location and diagnosis processing function of the airborne equipment. The fault diagnosis target machine loads the fault diagnosis model, receives the fault injection signal through the hardware interface, locates and diagnoses, and outputs the location and diagnosis results. At the same time, the fault is processed through the fault tolerance control and fault isolation model. After the fault is reported, the fault result does not affect the flight test status. The fault diagnosis results can be corrected, enriched and improved through the fault test and diagnosis process. The fault diagnosis knowledge base.

[0073] Specifically, the fault diagnosis model includes the fault location and diagnosis model of the faulty integrated navigation system (PHM_Integrated_Nav_sys), the flight control system fault location and diagnosis PHM_FCM, and the actuator cabinet fault location and diagnosis model (PHM_Actuator). The input of the model is the integrated navigation sensor bus signal, the flight control system FCM bus signal, and the servo bus signal. The fault diagnosis model can output the diagnosis results such as the inertial navigation IMU fault code, GPS navigation fault code, flight control FCM fault code, and actuator Actuation fault code through the positioning diagnosis logic diagnosis according to the application layer fault injection, protocol layer fault injection, and physical layer fault injection. The fault diagnosis model provides fault diagnosis and location functions, as well as fault-tolerant control and fault handling functions. In the flight test, the fault result reporting and fault handling are achieved, and the model outputs normal flight test data, and the fault does not affect the flight status as much as possible.

[0074] The present invention designs an aircraft application layer fault model under the MATLAB / Simulink environment, and automatically generates simulation target code, provides fault injection through a fault real-time simulator, and provides hardware layer fault simulation and injection through a physical layer fault injection device and an electrical / protocol layer fault injection device, and provides the fault to a fault diagnosis prototype through a hardware fault injection adapter. During the fault simulation process, the fault diagnosis prototype simulates the aircraft flight process and a typical fault diagnosis mode, performs real-time fault reasoning diagnosis, positioning and fault-tolerant control, and finally feeds back the diagnosis result to a fault expert diagnosis subsystem, forming a real-time closed-loop fault diagnosis test environment.

[0075] The fault real-time simulator is a real-time simulator that runs a real-time operating system and supports real-time operation of application fault models and fault data stimulation. It also provides fault hardware interfaces, real-time stimulation of analog quantities, discrete quantities, serial ports, CAN channels and other hardware interfaces, supports stimulation of test faults from the hardware layer, and provides injection of fault signals.

[0076] The fault diagnosis prototype subsystem mainly realizes the fault diagnosis prototype simulation function of the aircraft onboard equipment, runs the real-time simulation engine, is configured with the same physical hardware interface as the onboard equipment, has the functions of the onboard equipment and the fault diagnosis, prediction and positioning functions, and predicts and diagnoses the input faults, outputs the fault diagnosis results, and supports the storage and management of the fault diagnosis results. The hardware implementation is a real-time simulation computer, which realizes the fault diagnosis verification prototype target machine platform, runs the real-time operating system, and mainly completes the following functions:

[0077] a) Real-time simulation engine: It provides a real-time operation platform for the inference engine and fault-tolerant flight control software, can solve the fault diagnosis inference engine algorithm model in real time, and has the functions of decision control computer prototype start-stop control, data communication service, data storage service and algorithm scheduling service management;

[0078] b) The configuration provides the same hardware interface as the airborne equipment, and has the bus network communication and non-bus signal acquisition and control capabilities of the fault diagnosis verification prototype. It combines the various sensor variable information obtained by the system, and performs real-time calculations on the inference machine based on the input quantity, and outputs warning information and fault diagnosis results.

[0079] The present invention supports the access of real aircraft airborne equipment to replace the fault diagnosis prototype, and enriches and improves the fault tree model and fault diagnosis code table through real airborne fault tests and location diagnosis results. During the test, the hardware fault injection adapter unit supports the access of airborne equipment, provides multi-scenario fault simulation and injection to real airborne equipment, and further enriches and improves the fault expert knowledge base part of the present invention through the fault location and diagnosis test of real equipment.

[0080] The present invention provides a variety of fault diagnosis test application scenarios. System fault detection and fault diagnosis function testing are achieved through application layer, protocol layer and physical layer fault injection tests. For example, fault tests are mainly divided into the following test scenarios:

[0081] 1) Application layer fault injection: By stimulating the application layer fault model to simulate the control surface stuck fault injection, based on the fault diagnosis test software to inject faults, you can set the aileron, elevator or rudder stuck fault injection. The fault diagnosis prototype loads and runs the fault diagnosis model. After the fault diagnosis model detects the fault, it outputs the fault code 0xA1510000, and the corresponding fault is the elevator stuck. At the same time, the fault diagnosis model performs fault processing. The output value of the rudder deflection in the model remains unchanged after the jitter, which does not affect the flight test.

[0082] 2) Protocol layer fault injection: The protocol / electrical layer fault injection equipment is used to simulate the aircraft inertial navigation communication disconnection fault, and the fault diagnosis prototype runs the diagnostic model for fault detection and diagnosis. When the RS422 fault injection box does not inject a fault, the model operates normally; the RS422 fault is injected through the fault diagnosis test software, and the fault diagnosis model detects the fault and outputs the fault code 0xA2112000 and 0xA2111000. The corresponding faults are accelerometer 1 failure and gyroscope 1 failure. The fault diagnosis prototype model performs fault processing, and the output values ​​of flight parameters such as roll angle, yaw angle, pitch angle and north east sky speed remain unchanged, which does not affect the flight test.

[0083] 3) Physical layer fault injection, simulating physical layer fault injection through three scenarios:

[0084] a) GPS fault test: simulate GPS signal through analog output DA signal, simulate latitude fault injection through physical layer fault injection box, and realize fault detection and fault diagnosis through fault diagnosis prototype. When no fault is injected, the model outputs normally; inject latitude signal fault through fault diagnosis test software, and after the fault diagnosis model detects the fault, it outputs fault code 0xA2122200, which corresponds to GPS signal fault. The fault diagnosis prototype model performs fault processing, and the output values ​​of flight altitude, latitude, longitude and other parameters remain unchanged, which does not affect the flight test.

[0085] b) Flight control system power supply fault test: simulate the flight control system power supply through analog output DA signal, simulate the flight control computer power supply circuit fault injection through the physical layer fault injection box, and realize fault detection and fault diagnosis through the fault diagnosis prototype. When no fault is injected, the model outputs normally; inject FCM power supply fault through the fault diagnosis test software. After the fault diagnosis model detects the fault, it outputs the fault code 0xA3130000, which corresponds to the fault FCM power supply fault. The fault diagnosis prototype model performs fault processing without affecting the comprehensive voting of the flight control system.

[0086] c) Atmospheric data sensor fault test: The state detection signal of the atmospheric data sensor is simulated through the discrete signal DO, the sensor state fault injection scenario is simulated through the physical layer fault injection box, and the fault detection and fault diagnosis are realized through the fault diagnosis prototype. When no fault is injected, the model outputs normally; the atmospheric sensor fault is injected through the fault diagnosis test software, and the fault diagnosis model outputs the fault code 0xA4100000 after detecting the fault, which corresponds to the fault of the atmospheric sensor 1. The fault diagnosis prototype model performs fault processing without affecting the comprehensive collection of atmospheric data and the flight status.

[0087] In this embodiment, an aircraft fault diagnosis system is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0088] This embodiment provides an aircraft fault diagnosis system, such as Figure 3 As shown, including:

[0089] The fault expert knowledge base module 301 is used to obtain the fault tree model and fault code knowledge base of the target aircraft; the fault tree model represents the logical relationship of each fault in the aircraft's onboard equipment; the fault code knowledge base represents the information of each fault code in the aircraft's onboard equipment.

[0090] The fault simulation and injection module 302 is used to perform fault simulation on the target aircraft's onboard equipment in layers based on the target aircraft's fault tree model and fault code knowledge base to obtain fault simulation results; the layers include at least one of the application layer, physical layer, protocol layer and electrical layer.

[0091] The fault diagnosis prototype module 303 is used to perform real-time fault location and diagnosis based on the fault simulation result to obtain the fault diagnosis result.

[0092] In an optional implementation, the fault simulation and injection module 302 is also used to inject the fault simulation results into the fault diagnosis prototype through hardware interface resources and hardware fault injection adapter equipment; the fault diagnosis prototype is used to simulate aircraft onboard equipment.

[0093] In an optional implementation, the fault expert knowledge base module 301 is further used to update the fault tree model and the fault code knowledge base based on the fault diagnosis result.

[0094] In an optional implementation, the fault simulation and injection module 302 includes:

[0095] The application layer simulation unit is used to establish an application layer fault model and perform fault simulation at the application layer; the application layer fault model includes a combined navigation sensor fault, a flight control system fault, and a servo fault.

[0096] The physical layer simulation unit is used to establish a physical layer fault model and perform fault simulation at the physical layer; the physical layer fault model includes signal short circuit to power supply, signal short circuit to ground, and open circuit.

[0097] The protocol layer simulation unit is used to establish a protocol layer fault model and perform fault simulation at the protocol layer; the protocol layer fault model includes an electrical fault of the serial communication bus.

[0098] The electrical layer simulation unit is used to establish an electrical layer fault model and perform fault simulation at the electrical layer; the electrical layer fault model includes power supply anomalies and signal fluctuations.

[0099] In an optional implementation, the fault diagnosis result includes at least one of a fault code, a fault location, a fault occurrence time, a fault type, and a fault handling measure.

[0100] In an optional implementation, the above fault expert knowledge base module 301 includes:

[0101] The first fault tree model acquisition unit is used to determine the top event, intermediate event and basic fault; the top event is the main fault event of the aircraft onboard equipment; the intermediate event is the specific fault event that causes the top event; the basic fault is the basic fault that causes the intermediate event.

[0102] Fault tree analysis, also known as accident tree analysis, is the most important analysis method in safety system engineering. Accident tree analysis starts from a possible accident, and searches for the direct and indirect causes of the top event layer by layer from top to bottom until the basic cause event, and uses a logic diagram to express the logical relationship between these events.

[0103] The second fault tree model acquisition unit is used to generate a fault tree model according to the logical relationship between the top event, the intermediate event and the basic fault.

[0104] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0105] An aircraft fault diagnosis system in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above-mentioned functions.

[0106] The embodiment of the present invention also provides a computer device having the above Figure 3 An aircraft fault diagnostic system is shown.

[0107] See also Figure 4 , Figure 4 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 4As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 4 A processor 10 is taken as an example.

[0108] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0109] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0110] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0111] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0112] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 4 The example of connecting through bus is taken in the following.

[0113] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0114] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0115] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0116] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. An aircraft fault diagnosis method, characterized in that: The method comprises: Acquire a fault tree model and a fault code knowledge base of a target aircraft; the fault tree model represents the logical relationship of each fault in the aircraft's onboard equipment; the fault code knowledge base represents the information of each fault code in the aircraft's onboard equipment; Based on the fault tree model and fault code knowledge base of the target aircraft, fault simulation is performed on the onboard equipment of the target aircraft in layers to obtain fault simulation results; the layers include at least one of an application layer, a physical layer, a protocol layer and an electrical layer; Based on the fault simulation result, real-time fault location and diagnosis are performed to obtain a fault diagnosis result.

2. The method according to claim 1, characterized in that The method further comprises: performing fault simulation on the target aircraft's onboard equipment in layers based on the fault tree model and the fault code knowledge base of the target aircraft, and obtaining the fault simulation results; The fault simulation result is injected into a fault diagnosis prototype through hardware interface resources and hardware fault injection adapter equipment; the fault diagnosis prototype is used to simulate aircraft onboard equipment.

3. The method according to claim 1, characterized in that: The method further comprises: Based on the fault diagnosis result, the fault tree model and the fault code knowledge base are updated.

4. The method according to claim 1, characterized in that: The steps of performing fault simulation in layers include: At the application layer, an application layer fault model is established and fault simulation is performed; the application layer fault model includes a combined navigation sensor fault, a flight control system fault, and a steering gear fault; At the physical layer, a physical layer fault model is established and a fault simulation is performed; the physical layer fault model includes a signal short circuit to power supply, a signal short circuit to ground, and an open circuit; At the protocol layer, a protocol layer fault model is established and a fault simulation is performed; the protocol layer fault model includes an electrical fault of a serial communication bus; At the electrical layer, an electrical layer fault model is established and fault simulation is performed; the electrical layer fault model includes power supply anomalies and signal fluctuations.

5. The method according to claim 1, characterized in that The fault diagnosis result includes at least one of a fault code, a fault location, a fault occurrence time, a fault type, and a fault handling measure.

6. The method according to claim 1, characterized in that The obtaining of the fault tree model of the aircraft comprises: Determine the top event, the intermediate event and the basic fault; the top event is the main fault event of the aircraft onboard equipment; the intermediate event is the specific fault event that causes the top event; the basic fault is the basic fault that causes the intermediate event; The fault tree model is generated according to the logical relationship between the top event, the intermediate event and the basic fault.

7. An aircraft fault diagnosis system, characterized in that: The system comprises: A fault expert knowledge base module is used to obtain a fault tree model and a fault code knowledge base of a target aircraft; the fault tree model represents the logical relationship of each fault in the aircraft's airborne equipment; the fault code knowledge base represents the information of each fault code in the aircraft's airborne equipment; A fault simulation and injection module, for performing fault simulation on the target aircraft's onboard equipment in layers based on the target aircraft's fault tree model and fault code knowledge base, to obtain fault simulation results; the layers include at least one of an application layer, a physical layer, a protocol layer, and an electrical layer; The fault diagnosis prototype module is used to locate and diagnose the fault in real time based on the fault simulation result to obtain the fault diagnosis result.

8. The system according to claim 7, characterized in that The fault simulation and injection module is also used to inject the fault simulation results into a fault diagnosis prototype through hardware interface resources and hardware fault injection adapter equipment; the fault diagnosis prototype is used to simulate aircraft onboard equipment.

9. The system according to claim 7, characterized in that The fault expert knowledge base module is also used to update the fault tree model and the fault code knowledge base based on the fault diagnosis result.

10. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method according to any one of claims 1 to 6 by executing the computer instructions.

Images