Vehicle brake jitter checking method, vehicle and storage medium

Through visual wear detection, rough inspection and detailed vibration sensing data and braking pressure data analysis, efficient and accurate inspection of vehicle braking jitter is achieved, and the problems of low efficiency and high cost in the existing technology are solved, which has improved the Safety and comfort of the vehicle.

CN118961242APending Publication Date: 2024-11-15CHINA FAW CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411195507.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-29
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The prior art has problems such as long implementation cycle, high cost, low efficiency, and difficult to effectively predict and investigate problems in the early stages of the problem.

Method used

A vehicle brake jitter detection method is proposed, including visual wear detection, rough inspection, braking test, vibration sensing data and braking pressure analysis data, and obtain vibration analysis data and braking pressure analysis through frequency and time domain analysis. Data, conduct detailed inspections to improve inspection efficiency and accuracy.

Benefits of technology

It improves the efficiency and accuracy of vehicle braking jitter inspection, reduces maintenance time and cost, and improves the safety and comfort of the vehicle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118961242A_ABST
    Figure CN118961242A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of vehicle braking, in particular to a vehicle braking jitter checking method, a vehicle and a storage medium. According to the vehicle brake jitter checking method, visual wear detection needs to be carried out on the brake component of the target vehicle to obtain visual detection data; carrying out rough checking operation on the brake component based on the visual detection data to obtain rough checking data; driving the target vehicle to perform a braking test; vibration sensing data and brake pressure data generated in the brake test process of the target vehicle are obtained; carrying out vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data; brake pressure analysis is conducted on the brake pressure data, and brake pressure analysis data are obtained; and on the basis of the vibration analysis data and the brake pressure analysis data, fine checking operation is conducted on the brake component, and fine checking data are obtained. Therefore, the troubleshooting efficiency and accuracy can be improved, the maintenance time and cost of the vehicle are reduced, and the safety and comfort of the vehicle are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle braking technology, and in particular to a vehicle brake jitter troubleshooting method, a vehicle, and a storage medium. Background Art

[0002] Brake judder usually occurs when the vehicle brakes, manifesting as the shaking of the steering wheel and the body of the vehicle, which not only affects the driving experience, but also affects driving safety. At present, the investigation of brake judder mainly relies on actual vehicle braking tests, and the fault is diagnosed by replacing components such as brake discs and brake pads. However, this method has many shortcomings, such as long implementation cycle, high cost, low efficiency, and difficulty in effectively predicting and troubleshooting problems in the early stages.

[0003] In related technologies, there are also some studies dedicated to reducing the occurrence of brake judder by improving the manufacturing process of brake discs and optimizing the material of brake pads, but most of these studies focus on hardware improvements and rarely touch on the optimization of the brake judder troubleshooting process itself. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a vehicle brake judder troubleshooting method, a vehicle, and a storage medium, which can improve the troubleshooting efficiency and accuracy, reduce the vehicle maintenance time and cost, and improve the safety and comfort of the vehicle.

[0005] A vehicle brake judder troubleshooting method according to a first aspect of the present application includes:

[0006] Perform visual wear inspection on the brake components of the target vehicle to obtain visual inspection data;

[0007] Performing a rough inspection operation on the brake component based on the visual inspection data to obtain rough inspection data;

[0008] In response to the rough screening data satisfying a preset rough screening condition, driving the target vehicle to perform a brake test;

[0009] Acquiring vibration sensing data and brake pressure data generated by the target vehicle during a brake test;

[0010] Performing vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data;

[0011] performing brake pressure analysis on the brake pressure data to obtain brake pressure analysis data;

[0012] Based on the vibration analysis data and the brake pressure analysis data, a fine inspection operation is performed on the brake component to obtain fine inspection data.

[0013] According to some embodiments provided by the present application, performing vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data includes:

[0014] Performing frequency domain analysis on the vibration sensor data to obtain frequency component information corresponding to the vibration sensor data;

[0015] Performing time domain analysis on the vibration sensing data to determine the vibration intensity and vibration duration;

[0016] The frequency component information, the vibration intensity and the vibration duration are integrated to obtain the vibration analysis data.

[0017] According to some embodiments provided by the present application, performing time domain analysis on the vibration sensing data to determine the vibration intensity and vibration duration includes:

[0018] Performing time domain analysis on the vibration sensor data to determine the vibration peak value, vibration average value and vibration duration corresponding to the vibration sensor data;

[0019] The vibration intensity is determined based on the vibration peak value and the vibration average value.

[0020] According to some embodiments provided by the present application, performing brake pressure analysis on the brake pressure data to obtain brake pressure analysis data includes:

[0021] Performing brake pressure analysis on the brake pressure data to obtain the brake pressure magnitude, pressure response speed and pressure duration of the target vehicle during the brake test;

[0022] The brake pressure magnitude, the pressure response speed and the pressure duration are integrated to obtain the brake pressure analysis data.

[0023] According to some embodiments provided by the present application, the fine inspection data includes vibration inspection data and pressure inspection data, and the fine inspection operation is performed on the brake component based on the vibration analysis data and the brake pressure analysis data to obtain the fine inspection data, including:

[0024] Based on the vibration analysis data, determining the frequency component information, vibration intensity and vibration duration of the target vehicle during the braking test;

[0025] Based on the brake pressure analysis data, determine the brake pressure magnitude, pressure response speed and pressure duration of the target vehicle during the brake test;

[0026] Performing a vibration inspection on the frequency component information, the vibration intensity and the vibration duration to obtain the vibration inspection data;

[0027] A precise pressure check is performed on the brake pressure size, the pressure response speed and the pressure duration to obtain the pressure check data.

[0028] According to some embodiments provided by the present application, the vibration troubleshooting data includes vibration source troubleshooting data, vibration intensity troubleshooting data, and vibration stability troubleshooting data, and the vibration troubleshooting is performed on the frequency component information, the vibration intensity, and the vibration duration to obtain the vibration troubleshooting data, including:

[0029] Performing vibration source screening on the frequency component information based on the natural vibration frequency of the target vehicle to obtain the vibration source screening data;

