CN115373367A - Automobile remote diagnosis method, system, diagnostic instrument and terminal equipment - Google Patents
Automobile remote diagnosis method, system, diagnostic instrument and terminal equipment Download PDFInfo
- Publication number
- CN115373367A CN115373367A CN202210978924.3A CN202210978924A CN115373367A CN 115373367 A CN115373367 A CN 115373367A CN 202210978924 A CN202210978924 A CN 202210978924A CN 115373367 A CN115373367 A CN 115373367A
- Authority
- CN
- China
- Prior art keywords
- api
- remote
- program
- end program
- diagnosis
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004171 remote diagnosis Methods 0.000 title claims abstract description 60
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000004891 communication Methods 0.000 claims abstract description 62
- 238000003745 diagnosis Methods 0.000 claims abstract description 42
- 230000004044 response Effects 0.000 claims description 33
- 238000004590 computer program Methods 0.000 claims description 22
- 239000008186 active pharmaceutical agent Substances 0.000 description 9
- 238000012545 processing Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000002405 diagnostic procedure Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
- G05B23/0221—Preprocessing measurements, e.g. data collection rate adjustment; Standardization of measurements; Time series or signal analysis, e.g. frequency analysis or wavelets; Trustworthiness of measurements; Indexes therefor; Measurements using easily measured parameters to estimate parameters difficult to measure; Virtual sensor creation; De-noising; Sensor fusion; Unconventional preprocessing inherently present in specific fault detection methods like PCA-based methods
Abstract
The application discloses an automobile remote diagnosis method, a diagnosis instrument, terminal equipment and an automobile remote diagnosis system. The method is applied to a diagnostic apparatus, the diagnostic apparatus is provided with diagnostic software and a remote program, the remote program comprises a first Application Programming Interface (API), and the method comprises the following steps: the diagnostic software sending a request to the remote program to invoke the first API; the remote program acquires a calling parameter contained in the request; and the remote program sends the calling parameters to a near-end program on the terminal equipment through remote communication so as to instruct the near-end program to call a second API by using the calling parameters, the terminal equipment is in communication connection with the VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed. According to the technical scheme, the automobile diagnosis standard which does not support remote diagnosis can be used, the diagnosis of the vehicle by the diagnosis instrument is realized, and great convenience is brought to a user.
Description
Technical Field
The application belongs to the field of vehicle diagnosis, and particularly relates to a method, a system, a diagnostic instrument and terminal equipment for remote diagnosis of an automobile.
Background
Currently, automobile diagnosis is usually implemented by using a Vehicle Communication Interface (VCI) device to connect a diagnostic instrument and a Vehicle to be diagnosed in a one-to-one Communication manner. However, such diagnostic methods are limited by the used automotive diagnostic standards (such as SAE J2534 and ISO 22900 standards), and cannot realize remote diagnosis of automobiles.
Disclosure of Invention
In view of this, the present application provides an automobile remote diagnosis method, a diagnosis instrument, a terminal device and an automobile remote diagnosis system, which can use an automobile diagnosis standard that does not support remote diagnosis, and implement remote diagnosis of a vehicle by the diagnosis instrument, thereby bringing great convenience to a user.
In a first aspect, the present Application provides an automobile remote diagnosis method, which is applied to a diagnostic apparatus, where the diagnostic apparatus is installed with diagnostic software and a remote program, where the remote program includes a first Application Programming Interface (API), and the automobile remote diagnosis method includes:
the diagnostic software sends a request for calling the first API to the remote program;
the remote program acquires the calling parameters contained in the request;
and the remote program sends the calling parameters to a near-end program on the terminal equipment through remote communication so as to instruct the near-end program to call a second API by using the calling parameters, the terminal equipment is in communication connection with the VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed.
Optionally, after the far-end program sends the calling parameter to the near-end program on the terminal device through remote communication, the method for remote diagnosis of an automobile further includes:
the far-end program receives response data sent by the near-end program, and the response data is obtained after the terminal equipment executes diagnosis operation;
the remote program feeds back the response data to the diagnostic software.
Optionally, the first API is in a first Dynamic Link Library (dll), and before the remote program obtains the call parameter included in the request, the method for remote diagnosis of the vehicle further includes:
loading the first dll to a memory by the diagnostic software;
the diagnostic software generates a request to call a first API in the first dll.
In a second aspect, the present application provides an automobile remote diagnosis method, which is applied to a terminal device, where the terminal device is installed with a near-end program and a second application programming interface API, and the automobile remote diagnosis method includes:
when the near-end program receives a calling parameter aiming at a first API sent by a far-end program on a diagnostic instrument through remote communication, the near-end program calls the second API by using the calling parameter, the terminal equipment is in communication connection with VCI equipment through the second API, and the VCI equipment is in communication connection with a vehicle to be diagnosed.
Optionally, after the near-end program calls a second API using the call parameter, the method for remote diagnosis of an automobile further includes:
the near-end program acquires response data obtained by executing diagnosis operation;
the near-end program transmits the response data to the far-end program.
Optionally, the second API is located in a second dynamic link library dll, and before the near-end program calls the second API using the call parameter, the method for remote diagnosis of an automobile further includes:
the near-end program loads the second dll to the memory;
the near-end program calls a second API by using the call parameter, including:
the near-end program calls a second API in the second dll using the call parameter.
In a third aspect, the present application provides an automobile remote diagnosis method, which is applied to an automobile remote diagnosis system, where the automobile remote diagnosis system includes a diagnostic apparatus and a terminal device, the diagnostic apparatus is installed with diagnostic software and a remote program, the remote program includes a first application programming interface API, and the terminal device is installed with a near-end program and a second API, and the automobile remote diagnosis method includes:
the diagnostic software sends a request for calling the first API to the remote program;
the remote program acquires the calling parameters contained in the request;
the remote program sends the calling parameter to the near-end program through remote communication;
and the near-end program calls the second API by using the calling parameter, the terminal equipment is in communication connection with VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed.
In a fourth aspect, the present application provides a diagnostic apparatus comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to the first aspect when executing the computer program.
In a fifth aspect, the present application provides a terminal device, where the terminal device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the method according to the second aspect.
In a sixth aspect, the present application provides an automobile remote diagnosis system, comprising:
a vehicle;
the VCI equipment is connected with the vehicle;
the terminal device according to the fifth aspect is connected to the VCI device;
the diagnostic instrument according to the fourth aspect described above.
As can be seen from the above, in the present application, the diagnostic software sends a request for calling the first API to the remote program; the remote program acquires the calling parameters contained in the request; and the remote program sends the calling parameters to a near-end program on the terminal equipment through remote communication so as to instruct the near-end program to call a second API by using the calling parameters, the terminal equipment is in communication connection with the VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed. The diagnostic instrument is provided with a far-end program, the far-end program comprises a first API, the terminal equipment is provided with a near-end program and a second API, the first API can be called by the diagnostic instrument to remotely transmit calling parameters to the terminal equipment through remote communication of the far-end program and the near-end program, the terminal equipment is connected with a vehicle through VCI equipment, even if the first API and the second API are realized based on an automobile diagnostic standard which does not support remote diagnosis, the terminal equipment uses the calling parameters to call the second API and can still communicate with the VCI equipment, the VCI equipment is communicated with the vehicle to be diagnosed to perform diagnosis operation on the vehicle to be diagnosed, so that the remote diagnosis of the diagnostic instrument on the vehicle is realized, and great convenience is brought to a user.
It is to be understood that, for the beneficial effects of the second aspect to the sixth aspect, reference may be made to the relevant description in the first aspect, and details are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a schematic diagram of an automobile remote diagnosis system provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating an implementation of a method for remote diagnosis of an automobile according to an embodiment of the present application;
FIG. 3 is a flow chart of another implementation of a remote diagnosis method for a vehicle according to an embodiment of the present disclosure;
FIG. 4 is a flow chart of an interaction provided by an embodiment of the present application;
FIG. 5 is a schematic structural diagram of a diagnostic apparatus provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
Currently, the more mainstream automotive diagnostic standards used by the diagnostic apparatus are SAE J2534 standard and ISO 22900 standard. However, these two standards only define the implementation of local diagnosis, that is, the diagnostic apparatus using these two automotive diagnostic standards needs to be connected to the VCI device through a wiring harness near the vehicle to be diagnosed, and then the VCI device is connected to an On-Board Diagnostics (OBD) interface of the vehicle to be diagnosed. In this way, the Diagnostic instrument can use the J2534 API of SAE J2534 standard or the Diagnostic protocol data unit (D-PDU) API of ISO 22900 standard to perform short-distance local diagnosis on the vehicle to be diagnosed. However, nowadays, the convenience is pursued more and more, the user's demand for remote diagnosis of the automobile is more and more intense, and the diagnostic apparatus that only supports short-distance local diagnosis cannot meet the user's demand, which brings inconvenience to the user. Based on this, the embodiment of the application provides an automobile remote diagnosis method, system, diagnostic apparatus and terminal device, where the diagnostic software sends a request for calling the first API to the remote program; the remote program acquires the calling parameters contained in the request; and the remote program sends the calling parameters to a near-end program on the terminal equipment through remote communication so as to instruct the near-end program to call a second API by using the calling parameters, the terminal equipment is in communication connection with the VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed. The diagnostic instrument is provided with a far-end program, the far-end program comprises a first API, the terminal equipment is provided with a near-end program and a second API, the first API can be called by the diagnostic instrument to remotely transmit calling parameters to the terminal equipment through remote communication of the far-end program and the near-end program, the terminal equipment is connected with a vehicle through VCI equipment, even if the first API and the second API are realized based on an automobile diagnostic standard which does not support remote diagnosis, the terminal equipment uses the calling parameters to call the second API and can still communicate with the VCI equipment, the VCI equipment is communicated with the vehicle to be diagnosed to perform diagnosis operation on the vehicle to be diagnosed, so that the remote diagnosis of the diagnostic instrument on the vehicle is realized, and great convenience is brought to a user. In order to explain the technical solutions proposed in the embodiments of the present application, the following description is given by way of specific examples.
The following describes an automobile remote diagnosis system provided in an embodiment of the present application.
Referring to fig. 1, the remote diagnosis system for the automobile includes a vehicle, VCI devices, a terminal device and a diagnostic apparatus. In fig. 1, solid lines indicate wired connections, and broken lines indicate wireless connections. Specifically, the terminal device may be connected to the VCI device through a harness (i.e., a connection line in fig. 1), such as an ethernet or Controller Area Network (CAN) line. The VCI device interfaces with the OBD of the vehicle. The diagnostic apparatus is in communication connection with the terminal device through the internet, and optionally, the diagnostic apparatus may forward data through a preset server, so as to implement mutual communication with the terminal device, and may also perform mutual communication with the terminal device through a P2P (peer to peer) technology, which is not limited herein. The diagnostic instrument is provided with automobile diagnostic software and a remote program, and the remote program comprises a first API. The terminal equipment is provided with a near-end program and a second API. The VCI devices are used to implement the conversion of diagnostic protocols. The user interacts with an interface provided by the automobile diagnosis software, and can trigger the automobile diagnosis software to initiate a request so as to call the first API in the remote program. When the automobile diagnosis software calls the first API, the calling parameters can be transmitted to the first API. The remote program and the near-end program can be in remote communication, and the remote program can send the calling parameters to the near-end program through the remote communication. After the near-end program receives the calling parameter, the near-end program can call the second API, and transmit the received calling parameter when calling the second API, so that the second API is communicated with the VCI equipment based on the calling parameter, and diagnosis of the vehicle is achieved.
The following describes an automobile remote diagnosis method provided by an embodiment of the present application. The remote diagnosis method for the automobile can be applied to the diagnostic apparatus in fig. 1, the diagnostic apparatus is provided with diagnostic software and a remote program, the remote program comprises a first API, please refer to fig. 2, and the remote diagnosis method for the automobile comprises the following steps:
And 203, the far-end program sends the calling parameter to a near-end program on the terminal device through remote communication so as to instruct the near-end program to call a second API by using the calling parameter, the terminal device is in communication connection with the VCI device through the second API, and the VCI device is in communication connection with the vehicle to be diagnosed.
In the embodiment of the application, the diagnostic apparatus may be installed with the vehicle diagnostic software and a remote program, and the remote program includes a first API. The automobile diagnosis software can provide an interface for a user, and the user can trigger the automobile diagnosis software to initiate a request for calling the first API by interacting with the interface. It should be understood that the automobile diagnosis software may add call parameters required for calling the first API to the request when calling the first API, and then send the request to the remote program. The remote program can establish communication connection with the terminal device, and after extracting the calling parameter from the request, the calling parameter is sent to the terminal device. Optionally, the terminal device may install a near-end program and a second API. The near-end program may communicate with the far-end program, receive the call parameter sent by the far-end program, and then call the second API using the call parameter.
Wherein the second API is to perform a diagnostic operation. It should be noted that the first API and the second API meet the same automotive diagnostic standard. For example, the first API and the second API are developed based on SAE J2534 standard or ISO 22900 standard. Specifically, the first API and the second API may both be J2534 APIs, and may both be D-PDU APIs. Because the terminal equipment and the VCI equipment are connected through a wire harness, the terminal equipment can be in communication connection with the VCI equipment by calling the J2534 API or the D-PDU API, so that the diagnosis of the vehicle is realized.
It should be understood that although the first API and the second API conform to the same automotive diagnostic standard, the internal implementation of the two APIs may be different. The first API is used for the automobile diagnosis software to call, receives the call parameters transmitted by the automobile diagnosis software and then sends the call parameters to the near-end program of the terminal equipment. The near-end program may be communicatively connected to the VCI device through the second API, so as to perform a diagnostic operation, which is a function specified by an automotive diagnostic standard and is not described in detail herein. Since the first API and the second API conform to the same automotive diagnostic standard, the call parameters required to call the first API and call the second API are the same. The near-end program may call the second API using the received call parameters.
In some embodiments, after step 203, the method for remote diagnosis of an automobile further includes:
and the far-end program receives the response data sent by the near-end program.
The remote program feeds back the response data to the diagnostic software.
And the response data is obtained after the terminal equipment executes diagnosis operation after the near-end program calls the second API. For example, the response data is a parameter generated by the terminal device after the terminal device performs the diagnosis operation, and for example, the response data is a parameter fed back by the vehicle to be diagnosed after the terminal device performs the diagnosis operation and interacts with the vehicle to be diagnosed through the VCI device. After the far-end program receives the response data sent by the near-end program, the response data can be fed back to the diagnostic software which initiates the request.
In some embodiments, before step 202, the method for remote diagnosis of an automobile further includes:
the diagnostic software loads the first dll into memory.
The diagnostic software generates a request to call a first API in the first dll.
In an embodiment of the present application, the first dll may exist in the remote program with the first API in the first dll, i.e., the first API is defined in the first dll file. After the automobile diagnostic software is run, the first dll may be loaded into the memory and a request to call the first API in the first dll may be generated. After the automobile diagnostic software generates a request to call the first API in the first dll, the request may be sent to a remote program. The remote program, upon receiving the request, may invoke the first API.
Therefore, the remote diagnosis instrument can remotely transmit the calling parameters to the terminal equipment by installing the remote program containing the first API on the diagnosis instrument and installing the near-end program and the second API on the terminal equipment.
Another method for remote diagnosis of an automobile provided in the embodiments of the present application is described below. Referring to fig. 3, the method for remote diagnosis of an automobile may be applied to the terminal device in fig. 1, where the terminal device is installed with a near-end program and a second application programming interface API, and includes:
In the embodiment of the application, the terminal device is connected with the VCI device through a wire harness, and the VCI device is connected with an OBD interface of a vehicle to be diagnosed. The diagnostic instrument may have installed thereon automotive diagnostic software and a remote program that includes a first API. The automobile diagnosis software can provide an interface for a user, and the user can trigger the automobile diagnosis software to initiate a request for calling the first API by interacting with the interface. It should be understood that when the automobile diagnostic software calls the first API, the automobile diagnostic software may add call parameters required to call the first API to the request and then send the request to the remote program. The remote program can establish remote communication with the near-end program on the terminal equipment, and after the calling parameter is extracted from the request, the calling parameter is sent to the near-end program on the terminal equipment through the remote communication. Specifically, the terminal device may install a near-end program and a second API. The near-end program may communicate with the far-end program, receive the call parameter sent by the far-end program, and then call the second API using the call parameter.
The second API is used for being in communication connection with the VCI equipment so as to execute diagnosis operation. It should be noted that the first API and the second API meet the same automotive diagnostic standard. For example, the first API and the second API are developed based on the SAE J2534 standard or the ISO 22900 standard. Specifically, the first API and the second API may both be the J2534 API, and may both be the D-PDU API. Because the terminal equipment and the VCI equipment are connected through a wire harness, the terminal equipment can be in communication connection with the VCI equipment by calling the J2534 API or the D-PDU API, so that the diagnosis of the vehicle is realized.
It should be understood that although the first API and the second API conform to the same automotive diagnostic standard, the internal implementation of the two APIs may be different. The first API is used for the automobile diagnosis software to call, receives the call parameters transmitted by the automobile diagnosis software and then sends the call parameters to the near-end program of the terminal equipment. The second API is used for communicating with the VCI device to perform a diagnostic operation, which is a function specified by an automotive diagnostic standard and is not described in detail herein. Since the first API and the second API conform to the same automotive diagnostic standard, the call parameters required to call the first API and call the second API are the same. The terminal equipment can call the second API by using the received calling parameters.
In some embodiments, after step 301, the remote diagnosis method further includes:
the near-end program acquires response data obtained by executing diagnosis operation;
the near-end program transmits the response data to the far-end program.
And the response data is obtained after the terminal equipment executes diagnosis operation after the near-end program calls the second API. For example, the response data is a parameter generated by the terminal device after the terminal device performs the diagnosis operation, and for example, the response data is a parameter fed back by the vehicle to be diagnosed after the terminal device performs the diagnosis operation and interacts with the vehicle to be diagnosed through the VCI device. After the response data is obtained by the near-end program, the response data may be sent to the far-end program on the diagnostic instrument. After the far-end program receives the response data sent by the near-end program, the response data can be fed back to the initiating program which initiates the request, namely the diagnostic software. The diagnostic software may receive the response data through the first API and then use the response data to complete the diagnosis.
In some embodiments, the terminal device may store at least two second APIs, each implemented in a different manner, but both used to communicatively couple with the VCI device to perform the diagnostic operations. Based on this, the automobile remote diagnosis method further comprises the following steps:
the near-end program takes the second API selected by the user in the at least two second APIs as the target API.
The step 301 includes:
the near-end program calls the target API using the call parameter.
Wherein the at least two second APIs may be developed by different manufacturers based on the same automotive diagnostic standard. Although each second API is used for performing the diagnostic operation, the internal implementation is different, and each second API corresponds to a different VCI device. That is, the second API needs to be used with the corresponding VCI device to perform the diagnostic operation. For example, the second API developed by manufacturer a needs to be used with the VCI device developed by manufacturer a to perform the diagnostic operation. In the embodiment of the application, in order to realize compatibility between the API and the VCI of each manufacturer, at least two second APIs may be installed on the terminal device. The user may select a second API corresponding to the VCI device among the at least two second APIs as a target API according to the VCI device used. Then, the near-end program can use the received calling parameter to call the target API, and since the target API is the second API selected by the user and corresponding to the used VCI device, the calling target API can effectively drive the VCI device to implement diagnosis of the vehicle to be diagnosed.
In some embodiments, before step 301, the remote diagnosis method further includes:
the near-end program loads the second dll to memory.
Accordingly, the step 301 includes:
the near-end program calls a second API in the second dll using the call parameter.
In the embodiment of the present application, the second API is in the second dll, that is, the second API is defined in the second dll file. After the near-end program on the terminal device runs, the second dll may be loaded into the memory. After receiving the calling parameter sent by the far-end program, the near-end program can immediately use the calling parameter to call the second API of the second dll in the memory.
Therefore, according to the scheme, the remote program is installed on the diagnostic apparatus, the remote program comprises the first API, the near-end program and the second API are installed on the terminal device, the diagnostic apparatus can call the first API to remotely transmit the call parameters to the terminal device, and the terminal device is connected with the vehicle through the VCI device.
For ease of understanding, the interaction flow between the diagnostic apparatus and the terminal device is described below with reference to fig. 4.
Step 401, the diagnostic instrument runs the vehicle diagnostic software and the remote program.
Step 402, the terminal device runs a near-end program.
In step 403, the near-end program loads the second dll into the memory, with the second API in the second dll.
Step 404, the far-end program and the near-end program establish a communication connection through a preset communication protocol.
Step 405, the diagnostic software loads a first dll in the remote program into the memory, and the first API is in the first dll.
At step 406, the diagnostic software generates a request to call the first API in the first dll and sends the request to the remote program, and adds a calling parameter to the request.
Step 407, the remote program receives the request, and extracts the call parameters included in the request.
In step 408, the diagnostic device (remote program) sends the calling parameters to the terminal device (near-end program) via the internet.
And step 409, the near-end program receives the calling parameters sent by the far-end program on the diagnostic instrument through the Internet.
At step 410, the near-end program calls a second API in the second dll using the received call parameters to cause the second API to perform diagnostic operations.
Therefore, in the scheme of the application, the far-end program is installed on the diagnostic apparatus, the far-end program comprises the first API, the near-end program and the second API are installed on the terminal device, the diagnostic apparatus can call the first API to remotely transmit the call parameter to the terminal device, and the terminal device is connected with the vehicle through the VCI device.
Corresponding to the above provided method for remote diagnosis of an automobile, an embodiment of the present application further provides a diagnostic apparatus, please refer to fig. 5, in which the diagnostic apparatus 5 in the embodiment of the present application includes: a memory 501, one or more processors 502 (only one shown in fig. 5), and a computer program stored on the memory 501 and executable on the processors. Wherein: the memory 501 is used for storing software programs and units, and the processor 502 executes various functional applications and data processing by operating the software programs and units stored in the memory 501. Specifically, the processor 502 realizes the following steps by running the above-mentioned computer program stored in the memory 501:
the diagnostic software sends a request for calling the first API to the remote program;
the remote program acquires the calling parameters contained in the request;
and the remote program sends the calling parameters to a near-end program on the terminal equipment through remote communication so as to instruct the near-end program to call a second API by using the calling parameters, the terminal equipment is in communication connection with the VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed.
In a second possible implementation manner provided on the basis of the first possible implementation manner, after the far-end program sends the call parameter to the near-end program on the terminal device through remote communication, the processor 502 further implements the following steps when running the computer program stored in the memory 501:
the far-end program receives response data sent by the near-end program, and the response data is obtained after the terminal equipment executes diagnosis operation;
the remote program feeds the response data back to the diagnostic software.
In a third possible implementation manner provided on the basis of the first possible implementation manner, the first API is in the first dynamic link library dll, and before the remote program obtains the call parameter included in the request, the processor 502 further implements the following steps when running the computer program stored in the memory 501:
loading the first dll to a memory by the diagnostic software;
the diagnostic software generates a request to call a first API in the first dll.
It should be understood that in the embodiments of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor may be other general-purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Corresponding to another automobile remote diagnosis method provided above, an embodiment of the present application further provides a terminal device, where the terminal device is connected to a vehicle to be diagnosed through a vehicle communication interface VCI device. Referring to fig. 6, a terminal device 6 in the embodiment of the present application includes: a memory 601, one or more processors 602 (only one shown in fig. 6), and computer programs stored on the memory 601 and executable on the processors. Wherein: the memory 601 is used for storing software programs and units, and the processor 602 executes various functional applications and data processing by operating the software programs and units stored in the memory 601. Specifically, the processor 602 implements the following steps by running the above-mentioned computer program stored in the memory 601:
when the near-end program receives calling parameters aiming at the first API sent by the far-end program on the diagnostic instrument through remote communication, the near-end program calls the second API by using the calling parameters, the terminal equipment is in communication connection with VCI equipment through the second API, and the VCI equipment is in communication connection with a vehicle to be diagnosed.
In a second possible implementation manner provided on the basis of the first possible implementation manner, after the near-end program calls the second API using the call parameter, the processor 602 further implements the following steps when executing the computer program stored in the memory 601:
the near-end program acquires response data obtained by executing diagnosis operation;
the near-end program transmits the response data to the far-end program.
In a third possible implementation manner provided on the basis of the first possible implementation manner, the second API is in a second dynamic link library dll, and before the near-end program calls the second API using the call parameter, the processor 602 further implements the following steps when executing the computer program stored in the memory 601:
the near-end program loads the second dll to the memory;
the near-end program calls a second API by using the call parameter, including:
the near-end program calls a second API in the second dll using the call parameter.
It should be understood that in the embodiments of the present Application, the Processor 602 may be a Central Processing Unit (CPU), and the Processor may be other general-purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional units and modules is only used for illustration, and in practical applications, the above functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement all or part of the above described functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of external device software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the above-described modules or units is only one logical functional division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. The computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file or some intermediate form. The computer-readable storage medium may include: any entity or device capable of carrying the above-described computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer readable Memory, read-Only Memory (ROM), random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable storage medium may contain other contents which can be appropriately increased or decreased according to the requirements of the legislation and the patent practice in the jurisdiction, for example, in some jurisdictions, the computer readable storage medium does not include an electrical carrier signal and a telecommunication signal according to the legislation and the patent practice.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. The remote automobile diagnosis method is applied to a diagnosis instrument, the diagnosis instrument is provided with diagnosis software and a remote program, the remote program comprises a first Application Programming Interface (API), and the remote automobile diagnosis method comprises the following steps:
the diagnostic software sending a request to the remote program to invoke the first API;
the remote program acquires the calling parameters contained in the request;
and the far-end program sends the calling parameters to a near-end program on the terminal equipment through remote communication so as to instruct the near-end program to call a second API by using the calling parameters, the terminal equipment is in communication connection with VCI equipment through the second API, and the VCI equipment is in communication connection with a vehicle to be diagnosed.
2. The remote diagnosis method for automobile according to claim 1, wherein after the remote program transmits the calling parameter to the near-end program on the terminal device by remote communication, the remote diagnosis method for automobile further comprises:
the far-end program receives response data sent by the near-end program, and the response data is obtained after the terminal equipment executes diagnosis operation;
the remote program feeds back the response data to the diagnostic software.
3. The remote automobile diagnosis method as claimed in claim 1, wherein the first API is in a first dynamic link library dll, and before the remote program obtains the call parameter included in the request, the remote automobile diagnosis method further comprises:
the diagnostic software loads the first dll to a memory;
the diagnostic software generates a request to call a first API in the first dll.
4. The automobile remote diagnosis method is applied to terminal equipment, the terminal equipment is provided with a near-end program and a second Application Programming Interface (API), and the automobile remote diagnosis method comprises the following steps:
when the near-end program receives a calling parameter aiming at a first API sent by a far-end program on a diagnostic instrument through remote communication, the near-end program calls a second API by using the calling parameter, the terminal equipment is in communication connection with VCI equipment through the second API, and the VCI equipment is in communication connection with a vehicle to be diagnosed.
5. The automobile remote diagnosis method of claim 4, wherein after the near-end program calls the second API using the call parameter, the automobile remote diagnosis method further comprises:
the near-end program acquires response data obtained by executing diagnosis operation;
the near-end program sends the response data to the far-end program.
6. The automobile remote diagnosis method of claim 4, wherein the second API is in a second dynamic link library dll, and before the near-end program calls the second API using the call parameter, the automobile remote diagnosis method further comprises:
the near-end program loads the second dll to the memory;
the near-end program calls the second API by using the calling parameter, and the method comprises the following steps:
the near-end program calls a second API in the second dll using the call parameter.
7. The automobile remote diagnosis method is characterized by being applied to an automobile remote diagnosis system, the automobile remote diagnosis system comprises a diagnosis instrument and terminal equipment, the diagnosis instrument is provided with diagnosis software and a far-end program, the far-end program comprises a first Application Programming Interface (API), the terminal equipment is provided with a near-end program and a second API, and the automobile remote diagnosis method comprises the following steps:
the diagnostic software sending a request to the remote program to invoke the first API;
the remote program acquires a calling parameter contained in the request;
the far-end program sends the calling parameters to the near-end program through remote communication;
and the near-end program calls the second API by using the calling parameter, the terminal equipment is in communication connection with VCI equipment through the second API, and the VCI equipment is in communication connection with the vehicle to be diagnosed.
8. A diagnostic instrument comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor when executing the computer program implements the method of any one of claims 1 to 3.
9. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any of claims 4 to 6 when executing the computer program.
10. An automotive remote diagnostic system, comprising:
a vehicle;
a VCI device connected with the vehicle;
the terminal device of claim 9, connected to the VCI device;
the diagnostic instrument of claim 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210978924.3A CN115373367A (en) | 2022-08-16 | 2022-08-16 | Automobile remote diagnosis method, system, diagnostic instrument and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210978924.3A CN115373367A (en) | 2022-08-16 | 2022-08-16 | Automobile remote diagnosis method, system, diagnostic instrument and terminal equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115373367A true CN115373367A (en) | 2022-11-22 |
Family
ID=84065813
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210978924.3A Pending CN115373367A (en) | 2022-08-16 | 2022-08-16 | Automobile remote diagnosis method, system, diagnostic instrument and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115373367A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115933621A (en) * | 2023-03-14 | 2023-04-07 | 深圳顶匠科技有限公司 | Vehicle remote diagnosis service method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104850113A (en) * | 2014-11-14 | 2015-08-19 | 北汽福田汽车股份有限公司 | Automobile remote diagnostic system and method |
| FR3072622A1 (en) * | 2017-10-19 | 2019-04-26 | Psa Automobiles Sa | ON-LINE DIAGNOSTIC SYSTEM FOR A MOTOR VEHICLE EQUIPPED WITH A DIAGNOSTIC COMPUTER |
| CN110515366A (en) * | 2019-07-29 | 2019-11-29 | 华为技术有限公司 | A kind of method for diagnosing faults and device |
| CN111538312A (en) * | 2020-04-22 | 2020-08-14 | 深圳市元征科技股份有限公司 | Vehicle remote diagnosis method, system, equipment connector and vehicle connector |
| US20210005031A1 (en) * | 2019-07-01 | 2021-01-07 | Hunter Engineering Company | System and Method For Presentation of Remote Vehicle Diagnostics and Service Guidance Through A Local Vehicle Service System |
| CN114003018A (en) * | 2021-10-25 | 2022-02-01 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method and related device |
-
2022
- 2022-08-16 CN CN202210978924.3A patent/CN115373367A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104850113A (en) * | 2014-11-14 | 2015-08-19 | 北汽福田汽车股份有限公司 | Automobile remote diagnostic system and method |
| FR3072622A1 (en) * | 2017-10-19 | 2019-04-26 | Psa Automobiles Sa | ON-LINE DIAGNOSTIC SYSTEM FOR A MOTOR VEHICLE EQUIPPED WITH A DIAGNOSTIC COMPUTER |
| US20210005031A1 (en) * | 2019-07-01 | 2021-01-07 | Hunter Engineering Company | System and Method For Presentation of Remote Vehicle Diagnostics and Service Guidance Through A Local Vehicle Service System |
| CN110515366A (en) * | 2019-07-29 | 2019-11-29 | 华为技术有限公司 | A kind of method for diagnosing faults and device |
| CN111538312A (en) * | 2020-04-22 | 2020-08-14 | 深圳市元征科技股份有限公司 | Vehicle remote diagnosis method, system, equipment connector and vehicle connector |
| CN114003018A (en) * | 2021-10-25 | 2022-02-01 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method and related device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115933621A (en) * | 2023-03-14 | 2023-04-07 | 深圳顶匠科技有限公司 | Vehicle remote diagnosis service method and system |
| CN115933621B (en) * | 2023-03-14 | 2023-08-04 | 深圳鼎匠科技有限公司 | Vehicle remote diagnosis service method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107479525B (en) | Vehicle remote diagnosis system and its control method | |
| CN110928567A (en) | Vehicle system upgrading method, terminal device and computer-readable storage medium | |
| US11240317B2 (en) | Diagnostic method and system for vehicle, and related device thereof | |
| EP3072309B1 (en) | Virtual communication interface for motor vehicle diagnosis | |
| US9451028B2 (en) | Communication profile selection for vehicle telematics device | |
| CN102804126B (en) | Vehicle communication interface and method of operating thereof | |
| CN111538312B (en) | Vehicle remote diagnosis method, system, equipment connector and vehicle connector | |
| WO2021035634A1 (en) | Remote diagnosis method and system for vehicles | |
| CN111427335A (en) | Vehicle remote diagnosis method, equipment connector and vehicle connector | |
| CN111506047B (en) | Vehicle diagnosis method, device and storage medium | |
| CN114253251A (en) | Vehicle remote diagnosis method and device, equipment connector and storage medium | |
| CN115373367A (en) | Automobile remote diagnosis method, system, diagnostic instrument and terminal equipment | |
| WO2016008077A1 (en) | Method and apparatus for interconnecting intelligent terminal and vehicle terminal | |
| CN112578764A (en) | Vehicle fault diagnosis method and system and vehicle | |
| CN113038421A (en) | Automobile diagnosis method, automobile diagnosis device and automobile gateway | |
| US20140130063A1 (en) | Systems and methods for low overhead remote procedure calls | |
| CN111913472A (en) | Operation mode control method of vehicle diagnostic device and related device | |
| CN112927392A (en) | Communication method, vehicle communication interface device and readable storage medium | |
| CN112214228A (en) | Vehicle-mounted instrument upgrading method, device and system | |
| CN109917775A (en) | Automobile security gateway data transmission method and electronic equipment | |
| CN114817097A (en) | Single-wire communication method, system, device and storage medium | |
| CN108803582B (en) | Automatic bus switching system and method suitable for remote fault diagnosis | |
| CN114503041B (en) | Vehicle diagnosis method, diagnosis connector and diagnosis device | |
| CN112540825A (en) | Data receiving and transmitting method and system for diagnostic software in virtual machine | |
| CN115914429B (en) | Communication protocol adaptation method, device, electronic equipment, vehicle and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |