Vehicle can bus fault monitoring method, system and device

Abstract

The invention discloses a vehicle can bus fault monitoring method, system and device, and belongs to the technical field of vehicles. The monitoring method comprises the following steps: acquiring current message data of a can bus of a target vehicle in real time and recording the current message data; calling and analyzing the historical message data to obtain abnormal message data; and selecting the abnormal message data for playback to obtain vehicle problem data. After the current message data of the can bus of the target vehicle is acquired and recorded and the historical message data is called and analyzed, the abnormal message data can be found and played back, so that the vehicle problem occurrence environment can be reproduced, the problem can be solved, meanwhile, the possible cause of the problem can be checked fundamentally, and the problem can be effectively solved. And the problem that accidental problems are difficult to reproduce is solved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a vehicle CAN bus fault monitoring method, system and device. Background Art

[0002] With the development of new energy vehicles, the degree of vehicle intelligent networking continues to improve, the number of vehicle controllers continues to increase, and the number of vehicle CAN networks and CAN bus messages has grown several times. In the process of vehicle function development, the first step in troubleshooting is often to obtain bus message information, find out which controller is the source of the problem through fault codes, and then further analyze the problem controller to find a solution, but this method cannot fundamentally analyze the possible points of the problem. Summary of the invention

[0003] The purpose of the present invention is to provide a vehicle CAN bus fault monitoring method, system and device to solve one or more technical problems existing in the prior art and at least provide a beneficial choice or create conditions.

[0004] A technical solution adopted to solve the above technical problems provides a vehicle CAN bus fault monitoring method, including: acquiring the current message data of the target vehicle CAN bus in real time and recording it; retrieving historical message data and analyzing the historical message data to obtain abnormal message data, wherein the historical message data is the recorded current message data; selecting the abnormal message data for playback to obtain vehicle problem data.

[0005] This technical solution has at least the following beneficial effects: by acquiring and recording the current message data of the target vehicle CAN bus, after retrieving and analyzing the historical message data, abnormal message data can be discovered, and by replaying the abnormal message data, vehicle problem data that may have problems can be acquired to facilitate reproducing the environment in which the vehicle problem occurred and help solve the problem. At the same time, it can fundamentally troubleshoot possible causes of the problem and solve the problem that occasional problems are difficult to reproduce.

[0006] Optionally, the retrieval of historical message data and analysis of the historical message data includes: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; and determining the historical message data at the time when the fault occurred as the abnormal message data. When recording the current message data of the target vehicle's CAN bus in real time, by sending diagnostic messages and receiving response messages, the new fault detected by the target vehicle is learned, and the time when the new fault occurred is recorded. Based on this time when the fault occurred, the current message data at the time of the fault is played back, which can realize the simulation of the working conditions under the vehicle fault condition to quickly reproduce the problem.

[0007] Optionally, the retrieving and analyzing the historical message data includes: obtaining standard network file data; comparing the standard network file data with the historical message data to obtain abnormal message data, wherein the abnormal message data is data in the historical message data that is inconsistent with the standard network file data. By comparing the standard network file data with the historical message data stored in the actual vehicle, it is possible to verify which message information is inconsistent with the design when the problem occurs, and accurately identify the faulty part.

[0008] Optionally, the comparison of the standard network file data and the historical message data includes: analyzing the message identification number, message sending cycle and message length information in the standard network file data to form a first message information table; analyzing the message identification number, message sending cycle and message length information in the historical message data to form a second message information table; comparing the first message information table with the second message information table to obtain abnormal message data, wherein the abnormal message data is inconsistent data in the first message information table and the second message information table. By comparing the message identification number, message sending cycle and message length information of the standard network file data and the historical message data, it is easy to verify which message information does not conform to the design and quickly lock the faulty part.

[0009] Optionally, retrieving historical message data and analyzing the historical message data includes: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; obtaining standard network file data; comparing the standard network file data with the historical message data at the time when the fault occurred; and determining the data in the historical message data at the time when the fault occurred that is inconsistent with the standard network file data as the abnormal message data. According to the fault recorded by the target vehicle, by comparing the consistency of the current message data at the time when the fault occurred with the standard network file data, the faulty component can be quickly and accurately locked.

[0010] Optionally, the real-time acquisition and recording of the message data of the target vehicle includes: when the OBD interface of the target vehicle is connected, the real-time acquisition and recording of the current message data of the CAN bus of the target vehicle improves the operation efficiency.

[0011] A vehicle CAN bus fault monitoring system includes: an acquisition module, used to: acquire the current message data of the target vehicle CAN bus in real time and record it; a data analysis module, used to: retrieve historical message data and analyze the historical message data to obtain abnormal message data, wherein the historical message data is the recorded current message data; and select the abnormal message data for playback to obtain vehicle problem data.

[0012] Optionally, the data analysis module is also used to: send a diagnostic message to the target vehicle and receive a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, record the time when the new fault occurred; and determine the historical message data at the time when the fault occurred as the abnormal message data.

[0013] A device comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute any one of the above-mentioned vehicle CAN bus fault monitoring methods.

[0014] A computer-readable storage medium stores a computer program, wherein the computer program is configured to execute any of the above-mentioned vehicle CAN bus fault monitoring methods when running on a computer or a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0016] Figure 1 A flow chart of a vehicle CAN bus fault monitoring method according to an embodiment of the present invention;

[0017] Figure 2 A schematic diagram of a specific process of a vehicle CAN bus fault monitoring method according to an embodiment of the present invention;

[0018] Figure 3 It is a structural block diagram of a vehicle CAN bus fault monitoring method according to an embodiment of the present invention;

[0019] Figure 4 A flow chart of recording the time of occurrence of a fault in a vehicle CAN bus fault monitoring method according to an embodiment of the present invention;

[0020] Figure 5 It is a schematic diagram of the historical CAN message data analysis process in the vehicle CAN bus fault monitoring method according to an embodiment of the present invention;

[0021] Figure 6This is a structural block diagram of another embodiment of the vehicle CAN bus fault monitoring method of the embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] According to an embodiment of the present invention, an embodiment of a vehicle CAN bus fault monitoring method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system containing at least one set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0025] The method embodiment can also be executed in an electronic system / device including a memory and a processor, a similar control system or a cloud. Taking an electronic system / device as an example, the electronic system / device may include one or more processors and a memory for storing data. Optionally, the above-mentioned electronic system / device may also include a communication device and a display device for communication functions. It can be understood by those of ordinary skill in the art that the above-mentioned structural description is only illustrative and does not limit the structure of the above-mentioned electronic system / device. For example, the electronic system / device may also include more or fewer components than the above-mentioned structural description, or have a configuration different from the above-mentioned structural description.

[0026] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a field-programmable gate array (FPGA), a neural network processor (NPU), a tensor processing unit (TPU), an artificial intelligence (AI) type processor, and the like. Among them, different processing units may be independent components or integrated into one or more processors. In some instances, the electronic system may also include one or more processors.

[0027] The memory can be used to store computer programs, such as storing the computer program corresponding to the vehicle control method in the embodiment of the present invention, and the processor implements the above-mentioned vehicle control method by running the computer program stored in the memory. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include a memory remotely arranged relative to the processor, and these remote memories can be connected to the electronic system via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0028] like Figure 1-2 As shown, a vehicle CAN bus fault monitoring method includes the following steps:

[0029] Step S100, obtaining and recording the current message data of the target vehicle CAN bus in real time.

[0030] Specifically, CAN bus (Controller Area Network) is a controller local area network. During the use of the target vehicle, the CAN bus is used to transmit data between different components, namely, CAN bus message data. By obtaining and recording the message data of the CAN bus of the target vehicle, namely, the current message data, the transmission data between different components on the CAN bus can be understood.

[0031] Step S200, retrieve and analyze historical message data to obtain abnormal message data, where the historical message data is the recorded current message data.

[0032] Specifically, by analyzing historical message data and analyzing transmission data between different components on the CAN bus, abnormal message data can be found as abnormal message data.

[0033] Step S300, selecting abnormal message data for playback to obtain vehicle problem data.

[0034] Specifically, the abnormal message data found is replayed. Based on the replayed abnormal message data, the environment in which the vehicle problem occurs can be reproduced to help solve the problem. At the same time, the possible causes of the problem can be intelligently checked, and the problem that occasional problems are difficult to reproduce can be solved, thereby achieving a fundamental analysis of possible problem points.

[0035] Optionally, step S200 includes step S210: retrieving historical message data and analyzing the historical message data, including: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; and determining the historical message data at the time when the fault occurred as abnormal message data.

[0036] Specifically, when a connection is established with the OBD interface of the target vehicle, the current message data of the CAN bus can be automatically acquired and recorded in real time. During the recording process, a 19 02FF diagnostic message will be sent synchronously to record the fault information, that is, the fault code (DTC) of the target vehicle. If the vehicle response message indicates that a new fault has occurred in the vehicle, the time when the new fault occurred is recorded. The current message data at the time of the fault may have abnormal problems. The current message data of the CAN bus at the time of the fault is retrieved from the historical message data and marked as abnormal message data. The abnormal message data is selected for playback, so that the faulty component can be accurately locked.

[0037] Optionally, step S200 includes step S220: retrieving historical message data and analyzing the historical message data, including: obtaining standard network file data; comparing the standard network file data and the historical message data to obtain abnormal message data, wherein the abnormal message data is data in the historical message data that is inconsistent with the standard network file data.

[0038] Specifically, the standard network file data, namely the dbc (Database CAN) file data, is a file used to describe the data format in the controller area network. The standard network file data records the message information defined by the vehicle network designer. By importing the standard network file data and comparing the standard network dbc file data designed by the vehicle designer with the historical message data recorded by the actual vehicle, it is possible to verify which message information does not conform to the design when the problem occurs, accurately identify the faulty part, and solve the problem of difficulty in troubleshooting the real cause of the problem after recurrence.

[0039] Optionally, in another embodiment, step S220 includes step S221: comparing standard network file data and historical message data includes: analyzing the message identification number, message sending cycle and message length information in the standard network file data to form a first message information table; analyzing the message identification number, message sending cycle and message length information in the historical message data to form a second message information table; comparing the first message information table and the second message information table to obtain abnormal message data, wherein the abnormal message data is inconsistent data in the first message information table and the second message information table.

[0040] Specifically, after obtaining the dbc file data, the message identification number, message sending cycle and message length information in the standard network file data are analyzed to form a first message information table. The message identification number, message sending cycle and message length information in the historical message data are analyzed to form a second message information table. By comparing the first message information table and the second message information table, any one or more of the message identification number, message sending cycle and message length information in the second message information table that are inconsistent with the first message information table are stored in the third message information table as suspicious data, so that abnormal message data can be obtained from the third message information table, and the abnormal message data can be selected for playback, so that the faulty part can be accurately locked.

[0041] In other embodiments, the first message information table may also extract other information such as message Data and message sequence from the standard network file data. The second message information table may also extract other information such as message Data and message sequence from the historical message data. Any one or more of the information such as message identification number, message transmission period, message length, message Data, message sequence, etc. in the second message information table that is inconsistent with the first message information table is stored in the third message information table as suspicious data, so that abnormal message data can be obtained from the third message information table.

[0042] Optionally, in another embodiment, step S200 includes step S230: retrieving historical message data and analyzing the historical message data, including: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; obtaining standard network file data; comparing the standard network file data with the historical message data at the time of the fault occurrence; and determining the data in the historical message data at the time of the fault occurrence that is inconsistent with the standard network file data as abnormal message data.

[0043] Specifically, when the OBD interface of the target vehicle is connected, the current message data of the CAN bus is automatically acquired and recorded in real time. During the recording process, a 19 02FF diagnostic message is synchronously sent to record the fault information. If the vehicle response message indicates that a new fault has occurred in the vehicle, the time of occurrence of the new fault is recorded. The historical message data at the time of the fault may have abnormal problems, and the historical message data at the time of the fault is extracted. By importing the standard network file data, the standard network dbc file designed by the vehicle designer is obtained, and the data in the historical message data at the time of the fault that is inconsistent with the standard network file data is determined as abnormal message data. The abnormal message data is replayed, and the information inconsistent with the standard network file data in the historical message data at the time of the fault can be replayed, so that the fault problem can be quickly and accurately determined.

[0044] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0045] In this embodiment, a vehicle CAN bus fault monitoring system is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" is a combination of software and / or hardware that can implement a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0046] like Figure 3-6 As shown, a vehicle CAN bus fault monitoring system includes:

[0047] The acquisition module 400 is used to execute the above step S100, that is, the acquisition module is used to: acquire the current message data of the CAN bus of the target vehicle in real time and record it;

[0048] The data analysis module 500 is used to execute the above steps S200 and S300, that is, the data analysis module is used to: retrieve historical message data and analyze the historical message data to obtain abnormal message data, where the historical message data is the recorded current message data; select abnormal message data for playback to obtain vehicle problem data.

[0049] Optionally, the data analysis module 500 is also used to execute the above-mentioned step S210: retrieving historical message data and analyzing the historical message data including: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; and determining the historical message data at the time when the fault occurred as abnormal message data.

[0050] Optionally, the data analysis module 500 is also used to execute the above step S220: retrieving historical message data and analyzing the historical message data including: obtaining standard network file data; comparing the standard network file data and the historical message data to obtain abnormal message data, wherein the abnormal message data is data in the historical message data that is inconsistent with the standard network file data.