[0030] Performing a vibration intensity check on the vibration intensity based on a preset intensity threshold to obtain the vibration intensity check data;

[0031] The vibration stability check is performed on the vibration duration based on a preset time threshold to obtain the vibration stability check data.

[0032] According to some embodiments provided by the present application, before the vibration source screening of the frequency component information based on the natural vibration frequency of the target vehicle is performed, the method further includes:

[0033] Obtaining the vehicle mass and vehicle spring strength corresponding to the target vehicle during the braking test;

[0034] Based on the vehicle mass and the vehicle spring strength, a natural vibration frequency corresponding to the target vehicle is determined.

[0035] According to some embodiments provided by the present application, the pressure check data includes pressure size check data, pressure response check data and pressure stability check data. The pressure check is performed on the brake pressure size, the pressure response speed and the pressure duration to obtain the pressure check data, including:

[0036] Checking the pressure magnitude based on a preset pressure threshold to obtain pressure magnitude checking data;

[0037] Performing a pressure response check on the pressure response speed based on a preset brake response time threshold to obtain the pressure response check data;

[0038] The pressure stability is checked on the pressure duration based on a preset pressure time threshold to obtain the pressure stability check data.

[0039] A vehicle according to a second aspect of the present application includes:

[0040] The vehicle stores a program, and the program is executed to implement the vehicle brake jitter troubleshooting method as described in any one of the embodiments of the first aspect of the present application.

[0041] A computer-readable storage medium according to an embodiment of the third aspect of the present application includes:

[0042] The computer-readable storage medium stores a program, and the program is executed to implement the vehicle brake jitter troubleshooting method as described in any one of the embodiments of the first aspect of the present application.

[0043] The vehicle brake judder troubleshooting method, vehicle, and storage medium according to the embodiments of the present application have at least the following beneficial effects:

[0044] According to the vehicle brake jitter troubleshooting method of the embodiment of the present application, it is necessary to perform visual wear detection on the brake components of the target vehicle to obtain visual detection data; perform a rough inspection operation on the brake components based on the visual detection data to obtain rough inspection data; in response to the rough inspection data satisfying the preset rough screening conditions, drive the target vehicle to perform a brake test; obtain the vibration sensor data and brake pressure data generated by the target vehicle during the brake test; perform vehicle vibration analysis on the vibration sensor data to obtain vibration analysis data; perform brake pressure analysis on the brake pressure data to obtain brake pressure analysis data; based on the vibration analysis data and the brake pressure analysis data, perform a fine inspection operation on the brake components to obtain fine inspection data. In this way, it is possible to improve the efficiency and accuracy of the inspection, reduce the maintenance time and cost of the vehicle, and improve the safety and comfort of the vehicle.

[0045] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0047] Figure 1 A schematic diagram of a process flow of a vehicle brake judder troubleshooting method provided in an embodiment of the present application;

[0048] Figure 2 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0049] Figure 3 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0050] Figure 4 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0051] Figure 5 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0052] Figure 6 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0053] Figure 7 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0054] Figure 8 Another schematic diagram of the process of the vehicle brake judder troubleshooting method provided in the embodiment of the present application;

[0055] Fig. 9 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0056] The present application is further described in detail. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used 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 / equipment and methods consistent with some aspects of the embodiments of the present application as detailed in the attached claims.

[0057] 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".

[0058] 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.

[0059] 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.

[0060] With the continuous development of the vehicle industry, brake judder has become a key issue affecting vehicle safety and comfort.

[0061] Brake judder usually occurs when the vehicle brakes, manifesting as the shaking of the steering wheel and the body of the vehicle, which not only affects the driving experience, but also affects driving safety. At present, the investigation of brake judder mainly relies on actual vehicle braking tests, and the fault is diagnosed by replacing components such as brake discs and brake pads. However, this method has many shortcomings, such as long implementation cycle, high cost, low efficiency, and difficulty in effectively predicting and troubleshooting problems in the early stages.

[0062] In related technologies, there are also some studies dedicated to reducing the occurrence of brake judder by improving the manufacturing process of brake discs and optimizing the material of brake pads, but most of these studies focus on hardware improvements and rarely touch on the optimization of the brake judder troubleshooting process itself.

[0063] In addition, although simulation analysis technology has also been used to study brake judder problems, existing simulation models are often not accurate enough when simulating complex working conditions during brake testing, resulting in limited accuracy in brake judder analysis.

[0064] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a vehicle brake judder troubleshooting method, a vehicle, and a storage medium, which can improve the troubleshooting efficiency and accuracy, reduce the vehicle maintenance time and cost, and improve the safety and comfort of the vehicle.

[0065] Further explanation is given below based on the accompanying drawings.

[0066] Reference Figure 1 According to the first aspect of the present application, the vehicle brake judder troubleshooting method may include:

[0067] Step S101, performing visual wear detection on the brake components of the target vehicle to obtain visual detection data;

[0068] Step S102, performing a rough inspection operation on the brake component based on the visual inspection data to obtain rough inspection data;

[0069] Step S103, in response to the rough screening data satisfying the preset rough screening condition, driving the target vehicle to perform a braking test;

[0070] Step S104, obtaining vibration sensing data and brake pressure data generated by the target vehicle during the brake test;

[0071] Step S105, performing vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data;

[0072] Step S106, performing brake pressure analysis on the brake pressure data to obtain brake pressure analysis data;

[0073] Step S107 , based on the vibration analysis data and the brake pressure analysis data, a precise inspection operation is performed on the brake components to obtain precise inspection data.

