A vehicle power system troubleshooting method, device and vehicle

Abstract

The embodiment of the application provides a vehicle power system troubleshooting method and device and a vehicle, and belongs to the technical field of vehicle power systems. The application obtains fault phenomenon information; determines an identification bit according to the fault phenomenon information; records vehicle state data according to the identification bit; obtains troubleshooting signals of each fault; and analyzes the vehicle state data and the troubleshooting signals to obtain fault cause information. The application can be used for vehicle fault problem troubleshooting, solves the problem that the problem cannot be reproduced and the problem cannot be clearly generated, and solves the problem that the cause of abnormal generation cannot be found in the case that there is no fault code but the actual vehicle behaves abnormally.

Description

Technical Field

[0001] This application relates to the field of vehicle powertrain technology, and in particular to a method, device and vehicle for troubleshooting vehicle powertrain faults. Background Technology

[0002] Powertrain problems can occur, but they are not always reproducible during testing. In such cases, abnormal behavior can occur even without fault codes, posing a challenge to accurate problem localization and repair. Sometimes the powertrain exhibits abnormalities, but the vehicle's diagnostic system fails to record relevant fault codes. This renders traditional fault diagnosis methods insufficient to explain the root cause of the problem.

[0003] Traditional troubleshooting methods may not effectively record detailed data when a problem occurs, making it difficult for engineers to analyze the timing and related factors of the problem.

[0004] Existing technologies have some shortcomings in troubleshooting power system faults, such as insufficient capture of dynamic events, incomplete data storage, or inability to fully cover all possible fault scenarios. Summary of the Invention

[0005] The main objective of this application is to provide a method, device, and vehicle for troubleshooting vehicle powertrain system faults.

[0006] On one hand, embodiments of the present invention provide a method for troubleshooting vehicle powertrain system faults, the method comprising the following steps:

[0007] Obtain information about the fault symptoms;

[0008] Based on the fault phenomenon information, determine the identifier bit;

[0009] Record vehicle status data based on the aforementioned identifier bits;

[0010] Acquire troubleshooting signals for each type of fault;

[0011] The vehicle status data and the troubleshooting signals are analyzed to obtain information about the cause of the fault.

[0012] Furthermore, obtaining fault phenomenon information includes the following steps:

[0013] Scan the vehicle systems to obtain fault codes;

[0014] Based on the fault code, the fault phenomenon information is obtained;

[0015] The fault information includes fault information of the battery management system, fault information of the electric drive system, and fault information of the charging system.

[0016] Furthermore, the process of scanning the vehicle system to obtain fault codes includes the following steps:

[0017] Use diagnostic tools to scan the vehicle's electronic control unit to obtain fault codes.

[0018] Further, determining the identifier bit based on the fault phenomenon information includes the following steps:

[0019] Based on the fault phenomenon information, key signal data are obtained;

[0020] The key signal data includes battery voltage information, motor speed information, vehicle speed information, and accelerator pedal position information;

[0021] Abnormal values ​​in the key signal data are identified, and the identification bits are determined.

[0022] Furthermore, recording vehicle status data based on the identifier bit includes the following steps:

[0023] Set trigger condition information;

[0024] The triggering condition information includes a preset fault voltage range, abnormal current parameters, and sensor signal failure information;

[0025] Based on the trigger condition information, record the specific signals within 1 second before and after the trigger of the identifier bit;

[0026] Vehicle status data is obtained based on the specific signal.

[0027] Furthermore, acquiring the troubleshooting signal for each type of fault includes the following steps:

[0028] Troubleshooting signals for each type of fault are obtained from sensors and actuators in the vehicle controller;

[0029] The investigation signals are sorted and merged.

[0030] Furthermore, the analysis of the vehicle status data and the troubleshooting signals to obtain fault cause information includes the following steps:

[0031] A rolling storage mechanism is implemented in the vehicle controller to store the troubleshooting signals and obtain a signal list;

[0032] Based on the signal list, the vehicle status data is analyzed to obtain fault cause information.

[0033] Furthermore, the vehicle powertrain fault diagnosis method also includes the following steps:

[0034] Upload the signal list to the cloud for backup;

[0035] The signal list is read from the vehicle terminal.

[0036] On the other hand, embodiments of the present invention also provide a vehicle powertrain system fault diagnosis device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the vehicle powertrain system fault diagnosis method as described above.

[0037] On the other hand, embodiments of the present invention also provide a vehicle, the vehicle including the vehicle power system fault diagnosis device as described above.

