A vehicle diagnosis method, apparatus, device and medium

Abstract

The application discloses a vehicle diagnosis method and device, equipment and medium, relates to the technical field of vehicle diagnosis, and is applied to a client and includes the following steps: uploading vehicle information of a vehicle to be diagnosed to a server to obtain a whole-vehicle electronic control unit list corresponding to the vehicle information issued by the server; determining a target electronic control unit list selected by a target user from the whole-vehicle electronic control unit list, and uploading the target electronic control unit list to the server, so that the server determines a diagnosis data packet corresponding to the target electronic control unit list; obtaining the diagnosis data packet issued by the server, and using the diagnosis data packet to diagnose the vehicle to be diagnosed. Through the above scheme, the user can autonomously select the electronic control unit to be diagnosed, and only needs to download the corresponding diagnosis data packet, thereby avoiding the problem that the diagnosis time is too long and the network bandwidth is wasted due to the downloading of the whole-vehicle diagnosis data packet each time, and the diagnosis efficiency and user experience are improved.

Description

Technical Field

[0001] This invention relates to the field of vehicle diagnostic technology, and in particular to a vehicle diagnostic method, apparatus, equipment and medium. Background Technology

[0002] With the continuous development of automotive electronics, Electronic Control Units (ECUs) have been widely used in modern automobiles. While ECUs improve vehicle power, economy, comfort, and safety, they also make the vehicle's electronic and electrical systems increasingly complex, prompting greater development in automotive diagnostic technology. Throughout the vehicle lifecycle, to facilitate the exchange of diagnostic data, improve the efficiency of R&D, testing, production, and after-sales service, and reduce diagnostic data management costs, an open-source standardized diagnostic data format—ODX (Open Diagnostic Data Exchange)—has gained increasing adoption. ODX is an open-source standardized diagnostic data format based on the XML language. The ODX standard was developed with data exchangeability throughout the entire diagnostic development process in mind, standardizing the data format. Its application can improve the efficiency of R&D, testing, production, and after-sales service, and reduce diagnostic data management costs.

[0003] As ODX becomes increasingly widely used in automotive diagnostics, the mainstream application scenario for ODX diagnostics is as follows: OEM technicians develop ODX and OTX (Open Test sequence eXchange format) files for each ECU of the vehicle model. Then, they configure the systems included in the vehicle in the file representing the vehicle configuration information (i.e., the -v file) within the ODX file, package it into a vehicle diagnostic data file package, and upload it to the server. The diagnostic client downloads the vehicle's diagnostic data package from the server to its local machine using the VIN (Vehicle Identification Number) and vehicle model name. The client parses the entire vehicle's diagnostic data package, displays the vehicle topology, and the user selects a specific system to execute a specific function, thereby completing the vehicle diagnostics.

[0004] However, the existing solution has the problem of low efficiency because the scenario will download and parse the diagnostic data of all ECUs in the vehicle by default, which takes a long time. Sometimes users only want to diagnose the function of one or more systems in the vehicle and do not need to parse all EUCs, which will cause waste of resources and time, reduce diagnostic efficiency and user experience.

[0005] In summary, how to avoid downloading the entire vehicle's diagnostic data package during vehicle diagnostics, in order to further improve diagnostic efficiency and user experience, is a problem that needs to be solved. Summary of the Invention

[0006] In view of this, the purpose of this invention is to provide a vehicle diagnostic method, apparatus, device, and medium that can avoid downloading the entire vehicle's diagnostic data package during the vehicle diagnostic process, thereby further improving diagnostic efficiency and user experience. The specific solution is as follows:

[0007] Firstly, this application discloses a vehicle diagnostic method applied to a client, comprising:

[0008] Upload the vehicle information of the vehicle to be diagnosed to the server to obtain a list of vehicle electronic control units corresponding to the vehicle information issued by the server.

[0009] The system determines the list of target electronic control units selected by the target user from the list of vehicle electronic control units, and uploads the list of target electronic control units to the server so that the server can determine the diagnostic data package corresponding to the list of target electronic control units.

[0010] Obtain the diagnostic data packet sent by the server, and use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0011] Optionally, uploading the target electronic control unit list to the server so that the server can determine the diagnostic data package corresponding to the target electronic control unit list includes:

[0012] The target electronic control unit list is uploaded to the server, so that the server can filter out the target diagnostic files corresponding to each target electronic control unit in the target electronic control unit list from the vehicle diagnostic data package, update the system configuration file using the target electronic control unit list, and package the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data package to obtain a diagnostic data package.

[0013] Optionally, the step of using the diagnostic data packet to diagnose the vehicle to be diagnosed includes:

[0014] The diagnostic data packet is parsed to obtain the corresponding diagnostic data and the system configuration file, and a vehicle topology map is constructed based on the system configuration file;

[0015] The vehicle topology map is displayed on a preset interface, and the vehicle to be diagnosed is diagnosed using corresponding diagnostic data based on the electronic control unit system currently selected by the target user from the vehicle topology map.

[0016] Optionally, uploading the vehicle information of the vehicle to be diagnosed to the server includes:

[0017] The system reads the vehicle information of the vehicle to be diagnosed and uploads the vehicle information to the server; wherein, the vehicle information includes the vehicle identification number and vehicle model information.

[0018] Secondly, this application discloses a vehicle diagnostic method applied to a server, comprising:

[0019] Obtain the vehicle information of the vehicle to be diagnosed uploaded by the client, and send the list of vehicle electronic control units corresponding to the vehicle information to the client;

[0020] Obtain the list of target electronic control units selected by the target user from the list of vehicle electronic control units uploaded by the client, and determine the diagnostic data package corresponding to the list of target electronic control units;

[0021] The diagnostic data packet is sent to the client so that the client can use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0022] Optionally, determining the diagnostic data package corresponding to the target electronic control unit list includes:

[0023] Target diagnostic files corresponding to each target electronic control unit in the target electronic control unit list are selected from the vehicle diagnostic data package; the target diagnostic files include target ODX files and target OTX files corresponding to each target electronic control unit;

[0024] The system configuration file is updated using the target electronic control unit list, and the target diagnostic file, the updated system configuration file, and other target files in the vehicle diagnostic data package are packaged to obtain a diagnostic data package; the target files include multilingual files and vehicle menu configuration files.

[0025] Optionally, updating the system configuration file using the target electronic control unit list includes:

[0026] The system configuration file in the ODX file is determined, and the system configuration list in the system configuration file is updated using the target electronic control unit list; wherein, the system configuration file is used to record vehicle configuration information.

[0027] Thirdly, this application discloses a vehicle diagnostic device applied to a client, comprising:

[0028] The list acquisition module is used to upload the vehicle information of the vehicle to be diagnosed to the server in order to obtain a list of vehicle electronic control units corresponding to the vehicle information issued by the server.

[0029] The list selection module is used to determine the list of target electronic control units selected by the target user from the list of vehicle electronic control units;

[0030] The diagnostic data packet determination module is used to upload the target electronic control unit list to the server so that the server can determine the diagnostic data packet corresponding to the target electronic control unit list.

[0031] The vehicle diagnostic module is used to obtain the diagnostic data packet sent by the server and use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0032] Fourthly, this application discloses an electronic device, comprising:

[0033] Memory, used to store computer programs;

[0034] A processor is configured to execute the computer program to implement the steps of the aforementioned disclosed vehicle diagnostic method.

[0035] Fifthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the steps of the aforementioned disclosed vehicle diagnostic method.

[0036] As can be seen, this application involves the client uploading vehicle information of the vehicle to be diagnosed to the server to obtain a list of vehicle electronic control units (ECUs) corresponding to the vehicle information sent by the server; determining the target ECU list selected by the target user from the list of vehicle ECUs, and uploading the target ECU list to the server so that the server can determine the diagnostic data packet corresponding to the target ECU list; obtaining the diagnostic data packet sent by the server, and using the diagnostic data packet to diagnose the vehicle to be diagnosed. Thus, the client in this application first uploads the vehicle information of the vehicle to be diagnosed to the server so that the server returns a list of vehicle ECUs corresponding to the vehicle information. Then, the user can select the ECUs to be diagnosed from the list of vehicle ECUs to form a target ECU list. After the user confirms, the client uploads the target ECU list to the server. Finally, the server determines the corresponding diagnostic data packet based on the target ECU list and sends the diagnostic data packet to the client. The client then parses the diagnostic data packet to diagnose the vehicle to be diagnosed. With the above solution, users can choose the electronic control unit that needs to be diagnosed and only need to download the corresponding diagnostic data package. This avoids the problem of downloading the whole vehicle diagnostic data package for each diagnosis, which leads to excessive diagnosis time and waste of network bandwidth, thereby improving diagnostic efficiency and user experience. Attached Figure Description

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

[0038] Figure 1 This is a flowchart of a vehicle diagnostic method disclosed in this application;

[0039] Figure 2 This is a schematic diagram of a list of electronic control units for a vehicle disclosed in this application;

[0040] Figure 3 This is a flowchart of a specific vehicle diagnostic method disclosed in this application;

[0041] Figure 4 This is a schematic diagram of a specific vehicle diagnostic process disclosed in this application;

[0042] Figure 5 This is a flowchart of another vehicle diagnostic method disclosed in this application;

[0043] Figure 6 This is a schematic diagram of the structure of a vehicle diagnostic device disclosed in this application;

[0044] Figure 7 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0045] 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 only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0046] The current mainstream application scenario for ODX diagnostics is as follows: OEM technicians develop ODX and OTX files for each ECU of the vehicle model, then configure the systems included in the vehicle in the -v file, package them into a vehicle diagnostic data file package, upload it to the server, and the diagnostic client downloads the vehicle's diagnostic data package from the server to the local machine using the VIN and vehicle model name. The client parses the entire vehicle's diagnostic data package, displays the vehicle topology, and the user selects a specific system to execute a specific function, thereby completing the vehicle diagnostics.

[0047] However, existing solutions suffer from inefficiency because they default to downloading and parsing diagnostic data from all ECUs in the vehicle, which is time-consuming. Sometimes, users only want to diagnose the function of one or more systems in the vehicle and do not need to parse all ECUs, thus wasting resources and time and reducing diagnostic efficiency and user experience. Therefore, this application discloses a vehicle diagnostic method, apparatus, device, and medium that can avoid downloading the entire vehicle's diagnostic data package during the vehicle diagnostic process, thereby further improving diagnostic efficiency and user experience.

[0048] See Figure 1 As shown in the figure, this application discloses a vehicle diagnostic method applied to a client, the method comprising:

[0049] Step S11: Upload the vehicle information of the vehicle to be diagnosed to the server to obtain the list of vehicle electronic control units corresponding to the vehicle information issued by the server.

[0050] In this embodiment, after the target user runs the diagnostic client, the client first identifies the vehicle information of the vehicle to be diagnosed and uploads the vehicle information to the server so that the server can return a list of vehicle electronic control units corresponding to the vehicle information.

[0051] Step S12: Determine the list of target electronic control units selected by the target user from the list of vehicle electronic control units, and upload the list of target electronic control units to the server so that the server can determine the diagnostic data package corresponding to the list of target electronic control units.

[0052] In this embodiment, the target user can select the electronic control units (ECUs) to be diagnosed from the list of vehicle ECUs to form a target ECU list. The client then uploads the target ECU list to the server, so that the server can determine the corresponding diagnostic data package based on the target ECU list. In this way, the user can independently select the ECUs to be diagnosed and only needs to download the corresponding diagnostic data package, avoiding the problem of downloading the entire vehicle diagnostic data package for each diagnosis, which would lead to excessively long diagnosis time and wasted network bandwidth, thereby improving diagnostic efficiency and user experience.

