Vehicle diagnosis method, electronic device and computer program product

Abstract

The invention provides a vehicle diagnosis method, electronic equipment and a computer program product, and is suitable for the technical field of Internet of Vehicles, and the method is applied to diagnosis equipment, and comprises the steps: detecting the actual voltage of a target vehicle before the target vehicle is diagnosed; in response to the fact that the actual voltage is smaller than the target voltage, the target vehicle is charged, and the target voltage is the voltage needed by normal operation of the target vehicle; in the charging process of the target vehicle, if it is detected that the actual voltage is larger than or equal to the target voltage, charging of the target vehicle is stopped; and starting to diagnose the target vehicle. According to the invention, the diagnosis efficiency of vehicle diagnosis can be improved.

Description

Technical Field

[0001] The present application belongs to the field of vehicle networking technology, and in particular to vehicle diagnostic methods, electronic equipment and computer program products. Background Art

[0002] During the long-term use of vehicles, various problems and failures will inevitably occur. In order to ensure the safe, reliable and efficient operation of vehicles, vehicle diagnostic technology has emerged. Usually, diagnostic equipment is needed to diagnose the vehicle. The diagnostic equipment communicates with the vehicle's Electronic Control Unit (ECU) to read various vehicle data to complete the diagnosis of the vehicle.

[0003] However, when using diagnostic equipment to diagnose a vehicle, sometimes the diagnostic equipment cannot communicate normally with the vehicle ECU, resulting in the diagnostic equipment being unable to obtain valid vehicle data, thereby reducing the efficiency of vehicle diagnosis. Summary of the invention

[0004] In view of this, embodiments of the present application provide a vehicle diagnostic method, an electronic device, and a computer program product to solve the problem of low vehicle diagnostic efficiency in related technologies.

[0005] A first aspect of an embodiment of the present application provides a vehicle diagnosis method, the method comprising:

[0006] Before diagnosing the target vehicle, detecting the actual voltage of the target vehicle;

[0007] In response to the actual voltage being less than a target voltage, charging the target vehicle, the target voltage being a voltage required for normal operation of the target vehicle;

[0008] During the charging process of the target vehicle, if it is detected that the actual voltage is greater than or equal to the target voltage, the charging of the target vehicle is stopped;

[0009] Start diagnosing the target vehicle.

[0010] In some embodiments, before detecting the actual voltage of the target vehicle, the method further includes: acquiring a target voltage of the target vehicle.

[0011] In some embodiments, obtaining a target voltage of a target vehicle includes: scanning an identification code on the target vehicle, and determining a model of the target vehicle according to the identification code; and determining a target voltage of the target vehicle according to the model of the target vehicle.

[0012] In some embodiments, detecting the actual voltage of the target vehicle includes: in response to the diagnostic device establishing a connection with an on-board diagnostic system on the target vehicle, detecting the actual voltage of the target vehicle.

[0013] In some embodiments, the method further includes: in response to receiving a first diagnostic instruction, stopping detecting an actual voltage of the target vehicle, the first diagnostic instruction being used to instruct stopping diagnosis of the target vehicle.

[0014] In some embodiments, detecting the actual voltage of the target vehicle includes:

[0015] Acquire the actual voltage of the target vehicle from a first pin of a target interface, where the target interface is an interface for connecting the diagnostic device to an on-board diagnostic system on the target vehicle;

[0016] Charging the target vehicle includes: charging the target vehicle through a first pin.

[0017] In some embodiments, starting to diagnose the target vehicle includes: diagnosing the target vehicle in response to receiving a second diagnostic instruction, where the second diagnostic instruction is used to instruct to diagnose the target vehicle.

[0018] In some embodiments, before charging the target vehicle in response to the actual voltage being less than the target voltage, the method further includes: diagnosing the target vehicle in response to the actual voltage of the target vehicle being greater than or equal to the target voltage and receiving a second diagnostic instruction.

[0019] Compared with the prior art, the embodiments of the present application have the following beneficial effects: before diagnosing the vehicle, the actual voltage of the vehicle is first detected by using the diagnostic equipment; when the vehicle needs to be diagnosed but the actual voltage of the vehicle is lower than the voltage required for normal operation of the vehicle, the vehicle is charged by using the diagnostic equipment. On the one hand, the actual voltage of the vehicle can reach the voltage required for normal operation of the vehicle more quickly; on the other hand, the vehicle can be diagnosed on the premise of ensuring that the actual voltage of the vehicle is greater than or equal to the voltage required for normal operation of the vehicle, which can avoid abnormal communication between the diagnostic equipment and the vehicle due to insufficient vehicle voltage. That is, it can ensure that the vehicle diagnostic equipment can diagnose the vehicle when the vehicle voltage is normal, thereby improving the diagnostic efficiency.

[0020] A second aspect of an embodiment of the present application provides an electronic device, which includes a memory and a processor. The memory stores a computer program that can be run on the processor. When the processor executes the computer program, the electronic device implements the steps of any vehicle diagnostic method in the first aspect above.

[0021] A third aspect of an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is run, any vehicle diagnostic method in the first aspect is executed.

[0022] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, comprising: a computer program stored therein, which, when executed by a processor, enables an electronic device to implement the steps of any vehicle diagnostic method in the first aspect described above.

[0023] It can be understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 is a schematic diagram of an OBD interface provided by an embodiment of the present application;

[0026] Figure 2 This is a system architecture diagram of a vehicle diagnostic method application provided by an embodiment of the present application;

[0027] Figure 3 It is a flow chart of a vehicle diagnostic method provided by an embodiment of the present application;

[0028] Figure 4 is a schematic diagram of the structure of a diagnostic device provided by an embodiment of the present application;

[0029] Figure 5 It is a schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

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

[0031] Here we first explain some concepts involved in this application:

[0032] On-Board Diagnostics (OBD) interface: The OBD interface in this application is an interface inside the vehicle for communicating with external devices. Figure 1 , is a schematic diagram of an OBD interface provided in an embodiment of the present application. Figure 1 As shown, the OBD interface usually includes 16 pins: pin 1 to pin 16, each pin has its own unique definition and function. Usually, pin 4 is the body ground pin, which can be considered as the negative pole of the vehicle power supply, responsible for the vehicle to provide a reference potential for the electrical system. Pin 5 is the signal ground pin, responsible for providing a reference potential for digital signals. Pin 16 is the normal power pin, which can be considered as the positive pole of the vehicle power supply. Pin 6 is the CAN-H line pin, that is, the high line of the controller area network (CAN), responsible for the positive signal transmission in the CAN bus communication. Pin 14 is the CAN-L line pin, that is, the low line of the controller area network, responsible for the negative signal transmission of the CAN bus communication. Pin 7 is the K-Line pin. Pin 15 is the L-Line pin. Pin 2 can be considered as the positive pole of the J1850 data bus. Pin 10 can be considered as the negative pole of the J1850 data bus. While other pins, such as Pin 1, Pin 3, Pin 8, Pin 9, Pin 11, Pin 12 and Pin 13 can be adjusted according to specific requirements, so the functions of these pins are not fixed.

[0033] Vehicle Identification Number (VIN): The VIN code in this application is usually a code used to uniquely identify a vehicle. VIN usually consists of 17 letters or numbers, which are arranged according to certain rules and represent different information. VIN can usually identify the vehicle's manufacturer, model, engine, chassis serial number and other vehicle-related information.

[0034] Diagnostic equipment is an indispensable tool in today's vehicle diagnostic technology. In actual applications, it is found that when the diagnostic equipment is needed to diagnose the vehicle, sometimes the diagnostic equipment cannot communicate normally with the vehicle ECU, resulting in the diagnostic equipment being unable to obtain valid vehicle data, which in turn causes the vehicle diagnosis to be unable to proceed. For example, the communication between the diagnostic equipment and the ECU may be suddenly interrupted, and the transmitted vehicle data will be lost, making the vehicle data obtained by the diagnostic equipment incomplete; or the diagnostic equipment may even be unable to establish a communication connection with the ECU, making it impossible for the diagnostic equipment to obtain any vehicle data.

[0035] During the research and development process, it was found that when the power supply voltage of the vehicle (which can be called the vehicle voltage) is lower than the voltage required for normal operation of the vehicle, the vehicle components such as the vehicle ECU and communication bus that require a stable voltage from the vehicle power supply will work abnormally. In this case, the diagnostic equipment cannot communicate stably with the ECU, and thus cannot obtain effective vehicle data to diagnose the vehicle.

