Engine fault shielding detection method and device, electronic equipment and storage medium

Abstract

The application discloses an engine fault shielding detection method and device, electronic equipment and a storage medium. The engine fault shielding detection method comprises the following steps: in the case that the engine is powered on again after passing through at least one driving cycle, real-time monitoring is performed on a fault diagnosis bit corresponding to an engine fault; in response to the fault diagnosis bit being set, obtaining a fault corresponding parameter at the time of setting; judging whether the fault corresponding parameter meets a pre-set bit condition; if not, it is determined that there is a risk of fault shielding; if yes, according to a pre-set fault indication bit, it is determined whether there is a risk of fault shielding. The engine fault shielding detection method provided by the application can detect whether there is a risk of engine fault shielding, thereby reducing the probability of the following conditions: the fault is shielded but not found, the corresponding measures cannot be taken in time, the vehicle has a long-term problem but still drives normally, and a safety hazard is caused.

Description

Technical Field

[0001] This application relates to the field of engine technology, specifically to a method for preventing and shielding engine malfunctions. Background Technology

[0002] During vehicle operation, there is a practice where rewriting the Electronic Control Unit (ECU) data masks emission-related faults, preventing fault warnings from being reported and thus preventing situations such as speed and torque limiting from occurring. After the fault is masked, the fault diagnosis bits can be set normally, and the fault reporting bit remains in a "no fault reported" state, creating the false impression that the fault has been diagnosed but no fault exists. The vehicle will display the fault through warning lights or hazard lights on the instrument panel, allowing the user to locate and repair the engine problem based on the fault codes.

[0003] However, the relevant technologies cannot detect the risk of engine fault masking, which may lead to the following situation: the fault is masked but not detected, corresponding measures cannot be taken in time, and these fault information cannot be read or displayed normally, resulting in the vehicle continuing to operate with problems for a long time, causing safety hazards.

[0004] The above statements are for the purpose of providing background information in relation to this application only and do not necessarily constitute prior art. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus, electronic device, and storage medium for detecting engine fault masking risks. To provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. This summary is not intended as a general description, nor is it intended to identify key / important components or describe the scope of protection of these embodiments. Its sole purpose is to present some concepts in a simple form as a prelude to the detailed description that follows.

[0006] According to one aspect of the embodiments of this application, a method for detecting engine fault masking is provided, comprising:

[0007] When the engine is powered on again after at least one driving cycle, the fault diagnosis points corresponding to the engine fault are monitored in real time.

[0008] In response to the fault diagnosis bit being set, obtain the fault-related parameters when the bit is set.

[0009] Determine whether the parameters corresponding to the fault meet the preset bit conditions;

[0010] If the fault-corresponding parameter does not meet the preset bit condition, it is determined that there is a risk of fault masking.

[0011] If the fault-corresponding parameters meet the preset bit conditions, then it is determined whether there is a risk of fault masking based on the preset fault indication bit.

[0012] In some embodiments of this application, determining whether there is a risk of fault masking based on a preset fault indication bit includes:

[0013] Check whether the preset fault indicator bit has been set;

[0014] If the fault indicator bit is not set, it is determined that there is a risk of fault masking.

[0015] In some embodiments of this application, the step of determining whether there is a risk of fault masking based on a preset fault indication bit further includes:

[0016] If the fault indicator bit is set, a fault reporting calibration is performed so that the fault-corresponding parameters meet the preset fault reporting conditions.

[0017] When the fault reporting calibration is completed, read the status of the fault indication bit;

[0018] If the fault indicator bit is not set, it is determined that there is a risk of fault masking.

[0019] In some embodiments of this application, the step of determining whether there is a risk of fault masking based on a preset fault indication bit further includes:

[0020] If the fault indication bit is set, then a cure calibration is performed so that the fault-corresponding parameters meet the preset cure conditions.

[0021] Once the cure calibration is complete, read the status of the fault indicator bit;

[0022] If the fault indicator bit is not reset, it is determined that there is a risk of fault masking.

[0023] In some embodiments of this application, the method further includes:

[0024] If the fault indicator bit is reset, the fault data corresponding to the cured calibration will be restored to the fault data corresponding to the previous cured calibration.

[0025] In some embodiments of this application, the step of performing fault reporting calibration so that the fault-corresponding parameters meet preset fault reporting conditions includes: modifying the fault reporting conditions so that the fault-corresponding parameters meet the modified fault reporting conditions; or, modifying the fault-corresponding parameters so that the modified fault-corresponding parameters meet the fault reporting conditions.

[0026] The step of performing a cure calibration so that the fault-corresponding parameters meet preset cure conditions includes: modifying the preset cure conditions so that the fault-corresponding parameters meet the modified preset cure conditions; or, modifying the fault-corresponding parameters so that the modified fault-corresponding parameters meet the preset cure conditions.

[0027] In some embodiments of this application, the method further includes:

[0028] If a fault is deemed to be at risk, all data in the electronic control unit connected to the engine is checked to obtain the check results.

[0029] If the inspection result indicates that the fault is masked, the original data of the electronic control unit is restored by remote flashing to cancel the fault masking; the original data is the data before the fault was masked.

[0030] According to another aspect of the embodiments of this application, a detection device for engine fault shielding is provided, comprising:

[0031] The monitoring module is used to monitor the fault diagnosis points corresponding to engine faults in real time when the engine is powered on again after at least one driving cycle.

[0032] The fault-corresponding parameter acquisition module is used to acquire the fault-corresponding parameters when the fault diagnosis bit is set in response to the fault diagnosis bit being set.

[0033] A preset bit condition judgment module is used to determine whether the fault-corresponding parameter meets the preset bit condition;

[0034] The fault masking risk determination module is used to determine whether there is a fault masking risk if the fault-corresponding parameter does not meet the preset bit conditions, and to determine whether there is a fault masking risk based on the preset fault indication bit if the fault-corresponding parameter meets the preset bit conditions.

[0035] According to another aspect of the embodiments of this application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the engine fault masking detection method described in any embodiment of this application.

[0036] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, the computer program being executed by a processor to implement the engine fault masking detection method described in any embodiment of this application.

[0037] One aspect of the technical solution provided in this application embodiment may include the following beneficial effects:

[0038] The engine fault masking detection method provided in this application embodiment monitors the fault diagnosis bit corresponding to the engine fault in real time when the engine is powered on again after at least one driving cycle; in response to the fault diagnosis bit being set, it obtains the fault corresponding parameters when the bit is set; it determines whether the fault corresponding parameters meet the preset bit conditions; if the preset bit conditions are not met, it is determined that there is a risk of fault masking; if the fault corresponding parameters meet the preset bit conditions, it is determined whether there is a risk of fault masking according to the preset fault indication bit. This method can detect whether there is a risk of engine fault masking, so as to promptly remind relevant personnel of the risk of fault masking. This can greatly reduce the probability of the following situations: the fault is masked but not discovered, and corresponding measures cannot be taken in time; the fault information cannot be read or displayed normally, resulting in the vehicle having problems for a long time but still driving normally, causing safety hazards.

[0039] The above description is merely an overview of the technical solutions of the embodiments of this application. In order to better understand the technical means of the embodiments of this application and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of this application more obvious and understandable, specific implementation methods of this application are described below. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A flowchart of a detection method for engine fault masking according to an embodiment of this application is shown.

[0042] Figure 2 This document illustrates a flowchart of an embodiment of the present application for determining whether there is a risk of fault masking based on a preset fault indication bit.

[0043] Figure 3 A flowchart illustrating a specific example of an engine fault masking detection method according to this application is shown.

[0044] Figure 4 A block diagram of a detection device for engine fault shielding according to an embodiment of this application is shown.

[0045] Figure 5 A block diagram of an electronic device structure according to an embodiment of this application is shown.

[0046] Figure 6A schematic diagram of a computer-readable storage medium according to an embodiment of this application is shown. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0048] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have a meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0049] Data in the Electronic Control Unit (ECU) may be tampered with, causing faults to be masked and thus unable to be reported. This can lead to vehicles experiencing persistent malfunctions without proper repair, resulting in emissions pollution and safety hazards. While current technologies determine fault reporting and resolution by assessing engine status, sensor readings, fault codes, or indicator light status, they do not check for fault masking. In other words, these technologies can only detect whether a fault is reported and resolved, but cannot detect the risk of fault masking. This can lead to situations where faults are masked but not detected, preventing timely intervention and proper reading or display of fault information, resulting in vehicles continuing to operate despite persistent problems and creating safety hazards.

[0050] To address the technical problems existing in related technologies, the engine fault masking detection method provided in this application embodiment monitors the fault diagnosis bit corresponding to the engine fault in real time when the engine is powered on again after at least one driving cycle; in response to the fault diagnosis bit being set, it acquires the fault corresponding parameters when the bit is set; it determines whether the fault corresponding parameters meet preset bit conditions; if the preset bit conditions are not met, it is determined that there is a risk of fault masking; if the fault corresponding parameters meet the preset bit conditions, it is determined whether there is a risk of fault masking based on the preset fault indication bit. This method can detect whether there is a risk of engine fault masking, so as to promptly remind relevant personnel of the risk of fault masking. This can greatly reduce the probability of the following situations: the fault is masked but not discovered, and corresponding measures cannot be taken in time; the fault information cannot be read or displayed normally, resulting in the vehicle having problems for a long time but still driving normally, causing safety hazards.

[0051] refer to Figure 1 As shown, one embodiment of this application provides a method for detecting engine fault masking, which may include steps S10 to S50:

[0052] S10. When the engine is powered on again after at least one driving cycle, the fault diagnosis points corresponding to the engine fault are monitored in real time.

[0053] The complete process of a vehicle igniting, running (and, if necessary, detecting any malfunctions), and shutting down constitutes a driving cycle. This embodiment employs a self-checking method to detect the risk of malfunctions being masked. This method is used to detect the risk of malfunctions being masked across driving cycles, specifically by checking for malfunctions before the car key is turned off and then back on, driven a certain mileage, and then turned off again. It performs a self-check to prevent malfunction masking when malfunctions are re-diagnosed and detected after the key is turned off and then back on.

[0054] For example, a separate fault self-test module can be established in the electronic control unit (ECU) connected to the engine to prevent interference with the reporting and resolution of faults during non-fault self-test periods of the engine. A separate enable switch is used for this fault self-test module, and when the enable switch is set, fault self-test is allowed.

[0055] The fault diagnosis bit is a preset bit used to set the fault diagnosis bit when the fault diagnosis conditions are met, and not set it when the fault diagnosis conditions are not met. For example, if a fault diagnosis is only performed when the engine speed is not 0 (i.e., the fault diagnosis condition is that the engine speed is not 0), then the fault diagnosis bit will not be set when the engine speed is 0, and will only be set when the engine speed is not 0.

[0056] The fault diagnosis setting bit refers to the change in the state of the fault diagnosis bit from "diagnosis incomplete" to "diagnosis complete". When the state of the fault diagnosis bit is "diagnosis incomplete", the value of the fault diagnosis bit is 0. When the state of the fault diagnosis bit is "diagnosis complete", the value of the fault diagnosis bit is 1. The fault diagnosis setting bit is the change in the value of the fault diagnosis bit from 0 to 1.

[0057] For example, after the fault self-diagnosis module is enabled, it performs a risk screening test for each type of fault. From the time the vehicle is powered off to when it is powered on again, the fault diagnosis is performed again, and the fault diagnosis bits are monitored in real time.

[0058] S20. In response to the fault diagnosis bit being set, obtain the fault-related parameters when the bit is set.

[0059] For example, an array can be created to store fault-corresponding parameters for engine faults. These parameters may include, for example, engine speed. The fault-corresponding parameters are used to determine whether fault diagnosis conditions are met. A separate array is created and stored for each fault-corresponding parameter, and this array is monitored. The array at each fault diagnosis point is recorded, and the array is frozen, stored as a fault freeze frame. The fault freeze frame contains fault code data stored by the electronic control unit.

[0060] S30. Determine whether the parameters corresponding to the fault meet the preset bit conditions.

[0061] For example, if the fault diagnosis bit changes from a state of incomplete diagnosis to a state of complete diagnosis, i.e., it is set, the fault diagnosis logic is reversed, and the value frozen when it is set is compared with the preset bit condition.

[0062] Preset bit conditions could be, for example, the threshold that the corresponding fault parameter must reach when fault diagnosis is completed. The fault freeze frame is compared with the threshold that must be reached when fault diagnosis is completed to determine whether the preset bit conditions are met. If the fault freeze frame reaches the threshold that must be reached when fault diagnosis is completed, then the preset bit conditions are met; otherwise, they are not met.

[0063] For example, if diagnosing a certain fault requires engine speed data, a one-dimensional array can be created to store engine speed and monitor the status of the fault diagnosis bit. The change in engine speed value when the fault diagnosis bit is set can be obtained.

[0064] For example, if a fault requires a certain engine speed to be diagnosed, such as a threshold of 1000 rpm, we can determine whether the frozen engine speed value at the fault diagnosis location (from an incomplete state to a completed state) is greater than or equal to 1000 rpm. If the frozen value is 800 rpm, it is an abnormal diagnosis. If it is 1200 rpm, it is initially judged as a normal diagnosis.

