Vehicle diagnosis method, device, terminal equipment and storage medium

Abstract

The application discloses a vehicle diagnosis method and device, terminal equipment and storage medium, and obtains a current diagnosis node; a standardized vehicle communication interface state is inquired based on the current diagnosis node, and it is judged whether the standardized vehicle communication interface state is a target communication interface state, wherein the target communication interface state corresponds to the current diagnosis node; if the standardized vehicle communication interface state is not the target communication interface state, a diagnosis operation corresponding to the current diagnosis node is performed, so that the standardized vehicle communication interface state is switched to the target communication interface state, and the target communication interface state can be quickly loaded and initialized in the case that the diagnosis equipment is powered on again after unexpected power-off, without the need of user reoperation, thereby improving diagnosis efficiency.

Description

Technical Field

[0001] This invention relates to the field of automotive diagnostic technology, and more particularly to a vehicle diagnostic method, apparatus, terminal equipment, and storage medium. Background Technology

[0002] During automotive diagnostics, it is typically necessary to connect the computer and the vehicle's OBD (On-Board Diagnostics) interface via a VCI diagnostic box to communicate. After connecting the VCI and the vehicle, the diagnostic software obtains the vehicle's communication parameters by parsing the vehicle's ODX (Open Diagnostic Data Exchange) file. The user selects the system to enter the menu, the diagnostic tool obtains the system communication ID and communication pins, then calls the D-PDU interface to initialize communication, establish a link, and finally perform communication diagnostics with the vehicle via the VCI.

[0003] However, in practical applications, during the diagnostic process, the VCI may be powered off due to human error or accident. After power is restored, the diagnostic instrument cannot return to the state before the power failure, resulting in the inability to make a diagnosis. The diagnostic software must be reopened and run again, which reduces the diagnostic efficiency.

[0004] Therefore, it is necessary to propose a solution to improve diagnostic efficiency.

[0005] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0006] The main objective of this invention is to provide a vehicle diagnostic method, apparatus, terminal device, and storage medium, with the aim of improving diagnostic efficiency.

[0007] To achieve the above objectives, the present invention provides a vehicle diagnostic method, the vehicle diagnostic method comprising:

[0008] Get the current diagnostic node;

[0009] Based on the current diagnostic node, query the standardized vehicle communication interface status and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then perform the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status.

[0010] Optionally, the diagnostic node includes a first diagnostic node and / or a second diagnostic node, and the step of querying the standardized vehicle communication interface status based on the current diagnostic node and determining whether the standardized vehicle communication interface status is the target communication interface status includes:

[0011] Based on the status query of the standardized vehicle communication interface at the first diagnostic node, determine whether the standardized vehicle communication interface is in a loaded but uninitialized state; and / or,

[0012] Based on the query status of the standardized vehicle communication interface using the second diagnostic node, determine whether the standardized vehicle communication interface is in the loading and initialization state.

[0013] Optionally, the step of performing a diagnostic operation corresponding to the current diagnostic node to switch the state of the standardized vehicle communication interface to the state of the target communication interface includes:

[0014] Load the standardized vehicle communication system until the standardized vehicle communication interface is in a loaded but uninitialized state; and / or,

[0015] Load the standardized vehicle communication system, obtain the target system and its corresponding communication parameters, and perform communication parameter initialization until the standardized vehicle communication interface is in the loaded and initialized state.

[0016] Optionally, the step of loading a standardized vehicle communication system includes:

[0017] Load the standardized vehicle communication library;

[0018] A jump command is sent through the standardized vehicle communication library to jump to the standardized vehicle communication system.

[0019] Optionally, before the steps of obtaining the target system and its corresponding communication parameters and performing communication parameter initialization, the method further includes:

[0020] Get vehicle model information;

[0021] Download vehicle diagnostic data based on the vehicle model information and display the vehicle model topology interface corresponding to the vehicle model information to determine the target system;

[0022] The vehicle diagnostic data is used to provide the communication parameters corresponding to the target system.

[0023] Optionally, the step of obtaining the target system and its corresponding communication parameters, and performing communication parameter initialization includes:

[0024] In response to the user's operation command for the vehicle topology interface, the target system is determined;

[0025] The communication parameters corresponding to the target system are determined based on the vehicle diagnostic data.

[0026] A communication channel and communication link are created based on the aforementioned communication parameters.

[0027] Optionally, after the step of querying the standardized vehicle communication interface status based on the current diagnostic node and determining whether the standardized vehicle communication interface status is the target communication interface status, the method further includes:

[0028] The standardized vehicle communication interface status is checked at preset intervals using the communication status query interface to determine whether it is the target communication interface status.

[0029] Furthermore, to achieve the above objectives, the present invention also provides a vehicle diagnostic device, the vehicle diagnostic device comprising:

[0030] The acquisition module is used to acquire the current diagnostic node;

[0031] The query module is used to query the status of the standardized vehicle communication interface based on the current diagnostic node, and determine whether the status of the standardized vehicle communication interface is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the status of the standardized vehicle communication interface is not the target communication interface status, then the diagnostic operation corresponding to the current diagnostic node is executed to switch the status of the standardized vehicle communication interface to the target communication interface status.

[0032] In addition, to achieve the above objectives, the present invention also provides a terminal device, the terminal device including a memory, a processor, and a vehicle diagnostic program stored in the memory and executable on the processor, wherein the vehicle diagnostic program, when executed by the processor, implements the steps of the vehicle diagnostic method as described above.

[0033] In addition, to achieve the above objectives, the present invention also provides a computer-readable storage medium storing a vehicle diagnostic program, which, when executed by a processor, implements the steps of the vehicle diagnostic method as described above.

[0034] This invention provides a vehicle diagnostic method, apparatus, terminal device, and storage medium. The method involves acquiring the current diagnostic node; querying the standardized vehicle communication interface status based on the current diagnostic node; determining whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then performing a diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status. This allows for rapid loading and initialization after an unexpected power outage and subsequent power restoration of the diagnostic device, eliminating the need for user intervention and thus improving diagnostic efficiency. Attached Figure Description

[0035] Figure 1 This is a schematic diagram of the functional modules of the terminal equipment to which the vehicle diagnostic device of the present invention belongs;

[0036] Figure 2 This is a flowchart illustrating an exemplary embodiment of the vehicle diagnostic method of the present invention;

[0037] Figure 3 This is a schematic diagram of the internal jump of the VCI system in an embodiment of the present invention;

[0038] Figure 4 for Figure 2 A schematic diagram of the specific process of step S30 in the embodiment;

[0039] Figure 5 This is a schematic diagram of the vehicle topology interface in an embodiment of the present invention;

[0040] Figure 6 This is a schematic diagram of a specific system interface in an embodiment of the present invention;

[0041] Figure 7 This is a schematic diagram of the overall architecture in an embodiment of the present invention.

[0042] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0043] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0044] The main solution of this invention is as follows: First, obtain the current diagnostic node; second, query the standardized vehicle communication interface status based on the current diagnostic node, and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then perform the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status. This allows for rapid loading and initialization after an unexpected power outage and subsequent power restoration of the diagnostic equipment, without requiring user intervention, thereby improving diagnostic efficiency.

[0045] Technical terms involved in the embodiments of this invention:

[0046] ODX, Open Diagnostic Data Exchange, defines a new industry-standard diagnostic format that enables diagnostic data stream information to be used by diagnostic tool application manufacturers.

[0047] OBD, On-Board Diagnostics, is an in-vehicle automated diagnostic system.

[0048] In automotive diagnostics, a VCI diagnostic box is often used to connect the computer and the vehicle's OBD port for communication. After connecting the VCI and the vehicle, the diagnostic software parses the vehicle's ODX file to obtain various communication parameters for the entire vehicle. The user selects the system to enter the menu, the diagnostic tool obtains the system communication ID and communication pins, then calls the D-PDU interface to initialize communication, establish a link, and finally communicate with the vehicle for diagnostics. However, in practical applications, the VCI is often powered off due to human error or accidents during the diagnostic process. After power is restored, the diagnostic tool cannot return to the state before the power outage, making diagnostics impossible. The diagnostic software must be reopened and run again, resulting in a waste of time and resources.

