Aircraft fault processing and troubleshooting method, system and device, medium and aircraft

Abstract

The invention discloses an aircraft fault processing and troubleshooting method, system and device, a medium and an aircraft, and the aircraft fault processing and troubleshooting method comprises the steps: providing a fault report page, and obtaining the input information of a user from the fault report page; performing automatic testing of corresponding faults according to the input information to obtain a testing result; and outputting and displaying the test result, and storing the test result. According to the technical scheme provided by the invention, the technical problems of tedious and time-consuming operation process and low efficiency in the maintenance process of the aircraft in the prior art can be solved.

Description

Technical Field

[0001] The present invention relates to the field of aerospace technology, and in particular to an aircraft fault handling and troubleshooting method, system, electronic device, medium and aircraft. Background Art

[0002] With the commercial aircraft being put into operation, airlines are paying more and more attention to improving the efficiency of maintenance work, which can greatly shorten the maintenance time and reduce the operating costs. According to the conventional troubleshooting procedure, after the aircraft lands, the maintenance personnel need to enter the maintenance system page, and click on the maintenance information of the fault on the fault report page to jump to the electronic manual page for troubleshooting.

[0003] However, during the maintenance of the aircraft, maintenance personnel need to repeatedly jump between the onboard maintenance system function page and the electronic manual page, and thus need to jump between the two function pages of the startup test and status parameters. The operation process is cumbersome, time-consuming and inefficient. Summary of the invention

[0004] The present invention provides an aircraft fault handling and troubleshooting method, system, device, medium and aircraft, aiming to effectively solve the technical problems in the prior art that the operation process is cumbersome, time-consuming and inefficient during the maintenance of the aircraft.

[0005] According to a first aspect of the present invention, the present invention provides an aircraft fault handling and troubleshooting method, comprising: providing a fault report page, and obtaining user input information from the fault report page; performing an automated test of the corresponding fault according to the input information to obtain a test result; outputting and displaying the test result, and storing the test result.

[0006] Furthermore, the step of performing automated testing of the fault based on the input information includes: monitoring whether the fault on the fault report page is clicked; if clicked, generating detailed information of the fault; obtaining the root fault of the fault based on the detailed information; associating the root fault with a preset maintenance manual, the maintenance manual having maintenance methods for various faults; selecting a maintenance method in the maintenance manual based on the root fault; determining whether the selected maintenance method has a test module, and if so, associating the root fault with the test module, and providing a test entry for maintenance personnel to perform testing through the test entry.

[0007] Furthermore, the step of performing automated testing of faults based on the input information also includes: determining whether the maintenance personnel performs the test through the test entry; if so, obtaining the corresponding test module through the associated maintenance manual, and extracting the ground test items; displaying the ground test items for the maintenance personnel to confirm whether to perform the ground test items; receiving the maintenance personnel's confirmation instruction, and starting the test according to the ground test items, or receiving the maintenance personnel's denial instruction and not starting the test.

[0008] Furthermore, the step of starting the test according to the ground test item includes: determining whether the ground test item is an interactive test; if it is an interactive test, receiving interactive information input by the maintenance personnel and executing the ground test; if it is not an interactive test, directly executing the ground test according to the ground test item.

[0009] Furthermore, before the step of outputting the test results, the aircraft fault handling and troubleshooting method also includes: determining whether the automated test has passed; if the automated test has not passed, obtaining the test parameters obtained after starting the ground test item; displaying the test parameters for maintenance personnel to review and perform subsequent maintenance operations to troubleshoot the fault; if the automated test has passed, determining whether the aircraft fault has been eliminated; if the aircraft fault has been eliminated, exiting aircraft fault handling and troubleshooting; if the aircraft fault has not been eliminated, displaying a prompt message to prompt the maintenance personnel to test through other root faults that have not been tested.

[0010] Furthermore, the aircraft fault handling and troubleshooting method further includes: during the step of displaying the ground test items, the ground test items are displayed in a pop-up window.

[0011] Furthermore, after the step of determining whether the ground test item is an interactive test, the aircraft fault handling and troubleshooting method further includes: popping up an interactive information input box, the interactive information input box being used to execute the interactive information input by the maintenance personnel.