[0074] According to the embodiment shown in step S101 to step S107 of the present application, the vehicle brake jitter troubleshooting method of the present application needs to perform visual wear detection on the brake components of the target vehicle to obtain visual detection data; perform a rough inspection operation on the brake components based on the visual detection data to obtain rough inspection data; in response to the rough inspection data satisfying the preset rough screening conditions, drive the target vehicle to perform a brake test; obtain the vibration sensor data and brake pressure data generated by the target vehicle during the brake test; perform vehicle vibration analysis on the vibration sensor data to obtain vibration analysis data; perform brake pressure analysis on the brake pressure data to obtain brake pressure analysis data; perform a fine inspection operation on the brake components based on the vibration analysis data and the brake pressure analysis data to obtain fine inspection data. In this way, it is possible to improve the efficiency and accuracy of the inspection, reduce the maintenance time and cost of the vehicle, and improve the safety and comfort of the vehicle.

[0075] In step S101 of some embodiments, visual wear detection is performed on the brake components of the target vehicle. This step requires visual wear detection of the appearance of key components such as brake discs, brake pads, and brake calipers to identify any obvious wear, cracks, or other damage. Through this visual inspection, visual inspection data can be obtained to provide basic information for subsequent troubleshooting. At this stage, the embodiments of the present application can use an image acquisition device to capture images of key brake components such as brake discs, brake pads, and brake calipers from a close distance, and perform image recognition on the captured images to look for any visible signs of wear, cracks, deformation, or other damage.

[0076] The purpose of visual inspection is to collect data about the current state of brake components, which are called visual inspection data. Through image recognition, the embodiment of the present application can preliminarily evaluate the degree of wear of the components and determine whether there are obvious defects that need to be replaced or repaired. For example, if the thickness of the brake pad is lower than the minimum thickness marked by the manufacturer, or there is uneven wear or deep grooves on the surface of the brake disc, these will be recorded in the visual inspection data.

[0077] Additionally, visual inspections can include the identification of brake component color, temperature, and oil stains, as these factors can also indicate potential problems. For example, an unusual heat sensation or color change could mean the brake system is overheating, while oil stains could mean the brake system is contaminated by grease.

[0078] In step S102 of some embodiments, in this step, the embodiments of the present application will use the visual inspection data collected from the visual inspection to perform a preliminary rough inspection operation on the brake components of the vehicle. The purpose of the rough inspection is to screen out those brake components that may have problems through rapid evaluation, so as to determine whether more detailed inspection or repair is required.

[0079] Specifically, the embodiment of the present application will perform preliminary classification and evaluation of brake components based on visual inspection data, such as the degree of wear of the components, the depth of cracks, deformation, etc. For example, if the surface of the brake disc is obviously uneven or has deep grooves, or the thickness of the brake pad is lower than the minimum recommended by the manufacturer, these components will be marked as high risk and may require further testing or replacement.

[0080] During the rough inspection process, the embodiment of the present application can also determine other factors that may affect the braking performance through image recognition, such as the aging of the brake components, material degradation, and whether there are foreign objects embedded, etc. All of these factors may have a negative impact on the performance of the braking system, so in this step, the embodiment of the present application needs to comprehensively consider these factors to ensure that no potential problems are missed.

[0081] After the rough inspection is completed, the embodiment of the present application will obtain rough inspection data. These rough inspection data are a preliminary assessment of the current state of the brake components, and they will be used to determine whether a more in-depth brake test is required for the vehicle.

[0082] It should be understood that the rough inspection operation of step S102 is a rapid evaluation process based on visual inspection data, which helps the embodiment of the present application identify potential brake problems and provides direction for subsequent inspection and maintenance work. Through this step, the brake components that need further attention can be effectively screened out, thereby improving the efficiency and accuracy of the entire brake judder inspection method.

[0083] In some embodiments, if the rough screening data in step S103 meets the preset rough screening conditions, that is, there is a certain risk of brake judder or abnormal signs, the target vehicle will be driven to perform a brake test. In this step, a series of rough screening conditions are preset, which can be determined based on experience and performance standards of the brake system to evaluate whether the rough screening data indicates a potential brake problem.

[0084] According to some embodiments of the present application, when the rough inspection data reflects that there is an abnormality in the braking components, such as the degree of wear is close to or exceeds the safety threshold, or other problems that may affect the braking performance are detected, these rough inspection data meet the preset rough screening conditions. In this case, the embodiment of the present application will respond to this result and perform a braking test on the target vehicle. The purpose of the braking test is to further verify the findings of the rough inspection and collect more data on the braking performance of the vehicle. Among them, the braking test may include simulating braking scenarios in actual driving under controlled conditions, such as emergency braking, conventional braking, etc., to measure the vehicle's braking distance, braking pressure, braking stability and other key parameters. These braking tests can be performed at a professional testing site or using advanced braking testing equipment to ensure the accuracy and safety of the test.

[0085] In step S104 of some embodiments, vibration sensor data and brake pressure data generated by the target vehicle during the braking test are obtained. The vibration sensor data reflects the dynamic response of the vehicle during braking, while the brake pressure data is directly related to the performance of the braking system. It should be noted that step S104 needs to obtain the vibration sensor data and brake pressure data of the target vehicle during the braking test, the purpose of which is to deeply analyze the braking performance of the target vehicle and identify specific factors that may cause brake judder or other braking problems.

[0086] During a brake test, the vehicle is subjected to a series of braking maneuvers under controlled conditions, such as emergency braking, braking at different speeds, etc. At this point, various sensors are used to monitor and record multiple parameters during the braking process. Vibration sensors can be installed at key locations on the vehicle, such as the brake disc, suspension system, or body, to capture vibration sensing data generated during braking. These vibration sensing data reflect the dynamic response of the vehicle during braking, including information such as the frequency, amplitude, and duration of the vibration. In addition, brake pressure sensors are used to measure the pressure level in the brake system. These sensors monitor the pressure generated by the brake fluid in the line when the brake pedal is pressed, as well as the pressure applied by the brake caliper to the brake disc. Brake pressure data is critical to assessing whether the brake system is operating within a safe and effective pressure range.

[0087] It should be made clear that the collected vibration sensing data and brake pressure data will be used for subsequent detailed analysis. The vibration sensing data can reflect the frequency components and amplitude characteristics of the brake jitter, thereby analyzing the cause of the jitter, such as uneven wear of the brake disc or defects in the brake pad. The brake pressure data provides direct information about the performance of the brake system, such as whether the pressure is evenly distributed, whether it reaches the expected level, and whether there are leaks or other problems.