[0038] The embodiments of this application include at least the following beneficial effects: This application provides a method, device, and vehicle for troubleshooting vehicle powertrain system faults. The invention acquires fault phenomenon information; determines an identifier bit based on the fault phenomenon information; records vehicle status data based on the identifier bit; acquires troubleshooting signals for each type of fault; and analyzes the vehicle status data and the troubleshooting signals to obtain fault cause information. This invention can be used for troubleshooting vehicle faults, solving problems such as difficulty in diagnosing the cause of abnormalities, including situations where the cause cannot be clearly identified due to non-reproducible faults or where the actual vehicle exhibits abnormal behavior despite the absence of fault codes. Attached Figure Description

[0039] Figure 1 This is a flowchart of a vehicle powertrain fault diagnosis method provided in an embodiment of the present invention;

[0040] Figure 2 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0041] Figure 3 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0042] Figure 4 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0043] Figure 5 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0044] Figure 6 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0045] Figure 7 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0046] Figure 8This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0047] Figure 9 This is a flowchart of the steps in the vehicle powertrain fault diagnosis method provided in this embodiment of the invention;

[0048] Figure 10 This is a schematic diagram of the vehicle power system fault diagnosis device provided in an embodiment of the present invention. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0050] It is understood that the terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to a determination” as used herein may be interpreted as “when…” or “when…” or “in response to a determination.”

[0051] As used in this application, the terms "at least one", "multiple", "each", "any", etc., "at least one" includes one, two or more, "multiple" includes two or more, "each" refers to each of the corresponding multiples, and "any" refers to any one of the multiples.

[0052] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0053] This invention addresses the difficulty of troubleshooting system-level problems in vehicles by providing a method for diagnosing vehicle powertrain system faults. It stores relevant data for a period before and after the occurrence of potential powertrain system issues for troubleshooting, thus resolving problems such as situations where the cause of anomalies is difficult to determine, including cases where the problem cannot be reproduced and the circumstances at the time of its occurrence are unclear, or cases where there are no fault codes but the actual vehicle exhibits abnormal behavior.

[0054] The embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0055] On the one hand, embodiments of the present invention provide a method for troubleshooting vehicle powertrain system faults, which can be used to troubleshoot vehicle faults and solve problems such as difficulty in finding the cause of abnormalities, such as situations where the problem cannot be reproduced and the circumstances at which the problem occurred are unclear, or situations where there are no fault codes but the actual vehicle is not behaving normally.

[0056] This invention discloses a method for troubleshooting vehicle powertrain system faults. Specifically, refer to... Figure 1 The method includes the following steps:

[0057] S100, Obtain fault phenomenon information;

[0058] S200. Determine the flag bit based on the fault symptom information;

[0059] S300: Record vehicle status data based on the identifier position;

[0060] S400: Acquire troubleshooting signals for each type of fault;

[0061] S500 analyzes vehicle status data and troubleshooting signals to obtain information on the cause of the fault.

[0062] Troubleshooting vehicle powertrain systems is a crucial aspect of modern automotive repair, involving comprehensive diagnosis and analysis of components such as the engine, transmission system, and related control units. This invention will discuss in detail an embodiment of a vehicle powertrain system troubleshooting method, which effectively identifies and resolves various problems in the vehicle powertrain system through systematic steps.

[0063] In step S100 of this embodiment of the invention, which involves acquiring fault phenomenon information, it is necessary to accurately acquire vehicle fault phenomenon information before starting any repair work. This information can be acquired through various means, including the driver's description, warning light information displayed on the vehicle's dashboard, abnormal sounds or vibrations during vehicle operation, and real-time data provided by dedicated diagnostic tools. For example, the driver may mention engine power loss, increased fuel consumption, difficulty starting, etc., all of which could be manifestations of potential faults.

[0064] The fault information obtained should be as detailed and accurate as possible, including but not limited to the time of occurrence, frequency, and whether it is related to specific operations or conditions. This information is crucial for subsequent diagnostic analysis, providing technicians with a starting point to help them conduct targeted further inspections and tests.

[0065] During the S100 stage of acquiring fault information, the system collects real-time data from various vehicle components through sensors and monitoring devices. This data includes, but is not limited to, engine parameters, transmission system status, and wheel speed. Utilizing machine learning and deep learning technologies, the system can monitor and identify abnormal phenomena in real time, such as changes in engine noise and unstable vehicle speed.

[0066] In step S200 of this embodiment of the invention, determining the identifier based on fault phenomenon information means initially determining the possible fault type or location based on the aforementioned acquired fault phenomenon information. The determination of the identifier can be based on technical manuals, empirical data, or recommendations provided by dedicated diagnostic equipment. For example, if the driver reports unstable engine operation and the malfunction indicator light is illuminated, the identifier may point to a problem with the fuel system or ignition system.

[0067] In determining the flags, technicians can comprehensively consider the diversity of fault phenomena and possible causes to avoid prematurely focusing on a specific area while ignoring other potential sources of problems. Therefore, the key to this step is to fully and accurately understand the fault phenomena and continuously verify and adjust the assumptions about the flags during subsequent diagnosis.

[0068] Once an anomaly is detected, the system initiates a flag determination process. Using a neural network model, the system can classify and label fault modes, such as associating abnormalities in the engine, transmission, or braking system with specific fault codes. This classification can be based on prior training data and real-time sensor input.

[0069] In step S300 of this embodiment of the invention, which records vehicle status data based on an identifier bit, once the identifier bit is determined, the next task is to record vehicle status data related to the fault. This data includes, but is not limited to, real-time readings from various sensors, operating parameters of the control unit, engine operating status, and vehicle driving conditions. This data can be collected in real-time using diagnostic tools or by retrieving historical data from the vehicle's internal recording system.

[0070] The purpose of recording vehicle status data is to provide data support for subsequent analysis. This data can help technicians understand the specific environment and conditions under which a fault occurred. For example, recording parameters such as engine speed, throttle position, and oxygen sensor readings helps to confirm the specific timing of the fault and its correlation with vehicle operation.

[0071] During the S300 vehicle status data recording phase, the system records detailed vehicle status data collected by sensors. This data includes operating parameters of various vehicle components, fault codes, engine speed, lubricating oil temperature, and other information. Neural networks can process this large amount of data and extract key fault-related information, laying the foundation for subsequent analysis and diagnosis.

[0072] In step S400 of this embodiment of the invention, which acquires troubleshooting signals for each type of fault, the troubleshooting signals refer to additional information or data that needs to be acquired to confirm or eliminate a specific fault. These signals may be the output of a specific sensor, feedback signals from a control unit, data communication on the vehicle's internal communication bus, etc. For example, for a fault in the fuel system, it is necessary to acquire information such as the reading of the fuel pressure sensor and the operating status of the fuel injectors.

[0073] Acquiring troubleshooting signals relies on specialized diagnostic equipment or standard testing procedures provided by the vehicle manufacturer. By acquiring these signals, technicians can verify assumptions about the flags and further narrow down the location or cause of the fault. This step is crucial in the diagnostic process, directly impacting subsequent data analysis and final problem confirmation.

[0074] In the step of acquiring troubleshooting signals for each fault in the S400 system, the system obtains the troubleshooting signals associated with each fault based on previously identified bits and recorded status data. These signals may include detailed fault diagnosis steps, recommended inspection items, and possible remedial measures. Through an artificial intelligence-based decision support system, the system can optimize the fault troubleshooting process and improve the accuracy and efficiency of fault location.

[0075] In the S500 step of this embodiment of the invention, which analyzes vehicle status data and troubleshooting signals to obtain fault cause information, a comprehensive analysis is performed on the collected vehicle status data and troubleshooting signals to determine the root cause of the fault. This process can be performed in-depth by combining technical manuals, fault code interpretations, expert experience, and actual test results. For example, by comparing the actual measured fuel pressure with the standard value, it can be determined whether there is an abnormal pressure in the fuel system, and thus infer possible fault locations.

[0076] The key to the analysis lies in its comprehensiveness and logical consistency. Technicians need to ensure that every data point acquired is fully utilized and evaluated. Furthermore, the analysis process must consider the interactions between different vehicle components and their potential compound failures. Through systematic analysis, a clear diagnostic result can be obtained, and an effective repair plan can be developed to restore the vehicle to its normal operating condition.

[0077] In the S500's step of analyzing vehicle status data and troubleshooting signals to obtain fault cause information, the system utilizes neural networks and machine learning algorithms for in-depth analysis of the vehicle status data and troubleshooting signals. These algorithms can identify potential fault causes, such as damage to specific components, sensor failure, or system setting errors. Through this analysis, the system can provide accurate fault diagnosis reports, helping technicians quickly locate and resolve problems, thereby reducing vehicle repair time and costs.

[0078] refer to Figure 2 The present invention specifically discloses step S100 for obtaining fault phenomenon information, including the following steps:

[0079] S110. Scan the vehicle system to obtain fault codes;

[0080] S120. Obtain fault phenomenon information based on the fault code;

[0081] S130, Fault information includes battery management system fault information, electric drive system fault information, and charging system fault information.

[0082] As an optional implementation, in step S100, where fault phenomenon information is acquired, the system first acquires information about potential vehicle fault phenomena. This information is crucial for accurate diagnosis and problem solving.

[0083] In step S110, which involves scanning the vehicle system and obtaining fault codes, the system scans various vehicle systems to obtain detailed fault codes. These codes are collected from various sensors and control units and can directly indicate the location of problems in the vehicle system.

[0084] In step S120, based on the fault codes, fault phenomenon information is obtained. Once the fault codes are acquired, the system further analyzes and interprets these codes to obtain specific fault phenomenon information. This information can describe the specific problems occurring in the vehicle system and their possible causes.

[0085] In step S130, where the fault phenomenon information includes battery management system fault information, electric drive system fault information, and charging system fault information, the present invention systematically summarizes and organizes the fault phenomenon information obtained. This information covers multiple aspects, including but not limited to potential fault information in the battery management system, electric drive system, and charging system. This classification allows technicians to take targeted and appropriate maintenance and adjustment measures to ensure the normal operation of the vehicle system.

[0086] refer to Figure 3 The present invention specifically discloses step S110, which involves scanning the vehicle system to obtain fault codes, including the following steps:

[0087] S111. Use a diagnostic tool to scan the vehicle's electronic control unit to obtain fault codes.

[0088] As an optional implementation, this step involves connecting to the vehicle's electronic control unit (ECU) using a dedicated diagnostic tool, such as an OBD-II scanner or a diagnostic device provided by the vehicle manufacturer. The diagnostic tool is able to communicate with the various control units of the vehicle and read the fault codes stored within them.

[0089] Diagnostic tools scan a vehicle's ECUs to retrieve stored fault codes. These fault codes are automatically recorded by the vehicle's systems when they detect abnormalities; they provide a starting point and indicate potential problem areas. For example, fault codes related to communication with the electric motor, battery system, sensors, or control units may be retrieved.

[0090] refer to Figure 4 The present invention specifically discloses step S200, which determines the identifier bit based on the fault phenomenon information, including the following steps:

[0091] S210. Based on the fault phenomenon information, obtain key signal data;

[0092] S220, key signal data includes battery voltage information, motor speed information, vehicle speed information, and accelerator pedal position information;

[0093] S230. Identify abnormal values ​​in key signal data and determine the identifier bits.

[0094] As an optional implementation, in S210, based on the fault information reported by the vehicle, the system begins to capture and record key signal data. This signal data refers to important parameters that can reflect the vehicle's operating status and system response, such as battery voltage, motor speed, vehicle speed, and accelerator pedal position.

[0095] Key signal data content:

[0096] Battery voltage information: Reflects the voltage level of the electric vehicle's battery pack, and is crucial for determining the battery status and power supply.

[0097] Motor speed information: Records the speed of the electric vehicle's motor to help analyze power output and motor operating status.

[0098] Vehicle speed information: Measuring the current speed of the vehicle is an important basis for judging whether the power system output is normal.

[0099] Accelerator pedal position information: Indicates the driver's operation of the accelerator pedal, which directly affects the acceleration and power output of the electric vehicle.

[0100] Outlier identifier:

[0101] In step S230, the system analyzes the captured key signal data and identifies outliers. These outliers may indicate that the system is not working as expected or indicate a potential malfunction. For example, abnormal battery voltage, lower than expected motor speed, or a very low accelerator pedal position signal could all be indicators of a problem.

[0102] Determine the identifier:

[0103] After identifying anomalous values ​​in key signal data, the system can determine the fault flags. These flags mark the point in time when the system detected a specific anomaly, providing a crucial time window and data basis for subsequent fault diagnosis and analysis.

[0104] The embodiments of the present invention can provide a clearer understanding of how to use diagnostic tools to obtain fault codes in the troubleshooting of electric vehicle powertrain systems, and how to determine the problem identifier through key signal data, thereby achieving more effective fault diagnosis and solutions.

[0105] refer to Figure 5 The present invention specifically discloses step S300, which records vehicle status data based on the identifier bit, including the following steps:

[0106] S310, Set trigger condition information;

[0107] S320, the trigger condition information includes the preset fault voltage range, abnormal current parameters, and sensor signal failure information;

[0108] S330. Based on the trigger condition information, record the specific signals within 1 second before and after the trigger of the flag bit;

[0109] S340. Obtain vehicle status data based on specific signals.

[0110] The present invention sets trigger condition information (S310): In this step, the system first configures trigger condition information. These conditions are based on preset fault detection parameters, such as fault voltage range, abnormal current parameters, and sensor signal failure information. Each fault may have different trigger conditions, which help the system determine when to start recording vehicle status data.

[0111] The triggering condition information content of the present invention (S320):

[0112] Preset fault voltage range: Determines the range of abnormal voltages in the electric vehicle battery or other critical electrical components. Exceeding this range may indicate a problem with the power system.

[0113] Current anomaly parameters: Set parameters used to detect abnormal current in motors or other actuators, such as overload or open circuit.

[0114] Sensor signal failure information: Defines abnormal sensor signal conditions, such as sensor disconnection or unstable output.

[0115] In step S330 of this invention, specific signals within one second before and after the flag bit is triggered are recorded: when the system detects that the trigger condition is met, it records specific signal data around the flag bit. This data is typically captured within one second before and after the flag bit is triggered, because signal changes during this period are particularly important for fault analysis.

[0116] In step S340 of this invention, vehicle status data is obtained based on specific signals: the system generates vehicle status data based on the recorded specific signal data. This data may include various parameter values ​​at the trigger time, such as battery voltage, motor speed, vehicle speed, accelerator pedal position, etc. This information is crucial for engineers or technicians to diagnose faults and analyze the causes of problems.

[0117] refer to Figure 6 The present invention specifically discloses step S400 for acquiring troubleshooting signals for each type of fault, including the following steps:

[0118] S410: Obtain troubleshooting signals for each type of fault from sensors and actuators in the vehicle controller;

[0119] S420. Organize and merge the investigation signals.

[0120] In step S410 of this embodiment of the invention, troubleshooting signals are obtained from sensors and actuators in the vehicle controller. In this step, the system obtains troubleshooting signals related to each possible fault by accessing the sensors and actuators in the vehicle controller. These signals include, but are not limited to, sensor outputs, actuator operating states, and feedback information from other key components.

[0121] In step S420 of this embodiment of the invention, the troubleshooting signals are organized and merged: the acquired troubleshooting signals may come from multiple different systems and sensors, therefore, in step S420, the system organizes and merges these signals. This process helps to centralize fault-related information, facilitating subsequent analysis and diagnosis.

[0122] The embodiments of the present invention provide a clearer understanding of how the embodiments of the invention support fault diagnosis and maintenance of electric vehicle systems by setting trigger conditions, capturing specific signals and recording vehicle status data, and how to acquire and organize fault diagnosis signals.

[0123] refer to Figure 7 The present invention specifically discloses step S500, which involves analyzing vehicle status data and troubleshooting signals to obtain fault cause information, including the following steps:

[0124] S510. Implement a rolling storage mechanism in the vehicle controller to store the troubleshooting signals and obtain a signal list;

[0125] S520: Based on the signal list, analyze vehicle status data to obtain fault cause information.

[0126] In step S500 of this embodiment of the invention, vehicle status data and troubleshooting signals are analyzed to obtain fault cause information. This step involves in-depth analysis of vehicle status data and troubleshooting signals to obtain accurate fault cause information. Specific steps include:

[0127] In step S510 of this embodiment of the invention, a rolling storage mechanism is implemented to store the investigation signals:

[0128] A rolling memory mechanism is implemented in the vehicle controller to continuously record and store troubleshooting signals sent by the vehicle system. These signals can include information such as sensor readings, control unit outputs, or system status indications. Through this rolling memory mechanism, the system can effectively capture and record all significant signal changes, which may be the direct cause or indication of a fault. Specifically, this step includes:

[0129] Monitoring and capturing signal changes: The vehicle system periodically sends various troubleshooting signals that reflect the system's operational status and parameters. A rolling storage mechanism is responsible for monitoring these signals in real time and storing them chronologically in designated storage space on the vehicle controller.

[0130] Signal List Generation: Based on the captured signals, the system generates a detailed signal list. This list records all important signal types and their corresponding values ​​or states, providing foundational data for subsequent analysis.

[0131] Step S520 of this embodiment of the invention analyzes vehicle status data based on the signal list to obtain fault cause information:

[0132] After obtaining a detailed list of the troubleshooting signals, the system proceeds to the next stage: in-depth analysis based on these signals to determine the possible causes of vehicle malfunctions. Specific analysis steps include:

[0133] Signal correlation analysis: The system performs correlation analysis between the signal list and known vehicle status data. This status data can include various real-time and historical data such as engine operating parameters, vehicle speed, fuel consumption, and battery voltage.

[0134] Anomaly detection and fault diagnosis: Utilizing advanced data analysis techniques, the system identifies signal patterns or outliers that deviate from normal operation. These anomalies often indicate potential system malfunctions or performance degradation.

[0135] Generating Fault Cause Information: Finally, based on the analysis results, the system generates a detailed fault cause information report. This report includes a specific description of the fault diagnosis, possible root causes, and recommended corrective actions. This information provides technicians with the necessary guidance to quickly and accurately resolve any problems the vehicle may encounter.

[0136] In summary, step S500, by effectively combining real-time capture of troubleshooting signals with in-depth analysis of vehicle status data, provides a method and system for efficiently and accurately diagnosing vehicle faults. This not only helps improve vehicle repair efficiency but also reduces maintenance costs and enhances the user's vehicle experience.

[0137] refer to Figure 8 The vehicle powertrain fault diagnosis method disclosed in this embodiment of the invention further includes the following steps:

[0138] S600: Upload the signal list to the cloud for backup;

[0139] S700: Read the signal list from the vehicle terminal.

[0140] As an optional implementation, in step S600, where the signal list is uploaded to the cloud for backup, the vehicle powertrain fault diagnosis method involves uploading a predefined signal list to the cloud via an onboard terminal for backup. These signals may include data from various sensors, control units, or other monitoring devices. By uploading the data to the cloud, centralized storage and management of the data can be achieved, ensuring data security and reliability. Furthermore, cloud backup facilitates subsequent data analysis and fault diagnosis, enabling engineers to access this data anytime, anywhere for further analysis.

[0141] In the step of reading the signal list from the vehicle terminal in the S700, the powertrain fault diagnosis method requires reading the signal list previously uploaded and stored in the cloud from the vehicle terminal. This process may involve obtaining the backed-up signal list data from the cloud through the vehicle terminal's interface or specific software tools. Reading the signal list is for subsequent signal analysis and fault diagnosis. The vehicle terminal, as a key bridge connecting the vehicle's internal systems and cloud data, effectively supports data transmission and exchange, thereby helping engineers quickly and accurately locate and resolve potential faults in the vehicle's powertrain.

[0142] The complete implementation of these two steps ensures that necessary signal data can be quickly acquired and analyzed when problems occur in the vehicle's powertrain, thereby improving the efficiency and accuracy of fault diagnosis.

[0143] As an optional implementation method, refer to Figure 9 The present invention includes the following steps:

[0144] Based on the symptoms of each type of fault that needs to be investigated, determine the flag bit for each fault.

[0145] Determine the signals required for troubleshooting each type of fault;

[0146] Organize the signals required for each type of fault diagnosis, merge identical signals, and determine the list of signals required for fault diagnosis.

[0147] The signals required for fault diagnosis are stored in the vehicle controller and updated every 1 second (which can be calibrated according to different needs);

[0148] When a fault occurs and the flag is triggered, store the signals required for specific fault troubleshooting within 1 second before and after the flag is triggered.

[0149] Analyze the causes of system failures based on stored signals.

[0150] The stored signals can be read at any time via the vehicle terminal and periodically uploaded to the cloud for backup.

[0151] For each type of fault diagnosis signal identified above, identical and similar signals are sorted and merged to minimize signal storage and memory consumption, and finally a list of stored signals is determined.

[0152] The defined list of stored signals is stored in a rolling manner in the vehicle controller and is updated every 1 second (which can be calibrated according to different requirements) when no fault occurs and the flag bit is triggered.

[0153] When a fault occurs and the flag is triggered, the system stores the signals required for troubleshooting a specific fault when the specific flag, determined by the preceding steps 1 second before and after the flag is triggered, occurs.

[0154] This invention analyzes the causes of system failures based on stored signals.

[0155] refer to Figure 9 The embodiments of the present invention include:

[0156] Example 1: Analysis of Power-Limited Problems

[0157] 1. Definition of power limitation problem: When the current output capacity of the power system is less than or equal to 20% of the external characteristics of the system (calibrated value), the flag bit is triggered.

[0158] 2. When the flag is triggered, store the following signals 1 second before and after the flag: accelerator pedal opening, vehicle speed, brake pedal opening, current motor capacity, current battery capacity, vehicle controller torque request, current motor output torque, and battery current.

[0159] 3. Identify the problem based on the above signals and determine the root cause.

[0160] Example 2: Analysis of Accelerator Pedal Failure

[0161] 1. Accelerator pedal fault identification: The vehicle controller reports an accelerator pedal fault code. When this condition is met, the flag bit is triggered.

