Vehicle data flashing method, diagnostic equipment and flashing system

Abstract

The present application is applicable to the field of automobile technology, and provides a vehicle data flashing method, diagnostic equipment and flashing system. The method is applied to a first diagnostic device, the first diagnostic device is communicatively connected with a second diagnostic device, the first diagnostic device is communicatively connected with a first vehicle, and the second diagnostic device is communicatively connected with a second vehicle. The method includes obtaining the first vehicle information when receiving the second vehicle information sent by the second diagnostic device, and detecting whether the first vehicle information matches the second vehicle information; when detecting that the first vehicle information matches the second vehicle information, sending matching information to the second diagnostic device, and when receiving the flashing data sent by the second diagnostic device, flashing the data of the first ECU of the first vehicle. The embodiment of the present application can flash data by reading the ECU flashing data of similar vehicles whose vehicle information matches, thereby improving the efficiency and convenience of data flashing.

Description

Technical Field

[0001] The present application belongs to the field of automobile technology, and in particular relates to a vehicle data flashing method, diagnostic equipment and flashing system. Background Art

[0002] With the continuous development of automobile technology, the systems of automobiles are becoming more and more intelligent, and different software are loaded in the Electronic Control Units (ECU) with different functions.

[0003] After the vehicle is produced, if the software loaded in the ECU has changed or has defects and needs to be upgraded, the manufacturer or user needs to flash the ECU software or data. The existing flashing method usually downloads the corresponding flashing file through the Internet for flashing. When the network fails, the network signal is poor, or the server storing the flashing file has problems, the flashing cannot be performed, which affects the efficiency and convenience of the flashing. Summary of the invention

[0004] The embodiments of the present application provide a vehicle data flashing method, diagnostic equipment and flashing system, which are intended to solve the existing problem that when a network failure occurs or a problem occurs in a server storing the flashing file, flashing cannot be performed, thereby affecting the flashing efficiency and convenience.

[0005] In a first aspect, a method for flashing vehicle data is applied to a first diagnostic device, wherein the first diagnostic device is communicatively connected to a second diagnostic device, the first diagnostic device is communicatively connected to a first vehicle, and the second diagnostic device is communicatively connected to a second vehicle, wherein the communication connection is a local area network communication connection or an electrical connection, and the method comprises:

[0006] When receiving the second vehicle information sent by the second diagnostic device, acquiring the first vehicle information and detecting whether the first vehicle information matches the second vehicle information;

[0007] When detecting that the first vehicle information matches the second vehicle information, sending matching information to the second diagnostic device, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information;

[0008] When the flashing data is received, data is flashed to the first ECU of the first vehicle.

[0009] In one embodiment, when receiving the second vehicle information sent by the second diagnostic device, acquiring the first vehicle information and detecting whether the first vehicle information matches the second vehicle information includes:

[0010] Upon receiving the second vehicle identification sent by the second diagnostic device, acquiring the first vehicle identification;

[0011] When detecting that the first vehicle identifier matches the second vehicle identifier, sending a first matching instruction to the second diagnostic device, so that when the second diagnostic device receives the first matching instruction, it obtains the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU, and returns the second ECU identifier and the second software identifier to the first diagnostic device;

[0012] Upon receiving the second ECU identifier and the second software identifier sent by the second diagnostic device, acquiring the first ECU identifier of the first vehicle and the first software identifier of the first ECU;

[0013] When it is detected that the second ECU identifier matches the first ECU identifier, and the second software identifier is an updated version identifier of the second software, it is determined that the first vehicle information matches the second vehicle information.

[0014] In one embodiment, when receiving the flashing data, flashing data to the first ECU of the first vehicle includes:

[0015] When receiving the flashing address information and the flashing data size, sending a request instruction for obtaining the flashing data to the second diagnostic device, so that when the second diagnostic device receives the flashing data request instruction, the flashing data is sent to the first diagnostic device in packets;

[0016] When receiving the flashing data, flashing data to the first ECU of the first vehicle according to the flashing address information;

[0017] When the total amount of received flash data reaches the flash data size and the flashing of all received flash data is completed, it is determined that the flashing of the first ECU of the first vehicle is successful.

[0018] In one embodiment, when receiving the flashing address information and the flashing data size, sending a request instruction for obtaining the flashing data to the second diagnostic device includes:

[0019] When receiving the flashing address information and the flashing data size, sending a security verification request to the first ECU;

[0020] When receiving the verification success instruction sent by the first ECU, a request instruction for obtaining the flashing data is sent to the second diagnostic device.

[0021] In a second aspect, an embodiment of the present application provides a method for flashing vehicle data, which is applied to a second diagnostic device, wherein the second diagnostic device is communicatively connected to a first diagnostic device, the first diagnostic device is communicatively connected to a first vehicle, and the second diagnostic device is communicatively connected to a second vehicle, wherein the communication connection is a local area network communication connection or an electrical connection, and the method includes:

[0022] Upon receiving a flashing instruction sent by a user, acquiring the second vehicle information, and sending the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information;

[0023] When the matching information is received, the flashing data of the second ECU of the second vehicle is sent to the first diagnostic device, so that when the first diagnostic device receives the flashing data, the data of the first ECU of the first vehicle is flashed.

[0024] In one embodiment, upon receiving a flashing instruction sent by a user, acquiring the second vehicle information, and sending the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information, includes:

[0025] Upon receiving a flashing instruction sent by a user, acquiring the second vehicle identification, and sending the second vehicle identification to the first diagnostic device, so that the first diagnostic device sends a first matching instruction to the second diagnostic device when detecting that the first vehicle identification matches the second vehicle identification;

[0026] When the first matching instruction is received, the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU are obtained, and the second ECU identifier and the second software identifier are returned to the first diagnostic device, so that when the first diagnostic device detects that the second ECU identifier matches the first ECU identifier and the second software identifier is an updated version identifier of the second software, it determines that the first vehicle information matches the second vehicle information and sends matching information to the second diagnostic device.

[0027] In one embodiment, when the matching information is received, sending the flashing data of the second ECU of the second vehicle to the first diagnostic device includes:

[0028] When receiving the matching information, sending a security verification request to the second ECU;

[0029] When receiving the verification success instruction sent by the second ECU, the flashing data is acquired and sent to the first diagnostic device.

[0030] In one embodiment, the obtaining the flash data and sending the flash data to the first diagnostic device includes:

[0031] Acquire the flash data size of the second ECU, and send the flash data size to the first diagnostic device;

[0032] When receiving a data flashing request instruction sent by the first diagnostic device, the flashing data is acquired and the flashing data is sent to the first diagnostic device in packets, so that the first diagnostic device flashes data to the first ECU of the first vehicle.

[0033] In a third aspect, an embodiment of the present application provides a vehicle data flashing device, which is applied to a first diagnostic device, including:

[0034] a detection module, configured to, upon receiving the second vehicle information sent by the second diagnostic device, obtain the first vehicle information and detect whether the first vehicle information matches the second vehicle information;

[0035] a sending module, configured to send matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information;

[0036] The flashing module is used to flash the data of the first ECU of the first vehicle when receiving the flashing data.

[0037] In a fourth aspect, an embodiment of the present application provides a vehicle data flashing device, which is applied to a second diagnostic device, including:

[0038] an acquisition module, configured to acquire the second vehicle information upon receiving a flashing instruction sent by a user, and send the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information;

[0039] The receiving module is used to send the flashing data of the second ECU of the second vehicle to the first diagnostic device when receiving the matching information, so that the first diagnostic device flashes the data of the first ECU of the first vehicle when receiving the flashing data.

[0040] In a fifth aspect, an embodiment of the present application provides a diagnostic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data flashing method of the first aspect when executing the computer program, or implements the steps of the data flashing method of the second aspect when executing the computer program.

[0041] In a sixth aspect, an embodiment of the present application provides a data flashing system, including a first diagnostic device and a second diagnostic device:

[0042] The first diagnostic device is used to perform the steps of the vehicle data flashing method as described in the first aspect;

[0043] The second diagnostic device is used to execute the steps of the vehicle data flashing method as described in the second aspect.

[0044] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the above-mentioned computer program is executed by a processor, it implements the steps of the data flushing method described in the first aspect, or when the above-mentioned computer program is executed by a processor, it implements the steps of the data flushing method described in the second aspect.

[0045] In an eighth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on an electronic device, it enables the electronic device to execute the steps of the data flushing method described in the first aspect above, or enables the electronic device to implement the steps of the data flushing method described in the second aspect above when executed.

[0046] Compared with the prior art, the embodiment of the present application has the following beneficial effects: in the embodiment of the present application, since the first diagnostic device is connected in communication with the second diagnostic device, the first diagnostic device is connected in communication with the first vehicle, and the second diagnostic device is connected in communication with the second vehicle, the communication connection is a local area network communication connection or an electrical connection, and when the second vehicle information sent by the second diagnostic device is received, the first vehicle information is obtained, and it is detected whether the first vehicle information matches the second vehicle information; when it is detected that the first vehicle information matches the second vehicle information, matching information is sent to the second diagnostic device, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information; when the flashing data is received, the first ECU of the first vehicle is flashed. When the flashing data cannot be obtained due to special problems (such as network failure, poor network signal or problems with the server storing the flashing file), data can be flashed by reading the flashing data of the ECU of the same vehicle with matching vehicle information, thereby improving the efficiency and convenience of data flashing. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0048] Figure 1 This is a diagram of the vehicle data flashing system architecture provided in Example 1 of the present application;

[0049] Figure 2 It is a flowchart of the vehicle data flashing method provided in the first embodiment of the present application;

[0050] Figure 3 It is a flowchart of the vehicle data flashing method provided in the second embodiment of the present application;

[0051] Figure 4 It is a flowchart of another vehicle data flashing method provided in the second embodiment of the present application;

[0052] Figure 5 It is a flowchart of another vehicle data flashing method provided in the second embodiment of the present application;

[0053] Figure 6 It is a flowchart of the vehicle data flashing method provided in the third embodiment of the present application;

[0054] Figure 7 It is a flowchart of another vehicle data flashing method provided in Embodiment 3 of the present application;

[0055] Figure 8 is a structural schematic diagram of a first diagnostic device provided in Embodiment 4 of the present application;

[0056] Fig. 9 is a schematic diagram of the structure of a second diagnostic device provided in Embodiment 4 of the present application;

[0057] Fig.10 It is a schematic diagram of the structure of a diagnostic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0058] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0059] In order to illustrate the technical solution described in this application, a specific embodiment is provided below.

