Vehicle fault diagnosis method, device, equipment, storage medium and program product

Through the pre-built component model and fault mode library, combined with real-time vehicle data for fault identification, the problem of insufficient data accuracy and accuracy in existing vehicle fault diagnosis is solved, efficient and automated fault diagnosis is achieved, and the accuracy of diagnosis is improved. Sex and real-time.

CN118938851APending Publication Date: 2024-11-12深圳市易新亿意软件开发有限公司
View PDF 0 Cites 5 Cited by

Patent Information

Application Number
CN202410979838.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-19
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The data accuracy and accuracy of existing vehicle fault diagnosis methods are poor, relying on manual observation and empirical judgment, and traditional methods have problems such as low accuracy, long diagnosis time, and high dependence on technicians.

Method used

By obtaining real-time vehicle data, fault identification is performed based on the pre-constructed component model, pre-associated fault mode library is called for matching, and fault identification and positioning is performed based on the fault mode library and component model, and finally the vehicle fault diagnosis results are generated.

Benefits of technology

It realizes efficient and accurate fault diagnosis capabilities, automated and unmanned diagnostic processes, can quickly locate faults and determine the cause of faults, improve maintenance efficiency and accuracy, and provide real-time and immediate fault diagnosis results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118938851A_ABST
    Figure CN118938851A_ABST
Patent Text Reader

Abstract

The invention discloses a vehicle fault diagnosis method, device and equipment, a storage medium and a program product, and relates to the technical field of vehicle diagnosis, and the vehicle fault diagnosis method comprises the steps: obtaining real-time vehicle data; based on a pre-constructed component model, performing fault recognition according to the real-time vehicle data to obtain a fault recognition result; and generating a vehicle fault diagnosis result according to the fault identification result. And technical effects are improved. According to the vehicle fault diagnosis method and device, the vehicle fault is accurately recognized and positioned through the pre-constructed component model, and finally the vehicle fault diagnosis result is obtained. The component model can reflect the working characteristics and the mutual influence relationship of the components, and has higher data precision and accuracy compared with the existing vehicle diagnosis technology.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnosis technology, and in particular to a vehicle fault diagnosis method, device, equipment, storage medium and program product. Background Art

[0002] In the field of automobile diagnosis, traditional methods mainly rely on manual observation and empirical judgment, as well as the use of fault code reading tools for fault diagnosis. However, this method has problems such as low accuracy, long diagnosis time, and high dependence on technicians. With the development of information technology and artificial intelligence, virtual simulation technology, fault pattern recognition systems, vehicle simulation platforms and other methods have become emerging solutions. The above methods can simulate the working status of vehicle components to a certain extent and assist diagnosticians in fault location and diagnosis, but the data precision and accuracy are still poor.

[0003] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0004] The main purpose of this application is to provide a vehicle fault diagnosis method, device, equipment, storage medium and program product, aiming to solve the technical problem of poor data precision and accuracy in existing vehicle fault diagnosis methods.

[0005] To achieve the above objectives, the present application proposes a vehicle fault diagnosis method, the method comprising:

[0006] Get real-time vehicle data;

[0007] Based on the pre-built component model, fault identification is performed according to the real-time vehicle data to obtain a fault identification result;

[0008] A vehicle fault diagnosis result is generated according to the fault identification result.

[0009] In one embodiment, before the step of performing fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result, the step further includes:

[0010] Obtain vehicle working status data;

[0011] Based on a preset modeling method, deduction is performed according to the vehicle working state data to obtain component state parameters and component state equations;

[0012] The component model is constructed according to the component state parameters and the component state equation.

[0013] In one embodiment, the step of performing fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result comprises:

[0014] inputting the real-time vehicle data into the component model;

[0015] calling a pre-associated failure mode library through the component model;

[0016] Performing fault pattern matching on the real-time vehicle data through the fault pattern library to obtain a fault pattern matching result;

[0017] According to the fault pattern matching result, fault identification and location are performed in the component model to obtain the fault identification result.

[0018] In one embodiment, before the step of calling the pre-associated failure mode library through the component model, the step further includes:

[0019] Acquiring first fault data and first maintenance data;

[0020] Based on a preset fault classification rule and a component classification rule, classify the first fault data to obtain second fault data;

