Cockpit control device fault detection system and method

Abstract

The application relates to a cockpit control device fault detection system and method, which comprises a visual acquisition module, an electrical acquisition module, a processing module, an operation recognition module, a state recognition module and a fault diagnosis module. The visual acquisition module acquires visual data; the electrical acquisition module acquires electrical signal data; the processing module performs correlation processing on the visual data and the electrical signal data to generate correlation data; the operation recognition module generates operation information based on the correlation data; the state recognition module generates state information based on the correlation data; and the fault diagnosis module performs consistency verification based on the operation information, the state information and the correlation-processed electrical signal data to identify a fault occurrence link of the control device and generate a fault diagnosis result. Thus, state monitoring and fault diagnosis can be realized without changing the original structure and operation mode of the control device, and the application has good adaptability, universality and engineering application value.

Description

Technical Field

[0001] This application relates to the field of cockpit control devices for civil transport aircraft, and more specifically, to a cockpit control device fault detection system and method. Background Technology

[0002] Cockpit control devices in civil aircraft (such as control panels, handles, switches, buttons, knobs, etc.) are important human-machine interfaces between the flight crew and the various systems of the aircraft. They provide the flight crew with control and operation functions for the various systems of the aircraft and display system status information. The reliability and maintainability of the control devices are directly related to flight safety and airline operational efficiency.

[0003] Currently, civil aircraft control devices experience a certain failure rate during actual operation. These failures include, but are not limited to: abnormal electrical output due to poor contact of switch contacts, physical states failing to be achieved due to stuck switches or control components, and errors or loss of signals during transmission. These types of failures can not only cause abnormal control commands or display feedback, but also significantly increase the difficulty of troubleshooting during flight operations.

[0004] However, existing fault detection methods for control devices have the following main shortcomings: First, the detection range is limited. Existing methods mainly rely on monitoring the electrical signals themselves, which can only cover electrical failure states such as invalid or unstable bus signals of control devices. They cannot effectively detect failure modes such as device-specific faults (e.g., mechanical jamming), errors or loss of hard-wired transmission signals, and device output accuracy not matching design values.

[0005] Secondly, there is a lack of closed-loop monitoring. Because the actual operational behavior of the flight crew is unknown, it is difficult to comprehensively analyze the correlation between "human operation," "device physical response," and "electrical signal output." When an anomaly occurs, it is impossible to distinguish whether the fault is caused by crew inaction, device jamming, poor contact, or abnormal signal transmission, making fault tracing difficult.

[0006] The aforementioned problems prevent flight crews from obtaining timely and accurate fault information when control devices malfunction, and make it difficult for ground maintenance personnel to quickly locate the root cause of the fault, causing significant difficulties in troubleshooting line faults and potentially even posing flight safety hazards in severe cases. Summary of the Invention

[0007] The problem the invention aims to solve: To address the aforementioned issues, the purpose of this application is to provide a cockpit control device fault detection system and method that can achieve closed-loop monitoring of multi-dimensional human-machine signals and identify the fault occurrence stage.

[0008] Technical means to solve the problem: This application provides a cockpit control device fault detection system, comprising: a visual acquisition module configured to acquire visual data related to the control device within the cockpit; an electrical acquisition module configured to acquire electrical signal data corresponding to the control device; a processing module connected to both the visual acquisition module and the electrical acquisition module, configured to perform correlation processing on the visual data and the electrical signal data to generate correlation data corresponding to the control device; an operation recognition module connected to the processing module, configured to generate operation information characterizing the flight crew's operation behavior and / or operation intention on the control device based on the correlation data; a state recognition module connected to the processing module, configured to generate state information characterizing the physical state of the control device in response to the operation based on the correlation data; and a fault diagnosis module connected to both the state recognition module and the operation recognition module, configured to perform consistency verification based on the operation information, the state information, and the correlation-processed electrical signal data to identify the fault occurrence stage of the control device and generate a fault diagnosis result.

[0009] Preferably, the fault diagnosis module is further configured to: when it is detected that a flight crew is operating the control device based on the operation information, perform a consistency check between the operation information and the status information; if the consistency check results between the operation information and the status information are inconsistent, determine that the fault occurs in the control device itself.

[0010] Preferably, if the consistency verification result of the operation information and the status information is consistent, a consistency verification of the status information and the associated processed electrical signal data is performed; if the consistency verification result of the status information and the associated processed electrical signal data is inconsistent, it is determined that the fault occurs in the electrical output stage; if the consistency verification result of the status information and the associated processed electrical signal data is consistent, it is determined that there is no fault.

[0011] Preferably, the fault diagnosis module is further configured to: if no operation of the control device by the flight crew is detected based on the operation information, perform a consistency check between the status information and the associated processed electrical signal data; if the consistency check result between the status information and the associated processed electrical signal data is inconsistent, determine that the fault occurs in the electrical output stage; if the consistency check result between the status information and the associated processed electrical signal data is consistent, determine that there is no fault.

[0012] Preferably, it further includes: a display recognition module, which is connected to the processing module and configured to generate display information based on the associated data that characterizes the display status of the display device associated with the controller.

[0013] Preferably, the fault diagnosis module is also connected to the display recognition module and is configured to: when the operation information indicates that the flight crew is operating the control device, and the operation information is consistent with the status information and the status information is consistent with the associated processed electrical signal data, perform a consistency check between the associated processed electrical signal data and the display information.

[0014] Preferably, the fault diagnosis module is also connected to the display recognition module and is configured to: perform a consistency check between the associated electrical signal data and the display information when no operation of the control device by the flight crew is identified based on the operation information, and the status information is consistent with the associated electrical signal data.

[0015] Preferably, the fault diagnosis module is further configured to: if the consistency verification between the electrical signal data after association processing and the display information is not consistent, and the consistency verification result between the electrical signal data after association processing and the display information is inconsistent, determine that the fault occurs in the signal transmission link and / or the display response link; if the consistency verification result between the electrical signal data after association processing and the display information is consistent, determine that there is no fault.

[0016] Preferably, the system further includes: a display output module connected to the fault diagnosis module and configured to display the fault diagnosis results to the flight crew; and a data storage module connected to the fault diagnosis module and configured to store the fault diagnosis results.

[0017] Preferably, the data storage module is further configured to store multidimensional state information including the operation information, the state information, and the associated processed electrical signal data, and / or diagnostic evidence used to characterize the multidimensional state information.

