Automobile fault data remote acquisition method and system
By actively uploading fault data through the vehicle terminal and generating a remote download link, the problem of difficulty in remote data acquisition in automotive fault diagnosis is solved, enabling remote and rapid fault location and analysis, and reducing maintenance costs and time.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- DEEPAL AUTOMOBILE TECH CO LTD
- Filing Date
- 2022-08-31
- Publication Date
- 2026-07-07
AI Technical Summary
In existing technologies, it is difficult to remotely obtain bus data for automotive fault diagnosis, making it difficult for after-sales personnel to quickly locate faults, requiring on-site solutions, which wastes manpower and resources and is inefficient.
By actively uploading fault codes and vehicle data for a period of time before and after the fault occurrence through the vehicle terminal, and using a network communication server to generate fault logs and provide download links, remote fault data acquisition and analysis can be achieved.
It enables remote and rapid location of vehicle faults, reduces the need for on-site support, lowers maintenance costs and time, improves fault analysis efficiency, and alleviates after-sales pressure.
Smart Images
Figure CN115542876B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of automotive fault diagnosis, specifically to a technology for remotely acquiring automotive fault data. Background Technology
[0002] With the emergence of complex electronic and electrical systems in automobiles, fault repair has become more difficult. Inevitably, some faults cannot be diagnosed by after-sales personnel, often requiring OEM technicians to be dispatched on-site. However, even with significant investment of manpower, resources, and time, the root cause of the fault may not be found. This is mainly due to the difficulty in reproducing the problem or the lack of bus data at the time of the fault. Therefore, the need for a system that automatically stores bus data at the time of fault occurrence and allows for remote acquisition of vehicle fault data is crucial. This would solve the problem of remote bus data retrieval and enable rapid location of the fault occurrence. Summary of the Invention
[0003] The purpose of this invention is to provide a method for remotely acquiring vehicle fault data. The method involves actively uploading fault codes through an onboard terminal, and simultaneously, the onboard terminal actively packages vehicle data for a period of time before and after the fault occurred. When required by the designers, the fault data can be downloaded through a remote web interface, thus solving the problems of on-site location by technicians and the inability to remotely acquire fault bus data.
[0004] The technical solution of the present invention is as follows:
[0005] This invention provides a method for remotely acquiring fault data, comprising:
[0006] Step 1: Each vehicle controller performs a self-diagnosis of faults and sends the fault information to the vehicle terminal.
[0007] Step 2: The vehicle terminal extracts and stores the fault information based on the fault information, and uploads the fault information, the time of the fault occurrence, and the vehicle information to the network communication server; at the same time, it packages the bus data before and after the time of the received fault information into a fault data packet and stores it locally.
[0008] Step 3: The network communication server generates fault records and fault logs based on the pre-stored fault knowledge base and the received fault information. Each fault log corresponds to a download link.
[0009] Step 4: In response to the download link being clicked, the network communication server sends an instruction containing vehicle information and the time of the fault to the vehicle terminal.
[0010] Step 5: After receiving the instruction, the vehicle terminal uploads the specified fault data packet to the network communication server.
[0011] Step 6: The network communication server downloads the fault data.
[0012] Preferably, each of the controllers is connected to the vehicle terminal via a CAN bus. When each controller diagnoses a fault in the vehicle itself, it sends fault information containing fault codes and their status to the vehicle terminal in the form of CAN messages.
[0013] Preferably, the vehicle terminal uploads the fault information, the time of the fault occurrence, and the vehicle information to the network communication server based on the fault information.
[0014] Preferably, the vehicle-mounted terminal extracts and stores fault data based on the fault information, packages the fault information, fault data, and vehicle information, and stores them locally. The steps include:
[0015] The vehicle terminal determines the time when the controller malfunctions based on the fault information.
[0016] The vehicle terminal extracts fault data from the CAN network for the time periods preceding and following the fault time.
[0017] The vehicle terminal packages the fault information, the extracted fault data, and the vehicle information, and names the packaged file with the vehicle's VIN code, model configuration, and data packaging time period, and stores it locally.
[0018] Preferably, in the step of the vehicle terminal extracting fault data from the CAN network for the period before and after the fault time, the extracted fault data is all routing data on the CAN network or data of specific parameters related to the controller that has failed, wherein the specific parameters are parameters that are preset and stored in the vehicle terminal.
[0019] Preferably, the step of the vehicle-mounted terminal extracting fault data from the CAN network for the time periods preceding and following the fault time includes:
[0020] If the extracted fault time is a point, then the fault data between the previous time and the next time with a time interval T between the fault time and the time interval between the fault time is extracted from the CAN network.
[0021] When there are at least two extracted fault times, if the time interval ΔT between two adjacent fault times is greater than the preset time interval T, then the fault data between the time interval before and after the time interval between ... and the time interval between the time interval between the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the
[0022] If the time interval ΔT between two adjacent fault moments is less than the preset time interval T, then fault data is extracted from the CAN network from the moment before the preset time interval T between the first fault moment among at least two fault moments and the moment after the preset time interval T between the last fault moment among at least two fault moments. The total duration of the fault data cannot be greater than t.
[0023] Preferably, the network communication server generates fault records and fault logs based on a pre-stored fault knowledge base and the received fault information. Each fault log corresponds to a download link. The steps include:
[0024] The network communication server generates a fault log based on the received fault information. The fault log includes the vehicle identification number (VIN), the controller, the fault name, the fault status, and the time of the fault. Each fault log also corresponds to a fault data packet status, a fault data packet upload button, and a fault data packet download button.
[0025] Preferably, the network communication service responds to the fault data packet upload button being clicked, that is, when the user clicks the fault data packet upload button, the network communication server sends an instruction containing vehicle information and time to the vehicle terminal.
[0026] Preferably, the step of uploading the fault data packet cached in the vehicle terminal to the network communication server after receiving the instruction includes:
[0027] The vehicle-mounted terminal parses the command and obtains the fault time contained in the command;
[0028] The vehicle terminal searches for time periods in the names of all fault data packets. If the time period in the name of a fault data packet contains the time of the fault, the fault data packet that meets the requirements is extracted.
[0029] The vehicle-mounted terminal uploads the extracted fault data packets to the network communication server.
[0030] The present invention also provides a remote acquisition system for vehicle fault data, which includes an in-vehicle terminal and a network communication server.
[0031] The vehicle-mounted terminal is used to acquire fault information sent by each vehicle-mounted controller; and based on the fault information, to extract and store the fault information, upload the fault information, the time of fault occurrence, and vehicle information to the network communication server; at the same time, it packages the bus data for a period of time before and after the received fault information into a fault data packet for local storage; and after receiving an instruction from the network communication server, it uploads the specified fault data packet to the network communication server.
[0032] The network communication server is used to generate fault records and fault logs based on a pre-stored fault knowledge base and the received fault information, with each fault log corresponding to a download link; and in response to a click signal on the download link, to send an instruction containing vehicle information and the time of the fault occurrence to the vehicle terminal; and after receiving the fault data packet uploaded by the vehicle terminal, to download the fault data.
[0033] The beneficial effects of this invention are as follows:
[0034] 1. This invention actively uploads fault codes via an in-vehicle terminal, and simultaneously packages vehicle data for a period of time before and after the fault occurrence. When required by designers, the fault data can be downloaded via a remote web interface. Using wireless network and other technologies, vehicle faults can be diagnosed and analyzed remotely, eliminating the need for technicians to go to the site to resolve vehicle problems. By acquiring fault data, it supports OEM technicians in remotely analyzing and locating problems, avoiding the waste of manpower, resources, and time by providing on-site support. This enables rapid remote support, reduces after-sales pressure, and lowers maintenance time and costs.
[0035] 2. This invention extracts, packages, and stores fault data locally via an in-vehicle terminal, providing ample local storage space. Data does not need to be uploaded to a network server in real-time; instead, fault data packages are uploaded to the cloud platform only when needed by R&D personnel. This significantly reduces costs and ensures no data loss. Therefore, it avoids the waste of bandwidth and increased enterprise service costs caused by uploading all packaged data to the cloud platform in real-time at the moment of a fault; and it also avoids the loss of fault data due to untimely uploads.
[0036] 3. This invention sets an upper limit for the packaging time when packaging fault data. This can solve the problem that if faults occur continuously with an interval of less than T, data packaging will theoretically continue, which will cause storage overload and data loss, resulting in computational overload and causing the vehicle terminal to "crash" and causing related functions to fail.
[0037] 4. This invention can download data, allowing researchers to replay the data and accurately pinpoint problems. Attached Figure Description
[0038] Figure 1 This is a schematic flowchart of the method of the present invention;
[0039] Figure 2 A schematic diagram illustrating bus data packet storage when the time interval between T2 and T1 is greater than T;
[0040] Figure 3 This diagram illustrates the bus data packet storage when the time interval between T2 and T1 is less than T. Detailed Implementation
[0041] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
[0042] Reference Figure 1 This embodiment provides a detailed description of the method and process for remotely acquiring fault data, including:
[0043] Step 101: Each controller mounted on the vehicle performs a self-diagnosis of faults and sends fault information to the vehicle terminal when it detects a fault. The fault information includes the fault code and the fault code status.
[0044] For automobiles, this includes controllers such as the engine controller, vehicle controller, adaptive cruise control controller, and battery management system. Each controller operates according to its design logic to ensure safe vehicle operation. For automobiles, each controller needs to continuously perform fault self-diagnosis to promptly alert the driver to troubleshooting when a malfunction occurs. Typically, each controller connects to the on-board terminal via a CAN bus, and the CAN protocol between the controller and the on-board terminal is predefined. When a controller detects a fault, it sends the fault information to the on-board terminal via a CAN message.
[0045] Step 102: The vehicle terminal extracts the CAN message address, fault information and the time of the fault occurrence, and uploads the CAN message address, fault information and its timestamp to the network communication server, while packaging the bus data for a period of time before and after the time of the fault occurrence.
[0046] In this step, after receiving a message containing a fault signal, the vehicle terminal first extracts the CAN message address, fault information, and timestamp (i.e., time point). Then, it encapsulates the CAN message address, fault information, and fault time into a packet according to the agreed method. The vehicle terminal first caches the packet file. After the vehicle terminal establishes a connection with the network communication server, it sends the packet file to the network communication server.
[0047] The vehicle-mounted terminal retrieves fault data from the CAN network corresponding to the preceding and following time periods based on the time of the controller malfunction. During fault data extraction, the vehicle-mounted terminal can choose to extract all bus data on the CAN network, or it can choose to extract fault data corresponding to specific parameters related to the malfunctioning controller. These specific parameters are pre-set and stored in the vehicle-mounted terminal. The specific bus data extracted by the vehicle-mounted terminal can be calibrated. If the large amount of data transmitted between the vehicle-mounted terminal and the network communication server increases bandwidth costs, it can choose to extract only the fault data corresponding to the specific parameters of the malfunctioning controller. After completing the fault data extraction, the vehicle-mounted terminal uses the vehicle's VIN code, data packaging time period, and configuration file version number as the fault data packet name. The fault data packet is cached in the vehicle-mounted terminal with a fixed cache size. When the cache is full, the fault data packet is replaced according to the first-in, first-out (FIFO) principle. Generally, the number of cached data packets should not be less than a certain number.
[0048] The following rules apply when the vehicle-mounted terminal extracts fault data:
[0049] If there is only one fault time, then the fault data between the previous time and the next time with a preset time interval T between the fault time and the fault time is extracted from the CAN network. For example, if the fault time is T1, the vehicle terminal extracts the data between time T1-T and time T1+T from the CAN network.
[0050] When at least two fault times are extracted, if the time interval ΔT between two adjacent fault times is greater than the preset time interval T, then fault data is extracted from the CAN network from the time interval before and after the time interval between the preceding fault time and the time interval between the following fault time and the time interval before and after the preset time interval T. For example, Figure 2 As shown, two adjacent fault times include time T1 and time T2. If the time interval ΔT between time T1 and time T2 is greater than the preset time interval T, then data from time T1-T to time T1+T and data from time T2-T to time T2+T are extracted from the CAN network. If the time interval ΔT between two adjacent fault times is less than the preset time interval T, then fault data from the time before the preset time interval T between the first fault time of at least two fault times and the time after the preset time interval T between the last fault time of at least two fault times are extracted from the CAN network. For example, as... Figure 3As shown, the fault time includes time T1, time T2 and time T3. The time interval ΔT between time T1 and time T2 is less than the preset time interval T, and the time interval ΔT between time T2 and time T3 is also less than the preset time interval T. Then, data from time T1-T to time T3+T is extracted from the CAN network.
[0051] Step 103: The network communication server generates a fault log on the web interface and provides a data packet download link based on the pre-stored fault knowledge base and the received packet files.
[0052] In this step, the network communication server parses the packet file to obtain the message address, fault code, fault code status, and fault time. Based on the obtained information, the network communication server generates a fault log. The fault log includes the vehicle identification number (VIN), the controller, the fault name, the fault status, and the fault time. Each fault log also corresponds to a fault data packet status, a fault data packet upload button, and a fault data packet download button.
[0053] Step 104: When the user clicks the data upload button on the web interface, the network communication server sends a data upload command to the designated vehicle terminal. This command consists of the fault time, vehicle information, etc. The fault time refers to the fault time recorded in each fault log.
[0054] Step 105: After receiving the instruction sent by the network communication server, the vehicle terminal retrieves all cached fault data packets and uploads the fault data packets that meet the requirements to the network communication server.
[0055] The vehicle-mounted terminal parses the command to obtain the fault time contained within it. Then, it searches all fault data packet names for time periods. If a fault data packet name contains a time period that matches the fault time, the vehicle-mounted terminal uploads that fault data packet to the network communication server. If multiple fault data packets meet the requirements, the vehicle-mounted terminal repackages all matching fault data packets and uploads them to the network communication server. If no matching fault data is found among all fault data packet names, the vehicle-mounted terminal does not need to provide any data or information.
[0056] In step 106, the network communication server temporarily stores the received data packets and then displays the fault data status as "complete" in the corresponding fault log. If the network server does not receive the fault data packets uploaded by the vehicle terminal within a timeout period, the fault log displays "network abnormality or data loss". The user clicks the fault data packet download button corresponding to the fault log on the web interface, and the web interface uses its built-in download tool to download the fault data.
[0057] In this application, in addition to CAN bus, the above bus types can also be Ethernet, LIN, LVDS, UBS, etc.
[0058] In this application, vehicle fault data is remotely acquired using wireless network technology, eliminating the need for technicians to visit the site to resolve vehicle malfunctions. This improves the efficiency of fault cause analysis and problem-solving, reduces the cost pressure on manufacturers in after-sales service, and significantly reduces maintenance time, allowing users to quickly complete vehicle repairs and enhancing customer satisfaction.
[0059] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.
Claims
1. A method for remotely acquiring vehicle fault data, characterized in that, The method includes: Step 101: The vehicle terminal obtains fault information sent by each controller; Step 102: After receiving the fault information, the vehicle terminal first extracts the CAN message address, fault information, and timestamp. Then, it encapsulates and caches the CAN message address, fault information, and fault time. After the vehicle terminal establishes a connection with the network communication server, it sends the encapsulated file to the network communication server. At the same time, it packages the bus data before and after the received fault information time into a fault data packet and stores it locally. Step 103: The network communication server generates fault records and fault logs based on the pre-stored fault knowledge base and the received fault information. Each fault log corresponds to a download link. The fault log includes the vehicle identification number (VIN), the controller, the fault name, the fault status, and the fault time. Each fault log also corresponds to a fault data packet status, a fault data packet upload button, and a fault data packet download button. Step 104: In response to the download link being clicked, the network communication server sends an instruction containing vehicle information and the time of the fault to the vehicle terminal. Step 105: After receiving the instruction, the vehicle terminal parses the instruction and obtains the fault time contained in the instruction; the vehicle terminal searches for the time period in the names of all fault data packets. If the time period in the name of a certain fault data packet contains the fault time contained in the instruction, the corresponding fault data packet is extracted; the vehicle terminal uploads the extracted fault data packet to the network communication server; Step 106: The network communication server downloads the fault data.
2. The method for remotely acquiring vehicle fault data according to claim 1, characterized in that, In step 102: The vehicle-mounted terminal determines the time when the controller malfunctions based on the fault information. The vehicle-mounted terminal extracts fault data from the time period before and after the time of the fault. The vehicle terminal packages the fault information, fault data, and vehicle information, and names the packaged file with the vehicle's VIN code, model configuration, and data packaging time period, and stores it locally.
3. The method for remotely acquiring vehicle fault data according to claim 2, characterized in that, In step 102, the extracted fault data is all routing data on the CAN network or data of specific parameters related to the controller that has failed, wherein the specific parameters are parameters that are preset and stored in the vehicle terminal.
4. The method for remotely acquiring vehicle fault data according to claim 2, characterized in that, In step 102, the step of the vehicle terminal extracting fault data from the CAN network for the time period before and after the fault time includes: If the extracted fault time is a point, then the fault data between the previous time and the next time with a time interval T between the fault time and the time interval between the fault time is extracted from the CAN network. When there are at least two extracted fault times, if the time interval ΔT between two adjacent fault times is greater than the preset time interval T, then the fault data between the time interval before and after the time interval between ... and the time interval between the time interval between the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the time interval between the time interval and the time interval between the If the time interval ΔT between two adjacent fault moments is less than the preset time interval T, then fault data is extracted from the CAN network from the moment before the preset time interval T between the first fault moment among at least two fault moments and the moment after the preset time interval T between the last fault moment among at least two fault moments. The total duration of the fault data cannot be greater than t.
5. The method for remotely acquiring vehicle fault data according to any one of claims 1-4, characterized in that, In step 104, in response to the click of the fault data packet upload button, the network communication service sends an instruction containing vehicle information and time to the vehicle terminal.
6. The method for remotely acquiring vehicle fault data according to any one of claims 1-4, characterized in that, In step 101, when each controller diagnoses a fault in the vehicle itself, it sends fault information containing fault codes and their status to the vehicle terminal in the form of CAN messages.
7. A remote vehicle fault data acquisition system, characterized in that, Including vehicle-mounted terminals and network communication servers; The vehicle-mounted terminal is used to obtain fault information sent by each vehicle-mounted controller. After receiving the fault information, it first extracts the CAN message address, fault information, and timestamp, and then encapsulates and caches the CAN message address, fault information, and fault time. After the vehicle-mounted terminal establishes a connection with the network communication server, it sends the encapsulated file to the network communication server. At the same time, it packages the bus data before and after the received fault information time into a fault data packet and stores it locally. And after receiving the instruction from the network communication server, it uploads the specified fault data packet to the network communication server; The network communication server is used to record faults and generate fault logs based on a pre-stored fault knowledge base and the received fault information, with each fault log corresponding to a download link; The fault log includes the vehicle identification number (VIN), the controller, the fault name, the fault status, and the time of the fault; each fault log also corresponds to a fault data packet status, a fault data packet upload button, and a fault data packet download button. In response to the download link being clicked, the system sends an instruction containing vehicle information and the time of the fault to the vehicle terminal. The vehicle terminal parses the instruction sent by the network communication server and obtains the time of the fault contained in the instruction. The vehicle terminal searches for time periods in the names of all fault data packets. If the time period in the name of a fault data packet contains the time of the fault contained in the instruction, the corresponding fault data packet is extracted. The vehicle terminal uploads the extracted fault data packet to the network communication server. After receiving the fault data packet uploaded by the vehicle terminal, the fault data is downloaded.
8. The vehicle fault data remote acquisition system according to claim 7, characterized in that, The vehicle-mounted terminal packages bus data from a period of time before and after the received fault information into a fault data packet for local storage, specifically including: The vehicle-mounted terminal determines the time when the controller malfunctions based on the fault information. The vehicle-mounted terminal extracts fault data from the time period before and after the time of the fault. The vehicle terminal packages the fault information, fault data, and vehicle information, and names the packaged file with the vehicle's VIN code, model configuration, and data packaging time period, and stores it locally.
9. The vehicle fault data remote acquisition system according to claim 7, characterized in that, In response to the click of the fault data packet upload button, the network communication server sends an instruction containing vehicle information and time to the vehicle terminal.