[0065] For example, if fault diagnosis requires engine speed and intake pressure values, a two-dimensional array can be created to store these values. The system can then determine whether the fault diagnosis bit is set only when preset conditions are met. These preset conditions could be, for example, an engine speed exceeding 1000 rpm and an engine intake pressure greater than 0. When the fault diagnosis bit changes from 0 to 1, the stored parameter values ​​(i.e., engine speed and intake pressure) are recorded at the moment of change. Then, assuming the setting conditions are intake pressure greater than 0 and engine speed greater than or equal to 1000 rpm, if the intake pressure value is found to be less than 0 or the engine speed less than 1000 rpm during storage, then this setting is not a normal setting, indicating a risk of fault being masked.

[0066] S40. If the parameters corresponding to the fault do not meet the preset bit conditions, it is determined that there is a risk of fault masking.

[0067] Under normal circumstances, if the fault diagnosis bit is set, it means that a fault has been diagnosed and the corresponding fault parameters should meet the preset bit conditions. However, if the corresponding fault parameters are modified or otherwise fail to meet the preset bit conditions, it can be determined that there is a risk of fault masking.

[0068] In some embodiments, after determining that there is a risk of fault masking, a fault masking risk warning message can be issued to remind relevant personnel that there is a risk of fault masking in the current engine.

[0069] For example, if the preset bit conditions are not met, but the fault diagnosis bit has a rising edge indicating that the diagnosis is not completed, i.e., it is set, then it is determined that there is a risk of fault masking, and the fault self-test process is exited.

[0070] For example, if a pre-set condition for a fault is that a certain speed needs to be reached after the key is powered on to meet the diagnostic conditions, then the fault-corresponding parameters to be recorded are the power-on signal and the speed signal. If the fault is diagnosed normally, the information to be frozen when the fault diagnosis position is set is the speed signal and the ECU power-on signal. If the monitored fault has met the diagnostic conditions, the fault diagnosis position changes from an incomplete diagnosis state to a completed diagnosis state, but the recorded fault freeze frame shows a speed of zero and ECU power-on, instead of a non-zero value with a speed greater than a certain threshold and ECU power-on, then it is judged as an abnormal diagnosis, and the fault is considered to be at risk of being masked. After exiting this fault self-test process, all data in the ECU is sent back for inspection to check whether the fault is masked. For example, is there a situation where the fault is kept in the fault diagnosis position state but not reported through some calibration? If the fault is confirmed to be masked, the original data can be restored through remote flashing to cancel the fault masking. Currently, many vehicles have remote flashing capabilities. Remote flashing, also known as OTA, refers to uploading the update software to the OTA center, then the OTA center wirelessly transmits the update software to the vehicle, and finally the vehicle automatically updates the software.

[0071] If the fault freeze frame stored when the fault diagnosis position is set is compared with the threshold condition that the diagnosis condition needs to be met, and it is determined that the fault diagnosis condition is met, then the fault self-test can continue to check whether the fault indicator bit status is normal.

[0072] S50. If the fault-corresponding parameters meet the preset bit conditions, then determine whether there is a fault shielding risk based on the preset fault indication bit.

[0073] The fault indication bit is a preset bit that is set when a fault is detected and not set when no fault is detected.

[0074] For example, refer to Figure 2 As shown, determining whether there is a risk of fault masking based on a preset fault indication bit may include steps S501 to S502: detecting whether the preset fault indication bit is set; if the fault indication bit is not set, it is determined that there is a risk of fault masking.

[0075] The fault indicator bit is used to indicate whether a fault has been detected. The fault indicator bit is set when a fault is detected and not set when no fault is detected. When the fault indicator bit is used to indicate whether a fault has been detected, setting the fault indicator bit represents a change in its state from "fault not reported" to "fault reported". The value of the fault indicator bit in the "fault not reported" state is 0, and the value of the fault indicator bit in the "fault reported" state is 1. Setting the fault indicator bit, i.e., changing its value from 0 to 1, occurs on a rising edge.

[0076] If the fault-related parameters meet the preset bit conditions and the fault indicator bit is set, it can be determined that there is no risk of fault masking, and the fault self-test logic can be exited directly.

[0077] In some embodiments, determining whether there is a risk of fault masking based on a preset fault indication bit may further include a step of preprocessing the fault-corresponding parameters. The step of preprocessing the fault-corresponding parameters may include: marking the storage priority of the fault-corresponding parameters as the lowest and setting visibility information for fault diagnosis instrument diagnosis for the fault-corresponding parameters.

[0078] If the fault indicator bit does not have a rising edge indicating a change from no fault to a reported fault, i.e., the fault indicator bit is not set, the corresponding fault parameters are preprocessed. The preprocessing may include: establishing a fault information array; marking the fault storage priority as the lowest during the fault self-test process so that it is not entered into the storage logic; and setting the visibility information of the fault diagnostic instrument so that the fault cannot be read by the diagnostic instrument, thereby preventing the fault self-test process from increasing the failure rate.

[0079] In some embodiments, determining whether there is a risk of fault masking based on a preset fault indicator bit may further include: if the fault indicator bit is set, performing fault reporting calibration to make the fault-corresponding parameters meet preset fault reporting conditions; when the fault reporting calibration is completed, reading the state of the fault indicator bit; if the state of the fault indicator bit is not set, determining that there is a risk of fault masking.

[0080] For example, fault reporting calibration, to ensure that the parameters corresponding to the fault meet preset fault reporting conditions, may include:

[0081] Modify the fault reporting conditions so that the corresponding parameters meet the modified fault reporting conditions; or,

[0082] Modify the parameters corresponding to the fault so that the modified parameters meet the fault reporting conditions.

[0083] For example, if the fault-corresponding parameter is engine speed, and the fault reporting condition is engine speed below 1000 rpm, and the actual engine speed is 1200 rpm, then when calibrating the fault reporting for this engine speed, the fault reporting condition can be modified to 1300 rpm, thus ensuring the fault-corresponding parameter meets the fault reporting condition. At this point, the status of the fault indicator bit is read. If the fault indicator bit is not set, meaning that the fault indicator bit does not report a fault even though the fault-corresponding parameter meets the fault reporting condition, then it is determined that there is a risk of fault masking.

[0084] For example, if the fault-corresponding parameter is engine speed, and the fault reporting condition is an engine speed below 1000 rpm, and the actual engine speed is 1200 rpm, then the fault reporting calibration is performed on that engine speed, modifying it to 800 rpm, thus ensuring the fault-corresponding parameter meets the fault reporting condition. At this point, the status of the fault indicator bit is read. If the fault indicator bit is not set, meaning that the fault indicator bit does not report a fault even though the fault-corresponding parameter meets the fault reporting condition, then a fault masking risk is identified.

[0085] For example, after preprocessing the parameters corresponding to the fault, the fault reporting calibration logic is run, that is, the fault reporting parameters are calibrated to meet the fault reporting conditions. At this time, the fault indicator bit is detected. If the fault indicator bit changes from a non-reported fault state to a reported fault state with a rising edge, that is, the fault indicator bit is set, it is determined that the fault can be reported normally and there is no risk of the fault being masked. If the fault indicator bit is not set (that is, there is no rising edge changing from a non-reported fault state to a reported fault state), it is determined that there is a risk of the fault being masked. The data is sent back for inspection. If the fault is confirmed to be masked, the original data is restored by remote flashing, and the fault masking is canceled.

[0086] In some embodiments, determining whether there is a risk of fault masking based on a preset fault indicator bit may further include: if the state of the fault indicator bit is set, performing a cure calibration so that the fault-corresponding parameter meets a preset cure condition; if the cure calibration is completed, reading the state of the fault indicator bit; if the fault indicator bit is not reset, determining that there is a risk of fault masking.

[0087] Specifically, if it is determined that the fault can be reported normally and there is no risk of the fault being masked, the corresponding parameters of the fault are calibrated to meet the preset healing conditions; the status of the fault indicator bit is read; if the fault indicator bit is not reset, it is determined that there is a risk of fault masking; if the fault indicator bit is reset, it is determined that there is no risk of fault masking.

[0088] The fault indicator bit can also be used to indicate whether a fault has been cured. The fault indicator bit is set when the fault is cured and not set when the fault is not cured. When the fault indicator bit is used to indicate whether a fault has been cured, setting the fault indicator bit represents a change in the state of the fault indicator bit from an uncured state to a cured state. The value of the fault indicator bit in the uncured state is 0, and the value of the fault indicator bit in the cured state is 1. Setting the fault indicator bit means that the value of the fault indicator bit changes from 0 to 1. The fault indicator bit has a rising edge that indicates a change from an uncured state to a cured state.

[0089] For example, performing a cure calibration so that the fault-corresponding parameters meet preset cure conditions may include:

[0090] Modify the preset cure conditions so that the parameters corresponding to the fault meet the modified preset cure conditions; or,

[0091] Modify the parameters corresponding to the fault so that the modified parameters meet the preset cure conditions.

[0092] For example, if the fault corresponds to engine speed, and the preset cure condition is an engine speed greater than or equal to 1000 rpm, and the actual engine speed is 800 rpm, the preset cure condition can be modified to 700 rpm, thus ensuring the fault corresponds to the corrected preset cure condition. At this point, the status of the fault indicator bit is read. If the fault indicator bit is not set, meaning it is not reset even though the fault corresponds to the corrected cure condition, then a fault masking risk is identified. If the fault indicator bit is reset, then no fault masking risk is identified.

[0093] For example, if the fault corresponds to engine speed, and the preset cure condition is an engine speed greater than or equal to 1000 rpm, and the actual engine speed is 800 rpm, then the engine speed can be modified to 1200 rpm to satisfy the preset cure condition. At this point, the status of the fault indicator bit is read. If the fault indicator bit is not set, meaning it is not reset even though the fault corresponds to the fault condition, then a fault masking risk is identified. If the fault indicator bit is reset, then no fault masking risk is identified.

[0094] If the fault can be reported normally and there is no risk of the fault being masked, the fault healing calibration logic can continue. After the healing calibration is completed, the fault indicator bit is read again. If there is a rising edge that changes the fault reported state to the fault not reported state, the data before the healing calibration is restored and the fault self-test logic is exited.

[0095] In some embodiments, the method further includes: if the fault indicator bit is reset, restoring the fault corresponding data of the cured calibration to the fault corresponding data before the cured calibration.

[0096] The fault indicator bit is reset, indicating that the fault has not been masked. The fault data corresponding to the cured calibration will be restored to the fault data corresponding to the fault before the cured calibration, so that it can be used for subsequent fault self-testing.

[0097] In some embodiments, the method may further include:

[0098] If a fault is deemed to be at risk, all data in the electronic control unit connected to the engine is checked to obtain the check results.

[0099] If the inspection results indicate that the fault is masked, the original data of the electronic control unit will be restored by remote flashing to cancel the fault masking. This original data is the data before the fault was masked.

[0100] Specifically, if a fault masking risk is determined, in order to further determine whether fault masking has actually occurred, all data in the electronic control unit is checked and the check results are obtained. If the check results indicate that the fault has been masked, the original data of the electronic control unit is restored by remote flashing, and the fault masking is canceled. This original data is the data before the fault was masked.

[0101] refer to Figure 3 As shown, in a specific example, the detection method for engine fault masking may include: detecting whether the vehicle has undergone a power-on process; if not, no fault self-test is performed; if it has, detecting whether the fault self-test module is enabled; if not, no fault self-test is performed; if enabled, a fault self-test is performed; then determining whether the fault diagnosis bit is set; if not, no self-test is performed; if set, a diagnostic freeze frame is stored; determining whether the diagnostic freeze frame meets the condition for the fault diagnosis bit to be set; if not, it is determined that the fault has a risk of being masked; if so, it is determined whether the fault indication bit is set; if not, it is determined that the fault has a risk of being masked; if set, the corresponding fault parameters are preprocessed, and then a reporting calibration is performed; determining whether the fault indication bit is set; if not, it is determined that the fault has a risk of being masked; if set, a cure calibration is performed, and the status of the fault indication bit is further used to determine whether there is a risk of the fault being masked.

[0102] The method in this application embodiment executes detection logic to detect whether a fault is being masked. It monitors the rising edge of the fault reporting indicator and checks the rationality of the rising edge completion to determine if the fault is masked. This process does not affect the fault reporting rate or the reporting and resolution of faults under normal vehicle operation. The method in this application embodiment can effectively and cost-effectively detect the risk of fault masking, preventing situations where a vehicle or engine malfunction is masked, thus reducing the risk of safety hazards or increased emissions caused by operating a vehicle or engine with a fault.

[0103] refer to Figure 4As shown, another embodiment of this application provides a detection device for engine fault masking, comprising:

[0104] The monitoring module is used to monitor the fault diagnosis points corresponding to engine faults in real time when the engine is powered on again after at least one driving cycle.

[0105] The fault-corresponding parameter acquisition module is used to acquire the fault-corresponding parameters when the fault diagnosis bit is set in response to the fault diagnosis bit being set.

[0106] A preset bit condition judgment module is used to determine whether the fault-corresponding parameter meets the preset bit condition;

[0107] The fault masking risk determination module is used to determine whether there is a fault masking risk if the fault-corresponding parameter does not meet the preset bit conditions, and to determine whether there is a fault masking risk based on the preset fault indication bit if the fault-corresponding parameter meets the preset bit conditions.

