Fault code classification storage method, device, equipment and storage medium

Abstract

The embodiment of the present invention discloses a fault code classification storage method, device, equipment and storage medium. The method includes: obtaining enabled fault codes in an enabled state in a memory according to a fault code table; obtaining a fault code to be stored from the enabled fault code according to a preset condition; when the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored that meets the permanent fault code storage condition in a permanent fault code storage area; when the fault corresponding to the fault code to be stored is a non-permanent fault, storing the fault code to be stored that meets the non-permanent fault code storage condition in a non-permanent fault code storage area. The technical solution provided by the embodiment of the present invention does not require re-writing of the on-board controller during the research and development process, thereby improving test efficiency, reducing missed detection and identification of faults, ensuring vehicle maintenance quality and driving safety, while saving hardware costs and facilitating large-scale upgrades of mass-produced vehicles.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of electronic control technology, and in particular to a fault code classification storage method, device, equipment and storage medium. Background Art

[0002] A fault code is data stored in a memory device after a fault is detected by the vehicle controller. To ensure vehicle and road safety, the National VI regulations, with the increasing number of vehicles on the road, have introduced stricter requirements for fault code elimination to prevent dangerous driving of vehicles with faults.

[0003] Previous non-permanent fault codes can be deleted at any time, and the fault codes that have been self-healed will not take up storage space. However, a type of permanent fault code has been added to the National VI regulations. This type of fault code cannot be deleted by the diagnostic instrument. It needs to be deleted after the fault occurs and is stored, and after the number of warm-up cycles defined by the vehicle manufacturer. Because the storage element can only store a limited number of fault codes, once the permanent faults are full, new faults that occur later cannot be stored in the storage element. In this way, when the vehicle is repaired and developed and tested, many of the vehicle's current faults cannot be obtained by querying the fault code, which seriously affects the quality of repair and development efficiency. Summary of the Invention

[0004] The embodiments of the present invention provide a fault code classification storage method, device, equipment and storage medium, so as to achieve the goal of eliminating the need to rewrite the vehicle controller during the research and development process, thereby improving testing efficiency, reducing missed fault detection and identification, ensuring vehicle maintenance quality and driving safety, saving hardware costs, and facilitating large-scale upgrades of mass-produced vehicles.

[0005] In a first aspect, an embodiment of the present invention provides a method for storing fault codes by classification, the method comprising:

[0006] Obtain the enabled fault code of the enabled state in the memory according to the fault code table;

[0007] Obtaining a fault code to be stored from the enabled fault code according to a preset condition;

[0008] When the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored that meets the permanent fault code storage conditions into the permanent fault code storage area;

[0009] When 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.

[0010] In a second aspect, an embodiment of the present invention further provides a fault code classification storage device, the device comprising:

[0011] A fault code acquisition module is used to obtain an enabled fault code in an enabled state in a memory according to a fault code table;

[0012] A fault code screening module, configured to obtain the fault code to be stored from the enabled fault codes according to preset conditions;

[0013] a first fault code storage module, configured to store the fault code to be stored that meets the permanent fault code storage conditions into a permanent fault code storage area when the fault corresponding to the fault code to be stored is a permanent fault;

[0014] The second fault code storage module 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 storage area when the fault corresponding to the fault code to be stored is a non-permanent fault.

[0015] In a third aspect, an embodiment of the present invention further provides a fault code classification storage device, the fault code classification storage device comprising:

[0016] one or more processors;

[0017] a storage device for storing one or more programs;

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement any fault code classification storage method described in the first aspect.

[0019] In a fourth aspect, an embodiment of the present invention further provides a storage medium on which a computer program is stored, and when the program is executed by a processor, any of the fault code classification storage methods described in the first aspect is implemented.

[0020] The fault code classification storage method, device, equipment and storage medium provided by the embodiments of the present invention obtains enabled fault codes in an enabled state in a memory according to a fault code table; obtains a fault code to be stored from the enabled fault code according to a preset condition; when the fault corresponding to the fault code to be stored is a permanent fault, the fault code to be stored that meets the permanent fault code storage condition is stored in a permanent fault code storage area; when 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 a non-permanent fault code storage area. This eliminates the need to re-write the on-board controller during the research and development process, thereby improving test efficiency, reducing missed fault detection and identification, ensuring vehicle maintenance quality and driving safety, saving hardware costs, and facilitating large-scale upgrades of mass-produced vehicles. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Other features, objects and advantages of the present invention will become more apparent upon reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0022] Figure 1 This is a flow chart of a fault code classification storage method provided in the first embodiment of the present invention;