[0088] By integrating vibration sensor data and brake pressure data, the embodiment of the present application can more comprehensively quantify the performance of the braking system under actual working conditions during the troubleshooting process, thereby providing a basis for the diagnosis and troubleshooting of vehicle brake jitter.

[0089] In step S105 of some embodiments, during the vehicle vibration analysis, processing the vibration sensor data is a key step in obtaining vehicle status information. Since vibration sensors are usually installed in key parts of the vehicle, such as the engine, suspension system or body, to monitor and record vibration sensor data caused by vehicle operation or external environmental factors. Therefore, these vibration sensor data are crucial for evaluating the vehicle's operating status, predicting potential mechanical problems, and optimizing ride comfort.

[0090] After obtaining the vibration sensor data, the vibration sensor data can be preprocessed, which may include filtering, denoising and signal adjustment steps to improve data quality and reduce errors in subsequent analysis. The preprocessed data will more clearly reflect the actual vibration characteristics of the vehicle.

[0091] Furthermore, signal processing techniques, such as Fourier transform or wavelet transform, can be applied to convert the vibration signal in the time domain to the frequency domain to identify the frequency components in the vibration signal. This step is used to analyze the source of vibration, such as engine harmonics, vibration caused by tire imbalance, or resonance of the suspension system. Through these steps, vibration analysis data, that is, preliminary vehicle vibration characteristics analysis results, can be obtained. These results can include information such as the main vibration frequency, amplitude, vibration mode, etc. Vibration analysis data provides a basis for further vibration characteristics evaluation and fault diagnosis.

[0092] Reference Figure 2 According to some embodiments provided by the present application, step S105 performs vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data, which may include:

[0093] Step S201, performing frequency domain analysis on the vibration sensor data to obtain frequency component information corresponding to the vibration sensor data;

[0094] Step S202, performing time domain analysis on the vibration sensing data to determine the vibration intensity and vibration duration;

[0095] Step S203 , integrating the frequency component information, vibration intensity and vibration duration to obtain vibration analysis data.

[0096] In step S201 of some embodiments, it is necessary to perform frequency domain analysis on the vibration sensor data. Frequency domain analysis requires converting the vibration signal of the vibration sensor data in the time domain to the frequency domain through mathematical tools such as Fourier transform, so as to obtain the frequency component information corresponding to the vibration sensor data. Frequency domain analysis reveals all the frequency components and their amplitudes contained in the vibration signal, which is crucial for identifying the main vibration source in brake judder.

[0097] In step S202 of some embodiments, it is necessary to perform time domain analysis on the vibration sensing data. Unlike frequency domain analysis, time domain analysis focuses on the change of vibration signals over time. Through time domain analysis, the embodiments of the present application can determine the intensity of vibration, that is, the maximum amplitude of vibration, and the duration of vibration. Vibration intensity and duration are important parameters for evaluating the impact of vibration on vehicle comfort and safety.

[0098] In step S203 of some embodiments, the frequency component information, vibration intensity and vibration duration are integrated. This integration process is a comprehensive evaluation of the frequency domain and time domain analysis results, with the goal of obtaining comprehensive vibration analysis data. The vibration analysis data includes not only the frequency characteristics of the vibration, but also the time domain characteristics of the vibration.

[0099] Through the vibration analysis process shown in step S201 to step S203 of the embodiment of the present application, the specific frequency components that cause brake judder can be determined, and the intensity and duration of these vibration components and their impact on vehicle performance can be evaluated. These data are crucial for subsequent diagnosis and maintenance decisions, helping to accurately locate the source of the problem and develop effective solutions to improve the vehicle's braking performance and ride comfort.

[0100] Reference Figure 3 According to some embodiments provided by the present application, step S202 performs time domain analysis on vibration sensing data to determine vibration intensity and vibration duration, which may include:

[0101] Step S301, performing time domain analysis on the vibration sensor data to determine the vibration peak value, vibration average value and vibration duration corresponding to the vibration sensor data;

[0102] Step S302: determining the vibration intensity based on the vibration peak value and the vibration average value.

[0103] In step S301 of some embodiments, the vibration sensing data is first analyzed in the time domain. Time domain analysis directly observes the changes of the vibration signal over time. Through this method, the embodiments of the present application can capture the important features of the vibration signal. Specifically, this step includes determining the vibration peak value, that is, the maximum amplitude of the vibration signal over a period of time; the vibration average value, which is usually the average of the vibration amplitude within a specific time window; and the vibration duration, that is, the total time that the vibration occurs and can be detected. These parameters provide a quantitative description of the basic characteristics of the vibration signal.

[0104] In step S302 of some embodiments, the vibration intensity is determined based on the vibration peak value and the vibration average value. The vibration intensity is an indicator that describes the energy of the vibration signal, and is usually directly related to the vibration peak value. The higher the vibration peak value, the greater the energy of the vibration, which may have a greater impact on the comfort and structural integrity of the vehicle. At the same time, the vibration average value provides the average energy level of the vibration signal within a cycle, which helps to evaluate the continuous impact of the vibration.

[0105] By analyzing the vibration peak and average value, the embodiment of the present application can evaluate the overall intensity of the vibration, and evaluate the cumulative effect that the vibration may have on the vehicle in combination with the duration of the vibration. For example, even if the average intensity of the vibration is not very high, if the vibration lasts too long, it may cause fatigue damage to the vehicle structure.

[0106] In addition, the results of time domain analysis can also be combined with other analysis methods, such as frequency domain analysis, to provide a more comprehensive description of vibration characteristics. For example, if the time domain analysis shows that the vibration intensity is high, and the frequency domain analysis reveals the main frequency components, the embodiment of the present application can more accurately diagnose the source of the vibration, such as uneven wear of the brake disc or defects in the suspension system.