[0036] In order to solve the problem that the vehicle voltage is insufficient to support normal operation when the vehicle needs to be diagnosed, an optional method is to first charge the vehicle through a charging pile, and then use diagnostic equipment to diagnose the vehicle after the vehicle voltage returns to normal. Although this can solve the problem of insufficient vehicle voltage when diagnosing the vehicle, it usually takes a lot of time to find a charging pile temporarily.

[0037] Another option is to charge the vehicle by ignition, that is, by starting the vehicle's engine, and then using the engine to drive the generator to charge the vehicle power supply, and then use the diagnostic equipment to diagnose the vehicle after the vehicle voltage returns to normal. Although this can also solve the problem of insufficient vehicle voltage during vehicle diagnosis, the charging speed of charging the vehicle by ignition is often very slow.

[0038] However, both of the above-mentioned methods require a long time to restore the vehicle voltage to a normal state. Once the vehicle needs to be diagnosed but the voltage is lower than the voltage required for normal operation of the vehicle, it will take a long time to diagnose the vehicle, thereby reducing the efficiency of vehicle diagnosis.

[0039] Based on the above actual situation, the present application provides a vehicle diagnostic method, which is applied to a diagnostic device, including: before diagnosing the target vehicle, detecting the actual voltage of the target vehicle; in response to the actual voltage being less than the target voltage, charging the target vehicle, the target voltage being the voltage required for the normal operation of the target vehicle; during the charging process of the target vehicle, if it is detected that the actual voltage is greater than or equal to the target voltage, stopping charging the target vehicle; and starting diagnosis of the target vehicle.

[0040] In the present application, before diagnosing the vehicle, the actual voltage of the vehicle is first detected by the diagnostic equipment. When the vehicle needs to be diagnosed but the actual voltage of the vehicle is lower than the voltage required for the normal operation of the vehicle, the diagnostic equipment is used to charge the vehicle. On the one hand, the actual voltage of the vehicle can reach the voltage required for the normal operation of the vehicle more quickly. On the other hand, the vehicle can be diagnosed on the premise of ensuring that the actual voltage of the vehicle is greater than or equal to the voltage required for the normal operation of the vehicle. Abnormal communication between the diagnostic equipment and the vehicle due to insufficient vehicle voltage can be avoided. That is, the vehicle diagnostic equipment can be guaranteed to diagnose the vehicle when the vehicle voltage is normal, thereby improving the diagnostic efficiency.

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

[0042] refer to Figure 2 , which is a system architecture diagram of a vehicle diagnostic method application provided in an embodiment of the present application.

[0043] like Figure 2 As shown, the system architecture may include: a diagnostic device 201 , a target vehicle 202 , and an on-board diagnostic system (OBD) 203 .

[0044] The diagnostic device 201 is connected to the on-board diagnostic system 203 by wire. After the diagnostic device 201 is connected to the on-board diagnostic system 203, the diagnostic device 201 can communicate with the vehicle ECU through the on-board diagnostic system 203, so that the diagnostic device can read the vehicle data and fault codes in the ECU.

[0045] The target vehicle 202 may be any vehicle, such as an unmanned vehicle, a car, a truck, etc. It should be noted that the target vehicle 202 may also be any other means of transportation, such as an airplane or a ship.

[0046] The diagnostic device 201 is a device that can be used to diagnose the target vehicle 202. The diagnostic device 201 can obtain the actual voltage of the target vehicle 202 through the on-board diagnostic system 203, can also charge the target vehicle 202 through the on-board diagnostic system 203, and can also diagnose the target vehicle 202 through the on-board diagnostic system 203.

[0047] In another application scenario, the system architecture diagram of the vehicle diagnostic method application may also include a server. The diagnostic device 201 is connected to the server via a network. The network may include various connection types, such as wired or wireless communication links or optical fiber cables, etc. The server may pre-store the corresponding relationship between the vehicle model and the target voltage. In this scenario, the diagnostic device 201 can obtain the target voltage corresponding to the target vehicle 202 from the server.

[0048] Understandably, Figure 2 This is only an example. In actual application, the system architecture of the vehicle diagnosis method application may include Figure 1 The embodiments of the present application are not limited to more or fewer components shown.

[0049] refer to Figure 3 , is a flow chart of a vehicle diagnostic method provided in an embodiment of the present application, such as Figure 3 The vehicle diagnostic method shown includes the following steps 301 to 304:

[0050] In this embodiment, the vehicle diagnostic method is executed by a diagnostic device.

[0051] Step 301 : Before diagnosing the target vehicle, the diagnostic device detects the actual voltage of the target vehicle.

[0052] In some embodiments, the diagnostic device may detect the actual voltage of the target vehicle through the following steps: the diagnostic device obtains the actual voltage of the target vehicle from the first pin of the target interface.

[0053] The target interface is an interface for connecting the diagnostic device to the on-board diagnostic system of the target vehicle. In practice, the target interface can be implemented as an OBD interface.

[0054] Since pin 16 of the OBD interface is a normal power pin and can be considered as the positive pole of the vehicle power supply, the first pin of the target interface can be pin 16 of the OBD interface. In other words, the diagnostic device can obtain the actual voltage of the target vehicle by detecting the voltage at pin 16 of the OBD interface.

[0055] In this embodiment, the actual voltage of the target vehicle can be obtained by detecting the voltage at the first pin of the target interface, which is very convenient.

[0056] In some optional implementations of this embodiment, the above-mentioned diagnostic device detecting the actual voltage of the target vehicle may include: the diagnostic device detects the actual voltage of the target vehicle in response to the diagnostic device successfully establishing a connection with the on-board diagnostic system of the target vehicle.

[0057] Here, when the diagnostic device is connected to the target interface through a connecting line, the diagnostic device can establish a connection with the on-board diagnostic system on the target vehicle.

[0058] In a possible embodiment, the diagnostic device may stop detecting the actual voltage of the target vehicle in response to receiving the first diagnostic instruction, wherein the first diagnostic instruction is used to instruct to stop diagnosing the target vehicle.

[0059] In practice, the diagnostic device can also be connected to a terminal device, wherein the terminal device may include but is not limited to: a personal computer, a tablet computer, a smart phone, a laptop computer, a desktop computer, etc., and the terminal device and the diagnostic device can communicate with each other. If it is necessary to stop diagnosing the target vehicle, the user can send a first diagnostic instruction to the diagnostic device through the terminal device, and the diagnostic device can receive the first diagnostic instruction.

[0060] Considering that the diagnostic device usually includes an electronic screen that can perform human-computer interaction, the diagnostic device can also stop detecting the actual voltage of the target vehicle when detecting the operation that triggers the generation of the first diagnostic instruction. Exemplarily, the operation that triggers the generation of the first diagnostic instruction can be: clicking the operation of the control corresponding to the stop diagnosis; the operation that triggers the generation of the first diagnostic instruction can also be: long pressing the operation of the control corresponding to the stop diagnosis. The diagnostic device can detect the operation that triggers the generation of the first diagnostic instruction through a sensor, such as a pressure sensor.

[0061] In some embodiments, the diagnostic device may obtain a target voltage of the target vehicle before the diagnostic device detects an actual voltage of the target vehicle.

[0062] The target voltage is the voltage required for the normal operation of the target vehicle.

[0063] Here, the diagnostic device may first obtain the target voltage of the target vehicle, which helps the diagnostic device to more quickly determine the actual voltage state of the target vehicle based on the relationship between the target voltage and the actual voltage.

[0064] In this embodiment, the diagnostic device can obtain the target voltage of the target vehicle in a variety of ways.

[0065] In one implementation, the diagnostic device may obtain the target voltage of the target vehicle through the following steps:

[0066] In the first step, the diagnostic device scans the identification code on the target vehicle and determines the model of the target vehicle based on the identification code.

[0067] The identification code is usually information used to identify the vehicle. In practice, the identification code may include but is not limited to a VIN code, a vehicle model code (Vehicle Code, VC), etc. VC is usually a code used to indicate the model of the vehicle. After scanning the identification code, the diagnostic device can identify the model of the target vehicle.

