WO2023071961A1

WO2023071961A1 - Fault code storage method and apparatus, and device and storage medium

Info

Publication number: WO2023071961A1
Application number: PCT/CN2022/126907
Authority: WO
Inventors: 王宏民; 张晓谦; 李岩; 刘奇; 张天园
Original assignee: 中国第一汽车股份有限公司
Priority date: 2021-10-26
Filing date: 2022-10-24
Publication date: 2023-05-04
Also published as: CN113934898A

Abstract

Disclosed in the embodiments of the present application are a fault code storage method and apparatus, and a device and a storage medium. The method comprises: acquiring an enable fault code of an enable state in a memory according to a fault code table; acquiring, from the enable fault code and according to a preset condition, a fault code to be stored; if a fault corresponding to said fault code is a permanent fault, storing, in a permanent fault code storage area, said fault code that meets a permanent fault code storage condition; and if the fault corresponding to said fault code is a non-permanent fault, storing, in a non-permanent fault code storage area, said fault code that meets a non-permanent fault code storage condition.

Description

Fault code storage method, device, equipment and storage medium

This disclosure claims priority to a Chinese patent application with application number 202111248008.6 filed with the China Patent Office on October 26, 2021, the entire contents of which are incorporated herein by reference.

technical field

The embodiments of the present application relate to the technical field of electronic control, for example, to a fault code storage method, device, device, and storage medium.

Background technique

The fault code refers to the data stored in the storage element after the vehicle controller recognizes the fault. In the face of more and more driving vehicles on the road, in order to ensure vehicle driving and road safety, Chinese regulations have stricter requirements for the elimination of fault codes to prevent faulty vehicles from driving dangerously on the road.

The non-permanent fault codes in the past can be deleted at any time, and the fault codes that have been self-healed will not occupy storage space. According to Chinese laws and regulations (for example: National Phase VI Motor Vehicle Pollutant Emission Standards), there is a category of permanent fault codes. This type of fault code cannot be deleted by the diagnostic instrument. After the fault occurs and stored, it needs to be warmed up by the OEM It will be automatically deleted after the number of engine cycles (for example, if a fault does not appear again after at least 40 engine warm-up cycles, the fault code can be automatically cleared). Since the fault codes that can be stored in the storage element are limited, once the permanent faults are fully stored, new faults that occur later cannot be stored in the storage element. In this way, when the vehicle is being maintained and developed and tested, the existing faults of many vehicles cannot be obtained by querying the fault code, which seriously affects the maintenance quality and development efficiency.

Contents of the invention

The embodiment of the present application provides a fault code storage method, device, equipment, and storage medium, so as to realize that there is no need to re-flash the on-board controller during the research and development process, thereby improving test efficiency, reducing missed detection and identification of faults, and ensuring Vehicle maintenance quality and driving safety, while saving hardware costs, and easy to achieve large-scale upgrades to mass-produced vehicles.

In the first aspect, the embodiment of the present application provides a fault code storage method, the method comprising:

According to the fault code table, obtain the enabled fault codes in the enabled state in the memory;

Acquiring the fault codes to be stored from the enabled fault codes according to preset conditions;

In the case that the fault corresponding to the fault code to be stored is a permanent fault, the fault code to be stored that meets the storage condition of the permanent fault code is stored in the permanent fault code storage area;

In the case that the fault corresponding to the fault code to be stored is a non-permanent fault, the fault code to be stored that meets the non-permanent fault code storage condition is stored in the non-permanent fault code storage area.

In the second aspect, the embodiment of the present application also provides a fault code storage device, which includes:

The fault code acquisition module is set to obtain the enabled fault codes in the enabled state in the memory according to the fault code table;

The fault code screening module is configured to acquire fault codes to be stored from the enabled fault codes according to preset conditions;

The first fault code storage module is configured to store the fault codes to be stored that meet the permanent fault code storage conditions into the permanent fault code storage area when the fault corresponding to the fault code to be stored is a permanent fault;

The second fault code storage module is configured to store the fault codes to be stored that meet the non-permanent fault code storage conditions into the non-permanent fault code storage when the fault corresponding to the fault code to be stored is a non-permanent fault district.

In the third aspect, the embodiment of the present application also provides a fault code storage device, the fault code storage device includes:

processor;

a storage device configured to store a program;

When the program is executed by the processor, the processor implements any of the fault code storage methods in the first aspect.

In a fourth aspect, the embodiment of the present application also provides a computer storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the fault code storage method described in any of the first aspects is implemented.

Description of drawings

FIG. 1 is a flow chart of a fault code storage method provided in Embodiment 1 of the present application;

Fig. 2 is a flowchart of a fault code storage method provided in Embodiment 2 of the present application;

Fig. 3 is a structural block diagram of a fault code storage device provided in Embodiment 3 of the present application;

FIG. 4 is a schematic structural diagram of a fault code storage device provided in Embodiment 4 of the present application.

Detailed ways

The application will be described below in conjunction with the accompanying drawings and embodiments. It should be understood that the embodiments described here are only used to explain the present application. In addition, it should be noted that, for the convenience of description, only some structures related to the present application are shown in the drawings but not all structures.

Embodiment one

The present application provides a fault code storage method, and the fault code storage method may be a fault code classification storage method.

Fig. 1 is a flow chart of a method for storing fault codes provided by Embodiment 1 of the present application. This embodiment is applicable to situations where fault codes are stored when the vehicle is running on the road and fault records need to be recorded. This method It can be executed by the fault code storage device provided in the embodiment of the present application, and the device can be realized by software and/or hardware. The device may be configured in a vehicle controller, and the method may include:

S110. Obtain the enabled fault codes in the enabled state in the memory according to the fault code table.

The fault code table is the data pre-set in the vehicle controller (Electronic Control Unit, ECU), which stores the fault types and fault types of all possible faults. The fault type is determined according to the hardware equipment of the vehicle or the ECU, including permanent fault codes and non-permanent fault codes. Different fault classes are set for the same control target, and each control target may have multiple fault causes, so each control target corresponds to multiple different fault classes. The fault code can be understood as the coded information generated by the ECU for the fault when the control target fails.

In one embodiment, the ECU checks whether all the fault codes in the fault code list are currently enabled and whether reporting is allowed under the current working condition, to determine whether the fault codes are enabled or disabled. Optionally, enabled DTCs refer to DTCs that are allowed to be reported under the current working conditions of the vehicle, that is, DTCs that are enabled; correspondingly, non-enabled DTCs refer to DTCs that are not The fault codes that are allowed to be reported, that is, the fault codes that are not enabled. Non-enabled fault codes do not perform follow-up processing, and enabled fault codes perform subsequent S120 operations.

Exemplary: When the vehicle is in the parking state, if the vehicle detects a coolant overheating fault at this time, since the coolant overheating in the parking state is an irrelevant fault, under this working condition, the fault code corresponding to the coolant overheating fault will be It is judged as non-enabled state. Conversely, if a failure of the electronic handbrake is detected, which may cause the vehicle to be unable to enter or remain in the parking state, the fault code corresponding to the electronic handbrake failure is determined to be in the enabled state under the working condition of the parking state. By obtaining the current working condition of the vehicle, it is judged whether a fault is allowed to be reported under the current working condition, that is, the pre-screening of the fault code reduces the working pressure of the ECU, improves the processing efficiency of the fault code, and reduces the storage of the storage unit. pressure.

S120. Obtain a fault code to be stored from the enabled fault codes according to a preset condition.

The preset condition is a condition pre-selected and set in the ECU to filter the enabled fault codes, and the enabled fault codes are screened through the preset conditions to obtain the fault codes qualified for storage.

Optionally, the preset conditions include at least one of the following: the permanent fault code storage area and the non-permanent code storage area do not store the enabled fault code, the enabled fault code corresponds to a fault occurrence, the The fault confirmation level corresponding to the enabled fault code meets the preset standard, the fault type corresponding to the enabled fault code is non-zero, and the creation of fault storage is allowed. If the preset condition is met, the enabled fault code is determined as the The fault code is to be stored.

In order to save the storage space of the storage unit, for the fault codes stored in the storage unit, when the corresponding fault occurs again, even if it is detected that it is an enabled fault code, it will not be stored. In order to avoid the wrong or inaccurate use of DTCs caused by the vehicle system, it is necessary to check the occurrence of the fault corresponding to the enabled DTC again, so as to prevent the enabled DTC from being wrongly read and stored when the fault does not actually occur. to the storage unit. For different models (such as conventional A-class, B-class, C-class, D-class or compact, sports utility vehicle (Sport Utility Vehicle, SUV), large party vehicle (Massive Party Vehicle, MPV), etc.), its fault confirmation Level standards are inconsistent. For example, for the fault that the atmospheric pressure sensor cannot read the signal, as long as the conventional A-class car does not read the signal for 1 second, it is judged to be a fault, while the standard of the B-class car may be 0.5 seconds (s), C-class car The car is 0.3s, and the D-class car is 0.1s. For a control target, such as the atmospheric pressure sensor, the current vehicle only sets three fault categories: data abnormality, data instability, and data cannot be obtained. However, if the fault type reported by the detection fault code is poor contact of the atmospheric pressure sensor, The poor contact of the sensor is not one of the three preset fault types. At this time, the fault type of the poor contact of the atmospheric pressure sensor is set to zero and will not be stored to avoid errors caused by the original factory error or subsequent modification of the vehicle. The set fault categories are stored in the storage unit, which wastes the storage space of the storage unit and the maintenance effort of the staff. Fault storage creation permission refers to the working state that the storage unit is allowed to write data from the software, and the ECU of the vehicle on the hardware is always in a state of maintaining a complete path connection with the storage unit. The vehicle should also have sufficient resources (such as power, memory space) , operation thread, etc.) to execute the complete writing process of the fault code data.

S130. In the case that the fault corresponding to the fault code to be stored is a permanent fault, store the fault code to be stored that meets the permanent fault code storage condition into a permanent fault code storage area.

A permanent fault, also known as a permanent fault, is a fault that occurs and persists until it is removed or repaired. That is to say, a permanent fault is a fault that affects the operation of the equipment, and the normal operation of the equipment cannot be restored without taking measures.

The permanent fault code storage condition is used to judge whether the permanent fault code corresponding to the current confirmed permanent fault is allowed to be stored in the permanent fault code storage area.

For example, after the ECU obtains the fault codes to be stored, it compares the fault codes to be stored with the contents recorded in the fault code table, and when the fault codes corresponding to the fault codes to be stored are permanent faults and satisfy the When storing conditions, store the fault codes to be stored in the permanent fault code storage area.

Optionally, the permanent fault code storage condition includes: the permanent fault code storage area is not fully used. On the basis of screening the types of fault codes to be stored, it is judged whether the permanent fault code storage area can continue to store fault codes, which ensures the effective storage of fault information and avoids the resource waste of repeated attempts to write after the storage area is full. An exception occurred with the written data.

In an embodiment, if the fault corresponding to the fault code to be stored is a permanent fault, if the fault code to be stored does not meet the storage conditions of the permanent fault code, the fault code to be stored will not be saved.

S140. In the case that the fault corresponding to the fault code to be stored is a non-permanent fault, store the fault code to be stored that meets the non-permanent fault code storage condition into a non-permanent fault code storage area.

Non-permanent faults are non-permanent faults, including intermittent faults and transient faults. Intermittent failures are failures that occur repeatedly and then disappear. Intermittent failures can occur when a component is on the verge of failure or, for example, due to switching surges (transient drastic changes in voltage). A transient fault is one that occurs once and then disappears.

The non-permanent fault code storage condition is used to judge whether the permanent fault code corresponding to the non-permanent fault code that has been confirmed as non-permanent fault is allowed to be stored in the non-permanent fault code storage area.

In one embodiment, when the fault corresponding to the fault code to be stored is a non-permanent fault, if the fault code to be stored does not meet the non-permanent fault code storage conditions, the fault code to be stored will not be saved.

For example, after the ECU obtains the fault code to be stored, it compares the fault code to be stored with the content recorded in the fault code table, and when the fault code corresponding to the fault code to be stored is a non-permanent fault and satisfies the non-permanent When the fault code storage condition is met, the fault code to be stored is stored in a non-permanent fault code storage area.

Optionally, the non-permanent fault code storage conditions include: all the non-permanent fault code storage areas are not used, and the fault priority of the fault codes to be stored is higher than that of the stored fault codes. The fault priority of the fault code to be stored is preset according to the fault degree, and is stored in the fault code table together with the fault type of the fault code.

Exemplarily, when the control target is an atmospheric pressure sensor, determine the fault of the atmospheric pressure sensor, and set a fault code for each fault: for example, the fault code of a bad signal of the atmospheric pressure sensor is P0001, and the signal of the atmospheric pressure sensor is not The stable fault code is P0005, and the fault code that cannot read the atmospheric pressure sensor signal is P0010, and the priority can be set as P0010>P0005>P0001. When the vehicle has already stored the signal and cannot read the corresponding fault code P0010, because the fault is more serious, the staff will debug and maintain the atmospheric pressure sensor. Therefore, even if a poor signal fault with a lesser fault degree is subsequently detected, since P0010 with a higher priority has been stored, it is not necessary to store the fault code P0001 again, so the fault code P0001 will not be stored. On the contrary, if the fault type detected at the beginning is a bad signal, and the fault code is stored as P0001, if P0010 with a higher priority is detected later, it means that there is a more serious fault in the atmospheric pressure sensing system at this time, and the fault code is stored as P0001. P0010 will be stored. By pre-setting the fault priority of fault codes according to the fault degree, and storing fault codes in order of priority, avoiding storage of unimportant fault codes in the storage area, saving a large amount of non-permanent code storage space, and improving fault detection Code storage efficiency and effectiveness.

In the technical solution of this embodiment, the enabled fault codes in the enabled state in the memory are obtained according to the fault code table; the fault codes to be stored are obtained from the enabled fault codes according to preset conditions; If the fault is a permanent fault, store the fault code to be stored that meets the storage conditions of the permanent fault code into the permanent fault code storage area; if the fault corresponding to the fault code to be stored is a non-permanent fault, store the The fault codes to be stored that meet the non-permanent fault code storage conditions are stored in the non-permanent fault code storage area. It realizes that there is no need to re-flash the on-board controller during the research and development process, thereby improving the test efficiency, reducing the missed detection and identification of faults, ensuring the quality of vehicle maintenance and driving safety, and saving hardware costs. Massive upgrades for production vehicles.

On the basis of the above technical solution, optionally, the storage area of the storage device is at least divided into the permanent fault code storage area and the non-permanent fault code storage area according to the preprocessing instruction.

In one embodiment, unlike the current method of directly calling the interface provided by the hardware manufacturer, inputting the starting address pointer of the stored data and the size of the memory space occupied by the data to adjust the partition, the embodiment of the present application uses a preprocessing instruction to store The storage space in the component is divided into permanent fault code storage area and non-permanent fault code storage area.

Exemplarily, the embodiment of the present application sets the address of the permanent fault code storage area to 0x0000-0x4000, the address of the non-permanent fault code area to 0x4000-0x8000, and permanently stores the permanent fault code in the permanent fault code storage area through '#program', Non-permanent fault codes are permanently stored in the non-permanent fault code storage area. The storage components are partitioned by software. When storing fault codes, the permanent fault code storage area and the non-permanent fault code storage area are completely independent and do not interfere with each other. The permanent fault will not occupy the non-permanent fault storage space.

Embodiment two

This application provides a fault code storage method, the fault code storage method can be a fault code classification storage method

Figure 2 is a flow chart of a fault code storage method provided by Embodiment 2 of the present application. On the basis of the above embodiment, this embodiment explains the acquisition of enabled fault codes in the enabled state in memory according to the fault code table . Referring to Figure 2, the method may include:

S210. Detect the memory data at a preset time interval, and judge whether the memory data is valid; based on the judgment result that the memory data is abnormal, judge that the memory data is invalid, and restart the operating system.

The preset time interval is preset in the vehicle ECU system, for example, it may be a time interval of 10 milliseconds (ms) or other time lengths. This application takes the interval length of 10 ms as an example to make a statement, and does not make a statement for other time intervals temporarily.

