CN112685424A - Processing method and device for engine fault storage - Google Patents
Processing method and device for engine fault storage Download PDFInfo
- Publication number
- CN112685424A CN112685424A CN202110002821.9A CN202110002821A CN112685424A CN 112685424 A CN112685424 A CN 112685424A CN 202110002821 A CN202110002821 A CN 202110002821A CN 112685424 A CN112685424 A CN 112685424A
- Authority
- CN
- China
- Prior art keywords
- engine
- target fault
- storage
- fault
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02T—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO TRANSPORTATION
- Y02T10/00—Road transport of goods or passengers
- Y02T10/10—Internal combustion engine [ICE] based vehicles
- Y02T10/40—Engine management systems
Abstract
The application provides a processing method and a device for engine fault storage, wherein the method comprises the following steps: the method comprises the steps of obtaining a target fault storage state identification of the engine, wherein the target fault storage state identification is used for indicating whether the identification of the target fault of the engine is successfully stored in a storage device or not, obtaining the current storage state of the identification of the target fault in the storage device, and if the current storage state is determined to be not matched with the identification of the target fault storage state, determining that the target fault storage of the engine is abnormal, and correcting the target fault storage of the engine. Therefore, the correctness of engine fault storage can be guaranteed, and timeliness and accuracy of intelligent diagnosis, maintenance and alarm reminding functions of the engine are effectively guaranteed.
Description
Technical Field
The application relates to the technical field of engines, in particular to a processing method and device for engine fault storage.
Background
The engine is an important device for providing power for the vehicle, and if the engine fails, the normal operation of the vehicle can be directly influenced or the performance of the vehicle can be reduced. The engine fault storage plays a vital role in intelligent diagnosis, maintenance and alarm reminding of the engine. When the engine has a fault, an Electronic Control Unit (ECU) stores a fault code in a memory, and if the storage is successful, a fault storage state flag is set to 1, otherwise, the fault storage state flag is not set. And after the engine fault is cured, if the fault is not reported all the time through multiple driving cycles, deleting the fault code from the memory, and setting the fault storage state identifier to be null.
At present, due to the fact that engine fault storage is abnormal due to misoperation or special abnormal working conditions, timeliness and accuracy of fault diagnosis are affected, and therefore detection of the fault storage is urgently needed.
Disclosure of Invention
The application provides a processing method and device for engine fault storage, which are used for detecting abnormal storage of engine faults.
In a first aspect, the present application provides a method for processing engine fault storage, including:
and acquiring a target fault storage state identifier of the engine, wherein the target fault storage state identifier is used for indicating whether the identifier of the target fault of the engine is successfully stored in a storage device.
A current storage state of an identification of a target failure in a storage device is obtained.
And if the current storage state is determined not to be matched with the target fault storage state identification, determining that the target fault storage of the engine is abnormal.
The target failure storage for the engine is corrected.
Optionally, determining that the current storage state does not match the target failed storage state identifier includes:
if the current storage state indicates that the target fault identification is stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is not successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification; and if the current storage state indicates that the target fault identification is not stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification.
Optionally, correcting the target failure storage of the engine comprises:
if the target fault is occurring, the target fault storage state identification is set to be null, if the storage device stores the identification of the target fault, the identification of the target fault in the storage device is cleared, the identification of the target fault of the engine is obtained again, the identification of the target fault of the engine is stored in the storage device, and the identification of the target fault storage state of the engine is set to be the identification representing the target fault of the engine and successfully stored in the storage device.
Optionally, correcting the target failure storage of the engine comprises:
and if the target fault is detected to be eliminated, setting the current storage state and the target fault storage state identification to be consistent with the current storage state.
Optionally, the identifier of the target fault is a target fault code.
Optionally, when the target fault storage status flag is bit1, the flag indicating the target fault of the engine is successfully stored in the storage device; when the target failure storage state flag is bit0, the flag indicating the target failure of the engine is not successfully stored in the storage device.
In a second aspect, the present application provides a processing apparatus for engine fault storage, comprising:
the first obtaining module is used for obtaining a target fault storage state identifier of the engine, and the target fault storage state identifier is used for indicating whether the identifier of the target fault of the engine is successfully stored in the storage device.
And the second acquisition module is used for acquiring the current storage state of the identifier of the target fault in the storage device.
And the determining module is used for determining that the target fault storage of the engine is abnormal if the current storage state is determined not to be matched with the target fault storage state identification.
A processing module corrects a target failure store of the engine.
Optionally, the determining module is specifically configured to:
if the current storage state indicates that the target fault identification is stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is not successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification; and if the current storage state indicates that the target fault identification is not stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification.
Optionally, the processing module is specifically configured to:
if the target fault is occurring, the target fault storage state identification is set to be null, if the storage device stores the identification of the target fault, the identification of the target fault in the storage device is cleared, the identification of the target fault of the engine is obtained again, the identification of the target fault of the engine is stored in the storage device, and the identification of the target fault storage state of the engine is set to be the identification representing the target fault of the engine and successfully stored in the storage device.
Optionally, the processing module is specifically configured to:
and if the target fault is detected to be eliminated, setting the current storage state and the target fault storage state identification to be consistent with the current storage state.
Optionally, the identifier of the target fault is a target fault code.
Optionally, when the target fault storage status flag is bit1, the flag indicating the target fault of the engine is successfully stored in the storage device; when the target failure storage state flag is bit0, the flag indicating the target failure of the engine is not successfully stored in the storage device.
In a third aspect, the present application provides a processing apparatus for engine fault storage, comprising: a memory and a processor;
the memory is for storing program instructions.
The processor is adapted to invoke program instructions in the memory to perform a method of handling engine fault storage as described in the first aspect of the present application.
In a fourth aspect, the present application provides a computer readable storage medium having stored thereon computer program instructions which, when executed, implement a method of handling engine fault storage as described in the first aspect of the present application.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements a method of handling engine fault storage as described in the first aspect of the present application.
According to the processing method and device for engine fault storage, the target fault storage state identification of the engine is obtained, the target fault storage state identification is used for indicating whether the identification of the target fault of the engine is successfully stored in the storage device, the current storage state of the identification of the target fault in the storage device is obtained, and if the current storage state is determined to be not matched with the identification of the target fault storage state, the target fault storage of the engine is determined to be abnormal, and the target fault storage of the engine is corrected. Due to the fact that the abnormity of the engine fault storage can be detected in real time and corrected, the correctness of the engine fault storage can be guaranteed, and timeliness and accuracy of intelligent diagnosis, maintenance and alarm reminding functions of the engine can be effectively guaranteed.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
FIG. 2 is a flow chart of a method for processing engine fault storage provided by an embodiment of the present application;
FIG. 3 is a flow chart of a method of processing engine fault storage provided in another embodiment of the present application;
FIG. 4 is a schematic structural diagram of a processing device for storing engine faults according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a processing device for storing an engine fault according to another embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The engine fault storage plays a vital role in intelligent diagnosis, maintenance and alarm reminding of the engine. When the engine has a fault, the ECU stores the fault code into the internal memory, if the storage is successful, the fault storage state identifier is set to be 1, otherwise, the fault storage state identifier is not set. And after the engine fault is cured, if the fault is not reported all the time through multiple driving cycles, deleting the fault code from the memory, and setting the fault storage state identifier to be null. At present, due to the fact that engine fault storage is abnormal due to misoperation or special abnormal working conditions, timeliness and accuracy of fault diagnosis are affected, and therefore detection of the fault storage is urgently needed.
Therefore, the method and the device for processing the engine fault storage are provided, the engine fault storage is monitored in real time, the abnormity of the engine fault storage is found in time and corrected, and the correctness of the fault storage is ensured, so that the timeliness and the accuracy of the intelligent diagnosis, maintenance and alarm reminding functions of the engine are effectively ensured. And moreover, related information is recorded for abnormal and corrected conditions, so that related strategies and logics are convenient to follow-up statistical optimization.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application, as shown in fig. 1, when a vehicle 110 runs on a road 120, an engine of the vehicle 110 fails, an ECU of the vehicle 110 stores the engine failure, detects and processes an engine failure storage anomaly in real time, and periodically sends anomaly processing failure information, anomaly processing frequency, and operating condition information when the anomaly occurs to a cloud server 130. The specific implementation process of detecting and handling the storage abnormality of the engine fault can be referred to the scheme of each embodiment described below.
Fig. 2 is a flowchart of a processing method for storing an engine fault according to an embodiment of the present application, where the method of the present embodiment may be applied to a vehicle. As shown in fig. 2, the method of this embodiment may include:
s201, acquiring a target fault storage state identifier of the engine, wherein the target fault storage state identifier is used for indicating whether the identifier of the target fault of the engine is successfully stored in a storage device.
In the present embodiment, the storage device is an internal memory of the ECU. The ECU acquires a target fault storage state identifier of the engine from the memory, and the target fault storage state identifier uses different values to indicate whether the target fault identifier of the engine is successfully stored in the memory of the ECU.
Optionally, the identifier of the target fault is a target fault code.
In this embodiment, for example: if the target failure is an engine coolant temperature excessive failure, the target failure code is represented by GZ01, and when an engine coolant temperature excessive failure occurs, the target failure code GZ01 is stored in the memory of the ECU.
Optionally, when the target fault storage status flag is bit1, the flag indicating the target fault of the engine is successfully stored in the storage device; when the target failure storage state flag is bit0, the flag indicating the target failure of the engine is not successfully stored in the storage device.
In this embodiment, for example: the target fault is an engine coolant temperature over-high fault, and the target fault code is represented by GZ 01. When the engine has the fault, for example, the fault state is represented by GZ01_ st, the fault bit, for example, bit0, of GZ01_ st is set to 1, and the fault code GZ01 is stored in the memory (for example, the fault codes are stored in the array NC _ numGZ [10 ]). If the storage is successful, setting the storage success bit of the GZ01_ st, such as bit1, to 1, namely: the target failure storage state flag is bit1, otherwise it is not set, i.e.: the target failure storage state is identified as bit 0. Therefore, when the target failure storage state flag is bit1, the flag indicating the target failure of the engine is successfully stored in the storage device; when the target failure storage state flag is bit0, the flag indicating the target failure of the engine is not successfully stored in the storage device.
S202, acquiring the current storage state of the identification of the target fault in the storage device.
In this embodiment, the ECU obtains the current storage state of the identifier of the target fault from the memory, where the current storage state of the identifier of the target fault includes that the identifier of the target fault is successfully stored in the memory of the ECU or that the identifier of the target fault is not successfully stored in the memory of the ECU.
S203, if the current storage state is determined not to be matched with the target fault storage state identification, determining that the target fault storage of the engine is abnormal.
In this embodiment, after obtaining the target failure storage state identifier of the engine and the current storage state of the target failure identifier in the storage device, matching the current storage state of the target failure identifier with the target failure storage state identifier, and if it is determined that the current storage state of the target failure identifier is not matched with the target failure storage state identifier, determining that the target failure storage of the engine is abnormal.
And S204, correcting the target failure storage of the engine.
In the present embodiment, after it is determined that the target fail memory of the engine is abnormal, the target fail memory of the engine is corrected. After the target fault storage of the engine is corrected, the correctness of the fault storage of the engine can be ensured, so that the timeliness and the accuracy of intelligent diagnosis, maintenance and alarm reminding functions of the engine are effectively ensured.
It should be noted that the execution sequence of S201 and S202 is not limited.
According to the processing method for the engine fault storage, the target fault storage state identification of the engine is obtained, the target fault storage state identification is used for indicating whether the identification of the target fault of the engine is successfully stored in the storage device, the current storage state of the identification of the target fault in the storage device is obtained, if the current storage state is determined to be not matched with the identification of the target fault storage state, the target fault storage of the engine is determined to be abnormal, and the target fault storage of the engine is corrected. Due to the fact that the abnormity of the engine fault storage can be detected in real time and corrected, the correctness of the engine fault storage can be guaranteed, and timeliness and accuracy of intelligent diagnosis, maintenance and alarm reminding functions of the engine can be effectively guaranteed.
Based on the embodiment shown in fig. 2, in some embodiments, fig. 3 is a flowchart of a processing method for storing an engine fault according to another embodiment of the present application, and as shown in fig. 3, the method of this embodiment may include:
s301, acquiring a target fault storage state identifier of the engine, wherein the target fault storage state identifier is used for indicating whether the identifier of the target fault of the engine is successfully stored in a storage device.
S302, obtaining the current storage state of the target fault identification in the storage device.
In this embodiment, the specific implementation processes of S301 and S302 may refer to the related description of the embodiment shown in fig. 2, and are not described herein again.
And S303, if the current storage state indicates that the target fault identifier is stored in the storage device, and the target fault storage state identifier indicates that the target fault identifier of the engine is not successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identifier.
In this embodiment, for example: the target failure is a failure in which the temperature of the engine coolant is excessively high, the target failure code is represented by GZ01, and all the failure codes of the engine are stored in the array NC _ numGZ [10] in the ECU memory. The ECU determines whether GZ01 was successfully stored in NC _ numGZ [10] and determines that the current storage state does not match the target fail storage state identification if the current storage state is that GZ01 was already stored in NC _ numGZ [10] and the target fail storage state identification is bit 0.
S304, if the current storage state indicates that the target fault identification is not stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification.
In this embodiment, for example: the target failure is a failure in which the temperature of the engine coolant is excessively high, the target failure code is represented by GZ01, and all the failure codes of the engine are stored in the array NC _ numGZ [10] in the ECU memory. The ECU determines whether GZ01 was successfully stored in NC _ numGZ [10], and determines that the current storage state does not match the target fail storage state identification if the current storage state is not storing GZ01 in NC _ numGZ [10] and the target fail storage state identification is bit 1.
S305, if the current storage state is determined not to be matched with the target fault storage state identification, determining that the target fault storage of the engine is abnormal.
In this embodiment, the specific implementation process of S305 may refer to the related description of the embodiment shown in fig. 2, and is not described herein again.
S306, if the target fault happens, setting the target fault storage state identifier to be null, if the storage device stores the identifier of the target fault, clearing the identifier of the target fault in the storage device, reacquiring the identifier of the target fault of the engine, storing the identifier of the target fault of the engine into the storage device, and setting the identifier of the target fault storage state of the engine to represent that the identifier of the target fault of the engine is successfully stored into the storage device.
In this embodiment, for example: the target fault is a fault that the temperature of the engine coolant is excessively high, the target fault code is represented by GZ01, all fault codes of the engine are stored by an array NC _ numGZ [10] in the ECU memory, the fault state is represented by GZ01_ st, the fault bit of GZ01_ st is represented by bit0, and the fault storage state flag of GZ01_ st is represented by bit 1. If the engine is experiencing the fault, the fault storage status flag bit1 of GZ01_ st is set to null, the GZ01_ st status is cleared, and if the flag GZ01 of the target fault is stored in the array NC _ numGZ [10] in the ECU memory, the GZ01 in NC _ numGZ [10] is cleared. The ECU then makes a new determination of the fault GZ01, i.e.: and acquiring GZ01 again, storing GZ01 in an array NC _ numGZ [10] in an ECU memory again, setting a fault bit0 of GZ01_ st to 1, and setting a fault storage state identification bit1 of GZ01_ st to 1. By the mode, the correspondence and consistency of the current storage state of the target fault identification in the storage device and the target fault storage state identification are ensured, and the target fault storage of the engine is normal.
And S307, if the target fault is eliminated, setting the current storage state and the target fault storage state as the same as the current storage state.
In this embodiment, for example: the target fault is a fault that the temperature of the engine coolant is excessively high, the target fault code is represented by GZ01, all fault codes of the engine are stored by an array NC _ numGZ [10] in the ECU memory, the fault state is represented by GZ01_ st, the fault bit of GZ01_ st is represented by bit0, and the fault storage state flag of GZ01_ st is represented by bit 1. If the ECU detects that the target fault is eliminated, the fault storage state identification bit1 of the GZ01_ st is corrected according to whether the GZ01 is stored in the NC _ numGZ [10 ]. Namely: if the GZ01 is already stored in NC _ numGZ [10], the failure storage state identification bit1 of GZ01_ st is set to 1, and if the GZ01 is not stored in NC _ numGZ [10], the failure storage state identification bit1 of GZ01_ st is set to 0.
On the basis of the above embodiment, optionally, the ECU may further record the target failure of the engine to store the relevant information of the abnormality, such as the information of the abnormality failure (e.g., the engine coolant temperature excessive failure), the number of times of abnormality (e.g., 1 time, which is an accumulated value), and the information of the condition when the abnormality occurs (e.g., the engine speed, the coolant temperature, the vehicle speed, the ambient temperature, the ambient pressure, etc.). The ECU inquires abnormal record information periodically (for example, 24 hours, can be calibrated), and if abnormal information exists, the information is sent to the vehicle-mounted terminal through a message, and the vehicle-mounted terminal uploads the abnormal record information to the cloud server. And after collecting the abnormal relevant information, the cloud server gives an alarm in a lighting or other prompting modes. Research personnel can analyze and position the reasons for generation according to the abnormal relevant information, optimize strategies and perfect programs.
According to the processing method for the engine fault storage, the abnormity of the engine fault storage can be detected in real time and corrected, so that the correctness of the engine fault storage can be ensured, and the timeliness and the accuracy of the intelligent diagnosis, maintenance and alarm reminding functions of the engine can be effectively ensured. And in addition, the abnormal fault information, the abnormal times and the working condition information when the abnormality occurs are sent to the cloud server, and alarm reminding is carried out, so that the related strategies and logics can be conveniently calculated and optimized subsequently.
Fig. 4 is a schematic structural diagram of a processing device for storing an engine fault according to an embodiment of the present application, and as shown in fig. 4, the processing device 400 for storing an engine fault according to the present embodiment includes: a first obtaining module 401, a second obtaining module 402, a determining module 403, and a processing module 404.
The first obtaining module 401 is configured to obtain a target failure storage state identifier of the engine, where the target failure storage state identifier is used to indicate whether an identifier of a target failure of the engine is successfully stored in the storage device.
A second obtaining module 402, configured to obtain a current storage status of an identifier of a target failure in a storage device.
A determination module 403 is configured to determine that the target failed storage of the engine is abnormal if it is determined that the current storage status does not match the target failed storage status identification.
The processing module 404 corrects the target failure storage for the engine.
On the basis of any of the embodiments shown above, the determining module 403 is specifically configured to:
if the current storage state indicates that the target fault identification is stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is not successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification; and if the current storage state indicates that the target fault identification is not stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification.
On the basis of any of the embodiments shown above, the processing module 404 is specifically configured to:
if the target fault is occurring, the target fault storage state identification is set to be null, if the storage device stores the identification of the target fault, the identification of the target fault in the storage device is cleared, the identification of the target fault of the engine is obtained again, the identification of the target fault of the engine is stored in the storage device, and the identification of the target fault storage state of the engine is set to be the identification representing the target fault of the engine and successfully stored in the storage device.
On the basis of any of the embodiments shown above, the processing module 404 is specifically configured to:
and if the target fault is detected to be eliminated, setting the current storage state and the target fault storage state identification to be consistent with the current storage state.
On the basis of any of the above-described embodiments, the identification of the target fault is a target fault code.
On the basis of any one of the above-described embodiments, when the target failure storage state flag is bit1, the flag indicating the target failure of the engine is successfully stored in the storage device; when the target failure storage state flag is bit0, the flag indicating the target failure of the engine is not successfully stored in the storage device.
The apparatus of this embodiment may be configured to implement the technical solution of any one of the above-mentioned method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 5 is a schematic structural diagram of a processing device for storing an engine fault according to another embodiment of the present application, and as shown in fig. 5, the processing device 500 for storing an engine fault according to this embodiment includes: a memory 501 and a processor 502. The memory 501 and the processor 502 are connected by a bus.
The memory 501 is used to store program instructions.
The processor 502 is used to invoke the execution of program instructions in memory:
the method comprises the steps of obtaining a target fault storage state identification of the engine, wherein the target fault storage state identification is used for indicating whether the identification of the target fault of the engine is successfully stored in a storage device or not, obtaining the current storage state of the identification of the target fault in the storage device, and if the current storage state is determined to be not matched with the identification of the target fault storage state, determining that the target fault storage of the engine is abnormal, and correcting the target fault storage of the engine.
Based on any of the above embodiments, the processor 502 is specifically configured to:
if the current storage state indicates that the target fault identification is stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is not successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification; and if the current storage state indicates that the target fault identification is not stored in the storage device, and the target fault storage state identification indicates that the target fault identification of the engine is successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification.
Based on any of the above embodiments, the processor 502 is specifically configured to:
if the target fault is occurring, the target fault storage state identification is set to be null, if the storage device stores the identification of the target fault, the identification of the target fault in the storage device is cleared, the identification of the target fault of the engine is obtained again, the identification of the target fault of the engine is stored in the storage device, and the identification of the target fault storage state of the engine is set to be the identification representing the target fault of the engine and successfully stored in the storage device.
Based on any of the above embodiments, the processor 502 is specifically configured to:
and if the target fault is detected to be eliminated, setting the current storage state and the target fault storage state identification to be consistent with the current storage state.
On the basis of any of the above-described embodiments, the identification of the target fault is a target fault code.
On the basis of any one of the above-described embodiments, when the target failure storage state flag is bit1, the flag indicating the target failure of the engine is successfully stored in the storage device; when the target failure storage state flag is bit0, the flag indicating the target failure of the engine is not successfully stored in the storage device.
The apparatus of this embodiment may be configured to implement the technical solution of any one of the above-mentioned method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.
The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements aspects of the method of handling engine fault storage as described above.
The application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer execution instructions, and when the processor executes the computer execution instructions, the scheme of the processing method for storing the engine fault is realized.
The computer-readable storage medium may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. Readable storage media can be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. Of course, the readable storage medium may also be an integral part of the processor. The processor and the readable storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and readable storage medium may also reside as discrete components in the processing device of the engine fault storage.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A method of handling engine fault storage, comprising:
acquiring a target fault storage state identifier of an engine, wherein the target fault storage state identifier is used for indicating whether the identifier of the target fault of the engine is successfully stored in a storage device;
acquiring the current storage state of the identifier of the target fault in the storage device;
if the current storage state is determined not to be matched with the target fault storage state identification, determining that the target fault storage of the engine is abnormal;
correcting a target failure store for the engine.
2. The method of claim 1, wherein said determining that said current storage state does not match said target failed storage state identification comprises:
if the current storage state indicates that the target fault identifier is stored in the storage device, and the target fault storage state identifier indicates that the target fault identifier of the engine is not successfully stored in the storage device, determining that the current storage state does not match the target fault storage state identifier;
and if the current storage state indicates that the target fault identification is not stored in the storage device and the target fault storage state identification indicates that the target fault identification of the engine is successfully stored in the storage device, determining that the current storage state is not matched with the target fault storage state identification.
3. The method of claim 1, wherein said correcting a target fault storage for said engine comprises:
if the target fault happens, the target fault storage state identification is set to be null, if the target fault identification is stored in the storage device, the target fault identification in the storage device is cleared, the target fault identification of the engine is obtained again, the target fault identification of the engine is stored in the storage device, and the target fault storage state identification of the engine is set to indicate that the target fault identification of the engine is successfully stored in the storage device.
4. The method of claim 1, wherein said correcting a target fault storage for said engine comprises:
and if the target fault is detected to be eliminated, setting the current storage state and the target fault storage state to be consistent with the current storage state.
5. The method of claim 1, wherein the identification of the target fault is the target fault code.
6. The method according to any one of claims 1-5, wherein when the target fault storage status flag is bit1, the flag indicating the target fault of the engine is successfully stored in a storage device;
when the target fault storage status flag is bit0, an flag indicating a target fault of the engine is not successfully stored in a storage device.
7. A processing apparatus for engine fault storage, comprising:
the system comprises a first acquisition module, a second acquisition module and a storage module, wherein the first acquisition module is used for acquiring a target fault storage state identifier of an engine, and the target fault storage state identifier is used for indicating whether the identifier of the target fault of the engine is successfully stored in a storage device or not;
a second obtaining module, configured to obtain a current storage state of the identifier of the target fault in the storage device;
the determining module is used for determining that the target fault storage of the engine is abnormal if the current storage state is determined not to be matched with the target fault storage state identification;
a processing module to correct a target failure store of the engine.
8. A processing apparatus for engine fault storage, comprising: a memory and a processor;
the memory is to store program instructions;
the processor is configured to invoke the program instructions in the memory to perform the method of handling engine fault storage according to any of claims 1-6.
9. A computer readable storage medium having computer program instructions stored therein which, when executed, implement a method of handling engine fault storage as claimed in any one of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, carries out the method of handling an engine fault storage according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110002821.9A CN112685424B (en) | 2021-01-04 | 2021-01-04 | Processing method and device for engine fault storage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110002821.9A CN112685424B (en) | 2021-01-04 | 2021-01-04 | Processing method and device for engine fault storage |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112685424A true CN112685424A (en) | 2021-04-20 |
| CN112685424B CN112685424B (en) | 2022-08-23 |
Family
ID=75457079
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110002821.9A Active CN112685424B (en) | 2021-01-04 | 2021-01-04 | Processing method and device for engine fault storage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112685424B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090132117A1 (en) * | 2007-11-15 | 2009-05-21 | Denso Corporation | Vehicular memory management apparatus |
| US20100250061A1 (en) * | 2008-01-15 | 2010-09-30 | Toyota Jidosha Kabushiki Kaisha | Vehicle control device |
| CN106408684A (en) * | 2016-09-30 | 2017-02-15 | 北京新能源汽车股份有限公司 | Fault information storage method and device |
| US20170053710A1 (en) * | 2013-12-18 | 2017-02-23 | Freescale Semiconductor, Inc. | Storage element with storage and clock tree monitoring circuit and methods therefor |
| CN107128312A (en) * | 2017-05-27 | 2017-09-05 | 奇瑞汽车股份有限公司 | Hybrid vehicle fault diagnosis management system and method |
| CN110781146A (en) * | 2019-10-28 | 2020-02-11 | 宁波三星智能电气有限公司 | Event storage method, power terminal and computer-readable storage medium |
| CN111596638A (en) * | 2019-02-20 | 2020-08-28 | 南京天擎汽车电子有限公司 | Vehicle troubleshooting method, device, equipment and computer readable storage medium |
| CN112026787A (en) * | 2020-07-28 | 2020-12-04 | 北汽福田汽车股份有限公司 | Fault information processing method, device, vehicle and storage medium |
-
2021
- 2021-01-04 CN CN202110002821.9A patent/CN112685424B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090132117A1 (en) * | 2007-11-15 | 2009-05-21 | Denso Corporation | Vehicular memory management apparatus |
| US20100250061A1 (en) * | 2008-01-15 | 2010-09-30 | Toyota Jidosha Kabushiki Kaisha | Vehicle control device |
| US20170053710A1 (en) * | 2013-12-18 | 2017-02-23 | Freescale Semiconductor, Inc. | Storage element with storage and clock tree monitoring circuit and methods therefor |
| CN106408684A (en) * | 2016-09-30 | 2017-02-15 | 北京新能源汽车股份有限公司 | Fault information storage method and device |
| CN107128312A (en) * | 2017-05-27 | 2017-09-05 | 奇瑞汽车股份有限公司 | Hybrid vehicle fault diagnosis management system and method |
| CN111596638A (en) * | 2019-02-20 | 2020-08-28 | 南京天擎汽车电子有限公司 | Vehicle troubleshooting method, device, equipment and computer readable storage medium |
| CN110781146A (en) * | 2019-10-28 | 2020-02-11 | 宁波三星智能电气有限公司 | Event storage method, power terminal and computer-readable storage medium |
| CN112026787A (en) * | 2020-07-28 | 2020-12-04 | 北汽福田汽车股份有限公司 | Fault information processing method, device, vehicle and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112685424B (en) | 2022-08-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101744226B1 (en) | System and method for providing diagnostic fault information | |
| US20090313505A1 (en) | System and method for detecting combinations of perfomance indicators associated with a root cause | |
| CN106682162B (en) | Log management method and device | |
| CN112255552B (en) | Fault diagnosis method and device for temperature acquisition device of fuel cell and vehicle | |
| CN110888763A (en) | Disk fault diagnosis method and device, terminal equipment and computer storage medium | |
| CN113586239B (en) | Engine fault diagnosis method, engine fault diagnosis device, controller and storage medium | |
| CN111966518A (en) | Fault data recording method, system, automobile and storage medium | |
| CN113672415A (en) | Disk fault processing method, device, equipment and storage medium | |
| CN114563995B (en) | Reset detection method, device, equipment and storage medium of electronic control unit | |
| CN112416670A (en) | Hard disk test method, device, server and storage medium | |
| CN112685424B (en) | Processing method and device for engine fault storage | |
| CN111736579B (en) | Industrial control equipment safety detection method based on log inquiry and retention | |
| CN109254898B (en) | Software module execution sequence monitoring method and system | |
| CN113625957B (en) | Method, device and equipment for detecting hard disk faults | |
| CN111290365A (en) | Servo system monitoring method and device, computer equipment and storage medium | |
| CN115980585A (en) | Battery fault detection method and device, computer equipment and storage medium | |
| CN110987448B (en) | Engine air inlet state monitoring method, device and equipment | |
| CN112446980B (en) | Enhanced component fault diagnosis method for providing minimum probability fault | |
| CN114083987A (en) | Battery monitoring parameter correction method and device and computer equipment | |
| US9092315B2 (en) | Method and software program product for determining the quality of an information technology system | |
| CN113467984B (en) | Method, device, computer equipment and storage medium for diagnosing faults of aircraft system | |
| CN111445598A (en) | Optical fiber attitude and heading reference system information processing method, device, equipment and storage medium | |
| CN116345690B (en) | Power monitoring false alarm identification method and system based on power supply system equipment list | |
| CN112988506B (en) | Big data server node performance monitoring method and system | |
| CN113986142B (en) | Disk fault monitoring method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |