Fault detection method, electronic equipment and storage medium

Abstract

The invention discloses a fault detection method, electronic equipment and a storage medium. According to the specific scheme, operation data of a to-be-detected component under at least one collection index are obtained; determining an analysis result of the operation data according to the operation data obtained within a preset time length; wherein the analysis result comprises the fault duration and the fault frequency of the to-be-detected component in the preset duration; determining a target fault type of the to-be-detected component according to the fault duration and the fault frequency in the analysis result and predetermined benchmark reference data corresponding to the to-be-detected component; and when the target fault type is a preset fault type, determining troubleshooting information corresponding to the to-be-detected component. According to the invention, accurate fault detection is realized, and troubleshooting processing is facilitated, so that the to-be-detected component can operate normally.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a fault detection method, electronic equipment and storage medium. Background Art

[0002] At present, the method of setting a fault threshold is mainly used to detect faults of various components by using a controller. When a corresponding component fails, the corresponding parameter of the faulty component is detected. If the parameter meets the fault threshold and lasts for a certain period of time, it is considered that a fault exists.

[0003] However, in the above method, fault judgment is performed only based on the fault duration, which leads to low accuracy of fault detection. Some intermittent hardware faults cannot be accurately detected, which reduces the accuracy of fault detection and is not conducive to the normal operation of various components. Summary of the invention

[0004] The present invention provides a fault detection method, electronic equipment and storage medium, which realize accurate fault detection and facilitate troubleshooting so that the component to be detected can operate normally.

[0005] According to one aspect of the present invention, a fault detection method is provided, the method comprising:

[0006] Acquire operating data of the component to be inspected under at least one acquisition indicator;

[0007] Determine the analysis result of the operation data according to the operation data acquired within the preset time; wherein the analysis result includes the duration of the fault and the frequency of the fault of the component to be detected within the preset time;

[0008] Determine the target fault type of the component to be detected based on the fault duration and fault frequency in the analysis results and the predetermined benchmark reference data corresponding to the component to be detected;

[0009] When the target fault type is a preset fault type, the troubleshooting information corresponding to the component to be detected is determined.

[0010] According to another aspect of the present invention, there is provided a fault detection device, the device comprising:

[0011] A data acquisition module, used to acquire operating data of the component to be inspected under at least one acquisition index;

[0012] A data analysis module, used to determine the analysis results of the operation data according to the operation data acquired within a preset time period; wherein the analysis results include the duration of the fault and the frequency of the fault of the component to be detected within the preset time period;

[0013] A fault type determination module is used to determine the target fault type of the component to be detected based on the fault duration and fault frequency in the analysis results and the predetermined benchmark reference data corresponding to the component to be detected;

[0014] The troubleshooting information determination module is used to determine the troubleshooting information corresponding to the component to be detected when the target fault type is a preset fault type.

[0015] According to another aspect of the present invention, there is provided an electronic device, the electronic device comprising:

[0016] at least one processor; and

[0017] a memory communicatively connected to at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by at least one processor. The computer program is executed by at least one processor so that the at least one processor can execute the fault detection method of any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions. The computer instructions are used to enable a processor to implement the fault detection method of any embodiment of the present invention when executed.

[0020] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein the computer program implements the fault detection method according to any embodiment of the present invention when executed by a processor.

[0021] The technical solution of the embodiment of the present invention provides data support for subsequent data processing by obtaining the operating data of the component to be detected under at least one acquisition indicator. According to the operating data obtained within a preset time length, the analysis result of the operating data is determined, so as to determine whether the component to be detected has a fault according to the analysis result. According to the duration of the fault and the frequency of the fault in the analysis result, and the predetermined benchmark reference data corresponding to the component to be detected, the target fault type of the component to be detected is determined. When the target fault type is a preset fault type, the troubleshooting information corresponding to the component to be detected is determined to realize the troubleshooting and processing of the component to be detected. The present invention solves the problem of inaccurate fault detection in the prior art and realizes accurate detection of faults. By troubleshooting the component to be detected according to the target fault type, the fault existing in the component to be detected can be discovered in time, so that the component to be detected can operate normally.

[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 is a flow chart of a fault detection method provided by an embodiment of the present invention;

[0025] Figure 2 is a structural example diagram of a vehicle control system provided by an embodiment of the present invention;

[0026] Figure 3 is a flow chart of a fault detection method provided by an embodiment of the present invention;

[0027] Figure 4 is an example of a broken line graph corresponding to the fault frequency provided by an embodiment of the present invention;

[0028] Figure 5 is a structural schematic diagram of a fault detection device provided by an embodiment of the present invention;

[0029] Figure 6 It is a structural schematic diagram of an electronic device for implementing the fault detection method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] Before executing the technical solution provided by the present invention, the application scenario can be described first. The technical method provided by the embodiment of the present invention can be applied to a control system including a controller and at least one component to be detected that communicates with the controller to realize fault detection. Among them, the controller includes an acquisition chip and a processing chip, and the acquisition chip communicates with at least one data acquisition sensor in the component to be detected, and is used to obtain the operating data of the component to be detected collected by the data acquisition sensor. The processing chip is used to process the operating data acquired by the acquisition chip to realize fault detection. It should be noted that the control system can be a new energy vehicle control system, an industrial and commercial energy storage control system, and a home appliance control system, etc. The present invention does not limit the specific control system.

[0033] Embodiment 1

[0034] Figure 1 This is a flow chart of a fault detection method provided in the first embodiment of the present invention. This embodiment is applicable to the case of performing fault detection on a device including a component to be detected. The method can be executed by a fault detection device. The fault detection device can be implemented in the form of hardware and / or software. The fault detection device can be configured in an electronic device such as a mobile phone, a computer or a server. Figure 1 As shown, the method includes:

[0035] S110: Acquire operating data of a component to be inspected under at least one acquisition indicator.

[0036] In order to ensure the normal operation of the control system, at least one hardware component included in the control system may be detected. Among them, the hardware component currently being detected may be used as the component to be detected. For example, if the control system is a vehicle control system, the component to be detected may be a battery. In the implementation of the present invention, the fault detection and processing method for each hardware component is similar. Therefore, the following description will be given using the current component to be detected as an example. The collection index may be an index for detecting or evaluating the operating status, performance characteristics, and possible problems of the component to be detected. For example, if the component to be detected is a battery, the data corresponding to the collection index may be indicator data such as the temperature, current, and voltage of the battery. The operating data may be data collected when the component to be detected is in an operating state.

[0037] Specifically, in order to facilitate the collection of various data of the component to be detected, at least one data acquisition sensor can be deployed at a preset position of the component to be detected, so as to collect the operation data corresponding to at least one collection indicator based on the data acquisition sensor. It should be noted that the number and type of data acquisition sensors are determined according to actual needs and collection indicators.

[0038] Optionally, obtaining operating data of the component to be detected under at least one acquisition indicator includes: when it is determined that the data acquisition conditions are met, obtaining raw data collected by at least one data acquisition sensor deployed at a preset position of the component to be detected; and performing data cleaning processing on the raw data to obtain operating data corresponding to at least one acquisition indicator.

[0039] Among them, the data acquisition conditions can be conditions pre-set according to actual needs. For example, the following conditions can be used as data acquisition conditions, such as the normal power supply of the component to be detected, the normal data acquisition harness, and the absence of other problems that affect fault detection in the control system. The preset position can be a pre-set, specified position on the component to be detected. The data acquisition sensor is used to collect raw data during the operation of the component to be detected. Different data acquisition sensors have different corresponding acquisition indicators. Data cleaning processing can be processing or error correction of the raw data to solve problems such as data inconsistency and incompleteness in the raw data. Optionally, data cleaning processing can include operations such as data deduplication and data padding.

[0040] Specifically, before collecting data, it can be determined whether the data acquisition condition is currently met. When it is determined that the data acquisition condition is met, the raw data collected by at least one data acquisition sensor deployed at a preset position is obtained. The raw data is cleaned to improve the accuracy of subsequent data processing, and the operating data corresponding to at least one collection indicator is obtained.

[0041] For example, see Figure 2 , the data acquisition sensor is Figure 2 Sensors in . Figure 2 This is an example diagram of a vehicle control system. The vehicle control system includes a controller and at least one component to be detected that communicates with the controller. N data acquisition sensors are deployed on the component to be detected to collect original information of the component to be detected. The controller includes an acquisition chip, a processing chip (Microcontroller Unit, MCU) and a controller area network chip (Controller Area Network, CAN). The acquisition chip communicates with the n data acquisition sensors on the component to be detected through an acquisition harness. The processing chip is used to process the raw data obtained by the acquisition chip and transmit the processed results to the controller area network chip. The controller area network chip feeds back the processed results to the vehicle terminal through the CAN communication line, so that the vehicle terminal can remind or display a fault signal.

[0042] In combination with the above example, before data acquisition, the controller can be awakened to complete the initialization of the controller. When collecting the original data of the object to be detected, it is determined whether the data acquisition conditions are met. For example, whether the controller is operating normally, whether the power supply of the controller is within the normal range, etc. If the data acquisition conditions are met, the identifier used to mark the fault state in the processing chip of the controller is set to uncertain, and the acquisition chip in the controller obtains the original data of the object to be detected through the acquisition harness connected to the data acquisition sensor. Among them, the acquisition cycle is pre-set according to the characteristics of the data acquisition sensor and the function and accuracy of the controller. Accordingly, if the data acquisition conditions are not met, the corresponding prompt information is generated and the controller and other components are adjusted so that they meet the data acquisition conditions.

[0043] S120. Determine analysis results of the operation data according to the operation data acquired within a preset time period; wherein the analysis results include the duration of the fault and the frequency of the fault of the component to be detected within the preset time period.

[0044] Among them, the preset duration can be a preset fault detection duration. The fault duration can be understood as the duration corresponding to the fault of the component to be detected. For example, the fault duration can be 4 seconds. The fault frequency can be understood as the number of times the fault occurs in the component to be detected within the preset duration. Optionally, the analysis result can be determined by a preset fault trigger threshold. The preset fault trigger threshold is preset and is used to determine whether a fault occurs in the component to be detected. When the operating data reaches the preset fault trigger threshold, the fault frequency is counted as 1. For example, the preset fault trigger threshold can be a battery temperature of 125 degrees Celsius. When the battery temperature in the operating data collected within the preset duration reaches 125 degrees Celsius, the fault frequency is counted as 1.

[0045] Specifically, according to the operation data acquired within the preset time, the number of times the operation data reaches the preset fault trigger threshold, i.e., the fault frequency, is determined. And within the preset time, the duration of each time the operation data reaches the preset fault trigger threshold, i.e., the fault duration, is determined.

[0046] Exemplarily, in combination with the above examples, taking the component to be detected as a battery as an example, the operating data is the data corresponding to the battery voltage. Set the fault trigger threshold corresponding to the operating data to 4.8V. Within the preset time, determine the number of times the collected operating data reaches 4.8V, which is the fault frequency. Determine the duration corresponding to each time the operating data reaches 4.8V, and the duration is the fault duration. If the fault frequency is not once, and at least two durations are determined, the maximum duration is used as the fault duration.

[0047] S130 , determining a target fault type of the component to be detected according to the fault duration and fault frequency in the analysis result and predetermined benchmark reference data corresponding to the component to be detected.

[0048] Among them, the benchmark reference data may be a preset benchmark data. Optionally, the benchmark reference data may be a preset fault number threshold. The target fault type may include a continuous fault type and an intermittent fault type. If the fault of the component to be detected lasts for a long time, the target fault type of the component to be detected may be determined as a continuous fault type. For example, if the fault of the component to be detected lasts for 5 minutes and reaches the preset time, the target fault type may be a continuous fault type. If the fault of the component to be detected lasts for a short time and occurs randomly and intermittently, when the fault frequency reaches the benchmark reference data, the target fault type may be determined to be an intermittent fault type. For example, the intermittent fault type may be a short circuit, an open circuit, a short circuit to ground, or a short circuit to power supply of the component to be detected. This embodiment does not specifically limit the intermittent fault type.

[0049] Specifically, according to the fault duration and the preset duration in the analysis result, determine whether the fault duration reaches the preset duration. If the fault duration reaches the preset duration, the target fault type of the component to be detected is a continuous fault type. If the fault duration does not reach the preset duration, and the fault frequency within the preset duration reaches the benchmark reference data, the target fault type of the component to be detected is an intermittent fault type. Based on this, the target fault type of the component to be detected under different circumstances can be accurately known, and accurate fault detection can be achieved.

[0050] S140: When the target fault type is a preset fault type, determine the troubleshooting information corresponding to the component to be detected.

[0051] The preset fault type may be a preset fault type. The preset fault type may be a continuous fault type or an intermittent fault type. Different fault types have different processing methods and corresponding troubleshooting information. The troubleshooting information may be information obtained after troubleshooting each part of the component to be inspected one by one.

[0052] Specifically, when it is determined that the target fault type is a preset fault type, the information corresponding to the target fault type is fed back to the target terminal, so that the target terminal reminds the corresponding personnel to check and process each part in the inspected component one by one according to the feedback information to obtain the corresponding troubleshooting information.

[0053] Optionally, the method also includes: recording the operating data of the component to be detected, the analysis results corresponding to the operating data, and the troubleshooting information of the component to be detected in a fault detection list, so that when the operating data of the component to be processed is detected, the troubleshooting information of the component to be processed is determined based on the fault detection list.

[0054] The fault detection list can be used to record the corresponding operation data, analysis results and troubleshooting information within a preset time period each time a fault detection is performed. The fault detection list can shorten the subsequent fault detection time.

[0055] Specifically, the operation data corresponding to the current preset time, the analysis results corresponding to the operation data, and the troubleshooting information of the components to be detected are recorded in the fault detection list. According to the fault detection list, when the operation data of the components to be processed are obtained later, the analysis results and troubleshooting information corresponding to the operation data can be determined according to the operation data of the components to be processed, so as to simplify the subsequent fault troubleshooting process.

[0056] Optionally, the method further includes: for a target device integrating at least one component to be detected, optimizing the target device based on the troubleshooting information corresponding to each component to be detected to obtain an optimized target device.

[0057] Among them, at least one component to be detected may be integrated in the target device. For example, taking the target device as a new energy vehicle, the components to be detected integrated in the target device may include a battery, a vehicle control unit (VCU) or a speed sensor. This is only an example and does not limit the specific target device.

[0058] Specifically, for a target device that integrates at least one component to be detected, based on the above-mentioned fault detection method, each component to be detected can be fault-detected, and the corresponding target fault type and the troubleshooting information corresponding to the target fault type can be determined. The target device is repaired or adjusted according to the troubleshooting information corresponding to each component to be detected to obtain an optimized target device so that the target device can operate normally and stably.

[0059] The technical solution of this embodiment provides data support for subsequent data processing by obtaining the operating data of the component to be detected under at least one acquisition indicator. According to the operating data obtained within a preset time length, the analysis result of the operating data is determined, so as to determine whether the component to be detected has a fault according to the analysis result. According to the duration of the fault and the frequency of the fault in the analysis result, and the predetermined benchmark reference data corresponding to the component to be detected, the target fault type of the component to be detected is determined. When the target fault type is a preset fault type, the troubleshooting information corresponding to the component to be detected is determined to realize the troubleshooting and processing of the component to be detected. The present invention solves the problem of inaccurate fault detection in the prior art and realizes accurate detection of faults. By troubleshooting the component to be detected according to the target fault type, the fault existing in the component to be detected can be discovered in time, so that the component to be detected can operate normally.

[0060] Embodiment 2

[0061] Figure 3 1 is a flowchart of a fault detection method provided by Embodiment 2 of the present invention. This embodiment is a preferred embodiment of the above embodiment. The specific implementation method can refer to the technical solution of this embodiment. Among them, the technical terms that are the same or corresponding to the above embodiment are not repeated here. Figure 3 As shown, the method includes:

[0062] S210: Acquire operating data of a component to be inspected under at least one acquisition indicator.

[0063] S220: Within a preset time period, the operation data is detected based on a preset detection frequency to determine the fault frequency at which the operation data reaches a preset fault trigger threshold.

[0064] The preset detection frequency may be set according to actual needs and may be a detection frequency within a preset time period. For example, the preset detection frequency may be 50 times per second, that is, the operation data needs to be detected once every 0.02 seconds.

[0065] Specifically, within a preset time period, the operation data is detected according to a preset detection frequency to determine the fault frequency at which the operation data reaches a preset fault trigger threshold.

[0066] Exemplarily, taking the preset duration of 4 seconds as an example, the preset detection frequency can be 50 times per second, and 200 times can be detected within the preset duration. That is, within the preset duration, it is determined every 0.02 seconds whether the operating data reaches the preset fault trigger threshold. If the operating data reaches the preset fault trigger threshold, the fault frequency is counted as 1 time until the fault frequency reaches the preset fault number threshold. If the fault frequency reaches the preset fault number threshold within the preset duration, the fault detection can be stopped, the identifier used to mark the fault state is set to Fail, and the target fault type is determined. If the fault frequency does not reach the preset fault number threshold within the preset duration, it is determined that no fault has occurred at present, the identifier used to identify the fault state is set to Pass, and the next fault detection within the preset duration is started.

[0067] S230: Determine at least one duration to be analyzed corresponding to when the operating data reaches a preset fault trigger threshold within a preset duration.

[0068] The duration to be analyzed may be the duration when the operating data reaches a preset fault triggering threshold.

[0069] Specifically, when the component to be detected is detected according to the preset detection frequency within the preset time period, at least one duration to be analyzed corresponding to each time when the operation data reaches the preset fault trigger threshold is determined. The target fault type of the component to be detected is determined according to the at least one duration to be analyzed.

[0070] S240: Determine the fault duration of the component to be detected based on at least one duration to be analyzed.

[0071] Specifically, the maximum duration to be analyzed is determined from at least one duration to be analyzed corresponding to the component to be detected, and the maximum duration to be analyzed is used as the fault duration, so as to determine the target fault type of the component to be detected according to the fault duration.

[0072] Optionally, based on at least one duration to be analyzed, determining the fault duration of the component to be detected includes: determining the maximum duration to be analyzed corresponding to the at least one duration to be analyzed, and using the maximum duration to be analyzed as the fault duration of the component to be detected.

[0073] Specifically, the size corresponding to at least one duration to be analyzed is compared, a maximum duration to be analyzed is determined from the at least one duration to be analyzed, and the maximum duration to be analyzed is used as the fault duration. Based on this, the target fault type of the component to be detected can be determined by determining whether the maximum duration to be analyzed meets the condition.

[0074] In the case where the benchmark reference data is a preset fault number threshold, the target fault type can be determined as follows: S250: If the fault duration reaches a preset duration, determine that the target fault type of the component to be detected is a continuous fault type.

[0075] Specifically, when the fault duration reaches a preset duration, the target fault type of the component to be detected is determined to be a continuous fault type, so that the component to be detected is checked and processed according to the current target fault type to achieve optimization of the component to be detected.

[0076] S260: If the duration of the fault does not reach the preset duration and the fault frequency reaches the preset fault frequency threshold, determine that the target fault type of the component to be detected is an intermittent fault type.

[0077] Specifically, if the duration of the fault does not reach the preset duration, and the fault frequency reaches the preset fault number threshold, it is determined that the target fault type of the component to be detected is an intermittent fault type. Correspondingly, if the duration of the fault does not reach the preset duration, and the fault frequency does not reach the preset fault number threshold, it is determined that the component to be detected does not have a fault.