[0108] In some embodiments, the fault masking risk determination module is further specifically used to: detect whether a preset fault indicator bit is set; if the fault indicator bit is not set, it is determined that there is a fault masking risk.

[0109] In some embodiments, the fault masking risk determination module is further specifically used for: if the fault indicator bit is set, performing fault reporting calibration so that the fault-corresponding parameters meet preset fault reporting conditions; when the fault reporting calibration is completed, reading the state of the fault indicator bit; if the state of the fault indicator bit is not set, determining that there is a fault masking risk.

[0110] In some embodiments, the fault masking risk determination module is further specifically used for: if the state of the fault indicator bit is set, performing a cure calibration so that the fault-corresponding parameter meets the preset cure conditions; if the cure calibration is completed, reading the state of the fault indicator bit; if the fault indicator bit is not reset, determining that there is a fault masking risk.

[0111] In some embodiments, the detection device further includes a recovery module, which is used to restore the fault-corresponding data of the cured calibration to the fault-corresponding data before the cured calibration if the fault indication bit is reset.

[0112] In some embodiments, the fault masking risk determination module is further specifically used to: modify the fault reporting conditions so that the fault-corresponding parameters meet the modified fault reporting conditions; or, modify the fault-corresponding parameters so that the modified fault-corresponding parameters meet the fault reporting conditions; the step of performing cure calibration so that the fault-corresponding parameters meet the preset cure conditions includes: modifying the preset cure conditions so that the fault-corresponding parameters meet the modified preset cure conditions; or, modifying the fault-corresponding parameters so that the modified fault-corresponding parameters meet the preset cure conditions.

[0113] In some embodiments, the detection device further includes:

[0114] The inspection module is used to inspect all data in the electronic control unit connected to the engine when it is determined that there is a risk of fault masking, and to obtain the inspection results.

[0115] The flashing module is used to remotely flash and restore the original data of the electronic control unit to cancel the fault masking if the inspection result indicates that the fault has been masked; the original data is the data before the fault was masked.

[0116] The engine fault masking detection device provided in this application embodiment monitors the fault diagnosis bit corresponding to the engine fault in real time when the engine is powered on again after at least one driving cycle; in response to the fault diagnosis bit being set, it obtains the fault corresponding parameters when the bit is set; it determines whether the fault corresponding parameters meet the preset bit conditions; if the preset bit conditions are not met, it determines that there is a risk of fault masking; if the fault corresponding parameters meet the preset bit conditions, it determines whether there is a risk of fault masking based on the preset fault indication bit. This device can detect whether there is a risk of engine fault masking, so as to promptly remind relevant personnel of the risk of fault masking. This can greatly reduce the probability of the following situations: the fault is masked but not detected, and corresponding measures cannot be taken in time; the fault information cannot be read or displayed normally, resulting in the vehicle having problems for a long time but still driving normally, causing safety hazards.

[0117] Another embodiment of this application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any of the above embodiments.

[0118] refer to Figure 5As shown, the electronic device 10 may include: a processor 100, a memory 101, a bus 102 and a communication interface 103. The processor 100, the communication interface 103 and the memory 101 are connected through the bus 102. The memory 101 stores a computer program that can run on the processor 100. When the processor 100 runs the computer program, it executes the method provided in any of the foregoing embodiments of this application.

[0119] The memory 101 may include high-speed random access memory (RAM), and may also include non-volatile memory, such as at least one disk storage device. Communication between this device network element and at least one other network element is achieved through at least one communication interface 103 (which may be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc.

[0120] Bus 102 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. Memory 101 is used to store programs. After receiving an execution instruction, processor 100 executes the program. The methods disclosed in any of the foregoing embodiments of this application can be applied to processor 100, or implemented by processor 100.

[0121] Processor 100 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 100 or by instructions in software form. The processor 100 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), an Off-the-shelf Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 101. The processor 100 reads the information in memory 101 and, in conjunction with its hardware, completes the steps of the above method.

[0122] The electronic devices and methods provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods they employ, operate, or implement.

[0123] Another embodiment of this application provides a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the methods described in any of the above embodiments. Reference Figure 6 As shown, the computer-readable storage medium is an optical disc 20, on which a computer program (i.e., a program product) is stored. When the computer program is run by a processor, it executes the methods provided in any of the aforementioned embodiments.

[0124] It should be noted that examples of computer-readable storage media may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0125] The computer-readable storage medium provided in the above embodiments of this application and the method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0126] It should be noted that:

[0127] The term "module" is not intended to be limited to a specific physical form. Depending on the application, a module can be implemented as hardware, firmware, software, and / or a combination thereof. Furthermore, different modules may share common components or even be implemented using the same components. Clear boundaries may or may not exist between different modules.

[0128] The algorithms and displays provided herein are not inherently related to any particular computer, virtual device, or other equipment. Various general-purpose devices can also be used with the examples based on this. The required structure for constructing such devices is obvious from the above description. Furthermore, this application is not directed to any particular programming language. It should be understood that the content of this application described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of this application.

[0129] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0130] The above embodiments merely illustrate the implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for detecting engine fault masking, characterized in that, include: When the engine is powered on again after at least one driving cycle, the fault diagnosis points corresponding to the engine fault are monitored in real time. In response to the fault diagnosis bit being set, obtain the fault-related parameters when the bit is set. Determine whether the parameters corresponding to the fault meet the preset bit conditions; If the fault-corresponding parameter does not meet the preset bit condition, it is determined that there is a risk of fault masking. If the fault-corresponding parameters meet the preset bit conditions, then determine whether there is a risk of fault masking based on the preset fault indication bit. The step of determining whether there is a risk of fault masking based on a preset fault indication bit includes: Check whether the preset fault indicator bit has been set; If the fault indicator bit is not set, it is determined that there is a risk of fault masking. If the fault indicator bit is set, a fault reporting calibration is performed so that the fault-corresponding parameters meet the preset fault reporting conditions. When the fault reporting calibration is completed, read the status of the fault indication bit; If the fault indicator bit is not set, it is determined that there is a risk of fault masking. If the fault indication bit is set, then a cure calibration is performed so that the fault-corresponding parameters meet the preset cure conditions. Once the cure calibration is complete, read the status of the fault indicator bit; If the fault indicator bit is not reset, it is determined that there is a risk of fault masking.

2. The method according to claim 1, characterized in that, The method further includes: If the fault indicator bit is reset, the fault data corresponding to the cured calibration will be restored to the fault data corresponding to the previous cured calibration.

3. The method according to claim 1, characterized in that, The step of performing fault reporting calibration to make the fault-corresponding parameters meet the preset fault reporting conditions includes: modifying the fault reporting conditions so that the fault-corresponding parameters meet the modified fault reporting conditions; or, modifying the fault-corresponding parameters so that the modified fault-corresponding parameters meet the fault reporting conditions. The step of performing a cure calibration so that the fault-corresponding parameters meet preset cure conditions includes: modifying the preset cure conditions so that the fault-corresponding parameters meet the modified preset cure conditions; or, modifying the fault-corresponding parameters so that the modified fault-corresponding parameters meet the preset cure conditions.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: If a fault masking risk is determined, all data in the electronic control unit connected to the engine is checked to obtain the check results; If the inspection result indicates that the fault is masked, the original data of the electronic control unit is restored by remote flashing to cancel the fault masking; the original data is the data before the fault was masked.

5. A detection device for engine fault shielding, characterized in that, include: The monitoring module is used to monitor the fault diagnosis points corresponding to engine faults in real time when the engine is powered on again after at least one driving cycle. The fault-corresponding parameter acquisition module is used to acquire the fault-corresponding parameters when the fault diagnosis bit is set in response to the fault diagnosis bit being set. A preset bit condition judgment module is used to determine whether the fault-corresponding parameter meets the preset bit condition; The fault masking risk determination module is used to determine whether there is a fault masking risk if the fault-corresponding parameter does not meet the preset bit condition, and to determine whether there is a fault masking risk according to the preset fault indication bit if the fault-corresponding parameter meets the preset bit condition. The fault masking risk determination module is further used for: Check whether the preset fault indicator bit has been set; If the fault indicator bit is not set, it is determined that there is a risk of fault masking. If the fault indicator bit is set, a fault reporting calibration is performed so that the fault-corresponding parameters meet the preset fault reporting conditions. When the fault reporting calibration is completed, read the status of the fault indication bit; If the fault indicator bit is not set, it is determined that there is a risk of fault masking. If the fault indication bit is set, then a cure calibration is performed so that the fault-corresponding parameters meet the preset cure conditions. Once the cure calibration is complete, read the status of the fault indicator bit; If the fault indicator bit is not reset, it is determined that there is a risk of fault masking.

6. An electronic device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the detection method for engine fault masking as described in any one of claims 1-4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program is executed by a processor to implement the engine fault masking detection method as described in any one of claims 1-4.

Images