Fault code reporting optimization method and device, equipment and storage medium

Abstract

The present application belongs to the field of vehicle fault codes, and discloses a fault code reporting optimization method, device, equipment and storage medium. The method comprises: when the driving data of the vehicle meets the preset fault diagnosis condition, obtaining the fault diagnosis information corresponding to the preset fault diagnosis condition; determining the fault code with fault risk according to the fault diagnosis information and the driving data; and performing fault code reporting optimization on the vehicle according to the fault code to reduce the reporting risk of the fault code. Since the present application obtains the fault diagnosis information corresponding to the preset fault diagnosis condition when the driving data of the vehicle meets the preset fault diagnosis condition, determines the fault code with fault risk according to the fault diagnosis information and the driving data, and performs fault code reporting optimization on the vehicle according to the fault code, compared with the existing fault code reporting logic, the above-mentioned method can reduce the reporting frequency and risk of the fault code, reduce the vehicle maintenance frequency, and improve the user experience.

Description

Technical Field

[0001] This invention relates to the field of vehicle fault code technology, and in particular to a fault code reporting optimization method, apparatus, device, and storage medium. Background Technology

[0002] The batch issues related to On-Board Diagnostics (OBD) fault codes in vehicles stem from both component problems and calibration data issues. Currently, false fault codes are frequently reported due to unreasonable diagnostic thresholds or logic in the controller. Since a vehicle's electronic control system can generate hundreds of fault codes, it's difficult to analyze each one individually. These types of faults often appear early in the vehicle's lifespan, and troubleshooting is challenging. After-sales service often resorts to replacing parts, but repeated component replacements rarely resolve the problem effectively. Furthermore, the early stage of the fault and the lack of a clear solution after repairs easily lead to customer complaints.

[0003] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main objective of this invention is to provide a fault code reporting optimization method, apparatus, device, and storage medium, aiming to solve the technical problem of false fault code reporting caused by unreasonable fault diagnosis reporting thresholds or unreasonable control logic in the prior art, resulting in a high number of user repairs.

[0005] To achieve the above objectives, the present invention provides a fault code reporting optimization method, the method comprising the following steps:

[0006] When the vehicle's driving data meets the preset fault diagnosis conditions, obtain the fault diagnosis information corresponding to the preset fault diagnosis conditions.

[0007] Based on the fault diagnosis information and the driving data, fault codes indicating potential fault risks are determined;

[0008] Based on the fault codes, the vehicle's fault code reporting is optimized to reduce the risk of fault code reporting.

[0009] Optionally, the step of determining fault codes with potential fault risks based on the fault diagnosis information and the driving data includes:

[0010] The fault to be verified is determined based on the fault diagnosis information.

[0011] When the fault to be verified has a fault setting time, the measured value corresponding to the fault to be verified is determined based on the driving data;

[0012] When the measured value is greater than the fault threshold corresponding to the fault to be verified, the timer is started.

[0013] Based on the timing results and the aforementioned fault diagnosis information, fault codes indicating potential fault risks are identified.

[0014] Optionally, the step of determining fault codes with potential fault risk based on timing results and fault diagnosis information includes:

[0015] The fault setting time of the fault to be verified is determined based on the fault diagnosis information.

[0016] Determine the target setting time based on the fault setting time;

[0017] If the timing result is greater than the target setting time, it is determined that the fault to be verified has a fault risk, and the fault code of the fault to be verified is determined.

[0018] Optionally, after the step of determining the fault to be verified based on the fault diagnosis information, the method further includes:

[0019] When the fault to be verified does not have a fault setting time, the measured value corresponding to the fault to be verified is determined based on the driving data;

[0020] Based on the fault diagnosis information, determine the fault threshold and target value corresponding to the fault to be verified;

[0021] Based on the measured value, the fault threshold, and the target value, determine whether the fault to be verified has a fault risk;

[0022] When the fault to be verified has a risk of failure, the fault code corresponding to the fault to be verified is determined.

[0023] Optionally, the step of optimizing the vehicle's fault code reporting based on the fault code includes:

[0024] Obtain the test results of the vehicle test performed in response to the fault code;

[0025] Determine the ideal fault threshold corresponding to the fault code based on the test results;

[0026] The ideal fault threshold is used as the fault threshold corresponding to the fault code.

[0027] Optionally, the step of optimizing the vehicle's fault code reporting based on the fault code includes:

[0028] Identify the target influencing factors corresponding to the fault code;

[0029] Adjust the vehicle's control parameters according to the target influencing factors to reduce the measured value corresponding to the fault code.

[0030] Optionally, the step of obtaining fault diagnosis information corresponding to the preset fault diagnosis conditions when the vehicle's driving data meets the preset fault diagnosis conditions includes:

[0031] Acquire vehicle driving data during the testing process;

[0032] Obtain preset fault diagnosis conditions, wherein the preset fault diagnosis conditions include at least one fault diagnosis sub-condition;

[0033] When the driving data meets the preset fault diagnosis conditions, obtain the fault diagnosis information corresponding to the fault diagnosis sub-conditions met by the driving data.

[0034] Furthermore, to achieve the above objectives, the present invention also provides a fault code reporting optimization device, the device comprising:

[0035] The fault diagnosis information acquisition module is used to acquire fault diagnosis information corresponding to the preset fault diagnosis conditions when the vehicle's driving data meets the preset fault diagnosis conditions.

[0036] The fault code determination module is used to determine fault codes that pose a risk of failure based on the fault diagnosis information and the driving data.

[0037] An optimization module is used to optimize the fault code reporting of the vehicle based on the fault code, so as to reduce the reporting risk of the fault code.

[0038] Furthermore, to achieve the above objectives, the present invention also proposes a fault code reporting optimization device, the device comprising: a memory, a processor, and a fault code reporting optimization program stored in the memory and executable on the processor, the fault code reporting optimization program being configured to implement the steps of the fault code reporting optimization method described above.

[0039] Furthermore, to achieve the above objectives, the present invention also proposes a storage medium storing a fault code reporting optimization program, wherein when the fault code reporting optimization program is executed by a processor, it implements the steps of the fault code reporting optimization method described above.

[0040] This invention acquires fault diagnosis information corresponding to preset fault diagnosis conditions when vehicle driving data meets those conditions; determines fault codes with potential fault risks based on the fault diagnosis information and driving data; and optimizes fault code reporting for the vehicle based on these fault codes to reduce the reporting risk. Because this invention acquires fault diagnosis information corresponding to preset fault diagnosis conditions when vehicle driving data meets those conditions; determines fault codes with potential fault risks based on the fault diagnosis information and driving data; and optimizes fault code reporting for the vehicle based on these fault codes, compared to existing fault code reporting logic, this invention reduces the number of fault code reports and associated risks, decreases vehicle repair frequency, and improves user experience. Attached Figure Description

[0041] Figure 1 This is a schematic diagram of the structure of the fault code reporting optimization device for the hardware operating environment involved in the embodiments of the present invention;

[0042] Figure 2 This is a flowchart illustrating the first embodiment of the fault code reporting optimization method of the present invention;

[0043] Figure 3 This is a flowchart illustrating the second embodiment of the fault code reporting optimization method of the present invention;

[0044] Figure 4 This is a flowchart illustrating the third embodiment of the fault code reporting optimization method of the present invention;

[0045] Figure 5 This is a structural block diagram of the first embodiment of the fault code reporting optimization device of the present invention.

[0046] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0047] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0048] Reference Figure 1 , Figure 1 This is a schematic diagram of the fault code reporting device structure for the hardware operating environment involved in the embodiments of the present invention.

[0049] like Figure 1As shown, the fault code optimization device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be high-speed random access memory (RAM) or stable non-volatile memory (NVM), such as a disk storage device. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.

[0050] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the fault code optimization device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0051] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a fault code reporting optimization program.

[0052] exist Figure 1 In the fault code reporting optimization device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and memory 1005 in the fault code reporting optimization device of the present invention can be set in the fault code reporting optimization device, and the fault code reporting optimization device calls the fault code reporting optimization program stored in the memory 1005 through the processor 1001 and executes the fault code reporting optimization method provided in the embodiment of the present invention.

[0053] Based on the aforementioned fault code optimization device, this embodiment of the invention provides a fault code optimization method, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the fault code reporting optimization method of the present invention.

[0054] In this embodiment, the fault code reporting optimization method includes the following steps:

[0055] Step S10: When the vehicle's driving data meets the preset fault diagnosis conditions, obtain the fault diagnosis information corresponding to the preset fault diagnosis conditions.

[0056] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a mobile phone, tablet computer, personal computer, or vehicle computer, or an electronic device or fault code reporting optimization device capable of performing the above functions. The following description uses the fault code reporting optimization device as an example to illustrate this embodiment and the subsequent embodiments.

[0057] It should be noted that the driving data can be the vehicle's driving data during vehicle testing when optimizing fault code reporting. This data may include whether the vehicle is powered on, fuel injection volume during driving, accelerator pedal and brake pedal opening, vehicle speed, and other identifying information. The preset fault diagnosis conditions can be pre-set conditions that must be met when diagnosing fault codes. These conditions include multiple sub-conditions, each corresponding to a different fault code diagnosis condition. For example, if the preset fault diagnosis condition includes vehicle power-on, then based on the driving data indicating vehicle power-on, fault code reporting optimization can be performed on fault codes P010800, P010700, P023700, and P023800 corresponding to vehicle power-on. Another preset fault diagnosis condition is a vehicle speed greater than 30 km / h; therefore, based on the driving data indicating vehicle speed greater than 30 km / h, fault code reporting optimization can be performed on fault code P046700 corresponding to vehicle power-on. The fault diagnosis information corresponding to the preset fault diagnosis conditions may be the fault diagnosis information corresponding to the sub-conditions in the preset fault diagnosis conditions satisfied by the driving data. The fault diagnosis information may include the fault code corresponding to the sub-condition and the threshold for reporting the fault code.

[0058] Furthermore, in order to accurately identify fault codes that pose a risk of false alarms and then optimize them, step S10 may include: acquiring vehicle driving data during the test; acquiring preset fault diagnosis conditions, the preset fault diagnosis conditions including at least one fault diagnosis sub-condition; and when the driving data meets the preset fault diagnosis conditions, acquiring fault diagnosis information corresponding to the fault diagnosis sub-conditions met by the driving data.

[0059] It should be understood that each fault diagnosis sub-condition corresponds to a fault diagnosis information, which includes the fault code, the corresponding fault diagnosis threshold, and information such as whether a settling time is required. Only when the driving information meets the fault diagnosis sub-condition will the fault code corresponding to that sub-condition be detected to determine whether it is a fault code with a potential fault risk, and subsequently, the fault code will be optimized.

[0060] Step S20: Determine the fault codes that pose a risk of failure based on the fault diagnosis information and the driving data.

[0061] It should be noted that determining the fault code with potential fault risk based on the fault diagnosis information and the driving data can be done by determining whether the fault code to be verified has a fault risk based on the fault diagnosis information and the driving data. If the fault code to be verified has a fault risk, then the fault code is determined to be a fault code with potential fault risk. The fault code to be verified can be the fault code corresponding to the fault diagnosis information.

[0062] Step S30: Optimize the fault code reporting of the vehicle based on the fault code to reduce the reporting risk of the fault code.

[0063] It should be noted that the fault code reporting optimization of the vehicle based on the fault code may involve determining the fault diagnosis conditions corresponding to the fault code, such as a fault diagnosis threshold, and increasing the fault diagnosis threshold to reduce the reporting risk of the fault code.

[0064] In specific implementation, the initial fault threshold of signal A corresponding to fault code 1 is 10. That is, when the vehicle is in motion, if the measured value of signal A exceeds the initial fault threshold of 10, for example, if the measured value of signal A is 11, the vehicle will report fault code 1. In this embodiment, by raising the initial fault threshold of signal A to 12, the measured value of signal A will not lead to the reporting of fault code 1 when it is 11, thereby reducing the risk of fault code reporting.

[0065] Furthermore, in order to reduce the number of fault code reports and reduce the number of repairs and costs for users, step S30 may include: determining the target influencing factors corresponding to the fault code; and adjusting the vehicle's control parameters according to the target influencing factors to reduce the measured value corresponding to the fault code.

[0066] It should be noted that the target influencing factor can be a control factor that can affect the measured value corresponding to the fault code. In this embodiment, by adjusting the vehicle's control parameters through the target influencing factor, the measured value corresponding to the fault code can be reduced, thus preventing the measured value corresponding to the fault code from exceeding the fault threshold and causing the fault code to be reported.

