Civil aircraft flight control system HIRF test fault positioning method and system

By building a HIRF test fault database for civil aircraft flight control system, determining the troubleshooting items and prioritizing the priority, the problem of unclear fault positioning of HIRF test faults in the existing technology of civil aircraft flight control system has been solved, and the fault elimination efficiency and accuracy have been improved.

CN119472618AInactive Publication Date: 2025-02-18XIAN FLIGHT SELF CONTROL INST OF AVIC
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN202510061802.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-01-15
Publication Date
2025-02-18
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing technology lacks standard methods to isolate and locate HIRF test faults in civil aircraft flight control system, resulting in unclear failures, poor purpose, consumes a lot of manpower and time, and has low efficiency in troubleshooting.

Method used

By using multiple civil aircraft flight control system HIRF test data, we extract fault characteristics to build a fault database, determine the troubleshooting project, and compare the fault data containing the fault data with the fault database, filter the fault data and follow the troubleshooting project to perform the fault data. Processing, prioritization determines the optimal order of scheduling.

Benefits of technology

It improves the efficiency of fault location and troubleshooting, saves time and cost of troubleshooting, and ensures the rationality and effectiveness of the troubleshooting order.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119472618A_ABST
    Figure CN119472618A_ABST
Patent Text Reader

Abstract

The invention relates to a civil aircraft flight control system HIRF test fault positioning method and system, and the method comprises the steps: extracting fault features in a civil aircraft flight control system HIRF test through multiple times of civil aircraft flight control system HIRF test data, and constructing a fault database through the fault features; determining a troubleshooting item and storing the troubleshooting item into the fault database; carrying out fuzzification processing on fault-containing data acquired by the test data acquisition, monitoring and processing system, and inputting the fault-containing data after fuzzification processing into the fault database to obtain a fault processing result; performing defuzzification on the fault processing result, performing priority ranking on the fault removal items according to an effect direction, and determining an optimal fault removal sequence; and positioning and eliminating faults according to the optimal troubleshooting sequence. According to the method, the defect of troubleshooting purely depending on engineering experience in the prior art is overcome, the troubleshooting time and cost are saved, and the troubleshooting efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The disclosed embodiments relate to the field of data processing technology, and more particularly to a method and system for locating faults in a HIRF test of a civil aircraft flight control system. Background Art

[0002] At present, there is no standard method for isolating and locating faults that occur during HIRF (High-Intensity Radiated Field) tests of civil aircraft flight control systems, and most of the methods rely on engineering experience. For a test system consisting of a flight control electronic subsystem, a flight control hydraulic actuation subsystem, a flight control electric actuation subsystem, a sensor simulation load, other onboard equipment simulation loads, and a test data acquisition, monitoring, and processing system, troubleshooting is usually performed based on engineering experience in the following process: First, by changing the shielding effect, determine whether the fault of the target replaceable unit can be reproduced in the test, and roughly isolate or determine the subsystem or submodule where the fault may occur; then check the grounding status of all replaceable units and interconnected cables included in the test system, and finally, by improving the product characteristics of the target replaceable unit, determine whether the electromagnetic shielding effect of the target replaceable unit can be improved, and finally eliminate the fault.

[0003] The disadvantages of the above methods are: unclear troubleshooting sequence, weak purpose, heavy workload, large manpower and time consumption, low troubleshooting efficiency, and easy to make mistakes; the troubleshooting process lacks accurate fault state identification methods, lacks comprehensive analysis methods for fault causes, and is difficult to determine specific fault information. For example, when troubleshooting a certain type of aircraft flight control system HIRF test, it took nearly three months to finally locate the fault and determine the troubleshooting method.

[0004] Therefore, it is necessary to improve one or more problems existing in the above-mentioned related technical solutions.

[0005] It should be noted that this section is intended to provide background or context for the technical solutions of the present disclosure stated in the claims. The description herein is not admitted to be prior art by virtue of being included in this section. Summary of the invention

[0006] The object of the present invention is to provide a method and system for locating faults in a HIRF test of a civil aircraft flight control system, thereby overcoming one or more problems caused by limitations and defects of related technologies at least to a certain extent.

[0007] The present invention first provides a method for locating a HIRF test fault of a civil aircraft flight control system, the method comprising the following steps: Using multiple HIRF test data of civil aircraft flight control systems, extracting fault features in HIRF tests of civil aircraft flight control systems, and using the fault features to build a fault database, wherein the fault features include a fault data threshold; Determining troubleshooting items and storing the troubleshooting items in the fault database, the troubleshooting items including: subsystems that may fail, checking and adjusting the shielding status of the subsystems, checking the grounding status of the subsystems, and checking or changing product features of the subsystems; Performing fuzzy processing on the fault data collected by the test data collection, monitoring and processing system, inputting the fuzzy processed fault data into the fault database, comparing and screening the fault data with the fault data threshold to obtain fault data, and processing the fault data according to the fault elimination items to obtain fault processing results, wherein the fault processing results include: fault elimination items and the effect direction of the fault elimination items on the HIRF test; Defuzzifying the fault handling results, prioritizing the troubleshooting items according to their effects, and determining the optimal troubleshooting sequence; The fault is located and eliminated according to the optimal troubleshooting sequence.

[0008] In the present invention, the process of collecting fault data by the test data collection, monitoring and processing system is as follows: The test data acquisition, monitoring and processing system collects all signal data transmitted during the HIRF test of the civil aircraft flight control system.

[0009] In the present invention, the process of checking and adjusting the shielding state of the subsystem includes: By increasing or decreasing the shielding effect of each replaceable unit and interconnected wiring harness of the corresponding subsystem, check whether the corresponding fault recurs, locate the source of the fault, and confirm the cause of the fault.

[0010] In the present invention, the process of checking the grounding status of the subsystem includes: Check the grounding status of each replaceable unit and interconnection harness of the corresponding subsystem. The grounding status inspection items include: grounding method and grounding impedance value; By changing the grounding method and grounding impedance value, check whether the corresponding fault reappears, locate the fault source, and confirm the cause of the fault.

[0011] In the present invention, the process of checking or changing the product characteristics of a subsystem includes: By changing the shell packaging method of each replaceable unit of the corresponding subsystem and enhancing the filtering method of the internal electronic circuit, the product characteristics can be improved, and the corresponding fault can be checked to see whether it recurs, the source of the fault can be located, and the cause of the fault can be confirmed.

[0012] In the present invention, the fault database includes a table, the number of rows in the table is n, 1≤n≤100, and the number of columns is m, 6≤m≤10.

[0013] In the present invention, the grounding method includes: shell line overlap, shell surface overlap and cable overlap; the shell packaging method includes: copper foil pasted on the side seam, copper foil pasted on the back plate and copper foil pasted on the connector edge; the filtering method includes: filter delay increase, filter delay reduction, capacitive reactance increase and capacitive reactance reduction.

[0014] In the present invention, the effect direction of the troubleshooting items on the HIRF test includes forward and reverse directions. The process of prioritizing the troubleshooting items according to the effect direction and determining the optimal troubleshooting sequence includes: Determine the priority of troubleshooting items according to the direction of their effect on the HIRF test, increase the priority of troubleshooting items corresponding to positive effects, and decrease the priority of troubleshooting items corresponding to negative effects; Determine the optimal troubleshooting sequence based on the priority of all troubleshooting items.

[0015] The present invention secondly provides a civil aircraft flight control system HIRF test fault location system, comprising: a flight control electronic subsystem, a test data acquisition, monitoring and processing system, a simulated load of other equipment on the aircraft, a flight control hydraulic actuation subsystem, a flight control electric actuation subsystem and a simulated load of a sensor, wherein the simulated load of other equipment on the aircraft is a simulated load other than the sensor on the aircraft; The network interface of the test data acquisition, monitoring and processing system is connected to the network interface of the flight control electronic subsystem through a high-speed local area network, the bus port of the simulated load of other equipment on the aircraft is connected to the bus port of the flight control electronic subsystem through an A664 bus, the bus port of the simulated load of other equipment on the aircraft is connected to the bus port of the test data acquisition, monitoring and processing system through an A664 bus, the bus port of the flight control hydraulic actuation subsystem is connected to the bus port of the flight control electronic subsystem through an OAB bus (Outer Actuation Bus, external drive bus), the bus port of the flight control hydraulic actuation subsystem is connected to the bus port of the test data acquisition, monitoring and processing system through an OAB bus, the bus port of the flight control electric actuation subsystem is connected to the bus port of the flight control electronic subsystem through an OAB bus, the bus port of the flight control electric actuation subsystem is connected to the bus port of the test data acquisition, monitoring and processing system through an OAB bus, the bus port of the sensor simulated load is connected to the bus port of the flight control electronic subsystem through an A429 bus, and the bus port of the sensor simulated load is connected to the bus port of the test data acquisition, monitoring and processing system through an A429 bus.