[0051] Optionally, the data analysis module 500 is also used to execute the above-mentioned step S221: comparing the standard network file data and the historical message data includes: analyzing the message identification number, message sending cycle and message length information in the standard network file data to form a first message information table; analyzing the message identification number, message sending cycle and message length information in the historical message data to form a second message information table; comparing the first message information table and the second message information table to obtain abnormal message data, wherein the abnormal message data is inconsistent data in the first message information table and the second message information table.

[0052] Optionally, the data analysis module 500 is also used to execute the above-mentioned step S230: retrieving historical message data and analyzing the historical message data, including: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; obtaining standard network file data; comparing the standard network file data with the historical message data at the time of the fault occurrence; and determining the data in the historical message data at the time of the fault occurrence that is inconsistent with the standard network file data as abnormal message data.

[0053] In some embodiments of the present invention, the acquisition module 400 includes a CAN transceiver, which is used to acquire the current message data of the CAN bus of the target vehicle in real time and record it; the data analysis module 500 includes a SOC chip, which is used to retrieve historical message data and analyze the historical message data to obtain abnormal message data, and the historical message data is the recorded current message data; the abnormal message data is selected for playback to obtain vehicle problem data.

[0054] Optionally, the SOC chip is also used to execute the above step S210: retrieving historical message data and analyzing the historical message data, including: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; determining the historical message data at the time of the fault occurrence as abnormal message data.

[0055] Optionally, the SOC chip is also used to execute the above step S220: retrieving historical message data and analyzing the historical message data including: obtaining standard network file data; comparing the standard network file data and the historical message data to obtain abnormal message data, wherein the abnormal message data is data in the historical message data that is inconsistent with the standard network file data.

[0056] Optionally, the SOC chip is also used to execute the above-mentioned step S221: comparing the standard network file data and the historical message data, including: analyzing the message identification number, message sending cycle and message length information in the standard network file data to form a first message information table; analyzing the message identification number, message sending cycle and message length information in the historical message data to form a second message information table; comparing the first message information table and the second message information table to obtain abnormal message data, wherein the abnormal message data is inconsistent data in the first message information table and the second message information table.

[0057] Optionally, the SOC chip is also used to execute the above-mentioned step S230: retrieving historical message data and analyzing the historical message data, including: sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, recording the time when the new fault occurred; obtaining standard network file data; comparing the standard network file data with the historical message data at the time of the fault occurrence; and determining the data in the historical message data at the time of the fault occurrence that is inconsistent with the standard network file data as abnormal message data.

[0058] It should be noted that the SOC chip realizes the recording of the current message data of the CAN bus, the analysis of the DBC file data, the self-identification of the historical message data, the recording of fault information, the playback of historical message data, and the adaptive analysis of the suspicious error information of the CAN bus. The CAN transceiver realizes the conversion of electrical signals and converts the electrical signals into data that can be recognized by the SOC chip.

[0059] Specifically, after the system is connected to the OBD interface of the target vehicle, the recording of the current message data of the CAN bus will be automatically started. During the recording process, a 19 02FF diagnostic message will be sent synchronously to record the fault information. If the vehicle response message indicates that a new fault has occurred in the vehicle, the time when the fault occurred will be recorded.

[0060] After completing the road test of the target vehicle, disconnect this system from the target vehicle, use a computer to access the SOC chip in the instrument through SHH, and start the fault analysis program in the system. At this time, you will be prompted to import the standard network file data. We need to import the standard network dbc file designed by the vehicle designer. After that, the software starts to analyze the standard network file data and store it. Then the software starts to analyze the recorded bus message information and extract key information for storage. By comparing the standard network file data with the bus message information obtained through the bus recording message, you can filter out the inconsistencies, which will facilitate the designer to further solve the problem.

[0061] Among them, the message information table stores "message identification number, message sending cycle, message length (bytes)" information.

[0062] By analyzing the historical message data and the standard network file data, the second message information table and the first message information table are obtained respectively. The inconsistent suspicious message data "message identification number, message sending cycle, message length (bytes)" in the two message tables can be filtered out and stored to form a third message information table. The software in the SOC chip can realize the playback of all messages, and can also realize the playback of messages at the time of fault occurrence. If the subsequent designer wants to reproduce the problem and further analyze the problem, he only needs to connect the OBD interface to the vehicle and start the playback message program.