[0012] Furthermore, the test entry includes a button, and the button is also used to execute the steps of the automated test after receiving a trigger instruction from a maintenance personnel.

[0013] Furthermore, the method is used in aircraft health management technology.

[0014] According to the second aspect of the present invention, the present invention also provides an aircraft fault handling and troubleshooting system, including: an input module, used to provide a fault report page and obtain user input information from the fault report; an automated test program integration module, used to perform automated testing of corresponding faults based on the input information to obtain test results; an output module, used to output and display the test results; and a storage module, used to store the test results.

[0015] According to the third aspect of the present invention, the present invention also provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, any one of the above-mentioned aircraft fault handling and troubleshooting methods is implemented.

[0016] According to a fourth aspect of the present invention, the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, any one of the above-mentioned aircraft fault handling and troubleshooting methods is implemented.

[0017] According to another aspect of the present invention, the present invention further provides an aircraft, comprising the above-mentioned aircraft fault handling and troubleshooting system.

[0018] Through one or more of the above embodiments of the present invention, at least the following technical effects can be achieved:

[0019] In the technical solution disclosed in the present invention, when maintaining an aircraft, maintenance personnel only need to operate on the fault reporting page of the onboard maintenance system, perform relevant startup tests through the automated test program, output test results and complete the elimination of some faults. There is no need to repeatedly jump between the fault reporting page, maintenance manual, startup test page, etc., which makes the operation process simpler and saves time, thereby improving maintenance efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The technical solutions and other beneficial effects of the present invention will be made apparent by describing in detail the specific embodiments of the present invention in conjunction with the accompanying drawings.

[0021] Figure 1 A flow chart of an aircraft fault handling and troubleshooting method provided by an embodiment of the present invention;

[0022] Figure 2 A framework diagram of an aircraft fault handling and troubleshooting system provided by an embodiment of the present invention;

[0023] Figure 3 A schematic block diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The technical scheme in the embodiment of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiment of the present invention. Obviously, the described embodiment is only a part of the embodiment of the present invention, not all of the embodiments. Based on the embodiment 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] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the term "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " herein, unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.

[0026] With the operation of commercial aircraft, airlines are paying more and more attention to improving maintenance efficiency. Improving maintenance efficiency can greatly shorten maintenance time and reduce operating costs. According to the conventional troubleshooting procedure, after the aircraft lands, the maintenance personnel enter the onboard maintenance system page, and jump to the electronic manual page for troubleshooting by clicking the maintenance information of the fault on the fault report page. When the troubleshooting procedure shows that certain tests need to be performed, the maintenance personnel need to return to the ground test page of the onboard maintenance system to manually select the test execution. If the test result shows that the test passes, the fault is successfully eliminated. If the test fails, the maintenance personnel need to jump to the electronic manual page again and perform troubleshooting according to the troubleshooting procedure in the manual. According to the conventional procedure, the troubleshooting procedure will prompt the maintenance personnel to check the relevant parameters for further root cause location. The maintenance personnel need to jump to the status parameter page of the onboard maintenance system and manually select the relevant parameters for reference. By checking the parameter values ​​and their changes, they can return to the electronic manual to continue troubleshooting. Through the description of the current conventional troubleshooting process, the maintenance personnel need to jump back and forth between the onboard maintenance system page and the electronic manual page, and need to jump back and forth between the onboard maintenance system function pages. There are the following problems:

[0027] 1) Tedious manual operations may introduce human errors;

[0028] 2) Over-reliance on manual labor, resulting in high labor costs;

[0029] 3) It is inconvenient for maintenance personnel to operate and the whole process is cumbersome and time-consuming, resulting in low troubleshooting efficiency and increased operating costs.

[0030] Therefore, the embodiments of the present invention provide an aircraft fault handling and troubleshooting method, system, device, medium and aircraft, which can optimize the aircraft troubleshooting process and improve the overall maintenance efficiency.

[0031] Figure 1 The present invention provides an aircraft fault handling and troubleshooting method, including:

[0032] S101, providing a fault report page, and obtaining user input information from the fault report page;

[0033] S102, performing an automated test of the corresponding fault according to the input information to obtain a test result;

[0034] S103: Output and display the test results, and store the test results.

[0035] In step S101 , a fault report page has a fault of the aircraft, which may be provided by a record maintenance system.

[0036] In this embodiment, the root cause of the fault report details page is used as the input of the system, and the automated test program associates the input with the test execution. After the processing is completed, the result is output to the HMI for display and the storage unit for storage. Through this process, the test execution and the output of the test results are completed.

[0037] Therefore, the aircraft fault handling and troubleshooting method provided in this embodiment simplifies the operating procedures of maintenance personnel. Maintenance personnel only need to operate on the fault reporting page of the onboard maintenance system, perform relevant startup tests through the automated test program, output test results and complete the elimination of some faults without repeatedly jumping between the fault reporting page, maintenance manual, startup test page, etc., which makes the operation process relatively simple and time-saving, and improves maintenance efficiency.

[0038] In some embodiments, the step of performing automated testing of the fault based on the input information includes: monitoring whether the fault on the fault report page is clicked; if clicked, generating detailed information of the fault; obtaining the root fault of the fault based on the detailed information; associating the root fault with a preset maintenance manual, the maintenance manual having maintenance methods for various faults; selecting a maintenance method in the maintenance manual based on the root fault; determining whether the selected maintenance method has a test module, and if so, associating the root fault with the test module, and providing a test entry for maintenance personnel to perform testing through the test entry.

[0039] In this embodiment, the user clicks on a specific fault on the fault report page to enter the details page of the failure information. The system obtains the Root Cause information and associates the Root Cause with the maintenance manual. If the Root Cause is not associated with a test module in the maintenance manual, no test entry is provided; if the Root Cause is associated with a test module in the maintenance manual, a test entry is provided in the corresponding row of the Root Cause on the details page. In this embodiment, the test entry can be a button, which is used to execute the steps of the automated test after receiving a trigger instruction from the maintenance personnel. In other embodiments, the test entry can also be a command input box, etc.

[0040] In this embodiment, if the Root Cause is not associated with a test module in the maintenance manual, no button is provided. If the Root Cause is associated with a test module in the maintenance manual, a button is provided in the row corresponding to the Root Cause in the details page, and the user triggers the step of executing the automated test by clicking the button. In other embodiments, the maintenance personnel can use the command input box to input instructions to trigger the automated test.

[0041] In some embodiments, the step of performing automated testing of faults based on the input information also includes: determining whether maintenance personnel perform testing through the test entry; if so, obtaining the corresponding test module through the associated maintenance manual, and extracting ground test items; displaying the ground test items for maintenance personnel to confirm whether to perform the ground test items; receiving a confirmation instruction from the maintenance personnel, and starting the test according to the ground test items, or receiving a denial instruction from the maintenance personnel and not starting the test.

[0042] In this embodiment, during the step of displaying the ground test items, the ground test items are displayed in a pop-up window.

[0043] In this embodiment, after the user conducts the test through the test portal, the Root Cause and the state parameter database are associated with the maintenance manual, and the startup test module and related parameter information associated with the Root Cause are extracted. The system extracts the extracted startup test items and displays a test confirmation pop-up window. The user can confirm the test information through the pop-up window and decide whether to execute the extracted test. If the test is not executed, the system does not start the test and directly exits the execution of the aircraft fault handling and troubleshooting method.

[0044] In some embodiments, the step of starting the test according to the ground test item includes: determining whether the ground test item is an interactive test; if it is an interactive test, receiving interactive information input by the maintenance personnel and executing the ground test; if it is not an interactive test, directly executing the ground test according to the ground test item.

[0045] In this embodiment, after the step of determining whether the ground test item is an interactive test, the aircraft fault handling and troubleshooting method further includes: popping up an interactive information input box, wherein the interactive information input box is used to execute the interactive information input by the maintenance personnel.

[0046] In this embodiment, in some maintenance scenarios, the cooperation of ground maintenance personnel or ground maintenance equipment is required to complete ground test items. Therefore, in these scenarios, it is necessary to interact with ground maintenance personnel or ground maintenance equipment and then complete the ground test. If in some maintenance scenarios, the aircraft itself can perform maintenance, such as circuit inspection, etc., the ground test can be performed directly.

[0047] In some embodiments, before the step of outputting the test results, the aircraft fault handling and troubleshooting method also includes: determining whether the automated test has passed; if the automated test has not passed, obtaining the test parameters obtained after starting the ground test item; displaying the test parameters for maintenance personnel to review and perform subsequent maintenance operations to troubleshoot the fault; if the automated test has passed, determining whether the aircraft fault has been eliminated; if the aircraft fault has been eliminated, exiting aircraft fault handling and troubleshooting; if the aircraft fault has not been eliminated, displaying a prompt message to prompt the maintenance personnel to test through other root faults that have not been tested.

[0048] In this embodiment, the ground test may pass or fail. If it fails, it means that the automated test cannot successfully maintain the aircraft. In this case, the test parameters will be displayed for maintenance personnel to review and perform subsequent maintenance operations.

[0049] After the ground test is passed, this embodiment also determines whether the fault has been eliminated. This is because the aircraft may have multiple faults, and usually one test item cannot eliminate all faults. If a ground test item is executed and then exited, it is easy for maintenance personnel to forget other fault maintenance. The present application displays a prompt message to remind maintenance personnel that they need to continue fault maintenance, thereby ensuring that all faults of the aircraft can be maintained.

[0050] In summary, the aircraft fault handling and troubleshooting method provided by the embodiment of the present application realizes the integrated design of fault pre-diagnosis and testing by correlating the root cause, maintenance manual, and startup test, simplifies the operation of maintenance personnel, and further improves the maintenance efficiency and convenience of maintenance personnel, so as to reduce the maintenance time and reduce the aircraft operating cost. In addition, in order to facilitate the location of the cause of the test failure, the present invention proposes an associated state parameter database to extract and display the relevant parameter information.

[0051] The aircraft fault troubleshooting system and method proposed in the present invention are applicable to aircraft health management technology;

[0052] This aircraft fault troubleshooting system and method is based on the fault proposal and implementation of the troubleshooting program including the startup test module;

[0053] This aircraft fault troubleshooting system and method is to start the automated test program by setting a Task button on the fault details page;

[0054] The troubleshooting system and method described in this patent refers to closely linking the onboard maintenance system with the maintenance manual, eliminating the need to jump between the two pages;

[0055] The fault pre-diagnosis and test integration described in this patent means that the system links the root cause, maintenance manual, and startup test to each other.

[0056] Furthermore, based on the existing technology, the present application adds relevant status parameter information in the display and storage of test results.

[0057] See also Figure 2 The embodiment of the present application also provides an aircraft fault handling and troubleshooting system, including: an input module 1, an automated test program integration module 2, an output module 3 and a storage module 4; the input module 1 provides a fault report page and obtains user input information from the fault report page; the automated test program integration module 2 is used to perform automated testing of corresponding faults according to the input information to obtain test results; the output module 3 is used to output and display the test results; the storage module 4 is used to store the test results.

[0058] The aircraft fault handling and troubleshooting system provided in this embodiment allows maintenance personnel to only operate on the fault reporting page of the onboard maintenance system when maintaining the aircraft, perform related startup tests through automated test programs, output test results, and complete the elimination of some faults. There is no need to repeatedly jump between the fault reporting page, maintenance manual, startup test page, etc., which makes the operation process simpler and saves time, thereby improving maintenance efficiency.

[0059] In some embodiments, the automated testing program integration module 2 includes: a monitoring unit, a detail information generating unit, a root fault acquiring unit, a maintenance manual associating unit and a test entry providing unit; the monitoring unit is used to monitor whether the fault on the fault report page is clicked; the detail information generating unit is used to generate detail information of the fault if the monitoring unit detects that the fault on the fault report page is clicked; the root fault acquiring unit is used to acquire the root fault of the fault according to the detail information; the maintenance manual associating unit is used to associate the root fault with a preset maintenance manual, and the maintenance manual has test modules for different faults; the test entry providing unit is used to determine whether the root fault is associated with the test module on the maintenance manual, and if so, provide a test entry for maintenance personnel to test through the test entry, and if not, do not provide a test entry.