[0023] Figure 2 This is a flow chart of a fault code classification storage method provided in the second embodiment of the present invention;

[0024] Figure 3 This is a structural block diagram of a fault code classification storage device provided in the third embodiment of the present invention;

[0025] Figure 4 This is a structural diagram of a fault code classification storage device provided in the fourth embodiment of the present invention. DETAILED DESCRIPTION

[0026] The present invention will be further described in detail below with reference to the accompanying drawings and examples. It will be understood that the specific embodiments described herein are intended only to illustrate the present invention and are not intended to limit the present invention. It should also be noted that, for ease of description, the accompanying drawings only illustrate portions relevant to the present invention, not all structures.

[0027] Example A

[0028] Figure 1 This is a flowchart of a fault code classification storage method provided in the first embodiment of the present invention. This embodiment is applicable to situations where a vehicle experiences a fault while driving on the road and needs to store fault codes when a fault record is required. This method can be executed by the fault code classification storage device provided in the embodiment of the present invention, which can be implemented in software and / or hardware. The device can be configured in a vehicle controller. The method specifically includes:

[0029] S110 , obtaining an enabled fault code of an enabled state in a memory according to a fault code table.

[0030] Among them, the fault code table is data pre-set in the ECU (vehicle control unit), which stores the fault class and fault type of all possible faults. The fault type is determined based on the vehicle's hardware equipment or the ECU, and includes two types of faults: permanent fault codes and non-permanent fault codes. Different fault classes are set for the same control target. 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 a fault occurs in the control target.

[0031] Specifically, the ECU checks whether all fault codes in the fault code table are currently enabled and whether they are allowed to be reported under the current working conditions to determine whether the fault code is in an enabled state.

[0032] For example: when the vehicle is in the parking state, if the vehicle detects a coolant overheating fault, since coolant overheating is an unrelated fault in the parking state, the fault code corresponding to the coolant overheating fault is determined to be in a non-enabled state under this working condition. On the contrary, if a fault is detected in the electronic parking brake, since this fault may cause the vehicle to be unable to enter or maintain the parking state, the fault code corresponding to the electronic parking brake fault is determined to be in an enabled state under the parking state. By obtaining the current working condition, it is determined whether a certain fault is allowed to be reported under the current working condition, that is, pre-screening of the fault code, which reduces the working pressure of the ECU, improves the efficiency of fault code processing, and reduces the storage pressure of the storage unit.

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

[0034] The preset conditions are pre-selected conditions set in the ECU for screening the enabled fault codes, and the enabled fault codes are screened by the preset conditions to obtain the fault codes that are eligible for storage.

[0035] Optionally, the preset conditions include at least one of the following: if the permanent fault code storage area and the non-permanent code storage area do not store the enabled fault code, the fault corresponding to the fault code occurs, the fault confirmation level meets the preset standard, the fault type is non-zero and fault storage creation is allowed, if the preset conditions are met, the enabled fault code is determined as the fault code to be stored.

[0036] In order to save storage space in the storage unit, for a fault code that has been stored in the storage unit, when the corresponding fault occurs again, it will not be stored even if it is detected as an enabled fault code. In order to avoid the vehicle system causing an error or inaccurate use of the fault code, it is necessary to check again the recurrence of the corresponding fault of the enabled fault code to avoid the enabled fault code being erroneously read and stored in the storage unit when the fault does not actually occur. For different vehicle models (such as conventional A-class, B-class, C, D-class or compact, SUV, MPV, etc.), the standards for the fault confirmation level are inconsistent. For example, for the fault that the atmospheric pressure sensor cannot read the signal, a conventional A-class car will be judged as a fault as long as the signal is not read for 1 second, while the standard for a B-class car may be 0.5s, 0.3s for a C-class car, and 0.1s for a D-class car. For a certain control target, such as the atmospheric pressure sensor, the current vehicle only has three fault categories set: data anomaly, data instability, and inability to obtain data. However, if the fault type reported by the detection fault code is poor contact of the atmospheric pressure sensor, poor contact of the atmospheric pressure sensor is not one of the three preset fault categories. At this time, the fault category of poor contact of the atmospheric pressure sensor is set to zero and not stored, to avoid errors in the vehicle due to original factory errors or subsequent modifications. Non-preset fault categories are stored in the storage unit, wasting the storage space of the storage unit and the maintenance energy of the staff. Fault storage creation permission refers to the working state of the storage unit being allowed to write data from the software. The vehicle's ECU and the storage unit are always in a state of ensuring a complete path connection on the hardware. The vehicle should also have sufficient resources (power, memory space, operating threads, etc.) to execute the complete write fault code data writing process.