[0067] In practice, a certain engine control system reported a P2177 fault code risk, which corresponds to the air-fuel ratio closed-loop control self-learning value exceeding the fault threshold. This can be addressed by increasing the pre-control FKKVS and other calibration tables in the 800-2000 RPM range to increase the injection coefficient. The control system then reduces the multiplicative correction factor fri value of the air-fuel mixture adaptive feedback through self-learning (i.e., the measured value is reduced), giving fri a larger safety margin compared to the fault threshold FRADX.

[0068] This embodiment acquires fault diagnosis information corresponding to preset fault diagnosis conditions when the vehicle's driving data meets those conditions; determines fault codes with potential fault risks based on the fault diagnosis information and the driving data; and optimizes the fault code reporting for the vehicle based on the fault codes to reduce the reporting risk of the fault codes. Because this embodiment acquires fault diagnosis information corresponding to preset fault diagnosis conditions when the vehicle's driving data meets those conditions; determines fault codes with potential fault risks based on the fault diagnosis information and the driving data; and optimizes the fault code reporting for the vehicle based on the fault codes, compared to existing fault code reporting logic, this embodiment reduces the number of fault code reports and the associated risks, reduces vehicle repair frequency, and improves user experience.

[0069] refer to Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the fault code reporting optimization method of the present invention.

[0070] Based on the first embodiment described above, in this embodiment, step S20 includes:

[0071] Step S201: Determine the fault to be verified based on the fault diagnosis information.

[0072] It should be noted that the fault to be verified can be the fault information corresponding to the fault code of the fault diagnosis information.

[0073] Step S202: When the fault to be verified has a fault setting time, determine the measured value corresponding to the fault to be verified based on the driving data.

[0074] It should be noted that when determining whether a vehicle has malfunctioned, it is usually determined by comparing the measured value with a preset threshold. When the measured value is greater than the preset threshold, the vehicle is determined to have a malfunction. For the detection of certain malfunctions, in order to prevent false alarms, the measured value needs to be greater than the preset threshold for a continuous period of time before the vehicle is determined to have a malfunction. This type of malfunction, which requires the measured value to be greater than the preset threshold for a continuous period of time, is called a malfunction setting time. When the malfunction setting time is 2 seconds, that is, when the measured value is greater than the preset threshold for 2 consecutive seconds, the vehicle is determined to have a malfunction; when the malfunction setting time is 5 seconds, that is, when the measured value is greater than the preset threshold for 5 consecutive seconds, the vehicle is determined to have a malfunction. The measured value can be the parameter value corresponding to the malfunction to be verified.

[0075] Furthermore, for certain faults to be verified that do not have the fault set-time, in order to determine whether such faults pose a risk of fault code reporting, after step S201, the method further includes: when the fault to be verified does not have a fault set-time, determining the measured value corresponding to the fault to be verified based on the driving data; determining the fault threshold and target value corresponding to the fault to be verified based on the fault diagnosis information; determining whether the fault to be verified poses a fault risk based on the measured value, the fault threshold, and the target value; and determining the fault code corresponding to the fault to be verified when the fault to be verified poses a fault risk.

[0076] It should be noted that the target value can be the optimal value corresponding to the fault to be verified, determined through vehicle testing, or a standard value among the measured values. The step of determining whether the fault to be verified has a risk based on the measured value, the fault threshold, and the target value can be achieved by determining a risk value based on the measured value, the fault threshold, and the target value, specifically by calculating the risk value using the following formula:

[0077] S = |Measured value - Fault threshold| / |Fault threshold - Target value|

[0078] Here, S represents the risk value. When the risk value is less than or equal to 10%, the fault to be verified is determined to have a fault risk. In this case, the fault code corresponding to the fault to be verified is used as the fault code with the fault risk for optimization.

[0079] Step S203: When the measured value is greater than the fault threshold corresponding to the fault to be verified, start the timer to begin counting.

[0080] It should be noted that the fault threshold can be a pre-set reference value for determining whether the vehicle has a fault. For example, when the measured value is greater than the fault threshold corresponding to the fault to be verified, it can be determined that the vehicle has the fault to be verified.