[0107] It should be clear that the time domain analysis shown in step S301 to step S302 of the embodiment of the present application is an important part of the in-depth analysis of the vibration signal, which provides key quantitative indicators of vibration characteristics and provides important information for vibration diagnosis and control. Through these analyses, the embodiment of the present application can better understand the dynamic behavior of brake judder and take appropriate measures to reduce or eliminate vibration problems.

[0108] In some embodiments, step S106 , brake pressure analysis, requires in-depth analysis of data collected from brake system sensors.

[0109] First, the collected raw brake pressure data may need to be preprocessed to remove possible noise and errors. The preprocessing step may include filtering, signal smoothing or calibration to ensure the accuracy and reliability of the data. This process helps to clearly present the true situation of brake pressure changes over time.

[0110] Furthermore, the pre-processed data is analyzed in detail. The analysis content may include the peak value, build-up speed, stability of the brake pressure, and the change trend under different braking conditions. Through these steps, the brake pressure analysis data can be obtained, that is, in-depth information about the performance of the brake system.

[0111] In some more specific embodiments, the brake pressure analysis data may include, but is not limited to, the following types of information:

[0112] Braking effect evaluation information is used to analyze whether the braking pressure can quickly reach safety standards and whether the braking effect meets expectations.

[0113] System response time, which measures the time from when the brake pedal is depressed to when brake pressure builds.

[0114] Pressure distribution uniformity is used to evaluate whether the brake pressure between different wheels is balanced to avoid braking imbalance.

[0115] Long-term performance monitoring information to assess brake system performance changes and wear over time by continuously monitoring brake pressure.

[0116] In addition, brake pressure analysis data can also be used to diagnose possible problems in the target vehicle's brake system, such as leaks, blockages, or component wear.

[0117] Reference Figure 4 According to some embodiments provided by the present application, step S106 performs brake pressure analysis on the brake pressure data to obtain brake pressure analysis data, which may include:

[0118] Step S401, performing brake pressure analysis on the brake pressure data to obtain the brake pressure magnitude, pressure response speed and pressure duration of the target vehicle during the brake test;

[0119] Step S402: Integrate the brake pressure magnitude, pressure response speed and pressure duration to obtain brake pressure analysis data.

[0120] In step S401 of some embodiments, the brake pressure data is first analyzed for brake pressure. This process involves a detailed analysis of the brake pressure data generated by the target vehicle during the brake test. Through this analysis, the embodiments of the present application can obtain key information about the performance of the brake system, including the magnitude of the brake pressure, the pressure response speed, and the duration of the pressure. The magnitude of the brake pressure directly reflects the braking force applied by the brake system to the wheels, and is a key factor affecting the vehicle's deceleration ability. The pressure response speed refers to the time required for the brake system to receive the brake signal and for the pressure to reach a peak value, which is related to the speed of the brake reaction. The duration of the pressure describes the stability of the brake pressure over a certain period of time, which is related to the consistency and reliability of the braking process.

[0121] In step S402 of some embodiments, the parameters such as brake pressure, pressure response speed and pressure duration are integrated to obtain comprehensive brake pressure analysis data. This integration process is a comprehensive evaluation of the performance of the brake system, which not only considers the absolute value of the brake pressure, but also considers the change characteristics of the brake pressure over time. Through this comprehensive analysis, the embodiments of the present application can more accurately determine whether there are problems with the brake system, such as insufficient pressure, delayed response or short duration, which may affect the braking performance of the vehicle.

[0122] It should be noted that steps S401 to S402 provide a quantitative evaluation method for the embodiment of the present application, which helps diagnose possible problems in the braking system of the target vehicle and guides subsequent maintenance or adjustment work. For example, if the brake pressure is found to be insufficient, it may be necessary to check the brake fluid level, brake booster or brake line for leaks. If the pressure response speed is slow, it may be necessary to check the working status of the brake booster or the hydraulic components of the brake system. Through these detailed brake pressure data, the embodiment of the present application can locate the problem more accurately and take corresponding measures to improve the braking performance and safety of the vehicle.

[0123] In step S107 of some embodiments, a fine inspection operation is performed on the brake components based on the vibration analysis data and the brake pressure analysis data. This step is a deepening of the rough inspection. By integrating the vibration and pressure data, the problem can be more accurately identified, such as uneven wear of the brake disc, material problems of the brake pad, or other potential defects of the brake system. The fine inspection data obtained by the fine inspection operation provides a detailed basis for the final maintenance or adjustment, ensuring the accuracy and effectiveness of the inspection work.

[0124] First, vibration analysis data provides detailed information about the vibration characteristics of the vehicle, including vibration frequency, amplitude, and mode. This information is crucial to understanding the dynamic behavior of the vehicle during operation, especially the vibration phenomenon that may occur during braking. Brake pressure analysis data provides performance indicators of the braking system, including the speed, stability, and distribution of brake pressure. This data helps to evaluate whether the braking system can provide uniform and effective braking force, and whether there are factors that may affect braking stability.

[0125] Based on this, combined with these two types of data, the precise inspection operation of the embodiment of the present application can focus on brake components, such as brake discs, brake calipers, brake pads, etc., and their performance during the braking process. The precise inspection operation can include the following aspects:

[0126] The correlation analysis between vibration and braking performance is used to analyze whether the characteristic frequency in the vibration data matches the abnormal vibration during braking to determine whether it is caused by the braking components.

[0127] The brake pressure distribution uniformity check is used to evaluate the distribution of brake pressure on different brake components and to find out whether there is brake judder caused by uneven pressure.

[0128] Component wear and damage detection uses vibration and brake pressure data to identify signs of component wear or damage, such as uneven wear of brake discs or excessive wear of brake pads.

[0129] Dynamic response testing is used to simulate different braking situations, such as emergency braking or braking at different speeds, to observe the response of the braking components and the overall performance of the system.

[0130] Failure mode analysis is used to analyze possible failure modes based on the collected data, such as the sticking of the brake caliper, thermal deformation of the brake disc, etc.

[0131] Through these aspects of the detailed troubleshooting operation, you can get detailed troubleshooting data, which details the condition and potential problems of the brake components. Therefore, detailed troubleshooting data is essential for formulating maintenance strategies, improving designs and optimizing brake performance.