[0037] S130 . When the fault corresponding to the fault code to be stored is a permanent fault, the fault code to be stored that meets the permanent fault code storage conditions is stored in a permanent fault code storage area.

[0038] The permanent fault code storage condition is used to determine whether the permanent fault code corresponding to the currently confirmed permanent fault is allowed to be stored in the permanent fault code storage area.

[0039] Specifically, 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. When the fault code category corresponding to the fault code to be stored is a permanent fault and the fault code to be stored meets the permanent fault code storage conditions, it is stored in the permanent fault code storage area.

[0040] Optionally, the permanent fault code storage condition includes: the permanent fault code storage area is not fully used. By further determining whether the permanent fault code storage area can continue to store fault codes based on the fault type of the fault codes to be stored, effective storage of fault information is ensured, and waste of resources caused by repeated attempts to write after the storage area is full and abnormalities in the written data are avoided.

[0041] S140 . When 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 a non-permanent fault code storage area.

[0042] The non-permanent fault code storage condition is used to determine whether a permanent fault code corresponding to a currently confirmed non-permanent fault is allowed to be stored in the non-permanent fault code storage area.

[0043] Specifically, 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. When the fault code category corresponding to the fault code to be stored is a non-permanent fault and the non-permanent fault code storage conditions are met, the fault code to be stored is stored in the non-permanent fault code storage area.

[0044] Optionally, the non-permanent fault code storage conditions include: the non-permanent fault code storage area is not fully used, and the priority of the fault code to be stored is higher than the priority of the stored fault code. The priority of the fault code to be stored is pre-set according to the fault severity and stored in the fault code table together with the fault type of the fault code.

[0045] For example, when the control target is the atmospheric pressure sensor, an atmospheric pressure sensor fault is determined and a fault code is assigned for each fault: for example, a poor atmospheric pressure sensor signal is assigned a fault code of P0001, an unstable atmospheric pressure sensor signal is assigned a fault code of P0005, and an unreadable atmospheric pressure sensor signal is assigned a fault code of P0010. The priority is P0010 > P0005 > P0001. If the vehicle has already stored the fault code P0010 corresponding to the unreadable signal, the fault is more serious, and personnel will perform debugging and maintenance on the atmospheric pressure sensor. Therefore, even if a less serious poor signal fault is subsequently detected, since the higher priority P0010 has already been stored, there is no need to store the fault code P0001 again, and thus the fault code P0001 is not stored. Conversely, if the fault type initially detected is poor signal and the fault code P0001 is stored, if the higher priority P0010 is subsequently detected, it indicates that a more serious fault has occurred in the atmospheric pressure sensing system, and the fault code P0010 will be stored. By pre-setting the priority of the fault code according to the degree of fault and storing the fault codes in order of priority, it avoids storing unimportant fault codes in the storage area, saves a lot of non-permanent code storage space, and improves the storage efficiency and effectiveness of the fault codes.

[0046] The technical solution of this embodiment obtains enabled fault codes in the memory according to a fault code table; obtains the fault codes to be stored from the enabled fault codes according to preset conditions; and when the fault corresponding to the fault code to be stored is a permanent fault, stores the fault code to be stored that meets the permanent fault code storage conditions in the permanent fault code storage area; when the fault corresponding to the fault code to be stored is a non-permanent fault, stores the fault code to be stored that meets the non-permanent fault code storage conditions in the non-permanent fault code storage area. This eliminates the need to re-flash the on-board controller during the R&D process, thereby improving testing efficiency, reducing missed fault detection and identification, ensuring vehicle maintenance quality and driving safety, saving hardware costs, and facilitating large-scale upgrades for mass-produced vehicles.

[0047] On the basis of the above technical solution, optionally, the storage area of ​​the storage device is divided into at least the permanent fault code storage area and the non-permanent fault code storage area according to the pre-processing instruction.

[0048] Specifically, unlike the current method of directly calling the interface provided by the hardware manufacturer and inputting the starting address pointer of the stored data and the size of the memory space occupied by the data to adjust the partitioning, the embodiment of the present invention divides the storage space in the storage element into a permanent fault code storage area and a non-permanent fault code storage area through preprocessing instructions.

[0049] For example, the present invention sets the permanent fault code storage area address to 0x0000-0x4000 and the non-permanent fault code area address to 0x4000-0x8000. "#program" is used to permanently store permanent fault codes in the permanent fault code storage area, while non-permanent fault codes are permanently stored in the non-permanent fault code storage area. By partitioning the storage element through software, the permanent fault code storage area and the non-permanent fault code storage area are completely independent and do not interfere with each other when storing fault codes, ensuring that permanent faults do not occupy non-permanent fault storage space.

[0050] Example 2

[0051] Figure 2 This is a flowchart of a fault code classification storage method provided by the second embodiment of the present invention. Based on the above embodiment, this embodiment further explains how to obtain the enabled fault code of the enabled state in the memory according to the fault code table. Figure 2 The method includes:

[0052] S210. Detect the memory data at a preset time interval to determine whether the memory data is valid; if the memory data is abnormal, determine that the memory data is invalid and restart the operating system.

[0053] The preset time interval is pre-set in the vehicle ECU system, and may be, for example, 10 ms or a time interval of other time lengths. This application takes the time interval of 10 ms as an example for description, and does not describe other time intervals for the time being.

[0054] Specifically, the fault code storage module (Dsm_mainfunction) is first set up in the ECU's operating system, and then Dsm_mainfunction is executed every 10ms. Each time Dsm_mainfunction is executed, the data in the memory is first checked to determine whether the current memory data is valid. 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 determining that the current data is valid, the current memory data is still continuously checked at preset time intervals. If the memory data is detected to be invalid again, the above process is repeated. By continuously checking the memory data, the memory data is guaranteed to be valid, thereby ensuring the accurate acquisition and judgment of the enabled state fault code, thereby improving the vehicle's fault identification and storage capabilities.

[0055] Optionally, the validity of the current memory data is determined by detecting whether abnormal data appears in the current memory: if abnormal data is detected, the current memory data is determined to be invalid; if no abnormal data is detected in the current memory data, the current content data is determined to be valid. Preferably, the abnormality of the current memory data is determined by the size of the data.

[0056] S220 , initializing the diagnostic system and determining whether the diagnostic system is successfully initialized; if the diagnostic system is not successfully initialized, reinitializing the diagnostic system.

[0057] Among them, the diagnostic system can be a set program in the system for detecting the status of vehicle components, 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 it can realize the diagnostic function by combining the above software with the above hardware.

[0058] Specifically, after determining that the current vehicle memory data is valid, the vehicle's diagnostic system is initialized and a determination is made as to whether the diagnostic system has been successfully initialized. If the current diagnostic system is successfully initialized, it indicates that the current vehicle memory and diagnostic system are both operating normally and have an environment in which to detect vehicle faults and store fault codes. If the diagnostic system fails to initialize, it indicates that the current diagnostic system cannot operate in its original state and that there may be previously diagnosed faults in the diagnostic system. In this case, the fault data provided by the diagnostic system may be historical fault data that has been reported previously. At the same time, failure to initialize will also result in excessive accumulation of useless data in the diagnostic system, affecting subsequent reading and writing of data and the operating speed of the diagnostic system. Therefore, after the diagnostic system fails to initialize, the initialization process is executed again until the current diagnostic system is successfully initialized, ensuring that the diagnostic system is in an initialized state when performing vehicle fault diagnosis and will not be affected by the data of the previous diagnostic cycle, thereby improving the operating speed and diagnostic stability of the diagnostic system.

[0059] S230: Obtain an enabled fault code in an enabled state in the memory according to the fault code table.

[0060] S240: Obtain a fault code to be stored from the enabled fault codes according to a preset condition.

[0061] S250: When the fault corresponding to the fault code to be stored is a permanent fault, the fault code to be stored that meets the permanent fault code storage conditions is stored in a permanent fault code storage area.

[0062] S260: When 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 conditions is stored in a non-permanent fault code storage area.

[0063] The technical solution of this embodiment, based on the classified storage of fault codes, eliminates the need to rewrite the on-board controller during the research and development process, thereby improving test efficiency, reducing missed detection and identification of faults, ensuring vehicle maintenance quality and driving safety, saving hardware costs, and facilitating large-scale upgrades of mass-produced vehicles. In addition, by further checking whether the memory data is valid and whether the diagnostic system is successfully initialized, the validity of the memory and fault data is ensured, and the operating speed and diagnostic stability of the diagnostic system are improved.

[0064] Example 3

[0065] Figure 3 This is a structural block diagram of a fault code classification storage device provided by the third embodiment of the present invention. The device can execute the fault code classification storage method provided by any embodiment of the present invention and has the corresponding functional modules and beneficial effects of the execution method. Figure 3 As shown, the device may include:

[0066] The fault code acquisition module 310 is used to obtain the enabled fault code of the enabled state in the memory according to the fault code table;

[0067] The fault code screening module 320 is used to obtain the fault code to be stored from the enabled fault code according to a preset condition;

[0068] The first fault code storage module 330 is configured to store the fault code to be stored that meets 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;

[0069] 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 storage area when the fault corresponding to the fault code to be stored is a non-permanent fault.

[0070] Optionally, the fault code classification storage device may further include a memory data monitoring module 350:

[0071] The memory data monitoring module 350 is used to initialize the diagnostic system and determine whether the diagnostic system is initialized successfully; if the diagnostic system is not initialized successfully, the diagnostic system is initialized again.

[0072] Optionally, the fault code classification storage device may further include a diagnostic system initialization module 360:

[0073] The diagnostic system initialization module 360 ​​is configured to detect the memory data at a preset time interval to determine whether the memory data is valid; if the memory data is abnormal, the memory data is determined to be invalid and the operating system is restarted.

[0074] Optionally, the fault code screening module 320 is also used to determine the enabled fault code as the fault code to be stored if the enabled fault code is not stored in the permanent fault code storage area and the non-permanent code storage area, the fault corresponding to the fault code occurs, the fault confirmation level meets the preset standard, the fault type is non-zero and the fault storage creation is allowed.

[0075] Optionally, the storage area of ​​the storage device is divided into at least the permanent fault code storage area and the non-permanent fault code storage area according to the pre-processing instruction.

[0076] 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 the priority of the fault code to be stored is higher than the priority of the stored fault code.

[0077] Optionally, the storage content of the fault code table includes the fault type and fault priority of the fault code to be stored; the priority of the fault code to be stored is pre-set according to the degree of the fault.

[0078] The fault code classification storage device provided by the embodiment of the present invention obtains enabled fault codes 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 fault code to be stored is a permanent fault, the fault codes to be stored that meet the permanent fault code storage conditions are stored in the permanent fault code storage area; when the fault corresponding to the fault code to be stored is a non-permanent fault, 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. This eliminates the need to re-write the on-board controller during the research and development process, thereby improving testing efficiency, reducing missed fault detection and identification, ensuring vehicle maintenance quality and driving safety, saving hardware costs, and facilitating large-scale upgrades for mass-produced vehicles.

[0079] Example 4

[0080] Figure 4 A structural diagram of a fault code classification storage device provided in the third embodiment of the present invention is shown as follows: Figure 4 As shown, 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 in the device can be one or more. Figure 4 In the embodiment, a processor 40 is used as an example; the processor 40, memory 41, input device 42 and output device 43 of the device can be connected by a bus or other means. Figure 4 The bus connection is taken as an example.

[0081] The memory 41, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the fault code classification storage method in the embodiment of the present invention (e.g., the 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 the software programs, instructions, and modules stored in the memory 41 to execute various functional applications and data processing of the device, thereby implementing the above-mentioned fault code classification storage method.

[0082] The memory 41 may primarily include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store data created based on the use of the terminal, etc. Furthermore, the memory 41 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some instances, the memory 41 may further include memory remotely located relative to the processor 40, and these remote memories may be connected to the device via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0083] The input device 42 may be used to receive input digital 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.

[0084] Example 5