[0078] For example, see Figure 4 , Figure 4 This is an example of a broken line graph corresponding to the fault frequency. The total number of detections is determined based on the preset duration and the preset detection frequency. In combination with the above example, if it is determined every 0.02 seconds whether the operating data has reached the preset fault trigger threshold, when the operating data reaches the preset fault trigger threshold, the fault frequency is counted as 1, the total number of detections is counted as 1, and the duration of analysis for the operating data to reach the preset fault trigger threshold is determined. When the operating data does not reach the preset fault trigger threshold, the fault frequency is not counted, and the total number of detections is counted as 1. And, by Figure 4 It can be seen that within the preset time length, after the fault frequency reaches the preset fault number threshold, the current fault detection can be ended and the target fault type can be determined, that is, the target fault type is determined to be an intermittent fault type. If within the preset time length, the fault frequency does not reach the preset fault number threshold, it is determined that there is no fault in the component to be detected. In addition, the duration corresponding to when the fault frequency reaches the preset fault number threshold within the preset time length can be determined, and the duration and the preset duration can be recorded in the fault detection list to facilitate subsequent inquiries.

[0079] S270. When the target fault type is a preset fault type, generate warning prompt information based on the target fault type, and feed back the warning prompt information to the target terminal, so that the target terminal determines the troubleshooting information corresponding to the component to be detected based on the warning prompt information.

[0080] The warning information may be information generated according to the target fault type. The warning information may be displayed on the target terminal in the form of voice, text or other means. For example, taking the target device as a new energy vehicle, the warning information may be fault information displayed at a preset position on the vehicle display screen. The target terminal may be a pre-set display component, for example, the target terminal may be a display terminal of a new energy vehicle.

[0081] Specifically, when the target fault type is a preset fault type, early warning prompt information is generated according to the target fault type, and the early warning prompt information is sent to the target terminal, so that the target terminal performs an early warning reminder according to the early warning prompt information, thereby determining the troubleshooting information corresponding to the component to be detected.

[0082] For example, Figure 2 As shown, in combination with the above example, after the processing chip processes the raw data collected by the acquisition chip, the target fault type and the early warning prompt information corresponding to the target fault type are obtained. The early warning prompt information is transmitted to the vehicle terminal through the controller local area network chip to realize the troubleshooting of the components to be detected. It should be noted that when the early warning prompt information is transmitted to the vehicle terminal, the fault frequency, fault duration and other information stored in the processing chip are cleared, and the fault detection of the next preset duration is restarted.

[0083] The technical solution of this embodiment provides data support for subsequent data processing by acquiring the operating data of the component to be detected under at least one acquisition indicator. Within the preset time length, the operating data is detected based on the preset detection frequency to determine the fault frequency of the operating data reaching the preset fault trigger threshold, and at least one duration to be analyzed corresponding to the operating data reaching the preset fault trigger threshold within the preset time length. According to at least one duration to be analyzed, the duration of the fault of the component to be detected is determined. Based on this, it is convenient to determine the target fault type based on the subsequent fault frequency and fault duration. If the fault duration reaches the preset duration, the target fault type of the component to be detected is determined to be a continuous fault type; if the fault duration does not reach the preset duration, and the fault frequency reaches the preset fault number threshold, the target fault type of the component to be detected is determined to be an intermittent fault type. When the target fault type is a preset fault type, an early warning prompt information is generated based on the target fault type, and the early warning prompt information is fed back to the target terminal, so that the target terminal determines the troubleshooting information corresponding to the component to be detected based on the early warning prompt information, so as to realize the troubleshooting and processing of the component to be detected. The present invention solves the problem of inaccurate fault detection in the prior art and realizes accurate fault detection. By troubleshooting the components to be detected according to the target fault type, the faults existing in the components to be detected can be found in time, so that the components to be detected can operate normally.

[0084] Embodiment 3

[0085] Figure 5 Schematic diagram of a fault detection device provided by Embodiment 3 of the present invention. Figure 5 As shown, the device includes: a data acquisition module 310, a data analysis module 320, a fault type determination module 330 and a troubleshooting information determination module 340.

