CN111694341A - Fault data storage method and device, vehicle-mounted equipment and storage medium - Google Patents
Fault data storage method and device, vehicle-mounted equipment and storage medium Download PDFInfo
- Publication number
- CN111694341A CN111694341A CN202010507882.6A CN202010507882A CN111694341A CN 111694341 A CN111694341 A CN 111694341A CN 202010507882 A CN202010507882 A CN 202010507882A CN 111694341 A CN111694341 A CN 111694341A
- Authority
- CN
- China
- Prior art keywords
- fault
- stored
- priority
- code
- codes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a fault data storage method and device, vehicle-mounted equipment and a storage medium. When a vehicle fault is detected, determining a fault type and a fault priority of each fault code to be stored in the fault type, reading each fault code to be stored and fault information corresponding to each fault code to be stored based on a reading sequence of the fault priority, wherein the fault information comprises a frozen frame and related information of each fault code to be stored, and storing the frozen frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space. The problem of storage quantity limitation caused by overlarge occupied space in a vehicle-mounted fault information storage method in the prior art is solved. By integrating the freeze frames, only the freeze frame corresponding to the fault code to be stored with the highest fault priority is reserved, and the storage space is greatly saved.
Description
Technical Field
The embodiment of the invention relates to an electronic control technology, in particular to a fault data storage method and device, vehicle-mounted equipment and a storage medium.
Background
When an ECU (Electronic Control Unit) in the electric Control system diagnoses faults of the vehicle, various faults occurring in the electric Control system are mainly identified and recorded in the vehicle environment, and various vehicle information and fault states are read by a communication diagnostic instrument through communication buses such as a CAN and an ethernet. In the current vehicle-mounted ECU, a method of reading a DTC (Diagnostic Trouble Code) and its accompanying data such as a Trouble state (current or historical Trouble), a freeze frame (parameters of the entire vehicle when the Trouble occurs), and Trouble additional data (the number of times of Trouble occurrence, the number of times of disappearance, and the like) by a Diagnostic instrument is a main way for technicians in a vehicle sales service shop to analyze, evaluate, reproduce, and repair the Trouble.
Due to the advent of various advanced driving assistance systems and the increasing sophistication of controllers in recent years, the range of diagnostics required for on-board ECUs is continuously expanding, fault codes required to be stored is increasing, and the demand for memory space and for non-volatile memory is increasing. As for most faults of some system on the whole vehicle, a plurality of DTCs of the system are reported simultaneously, and because the additional data corresponding to each DTC is stored independently, the traditional vehicle-mounted ECU diagnostic system can only store 10 DTCs at the same time, so that the use of the diagnostic system by after-sales personnel and technicians is limited, and the requirements of bench test, road test and the like which need large-scale fault processing cannot be met.
In summary, the existing vehicle-mounted fault data storage method has the defect that the storage quantity is limited due to the fact that the occupied space is too large.
Disclosure of Invention
The embodiment of the invention provides a fault data storage method and device, vehicle-mounted equipment and a storage medium, which are used for reducing the storage capacity of fault data and further saving the storage space.
In a first aspect, an embodiment of the present invention provides a method for storing fault data, including:
when a vehicle fault is detected, determining a fault type and a fault priority of each fault code to be stored in the fault type;
reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority, wherein the fault information comprises a freeze frame and related information of each fault code to be stored;
and storing the frozen frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
In a second aspect, an embodiment of the present invention further provides a failure data storage device, including:
the fault type and fault priority determining module is used for determining the fault type and the fault priority of each fault code to be stored in the fault type when the vehicle fault is detected;
the fault data reading module is used for reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority, wherein the fault information comprises a freeze frame and related information of each fault code to be stored;
and the storage module is used for storing the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
In a third aspect, an embodiment of the present invention further provides an on-board device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the fault data storage method according to any one of the first aspect when executing the computer program.
In a fourth aspect, embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor implement the fault data storage method according to any one of the first aspect.
According to the technical scheme provided by the embodiment, when a vehicle fault is detected, the fault type and the fault priority of each fault code to be stored in the fault type are determined, each fault code to be stored and the fault information corresponding to each fault code to be stored are read based on the reading sequence of the fault priority, wherein the fault information comprises the freeze frame and the related information of each fault code to be stored, and the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored are stored in the storage space. The problem of storage quantity limitation caused by overlarge occupied space in a vehicle-mounted fault information storage method in the prior art is solved. By integrating the freeze frames, only the freeze frame corresponding to the fault code to be stored with the highest fault priority is reserved, and the storage space is greatly saved.
Drawings
Fig. 1 is a schematic flowchart of a failure data storage method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a fault data storage method according to a second embodiment of the present invention;
fig. 3a is a schematic diagram of a fault type and fault prioritization principle provided in the second embodiment of the present invention;
fig. 3b is a schematic diagram of another fault type and fault prioritization principle provided in the second embodiment of the present invention;
fig. 4a is a logic diagram of reading and storing information according to a sequence with sequentially increasing fault priorities according to the second embodiment of the present invention;
FIG. 4b is a logic diagram of reading and storing information according to a descending order of priority of failure according to the second embodiment of the present invention;
FIG. 5 is a logic diagram of a second embodiment of the present invention for diagnosing faults by a diagnostic device;
fig. 6 is a schematic structural diagram of a failure data storage device according to a third embodiment of the present invention;
fig. 7 is a schematic structural diagram of an on-board device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
It should be noted that, in the vehicle-mounted electronic control system, the vehicle fault diagnosis and analysis process includes: the method comprises the steps that a vehicle fault is detected through an ECU (Electronic Control Unit), when the ECU detects the vehicle fault, the fault type corresponding to the fault, each fault code in the fault type and relevant information of the fault are identified, the identified fault type, fault code and fault information are recorded, then the recorded data are sent to a diagnostic instrument through a communication bus such as a controller area network or an Ethernet, and the fault code, fault type and fault information are read through the diagnostic instrument, so that technicians of an automobile sales service shop or a whole automobile factory can analyze the fault, repair and the like.
Example one
Fig. 1 is a schematic flow chart of a fault data storage method according to an embodiment of the present invention, where this embodiment is applicable to a case where, when a vehicle fault is detected, a freeze frame corresponding to a fault code to be stored with a highest fault priority and related information of each fault code to be stored are stored in a storage space, and the method may be executed by a fault data storage device, where the device may be implemented by software and/or hardware and is generally integrated in a vehicle-mounted device. Referring specifically to fig. 1, the method may include the steps of:
s110, when the vehicle fault is detected, the fault type and the fault priority of each fault code to be stored in the fault type are determined.
Wherein the type of fault is determined from hardware devices of the vehicle or from the ECU. For example, one failure type is set for the same hardware device, or one failure type is set for one ECU. Each fault type may include a plurality of fault codes. The fault code may be understood as encoded information generated by the ECU for a fault when the exhaust system fails.
In the vehicle-mounted electric control system, before the fault codes and the fault information are stored, the fault types, the fault codes to be stored in the fault types and the fault priority can be predetermined. Optionally, by determining a control target corresponding to each fault code to be stored, determining each fault code to be stored, which is consistent with the control target, as a same fault type, and dividing a fault priority for each fault code to be stored in the same fault type. Further, a fault table can be generated according to the fault code to be stored and the fault priority of the same fault type, and the fault table is stored. The control target may be the above hardware device.
Illustratively, the control target is a brake booster, a fault of the brake booster (including a brake booster short circuit, a brake booster open circuit, a brake booster under-low, and the like) is determined, a to-be-stored fault code is set for each fault (e.g., the to-be-stored fault code of the brake booster short circuit is P0001, the to-be-stored fault code of the brake booster open circuit is P0013, and the to-be-stored fault code of the brake booster under-low is P0015), and the to-be-stored fault codes set for the fault of the brake booster are classified into the same fault type, and a fault priority is generated according to the degree of each fault. For another example, the control target is an atmospheric pressure sensor, the fault of the atmospheric pressure sensor is determined (including the poor signal of the atmospheric pressure sensor and the problem of adjustment of the atmospheric pressure sensor, etc.), a fault code to be stored is set for each fault (for example, the fault code to be stored with the poor signal of the atmospheric pressure sensor is P0105, and the fault code to be stored with the problem of adjustment of the atmospheric pressure sensor is P0106), the fault codes to be stored set for the fault of the atmospheric pressure sensor are divided into the same fault type, and the fault priority is generated according to the degree of each fault.
It is understood that the on-vehicle electronic control system determines the fault type, the fault code to be stored in each fault type, and the fault priority by the above-described manner, and generates the fault table. When an ECU in the vehicle-mounted electric control system detects a vehicle fault, the fault type and the fault priority of each fault code to be stored in the fault type are searched from a fault table according to the detected fault, so that the fault codes to be stored in the fault type can be read orderly according to the determined fault type and the determined fault priority, and fault information is recorded.
And S120, reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority.
The fault information comprises freeze frames and related information of fault codes to be stored. The related information may include fault status (e.g., current and historical fault status) and fault additional data (e.g., number of times the fault occurred and number of times it disappeared), etc. In this embodiment, each fault code to be stored and the corresponding fault information thereof may be read according to the order in which the priority of the fault is gradually decreased, and each fault code to be stored and the corresponding fault information thereof may also be read according to the order in which the priority of the fault is gradually increased. By reading the fault codes to be stored according to the reading sequence of the fault priority, the fault codes to be stored and fault information can be prevented from being omitted, and the probability of analysis errors during subsequent fault analysis is further reduced.
And S130, storing the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
It should be noted that, when the read fault codes and fault information to be stored are stored, the occupancy rate of the freeze frames in the fault information to the storage space is high, and if the freeze frames corresponding to all the read fault codes are stored in the storage space, a large amount of storage space needs to be occupied, but the limited storage space cannot meet the above requirements. To this end, in order to save a storage space, in this embodiment, when the fault code to be stored and the fault information corresponding to each fault code to be stored are read according to the reading sequence of the fault priority, if the fault code to be stored with the highest fault priority is read and no unread fault code to be stored exists in the fault type, the freeze frame of the fault code to be stored with the non-highest fault priority is deleted, the freeze frame of the fault code to be stored with the highest fault priority is retained, and the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored are correspondingly stored in the storage space.
The fault code to be stored with the highest fault priority in this embodiment may be understood as the encoded information corresponding to the most dominant fault in the fault type. As can be seen from the foregoing description, in this embodiment, a classification and priority manner is adopted, and according to the fault priority of the fault code to be stored of the fault type, the freeze frames are integrated, and only the freeze frame of the fault code to be stored with the highest fault priority is retained, so that the storage space is greatly saved, and the storage space in which only a certain amount of fault codes can be originally stored is released to a certain extent, and more fault codes can be stored.
According to the technical scheme provided by the embodiment, when a vehicle fault is detected, the fault type and the fault priority of each fault code to be stored in the fault type are determined, each fault code to be stored and the fault information corresponding to each fault code to be stored are read based on the reading sequence of the fault priority, wherein the fault information comprises the freeze frame and the related information of each fault code to be stored, and the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored are stored in the storage space. The problem of storage quantity limitation caused by overlarge occupied space in a vehicle-mounted fault information storage method in the prior art is solved. By integrating the freeze frames, only the freeze frame corresponding to the fault code to be stored with the highest fault priority is reserved, and the storage space is greatly saved.
Example two
Fig. 2 is a schematic flowchart of a fault data storage method according to a second embodiment of the present invention. The technical scheme of the embodiment adds a new step on the basis of the embodiment. Optionally, the method further comprises: if a diagnosis request sent by a diagnosis instrument is received, determining a fault code to be diagnosed according to the diagnosis request; and determining a target fault type to which the fault code to be diagnosed belongs, determining a target freeze frame of a fault code with the highest fault priority in the target fault types from the storage space, and sending the fault code to be diagnosed and the target freeze frame to the diagnostic instrument. In the method, reference is made to the above-described embodiments for those parts which are not described in detail. Referring specifically to fig. 2, the method may include the steps of:
s210, when the vehicle fault is detected, determining the fault type and the fault priority of each fault code to be stored in the fault type.
Similar to the foregoing embodiment, in the in-vehicle electronic control system, before storing the fault code and the fault information, the fault type, the fault code to be stored in each fault type, and the fault priority may be determined in advance. Fig. 3a and 3b are schematic diagrams of fault type and fault priority classification principles, and with reference to fig. 3a and 3b, an on-board system determines that the fault type of a vehicle includes a fault class 1 and a fault class 2 according to a control target of a fault, and each fault class includes two fault priorities, respectively, where the fault priority 1 of the fault class 1 includes two fault codes DTC1 and DTC2, and the fault priority 2 of the fault class 1 includes a fault code DTC 3; priority 1 of fault class 2 includes fault code DTC4 and priority 2 of fault class 2 includes fault code DTC 5.
And S220, reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority.
As described in the foregoing embodiment, in this embodiment, the fault codes to be stored and the fault information corresponding to the fault codes to be stored may be read according to the order in which the priority of the fault is sequentially decreased, and the fault codes to be stored and the fault information corresponding to the fault codes to be stored may also be read according to the order in which the priority of the fault is sequentially increased.
Specifically, the step of reading each fault code to be stored and the fault information corresponding to each fault code to be stored according to the sequence of sequentially decreasing fault priority includes: sequencing all fault codes to be stored in the fault types according to a descending order of the fault priority in sequence to obtain a first sequencing result, and taking the first sequencing result as a first reading order; and reading the fault codes to be stored with the highest fault priority according to the first reading sequence, analyzing the fault codes to be stored with the highest fault priority, and determining fault information corresponding to the fault codes to be stored with the highest fault priority according to an analysis result until all the fault codes to be stored in the fault type are read.
Specifically, the step of reading each fault code to be stored and the fault information corresponding to each fault code to be stored according to the sequence of sequentially increasing fault priority includes: sorting all fault codes to be stored in the fault types according to the sequence of sequentially increasing fault priorities to obtain a second sorting result, and taking the second sorting result as a second reading sequence; and reading the fault codes to be stored with the lowest fault priority according to the second reading sequence, analyzing the fault codes to be stored with the lowest fault priority, and determining fault information corresponding to the fault codes to be stored with the lowest fault priority according to the analysis result until all the fault codes to be stored in the fault type are read.
And S230, storing the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
Fig. 4a shows a logic diagram of reading and storing information according to an ascending order of the failure priority, and fig. 4b shows a logic diagram of reading and storing information according to a descending order of the failure priority. The steps of reading and storing the freeze frame to be stored and the related information are explained in conjunction with fig. 3a and fig. 4 a. When a fault of a fault class 1 occurs in the vehicle-mounted electronic control system, an ECU reads fault codes DTC1 and fault codes DTC2 with lower priority, analyzes key codes of the fault codes DTC1 through the ECU1 corresponding to the fault codes DTC1, analyzes key codes of the fault codes DTC2 through the ECU2 corresponding to the fault codes DTC2, determines freeze frames and related information corresponding to the fault codes DTC1 according to analysis results, determines freeze frames and related information corresponding to the fault codes DTC2, and temporarily stores the freeze frames and the related information corresponding to the fault codes DTC1 and the fault codes DTC2 to a storage space; further, the ECU reads the fault code DTC3 with higher priority, analyzes the key code of the fault code DTC3 through the ECU3 corresponding to the fault code DTC3, and determines the freeze frame and the related information corresponding to the fault code DTC3 according to the analysis result; further, when the ECU reads all fault codes of the fault class 1, the freeze frames of the fault codes DTC1 and the fault codes DTC2 which are temporarily stored are deleted, the freeze frames corresponding to the fault codes DTC1, the fault codes DTC2, the fault codes DTC3 and the fault codes DTC3 and the related information corresponding to the three fault codes are stored in the storage space, and the freeze frame of the fault code DTC3 can be used as the freeze frame of the fault codes DTC1 and the fault codes DTC 2.
The steps of reading and storing the freeze frame to be stored and the related information are explained in conjunction with fig. 3b and fig. 4 b. When the vehicle-mounted electric control system has a fault of a fault class 2, the ECU reads a fault code DTC5 with a higher priority, analyzes key codes of a fault code DTC5 through an ECU5 corresponding to the fault code DTC5, determines a freeze frame and related information corresponding to the fault code DTC5 according to an analysis result, and temporarily stores the freeze frame and the related information of the fault code DTC5 to a storage space; further, the ECU reads the fault code DTC4 with a lower priority, analyzes the key code of the fault code DTC4 through the ECU4 corresponding to the fault code DTC4, and determines the freeze frame and the related information corresponding to the fault code DTC4 according to the analysis result; further, when the ECU reads all fault codes of the fault class 2, the freeze frame corresponding to the fault code DTC4 stored temporarily is deleted, the freeze frames corresponding to the fault codes DTC4, the fault code DTC5, the fault code DTC5, and the related information corresponding to the two fault codes are stored in the storage space, and the freeze frame of the fault code DTC5 can be used as the freeze frame of the fault code DTC 4.
S240, if a diagnosis request sent by the diagnosis instrument is received, determining a fault code to be diagnosed according to the diagnosis request.
And S250, determining the target fault type to which the fault code to be diagnosed belongs, determining the target freeze frame of the fault code with the highest fault priority in the target fault types from the storage space, and sending the fault code to be diagnosed and the target freeze frame to the diagnostic instrument.
Fig. 5 is a logic diagram for diagnosing a fault by the diagnostic instrument. Optionally, after receiving the diagnosis request, the ECU of the vehicle-mounted electronic control system may retrieve the stored fault code and the freeze frame from the storage space according to the diagnosis request, and feed back the stored fault code and the freeze frame to the diagnostic apparatus, and the diagnostic apparatus receives and displays the data, so that a vehicle technician performs maintenance according to the displayed data.
Specifically, after receiving a diagnosis request, an ECU of the vehicle-mounted electronic control system reads a stored fault code from a storage space, uses the called stored fault code as a fault code to be diagnosed, determines a target fault type to which the fault code to be diagnosed belongs according to a data storage relation in the storage space, determines a fault code with the highest fault priority in the target fault type, uses a freeze frame of the fault code with the highest priority as a target freeze frame, and sends the fault code to be diagnosed and the target freeze frame to a diagnostic instrument. Therefore, after the diagnostic instrument receives the data, the frozen frame of the fault code with the highest fault priority can be highlighted, and the problem that technicians cannot process main faults is avoided.
In this embodiment, if the stored fault codes in the storage space exceed the preset storage number and the fault priority of the fault codes to be stored is not the lowest priority, the stored fault codes which belong to the same fault type and have the lowest priority with the fault codes to be stored in the storage space are deleted. By the method, the effect of further saving the storage space can be realized while key information is kept.
According to the technical scheme provided by the embodiment, if a diagnosis request sent by a diagnosis instrument is received, the fault code to be diagnosed is determined according to the diagnosis request, the target fault type to which the fault code to be diagnosed belongs is determined, the target freeze frame of the fault code with the highest fault priority in the target fault type is determined from the storage space, and the fault code to be diagnosed and the target freeze frame are sent to the diagnosis instrument. The frozen frame corresponding to the fault code with the highest fault priority can be highlighted, and the problem that technicians cannot process main faults is avoided. In addition, the stored fault codes which belong to the same fault type and have the lowest priority with the fault codes to be stored in the storage space are deleted, so that the effect of further saving the storage space while maintaining the key information can be realized.
EXAMPLE III
Fig. 6 is a schematic structural diagram of a failure data storage device according to a third embodiment of the present invention. Referring to fig. 6, the apparatus includes: a failure type and failure priority determination module 31, a failure data reading module 32, and a storage module 33.
The fault type and fault priority determining module 31 is configured to determine a fault type and a fault priority of each fault code to be stored in the fault type when a vehicle fault is detected;
a fault data reading module 32, configured to read each to-be-stored fault code and fault information corresponding to each to-be-stored fault code based on a reading sequence of the fault priority, where the fault information includes a freeze frame and related information of each to-be-stored fault code;
the storage module 33 is configured to store the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored in the storage space.
On the basis of the above technical solutions, the storage module 33 is further configured to, if a fault code to be stored with the highest fault priority is read and an unread fault code to be stored does not exist in the fault type, delete the freeze frame of the fault code to be stored with the non-highest fault priority, retain the freeze frame of the fault code to be stored with the highest fault priority, and correspondingly store the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored in the storage space.
On the basis of the above technical solutions, the apparatus further includes: a dividing module; the dividing module is configured to determine a control target corresponding to each fault code to be stored, determine each fault code to be stored with the same control target as the same fault type, and divide a fault priority for each fault code to be stored in the same fault type.
On the basis of the above technical solutions, the fault data reading module 32 is further configured to sort the fault codes to be stored in the fault type according to a sequence in which the fault priority is sequentially decreased to obtain a first sorting result, and use the first sorting result as a first reading sequence;
and reading the fault codes to be stored with the highest fault priority according to the first reading sequence, analyzing the fault codes to be stored with the highest fault priority, and determining fault information corresponding to the fault codes to be stored with the highest fault priority according to an analysis result until all the fault codes to be stored in the fault type are read.
On the basis of the above technical solutions, the fault data reading module 32 is further configured to sort the fault codes to be stored in the fault type according to a sequence in which the fault priorities are sequentially increased to obtain a second sorting result, and use the second sorting result as a second reading sequence;
and reading the fault codes to be stored with the lowest fault priority according to the second reading sequence, analyzing the fault codes to be stored with the lowest fault priority, and determining fault information corresponding to the fault codes to be stored with the lowest fault priority according to an analysis result until all the fault codes to be stored in the fault type are read.
On the basis of the above technical solutions, the apparatus further includes: a diagnostic request receiving module; the diagnostic request receiving module is used for determining a fault code to be diagnosed according to a diagnostic request if the diagnostic request sent by a diagnostic instrument is received;
and determining a target fault type to which the fault code to be diagnosed belongs, determining a target freeze frame of a fault code with the highest fault priority in the target fault types from the storage space, and sending the fault code to be diagnosed and the target freeze frame to the diagnostic instrument.
On the basis of the above technical solutions, the apparatus further includes: a deletion module; and the deleting module is used for deleting the stored fault codes which belong to the same fault type and have the lowest priority with the fault codes to be stored in the storage space if the stored fault codes in the storage space exceed the preset storage quantity and the fault priority of the fault codes to be stored is not the lowest priority.
According to the technical scheme provided by the embodiment, when a vehicle fault is detected, the fault type and the fault priority of each fault code to be stored in the fault type are determined, each fault code to be stored and the fault information corresponding to each fault code to be stored are read based on the reading sequence of the fault priority, wherein the fault information comprises the freeze frame and the related information of each fault code to be stored, and the frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored are stored in the storage space. The problem of storage quantity limitation caused by overlarge occupied space in a vehicle-mounted fault information storage method in the prior art is solved. By integrating the freeze frames, only the freeze frame corresponding to the fault code to be stored with the highest fault priority is reserved, and the storage space is greatly saved.
Example four
Fig. 7 is a schematic structural diagram of an on-board device according to a fourth embodiment of the present invention. FIG. 7 illustrates a block diagram of an exemplary vehicle-mounted device 12 suitable for use in implementing embodiments of the present invention. The in-vehicle apparatus 12 shown in fig. 7 is merely an example, and should not bring any limitation to the function and the range of use of the embodiment of the present invention.
As shown in fig. 7, the in-vehicle apparatus 12 is represented in the form of a general-purpose computing apparatus. Components of the in-vehicle device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
The in-vehicle device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by in-vehicle device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The in-vehicle device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 7, and commonly referred to as a "hard drive"). Although not shown in FIG. 7, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set of program modules (e.g., failure type and failure priority determination module 31, failure data reading module 32, and storage module 33 for a failure data storage device) configured to perform the functions of embodiments of the present invention.
A program/utility 44 having a set of program modules 46 (e.g., fault type and fault priority determination module 31, fault data reading module 32, and storage module 33 of a fault data storage device) may be stored, for example, in memory 28, such program modules 46 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may include an implementation of a network environment. Program modules 46 generally carry out the functions and/or methodologies of the described embodiments of the invention.
In-vehicle device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with in-vehicle device 12, and/or with any devices (e.g., network card, modem, etc.) that enable in-vehicle device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the in-vehicle device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with the other modules of the in-vehicle device 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the in-vehicle device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, implementing a fault data storage method provided by an embodiment of the present invention, the method including:
when a vehicle fault is detected, determining a fault type and a fault priority of each fault code to be stored in the fault type;
reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority, wherein the fault information comprises a freeze frame and related information of each fault code to be stored;
and storing the frozen frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement a fault data storage method provided by an embodiment of the present invention.
Of course, those skilled in the art can understand that the processor may also implement the technical solution of the failure data storage method provided by any embodiment of the present invention.
EXAMPLE five
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a fault data storage method provided in an embodiment of the present invention, where the method includes:
when a vehicle fault is detected, determining a fault type and a fault priority of each fault code to be stored in the fault type;
reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority, wherein the fault information comprises a freeze frame and related information of each fault code to be stored;
and storing the frozen frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
Of course, the computer program stored on the computer-readable storage medium provided by the embodiment of the present invention is not limited to the above method operations, and may also perform related operations in a fault data storage method provided by any embodiment of the present invention.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device.
A computer readable signal medium may include a computer readable program code embodied therein to store a fault code, store a freeze frame and associated information, and the like. The propagated fault codes to be stored, the freeze frames and related information are stored and the like. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It should be noted that, in the embodiment of the failure data storage device, the modules included in the embodiment are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. 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, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method of fault data storage, comprising:
when a vehicle fault is detected, determining a fault type and a fault priority of each fault code to be stored in the fault type;
reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority, wherein the fault information comprises a freeze frame and related information of each fault code to be stored;
and storing the frozen frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
2. The method according to claim 1, wherein the storing the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space comprises:
and if the fault code to be stored with the highest fault priority is read and the fault type does not have the unread fault code to be stored, deleting the freeze frame of the fault code to be stored with the highest fault priority, reserving the freeze frame of the fault code to be stored with the highest fault priority, and correspondingly storing the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored to the storage space.
3. The method of claim 1, wherein prior to the determining the fault type and the fault priority of each fault code to be stored in the fault type, the method further comprises:
determining a control target corresponding to each fault code to be stored, determining each fault code to be stored with the same control target as the same fault type, and dividing the fault priority of each fault code to be stored in the same fault type.
4. The method according to claim 1, wherein the reading the fault information corresponding to each fault code to be stored and each fault code to be stored based on the reading order of the fault priority includes:
sequencing the fault codes to be stored in the fault type according to a sequence of sequentially decreasing fault priority to obtain a first sequencing result, and taking the first sequencing result as a first reading sequence;
and reading the fault codes to be stored with the highest fault priority according to the first reading sequence, analyzing the fault codes to be stored with the highest fault priority, and determining fault information corresponding to the fault codes to be stored with the highest fault priority according to an analysis result until all the fault codes to be stored in the fault type are read.
5. The method according to claim 1, wherein the reading the fault information corresponding to each fault code to be stored and each fault code to be stored based on the reading order of the fault priority includes:
sorting the fault codes to be stored in the fault type according to a sequence of sequentially increasing fault priorities to obtain a second sorting result, and taking the second sorting result as a second reading sequence;
and reading the fault codes to be stored with the lowest fault priority according to the second reading sequence, analyzing the fault codes to be stored with the lowest fault priority, and determining fault information corresponding to the fault codes to be stored with the lowest fault priority according to an analysis result until all the fault codes to be stored in the fault type are read.
6. The method of claim 1, further comprising:
if a diagnosis request sent by a diagnosis instrument is received, determining a fault code to be diagnosed according to the diagnosis request;
and determining a target fault type to which the fault code to be diagnosed belongs, determining a target freeze frame of a fault code with the highest fault priority in the target fault types from the storage space, and sending the fault code to be diagnosed and the target freeze frame to the diagnostic instrument.
7. The method of claim 1, further comprising:
and if the stored fault codes in the storage space exceed the preset storage quantity and the fault priority of the fault codes to be stored is not the lowest priority, deleting the stored fault codes which belong to the same fault type and have the lowest priority in the storage space.
8. A failure data storage device, comprising:
the fault type and fault priority determining module is used for determining the fault type and the fault priority of each fault code to be stored in the fault type when the vehicle fault is detected;
the fault data reading module is used for reading each fault code to be stored and fault information corresponding to each fault code to be stored based on the reading sequence of the fault priority, wherein the fault information comprises a freeze frame and related information of each fault code to be stored;
and the storage module is used for storing the freeze frame of the fault code to be stored with the highest fault priority and the related information of each fault code to be stored into a storage space.
9. An in-vehicle apparatus comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the fault data storage method according to any one of claims 1 to 7 when executing the computer program.
10. A storage medium containing computer-executable instructions, which when executed by a computer processor implement the fault data storage method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010507882.6A CN111694341A (en) | 2020-06-05 | 2020-06-05 | Fault data storage method and device, vehicle-mounted equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010507882.6A CN111694341A (en) | 2020-06-05 | 2020-06-05 | Fault data storage method and device, vehicle-mounted equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111694341A true CN111694341A (en) | 2020-09-22 |
Family
ID=72479557
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010507882.6A Pending CN111694341A (en) | 2020-06-05 | 2020-06-05 | Fault data storage method and device, vehicle-mounted equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111694341A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112254983A (en) * | 2020-10-16 | 2021-01-22 | 中国第一汽车股份有限公司 | Vehicle detection method, device, equipment and storage medium |
| CN112650203A (en) * | 2020-12-31 | 2021-04-13 | 大运汽车股份有限公司 | Fault processing and diagnosis control strategy suitable for new energy automobile |
| CN112684779A (en) * | 2020-12-25 | 2021-04-20 | 长城汽车股份有限公司 | Vehicle fault detection method, system, storage medium and electronic device |
| CN113110371A (en) * | 2021-03-16 | 2021-07-13 | 佛山市飞驰汽车科技有限公司 | Vehicle fault code storage and transmission system and method |
| CN113359661A (en) * | 2021-05-12 | 2021-09-07 | 江铃汽车股份有限公司 | Vehicle fault detection method and system and automobile |
| CN113482773A (en) * | 2021-07-05 | 2021-10-08 | 无锡威孚高科技集团股份有限公司 | Fault management method and device for electric control system of off-road diesel engine |
| CN113762341A (en) * | 2021-08-06 | 2021-12-07 | 中国重汽集团济南动力有限公司 | Vehicle fault priority calculation method and system |
| CN113900425A (en) * | 2021-10-12 | 2022-01-07 | 柳州赛克科技发展有限公司 | Method and system for reading and analyzing fault information of controller |
| CN114137932A (en) * | 2021-11-11 | 2022-03-04 | 上汽通用五菱汽车股份有限公司 | Vehicle diagnosis method, vehicle control unit, vehicle and readable storage medium |
| CN114384887A (en) * | 2020-10-16 | 2022-04-22 | 长城汽车股份有限公司 | Emission diagnosis method and device and electronic equipment |
| CN114779747A (en) * | 2022-05-11 | 2022-07-22 | 中国第一汽车股份有限公司 | Vehicle fault cause determination system and method |
| CN115410292A (en) * | 2022-07-29 | 2022-11-29 | 成都赛力斯科技有限公司 | Vehicle fault analysis method and device, computer equipment and storage medium |
| WO2023071961A1 (en) * | 2021-10-26 | 2023-05-04 | 中国第一汽车股份有限公司 | Fault code storage method and apparatus, and device and storage medium |
| WO2024017072A1 (en) * | 2022-07-18 | 2024-01-25 | 中国第一汽车股份有限公司 | Vehicle fault information processing method and device, storage medium, and processor |
Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20090062428A (en) * | 2007-12-13 | 2009-06-17 | 현대자동차주식회사 | Fault information processing system and method for vehicle |
| CN101566852A (en) * | 2008-04-25 | 2009-10-28 | 通用汽车环球科技运作公司 | Control system and method for filtering dependent diagnostic trouble codes |
| CN101660974A (en) * | 2008-08-29 | 2010-03-03 | 丰田自动车株式会社 | Abnormality analysis system for vehicle and abnormality analysis method for vehicle |
| WO2010067547A1 (en) * | 2008-12-10 | 2010-06-17 | 本田技研工業株式会社 | Vehicle failure diagnostic device |
| CN101923348A (en) * | 2010-07-16 | 2010-12-22 | 北京工业大学 | Vehicle-mounted fault diagnosis system and method for hybrid electric vehicle based on CANopen |
| CN101981593A (en) * | 2008-03-25 | 2011-02-23 | 丰田自动车株式会社 | Abnormality detection device, abnormality information transmission method, and abnormality information transmission system |
| WO2012092622A2 (en) * | 2010-12-31 | 2012-07-05 | Nest Labs, Inc. | Inhibiting deleterious control coupling in an enclosure having multiple hvac regions |
| CN102620932A (en) * | 2012-03-28 | 2012-08-01 | 奇瑞汽车股份有限公司 | Online fault diagnosis prediction method and device thereof of automatic gearbox |
| WO2013052389A1 (en) * | 2011-10-07 | 2013-04-11 | Nest Labs, Inc. | Hvac controller with user-friendly installation features facilitating both do-it-yourself and professional installation scenarios |
| US20130103207A1 (en) * | 2010-11-19 | 2013-04-25 | Nest Labs, Inc. | Adjusting proximity thresholds for activating a device user interface |
| US20130204485A1 (en) * | 2008-04-14 | 2013-08-08 | Ieon C. Chen | Handheld Scan Tool with Fixed Solution Capability |
| CN103902746A (en) * | 2014-03-11 | 2014-07-02 | 深圳市元征科技股份有限公司 | Fault code, data stream and freeze frame data storage and playback method |
| US20140358358A1 (en) * | 2013-06-03 | 2014-12-04 | Honda Motor Co., Ltd. | Driving analytics |
| CN104512422A (en) * | 2013-09-26 | 2015-04-15 | 广州汽车集团股份有限公司 | Fault processing method and fault processing system of hybrid electric car |
| US9298196B2 (en) * | 2010-11-19 | 2016-03-29 | Google Inc. | Energy efficiency promoting schedule learning algorithms for intelligent thermostat |
| CN106408684A (en) * | 2016-09-30 | 2017-02-15 | 北京新能源汽车股份有限公司 | Fault information storage method and device |
| CN109901560A (en) * | 2019-04-04 | 2019-06-18 | 奇瑞新能源汽车技术有限公司 | A kind of storage method of new-energy automobile power drive system fail frost frame |
| CN110515366A (en) * | 2019-07-29 | 2019-11-29 | 华为技术有限公司 | A kind of method for diagnosing faults and device |
| CN110647137A (en) * | 2019-09-30 | 2020-01-03 | 深圳市元征科技股份有限公司 | Method, device, equipment and medium for acquiring frozen frame data |
| CN110851415A (en) * | 2019-11-13 | 2020-02-28 | 广州小鹏汽车科技有限公司 | Log data processing method and device of vehicle-mounted system |
| CN110850853A (en) * | 2020-01-14 | 2020-02-28 | 盛瑞传动股份有限公司 | Frozen frame reading method based on CANape tool |
-
2020
- 2020-06-05 CN CN202010507882.6A patent/CN111694341A/en active Pending
Patent Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20090062428A (en) * | 2007-12-13 | 2009-06-17 | 현대자동차주식회사 | Fault information processing system and method for vehicle |
| CN101981593A (en) * | 2008-03-25 | 2011-02-23 | 丰田自动车株式会社 | Abnormality detection device, abnormality information transmission method, and abnormality information transmission system |
| US20130204485A1 (en) * | 2008-04-14 | 2013-08-08 | Ieon C. Chen | Handheld Scan Tool with Fixed Solution Capability |
| US8909416B2 (en) * | 2008-04-14 | 2014-12-09 | Innova Electronics, Inc. | Handheld scan tool with fixed solution capability |
| CN101566852A (en) * | 2008-04-25 | 2009-10-28 | 通用汽车环球科技运作公司 | Control system and method for filtering dependent diagnostic trouble codes |
| CN101660974A (en) * | 2008-08-29 | 2010-03-03 | 丰田自动车株式会社 | Abnormality analysis system for vehicle and abnormality analysis method for vehicle |
| WO2010067547A1 (en) * | 2008-12-10 | 2010-06-17 | 本田技研工業株式会社 | Vehicle failure diagnostic device |
| CN101923348A (en) * | 2010-07-16 | 2010-12-22 | 北京工业大学 | Vehicle-mounted fault diagnosis system and method for hybrid electric vehicle based on CANopen |
| US9298196B2 (en) * | 2010-11-19 | 2016-03-29 | Google Inc. | Energy efficiency promoting schedule learning algorithms for intelligent thermostat |
| US20130103207A1 (en) * | 2010-11-19 | 2013-04-25 | Nest Labs, Inc. | Adjusting proximity thresholds for activating a device user interface |
| WO2012092622A2 (en) * | 2010-12-31 | 2012-07-05 | Nest Labs, Inc. | Inhibiting deleterious control coupling in an enclosure having multiple hvac regions |
| WO2013052389A1 (en) * | 2011-10-07 | 2013-04-11 | Nest Labs, Inc. | Hvac controller with user-friendly installation features facilitating both do-it-yourself and professional installation scenarios |
| CN102620932A (en) * | 2012-03-28 | 2012-08-01 | 奇瑞汽车股份有限公司 | Online fault diagnosis prediction method and device thereof of automatic gearbox |
| US20140358358A1 (en) * | 2013-06-03 | 2014-12-04 | Honda Motor Co., Ltd. | Driving analytics |
| CN104512422A (en) * | 2013-09-26 | 2015-04-15 | 广州汽车集团股份有限公司 | Fault processing method and fault processing system of hybrid electric car |
| CN104512422B (en) * | 2013-09-26 | 2017-06-06 | 广州汽车集团股份有限公司 | Hybrid electric vehicle fault handling method and its fault processing system |
| CN103902746A (en) * | 2014-03-11 | 2014-07-02 | 深圳市元征科技股份有限公司 | Fault code, data stream and freeze frame data storage and playback method |
| CN106408684A (en) * | 2016-09-30 | 2017-02-15 | 北京新能源汽车股份有限公司 | Fault information storage method and device |
| CN109901560A (en) * | 2019-04-04 | 2019-06-18 | 奇瑞新能源汽车技术有限公司 | A kind of storage method of new-energy automobile power drive system fail frost frame |
| CN110515366A (en) * | 2019-07-29 | 2019-11-29 | 华为技术有限公司 | A kind of method for diagnosing faults and device |
| CN110647137A (en) * | 2019-09-30 | 2020-01-03 | 深圳市元征科技股份有限公司 | Method, device, equipment and medium for acquiring frozen frame data |
| CN110851415A (en) * | 2019-11-13 | 2020-02-28 | 广州小鹏汽车科技有限公司 | Log data processing method and device of vehicle-mounted system |
| CN110850853A (en) * | 2020-01-14 | 2020-02-28 | 盛瑞传动股份有限公司 | Frozen frame reading method based on CANape tool |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112254983A (en) * | 2020-10-16 | 2021-01-22 | 中国第一汽车股份有限公司 | Vehicle detection method, device, equipment and storage medium |
| CN114384887A (en) * | 2020-10-16 | 2022-04-22 | 长城汽车股份有限公司 | Emission diagnosis method and device and electronic equipment |
| CN112684779A (en) * | 2020-12-25 | 2021-04-20 | 长城汽车股份有限公司 | Vehicle fault detection method, system, storage medium and electronic device |
| CN112684779B (en) * | 2020-12-25 | 2022-07-05 | 长城汽车股份有限公司 | Vehicle fault detection method, system, storage medium and electronic device |
| CN112650203A (en) * | 2020-12-31 | 2021-04-13 | 大运汽车股份有限公司 | Fault processing and diagnosis control strategy suitable for new energy automobile |
| CN112650203B (en) * | 2020-12-31 | 2023-09-26 | 大运汽车股份有限公司 | Fault processing and diagnosis control strategy suitable for new energy automobile |
| CN113110371A (en) * | 2021-03-16 | 2021-07-13 | 佛山市飞驰汽车科技有限公司 | Vehicle fault code storage and transmission system and method |
| CN113359661A (en) * | 2021-05-12 | 2021-09-07 | 江铃汽车股份有限公司 | Vehicle fault detection method and system and automobile |
| CN113482773A (en) * | 2021-07-05 | 2021-10-08 | 无锡威孚高科技集团股份有限公司 | Fault management method and device for electric control system of off-road diesel engine |
| CN113482773B (en) * | 2021-07-05 | 2022-05-31 | 无锡威孚高科技集团股份有限公司 | Fault management method and device for electric control system of off-road diesel engine |
| CN113762341A (en) * | 2021-08-06 | 2021-12-07 | 中国重汽集团济南动力有限公司 | Vehicle fault priority calculation method and system |
| CN113900425A (en) * | 2021-10-12 | 2022-01-07 | 柳州赛克科技发展有限公司 | Method and system for reading and analyzing fault information of controller |
| CN113900425B (en) * | 2021-10-12 | 2024-02-27 | 柳州赛克科技发展有限公司 | Method and system for reading and analyzing fault information of controller |
| WO2023071961A1 (en) * | 2021-10-26 | 2023-05-04 | 中国第一汽车股份有限公司 | Fault code storage method and apparatus, and device and storage medium |
| CN114137932A (en) * | 2021-11-11 | 2022-03-04 | 上汽通用五菱汽车股份有限公司 | Vehicle diagnosis method, vehicle control unit, vehicle and readable storage medium |
| CN114779747A (en) * | 2022-05-11 | 2022-07-22 | 中国第一汽车股份有限公司 | Vehicle fault cause determination system and method |
| WO2024017072A1 (en) * | 2022-07-18 | 2024-01-25 | 中国第一汽车股份有限公司 | Vehicle fault information processing method and device, storage medium, and processor |
| CN115410292A (en) * | 2022-07-29 | 2022-11-29 | 成都赛力斯科技有限公司 | Vehicle fault analysis method and device, computer equipment and storage medium |
| CN115410292B (en) * | 2022-07-29 | 2023-10-27 | 成都赛力斯科技有限公司 | Vehicle fault analysis method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111694341A (en) | Fault data storage method and device, vehicle-mounted equipment and storage medium | |
| CN108563214B (en) | Vehicle diagnosis method, device and equipment | |
| US6115656A (en) | Fault recording and reporting method | |
| CN112436968B (en) | Network traffic monitoring method, device, equipment and storage medium | |
| CN109213132B (en) | Method, device and equipment for generating UDS (Universal description System) diagnosis interface software | |
| CN114490161B (en) | Fault diagnosis method and device, vehicle and storage medium | |
| CN112798951A (en) | Fault processing method and device, electronic equipment and storage medium | |
| CN110191021B (en) | Protocol testing method and device, electronic equipment and storage medium | |
| CN110912964A (en) | Vehicle mileage backup system, method, device, electronic equipment and medium | |
| CN114374565A (en) | Intrusion detection method and device for vehicle CAN network, electronic equipment and medium | |
| CN111290881B (en) | Data recovery method, device, equipment and storage medium | |
| CN113808299A (en) | Vehicle fault snapshot storage method, device and equipment based on fault system | |
| CN111274130A (en) | Automatic testing method, device, equipment and storage medium | |
| CN114407812A (en) | Diagnostic database determination method, diagnostic database determination device, electronic equipment and storage medium | |
| US20150379788A1 (en) | Method for managing fault messages of a motor vehicle | |
| CN110281710B (en) | Identification method, device, equipment and storage medium of tire pressure sensor | |
| CN111784176A (en) | Data processing method, device, server and medium | |
| CN115550265A (en) | Vehicle-mounted network communication event filtering method, device, equipment and medium | |
| CN114489509A (en) | Video storage method and device of automobile data recorder, electronic equipment and storage medium | |
| CN113342430A (en) | Fault code processing method and device, terminal equipment and readable storage medium | |
| KR100977314B1 (en) | Method and apparatus for managing a data of network | |
| CN113094000A (en) | Vehicle signal storage method and device, storage equipment and storage medium | |
| CN113127710A (en) | Information presentation method, device, server and medium | |
| CN114338454B (en) | Network communication quality detection method, system, train display screen and storage medium | |
| CN112818204A (en) | Service processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200922 |