[0021] Analyzing the first maintenance data to obtain a maintenance data analysis result;

[0022] generating a fault mode mapping relationship according to the analysis results of the second fault data and the maintenance data;

[0023] The fault mode library is constructed based on the second fault data, the maintenance data analysis result and the fault mode mapping relationship, and the fault mode library is associated with the component model.

[0024] In one embodiment, the step of generating a vehicle fault diagnosis result according to the fault identification result includes:

[0025] Based on a preset fault analysis algorithm, a fault analysis is performed according to the fault identification result to obtain a fault analysis result;

[0026] Matching the fault identification result with a preset fault mode library to obtain maintenance suggestion data;

[0027] The vehicle fault diagnosis result is generated based on the fault identification result, fault analysis result and maintenance suggestion data.

[0028] In one embodiment, after the step of generating a vehicle fault diagnosis result according to the fault identification result, the step further includes:

[0029] Receiving vehicle maintenance data;

[0030] Based on a preset optimization algorithm, a comparative analysis is performed according to the vehicle fault diagnosis result and the vehicle maintenance data to generate fault analysis optimization parameters;

[0031] The fault analysis algorithm is optimized according to the fault analysis optimization parameters.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle fault diagnosis device, the vehicle fault diagnosis device comprising:

[0033] A data acquisition module, used to acquire real-time vehicle data;

[0034] A fault identification module, used to perform fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result;

[0035] The result generating module is used to generate a vehicle fault diagnosis result according to the fault identification result.

[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle fault diagnosis device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the vehicle fault diagnosis method described above.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the vehicle fault diagnosis method described above are implemented.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the vehicle fault diagnosis method described above are implemented.

[0039] This application provides a vehicle fault diagnosis method, which uses a pre-built component model to accurately identify and locate vehicle faults, and finally obtains vehicle fault diagnosis results. The component model can reflect the working characteristics and mutual influence of the components, and has higher data precision and accuracy than existing vehicle diagnosis technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0042] Figure 1 A schematic diagram of a process flow provided for the first embodiment of the vehicle fault diagnosis method of the present application;

[0043] Figure 2 A schematic diagram of a flow chart provided for the second embodiment of the vehicle fault diagnosis method of the present application;

[0044] Figure 3 A flow chart of the third embodiment of the vehicle fault diagnosis method of the present application;

[0045] Figure 4 This is a schematic diagram of the module structure of the vehicle fault diagnosis device according to an embodiment of the present application;

[0046] Figure 5 Schematic diagram of the device structure of the hardware operating environment involved in the vehicle fault diagnosis method in the embodiment of the present application.

[0047] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0048] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0049] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0050] The main solutions of the embodiments of this application are:

[0051] Get real-time vehicle data;

[0052] Based on the pre-built component model, fault identification is performed according to the real-time vehicle data to obtain a fault identification result;

[0053] A vehicle fault diagnosis result is generated according to the fault identification result.

[0054] There are several implementation solutions for vehicle fault diagnosis:

[0055] 1. Virtual simulation technology: Through computer simulation and virtual reality technology, the working status of vehicle components can be simulated. Virtual simulation technology can simulate the working principle and behavior of vehicle components, provide visual fault simulation and diagnosis result display, and help diagnosticians understand and locate faults.

[0056] 2. Fault pattern recognition system: Based on big data and machine learning technology, the fault pattern library is established by analyzing vehicle fault data and historical cases. Diagnostics technicians can input vehicle fault symptoms, and the system will match and identify them according to the pattern library, and give possible fault causes and suggestions.

[0057] 3. Vehicle simulation platform: Use computer simulation and emulation technology to establish mathematical and physical models of the vehicle. By inputting vehicle parameters and operating conditions, simulate the working state and operating characteristics of the vehicle, and provide comprehensive analysis and diagnosis of the vehicle system.

[0058] The above solutions have low data precision and accuracy, poor compatibility with actual vehicles, and cannot achieve real-time response.

[0059] This application provides a solution that uses a pre-built component model to accurately identify and locate vehicle faults, and ultimately obtains vehicle fault diagnosis results. The component model can reflect the working characteristics and mutual influence of the components, and has higher data precision and accuracy than existing vehicle diagnostic technologies.

[0060] It can be seen from the above embodiments that the present application provides a vehicle fault diagnosis method, which has the following advantages compared with the prior art:

[0061] 1. Efficient and accurate fault diagnosis capability: Through pre-built component models, efficient and accurate fault diagnosis capability can be achieved. Through the analysis and comparison of real-time vehicle data, faults can be quickly located and the cause of the fault can be determined, improving maintenance efficiency and accuracy.

[0062] 2. Automated and unmanned fault diagnosis process: The automated and unmanned diagnosis process of vehicle faults is realized without human intervention. The system can quickly obtain and analyze the working status data of each component of the vehicle and perform fault diagnosis, reducing the time and cost of manual operation.

[0063] 3. Multi-component collaborative diagnosis capability: Based on the component model and the associated fault mode library, the multi-component collaborative diagnosis capability can be realized. During the fault diagnosis process, the system can comprehensively consider the working status and mutual influence of multiple components to improve the accuracy and comprehensiveness of fault diagnosis.

[0064] 4. Real-time and immediate fault diagnosis results: Through optimized fault analysis algorithms and data processing systems, real-time and immediate fault diagnosis results can be achieved. The diagnosis results can be quickly displayed and output to diagnosticians or related personnel, so that they can take repair measures in time to reduce the impact of faults on vehicles and users.

[0065] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a vehicle fault diagnosis system, etc. The following takes the vehicle fault diagnosis system as an example to illustrate this embodiment and the following embodiments.

[0066] Based on this, the present application embodiment provides a vehicle fault diagnosis method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle fault diagnosis method of the present application.

[0067] In this embodiment, the vehicle fault diagnosis method includes steps S10 to S30:

[0068] Step S10, acquiring real-time vehicle data;

[0069] It should be noted that real-time vehicle data refers to various data generated in real time during the operation of the vehicle, such as engine parameters, sensor readings, etc. These data are the basis for fault diagnosis.

[0070] Step S20, based on the pre-built component model, fault identification is performed according to the real-time vehicle data to obtain a fault identification result;

[0071] The vehicle fault diagnosis system preprocesses the real-time vehicle data, including data cleaning, denoising, data format conversion and other operations to ensure data quality and suitability for model processing. The preprocessed real-time vehicle data is then input into the component model for analysis and comparison through algorithms. This may involve the use of supervised learning, unsupervised learning or deep learning methods to identify whether there are potential faults or abnormal conditions at present, and ultimately obtain fault identification results. The component models correspond to vehicle components such as engines, transmission systems, suspension systems, and braking systems.

[0072] In a feasible implementation manner, step S20 may include steps S401 to S403:

[0073] Step S401, obtaining vehicle operating status data;

[0074] Step S402, based on a preset modeling method, deriving from the vehicle working state data to obtain component state parameters and component state equations;

[0075] Step S403: constructing the component model according to the component state parameters and the component state equation.

[0076] It should be noted that vehicle operating status data may include sensor data (such as engine speed, vehicle speed, oil pressure, etc.), real-time parameters (such as temperature, pressure, etc.) and operating condition information (such as driving speed, acceleration, steering angle, etc.). Vehicle operating status data can be collected through on-board sensors, vehicle bus systems (such as CAN bus), etc.

[0077] The vehicle fault diagnosis system obtains the vehicle working status data through an appropriate data transmission method (such as wired or wireless communication), and then derives the vehicle working status data based on a preset modeling method to obtain component state parameters and component state equations. Common modeling methods include physical models, statistical models, and machine learning models. These parameters and equations can describe the behavior and performance of components under different working conditions, providing a basis for subsequent fault diagnosis and prediction. The derivation may involve steps such as parameter estimation, model training, and verification to ensure that the model can accurately reflect the status of the component. Finally, a component model is constructed based on the component state parameters and component state equations.

[0078] In this embodiment, based on a preset modeling method, a component model is constructed according to the vehicle operating status data. The vehicle fault diagnosis system will use the component model to identify and locate faults, and combine the fault indications or abnormal conditions obtained in real time to further diagnose and analyze the possible causes and impacts of vehicle faults.

[0079] Step S30: generating a vehicle fault diagnosis result according to the fault identification result.

[0080] The vehicle fault diagnosis system analyzes the fault identification results to obtain fault analysis results, which may include the specific fault type identified, possible fault causes or affected vehicle systems, and then obtains maintenance recommendation data based on the fault analysis results. Finally, based on the fault identification results, fault analysis results and maintenance recommendation data, the vehicle fault diagnosis results are generated. The vehicle fault diagnosis results usually include fault description, recommended action plan, predicted impact, etc.

[0081] In addition, the vehicle fault diagnosis system can display and output the diagnosis results for further processing by the diagnostician or other relevant personnel. The diagnosis results can be displayed to the diagnostician through a visual interface, including information such as fault location, fault cause, and recommended repair measures. The display interface can be presented in charts, text, or other forms to facilitate the diagnostician's understanding and judgment. In addition, the diagnosis results can also be output to other systems or devices to achieve the sharing and further processing of fault information.

[0082] This embodiment provides a vehicle fault diagnosis method, which uses a pre-built component model to accurately identify and locate vehicle faults, and finally obtains a vehicle fault diagnosis result. The component model can reflect the working characteristics and mutual influence of the components, and has higher data precision and accuracy than the existing vehicle diagnosis technology.

[0083] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 , step S20 may include steps S201 to S204:

[0084] Step S201, inputting the real-time vehicle data into the component model;

[0085] Step S202, calling a pre-associated fault mode library through the component model;

[0086] Step S203, performing fault pattern matching on the real-time vehicle data through the fault pattern library to obtain a fault pattern matching result;

[0087] Step S204: performing fault identification and location in the component model according to the fault pattern matching result to obtain the fault identification result.

[0088] The vehicle fault diagnosis system inputs real-time vehicle data into the component model, and then calls the pre-associated fault mode library through the component model. The fault mode library records the possible fault phenomena, characteristics and corresponding fault causes of each component. These fault modes can be obtained by analyzing a large number of fault cases and actual maintenance data. The system will use the real-time vehicle data of the component model to match the patterns in the fault mode library. This matching process may use pattern recognition, data mining or professional knowledge to compare the differences between the actual observed data and the expected fault mode to obtain the fault mode matching results. The fault mode matching results are then used as input to analyze the possible fault locations in the component model through the component model using special algorithms and logic. This may involve model simulation, pattern recognition or rule-based reasoning methods to ultimately obtain fault identification results. These results usually include the identified faulty components or systems, as well as the nature and severity of the fault. For example, the system may determine that a sensor in the engine is faulty, or that there is a hydraulic leak in the brake system.

[0089] In a feasible implementation manner, before step S302, steps S501 to S505 may also be included:

[0090] Step S501, obtaining first fault data and first maintenance data;

[0091] Step S502, classifying the first fault data based on preset fault classification rules and component classification rules to obtain second fault data;

[0092] Step S503, analyzing the first maintenance data to obtain maintenance data analysis results;

[0093] Step S504, generating a fault mode mapping relationship according to the analysis results of the second fault data and maintenance data;

[0094] Step S505: construct the fault mode library according to the second fault data, the maintenance data analysis result and the fault mode mapping relationship, and associate the fault mode library with the component model.

[0095] It should be noted that the first fault data refers to the fault phenomenon and related data recorded during the operation of the vehicle or system. These data may include but are not limited to: fault codes (such as OBD fault codes of automobiles), sensor data anomalies, abnormal behavior of the system or performance degradation, and the first maintenance data refers to the maintenance records and maintenance operations previously performed on the vehicle or system. These data include: the fault conditions that have occurred and their repair process, the replaced parts and components, the time and place of maintenance, and the maintenance methods and tools used.

[0096] The vehicle fault diagnosis system obtains first fault data and first maintenance data, and then classifies the first fault data based on preset fault classification rules and component classification rules to obtain second fault data. For example, according to the fault code and abnormal behavior, the fault data is divided into different fault types, such as electrical fault, mechanical fault, sensor fault, etc. According to the preset component classification rules, the fault data is associated with specific components or systems that may be affected, such as engines, transmissions, braking systems, etc., and then the first maintenance data is analyzed to obtain maintenance data analysis results. The main analysis objectives include: fault mode identification, component loss analysis, maintenance effect evaluation, etc. Then, according to the second fault data and the maintenance data analysis results, a fault mode mapping relationship is generated to associate the fault mode with possible root causes, system components and environmental conditions. This may include the use of fault tree analysis, cause-effect analysis or other structured methods. Finally, according to the second fault data, the maintenance data analysis results and the fault mode mapping relationship, the fault mode library is constructed and associated with the component model.