[0018] This application provides a method for detecting faults in cockpit control devices, comprising the following steps: acquiring operation information characterizing the flight crew's operational behavior and / or operational intentions towards the control device; acquiring state information characterizing the physical state of the control device in response to the operation; acquiring electrical signal data characterizing the electrical output of the control device in response to the operation; performing correlation processing on the operation information, the state information, and the electrical signal data; determining whether there is an operation by the flight crew on the control device based on the operation information; if the operation exists, performing a consistency check between the operation information and the state information; if the consistency check result between the operation information and the state information is inconsistent, determining that the fault occurs in the control device itself; if the operation information and the state information are inconsistent, determining that the fault occurs in the control device itself. If the consistency check result of the status information is consistent, then a consistency check between the status information and the associated electrical signal data is performed; if the consistency check result between the status information and the associated electrical signal data is inconsistent, then the fault is determined to occur in the electrical output stage; if the consistency check result between the status information and the associated electrical signal data is consistent, then no fault is determined; if the operation does not exist, then a consistency check between the status information and the associated electrical signal data is performed; if the consistency check result between the status information and the associated electrical signal data is inconsistent, then the fault is determined to occur in the electrical output stage; if the consistency check result between the status information and the associated electrical signal data is consistent, then no fault is determined.

[0019] Preferably, it further includes: acquiring display information of the display status of the display device associated with the controller.

[0020] Preferably, when the operation exists, and the consistency verification result of the operation information and the status information is consistent, and the consistency verification result of the status information and the associated electrical signal data is consistent, the consistency verification of the associated electrical signal data and the display information is performed.

[0021] Preferably, if the operation is not performed and the consistency verification result of the status information and the associated electrical signal data is consistent, the consistency verification of the associated electrical signal data and the display information is performed.

[0022] Preferably, in the case of consistency verification between the electrical signal data after association processing and the display information, if the consistency verification result between the electrical signal data after association processing and the display information is inconsistent, it is determined that the fault occurs in the signal transmission link and / or the display response link; if the consistency verification result between the electrical signal data after association processing and the display information is consistent, it is determined that there is no fault.

[0023] Effects of the Invention: According to this application, by associating visual data and electrical signal data related to cockpit control devices, and performing hierarchical consistency checks based on the generated operation information, status information, and the associated electrical signal data, a diagnostic link can be established between flight crew operation, control device physical response, and electrical output. This enables the identification and location of fault occurrence points, improving the accuracy and specificity of fault detection. Specifically, by associating visual data and electrical signal data related to control devices, and performing consistency checks based on operation information, status information, and the associated electrical signal data, a diagnostic link can be established between flight crew operation, control device physical response, and electrical output. This enables the identification and location of fault occurrence points, improving the accuracy and reliability of fault detection. Furthermore, by performing further consistency checks based on the display status information associated with the control devices, a closed-loop diagnostic path covering the display feedback link is established, further identifying faults in the signal transmission link and / or display response link, expanding the range of detectable fault types. Therefore, this application achieves condition monitoring and fault diagnosis without changing the original structure and operation mode of the controller, and has good adaptability, versatility and engineering application value. Attached Figure Description

[0024] Figure 1 This is a schematic diagram of the overall architecture of a cockpit control device fault detection system according to one embodiment of this application.

[0025] Figure 2 This is a schematic diagram of the data flow and module interaction in a cockpit control device fault detection system according to one embodiment of this application.

[0026] Figure 3 This is a flowchart illustrating a cockpit control device fault detection method according to one embodiment of this application. Detailed Implementation

[0027] The following, with reference to the accompanying drawings, provides a detailed description of a cockpit control device fault detection system and method according to an embodiment of this application.

[0028] It should be understood that the following embodiments are for illustrative purposes only and are not intended to limit the scope of this application. The same or corresponding reference numerals in the figures denote the same components, and repeated descriptions are omitted. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0029] In some implementations, such as Figure 1 As shown, the cockpit control device fault detection system of this application consists of multiple functional modules, which work together to monitor the status of control devices in the cockpit, identify faults, and output results. Control devices may include, but are not limited to, switches, buttons, knobs, and control handles on the control panel.

[0030] In some embodiments, the fault detection system includes at least: a visual acquisition module, an electrical acquisition module, a processing module, an operation recognition module, a status recognition module, and a fault diagnosis module. Furthermore, in some embodiments, a display recognition module may also be included. Additionally, in some embodiments, a display output module and a data storage module may be further included.

[0031] The vision acquisition module is used to collect visual data related to the control devices within the cockpit. This visual data may include at least visual data from the flight crew operating area and the control device body area. In some embodiments, the visual data may also include visual data from displays or instrument panels associated with the control devices. This visual data serves as the data basis for subsequently generating operational information, status information, and display information.

[0032] Furthermore, in some embodiments, the visual acquisition module may include one or more imaging devices, which may be arranged at predetermined locations within the cockpit to cover the flight crew operating area, the control device area, and / or the display device area associated with the control device. The visual acquisition module may continuously acquire video data or acquire image frame data at a preset frequency, and may use the same or different sampling frequencies, resolutions, and / or field of view for different areas depending on the fault detection task.

[0033] The electrical acquisition module is used to acquire electrical signal data corresponding to the control device. The electrical signal data may include discrete signals, analog signals, bus signals, and / or other data that can characterize the electrical output status of the control device, which are used by the subsequent fault diagnosis module to perform consistency verification.

[0034] Furthermore, in some implementations, the electrical acquisition module can be connected to the electrical interface, electrical processing unit, bus interface, and / or signal acquisition interface of the controller to acquire electrical signal data related to the controller. The electrical signal data may include discrete quantities, analog quantities, coded signals, bus messages, and / or status fields characterizing the output state of the controller. The electrical acquisition module can acquire data according to a preset sampling period, or it can trigger acquisition when a state change is detected, to meet the timing consistency requirements of fault diagnosis.

[0035] The processing module is connected to both the vision acquisition module and the electrical acquisition module to perform correlation processing on the visual data and electrical signal data, thereby forming associated data corresponding to the control device. The correlation processing may include, but is not limited to, time alignment, data synchronization, establishment of correspondence between control devices, and / or data organization, so that subsequent identification modules and fault diagnosis modules can process and analyze the same control device.

[0036] Furthermore, in some implementations, the processing module can perform preprocessing and correlation processing on the visual data and electrical signal data. Preprocessing may include, but is not limited to, noise reduction, format conversion, timestamp annotation, data resampling, outlier removal, and / or data integrity checks. Correlation processing may include, but is not limited to, time alignment, data synchronization, establishing correspondences between controllers, binding regional data to signal channels, and data organization for individual controllers. Through the processing module, correlation data corresponding to individual controllers can be generated for subsequent use by the identification and diagnosis modules.

[0037] In some implementations, when establishing the correspondence between control devices, the processing module can bind data from different data sources to the same control device based on the control device number, visual area identifier, signal channel identifier, bus field identifier, and / or a preset mapping table. This allows visual data, electrical signal data, and recognition results for a specific control device to be compared and analyzed within a unified data context, thereby improving the accuracy of fault location.

[0038] The operation identification module is connected to the processing module and is used to generate operation information based on associated data, characterizing the flight crew's operational behavior and / or operational intentions towards the control devices. This operation information can be used to determine whether there have been any operations by the flight crew on the control devices and serves as one of the inputs for the consistency verification performed by the fault diagnosis module.

[0039] Furthermore, in some embodiments, the operation recognition module can identify the flight crew's operational behaviors towards the control devices based on visual data of the flight crew's operational area in the associated data, and generate operation information. Operational behaviors may include approaching, touching, pressing, flicking, rotating, holding, and / or leaving. In some embodiments, the operation recognition module can also infer the operation intent by combining the action sequence, action trajectory, and / or contextual information, thereby making the operation information include both the operational behavior and / or the operational intent.

[0040] Furthermore, in some implementations, the operation recognition module can determine whether there is any operation by the flight crew on the control devices based on operation information. For example, when an operation event that meets preset judgment conditions is detected, it is determined that an operation exists. When no operation event that meets the preset judgment conditions is detected, it is determined that no operation exists. The preset judgment conditions can be set according to the type of control device, operation mode, and / or mission scenario.

[0041] The state recognition module is connected to the processing module and is used to generate state information characterizing the physical state of the controller in response to operation based on associated data. The state information may include the position state, pressing state, rotation angle state, and / or attitude state of the controller, and serves as one of the inputs for the consistency verification performed by the fault diagnosis module.

[0042] Furthermore, in some implementations, the state recognition module can identify the physical state of the controller based on visual data of the controller area in the associated data and generate state information. For different types of controllers, the state information can be represented in different forms. For example, a switch can be represented as a gear position, a button as a pressed state, a knob as an angle state, and a handle as a position state and / or attitude state.

[0043] Furthermore, in some implementations, the status information generated by the status recognition module is used to characterize the actual physical response of the controller after flight crew operation. The status information, combined with the operation information generated by the operation recognition module, can be used to determine whether the controller has made an expected physical response to the flight crew operation. The status information can also be further combined with correlated processed electrical signal data to determine whether the physical state of the controller is consistent with its electrical output state.

[0044] The display recognition module is connected to the processing module and is used to generate display information representing the display status of the display device associated with the controller based on the associated data. The display recognition module can perform recognition processing on the display device area associated with the controller to extract information that reflects the execution result of the controller, the system feedback status, and / or the display response status.

[0045] Furthermore, in some implementations, the display recognition module can identify the display status of the display device associated with the controller based on visual data of the display device area in the associated data, and generate display information. The display information can characterize changes in display content, graphic symbol status, alarm status, pointer position status, on / off status, and / or other visually identifiable display states. Based on the controller correspondence established by the processing module, the display recognition module can determine the display device area, display elements, and / or display parameters associated with the target controller, thereby allowing the display information to be compared with the target controller's operation information, status information, and associated processed electrical signal data within the same data context.

[0046] Furthermore, in some embodiments, the display recognition module can output time information and / or identification information of display status changes, so that the fault diagnosis module can perform consistency verification in conjunction with the associated processed electrical signal data. The recognition objects of the display recognition module may include display interface areas, instrument panel areas, indicator light areas, and / or alarm display areas associated with the functions of the controller; for different types of display devices, the display recognition module may use the same or different recognition strategies to generate display information, as long as it can characterize the response status of the display device to the operation and / or electrical output of the controller.

[0047] The fault diagnosis module is connected to both the operation identification module and the status identification module. It can also access electrical signal data from the associated data output by the processing module to perform consistency checks based on operation information, status information, and the associated processed electrical signal data. This identifies the fault location of the controller and generates a fault diagnosis result. Furthermore, in embodiments with a display identification module, the fault diagnosis module can also be connected to the display identification module and receive display information generated by it. When preset conditions are met, the fault diagnosis module can also perform consistency checks based on the associated processed electrical signal data and the display information to identify faults in the signal transmission and / or display response stages.

[0048] In addition, in some implementations, the fault diagnosis module can identify whether the flight crew has operated the control device based on the operation information, and select the corresponding consistency verification path according to the identification result to distinguish between control device body faults, electrical output link faults and / or fault-free states.

[0049] Furthermore, in some embodiments, the fault diagnosis module can receive operation information generated by the operation identification module, status information generated by the status identification module, and display information generated by the display identification module, and call the associated processed electrical signal data provided by the processing module. In embodiments where a display identification module is provided, it can also receive display information generated by the display identification module. Based on the above information, the fault diagnosis module performs a hierarchical consistency check to identify the fault occurrence stage and generate a fault diagnosis result.

[0050] Furthermore, in some implementations, hierarchical consistency verification may include: consistency verification between operation information and status information, consistency verification between status information and associated processed electrical signal data, and consistency verification between associated processed electrical signal data and display information performed when preset conditions are met. By adopting a hierarchical verification and condition-triggered diagnostic approach, the interference of previous-stage anomalies on subsequent-stage judgments can be reduced, improving the accuracy and reliability of fault identification.

[0051] Furthermore, in some implementations, the fault diagnosis results may include the fault occurrence point, fault type indication, fault time information, associated control device identification, and / or an index of evidence information for traceability analysis. The fault diagnosis results may be output to the flight crew and / or maintenance personnel by the display output module and stored by the data storage module.

[0052] The display output module is connected to the fault diagnosis module and is used to output fault diagnosis results to the flight crew. Furthermore, in some embodiments, the display output module may output fault diagnosis results using a cockpit display interface, maintenance terminal interface, alarm prompt interface, and / or other human-machine interface. The output content may include text prompts, graphic prompts, status indicators, fault level information, and / or handling suggestions.

[0053] The data storage module is connected to the fault diagnosis module and is used to store fault diagnosis results. Furthermore, in some embodiments, the data storage module may store, in addition to storing fault diagnosis results, multi-dimensional status information and / or diagnostic evidence associated with the fault diagnosis results. Diagnostic evidence may include visual data fragments, associated processed electrical signal data fragments, operation information, status information, display information, consistency verification results and their timestamps, etc., to facilitate subsequent fault review, maintenance analysis, and system optimization. In addition, in some embodiments, the data storage module may also store multi-dimensional status information including operation information, status information, and associated processed electrical signal data, and / or diagnostic evidence used to characterize the multi-dimensional status information, to facilitate subsequent traceability analysis and maintenance.

[0054] To facilitate the explanation of the fault detection process in this application, the following further describes the data and information involved in the fault detection system processing, which may include visual data, electrical signal data, correlated data, operation information, status information, display information, multi-dimensional status information, and / or diagnostic evidence. The relationships between the above data and information can be established through the collaborative processing of the processing module, operation recognition module, status recognition module, display recognition module, and fault diagnosis module.

[0055] In some implementations, visual data refers to image and / or video data associated with the control devices acquired by the visual acquisition module. Visual data may include visual data of the flight crew operating area, visual data of the control device area, and visual data of the display device area associated with the control devices. The visual data provides a recognition basis for the operation recognition module, status recognition module, and display recognition module.

[0056] In some implementations, electrical signal data refers to signal data acquired by the electrical acquisition module that characterizes the electrical output state of the controller. Electrical signal data may include discrete signals, analog signals, coded signals, bus signals, status fields in bus messages, and / or other data that can reflect changes in the electrical state of the controller. Electrical signal data can be directly used as one of the inputs for consistency verification performed by the fault diagnosis module, or it can be used as input for consistency verification after processing by the processing module.

[0057] In some implementations, associated data refers to a set of data corresponding to a control device, formed by the processing module after associating visual data and electrical signal data. Associated data may include visual data segments, electrical signal data segments, timestamp information, control device identifiers, and / or mapping relationship information corresponding to the same control device. Associated data is used to provide a unified data context for subsequent operation recognition modules, status recognition modules, display recognition modules, and fault diagnosis modules.

[0058] In some implementations, operational information refers to information generated by the operational identification module based on associated data, characterizing the flight crew's operational behaviors and / or operational intentions towards the control devices. Operational behaviors may include approaching, touching, pressing, flicking, rotating, holding, and / or leaving; operational intentions may be inferred from operational behaviors combined with timing information, trajectory information, and / or contextual information. In some implementations, operational information may include only operational behaviors, only operational intentions, or both operational behaviors and operational intentions.

[0059] In some implementations, status information refers to information generated by the status recognition module based on associated data, characterizing the physical state of the controller in response to operation. Depending on the type of controller, status information may include gear position, press position, rotation angle position, position state, posture state, and / or other information characterizing the physical response state of the controller. Status information is used for consistency verification with operation information and associated processed electrical signal data.

[0060] In some implementations, display information refers to information generated by the display recognition module based on associated data, characterizing the display status of the display device associated with the controller. Display information may include information on changes in display content, status of graphic symbols, alarm prompts, pointer position status, on / off status, and / or other information reflecting the response status of the display device. The display information can be used for consistency verification with the associated electrical signal data when preset conditions are met, for further identification of fault occurrence points.

[0061] In some implementations, multidimensional state information refers to a set of data used to characterize the state of a controller and its response chain. In some implementations, multidimensional state information includes at least operational information, state information, and associated processed electrical signal data; in some implementations, multidimensional state information may further include display information. Multidimensional state information can be used for fault diagnosis, result tracing, and / or maintenance analysis.

[0062] In some implementations, diagnostic evidence refers to data and / or information used to support fault diagnosis results. Diagnostic evidence may include visual data fragments, correlated electrical signal data fragments, operational information, status information, display information, consistency verification results, timestamp information, controller identifiers, and / or an index of evidence information corresponding to the fault diagnosis results. Diagnostic evidence may be stored by a data storage module to facilitate subsequent fault review, maintenance analysis, and system optimization.

[0063] In some implementations, consistency verification refers to a process of judging the degree of matching between at least two types of information in terms of state values, state changes, timing correspondences, and / or preset mapping relationships. Consistency verification may include consistency verification between operation information and state information, consistency verification between state information and associated processed electrical signal data, and consistency verification between associated processed electrical signal data and display information when preset conditions are met.

[0064] In some embodiments, the aforementioned "correlation-processed electrical signal data" can be understood as electrical signal data that has been bound to and / or time-aligned with the control device by the processing module. It can either retain the original electrical signal data format or be state-based data extracted from the original electrical signal data to characterize the electrical output state. Those skilled in the art will understand that the specific data organization format of the correlation-processed electrical signal data does not constitute a limitation of this application, as long as it supports subsequent consistency verification and fault identification.

[0065] Therefore, the generation, transformation, and calling relationships among the aforementioned visual data, electrical signal data, associated data, operation information, status information, display information, multidimensional status information, and diagnostic evidence can be achieved through the collaborative processing of the processing module, operation recognition module, status recognition module, display recognition module, and fault diagnosis module.

[0066] The following is for reference Figure 2 The processing of the above data and information will be further explained in conjunction with the functions of each module.

[0067] The processing module is connected to the vision acquisition module and the electrical acquisition module respectively. It is used to perform correlation processing on the visual data and electrical signal data to form correlation data corresponding to the control device, and to provide the correlation data or data generated based on the correlation data to the operation recognition module, status recognition module, display recognition module and / or fault diagnosis module.

[0068] In some implementations, the association processing performed by the processing module on visual data and electrical signal data may include preprocessing and association establishment. Preprocessing may include, but is not limited to, timestamp annotation, format conversion, noise reduction, resampling, outlier handling, and / or data integrity checks. Association establishment may include, but is not limited to, time alignment, establishing correspondences between controllers, establishing correspondences between display devices, and data organization for individual controllers.

