CN117092985A - Vehicle diagnosis method, device, equipment and medium - Google Patents
Vehicle diagnosis method, device, equipment and medium Download PDFInfo
- Publication number
- CN117092985A CN117092985A CN202311162943.XA CN202311162943A CN117092985A CN 117092985 A CN117092985 A CN 117092985A CN 202311162943 A CN202311162943 A CN 202311162943A CN 117092985 A CN117092985 A CN 117092985A
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- vehicle
- data
- server
- detected
- 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
- 238000003745 diagnosis Methods 0.000 title claims abstract description 198
- 238000000034 method Methods 0.000 title claims abstract description 25
- 230000006870 function Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 12
- 238000002405 diagnostic procedure Methods 0.000 claims description 11
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012631 diagnostic technique Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
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/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The application discloses a vehicle diagnosis method, a device, equipment and a medium, comprising the following steps: calling a preset server interface based on vehicle information of the vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected returned by a server; the target diagnosis data are diagnosis data which are analyzed from ODX diagnosis files of the electronic control units; the common data is data extracted from a common file of each electronic control unit; the executable diagnosis script file is a file obtained by analyzing an OTX flow file; diagnosing the vehicle to be diagnosed based on the target diagnosis data, the public data and the executable diagnosis script file. Therefore, the diagnosis data after analysis is downloaded by calling an interface provided by the server without downloading the diagnosis file to the local, and then the diagnosis data is used, so that the diagnosis data is smaller than the data quantity of the diagnosis file, the network overhead is reduced, the analysis is not needed locally, the diagnosis efficiency is improved, and the leakage risk is reduced.
Description
Technical Field
The present application relates to the field of vehicle diagnosis technologies, and in particular, to a vehicle diagnosis method, device, apparatus, and medium.
Background
With the development of ODX, open diagnostic data exchange, open diagnostic data exchange) diagnostic techniques, more and more host factories choose this approach to diagnose, and at present, the common diagnostic procedures are: the developer develops the diagnosis file of each ECU (Electronic Control Unit ) according to the vehicle type, packages the diagnosis file into a vehicle diagnosis data packet, uploads the vehicle diagnosis data packet to the server, reads the vehicle information from the diagnosis client, downloads the diagnosis data packet of the vehicle from the server, analyzes the diagnosis data packet locally, and acquires the analyzed data through a corresponding interface, thereby performing vehicle diagnosis. However, this may result in time consuming and inefficient overall process, where one diagnostic data packet includes diagnostic data ODX files, diagnostic script OTX (i.e. Open Test sequence eXchange, open test sequence exchange format) files, and multilingual files of all ECU systems, which are generally tens of M in size, and each time a diagnosis is performed, the data packet is downloaded and parsed, which is more inconvenient in a network bad scenario, consumes network resources, and presents a risk of disclosure.
Disclosure of Invention
In view of the above, an object of the present application is to provide a vehicle diagnosis method, apparatus, device, and medium, which can improve diagnosis efficiency and reduce risk of disclosure. The specific scheme is as follows:
in a first aspect, the present application discloses a vehicle diagnostic method comprising:
calling a preset server interface based on vehicle information of a vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected, which are returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of the electronic control units; the public data are data extracted from public files of all electronic control units; the executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected;
and diagnosing the vehicle to be diagnosed based on the target diagnosis data, the public data and the executable diagnosis script file.
Optionally, obtaining target diagnostic data corresponding to the vehicle to be detected returned by the server includes:
acquiring a diagnosis data structure corresponding to the vehicle to be detected returned by the server; the diagnosis data structure stores the target diagnosis data, and each element in the diagnosis data structure is the diagnosis data extracted from an ODX diagnosis file of an electronic control unit.
Optionally, the preset server interface includes a first preset interface, a second preset interface and a third preset interface;
the first preset interface is used for acquiring target diagnosis data corresponding to the vehicle to be detected returned by the server; the second preset interface is used for acquiring an executable diagnosis script file corresponding to the vehicle to be detected, which is returned by the server; the third preset interface is used for acquiring public data returned by the server.
Optionally, each OTX flow file corresponds to an interface function in the executable diagnostic script file.
Optionally, calling a preset server interface based on vehicle information of the vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected returned by the server, where the method includes:
calling a preset server interface based on vehicle information of a vehicle to be detected, determining a vehicle type corresponding to the vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle type returned by a server.
In a second aspect, the present application discloses a vehicle diagnostic apparatus including:
the acquisition module is used for calling a preset server interface based on vehicle information of the vehicle to be detected and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected, which are returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of the electronic control units; the public data are data extracted from public files of all electronic control units; the executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected;
and the diagnosis module is used for diagnosing the vehicle to be diagnosed based on the target diagnosis data, the public data and the executable diagnosis script file.
In a third aspect, the application discloses an electronic device comprising a processor and a memory; wherein,
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the vehicle diagnostic method described above.
In a fourth aspect, the present application discloses a computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the aforementioned vehicle diagnostic method.
The method comprises the steps of calling a preset server interface based on vehicle information of a vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of each electronic control unit, the public data are data extracted from public files of each electronic control unit, the executable diagnosis script files are diagnosis script files obtained by analyzing all OTX flow files corresponding to the vehicle to be detected, and then the vehicle to be diagnosed is diagnosed based on the target diagnosis data, the public data and the executable diagnosis script files. In other words, the application obtains the diagnostic data, the public data and the executable diagnostic script file which are corresponding to the vehicle to be detected and returned by the server and are analyzed from the diagnostic file by calling the preset server interface, and then diagnoses the vehicle to be diagnosed based on the target diagnostic data, the public data and the executable diagnostic script file.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a vehicle diagnostic method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a specific vehicle model diagnosis according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a vehicle diagnostic apparatus according to an embodiment of the present application;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
With the continuous popularity of ODX standards, more and more host factories choose to make after-market diagnosis in an ODX diagnosis data packet mode, after-market technicians upload diagnosis data packets of vehicles to a server, 4S end users download the diagnosis data packets of the vehicles through a network, and diagnosis software loads the diagnosis data to make vehicle diagnosis. Thus, each time a vehicle is diagnosed, it is necessary to upload vehicle information, download the vehicle diagnostic data packet, and parse it locally. However, the operation is complicated, the downloading needs to be performed again each time, the whole process is time-consuming and has low efficiency, one diagnosis data packet comprises diagnosis data ODX files, diagnosis script OTX files and multilingual files of all ECU systems, the size of the diagnosis data packet is tens of M generally, the data packet is downloaded and analyzed each time the diagnosis is performed, the network resource is more inconvenient in a network bad scene, and the leakage risk exists. If the vehicle diagnostic data packet is saved locally. Whether the local diagnosis version is up-to-date or not can not be judged, and the local diagnosis version is stored locally, is easy to acquire and crack, and is not high in safety. Therefore, the application provides a vehicle diagnosis scheme which can improve diagnosis efficiency and reduce leakage risk.
Referring to fig. 1, an embodiment of the present application discloses a vehicle diagnosis method, including:
step S11: calling a preset server interface based on vehicle information of a vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected, which are returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of the electronic control units; the public data are data extracted from public files of all electronic control units; the executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected.
It should be noted that the vehicle diagnosis method provided in the present embodiment may be applied to a diagnostic apparatus.
In a specific embodiment, a preset server interface may be called based on vehicle information of a vehicle to be detected, a vehicle type corresponding to the vehicle to be detected is determined, and target diagnosis data, public data and an executable diagnosis script file corresponding to the vehicle type returned by a server are obtained. Further, vehicle information can be read, a preset server interface is called based on the vehicle information, and a vehicle type corresponding to the vehicle to be detected is determined. The vehicle information may be a VIN code (i.e., vehicle Identification Number, vehicle identification code). The VIN code may be used as an input parameter to a predetermined server interface.
Further, in one embodiment, a diagnostic data structure corresponding to the vehicle to be detected returned by the server may be obtained; the diagnosis data structure stores the target diagnosis data, and each element in the diagnosis data structure is the diagnosis data extracted from an ODX diagnosis file of an electronic control unit. That is, in the embodiment of the present application, the target diagnostic data is diagnostic data that is parsed by the server from the ODX diagnostic files of each electronic control unit of the vehicle model, and the diagnostic data of each electronic control unit is stored in one diagnostic data structure. Each vehicle model is provided with a diagnosis data structure corresponding to the vehicle model and an executable diagnosis script file. It will be appreciated that the diagnostic data is critical data required for diagnosis extracted from the ODX diagnostic file, and the data size is small.
In a specific embodiment, the preset server interface includes a first preset interface and a second preset interface; the first preset interface is used for acquiring target diagnosis data corresponding to the vehicle to be detected returned by the server; the second preset interface is used for acquiring an executable diagnosis script file corresponding to the vehicle to be detected, which is returned by the server. The executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected, and each OTX flow file corresponds to one interface function in the executable diagnosis script file.
In addition, the preset server interface further comprises a third preset interface; the third preset interface is used for acquiring public data returned by the server; the common data is data extracted from a common file of each electronic control unit. Specifically, the third preset interface is configured to obtain a common data structure returned by the server, where the common data structure is used to store the common data. That is, each vehicle model has a diagnostic data structure, an executable diagnostic script file, and a common data structure corresponding to the vehicle model.
That is, the server provides three interfaces to the outside, and the first preset interface is used for acquiring a diagnostic data structure corresponding to the vehicle to be detected returned by the server; the second preset interface is used for acquiring an executable diagnosis script file corresponding to the vehicle to be detected, which is returned by the server. The third preset interface is used for acquiring a public data structure returned by the server. It should be noted that the data structure may be obtained and may be directly stored in a memory for operation, for example, in a specific embodiment, a developer develops an ODX file and an OTX flow file of each ECU according to a vehicle model, and uploads the ODX file and the OTX flow file to the server. The server analyzes each ODX file one by one, and stores diagnostic data in the files into an ECU data structure, wherein the ODX file of one ECU system corresponds to one ECU data structure, and all ECU data structures of the whole vehicle are integrated into one ECUS, namely a diagnostic data structure; extracting data in files common to all ECUs into a SHAREDATA data structure and a common data structure; analyzing all OTX flow files of the whole vehicle into 1 executable script file, wherein one OTX file corresponds to an interface function in the script file; the server provides three interfaces A, B, C to the outside, wherein the interface A returns the whole vehicle ECUS data structure on the server; the B interface returns a common part "SHAREDATE" data structure; and C, returning the executable script file of the whole vehicle special function flow by the interface. In this way, the resolving process is put into the server, the server provides the three interfaces, the user can quickly and directly acquire the data structure, then the user can apply the data structure without downloading the file to the local place, and the resolving process can directly store the acquired data structure, so that the efficiency is improved, the risk of disclosure is reduced, and the resolving process is not needed to be carried out locally.
Step S12: and diagnosing the vehicle to be diagnosed based on the target diagnosis data and the executable diagnosis script file.
Therefore, the embodiment of the application calls the preset server interface based on the vehicle information of the vehicle to be detected, and obtains the target diagnosis data, the public data and the executable diagnosis script file corresponding to the vehicle to be detected, which are returned by the server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of each electronic control unit, the public data are data extracted from public files of each electronic control unit, the executable diagnosis script files are diagnosis script files obtained by analyzing all OTX flow files corresponding to the vehicle to be detected, and then the vehicle to be diagnosed is diagnosed based on the target diagnosis data, the public data and the executable diagnosis script files. In other words, the embodiment of the application acquires the diagnostic data, the public data and the executable diagnostic script file which correspond to the vehicle to be detected and are analyzed from the diagnostic file and are returned by the server by calling the preset server interface, and then diagnoses the vehicle to be diagnosed based on the target diagnostic data, the public data and the executable diagnostic script file.
Further, referring to fig. 2, fig. 2 is a schematic diagram of a specific vehicle diagnosis according to an embodiment of the present application. Mainly comprises the following steps:
1. and developing the model diagnosis data ODX file and OTX flow file by a developer of the host factory, and uploading the model diagnosis data ODX file and the OTX flow file to the server.
2. The server analyzes the ODX file of each ECU, stores the ODX file in an ECU data structure, and all the ECUs are integrated into the ECUS. And analyzing files (such as communication parameter-c files) common to all ECUs, and extracting data in the files into a SHAREDATA data structure. Analyzing all OTX flow files of the whole vehicle into 1 executable script file, wherein one OTX file corresponds to an interface function in the script file
3. The server provides three interfaces A, B, C to the outside, wherein the interface A returns the whole vehicle ECUS data structure on the server; the B interface returns a common part "SHAREDATE" data structure; c, the interface returns to the executable script file of the whole vehicle special function flow;
4. the client reads the VIN code of the vehicle, uploads the VIN code to the server, calls an AB interface, and returns the vehicle diagnosis data structures ECUS and SHAREDATA, and the server quickly copies the content of the VIN code to a diagnosis software memory, so that data in the VIN code is obtained, diagnosis of basic functions is supported, and the Size of ECUS is the number of the vehicle ECU; and calling the C interface to obtain an executable script file of the special function of the whole vehicle, and supporting diagnosis of the special function by executing the script file. The basic functions are functions of each ECU, and the special functions are functions special to the ECU, such as vehicle password writing, tail gas measurement and the like.
4. And (5) vehicle diagnosis.
5. And (5) exiting.
Through the steps 1-5, the diagnostic instrument terminal does not need to download huge diagnostic data files each time, only needs to call the interface to copy the diagnostic data to the memory for use, and also does not need to store the diagnostic data locally, thereby greatly improving the diagnostic efficiency, reducing network output, improving after-sale efficiency, improving the safety of the diagnostic data, and being very convenient.
Referring to fig. 3, the present application discloses a vehicle diagnostic apparatus including:
the acquiring module 11 is configured to invoke a preset server interface based on vehicle information of a vehicle to be detected, and acquire target diagnostic data, public data and an executable diagnostic script file corresponding to the vehicle to be detected, which are returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of the electronic control units; the public data are data extracted from public files of all electronic control units; the executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected;
a diagnostic module 12 for diagnosing the vehicle to be diagnosed based on the target diagnostic data, the public data, and the executable diagnostic script file.
Therefore, the embodiment of the application calls the preset server interface based on the vehicle information of the vehicle to be detected, and obtains the target diagnosis data, the public data and the executable diagnosis script file corresponding to the vehicle to be detected, which are returned by the server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of each electronic control unit, the public data are data extracted from public files of each electronic control unit, the executable diagnosis script files are diagnosis script files obtained by analyzing all OTX flow files corresponding to the vehicle to be detected, and then the vehicle to be diagnosed is diagnosed based on the target diagnosis data, the public data and the executable diagnosis script files. In other words, the embodiment of the application acquires the diagnostic data, the public data and the executable diagnostic script file which correspond to the vehicle to be detected and are analyzed from the diagnostic file and are returned by the server by calling the preset server interface, and then diagnoses the vehicle to be diagnosed based on the target diagnostic data, the public data and the executable diagnostic script file.
The acquiring module 11 is specifically configured to acquire a diagnostic data structure corresponding to the vehicle to be detected returned by the server; the diagnosis data structure stores the target diagnosis data, and each element in the diagnosis data structure is the diagnosis data extracted from an ODX diagnosis file of an electronic control unit.
The preset server interface comprises a first preset interface, a second preset interface and a third preset interface; the first preset interface is used for acquiring target diagnosis data corresponding to the vehicle to be detected returned by the server; the second preset interface is used for acquiring an executable diagnosis script file corresponding to the vehicle to be detected, which is returned by the server; the third preset interface is used for acquiring public data returned by the server.
Specifically, the third preset interface is configured to obtain a common data structure returned by the server, where the common data structure is used to store the common data.
Wherein each OTX flow file corresponds to an interface function in the executable diagnostic script file.
And the obtaining module 11 is specifically configured to invoke a preset server interface based on vehicle information of a vehicle to be detected, determine a vehicle type corresponding to the vehicle to be detected, and obtain target diagnosis data, public data and executable diagnosis script file corresponding to the vehicle type returned by the server.
Referring to fig. 4, an embodiment of the present application discloses an electronic device 20 comprising a processor 21 and a memory 22; wherein the memory 22 is used for storing a computer program; the processor 21 is configured to execute the computer program, and the vehicle diagnosis method disclosed in the foregoing embodiment.
For the specific process of the vehicle diagnosis method, reference may be made to the corresponding content disclosed in the foregoing embodiment, and no further description is given here.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk or an optical disk, and the storage mode may be transient storage or permanent storage.
In addition, the electronic device 20 further includes a power supply 23, a communication interface 24, an input-output interface 25, and a communication bus 26; wherein the power supply 23 is configured to provide an operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 25 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application requirement, which is not limited herein.
Further, the embodiment of the application also discloses a computer readable storage medium for storing a computer program, wherein the computer program is executed by a processor to realize the vehicle diagnosis method disclosed in the previous embodiment.
For the specific process of the vehicle diagnosis method, reference may be made to the corresponding content disclosed in the foregoing embodiment, and no further description is given here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing has outlined rather broadly the principles and embodiments of the present application in order that the detailed description of the diagnostic method, apparatus, device and medium of the present application may be better understood, and in order that the present application may be better suited for use in conjunction with the detailed description of the embodiments that follow; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. A vehicle diagnostic method, comprising:
calling a preset server interface based on vehicle information of a vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected, which are returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of the electronic control units; the public data are data extracted from public files of all electronic control units; the executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected;
and diagnosing the vehicle to be diagnosed based on the target diagnosis data, the public data and the executable diagnosis script file.
2. The vehicle diagnosis method according to claim 1, wherein obtaining target diagnosis data corresponding to the vehicle to be detected returned by the server includes:
acquiring a diagnosis data structure corresponding to the vehicle to be detected returned by the server; the diagnosis data structure stores the target diagnosis data, and each element in the diagnosis data structure is the diagnosis data extracted from an ODX diagnosis file of an electronic control unit.
3. The vehicle diagnostic method of claim 1, wherein the preset server interface comprises a first preset interface, a second preset interface, and a third preset interface;
the first preset interface is used for acquiring target diagnosis data corresponding to the vehicle to be detected returned by the server; the second preset interface is used for acquiring an executable diagnosis script file corresponding to the vehicle to be detected, which is returned by the server; the third preset interface is used for acquiring public data returned by the server.
4. The vehicle diagnostic method of claim 1, wherein each OTX flow file corresponds to an interface function in the executable diagnostic script file.
5. The vehicle diagnosis method according to any one of claims 1 to 4, characterized in that calling a preset server interface based on vehicle information of a vehicle to be detected, obtaining target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected returned by a server, includes:
calling a preset server interface based on vehicle information of a vehicle to be detected, determining a vehicle type corresponding to the vehicle to be detected, and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle type returned by a server.
6. A vehicle diagnostic apparatus, characterized by comprising:
the acquisition module is used for calling a preset server interface based on vehicle information of the vehicle to be detected and acquiring target diagnosis data, public data and executable diagnosis script files corresponding to the vehicle to be detected, which are returned by a server; the target diagnosis data are diagnosis data analyzed from ODX diagnosis files of the electronic control units; the public data are data extracted from public files of all electronic control units; the executable diagnosis script file is a diagnosis script file obtained by analyzing all OTX flow files corresponding to the vehicle to be detected;
and the diagnosis module is used for diagnosing the vehicle to be diagnosed based on the target diagnosis data, the public data and the executable diagnosis script file.
7. The vehicle diagnostic apparatus of claim 6, wherein the acquisition module is specifically configured to:
acquiring a diagnosis data structure corresponding to the vehicle to be detected returned by the server; the diagnosis data structure stores the target diagnosis data, and each element in the diagnosis data structure is the diagnosis data extracted from an ODX diagnosis file of an electronic control unit.
8. The vehicle diagnostic apparatus of claim 6, wherein the preset server interface comprises a first preset interface, a second preset interface, and a third preset interface;
the first preset interface is used for acquiring target diagnosis data corresponding to the vehicle to be detected returned by the server; the second preset interface is used for acquiring an executable diagnosis script file corresponding to the vehicle to be detected, which is returned by the server; the third preset interface is used for acquiring public data returned by the server.
9. An electronic device comprising a processor and a memory; wherein,
the memory is used for storing a computer program;
the processor for executing the computer program to implement the vehicle diagnostic method as claimed in any one of claims 1 to 5.
10. A computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the vehicle diagnostic method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311162943.XA CN117092985A (en) | 2023-09-08 | 2023-09-08 | Vehicle diagnosis method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311162943.XA CN117092985A (en) | 2023-09-08 | 2023-09-08 | Vehicle diagnosis method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117092985A true CN117092985A (en) | 2023-11-21 |
Family
ID=88779328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311162943.XA Pending CN117092985A (en) | 2023-09-08 | 2023-09-08 | Vehicle diagnosis method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117092985A (en) |
-
2023
- 2023-09-08 CN CN202311162943.XA patent/CN117092985A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110377462B (en) | Interface testing method and device and terminal equipment | |
| CN108255701B (en) | Scene testing method and mobile terminal | |
| CN111597110B (en) | Page test method and device, electronic equipment and storage medium | |
| CN108459850B (en) | Method, device and system for generating test script | |
| CN110825073A (en) | Engine remote calibration system and method | |
| CN111813622B (en) | Equipment monitoring method and device | |
| CN113076253A (en) | Test method and test device | |
| CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN115203004A (en) | Code coverage rate testing method and device, storage medium and electronic equipment | |
| CN115757014A (en) | Power consumption testing method and device | |
| CN111046245A (en) | Multi-source heterogeneous data source fusion calculation method, system, equipment and storage medium | |
| CN114647422A (en) | Vehicle electronic control unit flashing method, device, equipment and medium | |
| CN111857103B (en) | Vehicle diagnosis method, device, equipment and storage medium | |
| CN117092985A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN110532193A (en) | A kind of method for analyzing performance, calculates equipment and storage medium at device | |
| CN115016968A (en) | Exception handling method, device, equipment and medium | |
| CN111338928A (en) | Chrome-based browser testing method and device | |
| CN115542875A (en) | Vehicle detection method based on SOA service and related equipment | |
| CN112379965B (en) | Sandbox file mapping system, client device, mapping end device, sandbox file mapping method and electronic equipment | |
| CN113934198A (en) | Vehicle diagnosis method, vehicle diagnosis device, electronic device, and storage medium | |
| CN112346981A (en) | Joint debugging test coverage rate detection method and system | |
| CN112817864A (en) | Test file generation method, device, equipment and medium | |
| CN114338846A (en) | Message testing method and device | |
| CN110740134B (en) | URL authentication test method, device, equipment and medium | |
| CN111881021A (en) | Interface test method, device and system |
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 |