[0060] Embodiment 1

[0061] An embodiment of the present application provides a vehicle data flashing system, wherein the vehicle data flashing system 1 includes a first diagnostic device 10 and a second diagnostic device 20, wherein the first diagnostic device 10 is communicatively connected to a first vehicle 30, and the second diagnostic device 20 is communicatively connected to a second vehicle 40, wherein the communication connection is a local area network communication connection or an electrical connection.

[0062] In a specific application scenario, the first diagnostic device is a first on-board diagnostic (OBD) device, and the second diagnostic device is a second OBD device. The first OBD device is connected to the first vehicle through a vehicle OBD diagnostic interface on the first vehicle, and the second OBD device is connected to the second vehicle through a vehicle OBD diagnostic interface on the second vehicle, and the first OBD device and the second OBD device communicate through a local area network communication method such as Bluetooth or WIFI.

[0063] In one embodiment, the embodiment of the present application provides a vehicle data flashing method, the vehicle data flashing method comprising: when the second diagnostic device receives the flashing instruction sent by the user, the second vehicle information is obtained, and the second vehicle information is sent to the first diagnostic device; when the first diagnostic device receives the second vehicle information sent by the second diagnostic device, the first vehicle information is obtained, and the first vehicle information is detected whether the first vehicle information matches the second vehicle information, and when the first vehicle information matches the second vehicle information, the matching information is sent to the second diagnostic device; when the second diagnostic device receives the matching information, the second diagnostic device returns the flashing data of the second ECU of the second vehicle to the first diagnostic device; when the first diagnostic device receives the flashing data, the first diagnostic device performs data flashing on the first ECU of the first vehicle. Specifically, in the embodiment of the present application, the functions of the first diagnostic device and the second diagnostic device can be implemented by the same diagnostic device; that is, in the same vehicle data flashing scenario, two diagnostic devices of the same model are respectively plugged into the vehicle OBD diagnostic interfaces of the first vehicle and the second vehicle, and the functions of the first diagnostic device and the second diagnostic device are correspondingly implemented. This application does not make specific restrictions on this, and separately elaborates on some flashing functions on the first vehicle and the second vehicle.

[0064] In a specific embodiment, see Figure 2 , showing a schematic diagram of a vehicle data flashing method, the vehicle data flashing method is applied to the above-mentioned vehicle flashing system, the method comprising:

[0065] Step S101: When receiving a flashing instruction sent by a user, the second diagnostic device obtains the second vehicle identification and sends the second vehicle identification to the first diagnostic device.

[0066] Specifically, the vehicle identification may include the vehicle model and the type of ECU that needs to be flashed. The user may send a flashing instruction to the second diagnostic device through a preset button in the diagnostic device or in an APP preloaded in the diagnostic device. When the second diagnostic device receives the flashing instruction, it obtains the identification of the vehicle connected to itself and the type of EUC to be flashed, such as the types of ECUs including engine EUC, ignition ECU, battery ECU, etc. The model and ECU type of the second vehicle are sent to the first diagnostic device.

[0067] In an application, when the second diagnostic device receives a flashing instruction sent by a user, if the flashing instruction includes the vehicle model information and ECU type to be flashed (such as flashing data for the engine ECU of the vehicle model information Mercedes-Benz S350), the user can select or enter the vehicle model and ECU type to be flashed on the APP of the diagnostic device, and submit the flashing instruction containing the vehicle model information and ECU type. When the second diagnostic device receives the vehicle model information and ECU type included in the flashing instruction, it obtains the vehicle model information of the connected vehicle, and detects whether the vehicle model information of the vehicle connected to the second diagnostic device is the same as the vehicle model information included in the flashing instruction. If the vehicle model information of the vehicle connected to the second diagnostic device is the same as the vehicle model information included in the flashing instruction, the vehicle model information of the second vehicle and the ECU type to be flashed are sent to the first diagnostic device.

[0068] In one embodiment, the diagnostic device obtains the vehicle model information of the connected vehicle by: sending a command to obtain the vehicle identification code to the vehicle in sequence according to the pre-stored diagnostic protocols of N types of vehicle models; the diagnostic protocol of the vehicle cannot be confirmed at the beginning, so the command to obtain the vehicle identification code (VIN code) is sent to the OBD system in the vehicle in sequence according to the pre-stored multiple diagnostic protocols in a preset order; when the vehicle identification code returned by the vehicle based on a certain diagnostic protocol is received, the vehicle identification code is obtained, and the vehicle model information is determined according to the vehicle identification. For example, the vehicle identification code can be a 17-byte vehicle identification. Assuming that the VIN code is WDD2210222a253260, it means that this car series is Mercedes-Benz (BENZ) and the model is S350.

[0069] Step S102, when the first diagnostic device receives the second vehicle identification sent by the second diagnostic device, it obtains the first vehicle identification, and when it is detected that the first vehicle identification matches the second vehicle identification, it sends a first matching instruction to the second diagnostic device.

[0070] Specifically, the first diagnostic device receives the second vehicle identification sent by the second diagnostic device, obtains the model of the first vehicle connected to the first diagnostic device, such as when receiving the model information of the second vehicle and the type of ECU to be flashed, obtains the model information of the first vehicle, and the acquisition of the model information of the first vehicle can be the same as the acquisition of the model information of the connected vehicle, which is not repeated here. And when it is detected that the model of the first vehicle matches the model of the second vehicle, a first matching instruction is sent to the second diagnostic device.