[0069] In some implementations, the processing module may perform unified time reference processing on the raw data from the visual acquisition module and the electrical acquisition module, so that data from different sources can be compared under the same time reference. Unified time reference processing may include adding timestamps to visual data frames and electrical signal data, correcting existing timestamps, and / or mapping data from different sampling periods to a preset time axis. Unified time reference processing provides a basis for timing correspondence determination in subsequent consistency checks.

[0070] In some implementations, the processing module can establish a correspondence between controllers based on preset mapping relationships, controller identifiers, visual area identifiers, signal channel identifiers, and / or bus field identifiers, so that visual data and electrical signal data related to the same controller are logically bound. The preset mapping relationships can be generated from system configuration files, calibration results, controller layout information, and / or manually set information, and this application does not limit this.

[0071] In some implementations, for display devices associated with the controller, the processing module can also establish a correspondence between the display devices to determine the correspondence between the controller and the display device area, display elements, and / or display parameters. Through this correspondence, the display identification module can determine the target display area based on the associated data, and the fault diagnosis module can also perform a consistency check on the associated electrical signal data and display information when preset conditions are met.

[0072] In some implementations, the processing module can organize data at the controller granularity to form associated data records for individual controllers. These associated data records may include visual data segments, electrical signal data segments, time information, controller identification, mapping relationship information, and / or auxiliary parameters for identification processing. Organizing data at the controller granularity improves the consistency of subsequent module processing and the targeted nature of fault diagnosis and localization.

[0073] In some implementations, the processing module may output associated data related to the flight crew's operating area and the target controller to the operation identification module, associated data related to the physical state of the target controller to the status identification module, associated data related to the display device area corresponding to the target controller to the display identification module, and associated processed electrical signal data and / or time information and identification information related to consistency verification to the fault diagnosis module.

[0074] In some implementations, the processing module can adjust the correlation processing strategy based on the controller type, detection task type, and / or system operating status. For example, a higher time resolution data organization method can be used for controllers with rapidly changing actions. For controllers that primarily focus on steady-state states, a lower frequency state-based data organization method can be used. By adjusting the correlation processing strategy, a balance can be struck between detection accuracy and processing resources.

[0075] In some implementations, the correlation data generated by the processing module can be used for real-time fault diagnosis or stored in the data storage module for offline analysis, fault verification, and algorithm optimization. In some implementations, the processing module may also output auxiliary information characterizing the quality of correlation processing, such as time alignment quality indicators, data integrity indicators, and / or mapping validity indicators, for the fault diagnosis module to refer to when performing consistency checks.

[0076] In some implementations, the processing module can be implemented in software, hardware, or a combination of both. As long as the correlation processing of visual data and electrical signal data can be achieved to form correlated data that supports subsequent recognition and diagnosis, the specific algorithm, processing order, and data structure of the processing module do not constitute a limitation on this application.

[0077] The operation recognition module is connected to the processing module and is used to generate operation information characterizing the flight crew's operational behavior and / or operational intentions towards the target control device based on the associated data provided by the processing module. The operation recognition module can perform recognition processing on visual data related to the target control device to determine whether the flight crew has performed an operation on the target control device.

[0078] In some embodiments, the operation recognition module can recognize actions such as approaching, touching, pressing, flicking, rotating, holding, releasing, and / or leaving. The operation recognition module can generate operation information based on changes in hand position, movement trajectory, and spatial and / or temporal relationships with the target control device. This application does not limit the specific recognition algorithm used by the operation recognition module.

[0079] In some implementations, the operation information generated by the operation identification module may include the operation behavior type, target controller identifier, operation occurrence time, operation duration, and / or operation status change information. The fault diagnosis module can determine whether there was any operation by the flight crew on the controller based on the operation information, and select the subsequent consistency verification path accordingly.

[0080] In some implementations, the operational intent can be inferred by the operation recognition module based on operational behavior information combined with temporal context information. For example, when the operation recognition module detects that a flight crew member's hand approaches and acts on a target control device, it can generate operation information characterizing an operational intent and / or operational behavior towards that target control device. In some implementations, the operation information may include only the operational behavior, or it may further include the operational intent.

[0081] The state recognition module is connected to the processing module and is used to generate state information characterizing the physical state of the controller in response to operation based on the associated data provided by the processing module. The state recognition module can perform recognition processing on visual data related to the target controller to identify the physical state and / or changes in physical state of the controller.

[0082] In some implementations, depending on the type of controller, the physical states that the state recognition module can recognize may include switch position state, button press state, knob angle state, handle position state, indicator posture state, and / or other states that can characterize the physical response of the controller. The state recognition module can output the current state value and / or state change information for the fault diagnosis module to perform consistency verification.

[0083] In some implementations, the status information generated by the status recognition module may include a target controller identifier, physical status value, direction of status change, time of status change, and / or status validity indication information. By including the target controller identifier and time information in the status information, the status information can be compared with the operation information and associated processed electrical signal data in a unified data context.

[0084] In some implementations, the state recognition module may only recognize the visual area related to the target controller, or it may limit the recognition range by combining the controller correspondence and / or auxiliary parameters provided by the processing module, so as to reduce the interference of irrelevant visual information on the state recognition results and improve the stability and accuracy of state recognition.

[0085] The display recognition module is connected to the processing module and is used to generate display information representing the display status of the display device associated with the controller based on the associated data provided by the processing module. The display recognition module can perform recognition processing on the display device area associated with the target controller to extract information that reflects the controller's execution results, system feedback status, and / or display response status.

[0086] In some implementations, the display recognition module can determine the display device area, display elements, and / or display parameters associated with the target controller based on the controller correspondence established by the processing module, and generate display information based on the corresponding visual data. The display information may include display content change information, graphic symbol status information, alarm prompt status information, pointer position status information, on / off status information, and / or display status change time information.

[0087] In some implementations, the display information generated by the display recognition module can be used to perform consistency verification with the associated processed electrical signal data when preset conditions are met, in order to further identify faults in the signal transmission link and / or display response link. For different types of display devices, the display recognition module can adopt the same or different recognition strategies, as long as it can generate display information to characterize the display response state.

[0088] In some implementations, the operation identification module, status identification module, and display identification module can perform identification processing based on the associated data provided by the processing module, and output operation information, status information, and display information respectively. The fault diagnosis module can receive operation information and status information, and call the associated processed electrical signal data. In implementations that include a display identification module, display information can also be received to perform hierarchical consistency verification and generate fault diagnosis results.

[0089] The fault diagnosis module performs hierarchical consistency checks based on the operation information generated by the operation recognition module, the status information generated by the status recognition module, and the associated processed electrical signal data provided by the processing module. In embodiments with a display recognition module, the fault diagnosis module can also perform further consistency checks based on the display information generated by the display recognition module.

[0090] The following section further explains the identification process of the fault occurrence stage in conjunction with the hierarchical verification path of the fault diagnosis module.

[0091] In some implementations, the fault diagnosis module can first determine whether there is any operation by the flight crew on the target control device based on the operation information, and then select the corresponding consistency verification path according to the determination result. "Operation exists" can be determined by the operation behavior and / or operation intention represented in the operation information, for example, based on the operation behavior identification result corresponding to the target control device identifier, the operation occurrence time and / or operation status change information.

[0092] In some implementations, when the fault diagnosis module determines that the flight crew has operated the target control device, the fault diagnosis module can perform a consistency check between the operation information and the status information to determine whether the flight crew's operation and the physical response of the control device are consistent. The consistency check can be based on the correspondence between status values, the correspondence between the direction of status changes, the correspondence between timing sequences, and / or a preset mapping relationship.

[0093] In some implementations, if the consistency verification results between the operation information and the status information are inconsistent, the fault diagnosis module can determine that the fault occurs in the controller body. Controller body faults may include, but are not limited to, jamming, incomplete pressing / pulling, abnormal mechanism response, physical state changes that do not conform to expectations, and / or other fault states that cause inconsistencies between operation and physical response.

[0094] In some implementations, if the consistency check results between the operation information and the status information are consistent, the fault diagnosis module can further perform a consistency check between the status information and the associated processed electrical signal data to determine whether the physical response and electrical output of the controller are consistent. The consistency check can be based on state value mapping relationships, state change mapping relationships, timing correspondence relationships, and / or preset logic rules.

[0095] In some implementations, if the consistency check result between the status information and the associated processed electrical signal data is inconsistent, the fault diagnosis module can determine that the fault occurs in the electrical output stage; if the consistency check result between the status information and the associated processed electrical signal data is consistent, the fault diagnosis module can determine that the target controller is fault-free under the current diagnostic path.

[0096] In some implementations, when the fault diagnosis module determines based on the operation information that there is no operation of the target control device by the flight crew, the fault diagnosis module can perform a consistency check between the status information and the associated processed electrical signal data to determine whether there is an anomaly between the physical state and electrical output of the control device under no-operation conditions.

[0097] In some implementations, if the consistency check result between the status information and the associated processed electrical signal data is inconsistent under no-operation conditions, the fault diagnosis module can determine that the fault occurs in the electrical output stage; if the consistency check result is consistent, the fault diagnosis module can determine that the target controller is fault-free under the current diagnostic path. By setting a verification path under no-operation conditions, abnormal electrical output faults that are not accompanied by obvious unit operation can be identified.

[0098] In some implementations, where a display recognition module is included, the fault diagnosis module can further perform a consistency check between the correlated electrical signal data and the displayed information when preset conditions are met. The preset conditions may include at least one of the following: there is operation by the flight crew on the target control device, and the consistency check results between the operation information and the status information are consistent, and the consistency check results between the status information and the correlated electrical signal data are consistent; or, there is no operation by the flight crew on the target control device, and the consistency check results between the status information and the correlated electrical signal data are consistent.

[0099] In some implementations, when performing consistency verification between the electrical signal data after correlation processing and the displayed information, the fault diagnosis module can make a judgment based on the correspondence between changes in display state and changes in electrical output, the timing correspondence, and / or a preset mapping relationship. If the consistency verification results are inconsistent, the fault diagnosis module can determine that the fault occurred in the signal transmission stage and / or the display response stage; if the consistency verification results are consistent, the fault diagnosis module can maintain the fault-free determination under the current diagnostic path.

[0100] In some implementations, the fault diagnosis module can generate fault diagnosis results based on the execution results of the aforementioned hierarchical consistency check. The fault diagnosis results may include the fault occurrence stage, fault type indication, associated control device identifier, fault occurrence time, and / or an index of evidence information related to this diagnosis. The fault diagnosis results can be output to a display output module for viewing by the flight crew and / or maintenance personnel, and can also be output to a data storage module for storage.

[0101] In some implementations, the fault diagnosis module can associate consistency verification results, intermediate judgment results, and / or final fault diagnosis results with corresponding operation information, status information, associated processed electrical signal data, and display information to form a traceable chain of diagnostic evidence. By saving the chain of diagnostic evidence, subsequent fault review, maintenance analysis, and system optimization can be supported.

[0102] The following is for reference. Figure 3 This application describes the method for detecting faults in cockpit control devices. Figure 3This paper illustrates a hierarchical consistency verification and diagnostic process when a display recognition module is configured in the system. The fault diagnosis module performs hierarchical consistency verification based on operation information, status information, correlated processed electrical signal data, and display information to identify the fault location and generate a fault diagnosis result. In embodiments without a display recognition module, the verification steps related to display information can be omitted.

[0103] like Figure 3 As shown, the cockpit control device fault detection method of this application may include steps S101 to S112.

[0104] Step S101: Acquire visual data and electrical signal data, and perform correlation processing to generate correlated data and correlated electrical signal data. Specifically, the visual acquisition module can acquire visual data related to the target controller, and the electrical acquisition module can acquire electrical signal data corresponding to the target controller; the processing module performs correlation processing on the visual data and electrical signal data to form correlated data corresponding to the target controller, and outputs the correlated electrical signal data.

[0105] Step S102: Generate operation information, status information, and display information based on the associated data. Specifically, the operation identification module generates operation information representing the flight crew's operation behavior and / or operation intention on the target control device based on the associated data; the status identification module generates status information representing the physical status of the target control device based on the associated data; and the display identification module generates display information representing the display status of the display device associated with the target control device based on the associated data.

[0106] Step S103: Determine whether there is any operation by the flight crew on the target control device. Specifically, the fault diagnosis module can make this determination based on the operation information. The determination can be based on the operation behavior type, target control device identifier, operation occurrence time, operation duration, and / or operation status change information in the operation information. If an operation is determined to exist, proceed to step S104; if no operation is determined to exist, proceed to step S107.

[0107] Step S104: Perform a consistency check between operation information and status information. If it is determined that the flight crew has operated the target control device, the fault diagnosis module performs a consistency check between the operation information and status information to determine whether the flight crew's operation and the physical response of the control device are consistent. The consistency check can be based on the correspondence between status values, the correspondence between the direction of status changes, the correspondence between timing sequences, and / or a preset mapping relationship.

[0108] Step S105: Determine whether the consistency verification results between the operation information and the status information are consistent.

[0109] If the consistency verification results between the operation information and the status information are inconsistent, the fault is determined to be a fault in the controller itself, and the process proceeds to step S111; if the consistency verification results between the operation information and the status information are consistent, the process proceeds to step S107.

[0110] Step S107: Perform a consistency check between the status information and the associated processed electrical signal data. As above, step S107 can be performed in either of the following situations: if it is determined in step S103 that there is no operation by the flight crew on the target control device; or if it is determined in step S105 that the consistency check result between the operation information and the status information is consistent.

[0111] Step S108: Determine whether the consistency check result between the status information and the associated processed electrical signal data is consistent. If the consistency check result between the status information and the associated processed electrical signal data is inconsistent, it is determined that the fault occurred in the electrical output link, and proceed to step S111; if the consistency check result is consistent, proceed to step S109.

[0112] Step S109: Perform a consistency check between the correlated electrical signal data and the displayed information. In some embodiments, if the consistency check result between the status information and the correlated electrical signal data is consistent in step S108, the fault diagnosis module further performs a consistency check between the correlated electrical signal data and the displayed information to identify faults in the signal transmission link and / or the display response link.

[0113] Step S110: Determine whether the consistency check result between the processed electrical signal data and the displayed information is consistent. If the consistency check result between the processed electrical signal data and the displayed information is inconsistent, it is determined that the fault occurred in the signal transmission link and / or the display response link, and proceed to step S111; if the consistency check result is consistent, it is determined that there is no fault, and proceed to step S111.

[0114] Step S111: Generate and output fault diagnosis results. Specifically, the fault diagnosis module generates fault diagnosis results based on the above-mentioned hierarchical consistency verification and judgment results. The fault diagnosis results may include the fault occurrence stage, fault type indication, target control device identifier, fault time information, and / or evidence information index.

[0115] Step S112: Display and store the fault diagnosis results. Specifically, the display output module can display the fault diagnosis results to the flight crew and / or maintenance personnel; the data storage module can store the fault diagnosis results, and can further store the operation information, status information, associated processed electrical signal data, display information (if any) and / or diagnostic evidence chain corresponding to this diagnosis, for subsequent fault review, maintenance analysis and system optimization.

[0116] In some implementations, the consistency verification in steps S104, S107 and S109 does not require the use of a unique fixed algorithm. As long as the consistency of the responses of each link can be judged based on relevant information and the link where the fault occurred can be identified, it can be applied to this application.

[0117] In some implementations... Figure 3 Steps S101 to S112 shown can be implemented by a program executed by one or more processors. The program can be stored in a computer-readable storage medium and implement the above steps during execution. The execution order of each step can be adjusted, combined, or split without affecting the fault identification logic.

[0118] In some implementations, the correlation processing of visual data and electrical signal data in step S101 may include time alignment, establishment of correspondence between control devices and / or data validity screening; the consistency verification in steps S104, S107 and S109 may be combined with preset rules, mapping relationships and / or timing constraints to improve the accuracy and stability of fault identification.

[0119] In some implementations, if the system does not have a display recognition module, step S102 may not generate display information, and steps S109 and S110 may be omitted. The judgment result after step S108 is taken as the final judgment result under the current diagnostic path, and the process proceeds to step S111.

[0120] It should be understood that any process or method description in the flowchart or otherwise described herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which the embodiments of this application pertain.

[0121] In summary, compared with the prior art, this application has at least the following beneficial effects.

[0122] Specifically, by introducing machine vision, this application first solves the problem of "limited detection range" in existing technologies, enabling the identification of mechanical jamming and other physical faults. Secondly, by establishing a closed-loop verification link of "operation-physical state-electrical signal-display feedback", it solves the problem of "lack of closed-loop monitoring link", which can accurately distinguish whether the fault originates from the unit's inaction, the device itself, the electrical output, or the signal transmission / display link, greatly improving the efficiency and accuracy of fault tracing.

[0123] Furthermore, upon detecting flight crew operation on the target control device, a consistency check is first performed between the operation information and the status information to determine if the flight crew's operation is consistent with the physical response of the control device. Then, a consistency check is performed between the status information and the associated processed electrical signal data to determine if the physical response of the control device is consistent with its electrical output. This hierarchical verification method distinguishes between control device faults and electrical output faults, reducing confusion between different fault types and improving the reliability of fault identification.

[0124] Furthermore, in embodiments where a display recognition module is configured, this application can further perform a consistency check between the associated processed electrical signal data and the display information when the consistency check result of the preceding stage meets preset conditions, thereby establishing a closed-loop diagnostic path covering the display feedback link. This allows for further identification of faults in the signal transmission and / or display response stages, expanding the range of detectable fault types and compensating for the inadequacy of covering display feedback anomalies based solely on electrical signal monitoring.

[0125] Furthermore, this application acquires status information related to the control device through a visual method (and can further acquire display information), enabling status monitoring and fault diagnosis without altering the original structure and operating feel of the control device. This demonstrates good adaptability and engineering application value. For different types of control devices (such as switches, buttons, knobs, and control handles) and different types of display devices, this application can be adapted by adjusting the identification strategy and consistency verification rules, thus exhibiting good versatility and scalability.

[0126] In addition, the fault diagnosis results generated by this application can be displayed and stored in combination with related data and / or diagnostic evidence, which facilitates the flight crew to obtain fault prompts in a timely manner, and also facilitates maintenance personnel to conduct fault review, cause analysis and subsequent maintenance, thereby helping to improve fault troubleshooting efficiency and operational support capabilities.

[0127] Therefore, this application can achieve condition monitoring and fault diagnosis without changing the original structure and operation mode of the controller, and has good adaptability, versatility and engineering application value.