[0097] In this embodiment, the fault mode library is constructed based on the first fault data and the first maintenance data, and the fault mode library is associated with the component model. The system can use historical fault data and maintenance experience to establish a complete fault diagnosis foundation, thereby improving the accuracy and efficiency of fault diagnosis in practical applications.

[0098] This embodiment provides a vehicle fault diagnosis method, which is based on component models and a fault mode library, performs fault identification according to real-time vehicle data, and obtains fault identification results. The system can monitor real-time vehicle data, identify fault modes, and locate fault locations, providing important guidance and decision support for subsequent maintenance and repair work.

[0099] Based on the first embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 , step S30 may include steps S301 to S303:

[0100] Step S301, based on a preset fault analysis algorithm, perform fault analysis according to the fault identification result to obtain a fault analysis result;

[0101] Step S302, matching the fault identification result with a preset fault mode library to obtain maintenance suggestion data;

[0102] Step S303, generating the vehicle fault diagnosis result according to the fault identification result, fault analysis result and maintenance suggestion data.

[0103] The vehicle fault diagnosis system is based on a preset fault analysis algorithm. It performs fault analysis according to the fault identification results to obtain fault analysis results, which includes deriving potential fundamental problems or anomalies from existing data. Common fault analysis algorithms include rule-based analysis, pattern matching, statistical methods, machine learning, etc. Depending on the specific situation, you can choose a suitable algorithm or combine multiple algorithms to achieve the goal of fault diagnosis. Then, the fault identification results are compared and matched with the pre-established fault mode library to determine the best matching fault mode. Based on the matched fault mode, specific maintenance suggestion data is generated, which may include recommended repair steps, suggestions for replacing parts, corrective operations or system adjustment plans, etc. Finally, the fault identification results, fault analysis results and maintenance suggestion data are integrated to generate the vehicle fault diagnosis results.

[0104] For example, taking machine learning as an example, the fault analysis algorithm can be analyzed as follows:

[0105] 1. Data collection and preprocessing:

[0106] Data collection: First, collect data containing faults and normal operating conditions. This data can be sensor data, log records, equipment operation records, etc., covering the behavior of the system under different operating conditions.

[0107] Preprocessing: Preprocess the collected data, including data cleaning, noise removal, feature selection or extraction, etc. This step is to ensure that the subsequent model training can effectively utilize the data.

[0108] 2. Feature Engineering:

[0109] Feature extraction: Extract features from preprocessed data. These features can be numerical, time series, spectral, or other features that domain experts consider relevant.

[0110] Feature transformation: Features may need to be standardized, normalized, or otherwise transformed to ensure that they have the appropriate value range and distribution during model training.

[0111] 3. Select model and train:

[0112] Model selection: Depending on the characteristics of the problem and the type of data, choose an appropriate machine learning model, such as support vector machine (SVM), decision tree, random forest, neural network, etc.

[0113] Model training: Use the labeled fault and normal operation datasets to train the selected model. The training goal is to enable the model to accurately distinguish between normal operation and different types of failure modes.

[0114] 4. Model evaluation and optimization:

[0115] Cross-validation: Use cross-validation techniques to evaluate the performance of the model and ensure the generalization ability of the model on unseen data.

[0116] Optimization: Adjust the model’s hyperparameters or perform feature engineering improvements based on the evaluation results to improve the model’s accuracy and robustness.

[0117] 5. Fault analysis and result interpretation:

[0118] Fault identification and analysis: Use the trained model to identify faults on new data. The model will make predictions based on the input data features to determine whether there is a fault.

[0119] Fault analysis results: Based on the fault prediction results output by the model, a fault analysis is performed. This may include identification of the fault type, possible root cause analysis, and recommended repair or treatment measures.

[0120] 6. Feedback and iteration:

[0121] Based on the feedback and verification results from actual applications, the models and algorithms are adjusted and optimized, including updating the data set, retraining the model, or improving the algorithm to ensure the accuracy and reliability of the system in long-term operation.

[0122] In a feasible implementation manner, step S301 may further include steps S601 to S603:

[0123] Step S601, receiving vehicle maintenance data;

[0124] Step S602, based on a preset optimization algorithm, a comparative analysis is performed according to the vehicle fault diagnosis result and the vehicle maintenance data to generate a fault analysis optimization parameter;

[0125] Step S603: optimizing the fault analysis algorithm according to the fault analysis optimization parameters.

[0126] It should be noted that vehicle maintenance data may include but is not limited to maintenance operation records, parts replacement information, fault repair effects, system feedback and test results, and maintenance personnel's notes and suggestions.

[0127] The vehicle fault diagnosis system receives vehicle maintenance data, and then based on a preset optimization algorithm, performs comparative analysis based on the vehicle fault diagnosis results and vehicle maintenance data. This may include comparing the consistency between the predicted fault type, location or cause and the actual problems found, and determining the accuracy of the fault diagnosis and possible improvement points, such as whether there are common misdiagnoses or missed diagnoses, generating fault analysis optimization parameters, and finally optimizing the fault analysis algorithm based on the fault analysis optimization parameters.

[0128] Among them, the optimization algorithm can be selected from genetic algorithm, particle swarm optimization algorithm, simulated annealing algorithm, artificial neural network, ant colony algorithm, degradation algorithm, etc. Taking the optimization algorithm as simulated degradation algorithm as an example, the optimization process using simulated annealing algorithm is as follows:

[0129] The simulated annealing algorithm is a heuristic optimization algorithm that simulates the lattice structure adjustment process during metal annealing. It is used to solve complex optimization problems, especially in global optimization and multi-modal optimization problems. The following is the basic process of optimization using the simulated annealing algorithm:

[0130] 1. Generation of initial solution:

[0131] Generate an initial solution randomly or according to the specific requirements of the problem. This initial solution can be a possible solution to the problem or randomly selected in the search space.

[0132] 2. Set the initial temperature and annealing strategy:

[0133] Set the initial temperature parameters and annealing strategy. The temperature determines the probability of accepting an inferior solution, while the annealing strategy determines how the temperature decreases over time, usually through an exponential or linear function.

[0134] 3. Status update and evaluation:

[0135] At each temperature, a new candidate solution is generated based on the current solution. This process can be random, such as by modifying some parts of the current solution through small perturbations to generate new solutions.

[0136] The newly generated solution is evaluated and its objective function value (or energy value) is calculated. The objective function is usually a problem-specific indicator to be minimized or maximized, such as cost, error, etc.

[0137] 4. Decision to accept or reject the new solution:

[0138] According to the Metropolis criterion (or Boltzmann criterion), decide whether to accept the newly generated solution:

[0139] If the new solution is better than the current solution, just accept it.

[0140] If the new solution is worse than the current one, accept it with some probability. This probability depends on the temperature and the energy difference between the new and old solutions, and usually follows a probability distribution.

[0141] 5. Temperature update:

[0142] According to the set annealing strategy, the temperature is lowered to reduce the probability of accepting inferior solutions. This process can be a linear, exponential or other functional cooling strategy.

[0143] 6. Termination conditions:

[0144] The algorithm stops when the termination condition is reached, such as reaching the maximum number of iterations, the temperature drops below a threshold, or the objective function value converges to a sufficiently small change range.

[0145] 7. Output results:

[0146] The final output is the optimal solution or a solution close to the optimal solution found by the algorithm during the search process.

[0147] The simulated annealing algorithm uses the strategy of randomly exploring and accepting inferior solutions in the solution space, while ensuring global search capabilities, and gradually moving towards a better solution. This makes it very robust and adaptable when dealing with complex optimization problems.

[0148] In this embodiment, the fault analysis algorithm is optimized and improved based on the feedback of vehicle maintenance data. The system can not only learn and improve from actual maintenance operations, but also gradually optimize its fault diagnosis and analysis capabilities to improve the overall service quality and efficiency.

[0149] This embodiment provides a vehicle fault diagnosis method, which generates a vehicle fault diagnosis result based on the fault identification result. The entire fault diagnosis and analysis process can be carried out in a systematic manner to ensure the consistency and accuracy from fault identification to the final diagnosis result, thereby improving vehicle maintenance efficiency and reliability.

[0150] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the vehicle fault diagnosis method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0151] This application also provides a vehicle fault diagnosis device, please refer to Figure 4 , the vehicle fault diagnosis device comprises:

[0152] A data acquisition module, used to acquire real-time vehicle data;

[0153] A fault identification module, used to perform fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result;

[0154] The result generating module is used to generate a vehicle fault diagnosis result according to the fault identification result.

[0155] Optionally, before the step of performing fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result, the step further includes:

[0156] Obtain vehicle working status data;

[0157] Based on a preset modeling method, deduction is performed according to the vehicle working state data to obtain component state parameters and component state equations;

[0158] The component model is constructed according to the component state parameters and the component state equation.

[0159] Optionally, the fault identification module 20 is further used for:

[0160] inputting the real-time vehicle data into the component model;

[0161] calling a pre-associated failure mode library through the component model;

[0162] Performing fault pattern matching on the real-time vehicle data through the fault pattern library to obtain a fault pattern matching result;

[0163] According to the fault pattern matching result, fault identification and location are performed in the component model to obtain the fault identification result.

[0164] Optionally, before the step of calling a pre-associated fault mode library through the component model, the step further includes:

[0165] Acquiring first fault data and first maintenance data;

[0166] Based on a preset fault classification rule and a component classification rule, classify the first fault data to obtain second fault data;

[0167] Analyzing the first maintenance data to obtain a maintenance data analysis result;

[0168] generating a fault mode mapping relationship according to the analysis results of the second fault data and the maintenance data;

[0169] The fault mode library is constructed based on the second fault data, the maintenance data analysis result and the fault mode mapping relationship, and the fault mode library is associated with the component model.

[0170] Optionally, the result generating module 30 is further used for:

[0171] Based on a preset fault analysis algorithm, a fault analysis is performed according to the fault identification result to obtain a fault analysis result;

[0172] Matching the fault identification result with a preset fault mode library to obtain maintenance suggestion data;

[0173] The vehicle fault diagnosis result is generated based on the fault identification result, fault analysis result and maintenance suggestion data.

[0174] Optionally, after the step of generating a vehicle fault diagnosis result according to the fault identification result, the step further includes:

[0175] Receiving vehicle maintenance data;

[0176] Based on a preset optimization algorithm, a comparative analysis is performed according to the vehicle fault diagnosis result and the vehicle maintenance data to generate fault analysis optimization parameters;

[0177] The fault analysis algorithm is optimized according to the fault analysis optimization parameters.

[0178] The vehicle fault diagnosis device provided by the present application adopts the vehicle fault diagnosis method in the above embodiment, which can solve the technical problem of poor data precision and accuracy of the existing vehicle fault diagnosis method. Compared with the prior art, the beneficial effects of the vehicle fault diagnosis device provided by the present application are the same as the beneficial effects of the vehicle fault diagnosis method provided by the above embodiment, and the other technical features in the vehicle fault diagnosis device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0179] The present application provides a vehicle fault diagnosis device, which includes: at least one processor; and a memory that is communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle fault diagnosis method in the above-mentioned embodiment one.

[0180] Reference below Figure 5 , which shows a schematic diagram of the structure of a vehicle fault diagnosis device suitable for implementing the embodiment of the present application. The vehicle fault diagnosis device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The vehicle fault diagnosis device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0181] like Figure 5As shown, the vehicle fault diagnosis device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle fault diagnosis device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the vehicle fault diagnosis device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a vehicle fault diagnosis device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided alternatively.

[0182] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0183] The vehicle fault diagnosis device provided by the present application adopts the vehicle fault diagnosis method in the above embodiment, which can solve the technical problem of poor data precision and accuracy of the existing vehicle fault diagnosis method. Compared with the prior art, the beneficial effects of the vehicle fault diagnosis device provided by the present application are the same as the beneficial effects of the vehicle fault diagnosis method provided by the above embodiment, and the other technical features in the vehicle fault diagnosis device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0184] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0185] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0186] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle fault diagnosis method in the above-mentioned embodiment.

[0187] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0188] The computer-readable storage medium may be included in the vehicle fault diagnosis device; or may exist independently without being assembled into the vehicle fault diagnosis device.