[0081] Step S204: Determine the fault codes that pose a risk of failure based on the timing results and the fault diagnosis information.

[0082] It should be noted that determining the fault code with fault risk based on the timing result and the fault diagnosis information can be done by judging whether the vehicle has the fault to be verified based on the timing result and the fault setting time in the fault diagnosis information. If it does, the fault code corresponding to the fault to be verified is taken as the fault code with fault risk.

[0083] Furthermore, in order to optimize the fault code when there is a risk of reporting the fault code, rather than only optimizing the fault code when the corresponding fault exists, so as to reduce the number of fault code reports, step S204 may include: determining the fault setting time of the fault to be verified based on the fault diagnosis information; determining the target setting time based on the fault setting time; and determining the fault code of the fault to be verified when the timing result is greater than the target setting time.

[0084] It should be noted that the fault setting time can be the fault diagnosis time corresponding to the fault to be verified. For example, when the fault setting time is 3 seconds, the vehicle is determined to have the fault to be verified only when the measured value corresponding to the fault to be verified is greater than the fault threshold for more than 3 seconds. Determining the target setting time based on the fault setting time can be done by using 90% of the fault setting time as the target setting time. When the timing result is greater than the setting time, the vehicle can be determined to have the fault to be verified. However, in this embodiment, it is necessary to determine the fault code that poses a risk of fault code reporting, not the fault code that actually causes a fault. Therefore, in this embodiment, the fault code of the fault to be verified whose timing result is greater than the target setting time is considered as the fault code that poses a risk of fault code reporting.

[0085] This embodiment determines the fault to be verified based on the fault diagnosis information; when the fault to be verified has a fault set time, it determines the measured value corresponding to the fault to be verified based on the driving data; when the measured value is greater than the fault threshold corresponding to the fault to be verified, a timer is started; and fault codes with fault risk are determined based on the timing result and the fault diagnosis information. This embodiment can accurately determine whether a fault code has a reporting risk, and then optimize fault codes with reporting risk, reducing the number of fault code reports, thereby reducing the number of repairs and costs for users, and improving the user experience.

[0086] refer to Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the fault code reporting optimization method of the present invention.

[0087] Based on the above embodiments, in this embodiment, step S30 includes:

[0088] Step S301: Obtain the test results of the vehicle test in response to the fault code.

[0089] In practice, when the fault code is a fault code with a reporting risk, in order to optimize the reporting risk of the fault code, it is necessary to test the vehicle and determine the ideal fault threshold based on the test results.

[0090] Step S302: Determine the ideal fault threshold corresponding to the fault code based on the test results.

[0091] It should be noted that the ideal fault threshold corresponding to the fault code determined based on the test results can be the highest upper limit threshold corresponding to the fault code under safe driving conditions determined based on the test results.

[0092] Step S302: Use the ideal fault threshold as the fault threshold corresponding to the fault code.

[0093] It should be understood that the ideal fault threshold is generally greater than the fault threshold corresponding to the fault code. Using the ideal fault threshold as the fault threshold corresponding to the fault code can reduce the number of fault code reports, thereby reducing the number of repairs required by the user.

[0094] This embodiment obtains the test results of vehicle testing in response to the fault code; determines the ideal fault threshold corresponding to the fault code based on the test results; and uses the ideal fault threshold as the fault threshold corresponding to the fault code. This embodiment determines the ideal fault threshold corresponding to the fault code based on the test results of vehicle testing in response to the fault code; and uses the ideal fault threshold as the fault threshold corresponding to the fault code. This avoids the actual measured value being too high or too low as to cause false fault code reports, increasing the number of repairs required by the user, and thus improving the user experience.

[0095] Reference Figure 5 , Figure 5 This is a structural block diagram of the first embodiment of the fault code reporting optimization device of the present invention.

[0096] like Figure 5 As shown, the fault code reporting optimization device proposed in this embodiment of the invention includes:

[0097] The fault diagnosis information acquisition module 10 is used to acquire fault diagnosis information corresponding to the preset fault diagnosis conditions when the vehicle's driving data meets the preset fault diagnosis conditions.

[0098] The fault code determination module 20 is used to determine fault codes that pose a risk of failure based on the fault diagnosis information and the driving data.

