CN114610570A - Fault storage method and device - Google Patents
Fault storage method and device Download PDFInfo
- Publication number
- CN114610570A CN114610570A CN202210223998.6A CN202210223998A CN114610570A CN 114610570 A CN114610570 A CN 114610570A CN 202210223998 A CN202210223998 A CN 202210223998A CN 114610570 A CN114610570 A CN 114610570A
- Authority
- CN
- China
- Prior art keywords
- fault
- event
- failure
- storage
- events
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Retry When Errors Occur (AREA)
Abstract
The embodiment of the application provides a fault storage method and device, and the method is applied to a controller comprising a plurality of storage spaces. Specifically, in executing the method for fault storage, the controller may first retrieve a first fault event, the first fault event being a fault affecting exhaust emissions of an engine of the vehicle. If each of the plurality of storage spaces stores a failure event, the controller may determine a failure event with a lowest priority from among the plurality of failure events stored in the plurality of storage spaces. This fault event is referred to as a second fault event. The controller stores the first failure event through a storage space in which the second failure event is stored. Therefore, the fault events stored in the storage space of the controller are dynamically adjusted, so that the newly generated fault events have enough storage space to be stored, the output power of the engine is limited in time, and the environment pollution caused by the engine fault is avoided.
Description
Technical Field
The present application relates to the field of vehicle control, and in particular, to a method and an apparatus for fault storage.
Background
Various malfunctions may occur during the operation of the vehicle. Among other things, partial failure may result in increased engine-out pollutants, thereby increasing the environmental impact of the vehicle. For example, if the exhaust aftertreatment system of a vehicle fails, the vehicle may not be able to properly treat the exhaust gas produced by engine combustion, resulting in the untreated exhaust gas being directly released into the atmosphere. The untreated tail gas has more pollutants and serious pollution to the environment.
For this reason, it is possible to start timing after the vehicle has suffered such a malfunction that may have a serious influence on the environment, and to limit the output power of the vehicle engine after the malfunction has continued for a certain time. Thus, by limiting the output of the vehicle engine, the fuel consumption rate of the engine is reduced, and the exhaust gas generated by the engine per unit time is reduced. Thus, even if the above-described malfunction occurs, the environmental pollution by the exhaust gas can be controlled within a reasonable range due to the reduction in the engine emission.
The above method requires that information about the fault is stored in a memory of a control system for controlling the engine. However, the memory space of the memory is limited, and information related to all faults may not be stored, and the output power of the vehicle engine cannot be limited in time.
Disclosure of Invention
In view of this, embodiments of the present application provide a method and an apparatus for fault storage, which aim to flexibly adjust a storage space of a vehicle so that information related to a fault has an available storage space.
In a first aspect, an embodiment of the present application provides a method for fault storage, where the method is applied to a controller, where the controller includes multiple storage spaces, and the method includes:
acquiring a first fault event;
in response to each of the plurality of storage spaces storing a failure event, determining a second failure event from the plurality of failure events stored in the plurality of storage spaces, the second failure event being the lowest priority event of the plurality of failure events;
and storing the first fault event through a storage space corresponding to the second fault event.
In one possible implementation, the determining a second failure event from among the plurality of failure events stored in the plurality of storage spaces includes:
and determining the second fault event from the plurality of fault events according to the storage priority parameter of each fault event in the plurality of fault events, wherein the second fault event is the fault event with the lowest storage priority parameter in the plurality of fault events, and the storage priority parameter represents the priority of the fault time.
In one possible implementation, the determining the second failure event from the plurality of failure events according to the storage priority parameter of each failure event of the plurality of failure events comprises:
determining at least one candidate fault event according to the plurality of fault events, wherein the fault event of which the fault corresponding to the candidate fault event is ended;
determining the second failure event from the at least one candidate failure event based on the storage priority parameter for each of the at least one candidate failure event.
In one possible implementation, the method further comprises:
determining a storage priority parameter of the first fault event according to the fault type corresponding to the first fault event;
in response to the first failure event ending, adjusting a storage priority parameter of the first failure event in accordance with a priority decay parameter. The priority decay parameter is indicative of a time-dependent change in priority of the second fault event.
In one possible implementation, the method further comprises:
acquiring the duration of the first fault event;
determining that the first failure event has occurred again;
in response to the storage priority parameter of the first failure event not being equal to zero, continuing to record the duration of the first failure event based on the duration of the first failure event.
In a second aspect, an embodiment of the present application provides an apparatus for fault storage, where the apparatus is applied to a controller, where the controller includes a plurality of storage spaces, and the apparatus includes:
an acquisition unit configured to acquire a first failure event;
a processing unit, configured to determine, in response to each of the plurality of storage spaces storing a failure event, a second failure event from a plurality of failure events stored in the plurality of storage spaces, where the second failure event is an event with a lowest priority among the plurality of failure events;
the processing unit is further configured to store the first failure event through a storage space corresponding to the second failure event.
In a possible implementation, the processing unit is specifically configured to determine the second failure event from the multiple failure events according to a storage priority parameter of each failure event in the multiple failure events, where the second failure event is a failure event with a lowest storage priority parameter in the multiple failure events, and the storage priority parameter indicates a priority of the failure time.
In a possible implementation, the processing unit is specifically configured to determine at least one candidate fault event according to the multiple fault events, where the fault event that a fault corresponding to the candidate fault event has ended is determined; determining the second failure event from the at least one candidate failure event based on the storage priority parameter for each of the at least one candidate failure event.
In a possible implementation, the processing unit is further configured to determine a storage priority parameter of the first failure event according to a failure type corresponding to the first failure event; in response to the first fault event ending, adjusting a storage priority parameter of the first fault event according to a priority decay parameter. The priority decay parameter is indicative of a time-dependent change in priority of the second fault event.
In a possible implementation, the obtaining unit is further configured to obtain a duration of the first failure event;
the processing unit is further configured to determine that the first failure event occurs again; in response to the storage priority parameter of the first failure event not being equal to zero, continuing to record the duration of the first failure event based on the duration of the first failure event.
In a third aspect, an embodiment of the present application provides an apparatus, which includes a memory and a processor, where the memory is configured to store instructions or codes, and the processor is configured to execute the instructions or codes, so as to cause the apparatus to perform the method for fault storage according to any one of the foregoing first aspects.
In a fourth aspect, an embodiment of the present application provides a computer storage medium, where codes are stored in the computer storage medium, and when the codes are executed, an apparatus that executes the codes implements the fault storage method according to any one of the foregoing first aspects.
In a fifth aspect, embodiments of the present application provide a vehicle, the vehicle includes an engine and a controller, the controller includes a plurality of storage spaces, the storage spaces are used for storing fault events of the engine, and the controller is used for adjusting information stored in the plurality of storage spaces to realize the fault storage method of any one of the first aspect.
The embodiment of the application provides a fault storage method and a fault storage device, wherein the method can be applied to a controller, the controller comprises a plurality of storage spaces, and each storage space in the plurality of storage spaces can be used for storing a fault event of a vehicle. In particular, when executing the method of fault storage, the controller may first retrieve a first fault event, the first fault event being a fault affecting exhaust emissions of the vehicle engine. The controller may then determine whether there is free memory space in the plurality of memory spaces. The controller may store the first failure event and information related to the first failure event in the free memory space if the free memory space exists in the plurality of memory spaces. If each of the plurality of storage spaces stores a failure event, the controller may determine a failure event with a lowest priority from among the plurality of failure events stored in the plurality of storage spaces. This failure event is referred to as a second failure event. Next, the controller stores the first failure event through a storage space in which the second failure event is stored. In this way, if the storage space of the controller is insufficient to store the newly generated first failure event, the controller may select the failure event having the lowest priority from among the failure events already stored as the second failure event, and replace the failure event stored in the storage space storing the second failure event with the first failure event. Therefore, the fault events stored in the storage space of the controller are dynamically adjusted, so that the newly generated fault events have enough storage space to be stored, the output power of the engine can be limited in time, and the environment is prevented from being polluted due to the faults of the engine.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, and obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart of a method of fault storage according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a fault storage apparatus according to an embodiment of the present application.
Detailed Description
The exhaust gas generated by the working of the engine pollutes the environment seriously. To reduce pollution, the emission of pollutants in exhaust gases can now be reduced by various means. For example, the air intake and fuel injection of the engine may be adjusted, or the exhaust gas of the engine may be treated. However, if the vehicle fails, the pollution reduction means may not operate normally, and thus the pollutant emission cannot be effectively reduced, and the environmental pollution cannot be effectively reduced.
In order to solve the above problem, whether a failure occurs may be detected by a sensor. In the embodiments of the present application, the occurrence of a failure is referred to as a failure event. After the fault event is detected, the time duration of the fault event may be recorded. If a fault event persists for more than a first predetermined period of time, the controller may limit the output power of the engine, for example, may limit the maximum output torque of the engine. Thus, by limiting the total amount of exhaust gas produced by the engine, environmental pollution is reduced.
Additionally, after the end of the fault event, the duration of the end of the fault event may be recorded. If the same type of fault as the fault event does not occur again within a second time period after the end of the fault event, the controller may delete the fault event stored in the memory. If the same type of fault as the fault event occurs again within a second time period after the fault event ends, the controller may continue to record the duration of the fault event based on the duration of the last fault event. The duration of the logging fault event and the time at which the logging fault event ends may be referred to as a storage fault event, also referred to as a logging fault event.
For effective emission reduction, the above treatment scheme has been implemented by the motor vehicle pollutant emission standard of the sixth phase of the country (abbreviated as "national six").
However, the controller is generally implemented by an Electronic Control Unit (ECU) of the engine or a vehicle controller. The storage space of both the ECU and the vehicle controller is limited. If a vehicle has multiple faults, the relevant information of the faults can occupy more storage space. After the storage space of the controller is completely occupied, the vehicle has faults needing to be recorded, so that the storage cannot continuously store fault events, the torque of the engine cannot be limited in time, and the emission reduction effect is poor.
In order to more reasonably utilize the storage space of a controller, the embodiment of the application provides a fault storage method and device.
Optionally, the technical solution provided in the embodiment of the present application is applied to a controller, where the controller may be an Electronic Control Unit (ECU) on a vehicle, or may be other devices that have data processing capability and are used for recording a fault on the vehicle. The controller may include a plurality of memory spaces. Each of the plurality of memory spaces may be used to record a failure event. Alternatively, the storage space may be implemented by a memory in the controller, or by a memory connected to the controller. Specifically, the storage may be a memory or a cache.
From the perspective of the controller. A method for storing a fault provided in the embodiment of the present application is described. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the 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.
Referring to fig. 1, fig. 1 is a flowchart of a method of storing a fault according to an embodiment of the present application, including:
s101: a first failure event is obtained.
The controller may detect a vehicle fault condition through sensors and the like. If the controller determines that a fault has occurred, the controller may be said to acquire a fault event. For convenience of illustration, the embodiment of the present application takes the controller acquiring the first failure event as an example.
In the embodiment of the present application, the first failure event may correspond to different failure types. Specifically, the first failure event may be any one of an intake type failure, a fuel type failure, an aftertreatment type failure, and a communication type failure, depending on the device where the failure occurs. Of course, the first failure event may also correspond to other failures that may affect the amount of pollutants emitted from the exhaust of the vehicle's engine.
After acquiring the first failure, the controller may determine whether a free storage space exists in the plurality of storage spaces corresponding to the controller. The free storage space includes storage space where no failure event is recorded. Alternatively, the free storage space may also include a storage space in which a fault event is recorded, but the recorded fault event has ended and the time from the end of the fault event exceeds a second preset event.
And if the plurality of storage spaces corresponding to the controller comprise free storage spaces, the controller stores the first fault event through the free storage spaces. For a specific method for storing the first failure time by the controller, reference may be made to S03, which is not described herein again.
If the plurality of memory spaces corresponding to the controller does not include a free memory space, the controller continues to perform S102 described below.
S102: in response to each of the plurality of storage spaces storing a failure event, a second failure event is determined from a plurality of failure events stored by the plurality of storage spaces.
After determining that the plurality of memory spaces corresponding to the controller do not include free memory spaces, the controller may determine a second failure event from the plurality of failure events stored in the read plurality of memory spaces. The storage space used to store the second failure event is referred to as the target storage space. The second failure event is the failure event with the lowest priority in the plurality of failure events stored in the plurality of storage spaces.
The priority of a fault event may be indicative of the severity of the fault event, particularly the magnitude of the probability that the fault event would cause serious pollution of the environment by the exhaust of the vehicle if the fault event were not recorded. That is, if a fault event is given a higher priority, the duration of the fault event is not recorded, and the more likely the engine of the vehicle is to be contaminated by the fault event. If a fault event is of lower priority, the duration of the fault event is not recorded and the engine of the vehicle is less likely to be environmentally contaminated by the fault event. Therefore, the failure event with the lowest priority among the plurality of failure events is determined as the second failure event, and even if the second failure event is discarded, the vehicle is less likely to cause environmental pollution due to the discarded failure event.
Alternatively, the priority of the fault event may be measured by storing a priority parameter. Specifically, when a certain failure event is stored in the storage space, the controller sets an initial storage priority parameter for the failure event. The controller then maintains the stored priority parameter of the fault event unchanged for the duration of the fault event. After the fault event ends, the controller gradually decreases the storage priority parameter of the fault event. The controller increases the storage priority parameter for the fault event if the fault event corresponding to the type of fault occurs again before the storage priority parameter is decreased to zero. After the storage priority parameter is reduced to zero, the controller discards the fault event.
In some possible implementations, the storage priority parameter may be implemented by a counter. Specifically, a counter may be provided for each of the plurality of memory spaces. The value of the counter represents a storage priority parameter of the fault event stored in the storage space corresponding to the counter.
In some possible implementations, the controller gradually decreases the stored priority parameter of the fault event according to the priority decay parameter. Wherein the priority attenuation parameter represents the time-varying relation of the priority of the fault time. Alternatively, the priority decay parameter may be determined according to the initial storage priority parameter and the second preset time period. That is, if the storage priority parameter of the fault event is equal to the initial storage priority parameter, the storage priority parameter is decreased according to the priority decay parameter, and after a second preset duration, the storage priority parameter of the fault event is equal to zero.
It will be appreciated that the type of fault may be different for different fault events. The initial storage priority parameter and/or the priority decay parameter may be different for fault events of different fault types.
Accordingly, when determining the second failure event, the controller may select, as the second failure event, a failure event having the lowest storage priority parameter from among the plurality of failure events stored in the plurality of storage spaces.
Alternatively, the second failure event may be determined from the failure events that have ended, considering that the failure events stored in the plurality of storage spaces may be included in the failure time of the execution. In particular, the controller may determine at least one candidate fault event from a plurality of fault events based on the status of the fault event. The candidate fault event is a fault event for which the corresponding fault has ended. Next, the controller selects a fault event with the smallest storage priority parameter as a second fault event from the at least one candidate fault event.
S103: and storing the first fault event through a storage space corresponding to the second fault event.
After determining the second failure event, the controller may store the first failure event through a storage space corresponding to the second failure event (i.e., the aforementioned target storage space).
If the second failure event is determined according to the storage priority parameter, the controller may set an initial storage priority parameter for the first failure event after storing the first failure event through the target storage space.
Specifically, the controller may set a storage priority parameter for the first failure event according to a failure type corresponding to the first failure event. For example, if the type of fault corresponding to the first fault event is an aftertreatment-type fault, the output torque of the engine is not limited as soon as possible after the first fault event occurs and the pollution caused by the vehicle may be more severe. Thus, the controller may set the initial storage priority parameter for the first failure event according to the higher storage priority parameter.
If the fault type corresponding to the first fault event is an intake type fault, the vehicle may be relatively free of pollution even if the output torque of the engine is not limited as soon as possible after the first fault event occurs. Thus, the controller may set the initial storage priority parameter for the first failure event according to the lower storage priority parameter.
Accordingly, after the first failure event is ended, the controller gradually decreases the storage priority parameter of the first failure event according to the priority decay parameter of the first failure time. If the fault corresponding to the first fault event occurs again before the storage priority parameter of the first fault event is reduced to 0, the controller continues to record the duration of the first fault event on the basis of the duration of the first fault event.
The embodiment of the application provides a fault storage method which can be applied to a controller, wherein the controller comprises a plurality of storage spaces, and each storage space in the plurality of storage spaces can be used for storing a fault event of a vehicle. Specifically, in executing the method for fault storage, the controller may first retrieve a first fault event, the first fault event being a fault affecting exhaust emissions of an engine of the vehicle. The controller may then determine whether there is free memory space in the plurality of memory spaces. The controller may store the first failure event and information related to the first failure event in the free memory space if the free memory space exists in the plurality of memory spaces. If each of the plurality of storage spaces stores a failure event, the controller may determine a failure event with a lowest priority from among the plurality of failure events stored in the plurality of storage spaces. This fault event is referred to as a second fault event. Next, the controller stores the first failure event through a storage space in which the second failure event is stored. In this way, if the storage space of the controller is insufficient to store the newly generated first failure event, the controller may select the failure event having the lowest priority from among the failure events already stored as the second failure event, and replace the failure event stored in the storage space storing the second failure event with the first failure event. Therefore, the fault events stored in the storage space of the controller are dynamically adjusted, so that the newly generated fault events have enough storage space to be stored, the output power of the engine can be limited in time, and the environmental pollution caused by the engine fault is avoided.
Based on the above specific implementation manners of the method for providing fault storage for the embodiments of the present application, the present application also provides a corresponding apparatus. The device provided by the embodiment of the present application will be described in terms of functional modularity.
Referring to the schematic structural diagram of the fault storage apparatus shown in fig. 2, the apparatus 200 includes an acquisition unit 210 and a control unit 220.
The obtaining unit 210 is configured to obtain a first failure event.
A processing unit 220, configured to determine, in response to each of the plurality of storage spaces storing a failure event, a second failure event from the plurality of failure events stored in the plurality of storage spaces, where the second failure event is an event with a lowest priority among the plurality of failure events.
The processing unit 220 is further configured to store the first failure event through a storage space corresponding to the second failure event.
The embodiment of the application provides a fault storage device, and the method can be applied to a controller, wherein the controller comprises a plurality of storage spaces, and each storage space in the plurality of storage spaces can be used for storing a fault event of a vehicle. In particular, when executing the method of fault storage, the controller may first retrieve a first fault event, the first fault event being a fault affecting exhaust emissions of the vehicle engine. The controller may then determine whether there is free memory space in the plurality of memory spaces. The controller may store the first failure event and information related to the first failure event in the free memory space if the free memory space exists in the plurality of memory spaces. If each of the plurality of storage spaces stores a failure event, the controller may determine a failure event with a lowest priority from among the plurality of failure events stored in the plurality of storage spaces. This failure event is referred to as a second failure event. Next, the controller stores the first failure event through a storage space in which the second failure event is stored. In this way, if the storage space of the controller is insufficient to store the newly generated first failure event, the controller may select the failure event having the lowest priority from among the failure events already stored as the second failure event, and replace the failure event stored in the storage space storing the second failure event with the first failure event. Therefore, the fault events stored in the storage space of the controller are dynamically adjusted, so that the newly generated fault events have enough storage space to be stored, the output power of the engine can be limited in time, and the environment is prevented from being polluted due to the faults of the engine.
Optionally, in some possible implementations, the processing unit 220 is specifically configured to determine, according to a storage priority parameter of each fault event of the multiple fault events, the second fault event from the multiple fault events, where the second fault event is a fault event with a lowest storage priority parameter among the multiple fault events, and the storage priority parameter indicates a priority of the fault time.
Optionally, in some possible implementations, the processing unit 220 is specifically configured to determine at least one candidate fault event according to the multiple fault events, where the fault event that the fault corresponding to the candidate fault event has ended; determining the second failure event from the at least one candidate failure event based on the storage priority parameter for each of the at least one candidate failure event.
Optionally, in some possible implementations, the processing unit 220 is further configured to determine a storage priority parameter of the first failure event according to a failure type corresponding to the first failure event; in response to the first fault event ending, adjusting a storage priority parameter of the first fault event according to a priority decay parameter. The priority decay parameter is indicative of a time-dependent change in priority of the second fault event.
Optionally, in some possible implementations, the obtaining unit 210 is further configured to obtain a duration of the first failure event.
The processing unit 220 is further configured to determine that the first failure event occurs again; in response to the storage priority parameter of the first failure event not being equal to zero, continuing to record the duration of the first failure event based on the duration of the first failure event.
The embodiment of the application also provides corresponding equipment, a computer storage medium and a vehicle, which are used for realizing any fault storage method provided by the embodiment of the application.
Wherein the device comprises a memory for storing instructions or code and a processor for executing the instructions or code to cause the device to perform the method of fault storage according to any of the embodiments of the present application.
The computer storage medium has code stored therein, and when the code is executed, the apparatus for executing the code implements the method for fault storage according to any embodiment of the present application.
A vehicle comprising an engine and a controller, the controller comprising a plurality of memory spaces for storing fault events of the engine, the controller being configured to adjust information stored in the plurality of memory spaces to implement a method of fault storage as described in any embodiment of the present application.
In the embodiments of the present application, the names "first" and "second" (if present) in the names "first" and "second" are used for name identification, and do not represent the first and second in sequence.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only an exemplary embodiment of the present application, and is not intended to limit the scope of the present application.
Claims (10)
1. A method for fault storage, wherein the method is applied to a controller, the controller comprises a plurality of storage spaces, and the method comprises the following steps:
acquiring a first fault event;
in response to each of the plurality of storage spaces storing a failure event, determining a second failure event from the plurality of failure events stored in the plurality of storage spaces, the second failure event being the lowest priority event of the plurality of failure events;
and storing the first fault event through a storage space corresponding to the second fault event.
2. The method of claim 1, wherein determining a second failure event from a plurality of failure events stored in the plurality of storage spaces comprises:
and determining the second fault event from the plurality of fault events according to the storage priority parameter of each fault event in the plurality of fault events, wherein the second fault event is the fault event with the lowest storage priority parameter in the plurality of fault events, and the storage priority parameter represents the priority of the fault time.
3. The method of claim 2, wherein the determining the second fault event from the plurality of fault events based on the storage priority parameter for each of the plurality of fault events comprises:
determining at least one candidate fault event according to the plurality of fault events, wherein the fault event of which the fault corresponding to the candidate fault event is ended;
determining the second failure event from the at least one candidate failure event based on the storage priority parameter for each of the at least one candidate failure event.
4. The method of claim 2, further comprising:
determining a storage priority parameter of the first fault event according to the fault type corresponding to the first fault event;
and responding to the end of the first fault event, and adjusting the storage priority parameter of the first fault event according to a priority attenuation parameter, wherein the priority attenuation parameter represents the change relation of the priority of the second fault event along with time.
5. The method according to any one of claims 2-4, further comprising:
acquiring the duration of the first fault event;
determining that the first failure event has occurred again;
in response to the storage priority parameter of the first failure event not being equal to zero, continuing to record the duration of the first failure event based on the duration of the first failure event.
6. An apparatus for fault storage, the apparatus being applied to a controller, the controller including a plurality of storage spaces, the apparatus comprising:
an acquisition unit configured to acquire a first failure event;
a processing unit, configured to determine, in response to each of the plurality of storage spaces storing a failure event, a second failure event from a plurality of failure events stored in the plurality of storage spaces, where the second failure event is an event with a lowest priority among the plurality of failure events;
the processing unit is further configured to store the first failure event through a storage space corresponding to the second failure event.
7. The apparatus of claim 6,
the processing unit is specifically configured to determine, according to a storage priority parameter of each of the multiple fault events, the second fault event from the multiple fault events, where the second fault event is a fault event with a lowest storage priority parameter among the multiple fault events, and the storage priority parameter indicates a priority of the fault time.
8. The apparatus of claim 7,
the processing unit is specifically configured to determine at least one candidate fault event according to the multiple fault events, where a fault event that a fault corresponding to the candidate fault event has ended is determined; determining the second fault event from the at least one candidate fault event based on the storage priority parameter for each of the at least one candidate fault event.
9. The apparatus of claim 7,
the processing unit is further configured to determine a storage priority parameter of the first fault event according to a fault type corresponding to the first fault event; and responding to the end of the first fault event, and adjusting the storage priority parameter of the first fault event according to a priority attenuation parameter, wherein the priority attenuation parameter represents the change relation of the priority of the second fault event along with time.
10. The apparatus according to any one of claims 6 to 9,
the acquisition unit is further used for acquiring the duration of the first fault event;
the processing unit is further configured to determine that the first failure event occurs again; in response to the storage priority parameter of the first failure event not being equal to zero, continuing to record the duration of the first failure event based on the duration of the first failure event.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210223998.6A CN114610570A (en) | 2022-03-07 | 2022-03-07 | Fault storage method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210223998.6A CN114610570A (en) | 2022-03-07 | 2022-03-07 | Fault storage method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114610570A true CN114610570A (en) | 2022-06-10 |
Family
ID=81860486
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210223998.6A Pending CN114610570A (en) | 2022-03-07 | 2022-03-07 | Fault storage method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114610570A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024017072A1 (en) * | 2022-07-18 | 2024-01-25 | 中国第一汽车股份有限公司 | Vehicle fault information processing method and device, storage medium, and processor |
| CN117572852A (en) * | 2024-01-16 | 2024-02-20 | 中国第一汽车股份有限公司 | Vehicle component fault analysis method, device, equipment, medium and product |
-
2022
- 2022-03-07 CN CN202210223998.6A patent/CN114610570A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024017072A1 (en) * | 2022-07-18 | 2024-01-25 | 中国第一汽车股份有限公司 | Vehicle fault information processing method and device, storage medium, and processor |
| CN117572852A (en) * | 2024-01-16 | 2024-02-20 | 中国第一汽车股份有限公司 | Vehicle component fault analysis method, device, equipment, medium and product |
| CN117572852B (en) * | 2024-01-16 | 2024-05-24 | 中国第一汽车股份有限公司 | Vehicle component fault analysis method, device, equipment, medium and product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114610570A (en) | Fault storage method and device | |
| US9514580B2 (en) | Fault code hierarchy system | |
| DE102006003146B4 (en) | Device and method for reading out a data word and device and method for storing a data block | |
| CN103077095B (en) | Error correction method and device for stored data and computer system | |
| CN113294256B (en) | Control method and device for exhaust gas recirculation control valve, vehicle and medium | |
| CN113513420A (en) | Method and device for treating carbon particles in particle catcher | |
| CN116220870A (en) | Control method and device for vehicle exhaust emission, electronic equipment and storage medium | |
| CN111042901A (en) | Method and device for adjusting diagnosis times of nitrogen oxide conversion efficiency | |
| JP2019039319A (en) | Internal combustion engine drive controller and internal combustion engine drive control method | |
| CN115324696B (en) | Smoke intensity control method and device and vehicle | |
| CN114233471B (en) | High-sulfur oil identification and post-processing method and device and working vehicle | |
| CN113762341B (en) | Calculation method and system for vehicle fault priority | |
| CN110908871A (en) | Data management method, device, equipment and storage medium based on vehicle control unit | |
| CN111327493B (en) | Data acquisition method and device | |
| CN109561083B (en) | Method, device, equipment and storage medium for bypass processing | |
| CN113063607B (en) | Method and system for setting ready state under extreme condition | |
| CN113513421B (en) | Vehicle thermal management control method, device, equipment, medium and product | |
| CN112362194B (en) | Sensor detection method and device | |
| CN110985172B (en) | Method and system for triggering DPF active regeneration | |
| CN114763772B (en) | Method and device for protecting particle catcher | |
| CN116877233A (en) | Control method and device for DPF regeneration, electronic equipment and storage medium | |
| CN113686585B (en) | Vehicle emission monitoring method, device, computer equipment and storage medium | |
| CN115217597B (en) | Secondary air control valve fault diagnosis method, device and system and vehicle | |
| CN116878897A (en) | Engine pedestal test method, system, terminal and storage medium | |
| CN118188224A (en) | Control method and related equipment for liquid attitude control engine spray pipe |
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 |