CN113934898B - Fault code classified storage method, device, equipment and storage medium - Google Patents
Fault code classified storage method, device, equipment and storage mediumInfo
- Publication number
- CN113934898B CN113934898B CN202111248008.6A CN202111248008A CN113934898B CN 113934898 B CN113934898 B CN 113934898B CN 202111248008 A CN202111248008 A CN 202111248008A CN 113934898 B CN113934898 B CN 113934898B
- Authority
- CN
- China
- Prior art keywords
- fault code
- fault
- stored
- permanent
- storage
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/906—Clustering; Classification
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The embodiment of the invention discloses a fault code classified storage method, device, equipment and storage medium. The method comprises the steps of obtaining enabling fault codes of enabling states in a memory according to a fault code table, obtaining fault codes to be stored from the enabling fault codes according to preset conditions, storing the fault codes to be stored, which meet the permanent fault code storage conditions, in a permanent fault code storage area when the fault corresponding to the fault codes to be stored is a permanent fault, and storing the fault codes to be stored, which meet the non-permanent fault code storage conditions, in a non-permanent fault code storage area when the fault corresponding to the fault codes to be stored is a non-permanent fault. According to the technical scheme provided by the embodiment of the invention, the vehicle-mounted controller is not required to be rewritten in the research and development process, so that the test efficiency is improved, missing detection and identification of faults are reduced, the vehicle maintenance quality and the driving safety are ensured, meanwhile, the hardware cost is saved, and the mass-production vehicle is easy to upgrade on a large scale.
Description
Technical Field
The embodiment of the invention relates to the technical field of electronic control, in particular to a fault code classified storage method, device and equipment and a storage medium.
Background
The fault code is data which is stored in the storage element after the vehicle controller recognizes the fault. In order to guarantee vehicle driving and road safety, the country has more strict requirements for eliminating fault codes in the national Six Codes rule to prevent dangerous driving of some fault vehicles on the road.
The traditional non-permanent fault code can be deleted at any time, so that the self-healing fault code does not occupy the storage space. In the state six regulation, a permanent fault code is added, which cannot be deleted by a diagnostic instrument, and the fault code can be automatically deleted after the number of warmup cycles defined by a whole vehicle factory is needed after the fault occurs and is stored. Since the fault codes that can be stored by the storage element are limited, once a permanent fault is full, a new fault cannot be stored in the storage element after that. Therefore, when the vehicles are maintained and developed, the faults existing in many vehicles can not be obtained by inquiring fault codes, and the maintenance quality and development efficiency are seriously affected
Disclosure of Invention
The embodiment of the invention provides a fault code classified storage method, device, equipment and storage medium, which are used for realizing that a vehicle-mounted controller is not required to be rewritten in the research and development process, so that the test efficiency is improved, missing detection and identification of faults are reduced, the maintenance quality and the driving safety of a vehicle are ensured, the hardware cost is saved, and the large-scale upgrading of a mass-production vehicle is easy to realize.
In a first aspect, an embodiment of the present invention provides a method for storing fault codes in a classified manner, where the method includes:
acquiring an enabling fault code of an enabling state in the memory according to the fault code table;
acquiring a fault code to be stored from the enabling 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 which accords with the storage condition of the permanent fault code into a permanent fault code storage area;
And when the fault corresponding to the fault code to be stored is a non-permanent fault, storing the fault code to be stored, which accords with the storage condition of the non-permanent fault code, into a non-permanent fault code storage area.
In a second aspect, an embodiment of the present invention further provides a fault code classification storage device, where the device includes:
the fault code acquisition module is used for acquiring an enabling fault code of an enabling state in the memory according to the fault code table;
The fault code screening module is used for acquiring the fault code to be stored from the enabling fault code according to preset conditions;
the first fault code storage module is used for storing the fault code to be stored, which accords with the permanent fault code storage condition, into a permanent fault code storage area when the fault corresponding to the fault code to be stored is a permanent fault;
and the second fault code storage module is used for storing the fault code to be stored, which accords with the storage condition of the non-permanent fault code, into the non-permanent fault code storage area when the fault corresponding to the fault code to be stored is the non-permanent fault.
In a third aspect, an embodiment of the present invention further provides a fault code classification storage device, where the fault code classification storage device includes:
One or more processors;
a storage means for storing one or more programs;
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the fault code classification storage method of any of the first aspects.
In a fourth aspect, an embodiment of the present invention further provides a storage medium, where a computer program is stored, where the program when executed by a processor implements the fault code classification storage method according to any of the first aspects.
The fault code classified storage method, the fault code classified storage device, the fault code classified storage equipment and the fault code classified storage medium are characterized in that enabling fault codes of enabling states in a memory are obtained according to a fault code table, fault codes to be stored are obtained from the enabling fault codes according to preset conditions, when faults corresponding to the fault codes to be stored are permanent faults, the fault codes to be stored, which are in accordance with the storage conditions of the permanent fault codes, are stored in a permanent fault code storage area, and when the faults corresponding to the fault codes to be stored are non-permanent faults, the fault codes to be stored, which are in accordance with the storage conditions of the non-permanent fault codes, are stored in a non-permanent fault code storage area. The vehicle-mounted controller is not required to be rewritten in the research and development process, so that the test efficiency is improved, missing detection and identification of faults are reduced, the vehicle maintenance quality and the driving safety are ensured, meanwhile, the hardware cost is saved, and the mass-production vehicle is easy to upgrade on a large scale.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
FIG. 1 is a flow chart of a method for storing fault code classifications according to a first embodiment of the present invention;
FIG. 2 is a flow chart of a method for storing fault codes in a classified manner according to a second embodiment of the present invention;
FIG. 3 is a block diagram of a fault code classification storage device according to a third embodiment of the present invention;
Fig. 4 is a schematic structural diagram of a fault code classification storage device according to a fourth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example A
Fig. 1 is a flowchart of a fault code classification storage method according to an embodiment of the present invention, where the embodiment is applicable to a situation that a vehicle fails when traveling on a road and performs fault code storage when a fault record is required, and the method may be performed by a fault code classification storage device according to an embodiment of the present invention, and the device may be implemented in a software and/or hardware manner. The device can be configured in a vehicle-mounted controller, and the method specifically comprises the following steps:
S110, acquiring an enabling fault code of an enabling state in the memory according to the fault code table.
The fault code table is data preset in an ECU (vehicle control Unit) and stores fault classes and fault types of all faults possibly occurring. The fault type is determined according to hardware equipment of the vehicle or according to the ECU, and comprises two fault types of 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 reasons, so each control target corresponds to multiple different fault classes. The failure code may be understood as encoded information generated by the ECU for a failure when the control target fails.
Specifically, the ECU detects whether all fault codes in a fault code table are enabled currently and whether the fault codes are allowed to be reported under the current working condition so as to judge whether the fault codes are in an enabled state.
When the vehicle is in a parking state, if the vehicle detects the overheat fault of the cooling liquid, the fault code corresponding to the overheat fault of the cooling liquid is judged to be in a non-enabling state under the working condition because the overheat of the cooling liquid belongs to an irrelevant fault in the parking state. Conversely, if the electronic hand brake is detected to be faulty, the vehicle cannot enter or keep the parking state due to the fault, and then the fault code corresponding to the fault of the electronic hand brake is determined to be in an enabling state under the working condition of the parking state. And whether a certain fault is allowed to be reported under the current working condition or not is judged by acquiring the current working condition, namely, the fault code is screened in advance, the working pressure of the ECU is reduced, the fault code processing efficiency is improved, and the storage pressure of the storage unit is also reduced.
S120, acquiring a fault code to be stored from the enabling fault code according to a preset condition.
The preset conditions are conditions which are pre-selected and arranged in the ECU and used for screening the enabling fault codes, and the enabling fault codes are screened through the preset conditions to obtain the fault codes with storage qualification.
Optionally, the preset condition comprises at least one of the following steps that if the permanent fault code storage area and the non-permanent code storage area do not store the enabling fault code, the fault code corresponds to the fault occurrence, the fault confirmation level meets the preset standard, the fault class is non-zero and the fault storage creation is allowed, and if the preset condition is met, the enabling fault code is determined to be the fault code to be stored.
In order to save the storage space of the storage unit, the fault code stored in the storage unit is not stored even if the fault code is detected as an enabled fault code when the corresponding fault occurs again. In order to avoid the occurrence of errors or inaccurate fault codes caused by the occurrence of vehicle systems, the fault codes corresponding to the enabling fault codes need to be checked again, and the enabling fault codes are wrongly read and stored in the storage unit under the condition that the fault does not occur in practice. The criteria for the failure confirmation level are inconsistent for different vehicle models (e.g., conventional class a, class B, C, D or compact, SUV, MPV, etc.). For example, for a failure that the atmospheric pressure sensor cannot read the signal, the conventional class a vehicle is determined to be failed as long as the signal is not read for 1 second, while the class B vehicle standard may be 0.5s, the class C parking space 0.3s, and the class D vehicle is 0.1s. For a certain control target, such as an atmospheric pressure sensor, the current vehicle is only provided with three fault types, such as abnormal data and unstable data, and can not acquire the data, but if the fault type reported by the detected fault code is one of the three preset fault types, the fault type with the poor atmospheric pressure sensor is not one of the three preset fault types, and at the moment, the fault type with the poor atmospheric pressure sensor is set to be zero and is not stored, so that the problem that the fault type with the poor atmospheric pressure sensor is not preset due to the error of the original factory or the subsequent refitting of the vehicle is avoided to be stored in a storage unit, and the storage space of the storage unit and the maintenance effort of staff are wasted. The fault storage creation permission refers to a working state that data is permitted to be written from a storage unit on software, an ECU (electronic control unit) of a vehicle on hardware is always in a state of being connected with the storage unit in a guaranteed complete path, and the vehicle also has enough resources (electric quantity, memory space, operation threads and the like) to execute a fault code data writing flow of complete writing.
And S130, storing the fault code to be stored, which accords with the storage condition of the permanent fault code, into a permanent fault code storage area when the fault corresponding to the fault code to be stored is the permanent fault.
Wherein the permanent fault code storage condition is used for judging whether the permanent fault code corresponding to the permanent fault which has been confirmed as the permanent fault at present is allowed to be stored in the permanent fault code storage area.
Specifically, after the ECU acquires the fault code to be stored, comparing the fault code to be stored with the contents recorded in the fault code table, and when the fault code class corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored, which meets the permanent fault code storage condition, into a permanent fault code storage area.
Optionally, the persistent fault code storage condition includes that the persistent fault code storage area is not fully used. On the basis of screening the fault type of the fault code to be stored, whether the permanent fault code storage area can continuously store the fault code is further judged, effective storage of fault information is guaranteed, and resource waste caused by repeated trial writing after the storage area is full and abnormality of written data are avoided.
And S140, when the fault corresponding to the fault code to be stored is a non-permanent fault, storing the fault code to be stored, which accords with the storage condition of the non-permanent fault code, into a non-permanent fault code storage area.
The non-permanent fault code storage condition is used for judging whether the permanent fault code corresponding to the non-permanent fault which is confirmed to be the non-permanent fault at present is allowed to be stored in the non-permanent fault code storage area.
Specifically, after the ECU acquires the fault code to be stored, comparing the fault code to be stored with the contents recorded in the fault code table, and storing the fault code to be stored in the non-permanent fault code storage area when the fault code class corresponding to the fault code to be stored is a non-permanent fault and the non-permanent fault code storage condition is met.
Optionally, the non-persistent fault code storage condition includes that the non-persistent fault code storage area is not used completely and the to-be-stored fault code priority is higher than the stored fault code priority. The priority of the fault code to be stored is preset according to the fault degree, and the priority and the fault type of the fault code are stored in a fault code table together.
Illustratively, when the control target is an atmospheric pressure sensor, determining a fault of the atmospheric pressure sensor, and further setting a fault code for each fault, for example, the fault code of the poor atmospheric pressure sensor signal is P0001, the fault code of the unstable atmospheric pressure sensor signal is P0005, the fault code of the unreadable atmospheric pressure sensor signal is P0010, and the specific priority is P0010> P0005> P0001. When the corresponding fault code P0010 cannot be read by the stored signal of the vehicle, the worker can debug and maintain the atmospheric pressure sensor due to serious faults. Therefore, even when a signal failure with a low degree of failure is detected later, since P0010 with a high priority has already been stored, it is not necessary to store the failure code P0001 again, and therefore the failure code P0001 is not stored. Conversely, if the failure class is detected as poor signal at first, and the failure code is stored as P0001, if P0010 with higher priority is detected later, which indicates that the atmospheric pressure sensing system has a more serious failure at this time, P0010 is also stored. The priority of the fault codes is preset according to the fault degree, and the fault codes are stored according to the priority order, so that unimportant fault codes are prevented from being stored in the storage area, a large amount of non-permanent code storage space is saved, and the storage efficiency and the effectiveness of the fault codes are improved.
According to the technical scheme, enabling fault codes of enabling states in a memory are obtained according to a fault code table, fault codes to be stored are obtained from the enabling fault codes according to preset conditions, when faults corresponding to the fault codes to be stored are permanent faults, the fault codes to be stored, which meet the storage conditions of the permanent fault codes, are stored in a permanent fault code storage area, and when the faults corresponding to the fault codes to be stored are non-permanent faults, the fault codes to be stored, which meet the storage conditions of the non-permanent fault codes, are stored in a non-permanent fault code storage area. The vehicle-mounted controller is not required to be rewritten in the research and development process, so that the test efficiency is improved, missing detection and identification of faults are reduced, the vehicle maintenance quality and the driving safety are ensured, meanwhile, the hardware cost is saved, and the mass-production vehicle is easy to upgrade on a large scale.
On the basis of the technical scheme, optionally, a 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 a preprocessing instruction.
Specifically, the method for inputting the initial address pointer of the stored data and the size of the memory space occupied by the data to adjust and partition is different from the method for normally and directly calling the interface provided by the hardware manufacturer at present. The embodiment of the 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 the preprocessing instruction.
Exemplary, in the embodiment of the present invention, the permanent fault code storage area address is set to be 0x0000-0x4000, the non-permanent fault code storage area address is set to be 0x4000-0x8000, and the permanent fault code is fixedly stored in the permanent fault code storage area through the '#program', and the non-permanent fault code is fixedly stored in the non-permanent fault code storage area. The storage element is partitioned by software, and the permanent fault code storage area and the non-permanent fault code storage area are completely independent when the fault code is stored, so that the permanent fault can not occupy the non-permanent fault storage space.
Example two
Fig. 2 is a flowchart of a fault code classification storage method according to a second embodiment of the present invention, where the embodiment further explains the enabling fault code that obtains the enabling state in the memory according to the fault code table based on the above embodiment. Specifically, referring to fig. 2, the method includes:
S210, detecting the memory data at preset time intervals, judging whether the memory data are valid or not, if the memory data are abnormal, judging that the memory data are invalid, and restarting the operating system.
The preset time interval is preset in the vehicle ECU system, and may be, for example, a time interval of 10ms or other time length. The application is stated with an interval length of 10ms as an example, and other time intervals are not stated at all.
Specifically, the fault code storage module (dsm_ mainfunction) is set into the operating system of the ECU first, after which dsm_ mainfunction is executed every 10 ms. And when the Dsm_ mainfunction is executed each time, firstly detecting the data in the memory, judging whether the current memory data is valid, restarting the operating system if the current memory data is invalid, and if the current memory data is valid, restarting the operating system. And detecting the current memory data continuously at preset time intervals even after the current data are judged to be valid, and continuously and repeatedly executing the process if the memory data are detected to be invalid again. Through carrying out the persistence detection to the memory data, the memory data is guaranteed to be effective, and then accurate acquisition and judgment of the enable state fault code are guaranteed, and the recognition and storage capacity of the vehicle to faults are improved.
Optionally, whether the current memory data is valid is judged by detecting whether abnormal data appear in the current memory, if so, the current memory data is judged to be invalid, and if not, the current content data is judged to be valid. Preferably, whether the current memory data is abnormal is judged according to the size of the data.
S220, initializing a diagnostic system, judging whether the diagnostic system is successfully initialized, and if the diagnostic system is not successfully initialized, initializing the diagnostic system again.
The diagnostic system may be a set program for detecting the state of a vehicle component in the system, a device that is mounted in a vehicle and connected to the vehicle component and transmits the state of each component to the ECU, or a diagnostic function that is realized by combining the software and the hardware.
Specifically, after the current vehicle memory data is determined to be valid, the diagnostic system of the vehicle is initialized, whether the diagnostic system is initialized successfully is judged, if the current diagnostic system is initialized successfully, the current vehicle memory and the diagnostic system can be normally operated, and the environment for detecting the vehicle faults and storing the fault codes is provided. If the diagnostic system is not initialized, the current diagnostic system cannot operate in an original state, the diagnostic system may have a fault which has been diagnosed before, the fault data given by the diagnostic system may be historical fault data which has been reported before, and meanwhile, too much useless data is accumulated in the diagnostic system due to the fact that the fault data cannot be initialized, and the reading and writing of subsequent data and the operation speed of the diagnostic system are affected. Therefore, after the initialization of the diagnostic system fails, the initialization process is executed again until the current diagnostic system is successfully initialized, so that the diagnostic system is ensured to be in an initialized state when the vehicle fault diagnosis is carried out, the influence of the data of the previous diagnostic period is avoided, and the running speed and the diagnostic stability of the diagnostic system are improved.
S230, acquiring an enabling fault code of an enabling state in the memory according to the fault code table.
S240, acquiring a fault code to be stored from the enabling fault code according to a preset condition.
S250, when the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored, which accords with the storage condition of the permanent fault code, into a permanent fault code storage area.
And S260, when the fault corresponding to the fault code to be stored is a non-permanent fault, storing the fault code to be stored, which accords with the storage condition of the non-permanent fault code, into a non-permanent fault code storage area.
According to the technical scheme, the fault codes are classified and stored, the fact that the vehicle-mounted controller is not required to be rewritten in the research and development process is achieved, so that the testing efficiency is improved, missing detection and identification of faults are reduced, the vehicle maintenance quality and the driving safety are guaranteed, meanwhile, the hardware cost is saved, the large-scale upgrading of the mass production vehicle is easy to achieve, the effectiveness of the memory and fault data is guaranteed by detecting whether the memory data are effective or not and whether the diagnosis system is successfully initialized or not, and the running speed and the diagnosis stability of the diagnosis system are improved.
Example III
Fig. 3 is a block diagram of a fault code classification storage device according to a third embodiment of the present invention, where the device may execute the fault code classification storage method according to any embodiment of the present invention, and the fault code classification storage device has functional modules and beneficial effects corresponding to the execution method. As shown in fig. 3, the apparatus may include:
A fault code obtaining module 310, configured to obtain an enable fault code of an enable state in the memory according to a fault code table;
the fault code screening module 320 is configured to obtain a fault code to be stored from the enabled fault codes according to a preset condition;
A first fault code storage module 330, configured to store, when a fault corresponding to the fault code to be stored is a permanent fault, the fault code to be stored that meets a permanent fault code storage condition into a permanent fault code storage area;
And the second fault code storage module 340 is configured to store the fault code to be stored, which meets the storage condition of the non-permanent fault code, in the non-permanent fault code storage area when the fault corresponding to the fault code to be stored is the non-permanent fault.
Optionally, the fault code classification storage device may further include a memory data monitoring module 350:
The memory data monitoring module 350 is configured to initialize a diagnostic system, determine whether the diagnostic system is initialized successfully, and initialize the diagnostic system again if the diagnostic system is not initialized successfully.
Optionally, the fault code classification storage device may further include a diagnostic system initialization module 360:
the diagnostic system initialization module 360 is configured to detect the memory data at preset time intervals, determine whether the memory data is valid, and if the memory data is abnormal, determine that the memory data is invalid, and restart the operating system.
Optionally, the fault code filtering module 320 is further configured to determine the enabling fault code as the fault code to be stored if the persistent fault code storage area and the non-persistent code storage area do not store the enabling fault code, the fault code corresponds to the fault occurrence, the fault confirmation level meets a preset standard, the fault class is non-zero, and the fault storage creation is allowed.
Optionally, the storage area of the storage device is divided into at least the persistent fault code storage area and the non-persistent fault code storage area according to a preprocessing instruction.
Optionally, the persistent fault code storage condition includes that the persistent fault code storage area is not used completely, the non-persistent fault code storage condition includes that the non-persistent fault code storage area is not used completely, and the to-be-stored fault code priority is higher than the stored fault code priority.
Optionally, the storage content of the fault code table comprises the fault type and the fault priority of the fault code to be stored, and the fault code priority to be stored is preset according to the fault degree.
The fault code classification storage device provided by the embodiment of the invention obtains the enabling fault code of the enabling state in the memory according to the fault code table, obtains the fault code to be stored from the enabling fault code according to the preset condition, stores the fault code to be stored which accords with the 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, and stores the fault code to be stored which accords with 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. The vehicle-mounted controller is not required to be rewritten in the research and development process, so that the test efficiency is improved, missing detection and identification of faults are reduced, the vehicle maintenance quality and the driving safety are ensured, meanwhile, the hardware cost is saved, and the mass-production vehicle is easy to upgrade on a large scale.
Example IV
Fig. 4 is a schematic structural diagram of a fault code classification storage device according to a third embodiment of the present invention, where, as shown in fig. 4, the fault code classification storage device includes a processor 40, a memory 41, an input device 42 and an output device 43, where the number of processors 40 in the device may be one or more, in fig. 4, one processor 40 is taken as an example, and the processor 40, the memory 41, the input device 42 and the output device 43 of the device may be connected by a bus or other manners, in fig. 4, the connection is taken as an example by a bus.
The memory 41 is a computer readable storage medium, and may be used to store software programs, computer executable programs, and modules, such as program instructions/modules (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) corresponding to the fault code classification storage method in the embodiment of the present invention. The processor 40 executes various functional applications of the device and data processing by running software programs, instructions and modules stored in the memory 41, i.e. implements the fault code classification storage method described above.
The memory 41 may mainly include a storage program area which may store an operating system, an application program required for at least one function, and a storage data area which may store data created according to the use of the terminal, etc. In addition, memory 41 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, memory 41 may further include memory located remotely from processor 40, which may be connected to the device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input means 42 may be used to receive entered numeric or character information and to generate key signal inputs related to user settings and function control of the device. The output means 43 may comprise a display device such as a display screen.
Example five
A fifth embodiment of the present invention also provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are for performing a fault code classification storage method, the method comprising:
acquiring an enabling fault code of an enabling state in the memory according to the fault code table;
acquiring a fault code to be stored from the enabling 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 which accords with the storage condition of the permanent fault code into a permanent fault code storage area;
And when the fault corresponding to the fault code to be stored is a non-permanent fault, storing the fault code to be stored, which accords with the storage condition of the non-permanent fault code, into a non-permanent fault code storage area.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present invention is not limited to the method operations described above, and may also perform the related operations in the fault code classification storage method provided in any embodiment of the present invention.
From the above description of embodiments, it will be clear to a person skilled in the art that the present invention may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk, or an optical disk of a computer, etc., and include several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments of the present invention.
It should be noted that, in the embodiment of the fault code classification storage device, each unit and module included are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented, and the specific names of the functional units are only for convenience of distinguishing each other, and are not used for limiting the protection scope of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (8)
1. The fault code classified storage method is characterized by comprising the following steps of:
acquiring an enabling fault code of an enabling state in the memory according to the fault code table;
Obtaining the fault code to be stored from the enabling fault code according to preset conditions, wherein if the enabling fault code is not stored in the permanent fault code storage area and the non-permanent fault code storage area, the fault code corresponds to the fault, the fault confirmation level meets preset standards, the fault class is non-zero and the fault storage creation permission is met, and the enabling fault code is determined to be the fault code to be stored;
when the fault corresponding to the fault code to be stored is a permanent fault, storing the fault code to be stored which accords with the permanent fault code storage condition into the permanent fault code storage area, wherein the permanent fault code storage condition comprises that the permanent fault code storage area is not used completely;
When the fault corresponding to the fault code to be stored is a non-permanent fault, storing the fault code to be stored, which accords with a non-permanent fault code storage condition, into the non-permanent fault code storage area, wherein the non-permanent fault code storage condition comprises that the non-permanent fault code storage area is not used completely and the priority of the fault code to be stored is higher than that of the stored fault code.
2. The method of claim 1, further comprising, prior to retrieving the enable fault code for the enable state in memory according to the fault code table:
initializing a diagnosis system and judging whether the diagnosis system is successfully initialized;
if the diagnostic system is not successfully initialized, initializing the diagnostic system again.
3. The method of claim 2, wherein initializing a diagnostic system, before determining whether the diagnostic system has been successfully initialized, further comprises:
Detecting memory data at preset time intervals, and judging whether the memory data are valid or not;
If the memory data is abnormal, judging that the memory data is invalid, and restarting the operating system.
4. The fault code classification storage method of claim 1, further comprising:
The memory area of the memory device is divided into at least the persistent fault code memory area and the non-persistent fault code memory area according to a preprocessing instruction.
5. The fault code classification storage method of claim 1, wherein;
The storage content of the fault code table comprises the fault type and the fault priority of the fault code to be stored;
And the priority of the fault code to be stored is preset according to the fault degree.
6. A fault code classification storage device, comprising:
the fault code acquisition module is used for acquiring an enabling fault code of an enabling state in the memory according to the fault code table;
The fault code screening module is used for acquiring the fault code to be stored from the enabling fault code according to preset conditions;
The fault code screening module is specifically configured to determine the enabling fault code as the fault code to be stored if the permanent fault code storage area and the non-permanent fault code storage area do not store the enabling fault code, the fault code corresponds to the fault, the fault confirmation level meets a preset standard, the fault class is non-zero, and the fault storage creation is allowed;
the first fault code storage module is used for storing the fault code to be stored, which accords with the 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 comprises that the permanent fault code storage area is not used completely;
And the second fault code storage module is used for storing the fault code to be stored, which accords with the storage condition of the non-permanent fault code, into the non-permanent fault code storage area when the fault corresponding to the fault code to be stored is the non-permanent fault, wherein the storage condition of the non-permanent fault code comprises that the non-permanent fault code storage area is not used completely and the priority of the fault code to be stored is higher than that of the stored fault code.
7. A fault code classification storage device, the fault code classification storage device comprising:
One or more processors;
storage means for storing one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the fault code classification storage method of any of claims 1-5.
8. A computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the fault code classification storage method of any of claims 1-5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111248008.6A CN113934898B (en) | 2021-10-26 | 2021-10-26 | Fault code classified storage method, device, equipment and storage medium |
| PCT/CN2022/126907 WO2023071961A1 (en) | 2021-10-26 | 2022-10-24 | Fault code storage method and apparatus, and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111248008.6A CN113934898B (en) | 2021-10-26 | 2021-10-26 | Fault code classified storage method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113934898A CN113934898A (en) | 2022-01-14 |
| CN113934898B true CN113934898B (en) | 2025-09-09 |
Family
ID=79284270
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111248008.6A Active CN113934898B (en) | 2021-10-26 | 2021-10-26 | Fault code classified storage method, device, equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113934898B (en) |
| WO (1) | WO2023071961A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113934898B (en) * | 2021-10-26 | 2025-09-09 | 中国第一汽车股份有限公司 | Fault code classified storage method, device, equipment and storage medium |
| CN115080344A (en) * | 2022-06-15 | 2022-09-20 | 东风时代(武汉)电池系统有限公司 | Automobile controller fault data storage method and system |
| CN117572852B (en) * | 2024-01-16 | 2024-05-24 | 中国第一汽车股份有限公司 | Vehicle component fault analysis method, device, equipment, medium and product |
| CN117891615B (en) * | 2024-03-15 | 2024-06-18 | 杭州涂鸦信息技术有限公司 | Method and device for determining equipment state |
| CN118859911B (en) * | 2024-09-25 | 2024-12-24 | 成都赛力斯科技有限公司 | Vehicle fault detection method and detection device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111694341A (en) * | 2020-06-05 | 2020-09-22 | 中国第一汽车股份有限公司 | Fault data storage method and device, vehicle-mounted equipment and storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4345860B2 (en) * | 2007-09-14 | 2009-10-14 | 株式会社デンソー | Vehicle memory management device |
| JP4475320B2 (en) * | 2007-11-15 | 2010-06-09 | 株式会社デンソー | Vehicle memory management device |
| CN109407646B (en) * | 2017-08-18 | 2020-06-02 | 宝沃汽车（中国）有限公司 | Vehicle fault data acquisition method and device, storage medium and management server |
| CN112732982B (en) * | 2021-01-18 | 2024-09-10 | 深圳市元征科技股份有限公司 | Fault code storage method and device, terminal equipment and readable storage medium |
| CN113110371A (en) * | 2021-03-16 | 2021-07-13 | 佛山市飞驰汽车科技有限公司 | Vehicle fault code storage and transmission system and method |
| CN113934898B (en) * | 2021-10-26 | 2025-09-09 | 中国第一汽车股份有限公司 | Fault code classified storage method, device, equipment and storage medium |
-
2021
- 2021-10-26 CN CN202111248008.6A patent/CN113934898B/en active Active
-
2022
- 2022-10-24 WO PCT/CN2022/126907 patent/WO2023071961A1/en not_active Ceased
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111694341A (en) * | 2020-06-05 | 2020-09-22 | 中国第一汽车股份有限公司 | Fault data storage method and device, vehicle-mounted equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023071961A1 (en) | 2023-05-04 |
| CN113934898A (en) | 2022-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113934898B (en) | Fault code classified storage method, device, equipment and storage medium | |
| CN109887125B (en) | Fault detection method and device | |
| CN111694687A (en) | Vehicle software fault detection method, device, equipment and storage medium | |
| KR101044544B1 (en) | How to monitor program execution on a microcomputer | |
| CN109884533A (en) | Battery failure diagnosis method and device, equipment and storage medium | |
| CN114326676A (en) | Intrusion detection method and device, storage medium and electronic equipment | |
| CN113672415A (en) | Disk fault processing method, device, equipment and storage medium | |
| JP2009217617A (en) | Method and device for identifying memory leak place | |
| CN116643906A (en) | Cloud platform fault processing method and device, electronic equipment and storage medium | |
| CN112068935A (en) | Method, device and equipment for monitoring deployment of kubernets program | |
| CN112559565A (en) | Abnormity detection method, system and device | |
| CN109254898B (en) | Software module execution sequence monitoring method and system | |
| CN114625106B (en) | Method, device, electronic equipment and storage medium for vehicle diagnosis | |
| CN114030439B (en) | Configuration method and device of air bag controller and computer storage medium | |
| CN118018383A (en) | Automobile fault recording method, device, system and storage medium | |
| CN112783683B (en) | Data processing method, device, equipment and storage medium | |
| CN117591322A (en) | Abnormality processing method and device, electronic equipment and storage medium | |
| CN115185741A (en) | Data recovery method, device, electronic device and storage medium | |
| CN117369424B (en) | Vehicle-mounted chip processor and detection method thereof | |
| CN105279044A (en) | Method for recognizing BIOS (Basic Input/Output System) state based on BOIS bus and computer system | |
| WO2021111728A1 (en) | Failure symptom detection device, failure symptom detection system, failure symptom detection method, and failure symptom detection program | |
| CN118588110B (en) | Model training method, device and electronic equipment | |
| CN115454954B (en) | Data processing method, system and device and electronic equipment | |
| CN119718749A (en) | Data dump management and control method and device | |
| CN120742841A (en) | Fault diagnosis method and fault diagnosis device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |