Fault analysis method and device of electric drive system, electronic equipment and storage medium

By linking vehicle information with cloud data and using the electric drive failure database to identify fault paths and key signals, a fault tree and troubleshooting path are generated. This solves the problem of electric drive system fault diagnosis relying on manual intervention and enables rapid and accurate fault analysis and diagnosis.

CN121973628APending Publication Date: 2026-05-05CHINA FAW CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511871112.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-11
Publication Date
2026-05-05

AI Technical Summary

Technical Problem

In existing technologies, fault diagnosis of electric drive systems relies on the manual intervention of technicians, which limits the speed and accuracy of fault location to professional experience and technical level, increases the cost of manual judgment and increases the error rate, making it difficult to meet the needs of rapid and accurate diagnosis.

Method used

By acquiring vehicle information of faulty vehicles and associating it with cloud data, fault information is generated. The fault path and key signals are identified using the electric drive failure database, a fault tree and troubleshooting path are generated, and abnormal signal data points are exported, enabling visualization and standardized guidance of faults and reducing reliance on the experience of technical personnel.

Benefits of technology

It enables accurate generation of fault information, avoids blind fault analysis, improves the efficiency and consistency of fault diagnosis, provides quantitative evidence of the root cause of the problem, lays the foundation for fault data accumulation and performance optimization, and enhances the scientificity, efficiency and operability of electric drive system fault analysis.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121973628A_ABST
    Figure CN121973628A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of fault diagnosis, in particular to a fault analysis method and device for an electric drive system, electronic equipment and a storage medium, and the method comprises the steps: obtaining the vehicle information of a faulty vehicle, generating the fault information of the faulty vehicle based on the vehicle information and corresponding cloud data, and storing the fault information of the faulty vehicle. According to the fault information, a fault path and a corresponding key signal are determined so as to identify an abnormal point, then a plurality of failure paths corresponding to an electric drive fault are generated based on the abnormal point, a fault tree and a troubleshooting path are output, and a corresponding abnormal signal data point is exported so as to determine a problem true cause. Therefore, the problems that related technologies depend on manual intervention of related technicians, the fault positioning speed and accuracy are limited by professional experience and technical level of the related technicians, the manual judgment cost is increased, the error rate is increased due to subjective judgment deviation, the troubleshooting efficiency is reduced, and the fault positioning accuracy is reduced are solved. And the requirements of rapid and accurate diagnosis of the electric drive system are difficult to meet.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of fault diagnosis technology, and in particular to a fault analysis method, apparatus, electronic device and storage medium for an electric drive system. Background Technology

[0002] With the rapid development of the new energy vehicle industry, its ownership is increasing rapidly. As a core power component of new energy vehicles, the electric drive system's safety and reliability directly determine the vehicle's operational capability and are crucial for maintaining normal vehicle operation. Under actual operating conditions, the electric drive system is susceptible to various abnormal operating conditions that can lead to malfunctions. The factors that induce malfunctions are complex and diverse, such as abnormalities in the low-voltage power supply system and abnormal operating conditions of the cooling system, all of which can cause the electric drive system to fail.

[0003] Among related technologies, some involve using diagnostic tools to scan the vehicle's electronic control unit, obtaining fault codes to identify the fault phenomenon, and then extracting key signal data based on the fault phenomenon. By marking outliers in the data, an identifier bit is generated. When the identifier bit meets certain trigger conditions, the current vehicle status data is recorded. Technicians then use diagnostic equipment and standard testing procedures to collect fault diagnosis signals, generate a signal list, and deduce the cause of the fault by analyzing the vehicle status data and the signal list.

[0004] However, in related technologies, fault diagnosis relies on the manual intervention of relevant technical personnel, which limits the speed and accuracy of fault location to the professional experience and technical level of the relevant technical personnel. This not only increases the cost of manual judgment, but also increases the error rate due to subjective judgment bias, reduces the efficiency of fault diagnosis, and makes it difficult to meet the needs of rapid and accurate diagnosis of electric drive systems, which urgently needs to be solved. Summary of the Invention

[0005] This application provides a fault analysis method, apparatus, electronic device, and storage medium for an electric drive system to address the problem that related technologies rely on manual intervention by technical personnel, which limits the speed and accuracy of fault location to the professional experience and technical level of the technical personnel. This not only increases the cost of manual judgment but also increases the error rate due to subjective judgment bias, reduces the efficiency of fault diagnosis, and makes it difficult to meet the needs of rapid and accurate diagnosis of electric drive systems.

[0006] The first aspect of this application provides a fault analysis method for an electric drive system, comprising the following steps: acquiring vehicle information of a faulty vehicle; generating fault information of the faulty vehicle based on the vehicle information and corresponding cloud data, so as to determine the fault path and corresponding key signals according to the fault information, so as to identify at least one abnormal point; generating multiple failure paths corresponding to electric drive faults based on the at least one abnormal point, and outputting a fault tree and troubleshooting path, and exporting the corresponding abnormal signal data points to determine the root cause of the problem.

[0007] Based on the above technical means, this application embodiment achieves accurate generation of fault information by associating vehicle information with cloud data, avoiding the blindness of fault analysis. Then, by matching fault paths with key signals, it achieves accurate location of anomalies, greatly reducing the reliance on the experience of technical personnel. Furthermore, by generating failure paths, fault trees, and troubleshooting paths, it transforms abstract fault logic into a visual and standardized guiding tool, improving the efficiency and consistency of fault troubleshooting. At the same time, by exporting abnormal signal data points, it provides a quantitative basis for the accurate confirmation of the root cause of the problem, and also lays the foundation for the accumulation of fault data of the electric drive system and subsequent performance optimization, thereby improving the scientificity, efficiency, and operability of electric drive system fault analysis.

[0008] Optionally, in one embodiment of this application, generating fault information of the faulty vehicle based on the vehicle information and corresponding cloud data includes: obtaining original cloud fault data based on the vehicle information and performing data format conversion to obtain the cloud data; determining whether there is an electric drive fault based on the cloud data; and if there is an electric drive fault, obtaining the fault information according to the electric drive fault code table.

[0009] Based on the above technical means, the embodiments of this application determine whether there is an electric drive failure by using cloud data, which can effectively eliminate the interference of non-electric drive system failures, narrow the scope of failure analysis, and parse the failure information by using the electric drive fault code table to transform the abstract fault code into specific electric drive fault types and related information, thereby constructing a standardized and process-oriented fault information generation link, which greatly reduces the reliance on human experience in the initial fault judgment and improves the efficiency and accuracy of fault information acquisition.

[0010] Optionally, in one embodiment of this application, determining the fault path and corresponding key signals based on the fault information to identify at least one abnormal point includes: confirming the fault path using the electric drive failure database based on the fault information; identifying the key signals of the fault path and matching a fault judgment threshold based on the key signals; and determining the at least one abnormal point based on the fault judgment threshold.

[0011] Based on the above technical means, the embodiments of this application provide a reliable basis for fault path confirmation by utilizing the historical failure patterns of the electric drive failure database, avoiding the blindness of fault investigation, and achieving accurate location of anomalies through quantitative comparison of key signals and thresholds, greatly reducing the error caused by subjective human judgment, and improving the scientificity and practicality of electric drive system fault analysis.

[0012] Optionally, in one embodiment of this application, the method further includes updating the electric drive failure database based on the root cause of the problem.

[0013] Based on the above technical means, the embodiments of this application fill the data coverage gaps of new and special working condition failures by updating the electric drive failure database, thereby improving the database adaptability. In addition, a self-optimization closed loop of fault analysis and database is constructed to reduce the dependence on human experience and improve the overall intelligence level of the system.

[0014] A second aspect of this application provides a fault analysis device for an electric drive system, comprising: an acquisition module for acquiring vehicle information of a faulty vehicle; an identification module for generating fault information of the faulty vehicle based on the vehicle information and corresponding cloud data, to determine fault paths and corresponding key signals based on the fault information, so as to identify at least one anomaly; and an analysis module for generating multiple failure paths corresponding to electric drive faults based on the at least one anomaly, outputting a fault tree and troubleshooting paths, and exporting corresponding abnormal signal data points to determine the root cause of the problem.

[0015] Based on the above technical means, this application embodiment achieves accurate generation of fault information by associating vehicle information with cloud data, avoiding the blindness of fault analysis. Then, by matching fault paths with key signals, it achieves accurate location of anomalies, greatly reducing the reliance on the experience of technical personnel. Furthermore, by generating failure paths, fault trees, and troubleshooting paths, it transforms abstract fault logic into a visual and standardized guiding tool, improving the efficiency and consistency of fault troubleshooting. At the same time, by exporting abnormal signal data points, it provides a quantitative basis for the accurate confirmation of the root cause of the problem, and also lays the foundation for the accumulation of fault data of the electric drive system and subsequent performance optimization, thereby improving the scientificity, efficiency, and operability of electric drive system fault analysis.