[0016] The technical solution provided by the present invention may include the following beneficial effects: The civil aircraft flight control system HIRF test fault location method and system of the present invention, the fault characteristics and troubleshooting items in the fault database are obtained based on multiple civil aircraft flight control system HIRF tests, each fault characteristic includes a fault data threshold, which can be used to determine whether the data collected in the HIRF test is abnormal, and then after the fault-containing data is input into the fault database, the fault database will determine which data has faults and output the fault processing results. Afterwards, the troubleshooting items are prioritized according to the effect direction, and the optimal troubleshooting order is determined, so that the troubleshooting order is more reasonable and effective, and the fault can be found as quickly as possible to troubleshoot as soon as possible. The above method solves the shortcomings of the prior art that relies solely on engineering experience for troubleshooting, saves troubleshooting time and cost, and improves troubleshooting efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0018] Figure 1 A schematic diagram showing a flow chart of a method for locating a fault in a HIRF test of a civil aircraft flight control system in an exemplary embodiment of the present disclosure; Figure 2 A schematic diagram of hardware equipment of a HIRF test fault location system for a civil aircraft flight control system in an exemplary embodiment of the present disclosure is shown.

[0019] Reference numerals: 1. Flight control electronic subsystem; 2. Test data acquisition, monitoring and processing system; 3. Simulation load of other equipment on board; 4. Flight control hydraulic actuation subsystem; 5. Flight control electric actuation subsystem; 6. Sensor simulation load; 7. High-speed local area network; 8. A664 bus; 9. OAB bus; 10. A429 bus. DETAILED DESCRIPTION

[0020] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0021] In addition, the accompanying drawings are only schematic illustrations of the embodiments of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated descriptions will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities.

[0022] This example implementation method first provides a method for locating a HIRF test fault in a civil aircraft flight control system. Figure 1 , the method comprises the following steps: S101, extracting fault features in the HIRF test of the civil aircraft flight control system using multiple civil aircraft flight control system HIRF test data, and constructing a fault database using the fault features, wherein the fault features include a fault data threshold.

[0023] S102, determining troubleshooting items and storing the troubleshooting items in the fault database, the troubleshooting items including: subsystems that may fail, checking and adjusting the shielding status of the subsystems, checking the grounding status of the subsystems, and checking or changing the product characteristics of the subsystems.

[0024] S103, fuzzy processing is performed on the fault data collected by the test data collection, monitoring and processing system, the fault data after fuzzy processing is input into the fault database, the fault data is compared and screened with the fault data threshold to obtain fault data, and the fault data is processed according to the fault elimination project to obtain a fault processing result, the fault processing result includes: the fault elimination project and the effect direction of the fault elimination project on the HIRF test. The effect direction of the fault elimination project on the HIRF test includes positive and reverse.

[0025] The test data collection, monitoring and processing system collects a large number of data items containing fault data, and each subsystem includes multiple possible fault combinations. Therefore, the data containing faults is relatively complex and irregular. After the data containing faults is input into the fault database, the fault database can determine which data has faults according to the fault data thresholds in its own fault characteristics, and output the fault distance as the fault processing result.

[0026] S104, defuzzifying the fault handling result, prioritizing the troubleshooting items according to the effect direction, and determining the optimal troubleshooting sequence.

[0027] In this process, it can be seen from the fault handling results given by the fault database whether the troubleshooting project has a positive or negative effect on the test results. The priority of the troubleshooting project is determined according to the effect direction of the troubleshooting project on the HIRF test, and the priority of the troubleshooting project corresponding to the positive effect is increased, and the priority of the troubleshooting project with the negative effect is reduced. Specifically, if it is a positive effect, the priority of this troubleshooting project in the troubleshooting sequence is increased, and if it is a negative effect, the priority is reduced. According to the priorities of all troubleshooting projects, the optimal troubleshooting sequence is determined, so that the troubleshooting sequence is more reasonable and effective, and the fault can be found as quickly as possible so as to be eliminated as soon as possible.