[0068] In the second step, the diagnostic equipment determines the target voltage based on the model of the target vehicle.

[0069] Optionally, the diagnostic device determines the target voltage of the target vehicle according to the model of the target vehicle, which may include: the diagnostic device searches for the target voltage corresponding to the model of the target vehicle from a pre-stored correspondence between the model and the target voltage.

[0070] Here, the correspondence between the vehicle type and the target voltage can be pre-stored in the diagnostic device or in the server. When the correspondence between the vehicle type and the target voltage is pre-stored in the server, the diagnostic device can send the vehicle type of the target vehicle to the server, and the server can send the target voltage of the target vehicle to the diagnostic device after receiving the vehicle type of the target vehicle, so that the diagnostic device can determine the target voltage of the target vehicle.

[0071] In this implementation, the target voltage corresponding to the model of the target vehicle is obtained by finding the correspondence between the model and the target voltage. This is technically easy to implement and can quickly obtain the target voltage of the target vehicle, thereby helping to improve the efficiency of vehicle diagnosis.

[0072] In another implementation, the diagnostic device may also obtain the target voltage of the target vehicle by receiving an identification code of the target vehicle input by a user.

[0073] In this implementation, the user can directly input the target voltage of the target vehicle into the diagnostic device, which is more suitable for scenarios where multiple vehicles need to be diagnosed using the diagnostic device. In this way, in scenarios where multiple target vehicles need to be diagnosed, the diagnostic device can enter the step of diagnosing the target vehicle more quickly, thereby helping to improve the efficiency of vehicle diagnosis.

[0074] In step 302 , the diagnostic device charges the target vehicle in response to the actual voltage being less than the target voltage.

[0075] After obtaining the target voltage of the target vehicle, the diagnostic device may compare the target voltage of the target vehicle with the actual voltage. If the actual voltage is less than the target voltage, the diagnostic device may charge the target vehicle in response to the actual voltage being less than the target voltage. If the actual voltage is greater than or equal to the target voltage, the diagnostic device may not need to charge the target vehicle.

[0076] In some embodiments, the diagnostic device may charge the target vehicle through the following steps: the diagnostic device charges the target vehicle through the first pin of the target interface.

[0077] The target interface is an interface for connecting the diagnostic device to the on-board diagnostic system of the target vehicle. In practice, the target interface can be implemented as an OBD interface.

[0078] The first pin of the target interface may be pin 16 of the OBD interface. Since pin 16 of the OBD interface may be considered as the positive pole of the vehicle power supply, and pin 4 of the OBD interface is the vehicle body ground pin and may be considered as the negative pole of the vehicle power supply, the diagnostic device may charge the target vehicle through pins 4 and 16 of the OBD interface.

[0079] In this embodiment, the pin of the target interface used by the diagnostic device to charge the target vehicle is the same as the pin of the target interface used by the aforementioned diagnostic device to obtain the actual voltage of the target vehicle. Both are the first pin of the target interface, which is relatively simple and easy to implement in terms of technical solutions.

[0080] The target vehicle can be charged through the first pin of the target interface, and the aforementioned diagnostic device obtains the actual voltage of the target vehicle from the first pin of the target interface.

[0081] In a possible embodiment, before the above step 303 , the diagnostic device may further diagnose the target vehicle in response to the actual voltage of the target vehicle being greater than or equal to the target voltage.

[0082] Here, when the actual voltage of the target vehicle is greater than or equal to the target voltage, the diagnostic device can directly start diagnosing the target vehicle without charging the target vehicle. In this way, the diagnostic device can quickly enter the process of diagnosing the target vehicle.

[0083] Step 303 : During the process of charging the target vehicle, if the diagnostic device detects that the actual voltage is greater than or equal to the target voltage, the diagnostic device stops charging the target vehicle.

[0084] It is understandable that during the charging process of the target vehicle, the diagnostic device is also detecting the actual voltage of the target vehicle. When the diagnostic device detects that the actual voltage is greater than or equal to the target voltage, the charging of the target vehicle can be stopped.

[0085] Step 304 : The diagnostic device starts to diagnose the target vehicle.

[0086] Optionally, the diagnostic device can start diagnosing the target vehicle while stopping charging the target vehicle. In this way, the diagnostic device can quickly enter the process of diagnosing the target vehicle, thereby helping to improve the diagnostic efficiency of the target vehicle.

[0087] Optionally, the diagnostic device may also diagnose the target vehicle in response to receiving a second diagnostic instruction after stopping charging the target vehicle.

[0088] The second diagnostic instruction is used to instruct to diagnose the target vehicle. As an example, the second diagnostic instruction can be "start" or "1". It can be understood that the embodiment of the present application does not limit the specific content of the second diagnostic instruction.

[0089] Here, if the target vehicle needs to be diagnosed, the user can send a second diagnostic instruction to the diagnostic device through the terminal device, and the diagnostic device can thereby receive a start diagnostic instruction.

[0090] In this embodiment, before diagnosing the vehicle, the actual voltage of the vehicle is first detected by the diagnostic equipment. When the vehicle needs to be diagnosed but the actual voltage of the vehicle is lower than the voltage required for the normal operation of the vehicle, the diagnostic equipment is used to charge the vehicle. On the one hand, the actual voltage of the vehicle can reach the voltage required for the normal operation of the vehicle more quickly. On the other hand, the vehicle can be diagnosed on the premise of ensuring that the actual voltage of the vehicle is greater than or equal to the voltage required for the normal operation of the vehicle. Abnormal communication between the diagnostic equipment and the vehicle due to insufficient vehicle voltage can be avoided. That is, the vehicle diagnostic equipment can be guaranteed to diagnose the vehicle when the vehicle voltage is normal, thereby improving the diagnostic efficiency.

[0091] In a possible embodiment, before the diagnostic device charges the target vehicle in response to the actual voltage being less than the target voltage, the vehicle diagnostic method may further include:

[0092] The diagnostic device diagnoses the target vehicle in response to an actual voltage of the target vehicle being greater than or equal to a target voltage and receiving a second diagnostic instruction.

[0093] Here, the diagnostic device can diagnose the target vehicle only when the actual voltage of the target vehicle is greater than or equal to the target voltage and the second diagnostic instruction is received. The user can determine the timing of the diagnostic device starting to diagnose the target vehicle according to actual needs, that is, the timing of the operation of the diagnostic device can be reasonably controlled.

[0094] Corresponding to the data transmission method described in the above embodiment, Figure 4 A schematic diagram of the structure of a diagnostic device provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0095] Reference Figure 4 , the diagnostic device 400 comprises:

[0096] The detection module 401 may be used to detect the actual voltage of the target vehicle before diagnosing the target vehicle.

[0097] The charging module 402 can be used to charge the target vehicle in response to the actual voltage being less than the target voltage, where the target voltage is the voltage required for the normal operation of the target vehicle; it can also be used to stop charging the target vehicle in response to the detection module detecting that the actual voltage is greater than or equal to the target voltage during the charging process of the target vehicle.

[0098] The diagnosis module 403 may be used to initiate diagnosis of the target vehicle.

[0099] As an embodiment of the present application, the diagnostic device can also be used as an execution subject to implement the above Figure 3 The steps of the embodiment shown and other related method embodiments. The process of each module in the diagnostic device provided in the embodiment of the present application realizing its own function can be specifically referred to the aforementioned Figure 3 The description of the illustrated embodiment and other related method embodiments will not be repeated here.

[0100] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0101] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0102] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0103] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0104] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0105] In addition, in the description of the present specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish descriptions, and cannot be understood as indicating or suggesting relative importance. It should also be understood that although the terms "first", "second", etc. are used to describe various elements in some embodiments of the present application in the text, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first table can be named as the second table, and similarly, the second table can be named as the first table without departing from the scope of the various described embodiments. The first table and the second table are both tables, but they are not the same table.

[0106] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0107] The vehicle diagnostic method provided in the embodiments of the present application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, laptop computers, industrial computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), etc. The embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

[0108] Figure 5 Schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 5 As shown, the electronic device 500 of this embodiment includes: at least one processor 502 ( Figure 5 Only one is shown in the figure), a memory 501, in which a computer program 503 that can be run on a processor 502 is stored. When the processor 502 executes the computer program 503, the steps in the above-mentioned vehicle diagnostic method embodiments are implemented, such as Figure 3 Alternatively, when the processor 502 executes the computer program 503, the functions of each module / unit in the above-mentioned device embodiments are implemented.

[0109] The electronic device 500 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The electronic device may include, but is not limited to, a memory 501 and a processor 502. Those skilled in the art will appreciate that Figure 5 It is only an example of the electronic device 500 and does not constitute a limitation of the electronic device 500. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include an input sending device, a network access device, a bus, etc.

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

[0111] In some embodiments, the processor 502 may be an internal storage unit of the electronic device 500, such as a hard disk or memory of the electronic device 500. The processor 502 may also be an external storage device of the electronic device 500, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 500. Further, the processor 502 may also include both an internal storage unit of the electronic device 500 and an external storage device. The processor 502 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as program codes of a computer program. The processor 502 may also be used to temporarily store data that has been sent or is to be sent.

[0112] In addition, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0113] An embodiment of the present application also provides an electronic device, which includes at least one memory, at least one processor, and a computer program stored in the at least one memory and executable on the at least one processor. When the processor executes the computer program, the electronic device implements the steps of any of the above-mentioned method embodiments.

[0114] The embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0115] An embodiment of the present application provides another computer program product. When the computer program product is run on an electronic device, the electronic device can implement the steps in the above-mentioned method embodiments.

[0116] An embodiment of the present application also provides a chip system, which includes a processor, the processor is coupled to a memory, and the processor executes a computer program stored in the memory to implement the steps in the above-mentioned method embodiments.

[0117] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. Computer-readable storage media may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0118] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0119] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0120] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0121] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A vehicle diagnostic method, characterized in that: Applications in diagnostic equipment, including: Before diagnosing the target vehicle, detecting the actual voltage of the target vehicle; In response to the actual voltage being less than a target voltage, charging the target vehicle, the target voltage being a voltage required for normal operation of the target vehicle; During the charging process of the target vehicle, if it is detected that the actual voltage is greater than or equal to the target voltage, the charging of the target vehicle is stopped; A diagnosis of the target vehicle is started.

2. The vehicle diagnostic method according to claim 1, characterized in that: Before detecting the actual voltage of the target vehicle, the method further includes: acquiring the target voltage of the target vehicle.

3. The vehicle diagnostic method according to claim 2, characterized in that: The obtaining the target voltage of the target vehicle includes: Scanning an identification code on the target vehicle, and determining the model of the target vehicle according to the identification code; The target voltage is determined according to the model of the target vehicle.

4. The vehicle diagnostic method according to claim 1, characterized in that: The detecting the actual voltage of the target vehicle comprises: In response to the diagnostic device successfully establishing a connection with the on-board diagnostic system of the target vehicle, an actual voltage of the target vehicle is detected.

5. The vehicle diagnostic method according to claim 4, characterized in that: The method further comprises: In response to receiving a first diagnosis instruction, detecting the actual voltage of the target vehicle is stopped, wherein the first diagnosis instruction is used to instruct to stop diagnosing the target vehicle.

6. The vehicle diagnostic method according to claim 1, characterized in that: The detecting the actual voltage of the target vehicle comprises: Acquire the actual voltage of the target vehicle from a first pin of a target interface, where the target interface is an interface for connecting the diagnostic device to an on-board diagnostic system on the target vehicle; The charging of the target vehicle includes: charging the target vehicle through the first pin.

7. The vehicle diagnostic method according to any one of claims 1 to 6, characterized in that: The starting of diagnosing the target vehicle includes: In response to receiving a second diagnosis instruction, diagnosis of the target vehicle is started, where the second diagnosis instruction is used to instruct to start diagnosis of the target vehicle.

8. The vehicle diagnostic method according to claim 7, characterized in that: Before charging the target vehicle in response to the actual voltage being less than the target voltage, the method further includes: In response to the actual voltage of the target vehicle being greater than or equal to the target voltage and receiving the second diagnosis instruction, starting to diagnose the target vehicle.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor implements the steps of the method according to any one of claims 1 to 8 when executing the computer program.

10. A computer program product, characterized in that The invention comprises a computer program which, when executed, causes the method according to any one of claims 1 to 8 to be performed.

Images