[0016] Optionally, in one embodiment of this application, the identification module includes: an acquisition unit, configured to acquire original cloud-based fault data based on the vehicle information and perform data format conversion to obtain the cloud-based data; a judgment unit, configured to determine whether there is an electric drive fault based on the cloud-based data; and a generation unit, configured to obtain the fault information according to the electric drive fault code table if there is an electric drive fault.

[0017] Based on the above technical means, the embodiments of this application determine whether there is an electric drive failure by using cloud data, which can effectively eliminate the interference of non-electric drive system failures, narrow the scope of failure analysis, and parse the failure information by using the electric drive fault code table to transform the abstract fault code into specific electric drive fault types and related information, thereby constructing a standardized and process-oriented fault information generation link, which greatly reduces the reliance on human experience in the initial fault judgment and improves the efficiency and accuracy of fault information acquisition.

[0018] Optionally, in one embodiment of this application, the identification module includes: a first determining unit, configured to confirm the fault path based on the fault information using the electric drive failure database; an identification unit, configured to identify key signals of the fault path and match a fault judgment threshold according to the key signals; and a second determining unit, configured to determine the at least one abnormal point according to the fault judgment threshold.

[0019] Based on the above technical means, the embodiments of this application provide a reliable basis for fault path confirmation by utilizing the historical failure patterns of the electric drive failure database, avoiding the blindness of fault investigation, and achieving accurate location of anomalies through quantitative comparison of key signals and thresholds, greatly reducing the error caused by subjective human judgment, and improving the scientificity and practicality of electric drive system fault analysis.

[0020] Optionally, in one embodiment of this application, it further includes: an update module, used to update the electric drive failure database based on the root cause of the problem.

[0021] Based on the above technical means, the embodiments of this application fill the data coverage gaps of new and special working condition failures by updating the electric drive failure database, thereby improving the database adaptability. In addition, a self-optimization closed loop of fault analysis and database is constructed to reduce the dependence on human experience and improve the overall intelligence level of the system.

[0022] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the fault analysis method for an electric drive system as described in the above embodiments.

[0023] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described fault analysis method for an electric drive system.

[0024] A fifth aspect of this application provides a computer program product, including a computer program that, when executed, implements the above-described fault analysis method for an electric drive system.

[0025] This application's embodiments achieve accurate generation of fault information by associating vehicle information with cloud data, avoiding the blindness of fault analysis. Then, by matching fault paths with key signals, it achieves precise location of anomalies, significantly reducing reliance on the experience of technical personnel. Furthermore, by generating failure paths, fault trees, and troubleshooting paths, it transforms abstract fault logic into visualized and standardized guidance tools, improving the efficiency and consistency of fault diagnosis. Simultaneously, by exporting abnormal signal data points, it provides quantitative evidence for the accurate confirmation of the root cause of the problem and lays the foundation for the accumulation of fault data in the electric drive system and subsequent performance optimization, enhancing the scientific rigor, efficiency, and operability of electric drive system fault analysis. Therefore, it solves the problem that related technologies rely on the manual intervention of technical personnel, resulting in the speed and accuracy of fault location being limited by the professional experience and technical level of these personnel. This not only increases the cost of manual judgment but also increases the error rate due to subjective judgment bias, reducing fault diagnosis efficiency and failing to meet the needs of rapid and accurate diagnosis of electric drive systems.

[0026] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0027] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart of a fault analysis method for an electric drive system provided according to an embodiment of this application; Figure 2 This is a flowchart illustrating the principle of a fault analysis method for an electric drive system according to an embodiment of this application. Figure 3 This is a block diagram of a fault analysis device for an electric drive system provided according to an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application.

[0028] Figure label: 30 - Fault analysis device for electric drive system; 100 - Acquisition module, 200 - Identification module, 300 - Analysis module; 401 - Memory, 402 - Processor, 403 - Communication interface. Detailed Implementation

[0029] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0030] The following description, with reference to the accompanying drawings, outlines a fault analysis method, apparatus, electronic device, and storage medium for an electric drive system according to embodiments of this application. Addressing the issues mentioned in the background section, where related technologies rely on manual intervention by skilled personnel, resulting in fault location speed and accuracy limited by their professional experience and technical level, this method not only increases manual judgment costs but also raises the error rate due to subjective judgment bias, reducing fault troubleshooting efficiency and failing to meet the needs for rapid and accurate diagnosis of electric drive systems. This application provides a fault analysis method for an electric drive system. In this method, the precise generation of fault information is achieved through the association of vehicle information and cloud data, avoiding blind fault analysis. Furthermore, the precise location of anomalies is achieved by matching fault paths with key signals, significantly reducing reliance on the experience of skilled personnel. By generating failure paths, fault trees, and troubleshooting paths, abstract fault logic is transformed into visualized and standardized guidance tools, improving the efficiency and consistency of fault troubleshooting. Simultaneously, by exporting abnormal signal data points, quantitative evidence is provided for the accurate confirmation of the root cause of the problem, laying the foundation for the accumulation of fault data and subsequent performance optimization of the electric drive system, thereby enhancing the scientific rigor, efficiency, and operability of electric drive system fault analysis. This solves the problem that the reliance on manual intervention by relevant technical personnel in related technologies leads to the speed and accuracy of fault location being limited by the professional experience and technical level of these personnel. This not only increases the cost of manual judgment but also increases the error rate due to subjective judgment bias, reduces the efficiency of fault diagnosis, and makes it difficult to meet the needs of rapid and accurate diagnosis of electric drive systems.

[0031] Specifically, Figure 1 This is a flowchart of a fault analysis method for an electric drive system provided according to an embodiment of this application.

[0032] like Figure 1 As shown, the fault analysis method for this electric drive system includes the following steps: In step S101, vehicle information of the faulty vehicle is obtained.

[0033] In the embodiments of this application, a faulty vehicle can be understood as a specific vehicle among new energy vehicles equipped with an electric drive system, which is identified as having abnormal electric drive system operating parameters, a fault related to the electric drive system, or a suspected electric drive system fault, based on feedback from after-sales technicians or through cloud-based early warning monitoring.