[0099] The optimization module 30 is used to optimize the fault code reporting of the vehicle based on the fault code, so as to reduce the reporting risk of the fault code.

[0100] This embodiment acquires fault diagnosis information corresponding to preset fault diagnosis conditions when the vehicle's driving data meets those conditions; determines fault codes with potential fault risks based on the fault diagnosis information and the driving data; and optimizes the fault code reporting for the vehicle based on the fault codes to reduce the reporting risk of the fault codes. Because this embodiment acquires fault diagnosis information corresponding to preset fault diagnosis conditions when the vehicle's driving data meets those conditions; determines fault codes with potential fault risks based on the fault diagnosis information and the driving data; and optimizes the fault code reporting for the vehicle based on the fault codes, compared to existing fault code reporting logic, this embodiment reduces the number of fault code reports and the associated risks, reduces vehicle repair frequency, and improves user experience.

[0101] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.

[0102] In addition, for technical details not described in detail in this embodiment, please refer to the fault code reporting optimization method provided in any embodiment of the present invention, which will not be repeated here.

[0103] Based on the first embodiment of the fault code reporting optimization device of the present invention, a second embodiment of the fault code reporting optimization device of the present invention is proposed.

[0104] In this embodiment, the fault code determination module 20 is further configured to determine the fault to be verified based on the fault diagnosis information;

[0105] When the fault to be verified has a fault setting time, the measured value corresponding to the fault to be verified is determined based on the driving data;

[0106] When the measured value is greater than the fault threshold corresponding to the fault to be verified, the timer is started.

[0107] Based on the timing results and the aforementioned fault diagnosis information, fault codes indicating potential fault risks are identified.

[0108] Furthermore, the fault code determination module 20 is also used to determine the fault setting time of the fault to be verified based on the fault diagnosis information;

[0109] Determine the target setting time based on the fault setting time;

[0110] If the timing result is greater than the target setting time, it is determined that the fault to be verified has a fault risk, and the fault code of the fault to be verified is determined.

[0111] Furthermore, the fault code determination module 20 is also used to determine the measured value corresponding to the fault to be verified based on the driving data when the fault to be verified does not have a fault setting time.

[0112] Based on the fault diagnosis information, determine the fault threshold and target value corresponding to the fault to be verified;

[0113] Based on the measured value, the fault threshold, and the target value, determine whether the fault to be verified has a fault risk;

[0114] When the fault to be verified has a risk of failure, the fault code corresponding to the fault to be verified is determined.

[0115] Furthermore, the optimization module 30 is also used to obtain the test results of vehicle testing in response to the fault code;

[0116] Determine the ideal fault threshold corresponding to the fault code based on the test results;

[0117] The ideal fault threshold is used as the fault threshold corresponding to the fault code.

[0118] Furthermore, the optimization module 30 is also used to determine the target influencing factors corresponding to the fault code;

[0119] Adjust the vehicle's control parameters according to the target influencing factors to reduce the measured value corresponding to the fault code.

[0120] Furthermore, the fault diagnosis information acquisition module 10 is also used to acquire the vehicle's driving data during the test process;

[0121] Obtain preset fault diagnosis conditions, wherein the preset fault diagnosis conditions include at least one fault diagnosis sub-condition;

[0122] When the driving data meets the preset fault diagnosis conditions, obtain the fault diagnosis information corresponding to the fault diagnosis sub-conditions met by the driving data.

[0123] Other embodiments or specific implementations of the fault code reporting optimization device of the present invention can be referred to the above-described method embodiments, and will not be repeated here.

[0124] Furthermore, this embodiment of the invention also proposes a storage medium storing a fault code reporting optimization program, which, when executed by a processor, implements the steps of the fault code reporting optimization method described above.

