A remote diagnosis method, storage medium and device for a whole vehicle distributed ECU

Abstract

The application discloses a kind of whole vehicle distributed ECU remote diagnosis method, storage medium and device, involve the diagnosis field of intelligent network connection car, which method includes the TBOX terminal of vehicle end to be diagnosed to register to cloud server, while cloud server establishes data acquisition and diagnosis task and issues to vehicle end;TBOX terminal is based on data acquisition and diagnosis task to vehicle end executes diagnosis process, and the data collected and the result obtained by diagnosis are uploaded to cloud server;Cloud server analyzes and saves the data collected, and the result obtained by diagnosis is displayed.The application can effectively improve the diagnosis efficiency of ECU.

Description

Technical Field

[0001] This invention relates to the field of diagnostics for intelligent connected vehicles, and specifically to a remote diagnostic method, storage medium, and device for a vehicle's distributed ECU. Background Technology

[0002] Currently, in the field of automotive diagnostics, data collection and diagnosis are mainly carried out manually using automotive diagnostic instruments on-site. By connecting the diagnostic instruments to the relevant interfaces on the vehicle, data and fault codes are collected. By analyzing the collected data, it can be determined whether the parts are in a normal or abnormal state. After troubleshooting, the ECU (Electronic Control Unit) can be reset to clear the fault codes.

[0003] However, the above diagnostic methods have the following problems: 1. Workers need technical training to master the diagnostic instruments, and they need to operate them on-site, resulting in high labor costs. In addition, the diagnostic instruments are expensive, with each instrument typically costing hundreds of thousands of yuan; 2. The diagnostic instruments have limited ability to analyze the collected data, often only performing simple analysis; 3. Different diagnostic instruments follow different testing standards, leading to low reliability of diagnostic results; 4. The diagnostic instruments have limitations in storage space and timeliness of the collected data. Summary of the Invention

[0004] In view of the deficiencies in the existing technology, the purpose of this invention is to provide a remote diagnostic method, storage medium and device for a vehicle distributed ECU, which can effectively improve the diagnostic efficiency of the ECU.

[0005] To achieve the above objectives, the present invention provides a remote diagnostic method for a vehicle's distributed ECU, specifically including the following steps:

[0006] The TBOX terminal on the vehicle to be diagnosed is registered to the cloud server, and at the same time the cloud server establishes data collection and diagnosis tasks and sends them to the vehicle.

[0007] The TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server.

[0008] The cloud server analyzes and saves the collected data and displays the diagnostic results.

[0009] Based on the above technical solution, the TBOX terminal of the vehicle to be diagnosed is registered to the cloud server, and the cloud server simultaneously establishes data collection and diagnostic tasks and sends them to the vehicle. The specific steps include:

[0010] The TBOX terminal on the vehicle side to be diagnosed is powered on and registers with the cloud server by calling the diagnostic communication specification interface;

[0011] Once the TBOX terminal is successfully registered, a data collection and diagnostic task is created on the cloud server or APP, and then the created data collection and diagnostic task is sent to the vehicle.

[0012] Based on the above technical solution, the specific steps of registering the diagnostic communication specification interface to the cloud server include:

[0013] When the TBOX terminal detects that the registration information has been updated, it calls the registration information upload interface. The registration thread then determines whether it has received a registration status update. The registration information upload interface is used to update the registration information and registration status.

[0014] When the registration thread receives a registration status update, it registers the registration information and updates the registration status to indicate success or failure.

[0015] When the registration thread does not receive a registration status update, it checks whether a registration file exists in the registration file directory. If the registration file does not exist, it sets the idle task to the highest priority, then calls the task scheduling function to perform the registration operation. If the registration file exists, it performs the corresponding operation according to the registration status of the registration file.

[0016] Based on the above technical solutions,

[0017] When the registration status is failed, the TBOX terminal will not enter the data acquisition and diagnostic task mode, and the cloud server will not send the configuration file containing the data acquisition and diagnostic tasks to the TBOX terminal.

[0018] The registration file includes SN, ICCID, VIN and registration status, which includes success, failure and pending registration.

[0019] When a TBOX terminal calls the registration information upload interface to register, if the registration fails and a preset number of re-registration attempts are made with a set time interval between each attempt, and the registration still fails after the preset number of re-registration attempts, the registration process will be terminated.

[0020] Based on the above technical solutions,

[0021] When the TBOX terminal is powered on, it checks the registration file. If the previous registration recorded in the registration file was a failure, it will try to register again. If the re-registration is considered a failure, it will try to register again a preset number of times, with a set time interval between each registration. If the registration still fails after the preset number of re-registrations, it will exit the registration process.

[0022] If the registration file is abnormal, registration will be performed again. Abnormalities in the registration file include the file existing but failing to open, and the file existing and opening successfully, but the registration status recorded in the file is unknown.

[0023] Based on the above technical solution, the TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server. The specific steps include:

[0024] The TBOX terminal receives a configuration file containing data acquisition and diagnostic tasks from the cloud server, enabling task parameter acquisition.

[0025] The system acquires package data and performs diagnostic procedures on the vehicle, uploading the collected data and diagnostic results to the cloud server in real time.

[0026] Based on the above technical solutions,

[0027] When the TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, it determines whether the TBOX terminal has received a notification from the cloud server to delete the configuration file:

[0028] If the TBOX terminal receives a notification from the cloud server to delete the configuration file, it will disable task parameter collection and delete the configuration file.

[0029] If the TBOX terminal does not receive a notification from the cloud server to delete the configuration file, the diagnostic process will continue.

[0030] Based on the above technical solutions,

[0031] The cloud server is also used to encapsulate batch query commands and perform query diagnosis on the vehicle.

[0032] The specific steps of the inquiry-based diagnosis include:

[0033] The cloud server encapsulates batch query commands and sends them to the TBOX terminal via diagnostic commands;

[0034] The TBOX terminal's communication module receives instructions, parses the instructions to obtain diagnostic instructions, and then transmits the diagnostic instructions to the remote diagnostic module.

[0035] The remote diagnostic module receives diagnostic instructions and parses them to obtain query instructions. It then encapsulates the query instructions according to the format of the middleware interface and calls the middleware's batch query interface.

[0036] The middleware returns a response message to the query command, and the remote diagnostic module calls the diagnostic data upload interface to upload the response message to the cloud server.

[0037] The present invention provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the remote diagnostic method for the distributed ECU of a vehicle described above.

[0038] This invention provides a remote diagnostic device for a vehicle's distributed ECU, comprising:

[0039] The registration module is used to drive the TBOX terminal in the vehicle to be diagnosed to register with the cloud server, while the cloud server establishes data collection and diagnosis tasks and sends them to the vehicle.

[0040] The diagnostic module is used by the TBOX terminal to perform a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server.

[0041] The analysis module is used to drive the cloud server to analyze and save the collected data and display the diagnostic results.

[0042] Compared with the prior art, the advantages of the present invention are as follows:

[0043] (1) It is simple and economical to operate. Generally, it can collect data and complete diagnostic tasks by operating on the cloud server. It does not require the purchase of expensive instruments, saving manpower and resources.

[0044] (2) The collected data is stored on the cloud server, which allows for the collection of a large amount of data, which can then be analyzed to make the diagnostic results more reliable and thus improve the accuracy of the diagnosis.

[0045] (3) The entire collection and diagnosis process is carried out under the control of the program, reducing human intervention. Only the collection and diagnosis tasks need to be configured in the cloud, and the rest is done by the program, resulting in more reliable diagnostic results.

[0046] (4) The cloud server and the APP can send tasks at the same time, ensuring that diagnostic tasks can still be performed even when the network conditions are poor, thus improving the reliability of the system. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 This is a flowchart of a remote diagnostic method for a vehicle-wide distributed ECU according to an embodiment of the present invention;

[0049] Figure 2 This is a schematic diagram of the structure corresponding to the remote diagnostic method for the distributed ECU of the whole vehicle in this invention. Detailed Implementation

[0050] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are some embodiments of this application, but not all embodiments.

[0051] This invention provides a remote diagnostic method for a vehicle's distributed ECU, involving various diagnostic communications between a cloud server and an in-vehicle TBOX (intelligent vehicle terminal), diagnostic communications between an intelligent diagnostic APP (application program) and the in-vehicle TBOX terminal, and diagnostic communications between the in-vehicle TBOX terminal and the downstream distributed ECU unit.

[0052] See Figure 1 As shown in the figure, the remote diagnostic method for a vehicle's distributed ECU provided by this embodiment of the invention specifically includes the following steps:

[0053] S1: The TBOX terminal on the vehicle to be diagnosed is registered to the cloud server, and at the same time the cloud server establishes data collection and diagnosis tasks and sends them to the vehicle.

[0054] In this invention, the TBOX terminal on the vehicle to be diagnosed is registered to the cloud server, and the cloud server simultaneously establishes data collection and diagnostic tasks and sends them to the vehicle. Specific steps include:

[0055] S101: The TBOX terminal on the vehicle side to be diagnosed is powered on and registers with the cloud server by calling the diagnostic communication specification interface;

[0056] S102: After the TBOX terminal is successfully registered, a data collection and diagnostic task is created on the cloud server or APP, and the created data collection and diagnostic task is sent to the vehicle.

[0057] After the TBOX terminal that needs to be diagnosed is powered on, the diagnostic communication specification interface is called to register the TBOX terminal to the cloud server. After successful registration, data collection and diagnostic tasks are created on the cloud server or mobile APP and sent to the vehicle.

[0058] For the TBOX terminal, it needs to have communication capabilities with the cloud server. That is, the TBOX terminal needs to maintain a stable communication capability with the cloud server for subsequent diagnostic functions to proceed normally. The main functional logic is as follows:

[0059] (1) The platform communication task of the TBOX terminal is mainly used to receive data from the cloud server, parse the data from the cloud server, obtain the operations that the SDK (Software Development Kit) needs to execute in the cloud server command, and then the platform communication task calls the interfaces or message notifications provided by other modules to complete the execution of the corresponding commands;

[0060] (2) The platform communication task of the TBOX terminal receives instructions from other modules of the SDK, such as the regular acquisition task, and calls the data upload interface of the platform communication task, so that the platform communication task uploads relevant data.

[0061] (3) The serial number used for communication with the cloud server is maintained by the platform's communication task module;

[0062] (3) If the data upload fails, the platform communication task needs to store the corresponding data.

[0063] In this invention, the diagnostic communication specification interface is called to register with the cloud server, and the specific steps include:

[0064] When the TBOX terminal detects that the registration information has been updated, it calls the registration information upload interface. The registration thread then determines whether it has received a registration status update. The registration information upload interface is used to update the registration information and registration status.

[0065] When the registration thread receives a registration status update, it registers the registration information and updates the registration status to indicate success or failure.

[0066] When the registration thread does not receive a registration status update, it checks whether a registration file exists in the registration file directory. If no registration file exists, it sets the idle task to the highest priority and then calls the task scheduling function to perform the registration operation. If a registration file exists, it performs the corresponding operation according to the registration status of the registration file. If the registration is successful, it performs subsequent data collection and diagnostic tasks.

[0067] In other words, for TBOX terminals, they need to have a registration function. The TBOX terminals participating in the diagnostic function must first be registered on the cloud server, and the diagnostic process can only be performed after successful registration.

[0068] In this invention, when the registration status is failed, the TBOX terminal does not enter the data acquisition and diagnostic task mode, and the cloud server does not send the configuration file containing the data acquisition and diagnostic tasks to the TBOX terminal.

[0069] The registration file includes SN (serial number), ICCID (integrated circuit card identification code), VIN (vehicle identification code), and registration status, which includes success, failure, and pending registration.

[0070] When a TBOX terminal calls the registration information upload interface to register, if the registration fails and a preset number of re-registration attempts are made with a set time interval between each attempt, and the registration still fails after the preset number of re-registration attempts, the registration process will be terminated.

[0071] For example, when registering via the registration information upload interface on the TBOX terminal, if registration fails, it can attempt to register a maximum of 9 times. Each registration attempt will have an appropriate delay. The rule is that after the first registration fails, there will be a 2-minute delay before the second registration attempt. If the second registration fails, there will be a 3-minute delay before the third registration attempt, and so on, with a maximum of 10 registration attempts. If all 10 attempts fail, the registration process will be terminated.

[0072] In this invention, when the TBOX terminal is powered on, the registration file is checked. If the previous registration recorded in the registration file was a failure, the registration is re-entered. If the re-registration is considered a failure, the re-registration is performed continuously for a preset number of times, with a set time interval between each registration. If the registration still fails after the preset number of re-registrations, the registration process is exited.

[0073] For example, when powered on, the registration file is checked. If the previous registration failed, the SDK should actively attempt to register. If registration fails again, it should attempt to register up to 10 times. Each registration attempt should have an appropriate delay. The rule is that after the first registration fails, there should be a 2-minute delay before attempting the second registration. If the second registration fails, there should be a 3-minute delay before attempting the third registration, and so on, with a maximum of 10 registration attempts. If all 10 attempts fail, the current registration round is terminated.

[0074] In this invention, when the registration file is abnormal, the registration is re-entered. The abnormality of the registration file includes the file existing but failing to open, and the file existing and opening successfully, but the registration status recorded in the file is unknown.

[0075] That is, when the registration file becomes abnormal for some reason, the SDK should actively re-register.

[0076] S2: The TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server.

[0077] This involves a unified and standardized diagnostic process for the vehicle based on the data collection and diagnostic tasks issued by the cloud server. The collected data and diagnostic results are uploaded to the cloud server, which processes the data and then saves the processed data to its database.

[0078] In this invention, the TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server. Specific steps include:

[0079] S201: The TBOX terminal receives a configuration file containing data acquisition and diagnostic tasks from the cloud server and enables task parameter acquisition.

[0080] S202: Acquire package data and perform diagnostic procedures on the vehicle, uploading the collected data and diagnostic results to the cloud server in real time.

[0081] For TBOX terminals, data acquisition capabilities are required. The cloud server needs to collect information about the components and then analyze it to determine whether the automotive parts are functioning correctly. These acquisition tasks are distributed to the TBOX terminal via configuration files, and the terminal then completes the data acquisition, parsing, and uploading according to the requirements of the configuration files.

[0082] For TBOX terminals, task scheduling management is required. Task scheduling management is a scheduling thread, and the work and task types it performs are shown in Table 1 below:

[0083] Table 1

[0084]

[0085] In this invention, when the TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, it determines whether the TBOX terminal has received a notification from the cloud server to delete the configuration file.

[0086] If the TBOX terminal receives a notification from the cloud server to delete the configuration file, it will disable task parameter collection and delete the configuration file.

[0087] If the TBOX terminal does not receive a notification from the cloud server to delete the configuration file, the diagnostic process will continue.

[0088] Furthermore, when data collection is performed, if the interface of another module does not return correctly during the collection thread, the exception is recorded by calling the exception write interface of the exception upload module.

[0089] S3: The cloud server analyzes and saves the collected data and displays the diagnostic results. Specifically, the cloud service analyzes and processes the collected data to determine the vehicle's operating status, then saves the analyzed data to the cloud service's database. Simultaneously, the diagnostic results are displayed on the cloud server's page or the app interface, providing a clear and intuitive view of the vehicle's current operating status.

[0090] In this invention, the cloud server is also used to encapsulate batch query commands and perform query diagnosis on the vehicle end;

[0091] The specific steps of inquiry-based diagnosis include:

[0092] a: The cloud server encapsulates batch query instructions and sends the instructions to the TBOX terminal through diagnostic instructions;

[0093] b: The communication module of the TBOX terminal receives the instruction, parses the instruction to obtain the diagnostic instruction, and transmits the diagnostic instruction to the remote diagnostic module;

[0094] c: The remote diagnostic module receives diagnostic instructions and parses them to obtain query instructions. It then encapsulates the query instructions according to the format of the middleware interface and calls the middleware's batch query interface.

[0095] d: The middleware returns a response message to the query command, and the remote diagnostic module calls the diagnostic data upload interface to upload the response message to the cloud server.

[0096] In other words, TBOX terminals need to have remote diagnostic batch query capabilities.

[0097] Furthermore, after receiving the response message, the cloud server decides whether to issue the next batch of query commands based on actual needs.

[0098] The remote diagnostic method for the distributed ECU of a vehicle according to the present invention includes a cloud server, an APP, a TBOX terminal, an RBOX_SDK diagnostic service program within the TBOX terminal, and multiple middleware components with specific functions. After the TBOX terminal requiring diagnostics is powered on, it calls the diagnostic communication specification interface and registers with the cloud server. Upon successful registration, it establishes data acquisition and diagnostic tasks on the cloud server or the APP, sends them to the vehicle, and performs a unified and standardized diagnostic process. The acquired data and diagnostic results are uploaded to the cloud server, which processes the data and saves the processed data to its database, greatly improving the storage capacity of diagnostic data and the accuracy of diagnostic results. Simultaneously, the diagnostic results are displayed on the cloud server's page or the APP interface, providing a clear and intuitive view of the vehicle's current operating status. The TBOX terminal runs a diagnostic RBOX_SDK service program, responsible for controlling the entire acquisition and diagnostic process. Multiple middleware components are involved, each with the ability to communicate with the server and perform data reception, processing, and transmission.