[0162] 2. When the flag is triggered, store the accelerator pedal power supply signal and accelerator pedal opening signal 1 second before and after the flag.

[0163] 3. Based on the above signals, identify the problem and determine whether the accelerator pedal fault code is caused by a power supply problem or an opening signal problem.

[0164] The signals used in all instances are sorted and merged to determine all signals in the rolling storage.

[0165] As an optional implementation, embodiments of the present invention describe a system fault diagnosis and analysis method that identifies and resolves problems such as vehicle power and accelerator pedal issues by continuously storing key signals. The following is a summary of the execution steps of this invention:

[0166] Execution steps overview:

[0167] Define fault determination conditions:

[0168] Define the specific criteria for each type of fault, such as limited power or accelerator pedal malfunction. These criteria are typically based on the system's monitoring and diagnostic functions, such as specific fault codes or performance indicators reaching or falling below predetermined thresholds.

[0169] Flag trigger conditions:

[0170] When the fault criteria are met, the system will trigger a flag indicating that a fault may exist.

[0171] Signal storage:

[0172] When the flag is triggered, the system begins to continuously store key signal data. These signals include, but are not limited to, accelerator pedal opening, vehicle speed, brake pedal opening, motor capability, battery capability, torque requested by the vehicle controller, motor output torque, and battery current.

[0173] Problem identification and root cause determination:

[0174] Stored signal data is used for problem analysis to determine the true cause of the malfunction. For example, a power limitation problem might require analyzing changes in motor and battery capabilities, while an accelerator pedal malfunction would require analyzing the accelerator pedal opening and power supply signals.

[0175] Signal processing and merging:

[0176] Organize and merge all possible fault signals to ensure the system can effectively capture and store critical data.

[0177] Storage and update frequency:

[0178] The vehicle controller performs rolling storage of signals, typically updating once per second, to ensure timely recording of signal changes before and after critical events.

[0179] Data backup and management:

[0180] The stored signal data can be read at any time through the vehicle terminal and uploaded to the cloud regularly for backup and analysis, so as to facilitate long-term data management and fault trend analysis.

[0181] Detailed description of the execution steps:

[0182] Step 1: Define fault determination conditions

[0183] Determine specific conditions such as limited power or accelerator pedal malfunction, for example, the motor capacity is less than 20% of the system's external characteristics, or the vehicle controller reports a specific accelerator pedal fault code.

[0184] Step 2: Flag Trigger Condition

[0185] When the fault determination conditions are met, the system generates a flag bit, and the storage of the fault signal begins when the flag bit is triggered.

[0186] Step 3: Signal Storage

[0187] The system stores key signal data within one second before and after the trigger of the storage flag, including accelerator pedal opening, vehicle speed, brake pedal opening, motor capacity, battery capacity, vehicle controller torque request, motor output torque, and battery current.

[0188] Step 4: Problem Identification and Root Cause Determination

[0189] The stored signal data is used for problem identification and analysis to determine the root cause of the malfunction, such as whether the power is limited due to insufficient battery capacity, or whether there is a malfunction in the power supply or opening signal of the accelerator pedal.

[0190] Step 5: Signal Sorting and Merging

[0191] Organize and merge all possible signals needed for troubleshooting to ensure that the system can fully record and analyze all critical data.

[0192] Step 6: Storage and Update Frequency

[0193] Rolling storage is implemented in the vehicle controller, updating signal data once per second to ensure timely recording of signal status changes before and after critical events.

[0194] Step 7: Data Backup and Management

[0195] The system reads stored signal data at any time through the vehicle terminal and uploads it to the cloud regularly for backup and long-term data management to support fault trend analysis and system optimization.

[0196] These steps ensure that various power and accelerator pedal related issues can be identified and resolved in a timely and accurate manner during vehicle operation, thereby improving the vehicle's stability and reliability.

[0197] refer to Figure 10 On the other hand, embodiments of the present invention provide a vehicle powertrain system fault diagnosis device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the vehicle powertrain system fault diagnosis method as described above.

[0198] The vehicle powertrain fault diagnosis device according to an embodiment of the present invention includes a memory and a processor.