[0034] In addition, vehicle information can be understood as a set of identifying information used to uniquely identify a faulty vehicle and to clearly define the background of the fault. This may include, but is not limited to, the faulty vehicle model (such as the model of the electric drive system configured in the vehicle, the version of the vehicle's power architecture), the location of the fault, and the time of the fault.

[0035] In actual implementation, the embodiments of this application can collect and confirm vehicle information of the faulty vehicle through feedback from after-sales technical personnel or cloud-based early warning monitoring. The vehicle information may include, but is not limited to, the faulty vehicle model, the fault location, and the fault time.

[0036] In step S102, fault information of the faulty vehicle is generated based on vehicle information and corresponding cloud data, so as to determine the fault path and corresponding key signals according to the fault information, and to identify at least one abnormal point.

[0037] In the embodiments of this application, cloud data can be understood as the set of operating data collected in real time by on-board terminals such as the vehicle electric drive system controller (such as the motor control unit), sensors and vehicle controller during the driving and parking process of the faulty vehicle and uploaded to the vehicle's back-end cloud server at a certain collection frequency. It may include, but is not limited to, the basic operating parameters of the electric drive system under normal operating conditions and the ErrCode (Error Code) signal under abnormal operating conditions of the electric drive system.

[0038] Fault information can be understood as a set of comprehensive information that characterizes the abnormal state of the electric drive system of a faulty vehicle. For example, by reading the ErrCode signal in the cloud data and comparing it with the electric drive fault code table, the specific fault type of the electric drive system and the initially associated components can be identified.

[0039] The fault path can be understood as the complete propagation link of an electric drive fault from the occurrence of the cause to the presentation of the fault phenomenon, based on the functional architecture and physical connection logic of the electric drive system, combined with historical fault cases and system topology relationships in the electric drive failure database. This may include, but is not limited to, physical component connection paths (such as the signal transmission path from the temperature sensor to the controller), as well as logical association paths at the functional level (such as the causal logic path of the cooling system failure leading to motor thermal runaway).

[0040] Key signals can be understood as the operating status signals of the electric drive system that are directly related to the generation, propagation, and manifestation of the fault in the confirmed fault path. These signals can be collected in real time by dedicated sensors or controllers of the electric drive system. Their types are strongly correlated with the fault path, such as temperature signals (stator temperature), electrical signals (low-voltage supply voltage), and mechanical signals (motor rotor speed). At the same time, each key signal is matched with a certain fault judgment threshold, which is calibrated by the design standards of the electric drive system and historical fault data. This application does not impose specific restrictions.

[0041] An anomaly can be understood as a specific physical component, signal monitoring node, or data transmission link in the electric drive system that has a functional or performance abnormality, located based on data from key signals and compared with fault judgment thresholds. For example, when the stator temperature exceeds the corresponding threshold, the corresponding anomaly could be the motor stator temperature sensor acquisition node or the cooling system water pump control module.

[0042] The following details how embodiments of this application generate fault information for a faulty vehicle based on vehicle information and corresponding cloud data, so as to determine the fault path and corresponding key signals based on the fault information, and to identify at least one abnormal point.

[0043] Specifically, in one embodiment of this application, generating fault information for a faulty vehicle based on vehicle information and corresponding cloud data includes: processing the original cloud fault data and performing data format conversion based on the vehicle information to obtain cloud data; determining whether there is an electric drive fault based on the cloud data; and obtaining fault information according to the electric drive fault code table if it is an electric drive fault.

[0044] In the embodiments of this application, the original cloud fault data can be understood as the set of original data related to the operation and fault of the electric drive system collected in real time by the vehicle terminal (including electric drive system controller, various sensors, vehicle controller, etc.) of the faulty vehicle before, during and after the fault occurs, according to certain collection rules and directly uploaded to the background cloud server without any format conversion, data cleaning and standardization processing.

[0045] Furthermore, the electric drive fault code table can be understood as a standardized mapping relationship table between ErrCode signals and specific fault information of the electric drive system, based on the design principles, functional architecture, fault mechanisms and historical fault statistics of the electric drive system. It may include, but is not limited to, ErrCode signals, fault-related components and preliminary fault characteristics. This application does not impose any specific limitations.

[0046] In actual implementation, this application embodiment can confirm whether there is an electric drive failure based on vehicle information and output specific fault information: First, based on the vehicle information, the target vehicle can be locked, the original cloud fault data of the target vehicle can be obtained, and then the original cloud fault data can be converted into a data format to obtain cloud data to adapt to the subsequent analysis standard. Then, the ErrCode signal (such as E1001) can be found and extracted from the cloud data to determine whether there is an electric drive failure. Then, when there is an electric drive failure, the electric drive fault code table can be queried to decode the ErrCode signal into specific fault information (such as abnormal cooling system temperature).

[0047] It should be noted that, in the case where it is difficult to obtain the original cloud-based fault data of the target vehicle, such as when the original cloud-based fault data is lost, the fault information can be manually supplemented in this embodiment of the application.

[0048] This application embodiment determines whether there is an electric drive failure by using cloud data, which can effectively eliminate interference from non-electric drive system failures, narrow the scope of failure analysis, and parse the fault information through the electric drive fault code table, transforming the abstract fault code into specific electric drive fault types and related information, constructing a standardized and process-oriented fault information generation link, greatly reducing the reliance on human experience in the initial fault judgment, and improving the efficiency and accuracy of fault information acquisition.

[0049] Furthermore, in one embodiment of this application, determining the fault path and corresponding key signals based on fault information to identify at least one anomaly includes: confirming the fault path using an electric drive failure database based on fault information; identifying key signals of the fault path and matching fault judgment thresholds based on the key signals; and determining at least one anomaly based on the fault judgment thresholds.

[0050] In the embodiments of this application, the electric drive failure database can be understood as a structured database of electric drive system fault association information that is pre-built and dynamically updated based on the design mechanism of the electric drive system, laboratory failure simulation test data, historical after-sales fault investigation cases and industry failure analysis results. It may include, but is not limited to, various types of electric drive system faults, typical fault paths corresponding to various faults, key signal characteristics associated with fault paths, and common distribution locations of fault anomalies. This application does not impose specific limitations.

[0051] Furthermore, the fault judgment threshold can be understood as a quantitative judgment benchmark for determining whether a signal is abnormal, which is pre-calibrated for each key signal of the electric drive system. Different thresholds can be set for different vehicle models, different electric drive system models, and different operating conditions (such as high-speed driving, low-temperature start-up, etc.) based on the design performance parameters of each component of the electric drive system, industry technical standards, and the safe operation requirements of the vehicle power system, as well as historical fault data in the electric drive failure database and laboratory extreme condition test data. This application does not impose specific restrictions.

[0052] In actual implementation, this application embodiment locks the fault path and identifies anomalies based on specific fault information: it can call the electric drive failure database, match fault information with the corresponding fault path, and then identify the key signals corresponding to the fault path to retrieve data and compare it with the fault judgment threshold to determine whether it is abnormal. For example, when the data of the key signal is greater than the fault judgment threshold, it is marked as an abnormal signal and the fault node data is output to form a screenshot of the fault time data. Then, based on the abnormal signal, the physical detection or control node corresponding to the abnormal signal is located to form an anomaly.

[0053] This application embodiment utilizes historical failure patterns from an electric drive failure database to provide a reliable basis for fault path confirmation, avoiding the blindness of fault investigation. Furthermore, it achieves precise location of anomalies through quantitative comparison of key signals and thresholds, significantly reducing errors caused by subjective human judgment and improving the scientific rigor and practicality of electric drive system fault analysis.

[0054] In step S103, based on at least one abnormal point, multiple failure paths corresponding to electric drive faults are generated, and a fault tree and troubleshooting path are output. The corresponding abnormal signal data points are also exported to determine the root cause of the problem.

[0055] In the embodiments of this application, the failure path can be understood as a complete causal link of the electric drive system from the generation of fault causes to the eventual functional failure, based on the physical architecture, signal transmission logic and failure mechanism of the electric drive system, combined with historical failure cases in the electric drive failure database.

[0056] A fault tree can be understood as a hierarchical and visualized fault association logic model constructed using logic gates (such as AND gates and OR gates), with the overall failure or specific fault phenomenon of the electric drive system as the top event, various failure paths as intermediate levels, and anomalies as bottom events. The top level of the model is the overall fault manifestation of the electric drive system (such as electric drive power interruption, motor overheat protection), the intermediate level is the specific failure path and fault type of the corresponding fault, and the bottom level is the specific anomaly at the end of the failure path.

[0057] The troubleshooting path can be understood as a standardized, step-by-step troubleshooting operation process based on the logical relationships of the fault tree and the transmission rules of the failure path, targeting different anomalies.

[0058] Abnormal signal data points can be understood as specific data records recorded by the cloud server where key signal data within the fault path of the electric drive system exceeds the fault judgment threshold. These records may include, but are not limited to, the timestamp of the fault trigger time, the signal acquisition frequency, and auxiliary information such as the operating conditions of the electric drive system associated with the signal (e.g., motor speed, vehicle speed).

[0059] In actual implementation, the embodiments of this application can generate multiple failure paths corresponding to electric drive faults based on multiple anomalies, so as to output a fault tree and troubleshooting path, and export the abnormal signal data points recorded in the cloud to determine the root cause of the problem.

[0060] Optionally, in one embodiment of this application, it further includes: updating the electric drive failure database based on the root cause of the problem.

[0061] In actual implementation, the embodiments of this application utilize a closed-loop iterative mechanism for fault analysis. After the cause of the fault is verified and confirmed, the core information such as the fault type, failure path, associated key signals, anomalies, and handling plan corresponding to the new fault is supplemented and entered into the database according to certain structured specifications.

[0062] This application embodiment fills the data coverage gaps of new and special operating condition faults by updating the electric drive failure database, improving the database adaptability. In addition, it constructs a self-optimization closed loop between fault analysis and database, reducing reliance on human experience and improving the overall intelligence level of the system.

[0063] The principle of the fault analysis method for the electric drive system proposed in this application is illustrated below with a specific embodiment.

[0064] Figure 2 This is a flowchart illustrating the principle of a fault analysis method for an electric drive system according to an embodiment of this application.

[0065] Step S201: Obtain vehicle information of the faulty vehicle.

[0066] In this embodiment of the application, vehicle information of the faulty vehicle can be collected and confirmed through feedback from after-sales technical personnel or cloud-based early warning monitoring. The vehicle information may include, but is not limited to, the faulty vehicle model, the fault location, and the fault time.

[0067] Step S202: Obtain cloud data.

[0068] In this embodiment, the target vehicle can be located first based on the vehicle information, the original cloud fault data of the target vehicle can be obtained, and then the original cloud fault data can be converted into a data format to obtain cloud data.

[0069] Step S203: Obtain fault information.

[0070] In this embodiment, the ErrCode signal can be searched and extracted from cloud data to determine whether there is an electric drive failure. Then, when there is an electric drive failure, the electric drive fault code table is queried to decode the ErrCode signal into specific fault information.

[0071] Step S204: Determine the fault path.

[0072] In this embodiment of the application, an electric drive failure database can be invoked to match fault information with the corresponding fault path.

[0073] Step S205: Identify anomalies.

[0074] In this embodiment, the key signal corresponding to the fault path can be identified to retrieve data and compare it with the fault judgment threshold to determine whether it is abnormal. For example, when the data of the key signal is greater than the fault judgment threshold, it is marked as an abnormal signal. Then, based on the abnormal signal, the physical detection or control node corresponding to the abnormal signal is located to form an abnormal point.

[0075] Step S206: Determine the root cause of the problem.

[0076] In this embodiment, multiple failure paths corresponding to electric drive faults can be generated based on multiple anomalies to output a fault tree and troubleshooting path, and abnormal signal data points recorded in the cloud can be exported to determine the root cause of the problem.

[0077] The fault analysis method for electric drive systems proposed in this application achieves accurate generation of fault information by associating vehicle information with cloud data, avoiding blind fault analysis. Furthermore, by matching fault paths with key signals, it achieves precise location of anomalies, significantly reducing reliance on the experience of technical personnel. By generating failure paths, fault trees, and troubleshooting paths, it transforms abstract fault logic into visualized and standardized guidance tools, improving the efficiency and consistency of fault diagnosis. Simultaneously, by exporting abnormal signal data points, it provides quantitative evidence for accurate confirmation of the root cause of the problem and lays the foundation for the accumulation of fault data and subsequent performance optimization of the electric drive system, enhancing the scientific rigor, efficiency, and operability of electric drive system fault analysis. This solves the problem that related technologies rely on the manual intervention of technical personnel, resulting in the speed and accuracy of fault location being limited by the professional experience and technical level of these personnel. This not only increases the cost of manual judgment but also increases the error rate due to subjective judgment bias, reducing fault diagnosis efficiency and failing to meet the needs of rapid and accurate diagnosis of electric drive systems.

[0078] Next, with reference to the accompanying drawings, a fault analysis apparatus for an electric drive system proposed according to an embodiment of this application is described.

[0079] Figure 3 This is a block diagram of a fault analysis device for an electric drive system provided according to an embodiment of this application.

[0080] like Figure 3 As shown, the fault analysis device 30 of the electric drive system includes: an acquisition module 100, an identification module 200, and an analysis module 300.

[0081] The acquisition module 100 is used to acquire vehicle information of the faulty vehicle.

[0082] The identification module 200 is used to generate fault information of the faulty vehicle based on vehicle information and corresponding cloud data, so as to determine the fault path and corresponding key signals according to the fault information, and to identify at least one abnormal point.

[0083] The analysis module 300 is used to generate multiple failure paths corresponding to electric drive faults based on at least one abnormal point, output a fault tree and troubleshooting path, and export the corresponding abnormal signal data points to determine the root cause of the problem.

[0084] Optionally, in one embodiment of this application, the identification module 200 includes: an acquisition unit, a judgment unit, and a generation unit.

[0085] The acquisition unit is used to acquire raw cloud-based fault data based on vehicle information and perform data format conversion to obtain cloud-based data.

[0086] The judgment unit is used to determine whether there is an electric drive malfunction based on cloud data.

[0087] The generation unit is used to obtain fault information based on the electric drive fault code table if the fault is an electric drive failure.

[0088] Optionally, in one embodiment of this application, the identification module 200 includes: a first determining unit, an identification unit, and a second determining unit.

[0089] The first determining unit is used to identify the fault path based on the fault information using the electric drive failure database.

[0090] The identification unit is used to identify key signals in the fault path and match fault judgment thresholds based on the key signals.

[0091] The second determining unit is used to determine at least one abnormal point based on the fault judgment threshold.

[0092] Optionally, in one embodiment of this application, it further includes: an update module for updating the electric drive failure database based on the root cause of the problem.

[0093] It should be noted that the foregoing explanation of the fault analysis method embodiment for the electric drive system also applies to the fault analysis device for the electric drive system in this embodiment, and will not be repeated here.

[0094] The fault analysis device for electric drive systems proposed in this application achieves accurate generation of fault information by associating vehicle information with cloud data, avoiding blind fault analysis. Furthermore, by matching fault paths with key signals, it achieves precise location of anomalies, significantly reducing reliance on the experience of technical personnel. By generating failure paths, fault trees, and troubleshooting paths, it transforms abstract fault logic into visualized and standardized guidance tools, improving the efficiency and consistency of fault diagnosis. Simultaneously, by exporting abnormal signal data points, it provides quantitative evidence for accurate confirmation of the root cause of the problem and lays the foundation for the accumulation of fault data and subsequent performance optimization of the electric drive system, enhancing the scientific rigor, efficiency, and operability of electric drive system fault analysis. This solves the problem that related technologies rely on the manual intervention of technical personnel, resulting in the speed and accuracy of fault location being limited by the professional experience and technical level of these personnel. This not only increases the cost of manual judgment but also increases the error rate due to subjective judgment bias, reducing fault diagnosis efficiency and failing to meet the needs of rapid and accurate diagnosis of electric drive systems.

[0095] Figure 4 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. The electronic device may include: The memory 401, the processor 402, and the computer program stored on the memory 401 and capable of running on the processor 402.

[0096] When the processor 402 executes the program, it implements the fault analysis method for the electric drive system provided in the above embodiments.

[0097] Furthermore, electronic devices also include: Communication interface 403 is used for communication between memory 401 and processor 402.

[0098] The memory 401 is used to store computer programs that can run on the processor 402.

[0099] Memory 401 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0100] If the memory 401, processor 402, and communication interface 403 are implemented independently, then the communication interface 403, memory 401, and processor 402 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized into address buses, data buses, control buses, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0101] Optionally, in a specific implementation, if the memory 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.

[0102] Processor 402 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0103] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described fault analysis method for an electric drive system.

[0104] This application also provides a computer program product, including a computer program that, when executed, implements the above-described fault analysis method for an electric drive system.

[0105] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0106] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0107] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, 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 embodiments of this application pertain.

[0108] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0109] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or more of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0110] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0111] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0112] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A fault analysis method for an electric drive system, characterized in that, Includes the following steps: Obtain vehicle information for the disabled vehicle; Based on the vehicle information and the corresponding cloud data, fault information of the faulty vehicle is generated, so as to determine the fault path and corresponding key signals according to the fault information, and to identify at least one abnormal point. Based on the at least one abnormal point, multiple failure paths corresponding to electric drive faults are generated, and a fault tree and troubleshooting path are output. The corresponding abnormal signal data points are also exported to determine the root cause of the problem.

2. The method according to claim 1, characterized in that, The process of generating fault information for the faulty vehicle based on the vehicle information and corresponding cloud data includes: Based on the vehicle information, the original cloud-based fault data is obtained and the data format is converted to obtain the cloud-based data; Based on the cloud data, determine whether there is an electric drive malfunction; If it is an electric drive failure, the fault information is obtained according to the electric drive fault code table.

3. The method according to claim 1, characterized in that, The step of determining the fault path and corresponding key signals based on the fault information to identify at least one anomaly includes: Based on the fault information, the fault path is confirmed using the electric drive failure database; Identify key signals of the fault path and match fault judgment thresholds based on the key signals; The at least one abnormal point is determined based on the fault judgment threshold.

4. The method according to claim 3, characterized in that, Also includes: The electric drive failure database is updated based on the root cause of the problem.

5. A fault analysis device for an electric drive system, characterized in that, include: The acquisition module is used to acquire vehicle information of the faulty vehicle; The identification module is used to generate fault information of the faulty vehicle based on the vehicle information and corresponding cloud data, so as to determine the fault path and corresponding key signals according to the fault information, and to identify at least one abnormal point. The analysis module is used to generate multiple failure paths corresponding to electric drive faults based on the at least one abnormal point, output a fault tree and troubleshooting path, and export the corresponding abnormal signal data points to determine the root cause of the problem.

6. The apparatus according to claim 5, characterized in that, The identification module includes: The acquisition unit is used to acquire raw cloud-based fault data based on the vehicle information and perform data format conversion to obtain the cloud-based data. The judgment unit is used to determine whether there is an electric drive malfunction based on the cloud data. The generation unit is used to obtain the fault information according to the electric drive fault code table if the fault is an electric drive fault.

7. The apparatus according to claim 5, characterized in that, The identification module includes: The first determining unit is used to confirm the fault path based on the fault information using the electric drive failure database; The identification unit is used to identify key signals of the fault path and match fault judgment thresholds based on the key signals. The second determining unit is used to determine the at least one abnormal point based on the fault judgment threshold.

8. A vehicle, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the fault analysis method for an electric drive system as described in any one of claims 1-4.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the fault analysis method for the electric drive system as described in any one of claims 1-4.

10. A computer program product, comprising a computer program, characterized in that, The computer program is executed to implement the fault analysis method for the electric drive system as described in any one of claims 1-4.