[0049] This invention provides a solution that uses a VCI lower-level machine to provide an interface for querying the D-PDU status, returning three D-PDU statuses: 1. Not loaded; 2. Loaded but not initialized; 3. Loaded and initialized. The diagnostic tool client identifies the vehicle model information, downloads and parses the PDX diagnostic file, enters the vehicle model topology diagram, and starts thread 1 to periodically query the D-PDU status by calling the status query interface. At this time, the normal D-PDU status should be "Loaded but not initialized". If the returned status is "Not loaded", it indicates that the VCI connection has failed, possibly due to an unexpected power outage. In this case, the diagnostic tool client prohibits user operation, reloads the D-PDU communication library dll, and the dll sends instructions to jump to the D-PDU system. The operation prohibition is lifted only when thread 1 returns the status interface status as "Loaded but not initialized". When a user selects a specific ECU system, the diagnostic tool client creates a communication channel and link, initializes the diagnostic address, communication pins, and other communication parameters based on the selected system. Simultaneously, thread 1 is closed, and thread 2 is started to periodically query the D-PDU status via the status query interface. At this point, the D-PDU's normal status should be "Loaded and Initialized." If the returned status is not this, the VCI may have unexpectedly disconnected and restarted. In this case, the VCI should be powered on again. The diagnostic tool client should then disable user operation, reload the D-PDU communication library DLL, and the DLL sends instructions to jump to the D-PDU system. Based on the selected system, it creates a communication channel and link, initializes the diagnostic address, communication pins, and other communication parameters, until thread 2 returns a status of "Loaded but not initialized." Only then is the client's operation restriction lifted, and the VCI has been successfully reset and reconnected, allowing normal diagnostics to continue. When exiting the specific ECU system diagnostics, thread 2 is closed. This solution allows users to quickly initialize the VCI according to the diagnostic scenario after an unexpected power outage and restart, significantly improving diagnostic efficiency, reducing after-sales costs, and enhancing the user experience.

[0050] Specifically, refer to Figure 1 , Figure 1 This is a schematic diagram of the functional modules of the terminal device to which the vehicle diagnostic device of the present invention belongs. The vehicle diagnostic device can be a device capable of performing vehicle diagnostics, independent of the terminal device, and can be implemented on the terminal device in hardware or software form. The terminal device can be a smart mobile terminal with data processing capabilities, such as a mobile phone or tablet computer, or it can be a fixed terminal device or server with data processing capabilities.

[0051] In this embodiment, the terminal device to which the vehicle diagnostic device belongs includes at least an output module 110, a processor 120, a memory 130, and a communication module 140.

[0052] The memory 130 stores the operating system and vehicle diagnostic program. The vehicle diagnostic device can store information such as the standardized vehicle communication interface status, the acquired target system, and the corresponding communication parameters in the memory 130. The output module 110 can be a display screen, etc. The communication module 140 can include a WIFI module, a mobile communication module, and a Bluetooth module, etc., and communicates with external devices or servers through the communication module 140.

[0053] When the vehicle diagnostic program in memory 130 is executed by the processor, it performs the following steps:

[0054] Get the current diagnostic node;

[0055] Based on the current diagnostic node, query the standardized vehicle communication interface status and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then perform the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status.

[0056] Furthermore, when the vehicle diagnostic program in memory 130 is executed by the processor, it also performs the following steps:

[0057] Based on the status query of the standardized vehicle communication interface at the first diagnostic node, determine whether the standardized vehicle communication interface is in a loaded but uninitialized state; and / or,

[0058] Based on the query status of the standardized vehicle communication interface using the second diagnostic node, determine whether the standardized vehicle communication interface is in the loading and initialization state.

[0059] Furthermore, when the vehicle diagnostic program in memory 130 is executed by the processor, it also performs the following steps:

[0060] Load the standardized vehicle communication system until the standardized vehicle communication interface is in a loaded but uninitialized state; and / or,

[0061] Load the standardized vehicle communication system, obtain the target system and its corresponding communication parameters, and perform communication parameter initialization until the standardized vehicle communication interface is in the loaded and initialized state.

[0062] Furthermore, when the vehicle diagnostic program in memory 130 is executed by the processor, it also performs the following steps:

[0063] Load the standardized vehicle communication library;

[0064] A jump command is sent through the standardized vehicle communication library to jump to the standardized vehicle communication system.

[0065] Furthermore, when the vehicle diagnostic program in memory 130 is executed by the processor, it also performs the following steps:

[0066] Get vehicle model information;

[0067] Download vehicle diagnostic data based on the vehicle model information and display the vehicle model topology interface corresponding to the vehicle model information to determine the target system;

[0068] The vehicle diagnostic data is used to provide the communication parameters corresponding to the target system.

[0069] Furthermore, when the vehicle diagnostic program in memory 130 is executed by the processor, it also performs the following steps:

[0070] In response to the user's operation command for the vehicle topology interface, the target system is determined;

[0071] The communication parameters corresponding to the target system are determined based on the vehicle diagnostic data.

[0072] A communication channel and communication link are created based on the aforementioned communication parameters.

[0073] Furthermore, when the vehicle diagnostic program in memory 130 is executed by the processor, it also performs the following steps:

[0074] The standardized vehicle communication interface status is checked at preset intervals using the communication status query interface to determine whether it is the target communication interface status.

[0075] This embodiment, through the above scheme, specifically obtains the current diagnostic node; based on the current diagnostic node, queries the standardized vehicle communication interface status to determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then performs the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status. This allows for rapid loading and initialization after an unexpected power outage and subsequent power restoration of the diagnostic equipment, without requiring user intervention, thereby improving diagnostic efficiency.

[0076] Based on, but not limited to, the terminal device architecture described above, embodiments of the method of the present invention are proposed.

[0077] The subject executing the method in this embodiment can be a vehicle diagnostic device or terminal equipment, etc. This embodiment takes a vehicle diagnostic device as an example.

[0078] Reference Figure 2 , Figure 2This is a schematic flowchart illustrating an exemplary embodiment of the vehicle diagnostic method of the present invention. The vehicle diagnostic method includes:

[0079] Step S10: Obtain the current diagnostic node;

[0080] Specifically, refer to Figure 3 , Figure 3 This is a schematic diagram of the internal jump of the VCI system in an embodiment of the present invention, as shown below. Figure 3 As shown, when the user connects the diagnostic device VCI to the vehicle, the diagnostic software loads the communication library dll and sends commands through the communication library to make the VCI jump from boot to the D-PDU system, which is the standardized vehicle communication system.

[0081] Optionally, the vehicle diagnostic method in this embodiment of the invention further includes:

[0082] Get vehicle model information;

[0083] Download vehicle diagnostic data based on the vehicle model information and display the vehicle model topology interface corresponding to the vehicle model information to determine the target system;

[0084] The vehicle diagnostic data is used to provide the communication parameters corresponding to the target system.

[0085] Specifically, the diagnostic software obtains vehicle model information, then downloads the corresponding vehicle diagnostic data based on the vehicle model information, and enters the vehicle model topology interface.

[0086] Optionally, the diagnostic nodes include a first diagnostic node and / or a second diagnostic node.

[0087] Specifically, the first diagnostic node includes the node that enters the vehicle topology map, and the second diagnostic node includes the node where the user has selected the target ECU system.

[0088] Specifically, the user can select the target system in the vehicle topology interface. During this process, the diagnostic software starts thread 1 (i.e., the first thread), calls the D-PDU status query interface (i.e., the communication status query interface), and periodically queries the D-PDU status (standardized vehicle communication interface status). The interval period can be selected according to actual needs, and this embodiment does not make specific limitations on it.

[0089] Step S20: Based on the current diagnostic node, query the standardized vehicle communication interface status and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, perform the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status.

[0090] Optionally, the step of determining whether the standardized vehicle communication interface status is the target communication interface status based on the current diagnostic node query includes:

[0091] Based on the status query of the standardized vehicle communication interface at the first diagnostic node, determine whether the standardized vehicle communication interface is in a loaded but uninitialized state; and / or,

[0092] Based on the second diagnostic node query, the status of the standardized vehicle communication interface is determined to be in the loading and initialization state.