[0060] In some embodiments, the automated testing program integration module 2 also includes: a test judgment unit, a test module acquisition unit, a ground test item display unit and an instruction execution unit; the test judgment unit is used to determine whether the maintenance personnel performs the test through the test entrance; the test module acquisition unit is used to obtain the corresponding test module through the associated maintenance manual and extract the ground test items if the test judgment unit determines that the maintenance personnel performs the test through the test entrance; the ground test item display unit is used to display the ground test items for the maintenance personnel to confirm whether to perform the ground test items; the instruction execution unit is used to receive the maintenance personnel's confirmation instruction and start the test according to the ground test item, or, receive the maintenance personnel's denial instruction and do not start the test.

[0061] In some embodiments, the instruction execution unit includes: an interactive test judgment subunit, an interactive information receiving subunit, and an execution subunit;

[0062] The interactive test judgment subunit is used to judge whether the ground test item is an interactive test;

[0063] The interactive information receiving subunit is used to receive the interactive information input by the maintenance personnel and execute the ground test when the interactive test judging subunit judges that the ground test item is an interactive test;

[0064] The execution subunit is used for directly executing the ground test according to the ground test item when the interactive test judgment subunit judges that the ground test item is not an interactive test.

[0065] In some embodiments, the aircraft fault handling and troubleshooting system also includes: an automated test judgment module, a test parameter acquisition module, a test parameter display module, a fault elimination judgment module, a maintenance exit module and a prompt information display module; the automated test judgment module is used to judge whether the automated test has passed; the test parameter acquisition module is used to obtain the test parameters obtained after starting the ground test item if the automated test judgment module judges that the automated test has passed; the test parameter display module is used to display the test parameters for maintenance personnel to review and perform subsequent maintenance operations to troubleshoot the fault; the fault elimination judgment module is used to judge whether the aircraft fault has been eliminated if the automated test judgment module judges that the automated test has not passed; the maintenance exit module is used to exit the aircraft fault handling and troubleshooting if the fault elimination judgment module judges that the aircraft fault has been eliminated; the prompt information display module is used to display a prompt message if the fault elimination judgment module judges that the aircraft fault has not been eliminated to prompt the maintenance personnel to test other root faults that have not been tested.

[0066] In some embodiments, when the ground test item display unit displays the ground test item, the ground test item is displayed in a pop-up window.

[0067] In some embodiments, the interactive test judgment subunit is further used to pop up an interactive information input box, and the interactive information input box is used to execute the steps of the interactive information input by the maintenance personnel.

[0068] In some embodiments, the test entry providing unit includes providing a button, and the button is also used to execute the automated test after receiving a trigger instruction from a maintenance personnel.

[0069] In some embodiments, the aircraft fault handling and troubleshooting system is used for aircraft health management technology.

[0070] The present application embodiment provides an electronic device. Figure 3 The electronic device includes: a memory 601, a processor 602, and a computer program stored in the memory 601 and executable on the processor 602. When the processor 602 executes the computer program, the aircraft fault handling and troubleshooting method described above is implemented.

[0071] Furthermore, the electronic device also includes: at least one input device 603 and at least one output device 604 .

[0072] The memory 601 , processor 602 , input device 603 and output device 604 are connected via a bus 605 .

[0073] The input device 603 may be a camera, a touch panel, a physical button or a mouse, etc. The output device 604 may be a display screen.

[0074] The memory 601 may be a high-speed random access memory (RAM) memory or a non-volatile memory, such as a disk memory. The memory 601 is used to store a set of executable program codes, and the processor 602 is coupled to the memory 601 .

[0075] Furthermore, the embodiment of the present application also provides a computer-readable storage medium, which may be disposed in the electronic device in each of the above embodiments, and the computer-readable storage medium may be the memory 601 in the above embodiments. The computer-readable storage medium stores a computer program, which, when executed by the processor 602, implements the aircraft fault handling and troubleshooting method described in the above method embodiment.

[0076] Furthermore, the computer storable medium may also be a U disk, a mobile hard disk, a read-only memory (ROM), a RAM, a magnetic disk or an optical disk, or other medium that can store program codes.

[0077] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0078] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0079] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of software functional modules.

[0080] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention.

