Vehicle power system troubleshooting method and device and vehicle
By obtaining and analyzing the fault phenomenon information, identification positions and troubleshooting signals of the vehicle power system, combined with machine learning technology, the problem of insufficient data and insufficient coverage in the power system troubleshooting in the existing technology is solved, and the failure of the vehicle power system is achieved Accurate positioning and efficient diagnosis.
Patent Information
- Application Number
- CN202411071421.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-06
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2044-08-06
AI Technical Summary
The prior art has problems in vehicle power system troubleshooting problems such as insufficient dynamic event capture, incomplete data storage and inability to fully cover all possible failure situations, making it difficult to accurately locate the root cause of the failure when there is no fault code but the vehicle performs abnormally.
By obtaining fault phenomenon information, determining the identification bit, recording vehicle status data, obtaining troubleshooting signals, and analyzing these data, combining machine learning and neural network technology, in-depth analysis and diagnosis of the causes of the fault are achieved.
It effectively solves the problem of troubleshooting when there is no fault code but the vehicle performs abnormally, improves the accuracy and efficiency of fault location, and reduces maintenance time and cost.
Smart Images

Figure CN118915701A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of vehicle power systems, and in particular to a vehicle power system fault troubleshooting method, device and vehicle. Background Art
[0002] Problems may occur in the powertrain, but they are not always reproducible during testing. In this case, even if there is no fault code, the actual performance is abnormal, which makes it challenging to accurately locate and repair the problem. Sometimes the powertrain behaves abnormally, but the vehicle's diagnostic system fails to record the relevant fault code. This makes traditional fault diagnosis methods insufficient to explain the root cause of the problem.
[0003] Traditional troubleshooting methods may not effectively record detailed data when the problem occurs, making it difficult for engineers to analyze the timing and related factors of the problem.
[0004] Existing technologies have some defects in power system troubleshooting, 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 purpose of the embodiments of the present application is to provide a vehicle power system fault troubleshooting method, device and vehicle.
[0006] In one aspect, an embodiment of the present invention provides a method for troubleshooting a vehicle power system, the method comprising the following steps:
[0007] Obtain fault phenomenon information;
[0008] Determine the identification position according to the fault phenomenon information;
[0009] Recording vehicle status data according to the identification bit;
[0010] Get troubleshooting signals for each fault;
[0011] The vehicle status data and the troubleshooting signal are analyzed to obtain fault cause information.
[0012] Furthermore, the obtaining of fault phenomenon information comprises the following steps:
[0013] Scan vehicle systems and obtain fault codes;
[0014] Obtaining fault phenomenon information according to the fault code;
[0015] The fault phenomenon information includes battery management system fault information, electric drive system fault information, and charging system fault information.
[0016] Furthermore, scanning the vehicle system to obtain the fault code includes the following steps:
[0017] Use a diagnostic tool to scan the vehicle's electronic control unit and get the fault code.
[0018] Further, determining the identification bit according to the fault phenomenon information includes the following steps:
[0019] Obtaining key signal data according to the fault phenomenon information;
[0020] The key signal data includes battery voltage information, motor speed information, vehicle speed information, and accelerator pedal position information;
[0021] The abnormal values of the key signal data are identified to complete the determination of the identification position.
[0022] Further, recording the vehicle status data according to the identification bit comprises the following steps:
[0023] Set trigger condition information;
[0024] The trigger condition information includes a preset fault voltage range, current abnormality parameters, and sensor signal failure information;
[0025] According to the trigger condition information, record the specific signal within 1 second before and after the flag is triggered;
[0026] Vehicle status data is obtained according to the specific signal.
[0027] Furthermore, obtaining the troubleshooting signal of each fault includes the following steps:
[0028] Obtain troubleshooting signals for each fault from sensors and actuators in the vehicle controller;
[0029] The troubleshooting signals are sorted and merged.
[0030] Furthermore, the analyzing the vehicle status data and the troubleshooting signal to obtain fault cause information includes the following steps:
[0031] Implementing a rolling storage mechanism in the vehicle controller to store the troubleshooting signal 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 power system fault troubleshooting method further includes the following steps:
[0034] Uploading the signal list to the cloud for backup;
[0035] The signal list is read from the vehicle-mounted terminal.
[0036] On the other hand, an embodiment of the present invention also provides a vehicle power system troubleshooting device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the vehicle power system troubleshooting method as described above is implemented.
[0037] On the other hand, an embodiment of the present invention further provides a vehicle, wherein the vehicle includes the vehicle power system fault troubleshooting device as described above.
[0038] The embodiments of the present application include at least the following beneficial effects: The present application provides a vehicle power system troubleshooting method, device and vehicle. The present invention obtains fault phenomenon information; determines an identification bit based on the fault phenomenon information; records vehicle status data based on the identification bit; obtains a troubleshooting signal for each fault; analyzes the vehicle status data and the troubleshooting signal to obtain fault cause information. The present invention can be used for vehicle fault problem troubleshooting to solve the problem of difficulty in troubleshooting the cause of abnormalities, such as the situation where the problem cannot be reproduced and the situation where the problem occurs cannot be clearly identified, the situation where there is no fault code but the actual vehicle performance is abnormal, and so on. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1 is a flow chart of a vehicle power system fault troubleshooting method provided by an embodiment of the present invention;
[0040] Figure 2 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0041] Figure 3 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0042] Figure 4 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0043] Figure 5 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0044] Figure 6 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0045] Figure 7 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0046] Figure 8is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0047] Fig. 9 is a flowchart of the steps of a vehicle power system troubleshooting method provided by an embodiment of the present invention;
[0048] Fig.10 It is a structural schematic diagram of a vehicle power system fault troubleshooting device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0049] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. When the following description refers to the 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 the embodiments of the present application. They are only examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the attached claims.
[0050] It is understood that the terms "first", "second", etc. used in this application can be used to describe various concepts in this article, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another concept. For example, without departing from the scope of the embodiment of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".
[0051] The terms "at least one", "multiple", "each", "any", etc. used in this application, at least one includes one, two or more, multiple includes two or more, each refers to each of the corresponding multiple, and any refers to any one of the multiple.
[0052] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.
[0053] Taking into account the difficulty in troubleshooting the causes of vehicle system-level problems, the present invention provides a vehicle power system fault troubleshooting method. For problems that may occur in the power system, relevant data within a period of time before and after the problem occurs is stored for problem troubleshooting, and solves problems such as the problem cannot be reproduced and the situation when the problem occurred cannot be clearly identified, and there is no fault code but the actual vehicle performance is abnormal.
[0054] The embodiments of the present invention are further described below in conjunction with the accompanying drawings.
[0055] On the one hand, an embodiment of the present invention provides a vehicle power system troubleshooting method that can be used for vehicle fault problem troubleshooting to solve difficult problems such as the situation where the problem cannot be reproduced and the situation when the problem occurred cannot be clearly identified, and the situation where there is no fault code but the actual vehicle performance is abnormal.
[0056] The embodiment of the present invention discloses a vehicle power system fault troubleshooting method, specifically, referring to Figure 1 , the method comprises the following steps:
[0057] S100, obtaining fault phenomenon information;
[0058] S200, determining an identification position according to the fault phenomenon information;
[0059] S300, recording vehicle status data according to the identification bit;
[0060] S400, obtaining a troubleshooting signal for each fault;
[0061] S500: Analyze the vehicle status data and the troubleshooting signal to obtain fault cause information.
[0062] Vehicle power system troubleshooting is an important part of modern automobile maintenance, which involves comprehensive diagnosis and analysis of vehicle engine, transmission system and related control units. The present invention will discuss in detail an embodiment of a vehicle power system troubleshooting method, which effectively identifies and solves various problems in the vehicle power system through systematic steps.
[0063] In the step of obtaining fault phenomenon information in S100 of the embodiment of the present invention, before starting any maintenance work, it is first necessary to accurately obtain the fault phenomenon information of the vehicle. This information can be obtained through various channels, including the driver's description, the warning light information displayed on the vehicle dashboard, abnormal sounds or vibrations during vehicle operation, and real-time data provided by special diagnostic tools. For example, the driver may mention the loss of engine power, increased fuel consumption, difficulty in starting, etc., which may be manifestations of potential faults.
[0064] The fault phenomenon information obtained should be as detailed and accurate as possible, including but not limited to the time and frequency of the fault, whether it is related to specific operations or conditions, etc. This information is crucial for subsequent diagnostic analysis, and it provides a starting point for technicians to conduct further inspections and tests in a targeted manner.
[0065] During the stage of S100 obtaining fault information, the system collects real-time data of various vehicle components through sensors and monitoring devices. These data include but are not limited to engine parameters, transmission system status, wheel speed, etc. Using machine learning and deep learning technology, the system can monitor and identify abnormal phenomena in real time, such as changes in engine noise and unstable vehicle speed.
[0066] In the step of determining the identification bit according to the fault phenomenon information in S200 of the embodiment of the present invention, determining the identification bit refers to preliminarily determining the possible fault type or location according to the fault phenomenon information obtained above. The identification bit can be determined based on technical manuals, empirical data or suggestions provided by special diagnostic equipment. For example, if the driver reports that the engine is running unstably and the fault indicator light is on, the identification bit may point to a problem with the fuel system or the ignition system.
[0067] In the process of determining the identification position, technicians can comprehensively consider the diversity of fault phenomena and possible causes to avoid prematurely focusing on a specific direction and ignoring other potential sources of problems. Therefore, the key to this step is to fully and accurately understand the fault phenomenon and continuously verify and adjust the assumptions of the identification position in subsequent diagnosis.
[0068] Once an anomaly is detected, the system initiates the flag determination process. Through the neural network model, the system can classify and label the fault mode, such as associating anomalies in the engine, transmission or braking system with specific fault codes. This classification can be based on previous training data and real-time sensor input.
[0069] In the step of recording vehicle status data according to the identification bit in S300 of the embodiment of the present invention, once the identification bit is determined, the next task is to record the vehicle status data related to the fault. Such data include but are not limited to the real-time readings of various sensors, the operating parameters of the control unit, the working state of the engine, the driving conditions of the vehicle, etc. The collection of such data can be carried out in real time through the diagnostic tool, or historical data can be extracted through the vehicle's internal recording system.
[0070] The purpose of recording vehicle status data is to provide data support for subsequent analysis. They can help technicians understand the specific environment and conditions when the fault occurred. For example, recording parameters such as engine speed, throttle position, oxygen sensor readings, etc. can help confirm the specific time when the fault occurred and its correlation with vehicle operation.
[0071] In the S300 vehicle status data recording stage, the system records detailed vehicle status data collected by sensors. This data will include information such as operating parameters of various vehicle components, fault codes, engine speed, lubricating oil temperature, etc. Neural networks can process this large amount of data and extract key information related to the fault, laying the foundation for subsequent analysis and diagnosis.
[0072] In the step of obtaining the troubleshooting signal of each fault in S400 of the embodiment of the present invention, the troubleshooting signal refers to the additional information or data required to confirm or eliminate the specific fault. These signals can be the output of a specific sensor, the feedback signal of the control unit, the data communication on the internal communication bus of the vehicle, etc. For example, for the fault of the fuel system, it is necessary to obtain the reading of the fuel pressure sensor, the working status of the fuel injector, and other information.
[0073] The process of obtaining troubleshooting signals requires the use of dedicated diagnostic equipment or standard test procedures provided by the vehicle manufacturer. By obtaining these signals, technicians can verify the assumptions of the identification position and further narrow down the scope of the fault location or cause. This step is an important part of the diagnostic process, which directly affects the subsequent data analysis and final problem confirmation.
[0074] In the step of obtaining troubleshooting signals for each fault in S400, the system obtains troubleshooting signals related to each fault based on the previous identification bits and recorded status data. These signals may include detailed fault diagnosis steps, recommended inspection items, and possible repair measures. Through the decision support system of artificial intelligence, the system can optimize the troubleshooting process and improve the accuracy and efficiency of fault location.
[0075] In the step of analyzing the vehicle status data and troubleshooting signals to obtain the fault cause information in S500 of the embodiment of the present invention, the collected vehicle status data and troubleshooting signals are comprehensively analyzed to obtain the root cause of the fault. The execution of this process can be combined with technical manuals, fault code interpretation, expert experience and actual test results for in-depth analysis. For example, by comparing the actual measured fuel pressure with the standard value, it can be determined whether there is a pressure abnormality in the fuel system, and then the possible fault point can be inferred.
[0076] The key to analysis is comprehensiveness and logic. Technicians need to ensure that every acquired data point is fully utilized and evaluated. In addition, the analysis process must also take into account the mutual influence between different vehicle components and their possible compound failures. Through systematic analysis, the diagnosis results can be clarified and effective repair plans can be formulated to restore the normal operation of the vehicle.
[0077] In the step where the S500 analyzes vehicle status data and troubleshooting signals to obtain fault cause information, the system uses neural network and machine learning algorithms to conduct in-depth analysis of vehicle status data and troubleshooting signals. These algorithms can identify potential causes of failures, such as damage to specific components, sensor failure, or system setting errors. Through this analysis, the system can provide accurate fault diagnosis reports to help technicians quickly locate and solve problems, thereby reducing vehicle maintenance time and costs.
[0078] refer to Figure 2 The embodiment of the present invention specifically discloses step S100 of acquiring fault phenomenon information, including the following steps:
[0079] S110, scanning the vehicle system to obtain fault codes;
[0080] S120, obtaining fault phenomenon information according to the fault code;
[0081] S130. Fault phenomenon information includes battery management system fault information, electric drive system fault information, and charging system fault information.
[0082] As an optional implementation, in the step of obtaining fault phenomenon information at S100, the system first obtains possible fault phenomenon information of the vehicle, which is crucial for accurate diagnosis and problem solving.
[0083] In step S110 of scanning the vehicle system and obtaining fault codes, the system scans various systems of the vehicle to obtain detailed fault codes. These codes are collected from various sensors and control units and can directly indicate where the problem is in the vehicle system.
[0084] In step S120, the fault phenomenon information is obtained according to the fault code. Once the fault code is obtained, the system further analyzes and interprets the code to obtain specific fault phenomenon information. The information can describe the specific problems and possible causes in the vehicle system.
[0085] In the step S130 of the present invention, the fault phenomenon information includes the fault information of the battery management system, the fault information of the electric drive system, and the fault information of the charging system. The system summarizes and organizes the fault phenomenon information. This information covers multiple aspects, including but not limited to possible fault information of the battery management system, the electric drive system, and the charging system. This classification allows technicians to take appropriate maintenance and adjustment measures in a targeted manner to ensure the normal operation of the vehicle system.
[0086] refer to Figure 3 The embodiment of the present invention specifically discloses step S110 of scanning the vehicle system to obtain the fault code, including the following steps:
[0087] S111. Use a diagnostic tool to scan the electronic control unit of the vehicle to obtain a fault code.
[0088] As an optional implementation, this step is connected to the vehicle's electronic control unit (ECU) through a dedicated diagnostic tool, such as an OBD-II scanner or a diagnostic device provided by the vehicle manufacturer. The diagnostic tool can communicate with each control unit of the vehicle and read the fault codes stored therein.
[0089] The diagnostic tool scans the vehicle's ECU, pulling stored fault codes from it. These fault codes are automatically recorded by the vehicle's system when an abnormal condition is detected, and they provide a starting point to indicate possible problem areas. For example, a fault code may be obtained for communication with the electric motor, battery system, sensor, or control unit.
[0090] refer to Figure 4 The embodiment of the present invention specifically discloses that step S200 determines the identification bit according to the fault phenomenon information, including the following steps:
[0091] S210, obtaining key signal data according to the fault phenomenon information;
[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 of key signal data to complete the determination of identification bits.
[0094] As an optional implementation, in S210, the system of the present invention starts to capture and record key signal data according to the fault phenomenon information reported by the vehicle. These signal data refer to important parameters that can reflect the vehicle operation status and system response, such as battery voltage, motor speed, vehicle speed, accelerator pedal position, etc.
[0095] Key signal data content:
[0096] Battery voltage information: reflects the voltage level of the electric vehicle battery pack, which is key to judging the battery status and power supply.
[0097] Motor speed information: records the speed of the electric vehicle motor to help analyze power output and motor operating conditions.
[0098] Vehicle speed information: Measuring the vehicle's current speed is an important basis for determining 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 identification:
[0101] In step S230, the system analyzes the captured key signal data and identifies abnormal values. These abnormal values may indicate that the system is not working as expected or indicate a potential fault. For example, abnormal battery voltage, lower than expected motor speed, or very low accelerator pedal position signal may be an indicator of a problem.
[0102] Determine the identification bit:
[0103] After the abnormal values of key signal data are identified, the system can determine the fault identification bits. These identification bits mark the time point when the system detects a specific abnormal situation, providing a critical time window and data basis for subsequent fault diagnosis and analysis.
[0104] The embodiments of the present invention can more clearly understand how to use diagnostic tools to obtain fault codes in electric vehicle power system troubleshooting, and determine the identification position of the problem through key signal data, thereby achieving more effective fault diagnosis and solutions.
[0105] refer to Figure 5 The embodiment of the present invention specifically discloses that step S300 records vehicle status data according to the identification bit, including the following steps:
[0106] S310, setting trigger condition information;
[0107] S320, trigger condition information includes a preset fault voltage range, current abnormality parameters, and sensor signal failure information;
[0108] S330, recording a specific signal within 1 second before and after the flag bit is triggered according to the trigger condition information;
[0109] S340. Obtain vehicle status data according to the specific signal.
[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, current abnormality 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 trigger condition information content of the present invention (S320):
[0112] Preset Fault Voltage Range: Identifies abnormal voltage ranges for electric vehicle batteries or other critical electrical components that could indicate power system problems.
[0113] Abnormal current parameters: Set the parameters used to detect abnormal current of the motor 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 S330, the present invention records specific signals within 1 second before and after the identification bit is triggered: when the system detects that the trigger condition is met, it records specific signal data around the identification bit. These data are usually captured within 1 second before and after the identification bit is triggered, because the signal changes during this period are particularly important for fault analysis.
[0116] In S340, the present invention obtains vehicle status data according to the specific signal: the system generates vehicle status data according to the recorded specific signal data. These data may include various parameter values at the triggering moment, such as battery voltage, motor speed, vehicle speed, accelerator pedal position, etc. This information is very important for engineers or technicians to diagnose faults and analyze the causes of problems.
[0117] refer to Figure 6 The embodiment of the present invention specifically discloses that step S400 obtains a troubleshooting signal for each fault, including the following steps:
[0118] S410, obtaining troubleshooting signals for each fault from sensors and actuators in the vehicle controller;
[0119] S420, sorting and merging the troubleshooting signals.
[0120] In step S410 of the embodiment of the present 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 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 the embodiment of the present invention, the troubleshooting signals can be sorted and merged: the obtained troubleshooting signals may come from multiple different systems and sensors, so in step S420, the system will sort and merge these signals. This process helps to centralize the information related to the fault, which is convenient for subsequent analysis and diagnosis.
[0122] The embodiments of the present invention provide a clearer understanding of how the embodiments of the present 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 obtain and organize troubleshooting signals.
[0123] refer to Figure 7 The embodiment of the present invention specifically discloses that step S500 analyzes the vehicle status data and the troubleshooting signal to obtain the fault cause information, including the following steps:
[0124] S510, implementing a rolling storage mechanism in the vehicle controller to store the troubleshooting signals and obtain a signal list;
[0125] S520: Analyze the vehicle status data based on the signal list to obtain fault cause information.
[0126] In step S500, the embodiment of the present invention analyzes the vehicle status data and the troubleshooting signal to obtain fault cause information. In this step, the embodiment of the present invention involves in-depth analysis of the vehicle status data and the troubleshooting signal to obtain accurate fault cause information. The specific steps include:
[0127] Step S510 of the embodiment of the present invention implements a rolling storage mechanism to store the troubleshooting signal:
[0128] In the vehicle controller, a rolling storage mechanism is implemented to continuously record and store troubleshooting signals sent by the vehicle system. These troubleshooting signals can be information such as sensor readings, control unit outputs, or indications of system status. Through the rolling storage mechanism, the system can effectively capture and record all important signal changes, which may be the direct cause or prompt of the fault. Specifically, the operations of this step include:
[0129] Monitor and capture signal changes: The vehicle system regularly sends various troubleshooting signals, which reflect the various states and parameters of the system during operation. The rolling storage mechanism is responsible for real-time monitoring of these signals and storing them in chronological order in the designated storage space of the vehicle controller.
[0130] Generate signal list: The system generates a detailed signal list based on the captured troubleshooting signals. This list will record all important signal types and their corresponding values or states, providing basic data for subsequent analysis.
[0131] In step S520 of the embodiment of the present invention, the vehicle status data is analyzed based on the signal list to obtain the fault cause information:
[0132] After obtaining a detailed list of troubleshooting signals, the system enters the next stage, which is to conduct in-depth analysis based on these signals to determine the possible causes of vehicle failures. The specific analysis steps include:
[0133] Signal correlation analysis: The system correlates the signal list with known vehicle status data. This status data can include engine operating parameters, vehicle speed, fuel consumption, battery voltage and other real-time and historical data.
[0134] Anomaly detection and fault diagnosis: Using advanced data analysis techniques, the system identifies signal patterns or outliers that are inconsistent with normal operation. These anomalies often indicate potential system failures or performance degradation.
[0135] Generate fault cause information: Finally, the system generates a detailed fault cause information report based on the results of the analysis. This report includes a specific fault diagnosis description, possible root causes, and recommended repair measures. This information provides technicians with the necessary guidance to quickly and accurately resolve possible vehicle problems.
[0136] In summary, step S500 provides a method and system for diagnosing vehicle faults efficiently and accurately by effectively combining the real-time capture of troubleshooting signals with the in-depth analysis of vehicle status data. This not only helps to improve vehicle maintenance efficiency, but also reduces maintenance costs and enhances the user's vehicle experience.
[0137] refer to Figure 8 The vehicle power system fault troubleshooting method specifically disclosed in the embodiment of the present invention further includes the following steps:
[0138] S600, upload the signal list to the cloud for backup;
[0139] S700. Read a signal list from the vehicle-mounted terminal.
[0140] As an optional implementation, in the step of uploading the signal list to the cloud for backup in S600 of the present invention, the vehicle power system troubleshooting method involves uploading a pre-defined signal list to the cloud for backup through the vehicle terminal. 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 to ensure the security and reliability of the data. In addition, cloud backup can also facilitate subsequent data analysis and fault diagnosis, allowing engineers to access the data anytime and anywhere and conduct further analysis.
[0141] In the step of reading the signal list from the vehicle-mounted terminal in S700 of the present invention, the power system troubleshooting method requires reading the signal list previously uploaded and stored in the cloud from the vehicle-mounted terminal. This process may involve obtaining the backed-up signal list data from the cloud through the interface of the vehicle-mounted terminal or a specific software tool. The signal list is read for subsequent signal analysis and fault diagnosis. As a key bridge connecting the vehicle's internal system and cloud data, the vehicle-mounted terminal can effectively support data transmission and exchange, thereby helping engineers quickly and accurately locate and solve possible fault problems in the vehicle's power system.
[0142] The complete implementation of these two steps can ensure that when a problem occurs in the vehicle power system, the necessary signal data can be quickly acquired and analyzed, thereby improving the efficiency and accuracy of fault diagnosis.
[0143] As an optional implementation, refer to Fig. 9 , the present invention comprises the following steps:
[0144] Determine the identification bit of each fault according to the phenomenon of each fault to be checked;
[0145] Identify the signals required for each type of troubleshooting;
[0146] Arrange the signals required for each troubleshooting, merge the same signals, and determine the signal list required for troubleshooting;
[0147] The signals required for troubleshooting are stored in the vehicle controller in a rolling manner and updated every 1s (which can be calibrated according to different requirements);
[0148] When the fault generation flag is triggered, the signal required for specific fault troubleshooting is stored 1 second before and after the flag is triggered;
[0149] Analyze the cause of system failure based on stored signals.
[0150] The stored signals can be read at any time through the vehicle terminal and regularly uploaded to the cloud for backup.
[0151] For each signal required for troubleshooting determined above, the same and similar signals are sorted and merged to reduce the signal storage amount and memory consumption as much as possible, and finally a list of stored signals is determined.
[0152] The determined stored signal list 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 there is no fault generating identification bit triggered.
[0153] When the fault generation flag is triggered, the signal required for specific fault troubleshooting when the specific flag determined in the previous step 1s before and after the flag is triggered is stored.
[0154] The present invention analyzes the cause of system failure based on the stored signal.
[0155] refer to Fig. 9 , embodiments of the present invention include:
[0156] Example 1: Analysis of power limitation problem
[0157] 1. Definition of power limitation problem: the current output capacity of the power system is less than or equal to 20% (calibrated quantity) of the external characteristics of the system. When this condition is met, the flag is triggered.
[0158] 2. When the identification bit is triggered, the accelerator pedal opening, vehicle speed, brake pedal opening, motor current capacity, battery current capacity, vehicle controller torque request, motor current output torque, battery current and other signals are stored 1 second before and after the identification bit.
[0159] 3. Identify the problem based on the above signals and determine the real cause of the problem.
[0160] Example 2: Analysis of accelerator pedal failure
[0161] 1. The accelerator pedal fault problem is defined. The vehicle controller reports the accelerator pedal fault code. When this condition is met, the flag is triggered.
[0162] 2. When the identification position is triggered, the accelerator pedal power supply signal and accelerator pedal opening signal 1 second before and after the identification position are stored.
[0163] 3. Identify the problem based on the above signals and determine whether the cause of the accelerator pedal fault code is a power supply problem or an opening signal problem.
[0164] The signals used in all instances are sorted and merged to determine all the signals for rolling storage.
[0165] As an optional implementation, the present invention describes a method for troubleshooting and analyzing system faults, which identifies and solves problems such as vehicle power and accelerator pedal by rolling storage of key signals. The following is a summary of the implementation steps of the invention:
[0166] Overview of execution steps:
[0167] Define the fault criteria:
[0168] Determine the specific defining conditions for each fault, such as limited power or accelerator pedal failure. These conditions are usually based on the system's monitoring and diagnostic capabilities, such as specific fault codes or performance indicators reaching or falling below a predetermined threshold.
[0169] Flag trigger conditions:
[0170] When the fault delimitation conditions are met, the system triggers a flag to indicate that a fault may exist.
[0171] Signal storage:
[0172] When the flag is triggered, the system starts to roll and store key signal data. These signals include but are not limited to accelerator pedal opening, vehicle speed, brake pedal opening, motor capacity, battery capacity, torque requested by the vehicle controller, motor output torque, battery current, etc.
[0173] Problem identification and root cause determination:
[0174] Use the stored signal data to analyze the problem to determine the real cause of the fault. For example, for a power limitation problem, it may be necessary to analyze the changes in motor capacity and battery capacity, while for an accelerator pedal fault, it may be necessary to analyze the accelerator pedal opening signal and power supply signal.
[0175] Signal sorting and merging:
[0176] All the signals required for possible faults are collated and merged to ensure that the system can effectively capture and store critical data.
[0177] Storage and update frequency:
[0178] The signal is rolled and stored in the vehicle controller, usually updated once a second, to ensure that signal changes before and after key events are recorded in a timely manner.
[0179] Data backup and management:
[0180] The stored signal data can be read at any time through the on-board terminal and uploaded to the cloud regularly for backup and analysis to facilitate long-term data management and fault trend analysis.
[0181] Detailed description of the execution steps:
[0182] Step 1: Define the fault criteria
[0183] Identify specific conditions such as limited power or accelerator pedal failure, such as motor capability less than 20% of the system's out-of-system characteristics, or the vehicle controller reporting a specific accelerator pedal fault code.
[0184] Step 2: Identify the trigger condition
[0185] When the fault definition conditions are met, the system generates an identification bit, and the storage of the fault signal begins when the identification bit is triggered.
[0186] Step 3: Signal Storage
[0187] The key signal data within 1 second before and after the storage flag is triggered includes accelerator pedal opening, vehicle speed, brake pedal opening, motor capacity, battery capacity, vehicle controller torque request, motor output torque, battery current, etc.
[0188] Step 4: Problem identification and root cause determination
[0189] Use stored signal data for problem identification and analysis to determine the root cause of a fault, such as limited power due to insufficient battery capacity or a fault in the accelerator pedal power supply or opening signal.
[0190] Step 5: Signal sorting and merging
[0191] All possible troubleshooting signals are collated and combined to ensure the system is able to fully record and analyze all critical data.
[0192] Step 6: Storage and Update Frequency
[0193] Rolling storage is implemented in the vehicle controller, and signal data is updated once a second to ensure timely recording of signal status changes before and after key events.
[0194] Step 7: Data backup and management
[0195] The stored signal data can be read at any time through the on-board terminal and uploaded 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 problems can be identified and resolved in a timely and accurate manner during vehicle operation, thereby improving vehicle stability and reliability.
[0197] refer to Fig.10 On the other hand, an embodiment of the present invention provides a vehicle power system fault troubleshooting 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, the vehicle power system fault troubleshooting method as described above is implemented.
[0198] The vehicle power system fault troubleshooting device according to the embodiment of the present invention includes a memory and a processor.
[0199] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0200] The memory may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage. Among them, ROM can store static data or instructions required by the processor or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even after the computer is powered off. In some embodiments, the permanent storage device uses a large-capacity storage device (such as a magnetic or optical disk, flash memory) as a permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as a dynamic random access memory. The system memory may store some or all instructions and data required by the processor at run time. In addition, the memory may 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 may also be used. In some embodiments, the memory may include a readable and / or writable removable storage device, such as a laser disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, double-layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, mini SD card, Micro-SD card, etc.), a magnetic floppy disk, etc. The computer-readable storage medium does not include carrier waves and transient electronic signals transmitted wirelessly or wired.
[0201] The memory stores executable codes, and when the executable codes are processed by the processor, the processor can execute part or all of the methods described above.
[0202] On the other hand, an embodiment of the present invention provides a vehicle, the vehicle including the vehicle power system fault troubleshooting device as described above.
[0203] The vehicle of the embodiment of the present invention includes the electric drive assembly of the above-mentioned vehicle power system troubleshooting device. Specifically, the vehicle can be a private car, such as a sedan, SUV, MPV or pickup truck. The vehicle can also be an operating vehicle, such as a van, bus, small truck or large trailer. The vehicle can be a gasoline 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 are described above with reference to the accompanying drawings, but the scope of the rights of the present application is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present application should be within the scope of the rights of the present application.
Claims
1. A vehicle power system fault troubleshooting method, characterized in that: The method comprises the following steps: Obtain fault phenomenon information; Determine the identification position according to the fault phenomenon information; Recording vehicle status data according to the identification bit; Get troubleshooting signals for each fault; The vehicle status data and the troubleshooting signal are analyzed to obtain fault cause information.
2. The method according to claim 1, characterized in that The method of obtaining fault phenomenon information comprises the following steps: Scan vehicle systems and obtain fault codes; Obtaining fault phenomenon information according to the fault code; The fault phenomenon information includes battery management system fault information, electric drive system fault information, and charging system fault information.
3. The method according to claim 2, characterized in that Scanning the vehicle system and obtaining the fault code comprises the following steps: Use a diagnostic tool to scan the vehicle's electronic control unit and get the fault code.
4. The method according to claim 1, characterized in that: Determining the identification bit according to the fault phenomenon information includes the following steps: Obtaining key signal data according to the fault phenomenon information; The key signal data includes battery voltage information, motor speed information, vehicle speed information, and accelerator pedal position information; The abnormal values of the key signal data are identified to complete the determination of the identification position.
5. The method according to claim 1, characterized in that The step of recording vehicle status data according to the identification bit comprises the following steps: Set trigger condition information; The trigger condition information includes a preset fault voltage range, current abnormality parameters, and sensor signal failure information; According to the trigger condition information, record the specific signal within 1 second before and after the flag is triggered; Vehicle status data is obtained according to the specific signal.
6. The method according to claim 1, characterized in that The step of obtaining the troubleshooting signal for each fault comprises the following steps: Obtain troubleshooting signals for each fault from sensors and actuators in the vehicle controller; The troubleshooting signals are sorted and merged.
7. The method according to claim 1, characterized in that The step of analyzing the vehicle status data and the troubleshooting signal to obtain fault cause information includes the following steps: Implementing a rolling storage mechanism in the vehicle controller to store the troubleshooting signal and obtain a signal list; Based on the signal list, the vehicle status data is analyzed to obtain fault cause information.
8. The method according to claim 7, characterized in that The vehicle power system fault troubleshooting method further includes the following steps: Uploading the signal list to the cloud for backup; The signal list is read from the vehicle-mounted terminal.
9. A vehicle power system troubleshooting device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the vehicle power system troubleshooting method as described in any one of claims 1 to 8 when executing the computer program.
10. A vehicle, characterized in that: The vehicle includes the vehicle power system troubleshooting device as claimed in claim 9.
Citation Information
Patent Citations
Electronic braking system cloud fault recording method, device, equipment and medium
CN116620245A
Vehicle fault information processing method, device and system
CN117472032A
Vehicle diagnosis method, device and equipment and storage medium
CN118012019A
Automobile fault recording method, device and system and storage medium
CN118018383A
New energy automobile remote diagnosis method and system based on cloud computing
CN118331239A