[0085] A fifth embodiment of the present invention further provides a storage medium comprising computer-executable instructions. When the computer-executable instructions are executed by a computer processor, the computer-executable instructions are used to perform a fault code classification storage method, the method comprising:

[0086] Obtain the enabled fault code of the enabled state in the memory according to the fault code table;

[0087] Obtaining a fault code to be stored from the enabled fault code according to a preset condition;

[0088] When the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored that meets the permanent fault code storage conditions into the permanent fault code storage area;

[0089] When 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.

[0090] Of course, the storage medium containing computer-executable instructions provided in an embodiment of the present invention is not limited to the method operations described above, and can also execute related operations in the fault code classification storage method provided in any embodiment of the present invention.

[0091] Through the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented with the help of software and necessary general-purpose hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0092] It is worth noting that in the embodiment of the above-mentioned fault code classification storage device, the various 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 achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0093] Note that the above are only preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments, and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments and may include many other equivalent embodiments without departing from the concept of the present invention. The scope of the present invention is determined by the scope of the appended claims.

Claims

1. A fault code classification storage method, characterized in that: include: Obtain the enabled fault code of the enabled state in the memory according to the fault code table; Obtaining a fault code to be stored from the enabled fault code according to preset conditions, including: if the enabled fault code is not stored in the permanent fault code storage area and the non-permanent fault code storage area, the fault corresponding to the fault code occurs, the fault confirmation level meets a preset standard, the fault type is non-zero, and fault storage creation is allowed, determining the enabled fault code as the fault code to be stored; When the fault corresponding to the fault code to be stored is a permanent fault, the fault code to be stored that meets the permanent fault code storage conditions is stored in the permanent fault code storage area; wherein the permanent fault code storage conditions include: the permanent fault code storage area is not fully used; When 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 conditions is stored in the non-permanent fault code storage area; wherein, the non-permanent fault code storage conditions include: the non-permanent fault code storage area is not fully used, and the priority of the fault code to be stored is higher than the priority of the stored fault code.

2. The method according to claim 1, characterized in that Before obtaining the enabled fault code of the enabled state in the memory according to the fault code table, the following steps are also included: Initializing the diagnostic system and determining whether the diagnostic system is successfully initialized; If the diagnostic system initialization is unsuccessful, the diagnostic system is initialized again.

3. The method according to claim 2, characterized in that Initializing the diagnostic system, and before determining whether the diagnostic system is successfully initialized, further comprising: Checking memory data at preset time intervals to determine whether the memory data is valid; If the memory data is abnormal, the memory data is determined to be invalid and the operating system is restarted.

4. The fault code classification storage method according to claim 1, characterized in that: Also includes: The storage area of ​​the storage device is divided into at least the permanent fault code storage area and the non-permanent fault code storage area according to the pre-processing instruction.

5. The fault code classification storage method according to claim 1, characterized in that: The storage content of the fault code table includes the fault type and fault priority of the fault code to be stored; The priority of the fault code to be stored is preset according to the degree of the fault.

6. A fault code classification storage device, characterized in that: include: A fault code acquisition module is used to obtain an enabled fault code in an enabled state in a memory according to a fault code table; A fault code screening module, configured to obtain the fault code to be stored from the enabled fault codes according to preset conditions; The fault code screening module is specifically configured to determine the enabled fault code as the fault code to be stored if the enabled fault code is not stored in the permanent fault code storage area and the non-permanent fault code storage area, the fault corresponding to the fault code occurs, the fault confirmation level meets a preset standard, the fault type is non-zero, and fault storage creation is allowed; a first fault code storage module, configured to store the fault code to be stored that meets a permanent fault code storage condition into the permanent fault code storage area when the fault corresponding to the fault code to be stored is a permanent fault; wherein the permanent fault code storage condition includes: the permanent fault code storage area is not fully used; a second fault code storage module, configured to store the fault code to be stored that meets the non-permanent fault code storage conditions into the non-permanent fault code storage area when the fault corresponding to the fault code to be stored is a non-permanent fault; wherein the non-permanent fault code storage conditions include: the non-permanent fault code storage area is not fully used, and the priority of the fault code to be stored is higher than the priority of the stored fault code.

7. A fault code classification storage device, characterized in that: The fault code classification storage device includes: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the fault code classification storage method as described in any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the fault code classification storage method as described in any one of claims 1 to 5 is implemented.

Images