[0128] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0129] The above detailed embodiments further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above are merely one specific embodiment of this application and are not limited to the scope of protection of this application. This application can be embodied in various forms without departing from its fundamental characteristics. Therefore, the embodiments described in this application are for illustrative purposes only and not for limitation. Since the scope of this application is defined by the claims rather than the description, and all variations falling within the scope defined by the claims, or their equivalents, should be understood to be included in the claims. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A cockpit control device fault detection system, characterized in that, include: A vision acquisition module, configured to acquire visual data related to the control devices within the cockpit; An electrical data acquisition module is configured to acquire electrical signal data corresponding to the control device. The processing module is connected to the visual acquisition module and the electrical acquisition module respectively, and is configured to perform correlation processing on the visual data and the electrical signal data to generate correlation data corresponding to the control device; An operation identification module, which is connected to the processing module, is configured to generate operation information based on the associated data that characterizes the flight crew's operation behavior and / or operation intentions on the control device; A state recognition module, which is connected to the processing module, and is configured to generate state information based on the associated data that characterizes the physical state of the controller in response to the operation; as well as The fault diagnosis module is connected to the status recognition module and the operation recognition module respectively, and is configured to perform consistency verification based on the operation information, the status information and the associated processed electrical signal data to identify the fault occurrence link of the control device and generate fault diagnosis results.

2. The cockpit control device fault detection system according to claim 1, characterized in that, The fault diagnosis module is further configured as follows: If, based on the operation information, it is identified that a flight crew has operated the control device, a consistency check is performed between the operation information and the status information. If the consistency verification results of the operation information and the status information are inconsistent, it is determined that the fault occurred in the controller itself.

3. The cockpit control device fault detection system according to claim 2, characterized in that, If the consistency check result between the operation information and the status information is consistent, then a consistency check between the status information and the associated electrical signal data is performed. If the consistency check result between the status information and the associated processed electrical signal data is inconsistent, the fault is determined to occur in the electrical output stage. If the consistency check result between the status information and the associated processed electrical signal data is consistent, it is determined that there is no fault.

4. The cockpit control device fault detection system according to claim 1, characterized in that, The fault diagnosis module is further configured as follows: If no operation of the control device by the flight crew is detected based on the operation information, a consistency check is performed between the status information and the associated electrical signal data. If the consistency check result between the status information and the associated processed electrical signal data is inconsistent, the fault is determined to occur in the electrical output stage. If the consistency check result between the status information and the associated processed electrical signal data is consistent, it is determined that there is no fault.

5. The cockpit control device fault detection system according to claim 1, characterized in that, It also includes a display recognition module, which is connected to the processing module and configured to generate display information based on the associated data that characterizes the display status of the display device associated with the controller.

6. The cockpit control device fault detection system according to claim 5, characterized in that, The fault diagnosis module is also connected to the display recognition module and configured as follows: If, based on the operation information, it is identified that a flight crew is operating the control device, and the operation information is consistent with the status information and the status information is consistent with the associated processed electrical signal data, then a consistency check is performed between the associated processed electrical signal data and the display information.

7. The cockpit control device fault detection system according to claim 5, characterized in that, The fault diagnosis module is also connected to the display recognition module and configured as follows: If no operation of the control device by the flight crew is detected based on the operation information, and the status information is consistent with the associated electrical signal data, a consistency check is performed between the associated electrical signal data and the display information.

8. The cockpit control device fault detection system according to claim 6 or 7, characterized in that, The fault diagnosis module is further configured as follows: If the consistency check between the electrical signal data after correlation processing and the display information is inconsistent, the fault is determined to occur in the signal transmission stage and / or the display response stage. If the consistency verification result of the electrical signal data after association processing is consistent with that of the display information, it is determined that there is no fault.

9. The cockpit control device fault detection system according to claim 1, characterized in that, It also includes: a display output module connected to the fault diagnosis module and configured to display the fault diagnosis results to the flight crew; and A data storage module is connected to the fault diagnosis module and configured to store the fault diagnosis results.

10. The cockpit control device fault detection system according to claim 9, characterized in that, The data storage module is further configured to store multidimensional state information including the operation information, the state information, and the associated processed electrical signal data, and / or diagnostic evidence used to characterize the multidimensional state information.

11. A method for detecting faults in cockpit control devices, characterized in that, Includes the following steps: To acquire operational information that characterizes the flight crew's operational behavior and / or operational intentions toward the control devices; Obtain state information characterizing the physical state of the controller in response to the operation; Acquire electrical signal data characterizing the electrical output generated by the controller in response to the operation; The operation information, the status information, and the electrical signal data are correlated and processed. Based on the operational information, determine whether there is any operation by the flight crew on the control device; If the operation exists, then perform a consistency check between the operation information and the status information; If the consistency verification results of the operation information and the status information are inconsistent, it is determined that the fault occurs in the controller itself. If the consistency check result of the operation information and the status information is consistent, then the consistency check between the status information and the associated electrical signal data is performed. If the consistency check result between the status information and the associated processed electrical signal data is inconsistent, the fault is determined to occur in the electrical output stage. If the consistency check result of the status information is consistent with the electrical signal data after association processing, then it is determined that there is no fault; If the operation is not performed, then a consistency check is performed between the status information and the associated electrical signal data. If the consistency check result between the status information and the associated processed electrical signal data is inconsistent, the fault is determined to occur in the electrical output stage. If the consistency check result of the status information is consistent with the electrical signal data after association processing, then it is determined that there is no fault.

12. The cockpit control device fault detection method according to claim 11, characterized in that, Also includes: Obtain display information about the display status of the display device associated with the controller.

13. The cockpit control device fault detection method according to claim 12, characterized in that, If the operation exists, and the consistency verification result of the operation information and the status information is consistent, and the consistency verification result of the status information and the associated electrical signal data is consistent, then the consistency verification of the associated electrical signal data and the display information is performed.

14. The cockpit control device fault detection method according to claim 12, characterized in that, If the operation is not performed and the consistency check result of the status information and the associated electrical signal data is consistent, perform a consistency check between the associated electrical signal data and the display information.

15. The cockpit control device fault detection method according to claim 13 or 14, characterized in that, If the consistency check results of the electrical signal data after association processing and the display information are inconsistent, it is determined that the fault occurred in the signal transmission link and / or the display response link. If the consistency check result of the electrical signal data after association processing is consistent with that of the display information, then it is determined that there is no fault.

Images