[0132] Reference Figure 5 According to some embodiments provided by the present application, the fine inspection data includes vibration inspection data and pressure inspection data. Step S107 performs a fine inspection operation on the brake components based on the vibration analysis data and the brake pressure analysis data to obtain the fine inspection data, which may include:

[0133] Step S501, determining the frequency component information, vibration intensity and vibration duration of the target vehicle during the braking test based on the vibration analysis data;

[0134] Step S502, based on the brake pressure analysis data, determining the brake pressure magnitude, pressure response speed and pressure duration of the target vehicle during the brake test;

[0135] Step S503, performing a vibration inspection based on the frequency component information, vibration intensity and vibration duration to obtain vibration inspection data;

[0136] Step S504, performing a precise pressure check on the brake pressure, pressure response speed and pressure duration to obtain pressure check data.

[0137] In step S501 of some embodiments, the vibration analysis data is first used to determine the frequency component information, vibration intensity and vibration duration of the target vehicle during the braking test. This information is obtained through the frequency domain and time domain analysis in the previous steps, and they provide an in-depth understanding of the vibration characteristics of the vehicle. The frequency component of the vibration can help identify the main vibration source causing the brake tremor, while the vibration intensity and duration can assess the severity and potential impact of the vibration.

[0138] In step S502 of some embodiments, the brake pressure analysis data is used to determine the brake pressure, pressure response speed and pressure duration of the target vehicle during the brake test. The brake pressure analysis data reflects the performance of the brake system, including the ability of the brake system to generate braking force, the speed of the brake response and the stability of the brake pressure.

[0139] In step S503 of some embodiments, a vibration fine-tuning is performed based on the obtained frequency component information, vibration intensity and vibration duration. This process involves further analysis of the vibration analysis data to identify possible sources of vibration problems, such as uneven wear of the brake disc or imbalance of the brake system. Through this fine-tuning, vibration troubleshooting data can be obtained, which details the specific characteristics and possible causes of the vibration problem.

[0140] Reference Figure 6 According to some embodiments provided by the present application, the vibration investigation data includes vibration source investigation data, vibration intensity investigation data and vibration stability investigation data. Step S503 performs vibration investigation on the frequency component information, vibration intensity and vibration duration to obtain vibration investigation data, which may include:

[0141] Step S601, performing vibration source screening on the frequency component information based on the natural vibration frequency of the target vehicle to obtain vibration source screening data;

[0142] Step S602, performing a vibration intensity check on the vibration intensity based on a preset intensity threshold to obtain vibration intensity check data;

[0143] Step S603, performing a vibration stability check on the vibration duration based on a preset time threshold to obtain vibration stability check data.

[0144] Reference Figure 7 According to some embodiments provided by the present application, before step S601 performs vibration source screening on the frequency component information based on the natural vibration frequency of the target vehicle, the method further includes:

[0145] Step S701, obtaining the vehicle mass and vehicle spring strength corresponding to the target vehicle during the braking test;

[0146] Step S702, determining the natural vibration frequency corresponding to the target vehicle based on the vehicle mass and the vehicle spring strength.

[0147] In certain embodiments of the present application, steps S701 and S702 are added before step S601 of vibration source screening. These two steps are intended to more accurately determine the natural vibration frequency of the target vehicle, thereby providing necessary basic data for vibration source screening.

[0148] In step S701 of some embodiments, it is necessary to obtain the vehicle mass and vehicle spring strength corresponding to the target vehicle during the braking test. The vehicle mass refers to the weight of the vehicle itself, which has a direct impact on the vibration characteristics of the vehicle. The vehicle spring strength refers to the stiffness of the spring in the suspension system, which determines the vehicle's ability to respond to road unevenness. These two parameters are key factors in determining the natural vibration frequency of the vehicle.

[0149] In step S702 of some embodiments, the natural vibration frequency corresponding to the target vehicle is determined based on the obtained vehicle mass and vehicle spring strength. The natural vibration frequency refers to the frequency at which the vehicle suspension system naturally tends to vibrate without external excitation. This frequency can be calculated by a physical formula, which is usually expressed as:

[0150]

[0151] Wherein, f is the vibration frequency, k is the spring stiffness, and m is the mass. In the embodiment of the present application, the natural vibration frequency of the target vehicle can be calculated by substituting the mass and spring strength of the actual target vehicle into the formula.

[0152] Through the embodiment of the present application shown in step S701 and step S702, the embodiment of the present application can obtain the natural vibration frequency of the target vehicle, which provides an important reference for the vibration source investigation in step S601. In step S601, the calculated natural vibration frequency is compared with the frequency component information recorded in the braking test to investigate the vibration source. If the vibration frequency of the frequency component information is close to or consistent with the natural vibration frequency, this may indicate that the vibration of the target vehicle is caused by the dynamic characteristics of the vehicle itself. Conversely, if the frequency component does not match the natural vibration frequency, it may indicate that the vibration is caused by other external factors, such as uneven wear of the brake disc or other problems with the braking system. This troubleshooting method based on the natural vibration frequency of the vehicle helps the embodiment of the present application to more accurately identify and locate the source of brake jitter, so as to take targeted measures to solve the problem and improve the braking performance and ride comfort of the vehicle.

[0153] In step S601 of some embodiments, the frequency component information is subjected to vibration source troubleshooting based on the natural vibration frequency of the target vehicle. This process analyzes the frequency component information based on the natural vibration frequency of the target vehicle. The natural vibration frequency, also known as the natural frequency, is the frequency at which a vehicle naturally tends to vibrate without external excitation. By comparing the frequency components obtained in the test with the natural vibration frequency of the target vehicle, the embodiments of the present application can identify which frequency components match the natural vibration characteristics of the vehicle, thereby obtaining vibration source troubleshooting data. The vibration source troubleshooting data is used to reflect whether the brake judder is caused by a specific component or system characteristic of the target vehicle.

[0154] In step S602 of some embodiments, a vibration intensity check is performed on the vibration intensity based on a preset intensity threshold. This step evaluates the intensity of the vibration based on the preset intensity threshold. The vibration intensity check involves comparing the measured vibration intensity with the preset safety or performance threshold. If the vibration intensity exceeds these thresholds, it means that there is a vibration problem that needs attention. Through this check, vibration intensity check data can be obtained, which directly indicates the severity of the vibration and the possible impact on the vehicle performance.

[0155] In step S603 of some embodiments, a vibration stability check is performed on the duration of the vibration based on a preset time threshold. This process evaluates the duration of the vibration based on a preset time threshold. The vibration stability check focuses on whether the vibration continues to occur over a period of time and whether such continuous vibration may cause cumulative damage to the vehicle structure. By setting a time threshold, the embodiments of the present application can identify those abnormal and continuous vibration events and obtain vibration stability check data. These vibration stability check data are helpful in evaluating the impact of vibration on the long-term performance and safety of the vehicle.

[0156] In the embodiment of the present application shown by steps S601 to S603, the vibration troubleshooting data provides a comprehensive vibration characteristic evaluation for the vibration sensing signal, including the source, intensity and stability of the vibration. These data provide the embodiment of the present application with the detailed information required to identify and solve the brake judder problem, which helps to take targeted measures in subsequent links, such as adjusting or replacing parts, modifying suspension system settings or performing other maintenance work to improve the braking performance and ride comfort of the vehicle.

[0157] In step S504 of some embodiments, a precise pressure check is performed on the brake pressure, pressure response speed, and pressure duration. This step is a detailed evaluation of the brake system performance, with the goal of identifying brake pressure-related problems, such as insufficient pressure, delayed response, or unstable pressure. Through this precise check, pressure check data can be obtained, which reveals specific problems with the brake system performance and areas that need improvement.

[0158] Reference Figure 8 According to some embodiments provided by the present application, the pressure check data includes pressure size check data, pressure response check data and pressure stability check data. Step S504 performs pressure precision check on the brake pressure size, pressure response speed and pressure duration to obtain pressure check data, which may include:

[0159] Step S801, checking the pressure level based on a preset pressure threshold to obtain pressure level checking data;

[0160] Step S802, performing pressure response checking on the pressure response speed based on a preset brake response time threshold to obtain pressure response checking data;

[0161] Step S803, performing a pressure stability check on the pressure duration based on a preset pressure time threshold to obtain pressure stability check data.

[0162] In step S801 of some embodiments, the pressure level is checked based on a preset pressure threshold. This step involves comparing the actually measured brake pressure with the preset pressure threshold. The preset pressure threshold is determined based on the design standards and safety requirements of the brake system to ensure that the brake pressure is between the specified minimum and maximum values. By comparing the actual pressure and the threshold, pressure level check data can be obtained, which directly indicates whether the brake pressure is within a safe and effective range, and whether there is a problem of too high or too low pressure.

[0163] In step S802 of some embodiments, a pressure response check is performed on the pressure response speed based on a preset brake response time threshold. This step focuses on the response speed of the braking system to the braking command, that is, the time required from the driver stepping on the brake pedal to the braking system generating the corresponding pressure. By comparing the actual pressure response speed with the preset brake response time threshold, the pressure response check data can be obtained. These pressure response check data reveal the responsiveness of the braking system and help the embodiments of the present application to evaluate whether the braking system can provide the required braking force in a timely manner.

[0164] In step S803 of some embodiments, a pressure stability check is performed on the pressure duration based on a preset pressure-time threshold. This step evaluates the stability of the brake pressure over a period of time, that is, whether the brake pressure can be continuously maintained within a preset threshold range. By comparing the actual pressure duration with the preset pressure-time threshold, pressure stability check data can be obtained. These pressure stability check data are crucial for identifying possible persistent problems in the brake system, such as fluctuations or attenuation of the brake pressure.

[0165] The embodiment of the present application shown by steps S801 to S803 provides a comprehensive brake system pressure performance evaluation. These data not only reveal the magnitude, response speed and stability of the brake pressure, but also help identify possible problem areas so that corresponding maintenance or adjustment measures can be taken. Through this refined pressure investigation, it can be ensured that the performance of the brake system meets the expected safety and efficiency standards, and improve the overall braking performance of the vehicle.

[0166] In the embodiment of the present application shown by steps S501 to S504, the refined troubleshooting data includes vibration troubleshooting data and pressure troubleshooting data, which provide a comprehensive analysis result for the embodiment of the present application, which helps to accurately diagnose problems in the brake system and formulate corresponding maintenance or adjustment strategies. This refined troubleshooting process ensures that problems can be discovered and resolved early, thereby improving the braking performance and safety of the vehicle.

[0167] The vehicle brake jitter troubleshooting method of the embodiment of the present application ensures a comprehensive diagnosis of the vehicle brake jitter problem through a gradual and in-depth analysis from macro to micro and from rough to precise, thereby improving the efficiency and accuracy of the troubleshooting.

[0168] In other embodiments of the present application, corresponding vehicle maintenance measures can also be taken based on the precise inspection data, such as replacing worn parts, adjusting the brake pressure distribution, repairing or replacing damaged brake components, etc., to ensure the stability and safety of the braking system.

[0169] The vehicle provided according to the embodiment of the present application may include:

[0170] The vehicle stores a program, and the program is executed to implement any one of the vehicle brake jitter troubleshooting methods provided in the embodiments of the present application.

[0171] It can be seen that the contents in the above-mentioned vehicle brake jitter troubleshooting method embodiment are all applicable to the embodiment of this vehicle, the functions specifically implemented by the present vehicle embodiment are the same as those in the above-mentioned vehicle brake jitter troubleshooting method embodiment, and the beneficial effects achieved are also the same as the beneficial effects achieved by the above-mentioned vehicle brake jitter troubleshooting method embodiment.

[0172] The computer-readable storage medium provided according to the embodiment of the present application may include:

[0173] The computer-readable storage medium stores a program, and the program is executed to implement any one of the vehicle brake jitter troubleshooting methods provided in the embodiments of the present application.