[0189] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the vehicle fault diagnosis device, the vehicle fault diagnosis device:

[0190] Get real-time vehicle data;

[0191] Based on the pre-built component model, fault identification is performed according to the real-time vehicle data to obtain a fault identification result;

[0192] A vehicle fault diagnosis result is generated according to the fault identification result.

[0193] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0194] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0195] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0196] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle fault diagnosis method, and can solve the technical problem of poor data precision and accuracy in the existing vehicle fault diagnosis method. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle fault diagnosis method provided by the above-mentioned embodiment, and will not be repeated here.

[0197] The present application also provides a computer program product, including a computer program, which implements the steps of the vehicle fault diagnosis method as described above when executed by a processor.

[0198] The computer program product provided by the present application can solve the technical problem of poor data precision and accuracy in the existing vehicle fault diagnosis method. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the vehicle fault diagnosis method provided by the above embodiment, which will not be repeated here.

[0199] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A vehicle fault diagnosis method, characterized in that: The method comprises: Get real-time vehicle data; Based on the pre-built component model, fault identification is performed according to the real-time vehicle data to obtain a fault identification result; A vehicle fault diagnosis result is generated according to the fault identification result.

2. The method according to claim 1, characterized in that Before the step of performing fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result, the method further includes: Obtain vehicle working status data; Based on a preset modeling method, deduction is performed according to the vehicle working state data to obtain component state parameters and component state equations; The component model is constructed according to the component state parameters and the component state equation.

3. The method according to claim 1, characterized in that The step of performing fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result comprises: inputting the real-time vehicle data into the component model; calling a pre-associated failure mode library through the component model; Performing fault pattern matching on the real-time vehicle data through the fault pattern library to obtain a fault pattern matching result; According to the fault pattern matching result, fault identification and location are performed in the component model to obtain the fault identification result.

4. The method according to claim 3, characterized in that Before the step of calling the pre-associated failure mode library through the component model, the method further includes: Acquiring first fault data and first maintenance data; Based on a preset fault classification rule and a component classification rule, classify the first fault data to obtain second fault data; Analyzing the first maintenance data to obtain a maintenance data analysis result; generating a fault mode mapping relationship according to the analysis results of the second fault data and the maintenance data; The fault mode library is constructed based on the second fault data, the maintenance data analysis result and the fault mode mapping relationship, and the fault mode library is associated with the component model.

5. The method according to claim 1, characterized in that The step of generating a vehicle fault diagnosis result according to the fault identification result comprises: Based on a preset fault analysis algorithm, a fault analysis is performed according to the fault identification result to obtain a fault analysis result; Matching the fault identification result with a preset fault mode library to obtain maintenance suggestion data; The vehicle fault diagnosis result is generated based on the fault identification result, fault analysis result and maintenance suggestion data.

6. The method according to claim 5, characterized in that After the step of generating a vehicle fault diagnosis result according to the fault identification result, the step further includes: Receiving vehicle maintenance data; Based on a preset optimization algorithm, a comparative analysis is performed according to the vehicle fault diagnosis result and the vehicle maintenance data to generate fault analysis optimization parameters; The fault analysis algorithm is optimized according to the fault analysis optimization parameters.

7. A vehicle fault diagnosis device, characterized in that: The device comprises: A data acquisition module, used to acquire real-time vehicle data; A fault identification module, used to perform fault identification based on the pre-built component model and the real-time vehicle data to obtain a fault identification result; The result generating module is used to generate a vehicle fault diagnosis result according to the fault identification result.

8. A vehicle fault diagnosis device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the vehicle fault diagnosis method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the vehicle fault diagnosis method as described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the vehicle fault diagnosis method according to any one of claims 1 to 6 are implemented.

Citation Information

Cited By

  • Vehicle diagnosis report generation method and device, equipment and storage medium

    CN119690046A

  • Vehicle fault diagnosis method based on OBD data

    CN120065998A

  • A vehicle fault diagnosis method based on OBD data

    CN120065998B

  • Automobile suspension abnormal sound diagnosis method and device, electronic equipment and storage medium

    CN121185417A

  • Vehicle fault prediction method based on AUTOSAR

    CN121560006A