Vehicle fault analysis method, electronic device, and storage medium

Abstract

The present application belongs to the technical field of vehicle fault diagnosis, and specifically discloses a vehicle fault analysis method, an electronic device and a storage medium. The method first defines the standard and specification of vehicle data collection, and defines fault information in the packet protocol; secondly, full-amount CAN matrix data is collected and packaged and uploaded to a cloud server; then the cloud server records the fault information corresponding to the uploaded CAN matrix data, manages the fault information by a fault monitoring management platform, and provides a signal analyzer jump interface; finally, in the signal analyzer, the CAN matrix signal mapped by each fault type is configured, is bound and managed with the fault of the fault monitoring management platform, and corresponds to the jump interface. When the vehicle fails, the present application completely captures the fault CAN data, applies the fault-bound CAN data signal to the signal analyzer, pulls the CAN data in real time, corresponds to the fault signal, and efficiently and accurately analyzes the vehicle fault.

Description

Technical Field

[0001] This invention belongs to the field of vehicle fault diagnosis technology, specifically relating to a vehicle fault analysis method, electronic device, and storage medium. Background Technology

[0002] The vehicle-mounted T-Box, or vehicle telematics processor, is an important component of the vehicle networking system. It communicates with the backend system, sending control messages via the CAN bus to control the vehicle. CAN, or Controller Area Network, is a serial communication bus defined by the International Organization for Standardization (ISO). It is primarily used to facilitate information exchange between various electronic control units (ECUs) within the vehicle network, forming the vehicle network system.

[0003] When a vehicle malfunctions, the analysis of its driving data mainly takes the following forms: First, engineers use CAN acquisition tools to read the vehicle's driving data and analyze the cause of the malfunction based on the fault conditions. Second, the onboard T-Box collects CAN data and uploads it to a cloud data server via the network. When a malfunction occurs, the data system exports the CAN data file and imports it into a CAN analysis tool for analysis. Third, after obtaining the CAN data file, professionals find the signals that need to be associated with the fault from the CAN matrix database file, configure them in the CAN analysis tool, and then perform the analysis.

[0004] The above three methods of vehicle driving data analysis all have the following problems: when a vehicle fault occurs, the fault CAN data cannot be captured, or the captured CAN data is incomplete. This makes it impossible for staff to analyze more detailed CAN data when a fault occurs, and thus makes it impossible to analyze vehicle faults efficiently and accurately. Summary of the Invention

[0005] To address the aforementioned shortcomings in existing technologies, this invention aims to provide a vehicle fault analysis method.

[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0007] A vehicle fault analysis method, the method comprising the following steps performed sequentially:

[0008] S1. Define the standards and specifications for vehicle data acquisition in the vehicle-mounted T-Box, and define fault information in the CAN message signal packetization protocol. The fault information includes fault signal and fault type.

[0009] S2, the vehicle-mounted T-Box collects all CAN matrix data according to the vehicle data collection standards and specifications, and packages and uploads it to the cloud server;

[0010] S3. The cloud server records the fault information corresponding to the uploaded CAN matrix data. The fault information is managed by the fault monitoring and management platform, which also provides a jump interface for the signal analyzer.

[0011] S4. In the signal analyzer, configure the CAN matrix signal mapped to each fault type according to the defined fault type;

[0012] The faults of the signal analyzer are bound to the fault monitoring and management platform for management, and the fault information receiving interface of the signal analyzer corresponds to the jump interface in step S3.

[0013] As a limitation, the standards and specifications for vehicle data acquisition in step S1 include: enterprise standard real-time CAN message signal reporting rules, enterprise standard fault CAN message signal reporting rules, and enterprise standard calibration CAN message signal reporting rules.

[0014] As a second limitation, the specific rules for reporting enterprise standard real-time CAN message signals are as follows:

[0015] During vehicle operation, the terminal needs to collect message signals sent to each controller ECU on the CAN bus and report the agreed CAN data to the fault monitoring and management platform at specified time intervals.

[0016] The packet assembly protocol includes the acquisition time, fault information, version number, and number of packets per second N; a packet per second is 8 bytes of data of MSG ID collected from the CAN matrix on the CAN bus, arranged in a specified order, and assembled into a packet per second.

[0017] Each of the second packets includes an MSG ID, a quantity, and a message content. The quantity is calculated based on the collection frequency of each MSG ID, representing the number of MSG IDs collected per second. The message content consists of 8*N bytes of data arranged sequentially from N 8-byte message contents.

[0018] As a third limitation, the specific rules for reporting enterprise standard fault CAN message signals are as follows:

[0019] When any fault CAN message signal occurs, all the full-cycle data of the MSG ID corresponding to this fault CAN message signal within the same period before and after the fault is packaged and uploaded to the cloud server.

[0020] As a fourth limitation, the acquisition of CAN matrix data by the vehicle-mounted T-Box in step S2 is specifically divided into non-fault data acquisition and fault data acquisition.

[0021] During non-fault data acquisition, the last frame of data is extracted every second; during fault data acquisition, no data extraction is performed, and the entire cycle of data is packaged.

[0022] As a fifth limitation, the management process of the fault monitoring and management platform is as follows:

[0023] The fault monitoring and management platform records the number and type of faults to be monitored in advance. Based on the fault information in the data reported by the T-Box, it maps the faults recorded by the monitoring and management platform and automatically adds the fault records on the fault monitoring and management platform interface. The fault monitoring and management platform then parses the data and displays the detailed content of the fault.

[0024] Another object of the present invention is to provide an electronic device including a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method described above.

[0025] Another object of the present invention is to provide a storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.

[0026] By adopting the above-described technical solution, the beneficial effects achieved by this invention compared to the prior art are as follows:

[0027] (1) When a vehicle malfunctions, the vehicle-mounted T-Box collects all CAN matrix data according to the period specified in the database file of the CAN matrix and uploads it to the cloud server. It reads all frequency data of all CAN IDs from the CAN bus and extracts all data before and after the malfunction to ensure the integrity of the CAN signal when the malfunction occurs.

[0028] (2) When a vehicle malfunctions, the method of the present invention can determine the associated CAN data signal for each type of malfunction and apply the fault-bound CAN data signal to the signal analyzer. When a fault signal occurs, the system can directly jump to the signal analyzer from the fault record in the cloud, pull CAN data from the cloud server in real time, correspond to the fault signal, and accurately mark the fault at the corresponding time point.

[0029] (3) The method of the present invention defines the fault from the source of vehicle data, and collects all the data before and after the fault according to the time of the fault occurrence, so as to analyze more detailed CAN data;

[0030] (4) This invention maps and associates fault types with CAN matrix signals. When a fault occurs, it can quickly jump to the signal analyzer to intuitively display the model change situation when the fault occurs, and more accurately locate the cause of the fault.

[0031] (5) When a fault occurs, the fault monitoring and management platform can monitor the vehicle fault in real time, and the engineer can view the cause of the vehicle fault in real time, thereby effectively improving the efficiency and accuracy of vehicle fault resolution.

[0032] In summary, when a vehicle malfunctions, this invention can completely capture the faulty CAN data and apply the fault-bound CAN data signal to a signal analyzer. It can also retrieve CAN data from a cloud server in real time, corresponding to the fault signal, and efficiently and accurately analyze vehicle malfunctions. Attached Figure Description

[0033] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0034] Figure 1 This is a diagram of the CAN matrix message data packet protocol format according to Embodiment 1 of the present invention;

[0035] Figure 2 This is a diagram illustrating the vehicle data collection and reporting cycle after the vehicle is powered on, as shown in Embodiment 1 of the present invention.

[0036] Figure 3 This is a diagram of the fault information recording system interface in the fault monitoring and management platform of Embodiment 1 of the present invention;

[0037] Figure 4 This is a diagram showing the fault signal markers and curve changes in the signal analyzer of Embodiment 1 of the present invention. Detailed Implementation

[0038] To better explain and facilitate understanding of the present invention, the preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0039] Example 1: Vehicle Fault Analysis Method

[0040] This embodiment provides a vehicle fault analysis method, including the following steps performed sequentially:

[0041] S1. Define the standards and specifications for vehicle data acquisition in the vehicle-mounted T-Box, and define fault information in the CAN message signal packetization protocol. The fault information includes fault signal and fault type.

[0042] The standards and specifications for vehicle data acquisition include: enterprise standard real-time CAN message signal reporting rules, enterprise standard fault CAN message signal reporting rules, and enterprise standard calibration CAN message signal reporting rules.

[0043] The specific rules for real-time CAN message signal reporting in the enterprise standard are as follows: During vehicle operation, the terminal needs to collect messages sent from the CAN bus to each controller ECU, and report the agreed CAN data to the fault monitoring and management platform at the specified time intervals. Among them, the T-Box only transparently transmits the CAN ID specified in the packet protocol.

[0044] Enterprise standard data is collected every 1 second and uploaded every 10 seconds. Enterprise standard cache data packets are cached for no less than seven days, and the cached data is overwritten cyclically.

[0045] like Figure 1 As shown, the packet assembly protocol includes the acquisition time, fault information, version number, and the number of packets per second (N). A packet per second is composed of 8 bytes of MSG ID data acquired from the CAN matrix on the CAN bus, arranged in a specified order. Each packet includes the MSG ID, the quantity, and the message content. The quantity is calculated based on the acquisition frequency of each MSG ID, representing the number of MSG IDs acquired per second. The message content consists of N 8-byte messages arranged sequentially, resulting in an 8*N byte length of data.

[0046] The specific rules for reporting enterprise standard fault CAN message signals are as follows: When any fault CAN message signal occurs, all data for the entire lifecycle of this fault CAN message signal, including the corresponding MSG ID, within the preceding and following 30 seconds, is packaged and uploaded to the cloud server. Any fault CAN message signal is recorded as a fault signal in GB / T32960. When encountering an enterprise standard fault CAN message signal during enterprise standard data packaging, the enterprise standard data that has not yet been fully packaged is discarded, as this incompletely packaged enterprise standard data has already been uploaded in the form of enterprise standard fault information.

[0047] like Figure 2 As shown, in this example, vehicle data is reported once every 10 seconds. When a fault occurs, the vehicle data collection includes all message signals within 30 seconds before and after the fault occurs.

[0048] Table 1 shows some common fault information recorded in GB / T32960 in this embodiment;

[0049]

[0050] Table 2 is a diagram showing the definition and marking of normal and fault messages in the vehicle message protocol of this embodiment;

[0051]

[0052] S2. The vehicle-mounted T-Box collects all CAN matrix data according to the standards and specifications for vehicle data collection, specifically the collection period specified in the CAN matrix database file, and packages and uploads it to the cloud server.

[0053] Table 3 shows a portion of the contents of the CAN matrix database file in this embodiment;

[0054]

[0055] The period specified in the CAN matrix's database file is the transmission cycle of the CAN ID in the controller ECU on the CAN bus, and data is transmitted according to the definition of the transmission type. According to Table 3, CAN ID 0x291 is defined as the cycle type, meaning that data is transmitted to the CAN bus once every 20ms.

[0056] The vehicle-mounted T-Box can collect CAN matrix data in two ways: non-fault data acquisition and fault data acquisition. During non-fault data acquisition, one frame is collected every 20ms, 50 frames are collected per second, and the last frame of data is extracted and uploaded to the cloud server every second. During fault data acquisition, no data extraction is performed, and the entire cycle of data is packaged and uploaded to the cloud server.

[0057] S3, the cloud server records the fault information corresponding to the uploaded CAN matrix data, the fault monitoring and management platform manages the fault information, and provides a jump interface for the signal analyzer.

[0058] The process of the fault monitoring and management platform is as follows: The fault monitoring and management platform records the number and type of faults to be monitored in advance. Based on the fault information in the data reported by the T-Box, it maps the faults recorded by the monitoring and management platform and automatically adds the fault records on the interface of the fault monitoring and management platform. After parsing the data, the fault monitoring and management platform displays the detailed content of the fault.

[0059] S4. In the signal analyzer, configure the CAN matrix signal mapped to each fault type according to the defined fault types.

[0060] The faults of the signal analyzer are bound to the fault monitoring and management platform for management, and the fault information receiving interface of the signal analyzer is matched with the jump interface in step S3.

[0061] In this embodiment, the cloud server, the fault monitoring and management platform, and the signal analyzer belong to three different platforms. The fault monitoring and management platform obtains fault information from the cloud server. The fault monitoring and management platform and the signal analyzer are bound together by the same pre-configured ID.