[0125] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0126] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0127] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory / random access memory, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0128] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A fault code reporting optimization method, characterized in that, The fault code reporting optimization method includes the following steps: When the vehicle's driving data meets the preset fault diagnosis conditions, obtain the fault diagnosis information corresponding to the preset fault diagnosis conditions. Based on the fault diagnosis information and the driving data, fault codes indicating potential fault risks are determined; Based on the fault codes, the vehicle's fault code reporting is optimized to reduce the risk of fault code reporting. The step of determining fault codes with potential fault risks based on the fault diagnosis information and the driving data includes: The fault to be verified is determined based on the fault diagnosis information. When the fault to be verified does not have a fault setting time, the measured value corresponding to the fault to be verified is determined based on the driving data; Based on the fault diagnosis information, determine the fault threshold and target value corresponding to the fault to be verified; The risk value is determined using the following formula based on the measured value, the fault threshold, and the target value: S = |Measured value - Fault threshold| / |Fault threshold - Target value| Wherein, S is used to characterize the risk value; Based on the risk value, determine whether the fault to be verified has a risk of failure; When the fault to be verified has a risk of failure, the fault code corresponding to the fault to be verified is determined.

2. The fault code reporting optimization method as described in claim 1, characterized in that, The step of determining fault codes with potential fault risks based on the fault diagnosis information and the driving data includes: The fault to be verified is determined based on the fault diagnosis information. When the fault to be verified has a fault setting time, the measured value corresponding to the fault to be verified is determined based on the driving data; When the measured value is greater than the fault threshold corresponding to the fault to be verified, the timer is started. Based on the timing results and the aforementioned fault diagnosis information, fault codes indicating potential fault risks are identified.

3. The fault code reporting optimization method as described in claim 2, characterized in that, The step of determining fault codes with potential fault risks based on timing results and fault diagnosis information includes: The fault setting time of the fault to be verified is determined based on the fault diagnosis information. Determine the target setting time based on the fault setting time; If the timing result is greater than the target setting time, it is determined that the fault to be verified has a fault risk, and the fault code of the fault to be verified is determined.

4. The fault code reporting optimization method as described in any one of claims 1-3, characterized in that, The step of optimizing the fault code reporting of the vehicle based on the fault code includes: Obtain the test results of the vehicle test performed in response to the fault code; Determine the ideal fault threshold corresponding to the fault code based on the test results; The ideal fault threshold is used as the fault threshold corresponding to the fault code.

5. The fault code reporting optimization method as described in any one of claims 1-3, characterized in that, The step of optimizing the fault code reporting of the vehicle based on the fault code includes: Identify the target influencing factors corresponding to the fault code; Adjust the vehicle's control parameters according to the target influencing factors to reduce the measured value corresponding to the fault code.

6. The fault code reporting optimization method as described in any one of claims 1-3, characterized in that, The step of obtaining fault diagnosis information corresponding to the preset fault diagnosis conditions when the vehicle's driving data meets the preset fault diagnosis conditions includes: Acquire vehicle driving data during the testing process; Obtain preset fault diagnosis conditions, wherein the preset fault diagnosis conditions include at least one fault diagnosis sub-condition; When the driving data meets the preset fault diagnosis conditions, obtain the fault diagnosis information corresponding to the fault diagnosis sub-conditions met by the driving data.

7. A fault code reporting optimization device, characterized in that, The fault code reporting optimization device includes: The fault diagnosis information acquisition module is used to acquire fault diagnosis information corresponding to the preset fault diagnosis conditions when the vehicle's driving data meets the preset fault diagnosis conditions. The fault code determination module is used to determine fault codes that pose a risk of failure based on the fault diagnosis information and the driving data. An optimization module is used to optimize the fault code reporting of the vehicle based on the fault code, so as to reduce the reporting risk of the fault code; The fault code determination module is used to determine the fault to be verified based on the fault diagnosis information; When the fault to be verified does not have a fault setting time, the measured value corresponding to the fault to be verified is determined based on the driving data; Based on the fault diagnosis information, determine the fault threshold and target value corresponding to the fault to be verified; The risk value is determined using the following formula based on the measured value, the fault threshold, and the target value: S = |Measured value - Fault threshold| / |Fault threshold - Target value| Wherein, S is used to characterize the risk value; Based on the risk value, determine whether the fault to be verified has a risk of failure; When the fault to be verified has a risk of failure, the fault code corresponding to the fault to be verified is determined.

8. A fault code reporting optimization device, characterized in that, The device includes: a memory, a processor, and a fault code optimization program stored in the memory and executable on the processor, the fault code optimization program being configured to implement the steps of the fault code optimization method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium stores a fault code reporting optimization program, which, when executed by a processor, implements the steps of the fault code reporting optimization method as described in any one of claims 1 to 6.

Images