[0174] It can be seen that the contents in the above-mentioned vehicle brake jitter troubleshooting method embodiment are all applicable to the embodiment of this computer-readable storage medium, the functions specifically implemented by the present computer-readable storage medium embodiment are the same as those in the above-mentioned vehicle brake jitter troubleshooting method embodiment, and the beneficial effects achieved are also the same as the beneficial effects achieved by the above-mentioned vehicle brake jitter troubleshooting method embodiment.

[0175] Reference Fig. 9 , Fig. 9 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes:

[0176] The processor 901 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0177] The memory 902 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 902, and the processor 901 calls and executes the vehicle brake judder troubleshooting method of the embodiment of this application;

[0178] Input / output interface 903, used to implement information input and output;

[0179] Communication interface 904, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WI FI, Bluetooth, etc.);

[0180] A bus 905 that transmits information between various components of the device (e.g., the processor 901, the memory 902, the input / output interface 903, and the communication interface 904);

[0181] The processor 901 , the memory 902 , the input / output interface 903 and the communication interface 904 are connected to each other in communication within the device via a bus 905 .

[0182] The third aspect of the present application also provides a vehicle, the vehicle including any of the above vehicle brake judder troubleshooting methods. Specifically, 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.

[0183] Specifically, the vehicle provided in the embodiment of the present application 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.

[0184] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program implements the above method when executed by a processor.

[0185] It can be understood that the contents of the above method embodiments are all applicable to the present storage medium embodiments, the functions specifically implemented by the present storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0186] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0187] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0188] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0189] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0190] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

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

[0192] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, which may include any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0193] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0194] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0195] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0196] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and may include multiple instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store programs.

[0197] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention 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 invention should be within the scope of the rights of the present invention.

Claims

1. A method for troubleshooting vehicle brake judder, characterized in that: include: Perform visual wear inspection on the brake components of the target vehicle to obtain visual inspection data; Performing a rough inspection operation on the brake component based on the visual inspection data to obtain rough inspection data; In response to the rough screening data satisfying a preset rough screening condition, driving the target vehicle to perform a brake test; Acquiring vibration sensing data and brake pressure data generated by the target vehicle during a brake test; Performing vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data; performing brake pressure analysis on the brake pressure data to obtain brake pressure analysis data; Based on the vibration analysis data and the brake pressure analysis data, a fine inspection operation is performed on the brake component to obtain fine inspection data.

2. The method according to claim 1, characterized in that The performing vehicle vibration analysis on the vibration sensing data to obtain vibration analysis data includes: Performing frequency domain analysis on the vibration sensor data to obtain frequency component information corresponding to the vibration sensor data; Performing time domain analysis on the vibration sensing data to determine the vibration intensity and vibration duration; The frequency component information, the vibration intensity and the vibration duration are integrated to obtain the vibration analysis data.

3. The method according to claim 2, characterized in that The performing time domain analysis on the vibration sensing data to determine the vibration intensity and the vibration duration includes: Performing time domain analysis on the vibration sensor data to determine the vibration peak value, vibration average value and vibration duration corresponding to the vibration sensor data; The vibration intensity is determined based on the vibration peak value and the vibration average value.

4. The method according to claim 2, characterized in that: The performing brake pressure analysis on the brake pressure data to obtain brake pressure analysis data includes: Performing brake pressure analysis on the brake pressure data to obtain the brake pressure magnitude, pressure response speed and pressure duration of the target vehicle during the brake test; The brake pressure magnitude, the pressure response speed and the pressure duration are integrated to obtain the brake pressure analysis data.

5. The method according to claim 1, characterized in that The fine inspection data includes vibration inspection data and pressure inspection data. Based on the vibration analysis data and the brake pressure analysis data, a fine inspection operation is performed on the brake component to obtain the fine inspection data, including: Based on the vibration analysis data, determining the frequency component information, vibration intensity and vibration duration of the target vehicle during the braking test; Based on the brake pressure analysis data, determine the brake pressure magnitude, pressure response speed and pressure duration of the target vehicle during the brake test; Performing a vibration inspection on the frequency component information, the vibration intensity and the vibration duration to obtain the vibration inspection data; A precise pressure check is performed on the brake pressure size, the pressure response speed and the pressure duration to obtain the pressure check data.

6. The method according to claim 5, characterized in that The vibration investigation data includes vibration source investigation data, vibration intensity investigation data and vibration stability investigation data. The vibration investigation data is obtained by performing vibration investigation on the frequency component information, the vibration intensity and the vibration duration, including: Performing vibration source screening on the frequency component information based on the natural vibration frequency of the target vehicle to obtain the vibration source screening data; Performing a vibration intensity check on the vibration intensity based on a preset intensity threshold to obtain the vibration intensity check data; The vibration stability check is performed on the vibration duration based on a preset time threshold to obtain the vibration stability check data.

7. The method according to claim 6, characterized in that Before checking the vibration source of the frequency component information based on the natural vibration frequency of the target vehicle, the method further includes: Obtaining the vehicle mass and vehicle spring strength corresponding to the target vehicle during the braking test; Based on the vehicle mass and the vehicle spring strength, a natural vibration frequency corresponding to the target vehicle is determined.

8. The method according to claim 5, characterized in that The pressure check data includes pressure size check data, pressure response check data and pressure stability check data. The pressure check is performed on the brake pressure size, the pressure response speed and the pressure duration to obtain the pressure check data, including: Checking the pressure magnitude based on a preset pressure threshold to obtain pressure magnitude checking data; Performing a pressure response check on the pressure response speed based on a preset brake response time threshold to obtain the pressure response check data; The pressure stability is checked on the pressure duration based on a preset pressure time threshold to obtain the pressure stability check data.

9. A vehicle, characterized in that: include: A memory and a processor, wherein the memory stores a computer program, and the processor implements the vehicle brake jitter troubleshooting method as described in any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The storage medium stores a program, and the program is executed by a processor to implement the vehicle brake judder troubleshooting method as described in any one of claims 1 to 8.