[0081] It should be noted that, for the convenience of description, the aforementioned method embodiments are all described as a series of action combinations, but those skilled in the art should be aware that the present invention is not limited by the described action sequence, because according to the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0082] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0083] In summary, although the present invention has been disclosed as above in terms of preferred embodiments, the above preferred embodiments are not intended to limit the present invention. A person skilled in the art may make various changes and modifications without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be based on the scope defined in the claims.

Claims

1. A method for handling and troubleshooting aircraft faults, characterized in that: include: Providing a fault report page, and obtaining user input information from the fault report page; Performing an automated test of the corresponding fault according to the input information to obtain a test result; The test results are output and displayed, and the test results are stored.

2. The method for handling and troubleshooting aircraft faults according to claim 1, characterized in that: The step of performing automated testing of faults according to the input information comprises: Monitoring whether the fault on the fault report page is clicked; If clicked, detailed information about the fault will be generated; Obtain the root fault of the fault according to the detailed information; Associating the root fault with a preset maintenance manual, wherein the maintenance manual has maintenance methods for various faults; Selecting a maintenance method in the maintenance manual according to the root fault; It is determined whether the selected maintenance method has a test module. If so, the root fault is associated with the test module, and a test entry is provided for maintenance personnel to perform testing through the test entry.

3. The method for handling and troubleshooting aircraft faults as claimed in claim 2, characterized in that: The step of performing automated testing of the fault according to the input information further includes: Determining whether the maintenance personnel conducts the test through the test entrance; If yes, then the corresponding test module is obtained through the associated maintenance manual, and the ground test items are extracted; Displaying the ground test item for maintenance personnel to confirm whether to perform the ground test item; Receive a confirmation instruction from the maintenance personnel and start the test according to the ground test item, or receive a denial instruction from the maintenance personnel and do not start the test.

4. The method for handling and troubleshooting aircraft faults as claimed in claim 3, characterized in that: The step of starting the test according to the ground test item comprises: Determining whether the ground test item is an interactive test; If it is an interactive test, it receives interactive information input by the maintenance personnel and performs ground tests; If it is not an interactive test, the ground test is directly performed according to the ground test items.

5. The method for handling and troubleshooting aircraft faults as claimed in claim 3, characterized in that: Before the step of outputting the test result, the aircraft fault handling and troubleshooting method further includes: Determine whether the automated test passes; If the automated test fails, obtaining test parameters obtained after starting the ground test item; The test parameters are displayed for maintenance personnel to review and perform subsequent maintenance operations to eliminate the fault; If the automated test passes, it is determined whether the aircraft fault has been eliminated; If the aircraft fault is eliminated, exit the aircraft fault processing and troubleshooting; If the aircraft fault has not been eliminated, a prompt message is displayed to prompt the maintenance personnel to test other root faults that have not been tested.

6. The method for handling and troubleshooting aircraft faults as claimed in claim 3, characterized in that: The aircraft fault handling and troubleshooting method also includes: In the step of displaying the ground test items, the ground test items are displayed in a pop-up window.

7. The method for handling and troubleshooting aircraft faults as claimed in claim 4, characterized in that: After the step of determining whether the ground test item is an interactive test, the aircraft fault handling and troubleshooting method further includes: An interactive information input box pops up, and the interactive information input box is used to execute the steps of the interactive information input by the maintenance personnel.

8. The method for handling and troubleshooting aircraft faults as claimed in claim 2, characterized in that: The test entry includes a button, and the button is also used to execute the steps of the automated test after receiving a trigger instruction from a maintenance person.

9. The method for handling and troubleshooting aircraft faults as claimed in claim 1, characterized in that: The method is used in aircraft health management technology.

10. An aircraft fault handling and troubleshooting system, characterized in that: include: An input module, used to provide a fault report page and obtain user input information from the fault report; An automated test program integration module, used to perform automated testing of corresponding faults according to the input information to obtain test results; An output module, used for outputting and displaying the test results; A storage module is used to store the test results.

11. An electronic device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method described in any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method described in any one of claims 1 to 9 is implemented.

13. An aircraft, characterized in that: It includes the aircraft fault handling and troubleshooting system as claimed in claim 10.

Images