[0086] The data acquisition module 310 is used to acquire the operating data of the component to be detected under at least one acquisition indicator; the data analysis module 320 is used to determine the analysis result of the operating data based on the operating data acquired within a preset time period; wherein the analysis result includes the fault duration and fault frequency of the component to be detected within the preset time period; the fault type determination module 330 is used to determine the target fault type of the component to be detected based on the fault duration and fault frequency in the analysis result, and the predetermined benchmark reference data corresponding to the component to be detected; the troubleshooting information determination module 340 is used to determine the troubleshooting information corresponding to the component to be detected when the target fault type is a preset fault type.

[0087] The technical solution of this embodiment provides data support for subsequent data processing by obtaining the operating data of the component to be detected under at least one acquisition indicator. According to the operating data obtained within a preset time length, the analysis result of the operating data is determined, so as to determine whether the component to be detected has a fault according to the analysis result. According to the duration of the fault and the frequency of the fault in the analysis result, and the predetermined benchmark reference data corresponding to the component to be detected, the target fault type of the component to be detected is determined. When the target fault type is a preset fault type, the troubleshooting information corresponding to the component to be detected is determined to realize the troubleshooting and processing of the component to be detected. The present invention solves the problem of inaccurate fault detection in the prior art and realizes accurate detection of faults. By troubleshooting the component to be detected according to the target fault type, the fault existing in the component to be detected can be discovered in time, so that the component to be detected can operate normally.

[0088] On the basis of the above embodiment, optionally, the data acquisition module includes: a raw data acquisition unit, which is used to acquire the raw data collected by at least one data acquisition sensor deployed at a preset position of the component to be detected when it is determined that the data acquisition conditions are met; a data cleaning unit, which is used to perform data cleaning processing on the raw data to obtain operating data corresponding to at least one acquisition indicator.

[0089] Optionally, the data analysis module includes: a fault frequency determination unit, which is used to detect the operating data based on a preset detection frequency within a preset time period, and determine the fault frequency at which the operating data reaches a preset fault trigger threshold; a duration determination unit for analysis, which is used to determine at least one duration for analysis corresponding to when the operating data reaches the preset fault trigger threshold within the preset time period; and a fault duration determination unit, which is used to determine the fault duration of the component to be detected based on at least one duration for analysis.

[0090] Optionally, the fault duration determination unit is used to determine a maximum duration to be analyzed corresponding to at least one duration to be analyzed, and use the maximum duration to be analyzed as the fault duration of the component to be detected.

[0091] Optionally, the benchmark reference data is a preset fault number threshold, and the fault type determination module is used to determine that the target fault type of the component to be detected is a continuous fault type if the fault duration reaches a preset duration; if the fault duration does not reach the preset duration and the fault frequency reaches a preset fault number threshold, then the target fault type of the component to be detected is determined to be an intermittent fault type.

[0092] Optionally, a troubleshooting information determination module is used to generate early warning prompt information based on the target fault type when the target fault type is a preset fault type, and to feed back the early warning prompt information to the target terminal, so that the target terminal determines the troubleshooting information corresponding to the component to be detected based on the early warning prompt information.

[0093] Optionally, the device also includes: a data recording module, used to record the operating data of the component to be detected, the analysis results corresponding to the operating data, and the troubleshooting information of the component to be detected in a fault detection list, so that when the operating data of the component to be processed is detected, the troubleshooting information of the component to be processed is determined based on the fault detection list.

[0094] Optionally, the apparatus further includes: a target device optimization module, configured to optimize the target device integrating at least one component to be detected based on the troubleshooting information corresponding to each component to be detected, so as to obtain an optimized target device.

[0095] The fault detection device provided in the embodiment of the present invention can execute the fault detection method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0096] Embodiment 4

[0097] Figure 61 is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0098] like Figure 6 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0099] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0100] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a fault detection method.

[0101] In some embodiments, the fault detection method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the fault detection method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the fault detection method in any other appropriate manner (e.g., by means of firmware).

[0102] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0103] The computer program for implementing the fault detection method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.

[0104] Embodiment 5

[0105] Embodiment 5 of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a processor to execute a fault detection method, the method comprising:

[0106] Obtain operating data of a component to be detected under at least one acquisition indicator; determine analysis results of the operating data based on the operating data acquired within a preset time period; wherein the analysis results include fault duration and fault frequency of the component to be detected within the preset time period; determine a target fault type of the component to be detected based on the fault duration and fault frequency in the analysis results, and predetermined benchmark reference data corresponding to the component to be detected; when the target fault type is a preset fault type, determine troubleshooting information corresponding to the component to be detected.

[0107] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0108] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0109] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0110] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0111] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0112] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A fault detection method, characterized in that: Applied to a controller and at least one component to be detected that communicates with the controller, the controller is used to obtain operating data of the component to be detected and process the operating data, the method comprising: Acquire operating data of the component to be detected under at least one acquisition indicator; Determine the analysis result of the operation data according to the operation data acquired within the preset time; wherein the analysis result includes the duration of the fault and the frequency of the fault of the component to be detected within the preset time; Determine the target fault type of the component to be detected according to the fault duration and the fault frequency in the analysis result and the predetermined benchmark reference data corresponding to the component to be detected; When the target fault type is a preset fault type, the troubleshooting information corresponding to the component to be detected is determined.

2. The method according to claim 1, characterized in that The obtaining of the operating data of the component to be detected under at least one acquisition indicator includes: When it is determined that the data acquisition condition is met, acquiring raw data collected by at least one data acquisition sensor deployed at a preset position of the component to be inspected; The raw data is cleaned to obtain operating data corresponding to at least one acquisition indicator.

3. The method according to claim 1, characterized in that: Determining the analysis result of the operation data according to the operation data acquired within the preset time period includes: Within the preset time period, the operation data is detected based on a preset detection frequency to determine the fault frequency at which the operation data reaches a preset fault trigger threshold; Determine at least one duration to be analyzed corresponding to when the operation data reaches the preset fault trigger threshold within the preset duration; Based on at least one of the durations to be analyzed, a duration of a fault of the component to be detected is determined.

4. The method according to claim 3, characterized in that The determining, based on at least one of the durations to be analyzed, the duration of the fault of the component to be detected comprises: A maximum duration to be analyzed corresponding to at least one of the durations to be analyzed is determined, and the maximum duration to be analyzed is used as the fault duration of the component to be detected.

5. The method according to claim 1, characterized in that The benchmark reference data is a preset fault number threshold, and the target fault type of the component to be detected is determined according to the fault duration and the fault frequency in the analysis result and the predetermined benchmark reference data corresponding to the component to be detected, including: If the duration of the fault reaches the preset duration, determining that the target fault type of the component to be detected is a continuous fault type; If the duration of the fault does not reach the preset duration, and the fault frequency reaches the preset fault frequency threshold, it is determined that the target fault type of the component to be detected is an intermittent fault type.

6. The method according to claim 1, characterized in that When the target fault type is a preset fault type, determining the troubleshooting information corresponding to the component to be detected includes: When the target fault type is a preset fault type, early warning prompt information is generated based on the target fault type, and the early warning prompt information is fed back to the target terminal, so that the target terminal determines the troubleshooting information corresponding to the component to be detected based on the early warning prompt information.

7. The method according to claim 1, characterized in that Also includes: The operating data of the component to be detected, the analysis results corresponding to the operating data, and the troubleshooting information of the component to be detected are recorded in a fault detection list, so that when the operating data of the component to be processed is detected, the troubleshooting information of the component to be processed is determined based on the fault detection list.

8. The method according to claim 1, characterized in that Also includes: For a target device that integrates at least one of the components to be detected, the target device is optimized based on the troubleshooting information corresponding to each component to be detected to obtain an optimized target device.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the fault detection method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the fault detection method according to any one of claims 1 to 8 when executed.

Images