[0028] Specifically, each row of data in the fault database is a sample data group consisting of a set of troubleshooting items. In the process of forming the fault database, each sample data group has been verified by the HIRF test to determine whether the troubleshooting items have a positive or negative effect on the test results. If it is a positive effect, the priority of this troubleshooting item in the troubleshooting sequence (the troubleshooting sequence may include the troubleshooting procedure) is increased, and if it is a negative effect, the priority is reduced. After the fault database is formed, the new fault characteristics are input into the fault database for comparison operation. According to the verification results of the historical sample data group, the priority of the fault improvement measures is determined for different troubleshooting items, and the fault distance is output as the fault processing result. The results output by the fault database can be used as a baseline for troubleshooting. After the output results of the fault database are verified by the HIRF test, if necessary, the improvement measures can be partially adjusted to achieve the purpose of troubleshooting, thereby determining the optimal troubleshooting sequence, making the troubleshooting sequence more reasonable and effective, and being able to find the fault as quickly as possible to eliminate it as soon as possible.

[0029] S105: locate and eliminate the fault according to the optimal troubleshooting sequence.

[0030] In this embodiment, the fault characteristics and troubleshooting items in the fault database are obtained based on multiple HIRF tests of civil aircraft flight control systems. Each fault characteristic includes a fault data threshold, which can be used to determine whether the data collected in the HIRF test is abnormal. After the fault data is input into the fault database, the fault database will determine which data has faults and output the fault processing results. Afterwards, the troubleshooting items are prioritized according to the effect direction, and the optimal troubleshooting order is determined, so that the troubleshooting order is more reasonable and effective, and the fault can be found as quickly as possible to troubleshoot as soon as possible. The above method solves the shortcomings of the prior art that relies solely on engineering experience for troubleshooting, saves troubleshooting time and cost, and improves troubleshooting efficiency.

[0031] In one embodiment, the fault database includes a table, the number of rows in the table is n, 1≤n≤100, the number of columns is m, 6≤m≤10, and each row of data is a sample data group consisting of a set of troubleshooting items. It should be noted that each subsystem may have multiple faults, and each row of data represents a fault condition that occurs in a certain subsystem. The column data in the table include: the replaceable unit or interconnection harness corresponding to the fault source; whether the corresponding replaceable unit or interconnection harness is wrapped with a copper mesh; the grounding method of the corresponding replaceable unit or interconnection harness; the grounding impedance of the corresponding replaceable unit or interconnection harness; the product shell packaging method of the corresponding replaceable unit; the product internal filtering method of the corresponding replaceable unit. The above is only an example, but is not limited to this.

[0032] It should be noted that the process of checking and adjusting the shielding status of the subsystem includes: checking whether the corresponding fault recurs, locating the fault source, and confirming the cause of the fault by increasing or decreasing the shielding effect of each replaceable unit and interconnecting harness of the corresponding subsystem. For example, the replaceable unit and interconnecting harness are shielded by wrapping with a copper mesh or the copper mesh is removed to remove the shielding, and then judging whether the fault recurs.

[0033] The process of checking the grounding status of the subsystem includes: checking the grounding status of each replaceable unit and interconnected harness of the corresponding subsystem. The grounding status check items include: grounding method and grounding impedance value; by changing the grounding method and grounding impedance value, check whether the corresponding fault reappears, locate the fault source, and confirm the cause of the fault. Among them, the grounding methods include: shell wire overlap, shell surface overlap, and cable overlap.

[0034] The process of checking or changing the product characteristics of a subsystem includes: improving product characteristics by changing the shell packaging method of each replaceable unit of the corresponding subsystem and enhancing the filtering method of the internal electronic circuit, checking whether the corresponding fault reappears, locating the source of the fault, and confirming the cause of the fault. Among them, the shell packaging method includes: copper foil on the side seam, copper foil on the back plate, copper foil on the edge of the connector, etc. The filtering method includes: increasing the filter delay, reducing the filter delay, increasing the capacitive reactance, reducing the capacitive reactance, etc.

[0035] This example implementation method provides a civil aircraft flight control system HIRF test fault location system, please refer to Figure 2 The civil aircraft flight control system HIRF test fault location system includes: a flight control electronic subsystem 1, a test data acquisition, monitoring and processing system 2, a simulated load of other equipment on the aircraft 3, a flight control hydraulic actuation subsystem 4, a flight control electric actuation subsystem 5 and a sensor simulated load 6, wherein the simulated load of other equipment on the aircraft 3 is a simulated load other than the sensor on the aircraft.