[0053] For example, see Figure 2 As shown, after the server returns the list of vehicle electronic control units (ECUs), the target user can independently select the ECU systems that need to be diagnosed and check the corresponding selection boxes. After the target user confirms, these selected ECU systems form the target ECU list, which the client then uploads to the server. The server then packages the corresponding diagnostic data files based on the target ECU list to form a diagnostic data package. Figure 2As shown, the target user selected EMS, BCM, GW, T-BOX, and IPK ECU systems. Therefore, the server only needs to package the diagnostic data files corresponding to the aforementioned ECU systems. Furthermore, it should be noted that if the user does not make a selection, the program defaults to selecting all systems in the vehicle.

[0054] Step S13: Obtain the diagnostic data packet sent by the server, and use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0055] In this embodiment, the server sends diagnostic data packets to the client, which then downloads and parses the diagnostic data packets to perform diagnostics on the vehicle to be diagnosed.

[0056] As can be seen, this application involves the client uploading vehicle information of the vehicle to be diagnosed to the server to obtain a list of vehicle electronic control units (ECUs) corresponding to the vehicle information sent by the server; determining the target ECU list selected by the target user from the list of vehicle ECUs, and uploading the target ECU list to the server so that the server can determine the diagnostic data packet corresponding to the target ECU list; obtaining the diagnostic data packet sent by the server, and using the diagnostic data packet to diagnose the vehicle to be diagnosed. Thus, the client in this application first uploads the vehicle information of the vehicle to be diagnosed to the server so that the server returns a list of vehicle ECUs corresponding to the vehicle information. Then, the user can select the ECUs to be diagnosed from the list of vehicle ECUs to form a target ECU list. After the user confirms, the client uploads the target ECU list to the server. Finally, the server determines the corresponding diagnostic data packet based on the target ECU list and sends the diagnostic data packet to the client. The client then parses the diagnostic data packet to diagnose the vehicle to be diagnosed. With the above solution, users can choose the electronic control unit that needs to be diagnosed and only need to download the corresponding diagnostic data package. This avoids the problem of downloading the whole vehicle diagnostic data package for each diagnosis, which leads to excessive diagnosis time and waste of network bandwidth, thereby improving diagnostic efficiency and user experience.

[0057] See Figure 3 and Figure 4 As shown, this application discloses a specific vehicle diagnostic method. Compared to the previous embodiment, this embodiment further explains and optimizes the technical solution. Specifically, it includes:

[0058] Step S21: Read the vehicle information of the vehicle to be diagnosed and upload the vehicle information to the server to obtain the list of vehicle electronic control units corresponding to the vehicle information issued by the server; wherein, the vehicle information includes vehicle identification number and vehicle model information.

[0059] In this embodiment, the vehicle information of the vehicle to be diagnosed may specifically include the vehicle identification number (VIN) and vehicle model information. After obtaining the VIN and vehicle model information, the server can determine the list of vehicle electronic control units (ECUs) corresponding to the vehicle and send the list of ECUs to the client.

[0060] Step S22: Determine the list of target electronic control units selected by the target user from the list of vehicle electronic control units, and upload the list of target electronic control units to the server. The server then filters out the target diagnostic files corresponding to each target electronic control unit in the list of target electronic control units from the vehicle diagnostic data package. After updating the system configuration file using the list of target electronic control units, the server packages the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data package to obtain a diagnostic data package.

[0061] In this embodiment, after the client uploads the target electronic control unit list to the server, the server can filter out the target diagnostic files corresponding to each target electronic control unit in the target electronic control unit list from the vehicle diagnostic data package. Furthermore, the server also needs to update the system configuration file using the target electronic control unit list. Then, the server packages the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data package together to obtain the final diagnostic data package.

[0062] Step S23: Obtain the diagnostic data packet sent by the server, parse the diagnostic data packet to obtain the corresponding diagnostic data and the system configuration file, and construct a vehicle topology map based on the system configuration file.

[0063] In this embodiment, the client obtains the diagnostic data packet sent by the server, parses the diagnostic data packet to obtain the corresponding diagnostic data and system configuration file, and constructs a vehicle topology map based on the system configuration file. That is, the vehicle topology map constructed by the client only needs to display the ECU system selected by the target user, and does not need to display all ECU systems. It can be understood that the diagnostic data packet carries the system configuration file (i.e., the -v file), and the LOGICAL-LINKS tag in the -v file configures the list of ECU system configurations for the vehicle. Each LOGICAL-LINKS represents a system, and the diagnostic client parses this tag to display the vehicle topology map.

[0064] Step S24: Display the vehicle topology map on the preset interface, and diagnose the vehicle to be diagnosed based on the electronic control unit system currently selected by the target user from the vehicle topology map using the corresponding diagnostic data.

[0065] In this embodiment, the client displays the constructed vehicle topology diagram on a preset interface, allowing the user to intuitively understand the topological relationships between the various ECUs within the vehicle. Furthermore, based on the electronic control unit system currently selected by the target user from the vehicle topology diagram, the corresponding diagnostic data is used to diagnose the vehicle to be diagnosed.

[0066] As can be seen, in this embodiment, the vehicle information of the vehicle to be diagnosed may specifically include the vehicle identification number (VIN) and vehicle model information. Furthermore, after the client uploads the target electronic control unit (ECU) list to the server, the server can filter out the target diagnostic files corresponding to each ECU in the target ECU list from the vehicle diagnostic data package. Further, the server needs to update the system configuration file using the target ECU list. Then, the server packages the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data package together to obtain the final diagnostic data package. Finally, after the client parses the diagnostic data package to obtain the corresponding diagnostic data and system configuration file, it needs to construct a vehicle topology diagram based on the system configuration file, allowing the user to intuitively understand the topological relationships between the various ECUs within the vehicle. Through this solution, users can independently select the ECU system to be diagnosed, greatly reducing unnecessary download and parsing time and improving diagnostic efficiency.

[0067] See Figure 5 As shown in the embodiment of this application, another vehicle diagnostic method is disclosed, applied to a server. The method includes:

[0068] Step S31: Obtain the vehicle information of the vehicle to be diagnosed uploaded by the client, and send the list of vehicle electronic control units corresponding to the vehicle information to the client.

[0069] In this embodiment, after the server obtains the vehicle information of the vehicle to be diagnosed uploaded by the client, it sends the list of vehicle electronic control units corresponding to the vehicle information to the client.

[0070] Step S32: Obtain the list of target electronic control units selected by the target user from the list of vehicle electronic control units uploaded by the client, and determine the diagnostic data package corresponding to the list of target electronic control units.

[0071] In this embodiment, after the target user selects the target electronic control unit list from the list of vehicle electronic control units, the client uploads the target electronic control unit list to the server, and then the server determines the diagnostic data packet corresponding to the target electronic control unit list.

[0072] In a specific implementation, determining the diagnostic data package corresponding to the target electronic control unit list includes: filtering target diagnostic files from the vehicle diagnostic data package corresponding to each target electronic control unit in the target electronic control unit list; the target diagnostic files include target ODX files and target OTX files corresponding to each target electronic control unit; updating the system configuration file using the target electronic control unit list, and packaging the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data package to obtain the diagnostic data package; the target files include multilingual files and vehicle menu configuration files. It should be noted that the vehicle diagnostic data package includes target ODX files and target OTX files corresponding to each electronic control unit, as well as other target files. The target files include multilingual files and vehicle menu configuration files; that is, the vehicle diagnostic data package includes all files related to vehicle diagnostics. Each ECU has its own separate ODX file, and the compressed package formed by the ODX files of all ECUs is a PDX file; furthermore, each OTX file corresponds to a specific functional flow.

[0073] Therefore, after obtaining the list of target electronic control units uploaded by the client, the server needs to filter out the target ODX and target OTX files corresponding to each target electronic control unit in the target electronic control unit list from the vehicle diagnostic data package. It also needs to update the system configuration file using the target electronic control unit list. Then, the target ODX files, target OTX files, updated system configuration files, multilingual files, and vehicle menu configuration files are packaged together to obtain the diagnostic data package. In another implementation, the ODX and OTX files corresponding to ECUs not selected by the target user can be deleted from the vehicle diagnostic data package. After updating the system configuration file using the target electronic control unit list, the remaining diagnostic files in the vehicle diagnostic data package are then packaged to obtain the diagnostic data package.

[0074] Furthermore, it should be noted that the above-mentioned updating of the system configuration file using the target electronic control unit list specifically includes: determining the system configuration file in the ODX file, and updating the system configuration list in the system configuration file using the target electronic control unit list; wherein, the system configuration file is used to record vehicle configuration information. It is understood that the ODX file also includes a system configuration file, i.e., a -v file, which records the number of ECUs in the vehicle configuration, the names of the ECUs, and communication pin information, etc. Therefore, this embodiment also needs to update the system configuration list in the system configuration file using the target electronic control unit list, that is, trimming the system configuration list in the -v file to the user-uploaded target electronic control unit list, thereby automatically modifying the corresponding system topology in the -v file.

[0075] Step S33: Send the diagnostic data packet to the client so that the client can use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0076] In this embodiment, the server sends the packaged diagnostic data packet to the client so that the client can use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0077] As can be seen, in this embodiment, after the server obtains the vehicle information of the vehicle to be diagnosed uploaded by the client, it sends the list of vehicle electronic control units corresponding to the vehicle information to the client. When the target user selects a target electronic control unit from the list, the client uploads the target electronic control unit list to the server, and then the server determines the diagnostic data package corresponding to the target electronic control unit list. Finally, the server sends the packaged diagnostic data package to the client so that the client can use the diagnostic data package to diagnose the vehicle to be diagnosed. Specifically, when determining the diagnostic data package corresponding to the target electronic control unit list, it is necessary to filter out the target ODX file and target OTX file corresponding to each target electronic control unit in the target electronic control unit list from the vehicle diagnostic data package. Furthermore, it is necessary to update the system configuration file using the target electronic control unit list. Then, the target ODX file, target OTX file, updated system configuration file, multilingual file, and vehicle menu configuration file are packaged together to obtain the diagnostic data package. In addition, when updating the system configuration file, it mainly uses the target electronic control unit list to update the system configuration list in the system configuration file, and the system configuration file is also located in the ODX file. In this way, users can choose the electronic control unit that needs to be diagnosed and only need to download the corresponding diagnostic data package, avoiding the problem of downloading the whole vehicle diagnostic data package for each diagnosis, which leads to excessive diagnosis time and waste of network bandwidth, thereby improving diagnostic efficiency and user experience.

[0078] See Figure 6 As shown in the figure, this application discloses a vehicle diagnostic device applied to a client, the device comprising:

[0079] The list acquisition module 11 is used to upload the vehicle information of the vehicle to be diagnosed to the server in order to obtain the list of vehicle electronic control units corresponding to the vehicle information issued by the server.

[0080] List selection module 12 is used to determine the list of target electronic control units selected by the target user from the list of vehicle electronic control units;

[0081] The diagnostic data packet determination module 13 is used to upload the target electronic control unit list to the server so that the server can determine the diagnostic data packet corresponding to the target electronic control unit list.

[0082] The vehicle diagnostic module 14 is used to obtain the diagnostic data packet sent by the server and use the diagnostic data packet to diagnose the vehicle to be diagnosed.

[0083] As can be seen, this application involves the client uploading vehicle information of the vehicle to be diagnosed to the server to obtain a list of vehicle electronic control units (ECUs) corresponding to the vehicle information sent by the server; determining the target ECU list selected by the target user from the list of vehicle ECUs, and uploading the target ECU list to the server so that the server can determine the diagnostic data packet corresponding to the target ECU list; obtaining the diagnostic data packet sent by the server, and using the diagnostic data packet to diagnose the vehicle to be diagnosed. Thus, the client in this application first uploads the vehicle information of the vehicle to be diagnosed to the server so that the server returns a list of vehicle ECUs corresponding to the vehicle information. Then, the user can select the ECUs to be diagnosed from the list of vehicle ECUs to form a target ECU list. After the user confirms, the client uploads the target ECU list to the server. Finally, the server determines the corresponding diagnostic data packet based on the target ECU list and sends the diagnostic data packet to the client. The client then parses the diagnostic data packet to diagnose the vehicle to be diagnosed. With the above solution, users can choose the electronic control unit that needs to be diagnosed and only need to download the corresponding diagnostic data package. This avoids the problem of downloading the whole vehicle diagnostic data package for each diagnosis, which leads to excessive diagnosis time and waste of network bandwidth, thereby improving diagnostic efficiency and user experience.

[0084] In some specific embodiments, the diagnostic data packet determination module 13 may specifically include:

[0085] The data packet packaging unit is used to upload the target electronic control unit list to the server, so that the server can filter out the target diagnostic files corresponding to each target electronic control unit in the target electronic control unit list from the vehicle diagnostic data packet, update the system configuration file using the target electronic control unit list, and package the target diagnostic files, the updated system configuration file and other target files in the vehicle diagnostic data packet to obtain a diagnostic data packet.

[0086] In some specific embodiments, the vehicle diagnostic module 14 may specifically include:

[0087] A data packet parsing unit is used to parse the diagnostic data packet to obtain the corresponding diagnostic data and the system configuration file, and to construct a vehicle topology map based on the system configuration file;

[0088] The diagnostic unit is used to display the vehicle topology map on a preset interface and, based on the electronic control unit system currently selected by the target user from the vehicle topology map, to diagnose the vehicle to be diagnosed using corresponding diagnostic data.

[0089] In some specific embodiments, the list acquisition module 11 may specifically include:

[0090] The information uploading unit is used to read the vehicle information of the vehicle to be diagnosed and upload the vehicle information to the server; wherein, the vehicle information includes the vehicle identification number and vehicle model information.

[0091] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Specifically, it may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the vehicle diagnostic method performed by the electronic device disclosed in any of the foregoing embodiments.

[0092] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0093] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0094] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored on it include operating system 221, computer program 222 and data 223, etc., and the storage method can be temporary storage or permanent storage.

[0095] The operating system 221 manages and controls the various hardware devices and computer programs 222 on the electronic device 20 to enable the processor 21 to perform calculations and processing on the massive amounts of data 223 in the memory 22. The operating system 221 can be Windows, Unix, Linux, etc. The computer program 222, in addition to including a computer program capable of performing the vehicle diagnostic method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, may further include computer programs capable of performing other specific tasks. The data 223 may include data received by the electronic device from external devices, as well as data collected by its own input / output interface 25.

[0096] Furthermore, embodiments of this application also disclose a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by a processor, it implements the method steps performed during vehicle diagnostics as disclosed in any of the foregoing embodiments.

[0097] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0098] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0099] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0100] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0101] The present invention provides a detailed description of a vehicle diagnostic method, apparatus, device, and storage medium. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A vehicle diagnostic method, characterized in that, Applied to the client side, including: Upload the vehicle information of the vehicle to be diagnosed to the server to obtain a list of vehicle electronic control units corresponding to the vehicle information issued by the server. The system determines the list of target electronic control units selected by the target user from the list of vehicle electronic control units, and uploads the list of target electronic control units to the server so that the server can determine the diagnostic data package corresponding to the list of target electronic control units. Obtain the diagnostic data packet sent by the server, and use the diagnostic data packet to diagnose the vehicle to be diagnosed; The step of uploading the list of target electronic control units to the server so that the server can determine the diagnostic data package corresponding to the list of target electronic control units includes: The target electronic control unit (ECU) list is uploaded to the server, so that the server can filter out the target diagnostic files corresponding to each target ECU in the target ECU list from the vehicle diagnostic data package, update the system configuration file using the target ECU list, and package the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data package to obtain a diagnostic data package; the target diagnostic files include target ODX files and target OTX files corresponding to each target ECU, and the target files include multilingual files and vehicle menu configuration files.