[0099] See Figure 2 As shown, the remote diagnostic method for the vehicle distributed ECU of the present invention will be specifically described.

[0100] This includes cloud servers, APP clients, remote diagnostic RBOX_SDK service programs, various middleware with specific functions, TBOX terminals, automotive component ECU units, etc. The implementation of data acquisition tasks and diagnostic tasks will be explained below.

[0101] 1. Data Acquisition Task

[0102] (1) After the TBOX terminal is powered on, it registers with the diagnostic cloud server and sends the registration result back to the vehicle. If it fails, it repeatedly sends the registration request until the registration is successful.

[0103] (2) Establish a data collection task on the cloud server or APP. The collection task is described by the configuration file, including the collection period, collection parameters, etc. The configuration file is sent to the vehicle to establish the collection task.

[0104] (3) After the data acquisition task is established, the RBOX_SDK service program schedules the data acquisition interface of the middleware to acquire data on the CAN bus. After the data is acquired, the middleware encapsulates and packages the data, and then uploads it to the cloud server or APP through the upload interface.

[0105] (4) The cloud server or APP terminal analyzes the collected data and obtains the required collection results.

[0106] 2. Diagnostic tasks

[0107] (1) After the TBOX terminal is powered on, the registration process begins;

[0108] (2) After successful registration, the cloud server or APP will issue diagnostic commands;

[0109] (3) After receiving the diagnostic command, the RBOX_SDK service program parses and executes it, and sends it to the automotive component control unit (ECU) for diagnostic inquiry. The ECU then feeds back the diagnostic results to the RBOX_SDK service program.

[0110] (4) The RBOX_SDK service program calls the relevant interfaces to encapsulate and package the diagnostic results, and uploads them to the cloud server or APP through the diagnostic protocol to complete the diagnostic process.

[0111] This invention utilizes remote diagnostics, eliminating the need for on-site visits and saving labor costs. Data is uploaded to a cloud server, allowing for greater data storage and analysis of larger datasets, resulting in more accurate results. The entire data acquisition and diagnostic process is distributed from the cloud server and controlled by software, minimizing human intervention. The use of standardized diagnostic criteria improves both accuracy and efficiency. Both remote and local diagnostics are supported. Even in poor network conditions, the system can be accessed via Bluetooth through an app, ensuring continued diagnostic functionality and enhancing system availability.

[0112] In one possible implementation, the present invention also provides a non-transitory computer-readable storage medium located in a PLC (Programmable Logic Controller) controller. The storage medium stores a computer program that, when executed by a processor, implements the steps of the following remote diagnostic method for a distributed ECU of a vehicle:

[0113] The TBOX terminal on the vehicle to be diagnosed is registered to the cloud server, and at the same time the cloud server establishes data collection and diagnosis tasks and sends them to the vehicle.

[0114] The TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server.

[0115] The cloud server analyzes and saves the collected data and displays the diagnostic results.

[0116] Storage media may be any combination of one or more computer-readable media. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable storage media may be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0117] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wireline, optical fiber, RF, etc., or any suitable combination thereof.

[0118] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0119] This invention provides a remote diagnostic device for a vehicle's distributed ECU, comprising a registration module, a diagnostic module, and an analysis module.

[0120] The registration module drives the TBOX terminal on the vehicle to be diagnosed to register with the cloud server, while the cloud server establishes data collection and diagnosis tasks and sends them to the vehicle. The diagnosis module is used by the TBOX terminal to perform the diagnosis process on the vehicle based on the data collection and diagnosis tasks, and uploads the collected data and diagnosis results to the cloud server. The analysis module is used to drive the cloud server to analyze and save the collected data, and display the diagnosis results.

[0121] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

[0122] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

Claims

1. A remote diagnostic method for a vehicle's distributed ECU, characterized in that, Specifically, the following steps are included: The TBOX terminal on the vehicle to be diagnosed is registered to the cloud server, and at the same time the cloud server establishes data collection and diagnosis tasks and sends them to the vehicle. The TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server. The cloud server analyzes and saves the collected data and displays the diagnostic results; The TBOX terminal in the vehicle to be diagnosed is registered to the cloud server, and the cloud server simultaneously establishes a data collection and diagnostic task and sends it to the vehicle. The specific steps include: The TBOX terminal on the vehicle side to be diagnosed is powered on and registers with the cloud server by calling the diagnostic communication specification interface; Once the TBOX terminal is successfully registered, a data collection and diagnostic task is created on the cloud server or APP, and then the created data collection and diagnostic task is sent to the vehicle. The specific steps for registering the diagnostic communication specification interface with the cloud server include: When the TBOX terminal detects that the registration information has been updated, it calls the registration information upload interface. The registration thread then determines whether it has received a registration status update. The registration information upload interface is used to update the registration information and registration status. When the registration thread receives a registration status update, it registers the registration information and updates the registration status to indicate success or failure. When the registration thread does not receive a registration status update, it checks whether a registration file exists in the registration file directory. If the registration file does not exist, it sets the idle task to the highest priority, then calls the task scheduling function to perform the registration operation. If the registration file exists, it performs the corresponding operation according to the registration status of the registration file.

2. The remote diagnostic method for a vehicle's distributed ECU as described in claim 1, characterized in that: When the registration status is failed, the TBOX terminal will not enter the data acquisition and diagnostic task mode, and the cloud server will not send the configuration file containing the data acquisition and diagnostic tasks to the TBOX terminal. The registration file includes SN, ICCID, VIN and registration status, which includes success, failure and pending registration. When a TBOX terminal calls the registration information upload interface to register, if the registration fails and a preset number of re-registration attempts are made with a set time interval between each attempt, and the registration still fails after the preset number of re-registration attempts, the registration process will be terminated.

3. The remote diagnostic method for a vehicle's distributed ECU as described in claim 1, characterized in that: When the TBOX terminal is powered on, it checks the registration file. If the previous registration recorded in the registration file was a failure, it will try to register again. If the re-registration is considered a failure, it will try to register again a preset number of times, with a set time interval between each registration. If the registration still fails after the preset number of re-registrations, it will exit the registration process. If the registration file is abnormal, registration will be performed again. Abnormalities in the registration file include the file existing but failing to open, and the file existing and opening successfully, but the registration status recorded in the file is unknown.

4. The remote diagnostic method for a vehicle's distributed ECU as described in claim 1, characterized in that, The TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, and uploads the acquired data and diagnostic results to the cloud server. The specific steps include: The TBOX terminal receives a configuration file containing data acquisition and diagnostic tasks from the cloud server, enabling task parameter acquisition. The system acquires package data and performs diagnostic procedures on the vehicle, uploading the collected data and diagnostic results to the cloud server in real time.

5. The remote diagnostic method for a vehicle's distributed ECU as described in claim 4, characterized in that: When the TBOX terminal performs a diagnostic process on the vehicle based on data acquisition and diagnostic tasks, it determines whether the TBOX terminal has received a notification from the cloud server to delete the configuration file: If the TBOX terminal receives a notification from the cloud server to delete the configuration file, it will disable task parameter collection and delete the configuration file. If the TBOX terminal does not receive a notification from the cloud server to delete the configuration file, the diagnostic process will continue.

6. The remote diagnostic method for a vehicle's distributed ECU as described in claim 1, characterized in that: The cloud server is also used to encapsulate batch query commands and perform query diagnosis on the vehicle. The specific steps of the inquiry-based diagnosis include: The cloud server encapsulates batch query commands and sends them to the TBOX terminal via diagnostic commands; The TBOX terminal's communication module receives instructions, parses the instructions to obtain diagnostic instructions, and then transmits the diagnostic instructions to the remote diagnostic module. The remote diagnostic module receives diagnostic instructions and parses them to obtain query instructions. It then encapsulates the query instructions according to the format of the middleware interface and calls the middleware's batch query interface. The middleware returns a response message to the query command, and the remote diagnostic module calls the diagnostic data upload interface to upload the response message to the cloud server.

7. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the remote diagnostic method for a vehicle-wide distributed ECU as described in any one of claims 1 to 6.

Images