[0062] like Figure 3As shown, when a fault occurs, a fault record is automatically added to the fault monitoring and management platform. The platform displays the faulty vehicle identification number (VIN), license plate number, fault name, fault unit, fault time, fault location, fault mileage, resolution status, resolution time, and dealer. Details and message signals can be viewed in the operation section. Clicking "View Message Signals" will redirect to... Figure 4 In the signal analyzer web interface shown, the person in charge of the fault has the right to configure the configuration file, that is, to configure the CAN matrix signal mapped to each fault type. The “948: ME7 OFF electrical abnormality” displayed on this interface is the vehicle fault type, and the corresponding CAN matrix signal mapped to each fault type is below it. At the same time, on this interface, you can view the fault signal curve change graph associated with the enterprise standard fault message 30 seconds before and after the fault. The shaded part within the dashed box in the graph is the fault signal curve when the fault occurs.

[0063] Example 2: Electronic equipment and storage medium for vehicle fault analysis using a signal analyzer

[0064] The electronic device in this embodiment is a computer device, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it can implement the steps of the vehicle fault analysis method in Embodiment 1.

[0065] A computer-readable storage medium stores a computer program thereon, which, when executed by a processor, can implement the steps of the vehicle fault analysis method of Embodiment 1. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium includes: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

Claims

1. A vehicle fault analysis method, characterized in that, The method includes the following steps performed sequentially: S1. Define the standards and specifications for vehicle data acquisition in the vehicle-mounted T-Box, and define fault information in the CAN message signal packetization protocol. The fault information includes fault signal and fault type. S2, the vehicle-mounted T-Box collects all CAN matrix data according to the vehicle data collection standards and specifications, and packages and uploads it to the cloud server; S3. The cloud server records the fault information corresponding to the uploaded CAN matrix data. The fault monitoring and management platform manages the fault information and provides a jump interface for the signal analyzer. S4. In the signal analyzer, configure the CAN matrix signal mapped to each fault type according to the defined fault type; The faults of the signal analyzer are bound to the fault monitoring and management platform for management, and the fault information receiving interface of the signal analyzer corresponds to the jump interface in step S3.

2. The vehicle fault analysis method according to claim 1, characterized in that, The standards and specifications for vehicle data acquisition in step S1 include: enterprise standard real-time CAN message signal reporting rules and enterprise standard fault CAN message signal reporting rules.

3. The vehicle fault analysis method according to claim 2, characterized in that, The specific rules for reporting enterprise standard real-time CAN message signals are as follows: During vehicle operation, the terminal needs to collect message signals sent to each controller ECU on the CAN bus and report the agreed CAN data to the fault monitoring and management platform at specified time intervals. The packet assembly protocol includes the acquisition time, fault information, version number, and number of packets per second N; a packet per second is 8 bytes of MSG ID data acquired from the CAN matrix on the CAN bus, arranged in a specified order, and assembled into a packet per second. Each of the second packets includes an MSG ID, a quantity, and a message content. The quantity is calculated based on the collection frequency of each MSG ID, representing the number of MSG IDs per second. The message content consists of 8*N bytes of data arranged sequentially from N 8-byte message contents.

4. The vehicle fault analysis method according to claim 3, characterized in that, The specific rules for reporting enterprise standard fault CAN message signals are as follows: When any fault CAN message signal occurs, all the full-cycle data of the MSG ID corresponding to this fault CAN message signal within the same period before and after the fault is packaged and uploaded to the cloud server.

5. The vehicle fault analysis method according to claim 4, characterized in that, In step S2, the acquisition of CAN matrix data by the vehicle-mounted T-Box is specifically divided into non-fault data acquisition and fault data acquisition. During non-fault data acquisition, the last frame of data is extracted every second; during fault data acquisition, no data extraction is performed, and the entire cycle of data is packaged.

6. The vehicle fault analysis method according to any one of claims 1-5, characterized in that, The management process of the fault monitoring and management platform is as follows: The fault monitoring and management platform records the number and type of faults to be monitored in advance. Based on the fault information in the data reported by the T-Box, it maps the faults recorded by the monitoring and management platform and automatically adds the fault records on the fault monitoring and management platform interface. The fault monitoring and management platform then parses the data and displays the detailed content of the fault.

7. An electronic device, characterized in that, The method includes a memory and a processor, the memory storing a computer program, characterized in that the processor executes the computer program to implement the steps of the method described in any one of claims 1-6.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1-6.

Images