2. The vehicle diagnostic method according to claim 1, characterized in that, The process of diagnosing the vehicle to be diagnosed using the diagnostic data packet includes: The diagnostic data packet is parsed to obtain the corresponding diagnostic data and the system configuration file, and a vehicle topology map is constructed based on the system configuration file; The vehicle topology map is displayed on a preset interface, and the vehicle to be diagnosed is diagnosed using corresponding diagnostic data based on the electronic control unit system currently selected by the target user from the vehicle topology map.

3. The vehicle diagnostic method according to claim 1, characterized in that, Uploading the vehicle information of the vehicle to be diagnosed to the server includes: The system reads the vehicle information of the vehicle to be diagnosed and uploads the vehicle information to the server; wherein, the vehicle information includes the vehicle identification number and vehicle model information.

4. A vehicle diagnostic method, characterized in that, Applied to servers, including: Obtain the vehicle information of the vehicle to be diagnosed uploaded by the client, and send the list of vehicle electronic control units corresponding to the vehicle information to the client; Obtain the list of target electronic control units selected by the target user from the list of vehicle electronic control units uploaded by the client, and determine the diagnostic data package corresponding to the list of target electronic control units; The diagnostic data packet is sent to the client so that the client can use the diagnostic data packet to diagnose the vehicle to be diagnosed. The step of determining the diagnostic data package corresponding to the target electronic control unit list includes: Target diagnostic files corresponding to each target electronic control unit in the target electronic control unit list are selected from the vehicle diagnostic data package; the target diagnostic files include target ODX files and target OTX files corresponding to each target electronic control unit; The system configuration file is updated using the target electronic control unit list, and the target diagnostic file, the updated system configuration file, and other target files in the vehicle diagnostic data package are packaged to obtain a diagnostic data package; the target files include multilingual files and vehicle menu configuration files.

5. The vehicle diagnostic method according to claim 4, characterized in that, The step of updating the system configuration file using the target electronic control unit list includes: The system configuration file in the ODX file is determined, and the system configuration list in the system configuration file is updated using the target electronic control unit list; wherein, the system configuration file is used to record vehicle configuration information.

6. A vehicle diagnostic device, characterized in that, Applied to the client side, including: The list acquisition module is used to upload the vehicle information of the vehicle to be diagnosed to the server in order to obtain a list of vehicle electronic control units corresponding to the vehicle information issued by the server. The list selection module is used to determine the list of target electronic control units selected by the target user from the list of vehicle electronic control units; The diagnostic data packet determination module is used to upload the target electronic control unit list to the server so that the server can determine the diagnostic data packet corresponding to the target electronic control unit list. The vehicle diagnostic module is used to obtain the diagnostic data packet sent by the server and use the diagnostic data packet to diagnose the vehicle to be diagnosed. The diagnostic data packet determination module specifically includes: The data packet packaging unit is used to upload the target electronic control unit list to the server, so that the server can filter out the target diagnostic files corresponding to each target electronic control unit in the target electronic control unit list from the vehicle diagnostic data packet, update the system configuration file using the target electronic control unit list, and package the target diagnostic files, the updated system configuration file, and other target files in the vehicle diagnostic data packet to obtain a diagnostic data packet; the target diagnostic files include target ODX files and target OTX files corresponding to each target electronic control unit, and the target files include multilingual files and vehicle menu configuration files.

7. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the vehicle diagnostic method as described in any one of claims 1 to 3.

8. A computer-readable storage medium, characterized in that, Used to store a computer program; wherein, when executed by a processor, the computer program implements the steps of the vehicle diagnostic method as described in any one of claims 1 to 3.

Images