Exemplarily, the fault code storage module (Dsm_mainfunction) is first set into the operating system of the ECU, and then the Dsm_mainfunction is executed every 10ms. Every time Dsm_mainfunction is executed, the data in the memory is first detected to determine whether the current memory data is valid, and if the current memory data is invalid, the operating system is restarted; if the current memory data is valid, there is no need to restart the operating system. Even after it is determined that the current data is valid, the current internal memory data is still continuously detected at a preset time interval, and if the internal memory data is detected to be invalid again, the above-mentioned process will continue to be repeatedly executed. Through the continuous detection of the memory data, the validity of the memory data is guaranteed, and the accurate acquisition and judgment of the fault codes in the enabled state is ensured, and the vehicle's ability to identify and store faults is improved.

Optionally, judge whether the current memory data is valid by detecting whether there is abnormal data in the current memory: based on the judgment result of detecting abnormal data, it is judged that the current memory data is invalid, based on the judgment result of detecting that there is no abnormal data in the current memory data , to determine that the current content data is valid. For example, whether the current memory data is abnormal can be judged by the size of the data.

S220. Initialize the diagnosis system, and judge whether the initialization of the diagnosis system is successful; based on the judgment result that the initialization of the diagnosis system is not successful, initialize the diagnosis system again.

The diagnostic system can be a setting program used to detect the status of vehicle components in the system, or it can be a device installed in the vehicle that is connected to the vehicle components and sends the status of each component to the ECU, or a combination of the above software and the above hardware Realize the diagnosis function.

Exemplarily, after it is determined that the current vehicle memory data is valid, initialize the diagnostic system of the vehicle, and judge whether the diagnostic system is initialized successfully. If the current diagnostic system is successfully initialized, it means that the current vehicle memory and the diagnostic system can operate normally. An environment for detecting vehicle faults and storing fault codes. If the initialization of the diagnostic system fails, it means that the current diagnostic system cannot operate in its original state, and there may be faults diagnosed before in the diagnostic system. At this time, the fault data given by the diagnostic system may be the historical fault data that has been reported before; at the same time, Failure to initialize will also lead to the accumulation of too much useless data in the diagnostic system, which will affect the reading and writing of subsequent data and the operating speed of the diagnostic system. Therefore, after the initialization of the diagnostic system fails, the initialization process is performed again until the current diagnostic system is initialized successfully, so as to ensure that the diagnostic system is in the initialization state when performing vehicle fault diagnosis, and will not be affected by the data of the previous diagnostic cycle, improving the operation of the diagnostic system speed and diagnostic stability.

S230. Obtain the enabled fault codes in the enabled state in the memory according to the fault code table.

S240. Obtain the fault codes to be stored from the enabled fault codes according to preset conditions.

S250. In the case that the fault corresponding to the fault code to be stored is a permanent fault, store the fault code to be stored that meets the permanent fault code storage condition into a permanent fault code storage area.

S260. In the case that the fault corresponding to the fault code to be stored is a non-permanent fault, store the fault code to be stored that meets the non-permanent fault code storage condition into a non-permanent fault code storage area.

The technical solution of this embodiment realizes the classification and storage of fault codes, and realizes that there is no need to re-flash the on-board controller during the research and development process, thereby improving test efficiency, reducing missed detection and identification of faults, and ensuring vehicle maintenance. Quality and driving safety, while saving hardware costs. On the basis of easy realization of large-scale upgrades to mass-produced vehicles, the validity of memory and fault data is guaranteed by checking whether the memory data is valid and whether the diagnostic system is initialized successfully. Improve the operating speed and diagnostic stability of the diagnostic system.

Embodiment three

The present application provides a fault code storage device, and the fault code storage method may be a fault code classification storage device.

Fig. 3 is a structural block diagram of a fault code storage device provided in Embodiment 3 of the present application. The device can execute the fault code storage method provided in any embodiment of the present application, and has corresponding functional modules and beneficial effects for executing the method. As shown in Figure 3, the device may include:

The fault code acquisition module 310 is configured to obtain the enabled fault codes in the enabled state in the memory according to the fault code table;

The fault code screening module 320 is configured to acquire fault codes to be stored from the enabled fault codes according to preset conditions;

The first fault code storage module 330 is configured to store the fault codes to be stored that meet the permanent fault code storage conditions into the permanent fault code storage area when the fault corresponding to the fault code to be stored is a permanent fault;

The second fault code storage module 340 is configured to store the fault code to be stored that meets the non-permanent fault code storage condition into the non-permanent fault code when the fault corresponding to the fault code to be stored is a non-permanent fault storage area.

Optionally, the fault code storage device may also include a memory data monitoring module 350:

The memory data monitoring module 350 is configured to initialize the diagnostic system, judge whether the diagnostic system is initialized successfully, and re-initialize the diagnostic system based on the judgment result that the diagnostic system initialization is not successful.

Optionally, the fault code storage device may also include a diagnostic system initialization module 360:

The diagnostic system initialization module 360 is configured to detect the memory data at a preset time interval, and judge whether the memory data is valid; based on the judgment result that the memory data is abnormal, judge that the memory data is invalid, and restart the operation system.

Optionally, the fault code screening module 320 is configured to obtain fault codes to be stored from the enabled fault codes according to preset conditions in the following manner: based on the permanent fault code storage area and the non-permanent code storage The enabled fault code is not stored in the zone, the enabled fault code corresponds to a fault occurrence, the fault confirmation level corresponding to the enabled fault code meets the preset standard, the enabled fault code corresponds to a non-zero fault type, and fault storage is created If the judgment result is allowed, the enabled fault code is determined as the fault code to be stored.

Optionally, the storage area of the storage device is at least divided into the permanent fault code storage area and the non-permanent fault code storage area according to the preprocessing instruction.

Optionally, the permanent fault code storage condition includes: the permanent fault code storage area is not fully used; the non-permanent fault code storage condition includes: the non-permanent fault code storage area is not fully used, and all The fault priority of the fault codes to be stored is higher than that of the stored fault codes.

Optionally, the storage content of the fault code table includes the fault type and fault priority of the fault codes to be stored; the fault priority of the fault codes to be stored is preset according to the fault degree.

The fault code storage device provided by the embodiment of the present application obtains the enabled fault codes in the enabled state in the memory according to the fault code table; obtains the fault codes to be stored from the enabled fault codes according to preset conditions; When the fault corresponding to the stored fault code is a permanent fault, store the fault code to be stored that meets the storage conditions of the permanent fault code into the permanent fault code storage area; if the fault corresponding to the fault code to be stored is a non-permanent fault In this case, the fault codes to be stored that meet the non-permanent fault code storage conditions are stored in the non-permanent fault code storage area. It realizes that there is no need to re-flash the on-board controller during the research and development process, thereby improving the test efficiency, reducing the missed detection and identification of faults, ensuring the quality of vehicle maintenance and driving safety, and saving hardware costs. Massive upgrades for production vehicles.

Embodiment four

The present application provides a fault code storage device, which may be a fault code classification storage device.

Fig. 4 is a schematic structural diagram of a fault code storage device provided in Embodiment 4 of the present application. As shown in Fig. 4, the fault classification device includes a processor 40, a memory 41, an input device 42 and an output device 43; The number of processors 40 can be one or more, and one processor 40 is taken as an example in FIG. Take connection via bus as an example.

Memory 41, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs and modules, such as program instructions/modules corresponding to the fault code storage method in the embodiment of the present application (for example, a fault code acquisition module 310, the fault code screening module 320, the first fault code storage module 330 and the second fault code storage module 340). The processor 40 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 41 , that is, realizes the above-mentioned fault code storage method.

The memory 41 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the terminal, and the like. In addition, the memory 41 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices. In some examples, memory 41 may include memory located remotely from processor 40, and such remote memory may be connected to the device via a network. Examples of such networks include the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 42 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the device. The output device 43 may include a display device such as a display screen.

Embodiment five

Embodiment 5 of the present application also provides a storage medium containing computer-executable instructions, the computer-executable instructions are used to execute a fault code storage method when executed by a computer processor, the method comprising:

In the case that the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored that meets the storage condition of the permanent fault code into the permanent fault code storage area;

Of course, a storage medium containing computer-executable instructions provided in the embodiments of the present application, the computer-executable instructions are not limited to the method operations described above, and can also execute the fault code storage method provided in any embodiment of the present application. related operations.

Through the above description about the implementation, those skilled in the art can clearly understand that the present application can be realized by means of software and necessary general-purpose hardware, and of course it can also be realized by hardware, but in many cases the former is a better implementation . Based on this understanding, the essence of the technical solution of this application or the part that contributes to related technologies can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as computer floppy disks, Read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), flash memory (FLASH), hard disk or optical disc, etc., including at least one instruction to make a computer device (which can be a personal computer) , server, or network device, etc.) execute the method described in each embodiment of the present application.

For the beneficial effects of the device, program, and storage medium of the embodiment of the present application, reference may be made to the analysis of the beneficial effects of the above fault code storage method, and details will not be repeated this time.

It is worth noting that in the above-mentioned embodiment of the fault code storage device, the units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be realized; in addition, each The names of the functional units are also only for the convenience of distinguishing each other.

Claims

A fault code storage method, comprising:

According to the fault code table, obtain the enabled fault codes in the enabled state in the memory;

Acquiring the fault codes to be stored from the enabled fault codes according to preset conditions;

In the case that the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored that meets the storage condition of the permanent fault code into the permanent fault code storage area;

In the case that the fault corresponding to the fault code to be stored is a non-permanent fault, the fault code to be stored that meets the non-permanent fault code storage condition is stored in the non-permanent fault code storage area.
According to the fault code storage method according to claim 1, before obtaining the enabled fault codes in the enabled state in the memory according to the fault code table, the method also includes:

Initialize the diagnostic system, and determine whether the diagnostic system is initialized successfully;

The diagnostic system is re-initialized based on a judgment result that the initialization of the diagnostic system is not successful.
According to the fault code storage method according to claim 2, before initializing the diagnostic system and judging whether the diagnostic system is initialized successfully, the method further includes:

Detecting the memory data at preset time intervals to determine whether the memory data is valid;

Based on the judgment result that the memory data is abnormal, it is determined that the memory data is invalid, and the operating system is restarted.
The fault code storage method according to claim 1, wherein said acquiring fault codes to be stored from said enabled fault codes according to preset conditions comprises:

Based on the fact that the permanent fault code storage area and the non-permanent code storage area do not store the enabled fault codes, that the faults corresponding to the enabled fault codes occur, and that the fault confirmation level corresponding to the enabled fault codes meets a preset standard, The enabling fault code corresponds to a non-zero fault type and a judgment result that fault storage creation is allowed, and the enabling fault code is determined as the fault code to be stored.
The fault code storage method according to claim 1, said method further comprising:

The storage area of the storage device is at least divided into the permanent fault code storage area and the non-permanent fault code storage area according to the preprocessing instructions.
The fault code storage method according to claim 1, wherein,

The permanent fault code storage conditions include: the permanent fault code storage area is not fully used;

The non-permanent fault code storage conditions include: the non-permanent fault code storage area is not fully used, and the fault priority of the fault codes to be stored is higher than that of the stored fault codes.
The fault code storage method according to claim 6, wherein,

The storage content of the fault code table includes the fault type and fault priority of the fault codes to be stored;

The fault priority of the fault codes to be stored is preset according to the fault degree.
A fault code storage device, comprising:

The fault code acquisition module is set to obtain the enabled fault codes in the enabled state in the memory according to the fault code table;

The fault code screening module is configured to acquire fault codes to be stored from the enabled fault codes according to preset conditions;

The first fault code storage module is configured to store the fault codes to be stored that meet the permanent fault code storage conditions into the permanent fault code storage area when the fault corresponding to the fault code to be stored is a permanent fault;

The second fault code storage module is configured to store the fault codes to be stored that meet the non-permanent fault code storage conditions into the non-permanent fault code storage when the fault corresponding to the fault code to be stored is a non-permanent fault district.
A fault code storage device, the fault code storage device includes:

processor;

memory device, is arranged to store the program,

When the program is executed by the processor, the processor implements the fault code storage method according to any one of claims 1-7.
A computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the fault code storage method according to any one of claims 1-7 is realized.