[0093] Specifically, the target communication interface status corresponds to the current diagnostic node. In this embodiment of the invention, the target communication interface status corresponding to the first diagnostic node is loaded but not initialized, and the target communication interface status corresponding to the second diagnostic node is loaded and initialized.

[0094] When the standardized vehicle communication interface is found to be in an unloaded state based on the first diagnostic node (i.e., the standardized vehicle communication interface is not in a loaded but uninitialized state), the diagnostic operation corresponding to the first diagnostic node is executed, i.e., the standardized vehicle communication system is loaded, until the standardized vehicle communication interface is in a loaded but uninitialized state.

[0095] When the standardized vehicle communication interface is not in the loaded and initialized state as determined by the second diagnostic node, the diagnostic operation corresponding to the second diagnostic node is executed, namely, loading the standardized vehicle communication system, obtaining the target system and its corresponding communication parameters, and performing communication parameter initialization, until the standardized vehicle communication interface is in the loaded and initialized state.

[0096] Optionally, the step of performing a diagnostic operation corresponding to the current diagnostic node to switch the state of the standardized vehicle communication interface to the state of the target communication interface includes:

[0097] Load the standardized vehicle communication system until the standardized vehicle communication interface is in a loaded but uninitialized state; and / or,

[0098] Load the standardized vehicle communication system, obtain the target system and its corresponding communication parameters, and perform communication parameter initialization until the standardized vehicle communication interface is in the loaded and initialized state.

[0099] Specifically, if the D-PDU status query interface finds that the D-PDU status is not loaded, that is, the standardized vehicle communication interface status is not loaded but not initialized, then the user is prohibited from operating the diagnostic software, checking the VCI, reloading the communication library, and sending a command to jump to the D-PDU system.

[0100] Optionally, the step of loading a standardized vehicle communication system includes:

[0101] Load the standardized vehicle communication library;

[0102] A jump command is sent through the standardized vehicle communication library to jump to the standardized vehicle communication system.

[0103] Optionally, if the standardized vehicle communication interface is in an unloaded state or not in a loaded and initialized state, the vehicle diagnostic method further includes:

[0104] Startup software disablement to stop receiving operation commands from the user.

[0105] Optionally, if the standardized vehicle communication interface is in a loaded but uninitialized state or a loaded and initialized state, the vehicle diagnostic method further includes:

[0106] Remove the software restriction to receive the user's operation commands.

[0107] Optionally, if the D-PDU status query interface shows that the D-PDU is loaded but not initialized, the software restriction can be lifted, and the diagnostic software can be restored to normal use. At this time, the D-DPU is in normal state. The user can select the target system by clicking the specific system icon in the vehicle topology interface. Based on the target system selected by the user, the system communication address, communication pins and other communication parameters are obtained from the ODX file, the communication channel and communication link are created, the communication parameters are initialized, thread 1 is closed, and thread 2 is started.

[0108] Optionally, after the step of querying the standardized vehicle communication interface status based on the current diagnostic node and determining whether the standardized vehicle communication interface status is the target communication interface status, the method further includes:

[0109] The communication status query interface is used to query whether the status of the standardized vehicle communication interface is the target communication interface status at preset intervals.

[0110] Furthermore, by calling the D-PDU status query interface through thread 2, the status of the standardized vehicle communication interface is periodically queried. The preset interval can be selected according to actual needs, and this embodiment does not impose specific limitations on it.

[0111] Optionally, if thread 2 returns a status that is not "loaded and initialized", then user operation of the software is prohibited, the standardized vehicle communication system is reloaded, and the corresponding communication parameters are obtained in conjunction with the target system previously selected by the user. Communication parameter initialization is performed until the returned status is "loaded and initialized", then the software prohibition can be ended and normal use can be restored.

[0112] In addition, thread 2 is closed when the user returns to the vehicle topology interface or exits the software.

[0113] In this embodiment, the current diagnostic node is obtained; based on the current diagnostic node, the status of the standardized vehicle communication interface is queried to determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, a diagnostic operation corresponding to the current diagnostic node is executed to switch the standardized vehicle communication interface status to the target communication interface status. This allows for rapid loading and initialization after an unexpected power outage and subsequent power restoration of the diagnostic equipment, without requiring user intervention, thereby improving diagnostic efficiency and saving diagnostic resources.

[0114] Reference Figure 4 , Figure 4 for Figure 2 This embodiment illustrates the specific process of acquiring the target system and its corresponding communication parameters, and performing communication parameter initialization. This embodiment is based on the above... Figure 2 In the illustrated embodiment, the steps of obtaining the target system and its corresponding communication parameters, and performing communication parameter initialization include:

[0115] Step S301: In response to the user's operation command for the vehicle model topology interface, determine the target system;

[0116] Specifically, refer to Figure 5 , Figure 5 This is a schematic diagram of the vehicle topology interface in an embodiment of the present invention, such as... Figure 3 As shown, after entering the vehicle topology interface, users can select a specific ECU system. After selecting the target system according to the user's operation command, they can enter the specific system interface.

[0117] Step S302: Determine the communication parameters corresponding to the target system based on the vehicle diagnostic data;

[0118] Furthermore, after selecting the target system through the vehicle topology interface, the user can select the corresponding communication parameters from the downloaded vehicle diagnostic data based on the name of the target system, and then use them to initialize the communication parameters.

[0119] Step S303: Create a communication channel and communication link based on the communication parameters.

[0120] Furthermore, after selecting or determining the communication parameters of the target system, communication parameter initialization can be performed in the specific system interface, as shown below. Figure 6 , Figure 6 This is a schematic diagram of a specific system interface in an embodiment of the present invention, such as... Figure 6 As shown, after entering the specific system interface, the D-DPU begins to create communication channels and communication links. Based on the communication address and pins obtained from the system name, it sets the communication address and pins, initializes the communication parameters, and then uses them for specific diagnostics.

[0121] This embodiment, through the above scheme, specifically determines the target system in response to the user's operation command on the vehicle topology interface; determines the communication parameters corresponding to the target system based on the vehicle diagnostic data; creates a communication channel and communication link based on the communication parameters; obtains the target system and its corresponding communication parameters through the vehicle topology interface; performs communication parameter initialization; and performs diagnostics on the specific system.

[0122] Furthermore, embodiments of the present invention also propose a vehicle diagnostic device, the vehicle diagnostic device comprising:

[0123] The acquisition module is used to acquire the current diagnostic node;

[0124] The query module is used to query the status of the standardized vehicle communication interface based on the current diagnostic node, and determine whether the status of the standardized vehicle communication interface is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the status of the standardized vehicle communication interface is not the target communication interface status, then the diagnostic operation corresponding to the current diagnostic node is executed to switch the status of the standardized vehicle communication interface to the target communication interface status.

[0125] The diagnostic node includes a first diagnostic node and / or a second diagnostic node, and the query module includes a first query module and / or a second query module. The first query module is used to query the status of the standardized vehicle communication interface based on the first diagnostic node and determine whether the status of the standardized vehicle communication interface is loaded but not initialized. The second query module is used to query the status of the standardized vehicle communication interface based on the second diagnostic node and determine whether the status of the standardized vehicle communication interface is loaded and initialized.

[0126] The query module further includes a first execution unit and / or a second execution unit. The first execution unit is used to load the standardized vehicle communication system until the standardized vehicle communication interface is in a loaded but uninitialized state. The second execution unit is used to load the standardized vehicle communication system, obtain the target system and its corresponding communication parameters, and perform communication parameter initialization until the standardized vehicle communication interface is in a loaded and initialized state.

[0127] The first execution unit and / or the second execution unit includes a loading unit and a jump unit. The loading unit is used to load a standardized vehicle communication library; the jump unit is used to send a jump instruction through the standardized vehicle communication library to jump to the standardized vehicle communication system.

[0128] The second execution unit further includes an acquisition unit and a download unit. The acquisition unit is used to acquire vehicle model information. The download unit is used to download vehicle diagnostic data based on the vehicle model information and display the vehicle model topology interface corresponding to the vehicle model information to determine the target system. The vehicle diagnostic data is used to provide communication parameters corresponding to the target system.

[0129] The second execution unit further includes a response unit, a determination unit, and a creation unit. The response unit is used to determine the target system in response to the user's operation command for the vehicle topology interface. The determination unit is used to determine the communication parameters corresponding to the target system based on the vehicle diagnostic data. The creation unit is used to create a communication channel and a communication link based on the communication parameters.

[0130] The query module also includes a periodic query unit, which is used to query whether the status of the standardized vehicle communication interface is the target communication interface status at preset intervals through the communication status query interface.

[0131] Reference Figure 7 , Figure 7 This is a schematic diagram of the overall architecture in an embodiment of the present invention, such as... Figure 7As shown, the diagnostic tool client identifies the vehicle model information, downloads and parses the PDX diagnostic file, enters the vehicle model topology diagram, and starts thread 1 to periodically query the D-PDU status by calling the query status interface. At this time, the normal D-PDU status should be "loaded but not initialized". If the return status is "not loaded", it means that the VCI connection has failed, possibly due to an unexpected power outage. At this time, the diagnostic tool client prohibits user operation, reloads the D-PDU communication library dll, and the dll sends a command to jump to the D-PDU system. The operation prohibition is lifted only when the status interface of thread 1 returns "loaded but not initialized". When the user selects a specific ECU system, the diagnostic tool client will create a communication channel and link, initialize the diagnostic address, communication pins, and other communication parameters according to the selected system. Simultaneously, thread 1 will be closed, and thread 2 will be started to periodically query the D-PDU status via the status query interface. At this point, the normal D-PDU status should be "Loaded and Initialized". If the returned status is not this, the VCI may have unexpectedly disconnected and restarted. In this case, the VCI should be checked and powered on again. The diagnostic tool client will then prohibit user operation and reload the D-PDU communication library dll. The dll will send instructions to jump to the D-PDU system, creating a communication channel and link, and initializing the diagnostic address, communication pins, and other communication parameters according to the selected system. This process continues until thread 2 returns a status of "Loaded but not initialized" before the client's operation restriction is lifted. At this point, the VCI has been successfully reset and reconnected, and normal diagnostics can continue. When exiting the specific ECU system diagnostics, thread 2 will be closed.

[0132] This embodiment, through the above solution, enables users to quickly initialize the VCI according to the diagnostic scenario after an unexpected power outage and restart, greatly improving diagnostic efficiency, reducing after-sales costs, and enhancing user experience.

[0133] The principle and implementation process of vehicle diagnosis in this embodiment are explained in the above embodiments and will not be repeated here.

[0134] Furthermore, this embodiment of the invention also proposes a terminal device, which includes a memory, a processor, and a vehicle diagnostic program stored in the memory and executable on the processor. When the vehicle diagnostic program is executed by the processor, it implements the steps of the vehicle diagnostic method described above.

[0135] Since the vehicle diagnostic program employs all the technical solutions of all the aforementioned embodiments when executed by the processor, it has at least all the beneficial effects brought about by all the technical solutions of all the aforementioned embodiments, which will not be elaborated here.

[0136] Furthermore, embodiments of the present invention also propose a computer-readable storage medium storing a vehicle diagnostic program, which, when executed by a processor, implements the steps of the vehicle diagnostic method described above.

[0137] Since the vehicle diagnostic program employs all the technical solutions of all the aforementioned embodiments when executed by the processor, it has at least all the beneficial effects brought about by all the technical solutions of all the aforementioned embodiments, which will not be elaborated here.

[0138] Compared to existing technologies, the vehicle diagnostic method, apparatus, terminal device, and storage medium proposed in this invention obtain the current diagnostic node; query the standardized vehicle communication interface status based on the current diagnostic node, and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then perform the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status. This allows for rapid loading and initialization after an unexpected power outage and subsequent power restoration of the diagnostic device, without requiring user intervention, thereby improving diagnostic efficiency and saving diagnostic resources.

[0139] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system 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 system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0140] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0141] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.

[0142] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A vehicle diagnostic method, characterized in that, The vehicle diagnostic method includes the following steps: Get the current diagnostic node; Based on the current diagnostic node, query the standardized vehicle communication interface status and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then perform the diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface status to the target communication interface status. The standardized vehicle communication interface status is checked at preset intervals using the communication status query interface to determine whether it is the target communication interface status. The diagnostic node includes a first diagnostic node and / or a second diagnostic node. The step of querying the standardized vehicle communication interface status based on the current diagnostic node and determining whether the standardized vehicle communication interface status is the target communication interface status includes: Based on the status query of the standardized vehicle communication interface at the first diagnostic node, determine whether the standardized vehicle communication interface is in a loaded but uninitialized state; and / or, Based on the query of the standardized vehicle communication interface status at the second diagnostic node, determine whether the standardized vehicle communication interface status is in the loading and initialization state. If the standardized vehicle communication interface is not in a loaded but uninitialized state, then user operation of the diagnostic software is prohibited. The step of performing a diagnostic operation corresponding to the current diagnostic node to switch the standardized vehicle communication interface state to the target communication interface state includes: Load the standardized vehicle communication system until the standardized vehicle communication interface is in a loaded but uninitialized state; and / or, Load the standardized vehicle communication system, obtain the target system and corresponding communication parameters, and perform communication parameter initialization until the standardized vehicle communication interface is in the loaded and initialized state. The standardized vehicle communication interface states include unloaded state, loaded but uninitialized state, and loaded and initialized state.

2. The vehicle diagnostic method as described in claim 1, characterized in that, The steps for loading the standardized vehicle communication system include: Load the standardized vehicle communication library; A jump command is sent through the standardized vehicle communication library to jump to the standardized vehicle communication system.

3. The vehicle diagnostic method as described in claim 1, characterized in that, Before the steps of obtaining the target system and its corresponding communication parameters and performing communication parameter initialization, the following steps are also included: Get vehicle model information; Download vehicle diagnostic data based on the vehicle model information and display the vehicle model topology interface corresponding to the vehicle model information to determine the target system; The vehicle diagnostic data is used to provide the communication parameters corresponding to the target system.

4. The vehicle diagnostic method as described in claim 3, characterized in that, The steps of obtaining the target system and its corresponding communication parameters, and performing communication parameter initialization include: In response to the user's operation command for the vehicle topology interface, the target system is determined; The communication parameters corresponding to the target system are determined based on the vehicle diagnostic data. A communication channel and communication link are created based on the aforementioned communication parameters.

5. A vehicle diagnostic device, characterized in that, The vehicle diagnostic device includes: The acquisition module is used to acquire the current diagnostic node; The query module is used to query the standardized vehicle communication interface status based on the current diagnostic node, and determine whether the standardized vehicle communication interface status is the target communication interface status, wherein the target communication interface status corresponds to the current diagnostic node; if the standardized vehicle communication interface status is not the target communication interface status, then a diagnostic operation corresponding to the current diagnostic node is executed to switch the standardized vehicle communication interface status to the target communication interface status; the diagnostic node includes a first diagnostic node and / or a second diagnostic node; The query module is also used to query the status of the standardized vehicle communication interface based on the first diagnostic node, and determine whether the status of the standardized vehicle communication interface is loaded but not initialized; and / or, to query the status of the standardized vehicle communication interface based on the second diagnostic node, and determine whether the status of the standardized vehicle communication interface is loaded and initialized. The query module is also used to query, at preset intervals, whether the status of the standardized vehicle communication interface is the target communication interface status through the communication status query interface; the status of the standardized vehicle communication interface includes unloaded status, loaded but uninitialized status, and loaded and initialized status. The query module is also used to load the standardized vehicle communication system until the standardized vehicle communication interface is in the loaded but uninitialized state; and / or, load the standardized vehicle communication system, obtain the target system and the corresponding communication parameters, and perform communication parameter initialization until the standardized vehicle communication interface is in the loaded and initialized state. The operation-disable module is used to prevent the user from operating the diagnostic software if the standardized vehicle communication interface is not in a loaded but uninitialized state.

6. A terminal device, characterized in that, The terminal device includes a memory, a processor, and a vehicle diagnostic program stored in the memory and executable on the processor. When the vehicle diagnostic program is executed by the processor, it implements the steps of the vehicle diagnostic method as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a vehicle diagnostic program, which, when executed by a processor, implements the steps of the vehicle diagnostic method as described in any one of claims 1-4.

Images