[0071] Step S103, when the second diagnostic device receives the first matching instruction, it obtains the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU, and returns the second ECU identifier and the second software identifier to the first diagnostic device.

[0072] Specifically, when the second diagnostic device receives the first matching instruction, it indicates that the models of the two vehicles are the same, and at this time, the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU are obtained, and the second ECU identifier and the second software identifier are returned to the first diagnostic device. In this way, the model of the ECU corresponding to the second vehicle and the software version number loaded in the ECU are obtained.

[0073] In one embodiment, before the second ECU of the second vehicle is identified and the second software identification corresponding to the second ECU is obtained, a communication connection is established with the second ECU, such as obtaining the diagnostic information of the second ECU, establishing a communication connection between the diagnostic device and the second ECU; the diagnostic information of the ECU includes the diagnostic protocol of the ECU; and sending an activation command to the ECU. After obtaining the diagnostic information of the ECU, a communication connection between the diagnostic device and the ECU is established according to the diagnostic protocol included in the diagnostic information of the ECU, and an activation command is sent to the ECU. After the ECU is activated, the ECU identification and the software identification loaded by the ECU can be obtained from the ECU. If it is an engine ECU, the command 0x22f001 is sent to the engine ECU, and the engine ECU returns 0x62f001030402, 03 indicates that the engine model is ME28, and 0402 indicates that the software version is 4.2, and then the engine model and software version number are sent to the first diagnostic device.

[0074] Step S104: When the first diagnostic device receives the second ECU identifier and the second software identifier sent by the second diagnostic device, it obtains the first ECU identifier of the first vehicle and the first software identifier of the first ECU; when it is detected that the second ECU identifier matches the first ECU identifier and the second software identifier is an updated version identifier of the second software, it is determined that the first vehicle information matches the second vehicle information, and matching information is sent to the second diagnostic device.

[0075] Specifically, when the first diagnostic device receives the second ECU identifier and the second software identifier sent by the second diagnostic device, it obtains the ECU identifier of the first vehicle, referred to as the first ECU identifier, and obtains the identifier of the software loaded on the first vehicle, referred to as the first software identifier. It is determined whether the second ECU identifier is the same as the first ECU identifier. The ECU identifier can be understood as the version number of the loaded software. If the ECU is an engine ECU, the ECU identifier is the engine model. Detecting whether the second ECU identifier matches the first ECU identifier can be detecting whether the models of the first ECU and the second ECU are consistent. If the models of the first ECU and the second ECU are consistent, and the second software identifier is an updated version identifier of the second software, it is determined that the first vehicle information matches the second vehicle information, and matching information is sent to the second diagnostic device.

[0076] Step S105, when the second diagnostic device receives the matching information, it sends a security verification request to the second ECU, and when receiving the verification success instruction sent by the second ECU, it obtains the flashing address information and the flashing data size of the second ECU, and sends the flashing address information and the flashing data size to the first diagnostic device.

[0077] Specifically, when the second diagnostic device receives the matching information, it indicates that the second vehicle is a vehicle that can provide flash data for the ECU corresponding to the first vehicle. It first sends a safety verification request to the second ECU to perform engine safety verification, which can prevent illegal operation of the engine. When receiving the verification success instruction sent by the second ECU, it can send a command to ask the ECU for the starting address of the flash data and the number of all bytes. For example, when sending the command 0x2300, the ECU replies 0x6300112233440000ffff, 0x11223344 is the starting address, and 0x0000ffff is the number of bytes of all data, and then sends the starting address and the number of bytes to the first diagnostic device.

[0078] In one application scenario, the specific process of performing a safety check on the engine ECU may be: sending a safety check request to the engine ECU. When the engine ECU receives the safety check request, the engine ECU returns a safety check code. The diagnostic device generates corresponding verification information based on the safety check code according to the safety check rules set for the vehicle model in advance. After the diagnostic device generates the corresponding verification information, it sends the verification information to the engine ECU so that the engine ECU verifies the verification information. When the engine ECU verifies the verification information successfully, it returns a successful verification instruction based on the verification information. The diagnostic device receives the successful verification instruction returned by the engine ECU based on the verification information. After the diagnostic device passes the engine safety check, the vehicle-mounted device can control the state of the engine ECU.

[0079] In a specific application scenario, for example, ECU security verification is performed through commands to prevent illegal operations, which is equivalent to a password. For example, the diagnosis first sends the 0x2703 command to the corresponding ECU, and the ECU will reply with a SEED data, such as 0x670311223344, where 11223344 is the SEED data. After obtaining the SEED data, the SEED data must be calculated into a CODE code through a preset decryption algorithm. Only when the CODE code is calculated correctly, the ECU is allowed to perform a flash operation. The diagnostic device can calculate the CODE code from SEED through the diagnostic algorithm. For example, 0x11223344 is calculated through the preset decryption. The CODE is 0x55667788. The calculated CODE code is filled into the security verification command and sent to the ECU, such as 0x270455667788. After the engine ECU receives the CODE code, it will perform calculation verification in the ECU to see if it is correct. If the CODE is correct, it will return the correct data to the diagnostic device, such as 0x6704, which means that the ECU's safety check has passed. After the engine ECU passes the safety verification, it sends a command to the engine ECU to inquire about the starting address and the number of all bytes of the read data. For example, it sends the command 0x2300, and the ECU replies 0x6300112233440000ffff, where 0x11223344 is the starting address and 0x0000ffff is the number of bytes of all data.

[0080] Step S106, when the first diagnostic device receives the flash address information and the flash data size, it sends a security verification request to the first ECU; when receiving the verification success instruction sent by the first ECU, it sends a request instruction for obtaining the flash data to the second diagnostic device.

[0081] Specifically, when the first diagnostic device receives the flash address information and the flash data size, it also needs to send a safety verification request to the first ECU to perform engine safety verification, which can prevent illegal operation of the ECU. Send a safety verification request to the first ECU; when receiving the verification success instruction sent by the first ECU, send a request instruction to obtain the flash data to the second diagnostic device.

[0082] Step S107 : When the second diagnostic device receives the request instruction for flashing data, it sends the flashing data to the first diagnostic device in packets.

[0083] Specifically, considering that the amount of the flash data may be large, the second diagnostic device may group the data and send the data to the first diagnostic device in multiple batches.

[0084] For example, in a specific application scenario, the second diagnostic device reads 1024 bytes each time, and sends a command 0x351122334400000400 to the second ECU, where 0x35 indicates that ECU data is to be read, 0x11223344 indicates the address of the ECU data to be read (this address is different for each command as the address of the read data is different), and 0x00000400 is 1024 in decimal, indicating the number of bytes to be read. After each reading, the 1024 bytes read are sent to the first diagnostic device in sequence. If the last frame of data may be less than 1024 bytes, it is sent according to the actual received data.

[0085] Step S108, when the first diagnostic device receives the flash data, it flashes data to the first ECU of the first vehicle; when the total amount of flash data received reaches the flash data size and the flashing of all the received flash data is completed, it is determined that the flashing of the first ECU of the first vehicle is successful.

[0086] Specifically, when the flashing data is received, data is flashed to the first ECU of the first vehicle according to the flashing address; when it is calculated that the number of bytes received from the second diagnostic device has reached the total number of bytes to be flashed and all these data are flashed successfully, it means that the flashing is completed.

[0087] In the embodiment of the present application, when the flash data cannot be obtained due to special problems (such as network failure, poor network signal, or problems with the server storing the flash file), data can be flashed by reading the ECU flash data of a similar vehicle with matching vehicle information, thereby improving data flashing efficiency and convenience.

[0088] Embodiment 2

[0089] The embodiment of the present application provides a vehicle data flashing method, which is applied to a first diagnostic device, wherein the first diagnostic device is communicatively connected to a second diagnostic device, the first diagnostic device is communicatively connected to a first vehicle, and the second diagnostic device is communicatively connected to a second vehicle, wherein the communication connection is a local area network communication connection or an electrical connection, such as Figure 3 As shown, the method includes:

[0090] Step S201, upon receiving the second vehicle information sent by the second diagnostic device, obtaining the first vehicle information, and detecting whether the first vehicle information matches the second vehicle information.

[0091] In the application, the second vehicle information is obtained by the second diagnostic device when receiving a flash instruction sent by a user, and the second vehicle information is sent to the first diagnostic device.

[0092] In one embodiment, Figure 4 As shown, step S201 includes steps S2011 to S2014, including:

[0093] Step S2011, upon receiving the second vehicle identification sent by the second diagnostic device, acquiring the first vehicle identification;

[0094] Step S2012, when it is detected that the first vehicle identifier matches the second vehicle identifier, sending a first matching instruction to the second diagnostic device, so that when the second diagnostic device receives the first matching instruction, it obtains the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU, and returns the second ECU identifier and the second software identifier to the first diagnostic device;

[0095] Step S2013, upon receiving the second ECU identifier and the second software identifier sent by the second diagnostic device, acquiring the first ECU identifier of the first vehicle and the first software identifier of the first ECU;

[0096] Step S2014: when it is detected that the second ECU identifier matches the first ECU identifier and the second software identifier is an updated version identifier of the second software, it is determined that the first vehicle information matches the second vehicle information.

[0097] Specifically, the same or similar parts of the above steps S2011 to S2014 and the above steps S101 to S104 can be found in the relevant descriptions of steps S101 to S104, which will not be repeated here.

[0098] Step S202, when it is detected that the first vehicle information matches the second vehicle information, matching information is sent to the second diagnostic device, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information.

[0099] Specifically, when it is detected that the second ECU identifier matches the first ECU identifier and the second software identifier is an updated version identifier of the second software, it is determined that the first vehicle information matches the second vehicle information, and matching information is sent to the second diagnostic device.

[0100] In one embodiment, when the second diagnostic device receives the matching information, it sends a security verification request to the second ECU, and when receiving the verification success instruction sent by the second ECU, it obtains the flashing address information and the flashing data size of the second ECU, and sends the flashing address information and the flashing data size to the first diagnostic device.

[0101] Specifically, the contents of step S202 are the same as or similar to those of step S104 and step S105, and details thereof may be found in the relevant descriptions of step S104 and step S105, which will not be repeated here.

[0102] Step S203: When the flashing data is received, flashing data is performed on the first ECU of the first vehicle.

[0103] In one embodiment, Figure 5 As shown, step S203 includes steps S2031 to S2033:

[0104] Step S2031, when receiving the flashing address information and the flashing data size, sending a request instruction for obtaining the flashing data to the second diagnostic device, so that when the second diagnostic device receives the flashing data request instruction, it sends the flashing data to the first diagnostic device in packets;

[0105] In one embodiment, when the flash address information and the flash data size are received, a request instruction for obtaining the flash data is sent to the second diagnostic device, including: when the flash data size is received, a request for safety verification is sent to the first ECU; when a verification success instruction is received from the first ECU, a request instruction for obtaining the flash data is sent to the second diagnostic device.

[0106] Step S2032, when the flashing data is received, flashing the first ECU of the first vehicle according to the flashing address information;

[0107] Step S2033: When the total amount of received flash data reaches the flash data size and the flashing of all received flash data is completed, it is determined that the flashing of the first ECU of the first vehicle is successful.

[0108] Specifically, the same or similar parts of the above steps S2031 to S2033 and the above steps S106 to S108 can be found in the relevant descriptions of steps S106 to S108, which will not be repeated here.

[0109] In the embodiment of the present application, when the flash data cannot be obtained due to special problems (such as network failure, poor network signal, or problems with the server storing the flash file), data can be flashed by reading the ECU flash data of a similar vehicle with matching vehicle information, thereby improving data flashing efficiency and convenience.

[0110] Embodiment 3

[0111] The embodiment of the present application provides a vehicle data flashing method, which is applied to a second diagnostic device, wherein the second diagnostic device is communicatively connected to a first diagnostic device, the first diagnostic device is communicatively connected to a first vehicle, and the second diagnostic device is communicatively connected to a second vehicle, wherein the communication connection is a local area network communication connection or an electrical connection, such as Figure 6 As shown, the method includes:

[0112] Step S301, upon receiving a flash instruction sent by a user, obtaining the second vehicle information, and sending the second vehicle information to the first diagnostic device, so that when the first diagnostic device detects that the first vehicle information matches the second vehicle information, the first diagnostic device returns matching information to the second diagnostic device;

[0113] Specifically, when a flash instruction sent by the user is received, the second vehicle information is obtained, and the second vehicle information is sent to the first diagnostic device, so that when the first diagnostic device receives the second vehicle information, it obtains the first vehicle information, and when it detects that the first vehicle information matches the second vehicle information, it returns matching information to the second diagnostic device.

[0114] In one embodiment, step S301 includes steps S3011 to S3016:

[0115] Step S3011, upon receiving the flashing instruction sent by the user, obtaining the second vehicle identification, and sending the second vehicle identification to the first diagnostic device, so that the first diagnostic device sends a first matching instruction to the second diagnostic device when detecting that the first vehicle identification matches the second vehicle identification;

[0116] Step S3012, when the first matching instruction is received, the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU are obtained, and the second ECU identifier and the second software identifier are returned to the first diagnostic device, so that when the first diagnostic device detects that the second ECU identifier matches the first ECU identifier and the second software identifier is an updated version identifier of the second software, it determines that the first vehicle information matches the second vehicle information and sends matching information to the second diagnostic device.

[0117] Specifically, the same or similar parts of the above steps S3031 to S3012 and the above steps S101 to S104 can be found in the relevant descriptions of steps S101 to S104, which will not be repeated here.

[0118] Step S302, when the matching information is received, the flashing data of the second ECU of the second vehicle is sent to the first diagnostic device, so that when the first diagnostic device receives the flashing data, it flashes the data of the first ECU of the first vehicle.

[0119] In one embodiment, when the matching information is received, the flashing data of the second ECU of the second vehicle is sent to the first diagnostic device, including: when the matching information is received, sending a request for safety verification to the second ECU; when receiving the verification success instruction sent by the second ECU, obtaining the flashing data, and sending the flashing data to the first diagnostic device.

[0120] In one embodiment, the obtaining the flashing data and sending the flashing data to the first diagnostic device includes: obtaining the flashing data size and flashing address information of the second ECU, and sending the flashing data size and the flashing address information to the first diagnostic device;

[0121] When receiving a request instruction for flashing data sent by the first diagnostic device, the flashing data is read according to the flashing address, and the flashing data is sent to the first diagnostic device in packets, so that the first diagnostic device flashes data to the first ECU of the first vehicle.

[0122] Specifically, the same or similar parts of the above-mentioned step S302 and the above-mentioned steps S105 to S108 can be specifically referred to the relevant descriptions of steps S105 to S108, which will not be repeated here.

[0123] In the embodiment of the present application, when the flash data cannot be obtained due to special problems (such as network failure, poor network signal, or problems with the server storing the flash file), data can be flashed by reading the ECU flash data of a similar vehicle with matching vehicle information, thereby improving data flashing efficiency and convenience.

[0124] It should be noted that the above-mentioned Embodiment 1, Embodiment 2 and Embodiment 3 are embodiments with different execution entities, and the specific technical contents can be referenced to each other.

[0125] In response to the above vehicle data flashing method, on the one hand, the embodiment of the present application further provides a vehicle data flashing device, which is applied to a first diagnostic device, including:

[0126] a detection module, configured to, upon receiving the second vehicle information sent by the second diagnostic device, obtain the first vehicle information and detect whether the first vehicle information matches the second vehicle information;

[0127] a sending module, configured to send matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information;

[0128] The flashing module is used to flash the data of the first ECU of the first vehicle when receiving the flashing data.

[0129] On the other hand, an embodiment of the present application provides a vehicle data flashing device, which is applied to a second diagnostic device, including:

[0130] an acquisition module, configured to acquire the second vehicle information upon receiving a flashing instruction sent by a user, and send the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information;

[0131] The receiving module is used to send the flashing data of the second ECU of the second vehicle to the first diagnostic device when receiving the matching information, so that the first diagnostic device flashes the data of the first ECU of the first vehicle when receiving the flashing data.

[0132] Embodiment 4

[0133] The present application embodiment provides a vehicle data flashing system, such as Figure 1 As shown, the vehicle data flashing system includes a first diagnostic device 10 and a second diagnostic device 20, wherein the first diagnostic device 10 is communicatively connected to a first vehicle 30, and the second diagnostic device 20 is communicatively connected to a second vehicle 40, wherein the communication connection is a local area network communication connection or an electrical connection.

[0134] like Figure 8 As shown, the first diagnostic device 10 includes:

[0135] The detection module 11 is used to obtain the first vehicle information and detect whether the first vehicle information matches the second vehicle information when receiving the second vehicle information sent by the second diagnostic device;

[0136] The sending module 12 is used to send matching information to the second diagnostic device when it is detected that the first vehicle information matches the second vehicle information, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information;

[0137] The flashing module 13 is used to flash the data of the first ECU of the first vehicle when receiving the flashing data.

[0138] like Fig. 9 As shown, the second diagnostic device 20 includes:

[0139] an acquisition module 21, configured to acquire the second vehicle information upon receiving a flashing instruction sent by a user, and send the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information;

[0140] The receiving module 22 is used to send the flashing data of the second ECU of the second vehicle to the first diagnostic device when receiving the matching information, so that the first diagnostic device flashes the data of the first ECU of the first vehicle when receiving the flashing data.

[0141] In the embodiment of the present application, when the flash data cannot be obtained due to special problems (such as network failure, poor network signal, or problems with the server storing the flash file), data can be flashed by reading the ECU flash data of a similar vehicle with matching vehicle information, thereby improving data flashing efficiency and convenience.

[0142] Embodiment 5

[0143] Embodiment 5 of the present application provides a schematic diagram of a terminal device, such as Fig.10 As shown, the diagnostic device 100 in this embodiment includes: a processor 1001, a memory 1002, and a computer program 1003 stored in the memory 1002 and executable on the processor 1001, wherein the computer program includes:

[0144] a detection module, configured to, upon receiving the second vehicle information sent by the second diagnostic device, obtain the first vehicle information and detect whether the first vehicle information matches the second vehicle information;

[0145] a sending module, configured to send matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information;

[0146] The flashing module is used to flash the data of the first ECU of the first vehicle when receiving the flashing data.

[0147] an acquisition module, configured to acquire the second vehicle information upon receiving a flashing instruction sent by a user, and send the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information;

[0148] The receiving module is used to send the flashing data of the second ECU of the second vehicle to the first diagnostic device when receiving the matching information, so that the first diagnostic device flashes the data of the first ECU of the first vehicle when receiving the flashing data.

[0149] The diagnostic device 100 may be a vehicle-mounted device, a smart device, a computer, a notebook, a PDA or other computing device. The diagnostic device 100 may include, but is not limited to, a processor 1001 and a memory 1002. Those skilled in the art will appreciate that Fig.10 It is only an example of the diagnostic device 100 and does not constitute a limitation of the diagnostic device 100. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the above-mentioned diagnostic device 100 may also include input and output devices, network access devices, buses, etc.

[0150] The processor 1001 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0151] The memory 1002 may be an internal storage unit of the diagnostic device 100, such as a hard disk or memory of the diagnostic device 100. The memory 1002 may also be an external storage device of the diagnostic device 100, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the diagnostic device 100. Further, the memory 1002 may also include both an internal storage unit of the diagnostic device 100 and an external storage device. The memory 1002 is used to store the computer program and other programs and data required by the diagnostic device 100. The memory 1002 may also be used to temporarily store data that has been output or is to be output.

[0152] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0153] In the several embodiments provided in this application, it should be understood that the disclosed systems, servers and methods can be implemented in other ways. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

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

[0155] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for flashing vehicle data, characterized in that: Applied to a first diagnostic device, the first diagnostic device is communicatively connected to a second diagnostic device, the first diagnostic device is communicatively connected to a first vehicle, the second diagnostic device is communicatively connected to a second vehicle, the first diagnostic device is a first OBD device, the second diagnostic device is a second OBD device, the first OBD device is connected to the first vehicle via a vehicle OBD diagnostic interface on the first vehicle, the second OBD device is connected to the second vehicle via a vehicle OBD diagnostic interface on the second vehicle, the method comprises: When receiving the second vehicle information sent by the second diagnostic device, acquiring the first vehicle information and detecting whether the first vehicle information matches the second vehicle information includes: Upon receiving the second vehicle identification sent by the second diagnostic device, acquiring the first vehicle identification; When detecting that the first vehicle identifier matches the second vehicle identifier, sending a first matching instruction to the second diagnostic device, so that when the second diagnostic device receives the first matching instruction, it obtains the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU, and returns the second ECU identifier and the second software identifier to the first diagnostic device; Upon receiving the second ECU identifier and the second software identifier sent by the second diagnostic device, acquiring the first ECU identifier of the first vehicle and the first software identifier of the first ECU; When it is detected that the second ECU identifier matches the first ECU identifier, and the second software identifier is an updated version identifier of the second software, determining that the first vehicle information matches the second vehicle information; When detecting that the first vehicle information matches the second vehicle information, sending matching information to the second diagnostic device, so that the second diagnostic device returns the flashing data of the second ECU of the second vehicle when receiving the matching information; When the flashing data is received, data is flashed to the first ECU of the first vehicle.

2. The method according to claim 1, characterized in that When the flashing data is received, flashing data to the first ECU of the first vehicle includes: When receiving the flashing address information and the size of the flashing data, sending a request instruction for obtaining the flashing data to the second diagnostic device, so that when the second diagnostic device receives the request instruction for the flashing data, the flashing data is sent to the first diagnostic device in packets; When receiving the flashing data, flashing data to the first ECU of the first vehicle according to the flashing address information; When the total amount of received flash data reaches the flash data size and the flashing of all received flash data is completed, it is determined that the flashing of the first ECU of the first vehicle is successful.

3. The method according to claim 2, characterized in that The step of sending a request instruction for obtaining the flashing data to the second diagnostic device upon receiving the flashing address information and the flashing data size comprises: When receiving the flashing address information and the flashing data size, sending a security verification request to the first ECU; When receiving the verification success instruction sent by the first ECU, a request instruction for obtaining the flashing data is sent to the second diagnostic device.

4. A method for flashing vehicle data, characterized in that: Applied to a second diagnostic device, the second diagnostic device is communicatively connected to a first diagnostic device, the first diagnostic device is communicatively connected to a first vehicle, the second diagnostic device is communicatively connected to a second vehicle, the first diagnostic device is a first OBD device, the second diagnostic device is a second OBD device, the first OBD device is connected to the first vehicle via a vehicle OBD diagnostic interface on the first vehicle, the second OBD device is connected to the second vehicle via a vehicle OBD diagnostic interface on the second vehicle, the method comprises: Upon receiving a flashing instruction sent by a user, obtaining second vehicle information, and sending the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information; upon receiving the second vehicle identification sent by the second diagnostic device, the first diagnostic device obtains the first vehicle identification; upon detecting that the first vehicle identification matches the second vehicle identification, sending a first matching instruction to the second diagnostic device, so that upon receiving the first matching instruction, the second diagnostic device obtains the second ECU identification of the second vehicle and the second software identification corresponding to the second ECU, and returns the second ECU identification and the second software identification to the first diagnostic device; upon receiving the second ECU identification and the second software identification sent by the second diagnostic device, obtaining the first ECU identification of the first vehicle and the first software identification of the first ECU; upon detecting that the second ECU identification matches the first ECU identification, and the second software identification is an updated version identification of the second software, determining that the first vehicle information matches the second vehicle information; When the matching information is received, the flashing data of the second ECU of the second vehicle is sent to the first diagnostic device, so that when the first diagnostic device receives the flashing data, the data of the first ECU of the first vehicle is flashed.

5. The method according to claim 4, characterized in that Upon receiving a flashing instruction sent by a user, acquiring the second vehicle information, and sending the second vehicle information to the first diagnostic device, so that the first diagnostic device returns matching information to the second diagnostic device when detecting that the first vehicle information matches the second vehicle information, including: Upon receiving a flashing instruction sent by a user, acquiring the second vehicle identification, and sending the second vehicle identification to the first diagnostic device, so that the first diagnostic device sends a first matching instruction to the second diagnostic device when detecting that the first vehicle identification matches the second vehicle identification; When the first matching instruction is received, the second ECU identifier of the second vehicle and the second software identifier corresponding to the second ECU are obtained, and the second ECU identifier and the second software identifier are returned to the first diagnostic device, so that when the first diagnostic device detects that the second ECU identifier matches the first ECU identifier and the second software identifier is an updated version identifier of the second software, it determines that the first vehicle information matches the second vehicle information and sends matching information to the second diagnostic device.

6. The method according to claim 5, characterized in that When the matching information is received, the flashing data of the second ECU of the second vehicle is sent to the first diagnostic device, including: When receiving the matching information, sending a security verification request to the second ECU; When receiving the verification success instruction sent by the second ECU, the flashing data is acquired and sent to the first diagnostic device.

7. The method according to claim 6, characterized in that The step of obtaining the flash data and sending the flash data to the first diagnostic device includes: Acquire the flash data size and the flash address information of the second ECU, and send the flash data size and the flash address information to the first diagnostic device; When receiving a request instruction for flashing data sent by the first diagnostic device, the flashing data is read according to the flashing address, and the flashing data is sent to the first diagnostic device in packets, so that the first diagnostic device flashes data to the first ECU of the first vehicle.

8. A diagnostic device, characterized in that The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 3 is implemented; or when the processor executes the computer program, the method according to claims 4 to 7 is implemented.

9. A vehicle data flashing system, characterized in that: The first diagnostic device and the second diagnostic device include: The first diagnostic device is used to perform the steps of the vehicle data flashing method according to any one of claims 1 to 3; The second diagnostic device is used to execute the steps of the vehicle data flashing method as described in any one of claims 4 to 7.

Images