[0036] Specifically, the network interface of the test data acquisition, monitoring and processing system 2 and the network interface of the flight control electronic subsystem 1 are connected through a high-speed local area network 7, the bus port of the simulated load 3 of other equipment on board is connected to the bus port of the flight control electronic subsystem 1 through an A664 bus 8, the bus port of the simulated load 3 of other equipment on board is connected to the bus port of the test data acquisition, monitoring and processing system 2 through an A664 bus 8, the bus port of the flight control hydraulic actuation subsystem 4 is connected to the bus port of the flight control electronic subsystem 1 through an OAB bus 9 (Outer Actuation Bus 9). Bus, external drive bus), the bus port of the flight control hydraulic actuation subsystem 4 is connected to the bus port of the test data acquisition, monitoring and processing system 2 through the OAB bus 9, the bus port of the flight control electric actuation subsystem 5 is connected to the bus port of the flight control electronic subsystem 1 through the OAB bus 9, the bus port of the flight control electric actuation subsystem 5 and the bus port of the test data acquisition, monitoring and processing system 2 are connected through the OAB bus 9, the bus port of the sensor simulation load 6 is connected to the bus port of the flight control electronic subsystem 1 through the A429 bus 10, and the bus port of the sensor simulation load 6 is connected to the bus port of the test data acquisition, monitoring and processing system 2 through the A429 bus 10. The civil aircraft flight control system HIRF test fault location method of any of the aforementioned embodiments is used to locate the civil aircraft flight control system HIRF test fault.

[0037] In this embodiment, the test data acquisition, monitoring and processing system 2 is used to collect various data of the flight control electronic subsystem 1, including the sensor simulation load 6, the simulation load of other equipment on the aircraft 3, the flight control hydraulic actuation subsystem 4 and the flight control electric actuation subsystem 5. The collected data is then input into the fault database to obtain the best troubleshooting sequence, thereby improving the troubleshooting efficiency.

[0038] A specific embodiment is listed below to illustrate the fault location method of the present application.

[0039] The method of this application was applied to a certain model of HIRF test, and the implementation steps are as follows: 1. Utilize multiple civil aircraft flight control system HIRF test data to extract fault features in the civil aircraft flight control system HIRF test, and construct a fault database using the fault features, wherein the fault features include fault data thresholds. The multiple civil aircraft flight control system HIRF test data may be a combination of previous test data and current test data. It should be emphasized that once the database is constructed, it can be used for a long time, and the data in the database can also be updated before use.

[0040] Among them, the HIRF test fault database is shown in Table 1.

[0041] Table 1 HIRF test failure database 2. Perform fuzzy processing on the fault data collected by the test data collection, monitoring and processing system 2, and input the fuzzy processed fault data into the fault database to obtain the fault processing result.

[0042] 3. The fault database determines the optimal troubleshooting sequence according to the faults that occurred and the troubleshooting sequence.

[0043] 4. The staff locates and eliminates the fault according to the optimal troubleshooting sequence obtained.

[0044] The above troubleshooting process usually takes two weeks to complete, which is significantly better than the several months required in the prior art.

[0045] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

[0046] Those skilled in the art may combine and combine the different embodiments or examples described in this specification. Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present invention, which follows the general principles of the present invention and includes common knowledge or customary techniques in the art that are not disclosed by the present invention. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present invention are indicated by the appended claims.

Claims

1. A method for locating faults in a HIRF test of a civil aircraft flight control system, characterized in that: The method comprises the following steps: Using multiple HIRF test data of civil aircraft flight control systems, extracting fault features in HIRF tests of civil aircraft flight control systems, and using the fault features to build a fault database, wherein the fault features include a fault data threshold; Determining troubleshooting items and storing the troubleshooting items in the fault database, the troubleshooting items including: subsystems that may fail, checking and adjusting the shielding status of the subsystems, checking the grounding status of the subsystems, and checking or changing product features of the subsystems; Performing fuzzy processing on the fault data collected by the test data collection, monitoring and processing system, inputting the fuzzy processed fault data into the fault database, comparing and screening the fault data with the fault data threshold to obtain fault data, and processing the fault data according to the fault elimination items to obtain fault processing results, wherein the fault processing results include: fault elimination items and the effect direction of the fault elimination items on the HIRF test; Defuzzifying the fault handling results, prioritizing the troubleshooting items according to their effects, and determining the optimal troubleshooting sequence; The fault is located and eliminated according to the optimal troubleshooting sequence.

2. According to claim 1, the method for locating faults in a HIRF test of a civil aircraft flight control system is characterized in that: The process of collecting fault data by the test data acquisition, monitoring and processing system is as follows: The test data acquisition, monitoring and processing system collects all signal data transmitted during the HIRF test of the civil aircraft flight control system.

3. The method for locating faults in a HIRF test of a civil aircraft flight control system according to claim 1, characterized in that: The process of checking and adjusting the shielding status of a subsystem includes: By increasing or decreasing the shielding effect of each replaceable unit and interconnected wiring harness of the corresponding subsystem, check whether the corresponding fault recurs, locate the source of the fault, and confirm the cause of the fault.

4. The method for locating faults in a HIRF test of a civil aircraft flight control system according to claim 3, characterized in that: The process of checking the grounding status of the subsystem includes: Check the grounding status of each replaceable unit and interconnection harness of the corresponding subsystem. The grounding status inspection items include: grounding method and grounding impedance value; By changing the grounding method and grounding impedance value, check whether the corresponding fault reappears, locate the fault source, and confirm the cause of the fault.

5. The method for locating faults in a HIRF test of a civil aircraft flight control system according to claim 4, characterized in that: The process of reviewing or changing the product characteristics of a subsystem includes: By changing the shell packaging method of each replaceable unit of the corresponding subsystem and enhancing the filtering method of the internal electronic circuit, the product characteristics can be improved, and the corresponding fault can be checked to see whether it recurs, the source of the fault can be located, and the cause of the fault can be confirmed.

6. The method for locating faults in a HIRF test of a civil aircraft flight control system according to claim 1, characterized in that: The fault database includes a table, the number of rows in the table is n, 1≤n≤100, and the number of columns in the table is m, 6≤m≤10.

7. The method for locating faults in a HIRF test of a civil aircraft flight control system according to claim 5, characterized in that: The grounding methods include: shell wire overlap, shell surface overlap and cable overlap; the shell packaging methods include: copper foil on the side seams, copper foil on the back plate and copper foil on the connector edge; the filtering methods include: filter delay increase, filter delay reduction, capacitive reactance increase and capacitive reactance reduction.

8. The method for locating faults in a HIRF test of a civil aircraft flight control system according to claim 1, characterized in that: The effect directions of the troubleshooting items on the HIRF test include positive and reverse directions. The process of prioritizing the troubleshooting items according to the effect directions and determining the optimal troubleshooting sequence includes: Determine the priority of troubleshooting items according to the direction of their effect on the HIRF test, increase the priority of troubleshooting items corresponding to positive effects, and decrease the priority of troubleshooting items corresponding to negative effects; Determine the optimal troubleshooting sequence based on the priority of all troubleshooting items.

9. Civil aircraft flight control system HIRF test fault location system, characterized by: The method described in any one of claims 1 to 8 is used to locate and eliminate the HIRF test fault of the civil aircraft flight control system, and the civil aircraft flight control system HIRF test fault location system comprises: a flight control electronic subsystem, a test data acquisition, monitoring and processing system, a simulated load of other equipment on the aircraft, a flight control hydraulic actuation subsystem, a flight control electric actuation subsystem and a sensor simulated load, wherein the simulated load of other equipment on the aircraft is a simulated load other than the sensor on the aircraft; The network interface of the test data acquisition, monitoring and processing system is connected to the network interface of the flight control electronic subsystem through a high-speed local area network, the bus port of the simulated load of other equipment on the aircraft is connected to the bus port of the flight control electronic subsystem through an A664 bus, the bus port of the simulated load of other equipment on the aircraft is connected to the bus port of the test data acquisition, monitoring and processing system through an A664 bus, the bus port of the flight control hydraulic actuation subsystem is connected to the bus port of the flight control electronic subsystem through an OAB bus, the bus port of the flight control hydraulic actuation subsystem is connected to the bus port of the test data acquisition, monitoring and processing system through an OAB bus, the bus port of the flight control electric actuation subsystem is connected to the bus port of the flight control electronic subsystem through an OAB bus, the bus port of the flight control electric actuation subsystem is connected to the bus port of the test data acquisition, monitoring and processing system through an OAB bus, the bus port of the sensor simulated load is connected to the bus port of the flight control electronic subsystem through an A429 bus, and the bus port of the sensor simulated load is connected to the bus port of the test data acquisition, monitoring and processing system through an A429 bus.

Citation Information

Patent Citations

  • Civil airplane flight control system mixing heterogeneous simulation platform

    CN106055728A

  • A fault diagnosis method based on maintenance data and a fault diagnosis system

    CN106155035A

  • Flight control system fault diagnosis method based on PL code list

    CN114326661A

  • Airworthiness appraisal test system and airworthiness appraisal test method for civil aircraft flight control system

    CN114661029A

  • Fault diagnosis simulation system and fault diagnosis simulation method for airborne maintenance system

    CN116108698A