[0063] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0064] An embodiment of the present invention further provides a device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute a vehicle CAN bus fault monitoring method described in any of the above embodiments.

[0065] Optionally, in this embodiment, the processor in the above device may be configured to run a computer program to execute the steps of the control method in the above embodiment:

[0066] Step S100: obtaining the current message data of the CAN bus of the target vehicle in real time and recording it;

[0067] Step S200, retrieve and analyze historical message data to obtain abnormal message data, where the historical message data is the recorded current message data;

[0068] Step S300, selecting abnormal message data for playback to obtain vehicle problem data.

[0069] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0070] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute a vehicle CAN bus fault monitoring method described in any of the above embodiments when running on a computer or a processor.

[0071] Optionally, in this embodiment, the above-mentioned computer program may be configured to store a computer program for executing the steps of the control method in the above-mentioned embodiment:

[0072] Step S100: obtaining the current message data of the CAN bus of the target vehicle in real time and recording it;

[0073] Step S200, retrieve and analyze historical message data to obtain abnormal message data, where the historical message data is the recorded current message data;

[0074] Step S300, selecting abnormal message data for playback to obtain vehicle problem data.

[0075] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0076] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0077] In some embodiments provided in the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the system embodiments described above are only schematic. For example, the division of the modules can be a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, modules or indirect coupling or communication connection of modules, which can be electrical or other forms.

[0078] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0079] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of software functional modules.

[0080] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0081] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A vehicle CAN bus fault monitoring method, characterized in that: include: Obtain the current message data of the target vehicle's CAN bus in real time and record it; Retrieving historical message data and analyzing the historical message data to obtain abnormal message data, wherein the historical message data is the recorded current message data; The abnormal message data is selected for playback to obtain vehicle problem data.

2. According to claim 1, a vehicle CAN bus fault monitoring method is characterized in that: The retrieving historical message data and analyzing the historical message data includes: Sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; When the response message indicates that a new fault occurs in the vehicle, the time of occurrence of the new fault is recorded; The historical message data at the time when the fault occurs is determined as the abnormal message data.

3. A vehicle CAN bus fault monitoring method according to claim 1, characterized in that: The retrieving historical message data and analyzing the historical message data includes: Get standard network file data; The standard network file data and the historical message data are compared to obtain abnormal message data, wherein the abnormal message data is data in the historical message data that is inconsistent with the standard network file data.

4. A vehicle CAN bus fault monitoring method according to claim 3, characterized in that: The comparing the standard network file data with the historical message data comprises: Analyze the message identification number, message sending period and message length information in the standard network file data to form a first message information table; Analyze the message identification number, message sending cycle and message length information in the historical message data to form a second message information table; The first message information table and the second message information table are compared to obtain abnormal message data, wherein the abnormal message data is inconsistent data in the first message information table and the second message information table.

5. A vehicle CAN bus fault monitoring method according to claim 1, characterized in that: Retrieving historical message data and analyzing the historical message data includes: Sending a diagnostic message to the target vehicle and receiving a response message from the target vehicle; When the response message indicates that a new fault occurs in the vehicle, the time of occurrence of the new fault is recorded; Get standard network file data; Comparing the standard network file data with the historical message data at the time when the fault occurs; The data in the historical message data at the time when the fault occurs that is inconsistent with the standard network file data is determined as the abnormal message data.

6. A vehicle CAN bus fault monitoring method according to claim 1, characterized in that: The real-time acquisition and recording of the message data of the target vehicle includes: When the OBD interface of the target vehicle is connected, the current message data of the CAN bus of the target vehicle is acquired and recorded in real time.

7. A vehicle CAN bus fault monitoring system, characterized in that: include: The acquisition module is used to: obtain the current message data of the target vehicle CAN bus in real time and record it; A data analysis module, used to retrieve and analyze historical message data to obtain abnormal message data, wherein the historical message data is the recorded current message data; The abnormal message data is selected for playback to obtain vehicle problem data.

8. A vehicle CAN bus fault monitoring system according to claim 7, characterized in that: The data analysis module is also used to: send a diagnostic message to the target vehicle and receive a response message from the target vehicle; when the response message indicates that a new fault has occurred in the vehicle, record the time when the new fault occurred; and determine the historical message data at the time when the fault occurred as the abnormal message data.

9. A device comprising a memory and a processor, characterized in that: The memory stores a computer program, and the processor is configured to run the computer program to execute the vehicle CAN bus fault monitoring method described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute a vehicle CAN bus fault monitoring method as described in any one of claims 1 to 6 when running on a computer or a processor.

Images