[0199] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0200] Memory can include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. ROM can store static data or instructions required by the processor or other modules of the computer. Permanent storage devices can be read-write storage devices. Permanent storage devices can be non-volatile storage devices that retain stored instructions and data even when the computer is powered off. In some embodiments, permanent storage devices use high-capacity storage devices (e.g., magnetic or optical disks, flash memory) as permanent storage devices. In other embodiments, permanent storage devices can be removable storage devices (e.g., floppy disks, optical drives). System memory can be a read-write storage device or a volatile read-write storage device, such as dynamic random access memory. System memory can store some or all of the instructions and data required by the processor during operation. Furthermore, memory can include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and disks and / or optical disks can also be used. In some implementations, the memory may include removable storage devices that are readable and / or writable, such as laser discs (CDs), read-only digital versatile optical discs (e.g., DVD-ROMs, dual-layer DVD-ROMs), read-only Blu-ray discs, ultra-high density optical discs, flash memory cards (e.g., SD cards, mini SD cards, Micro-SD cards, etc.), magnetic floppy disks, etc. Computer-readable storage media do not contain carrier waves or transient electronic signals transmitted wirelessly or via wired connections.

[0201] The memory stores executable code, which, when processed by the processor, can cause the processor to execute some or all of the methods described above.

[0202] On the other hand, embodiments of the present invention provide a vehicle that includes the vehicle powertrain fault diagnosis device as described above.

[0203] The vehicle in this embodiment of the invention includes the electric drive assembly of the aforementioned vehicle powertrain fault diagnosis device. Specifically, the vehicle can be a private car, such as a sedan, SUV, MPV, or pickup truck. The vehicle can also be a commercial vehicle, such as a van, bus, small truck, or large trailer. The vehicle can be a gasoline-powered vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle.

[0204] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method for troubleshooting vehicle powertrain system faults, characterized in that, The method includes the following steps: Obtain information about the fault symptoms; Based on the fault phenomenon information, the identifier bits are determined, including: Based on the fault phenomenon information, key signal data are obtained; The key signal data includes battery voltage information, motor speed information, vehicle speed information, and accelerator pedal position information; Abnormal values ​​in the key signal data are identified, and the identification bits are determined. Record vehicle status data based on the aforementioned identifier bits; Acquire troubleshooting signals for each type of fault, including: Troubleshooting signals for each type of fault are obtained from sensors and actuators in the vehicle controller; The investigation signals are processed and merged; the investigation signals come from multiple different systems and sensors; The troubleshooting signals are stored in a rolling manner in the vehicle controller and updated once per second; The vehicle status data and the troubleshooting signals are analyzed to obtain fault cause information; The fault cause information includes a fault diagnosis description, root cause, and recommended repair measures; Based on the stored signals, analyze the causes of system failures: In defining the power limitation problem, when the flag is triggered, the accelerator pedal opening, vehicle speed, brake pedal opening, current motor capacity, current battery capacity, vehicle controller torque request, current motor output torque, and battery current are stored 1 second before and after the flag to identify the problem and determine the root cause. In defining accelerator pedal malfunctions, the accelerator pedal fault code is obtained, the flag bit is triggered, and the accelerator pedal power supply signal and accelerator pedal opening signal are stored 1 second before and after the flag bit. Problem identification is then performed to determine whether the cause of the accelerator pedal fault code is a power supply problem or an opening signal problem.

2. The method according to claim 1, characterized in that, The process of obtaining fault information includes the following steps: Scan the vehicle systems to obtain fault codes; Based on the fault code, the fault phenomenon information is obtained; The fault information includes fault information of the battery management system, fault information of the electric drive system, and fault information of the charging system.

3. The method according to claim 2, characterized in that, The process of scanning the vehicle system to obtain fault codes includes the following steps: Use diagnostic tools to scan the vehicle's electronic control unit to obtain fault codes.

4. The method according to claim 1, characterized in that, The process of recording vehicle status data based on the identifier bit includes the following steps: Set trigger condition information; The triggering condition information includes a preset fault voltage range, abnormal current parameters, and sensor signal failure information; Based on the trigger condition information, record the specific signals within 1 second before and after the trigger of the identifier bit; Vehicle status data is obtained based on the specific signal.

5. The method according to claim 1, characterized in that, The process of analyzing the vehicle status data and the troubleshooting signals to obtain fault cause information includes the following steps: A rolling storage mechanism is implemented in the vehicle controller to store the troubleshooting signals and obtain a signal list; Based on the signal list, the vehicle status data is analyzed to obtain fault cause information.

6. The method according to claim 5, characterized in that, The vehicle powertrain system fault diagnosis method also includes the following steps: Upload the signal list to the cloud for backup; The signal list is read from the vehicle terminal.

7. A vehicle powertrain system fault diagnosis device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the vehicle powertrain system fault diagnosis method as described in any one of claims 1 to 6.

8. A vehicle, characterized in that, The vehicle includes the vehicle powertrain fault diagnosis device as described in claim 7.

Images