CN113778557A - Vehicle diagnosis software configuration method, device, server and storage medium - Google Patents
Vehicle diagnosis software configuration method, device, server and storage medium Download PDFInfo
- Publication number
- CN113778557A CN113778557A CN202111078894.2A CN202111078894A CN113778557A CN 113778557 A CN113778557 A CN 113778557A CN 202111078894 A CN202111078894 A CN 202111078894A CN 113778557 A CN113778557 A CN 113778557A
- Authority
- CN
- China
- Prior art keywords
- target
- software
- data
- user
- function data
- 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
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000003745 diagnosis Methods 0.000 claims abstract description 63
- 230000006870 function Effects 0.000 claims description 151
- 238000004590 computer program Methods 0.000 claims description 20
- 238000012360 testing method Methods 0.000 claims description 17
- 230000009471 action Effects 0.000 claims description 16
- 230000008569 process Effects 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000008439 repair process Effects 0.000 description 3
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 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
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Abstract
The application is applicable to the technical field of vehicles, and provides a vehicle diagnosis software configuration method, a device, diagnosis equipment and a storage medium, wherein the method comprises the following steps: receiving a diagnosis software acquisition instruction sent by a user, wherein the diagnosis software acquisition instruction is used for acquiring target diagnosis software corresponding to target vehicle type information; judging whether the target diagnosis software is obtained for the first time; if yes, sending general data, designated function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software to a user; and if not, sending general data for configuring the target diagnosis software, first function data corresponding to the historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user. Different data for configuring the target diagnosis software can be automatically sent to the user when the data are acquired for the first time and are not acquired for the first time, all the data for configuring the diagnosis software do not need to be sent to the user every time, and the storage requirement on the diagnosis equipment is lowered.
Description
Technical Field
The application belongs to the technical field of vehicles, and particularly relates to a vehicle diagnosis software configuration method, a vehicle diagnosis software configuration device, vehicle diagnosis software configuration equipment and a storage medium.
Background
With the continuous and rapid development of society, automobiles become important transportation tools for people to go out, and when the automobiles have faults, vehicle diagnosis can be carried out through diagnosis software.
Different diagnostic software can be used for diagnosing different types of vehicles, along with the increasing functions of the vehicles, the related configuration data of the diagnostic software is increased, and the requirement on hardware storage resources in diagnostic equipment for installing the diagnostic software is increased.
Disclosure of Invention
The embodiment of the application provides a vehicle diagnostic software configuration method, a vehicle diagnostic software configuration device, a vehicle diagnostic device and a storage medium, and aims to solve the problem that the requirement on hardware storage resources in the existing diagnostic device for installing the vehicle diagnostic software is higher and higher.
In a first aspect, an embodiment of the present application provides a vehicle diagnostic software configuration method, including:
receiving a diagnosis software acquisition instruction sent by a user, wherein the diagnosis software acquisition instruction comprises target vehicle type information and is used for acquiring target diagnosis software corresponding to the target vehicle type information;
judging whether the target diagnosis software is obtained for the first time;
if yes, sending general data, designated function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software to the user;
and if not, sending general data for configuring the target diagnosis software, first functional data corresponding to a historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user.
In one embodiment, the sending, to the user, first function data corresponding to a historical diagnosis result associated with the target vehicle type information includes:
judging whether the historical diagnosis result has a fault or not;
if so, the first functional data is functional data corresponding to the fault type;
and if not, the first functional data is the specified functional data.
In one embodiment, the method further comprises:
acquiring the execution result of the specified function data or the first function data in the use process of the target diagnosis software;
and sending second function data which needs to be configured and is executed by the target diagnosis software in the next step to the user according to the execution result.
In one embodiment, the specified functional data or the first functional data comprises read fault code functional data;
the execution result comprises reading a fault code;
correspondingly, the sending, to the user, second function data that needs to be configured for next execution of the target diagnostic software according to the execution result includes:
and sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step according to the fault code.
In one embodiment, the fault code comprises a fault code for a class of software;
correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises:
and sending fault code clearing function data for configuring the target diagnosis software to the user according to the fault codes of the software categories.
In one embodiment, the fault code comprises a fault code for a hardware class;
correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises:
and sending read data stream function data and action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware category.
In one embodiment, the fault codes include ECU fault codes belonging to a preset severity level;
correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises:
and sending read data flow function data, online programming function data and action test function data for configuring the target diagnosis software to the user according to the ECU fault code belonging to the preset severity level.
In a second aspect, an embodiment of the present application provides a vehicle diagnostic software configuration apparatus, including:
the system comprises an acquisition instruction receiving module, a diagnosis software acquisition module and a diagnosis software analysis module, wherein the acquisition instruction receiving module is used for receiving a diagnosis software acquisition instruction sent by a user, the diagnosis software acquisition instruction comprises target vehicle type information and is used for acquiring target diagnosis software corresponding to the target vehicle type information;
the judging module is used for judging whether the target diagnosis software is obtained for the first time;
the first sending module is used for sending general data, designated function data and configuration parameters corresponding to the target vehicle type information to the user when the target diagnosis software is obtained for the first time;
and the second sending module is used for sending general data for configuring the target diagnosis software, first functional data corresponding to a historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user when the target diagnosis software is not obtained for the first time.
In one embodiment, the second sending module specifically includes:
the judging unit is used for judging whether the historical diagnosis result has a fault or not;
the first sending unit is used for judging that the historical diagnosis result has a fault and sending first function data corresponding to the historical diagnosis result related to the target vehicle type information to the user as function data corresponding to the fault type;
and the second sending unit is used for judging that the historical diagnosis result has no fault, and sending the first function data corresponding to the historical diagnosis result related to the target vehicle type information to the user as the specified function data.
In one embodiment, the vehicle diagnostic software configuration apparatus further comprises:
an execution result acquisition module, configured to acquire an execution result of the specified functional data or the first functional data in a use process of the target diagnostic software;
and the third sending module is used for sending second function data which needs to be configured in the next step of the target diagnosis software to the user according to the execution result.
In one embodiment, the specified functional data or the first functional data comprises read fault code functional data; the execution result comprises reading a fault code;
correspondingly, the third sending module is specifically configured to: and sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step according to the fault code.
In one embodiment, the fault code comprises a fault code for a class of software; the third sending module is specifically configured to: and sending fault code clearing function data for configuring the target diagnosis software to the user according to the fault codes of the software categories.
In one embodiment, the fault code comprises a fault code for a hardware class; the third sending module is specifically configured to: and sending read data stream function data and action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware category.
In one embodiment, the fault codes include ECU fault codes belonging to a preset severity level; the third sending module is specifically configured to: and sending read data flow function data, online programming function data and action test function data for configuring the target diagnosis software to the user according to the ECU fault code belonging to the preset severity level.
In a third aspect, an embodiment of the present application provides a server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the vehicle diagnostic software configuration method when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and the computer program, when executed by a processor, implements the steps of the vehicle diagnostic software configuration method.
In a fifth aspect, the present application provides a computer program product, which when run on a diagnostic device, causes the diagnostic device to perform the steps of the above vehicle diagnostic software configuration method.
Compared with the prior art, the embodiment of the application has the advantages that: according to the method and the device, whether the target diagnosis software corresponding to the target vehicle type information in the diagnosis software obtaining instruction is obtained for the first time or not can be judged according to the diagnosis software obtaining instruction sent by the user, and different data used for configuring the target diagnosis software are respectively sent to the user during the first time obtaining and the non-first time obtaining. On one hand, the server automatically sends the data of the corresponding configuration diagnosis software, and the corresponding data does not need to be stored in the diagnosis equipment, so that the hardware storage requirement of the diagnosis equipment can be reduced; on the other hand, when the data are acquired for the first time and are not acquired for the first time, different data for configuring the target diagnosis software are automatically sent to the user, so that the flexible configuration of the diagnosis software can be realized, all the data for configuring the diagnosis software do not need to be sent to the user every time, and the storage requirement of the diagnosis equipment can be further reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in 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 embodiments of the present application, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is a schematic flow chart diagram illustrating a vehicle diagnostic software configuration method according to an embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating a specific step S104 of a vehicle diagnostic software configuration method according to an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram illustrating a vehicle diagnostic software configuration method according to a second embodiment of the present application;
FIG. 4 is a schematic structural diagram of a vehicle diagnostic software configuration apparatus provided in a third embodiment of the present application;
fig. 5 is a schematic structural diagram of a server according to a fourth 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 module 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 system modules, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
The vehicle diagnosis software configuration method provided by the embodiment of the application can be applied to a server, the server is in communication connection with a diagnosis device, the diagnosis device can be used for loading diagnosis software for diagnosing a vehicle, the diagnosis device can be an on-board device, a diagnosis instrument, a fault detection device, a mobile phone, a tablet computer, a notebook computer, a netbook, a Personal Digital Assistant (PDA) and other electronic devices, and the specific type of the diagnosis device is not limited at all in the embodiment of the application.
In order to explain the technical solution described in the present application, the following description is given by way of specific examples.
Example one
Referring to fig. 1, a schematic flow chart of a vehicle diagnostic software configuration method provided by an embodiment of the present application is shown, the method including:
step S101, receiving a diagnosis software obtaining instruction sent by a user, wherein the diagnosis software obtaining instruction comprises target vehicle type information and is used for obtaining target diagnosis software corresponding to the target vehicle type information.
Specifically, when a user of a diagnostic device needs diagnostic software to diagnose, a diagnostic software acquisition instruction can be sent, and corresponding target diagnostic software is acquired according to the diagnostic software acquisition instruction; the diagnostic software acquisition instruction comprises target vehicle type information of the vehicle to be diagnosed, and the target diagnostic software is diagnostic software corresponding to the target vehicle type information.
And step S102, judging whether the target diagnosis software is acquired for the first time.
Specifically, whether the target diagnostic software is primarily acquired is determined according to the history acquisition information of the target diagnostic software, so that different data for configuring the target diagnostic software are transmitted to the diagnostic device where the user is located when the primary acquisition and the non-primary acquisition are performed. The configuration data corresponding to the diagnostic software can be set into general data and functional data required by different vehicle types and configuration parameters corresponding to different vehicle types, and the general data, the functional data and the configuration parameters are stored in the server. The generic data may be some configuration file that is generic. The function data can be a configuration file required by the diagnostic software to execute the corresponding function, and the function data can enable the corresponding function of the diagnostic software to be diagnosed normally. Different general data and functional data for configuring the target diagnosis software and different configuration parameters corresponding to different vehicle types can be sent to the user during the primary acquisition and the non-primary acquisition.
And step S103, if yes, sending general data, appointed function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software to the user.
Specifically, a mapping relation between vehicle type configuration parameters and vehicle type information is established in advance and stored in a server, and general data and functional data associated with the vehicle type configuration parameters are stored in the server. If the target diagnosis software is judged to be obtained for the first time, vehicle type configuration parameters corresponding to the vehicle type can be obtained from the server according to the mapping relation, general data and designated function data which are stored correspondingly to the vehicle type configuration parameters are obtained from the server, and the designated function data can be fault code reading function data included in the function data. And enabling a user of the diagnosis equipment to configure the diagnosis software according to the general data, the specified function data and the configuration parameters corresponding to the target vehicle type information. Under the condition of obtaining the diagnosis software for the first time, when a user diagnoses the vehicle by using the diagnosis software, whether faults exist in each function diagnosis of the vehicle is checked by reading a fault code function, and the target diagnosis software can be generated and normally operated only by combining general data and configuration parameters corresponding to target vehicle type information. Further, when the user is to obtain the target diagnosis software corresponding to the target vehicle type information for the first time, the vehicle to be diagnosed does not necessarily have a fault and does not necessarily need to be further detected and repaired, so in this scenario, the server only issues the general data, the fault code reading function data and the configuration parameters corresponding to the target vehicle type information, which are pre-associated with the target diagnosis software, for rapidly configuring the target diagnosis software.
And step S104, if not, sending general data for configuring the target diagnosis software, first function data corresponding to a historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user.
Specifically, since the user does not initially acquire the diagnostic software of the target vehicle type, it is described that if the vehicle of the vehicle type has been diagnosed by using the diagnostic software in the past, the vehicle may be used for a period of time, and thus there is a high possibility of a failure in the past, and at the same time, there is a high possibility of a failure occurring in the past in the current vehicle, and therefore, when the user does not initially acquire the target diagnostic software, the past historical diagnostic result may be retrieved to configure the target diagnostic software accordingly.
According to the method and the device, whether the target diagnosis software corresponding to the target vehicle type information in the diagnosis software obtaining instruction is obtained for the first time or not can be judged according to the diagnosis software obtaining instruction sent by the user, and different data used for configuring the target diagnosis software are respectively sent to the user during the first time obtaining and the non-first time obtaining. On one hand, the server automatically sends the data of the corresponding configuration diagnosis software, and the corresponding data does not need to be stored in the diagnosis equipment, so that the hardware storage requirement of the diagnosis equipment can be reduced; on the other hand, when the data are acquired for the first time and are not acquired for the first time, different data for configuring the target diagnosis software are automatically sent to the user, so that the flexible configuration of the diagnosis software can be realized, all the data for configuring the diagnosis software do not need to be sent to the user every time, and the storage requirement of the diagnosis equipment can be further reduced.
In one embodiment, as shown in fig. 2, the sending of the first function data corresponding to the historical diagnosis result associated with the target vehicle type information to the user in step S104 includes steps S1041 to S1043:
step S1041, determining whether there is a fault in the historical diagnosis result.
Specifically, it may be determined whether a historical diagnosis result of a preset time period has a fault, for example, the preset time period may be set to be a week or a month in the recent period, and the historical diagnosis result may be a diagnosis result obtained by the server before the server obtains the target diagnosis software to diagnose the vehicle corresponding to the target vehicle type.
Step S1042, if yes, the first functional data is the functional data corresponding to the fault type.
Specifically, if the historical diagnosis result has a fault, and the current vehicle has a high possibility of having a fault which has occurred in the past, functional data corresponding to the fault type of the historical fault is issued to the user, and meanwhile, general data necessary for configuring the diagnosis software and configuration parameters corresponding to the target vehicle type information are combined for configuring the target diagnosis software. The types of different faults are associated with corresponding functional data in advance, so that faults exist in the historical diagnosis result, and the corresponding functional data can be obtained according to the types of the faults. For example, the functional data may be one or more of fault code reading functional data, fault code clearing functional data, data stream reading functional data, on-line programming functional data, and motion test functional data.
Step S1043, if not, the first function data is the designated function data.
Specifically, if no fault exists in the historical diagnosis result, the possibility that the current vehicle has no fault is high, and even if the fault exists, the fault is not known, so that in order to rapidly configure the target diagnosis software, the fault code reading function data for detecting whether the vehicle has the fault, the general data necessary for configuring the diagnosis software and the configuration parameters corresponding to the target vehicle type information are issued to the user. Therefore, when the diagnosis software is not acquired for the first time, the diagnosis software can be configured according to the historical diagnosis information of the diagnosis software. Therefore, the non-initial acquisition condition can be associated with the general data of the target diagnosis software, the first function data corresponding to the historical diagnosis result associated with the target vehicle type information and the configuration parameters corresponding to the target vehicle type information in advance. When the target diagnosis software is judged not to be acquired for the first time, vehicle type configuration parameters corresponding to the vehicle type can be acquired according to the mapping relation, and first functional data corresponding to the historical diagnosis result of the target diagnosis software and general data corresponding to the vehicle type configuration parameters are acquired. If the historical diagnosis result of the target diagnosis software has a fault, acquiring first function data corresponding to the historical diagnosis result of the target diagnosis software, wherein the first function data can be function data corresponding to the type of the fault; when the historical diagnosis result does not have a fault, acquiring first function data corresponding to the historical diagnosis result of the target diagnosis software may be fault code reading function data.
In this embodiment, sending the first functional data corresponding to the historical diagnosis result associated with the target vehicle type information to the user may be determining the first functional data according to whether a fault exists in the historical diagnosis result, where the fault exists in the historical diagnosis result, and the first functional data is functional data corresponding to a fault type; and the fault does not exist in the historical diagnosis result, the first functional data is the designated functional data, so that different data can be intelligently sent according to different historical diagnosis results, the flexible configuration of the diagnosis software is realized, only the data corresponding to the historical diagnosis result is needed to be sent, excessive data is not needed, and the storage requirement in the diagnosis equipment can be further reduced.
Example two
The present embodiment is further described in the first embodiment, and reference may be specifically made to the related description of the first embodiment where the same or similar to the first embodiment, and details are not described herein again. As shown in fig. 3, the vehicle diagnostic software configuration method includes:
step S101, receiving a diagnosis software obtaining instruction sent by a user, wherein the diagnosis software obtaining instruction comprises target vehicle type information and is used for obtaining target diagnosis software corresponding to the target vehicle type information.
And step S102, judging whether the target diagnosis software is acquired for the first time.
And step S103, if yes, sending general data, appointed function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software to the user.
And step S104, if not, sending general data for configuring the target diagnosis software, first function data corresponding to a historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user.
Specifically, the relevant description of step S101 to step S104 can refer to the relevant description of the first embodiment, and is not repeated herein.
Step S105, obtaining an execution result of the specified function data or the first function data in the using process of the target diagnosis software.
Specifically, the user automatically sends the next associated module data according to the function execution result of the current functional module of the diagnostic software in the process of using the diagnostic software. Therefore, the execution result of the specified function data or the first function data is acquired during the use of the target diagnosis software. If the specified function data is fault code reading function data, the currently executed function module is a fault code reading function, the obtained execution result is the execution result of the fault code reading function, and if the execution result of the fault code reading function can be a fault code read into an on-board electric control system such as an engine or a gearbox.
And step S106, sending second function data which needs to be configured in the next step of the target diagnosis software to the user according to the execution result.
For example, when the execution result is that a fault code of a certain system is read, then fault repair needs to be performed on the vehicle for the fault code, and when the repair is completed, the corresponding fault code is cleared. Then, the second function data that is sent to the user according to the execution result and needs to be configured for the next execution of the target diagnostic software in this embodiment may be function data related to performing fault recovery and fault clearing code function data. The functional data relating to the execution of the fault repair is functional data associated with the fault code. For example: when the first functional data is read data stream functional data, the execution result of the read data stream comprises an execution result of reading the engine data stream abnormity, and the execution result of reading the engine data stream abnormity is pre-associated with the engine revolution table action test functional data in the next step, so that when the execution result is reading the engine data stream abnormity, the second functional data which is sent to the user and needs to be configured in the next step by the target diagnosis software can be the engine revolution table action test functional data.
In one embodiment, the fault code comprises a fault code for a class of software; correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises: and sending fault code clearing function data for configuring the target diagnosis software to the user according to the fault codes of the software categories.
Specifically, the next step of the fault code of the software category may execute a fault code clearing function for clearing the fault code of the software category, and may associate the second function data that needs to be configured when the fault code of the software category is executed next step with the fault code clearing function data in advance, and if the fault code reading function reads the fault code of the software category during execution, the fault code clearing function data of the target diagnostic software is sent to the user, so as to further configure the fault code clearing function data for the user.
In one embodiment, the fault code comprises a fault code for a hardware class; correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises: and sending read data stream function data and action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware category.
Specifically, the data state of the vehicle component can be further detected in the next step by the fault code of the hardware type, the second function data which needs to be configured in the next step of executing the fault code of the hardware type can be associated to read data stream function data and action test function data in advance, the data can be used for further detecting and analyzing the vehicle data, and if the fault code reading function reads the fault code of the hardware type in the executing process, the read data stream function data and the action test function data of the target diagnosis software are sent to a user, so that the read data stream function data and the action test function data are further configured for the target diagnosis software.
In one embodiment, the fault codes include ECU fault codes belonging to a preset severity level; correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises: and sending read data flow function data, online programming function data and action test function data for configuring the target diagnosis software to the user according to the ECU fault code belonging to the preset severity level.
Specifically, because some ECU fault codes of a serious level need to detect specific data conditions of the vehicle ECU, the ECU fault codes of a preset serious level can be used for executing second function data to be configured in the next step in advance to associate with read data stream function data, online programming function data and action test function data, and can be used for further detecting and analyzing ECU faults of the vehicle.
According to the embodiment of the application, the execution result of the specified function data or the first function data in the use process of the target diagnosis software can be obtained; and sending second function data which needs to be configured and is executed by the target diagnosis software in the next step to the user according to the execution result. In the using process of the diagnostic software, second function data which needs to be configured in the next step of execution is sent according to the execution result of the currently executed function module, so that the correspondingly configured data is not required to be completely arranged in the diagnostic equipment, and the corresponding data is sent according to the using process of the diagnostic software, so that the occupation of the storage space of the diagnostic equipment can be reduced, and the hardware storage requirement in the diagnostic equipment can be reduced.
EXAMPLE III
Fig. 4 shows a block diagram of a configuration device of vehicle diagnostic software provided in an embodiment of the present application, corresponding to the configuration method of the vehicle diagnostic software described in the above embodiment, and only the relevant parts of the embodiment of the present application are shown for convenience of description. The vehicle diagnostic software configuration apparatus 400 includes:
an acquisition instruction receiving module 401, configured to receive a diagnostic software acquisition instruction sent by a user, where the diagnostic software acquisition instruction includes target vehicle type information and is used to acquire target diagnostic software corresponding to the target vehicle type information;
a determining module 402, configured to determine whether the target diagnostic software is acquired for the first time;
a first sending module 403, configured to send, to the user, general data, specified function data, and configuration parameters corresponding to the target vehicle type information, where the general data and the specified function data are used to configure the target diagnostic software when the target diagnostic software is obtained for the first time;
a second sending module 404, configured to send, to the user, general data for configuring the target diagnostic software, first function data corresponding to a historical diagnosis result associated with the target vehicle type information, and a configuration parameter corresponding to the target vehicle type information when the target diagnostic software is not obtained for the first time.
In one embodiment, the second sending module specifically includes:
the judging unit is used for judging whether the historical diagnosis result has a fault or not;
the first sending unit is used for judging that the historical diagnosis result has a fault and sending first function data corresponding to the historical diagnosis result related to the target vehicle type information to the user as function data corresponding to the fault type;
and the second sending unit is used for judging that the historical diagnosis result has no fault, and sending the first function data corresponding to the historical diagnosis result related to the target vehicle type information to the user as the specified function data.
In one embodiment, the vehicle diagnostic software configuration apparatus further comprises:
an execution result acquisition module, configured to acquire an execution result of the specified functional data or the first functional data in a use process of the target diagnostic software;
and the third sending module is used for sending second function data which needs to be configured in the next step of the target diagnosis software to the user according to the execution result.
In one embodiment, the specified functional data or the first functional data comprises read fault code functional data; the execution result comprises reading a fault code;
correspondingly, the third sending module is specifically configured to: and sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step according to the fault code.
In one embodiment, the fault code comprises a fault code for a class of software; the third sending module is specifically configured to: and sending fault code clearing function data for configuring the target diagnosis software to the user according to the fault codes of the software categories.
In one embodiment, the fault code comprises a fault code for a hardware class; the third sending module is specifically configured to: and sending read data stream function data and action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware category.
In one embodiment, the fault codes include ECU fault codes belonging to a preset severity level; the third sending module is specifically configured to: and sending read data flow function data, online programming function data and action test function data for configuring the target diagnosis software to the user according to the ECU fault code belonging to the preset severity level.
According to the method and the device, whether the target diagnosis software corresponding to the target vehicle type information in the diagnosis software obtaining instruction is obtained for the first time or not can be judged according to the diagnosis software obtaining instruction sent by the user, and different data used for configuring the target diagnosis software are respectively sent to the user during the first time obtaining and the non-first time obtaining. On one hand, the server automatically sends the data of the corresponding configuration diagnosis software, and the corresponding data does not need to be stored in the diagnosis equipment, so that the hardware storage requirement of the diagnosis equipment can be reduced; on the other hand, when the data are acquired for the first time and are not acquired for the first time, different data for configuring the target diagnosis software are automatically sent to the user, so that the flexible configuration of the diagnosis software can be realized, all the data for configuring the diagnosis software do not need to be sent to the user every time, and the storage requirement of the diagnosis equipment can be further reduced.
Example four
Fig. 5 is a schematic structural diagram of a diagnostic apparatus provided in an embodiment of the present application. The server 500 includes: a processor 501, a memory 502 and a computer program 503 stored in the memory 502 and executable on the processor 501. The steps in the vehicle diagnostic software configuration method embodiment described above are implemented when the processor 501 executes the computer program 503 described above.
Illustratively, the computer program 503 may be divided into one or more units/modules, which are stored in the memory 502 and executed by the processor 501 to complete the present application. The one or more units/modules may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 503 in the server 500. For example, the computer program 503 may be divided into an obtaining instruction receiving module, a determining module, a first sending module, a second sending module, and the like, and specific functions of the modules are described in the foregoing embodiments, and are not described herein again.
The server 500 may include, but is not limited to, a processor 501 and a memory 502. Those skilled in the art will appreciate that fig. 5 is merely an example of a server 500 and is not intended to limit server 500 and may include more or fewer components than those shown, or some components in combination, or different components, e.g., server 500 may also include input-output devices, network access devices, buses, etc.
The Processor 501 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 502 may be an internal storage unit of the server 500, such as a hard disk or a memory of the server 500. The memory 502 may also include both an internal storage unit and an external storage device of the server 500. The memory 502 is used to store the computer programs and other programs and data required by the server 500. The memory 502 described above may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned 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-mentioned 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 maintenance case generation device 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 will 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 computer 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 apparatus 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, a plurality of units or components may be combined or integrated into another system module, 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 embodiments of the present application.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
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 may be implemented by a computer program, which may be stored in a computer readable storage medium and used by a processor to implement the steps of the embodiments of the methods described above. 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 medium may include: any entity or device capable of carrying the above-mentioned computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer 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 medium described above may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media excludes electrical carrier signals and telecommunications signals in accordance with legislation and patent practice. The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting 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. A vehicle diagnosis software configuration method is applied to a server and comprises the following steps:
receiving a diagnosis software acquisition instruction sent by a user, wherein the diagnosis software acquisition instruction comprises target vehicle type information and is used for acquiring target diagnosis software corresponding to the target vehicle type information;
judging whether the target diagnosis software is obtained for the first time;
if yes, sending general data, designated function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software to the user;
and if not, sending general data for configuring the target diagnosis software, first functional data corresponding to a historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user.
2. The vehicle diagnostic software configuration method according to claim 1, wherein the sending of the first function data corresponding to the historical diagnosis result associated with the target vehicle type information to the user includes:
judging whether the historical diagnosis result has a fault or not;
if so, the first functional data is functional data corresponding to the fault type;
and if not, the first functional data is the specified functional data.
3. The vehicle diagnostic software configuration method according to claim 1 or 2, characterized in that the method further comprises:
acquiring the execution result of the specified function data or the first function data in the use process of the target diagnosis software;
and sending second function data which needs to be configured and is executed by the target diagnosis software in the next step to the user according to the execution result.
4. The configuration method according to claim 3, wherein the specified function data or the first function data includes read fault code function data;
the execution result comprises reading a fault code;
correspondingly, the sending, to the user, second function data that needs to be configured for next execution of the target diagnostic software according to the execution result includes:
and sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step according to the fault code.
5. The configuration method of claim 4, wherein the fault code comprises a fault code for a class of software;
correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises:
and sending fault code clearing function data for configuring the target diagnosis software to the user according to the fault codes of the software categories.
6. The configuration method of claim 4, wherein the fault code comprises a fault code for a hardware class;
correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises:
and sending read data stream function data and action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware category.
7. The configuration method according to claim 4, wherein the fault code includes an ECU fault code belonging to a preset severity level;
correspondingly, according to the fault code, sending second function data which needs to be configured and is executed by the target diagnosis software associated with the fault code to a user in the next step, wherein the second function data comprises:
and sending read data flow function data, online programming function data and action test function data for configuring the target diagnosis software to the user according to the ECU fault code belonging to the preset severity level.
8. A vehicle diagnostic software configuration apparatus, comprising:
the system comprises an acquisition instruction receiving module, a diagnosis software acquisition module and a diagnosis software analysis module, wherein the acquisition instruction receiving module is used for receiving a diagnosis software acquisition instruction sent by a user, the diagnosis software acquisition instruction comprises target vehicle type information and is used for acquiring target diagnosis software corresponding to the target vehicle type information;
the judging module is used for judging whether the target diagnosis software is obtained for the first time;
the first sending module is used for sending general data, designated function data and configuration parameters corresponding to the target vehicle type information to the user when the target diagnosis software is obtained for the first time;
and the second sending module is used for sending general data for configuring the target diagnosis software, first functional data corresponding to a historical diagnosis result associated with the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user when the target diagnosis software is not obtained for the first time.
9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111078894.2A CN113778557A (en) | 2021-09-15 | 2021-09-15 | Vehicle diagnosis software configuration method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111078894.2A CN113778557A (en) | 2021-09-15 | 2021-09-15 | Vehicle diagnosis software configuration method, device, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113778557A true CN113778557A (en) | 2021-12-10 |
Family
ID=78843922
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111078894.2A Pending CN113778557A (en) | 2021-09-15 | 2021-09-15 | Vehicle diagnosis software configuration method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778557A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114936054A (en) * | 2022-04-11 | 2022-08-23 | 中车青岛四方机车车辆股份有限公司 | Method and device for generating debugging process file of vehicle and rail vehicle |
| CN114995862A (en) * | 2022-08-03 | 2022-09-02 | 深圳市星卡软件技术开发有限公司 | Method, device and system for calling diagnosis module |
| CN116300780A (en) * | 2022-09-07 | 2023-06-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
| CN116700808A (en) * | 2023-06-26 | 2023-09-05 | 中国第一汽车股份有限公司 | EOL configuration code processing method, system, electronic equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102007059524A1 (en) * | 2007-12-11 | 2009-06-25 | Continental Automotive Gmbh | Method for generating operating software on a control unit for a motor vehicle and control unit |
| CN107544461A (en) * | 2017-09-07 | 2018-01-05 | 深圳市元征科技股份有限公司 | A kind of method and apparatus for configuring vehicle diagnostics parameter |
| CN109800040A (en) * | 2018-12-21 | 2019-05-24 | 深圳市元征科技股份有限公司 | A kind of diagnostic program interface display method, device and vehicle diagnostic equipment |
| CN111474921A (en) * | 2020-04-29 | 2020-07-31 | 深圳市元征科技股份有限公司 | Configuration method of automobile diagnosis software and related equipment |
| CN111708584A (en) * | 2020-05-29 | 2020-09-25 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method and device, diagnosis equipment and storage medium |
| US20200331483A1 (en) * | 2017-12-27 | 2020-10-22 | Scania Cv Ab | Method and control unit for facilitating diagnosis for a vehicle |
| CN112055066A (en) * | 2020-08-28 | 2020-12-08 | 深圳市元征科技股份有限公司 | Communication method, apparatus, diagnostic device, and computer-readable storage medium |
| CN112102103A (en) * | 2020-11-02 | 2020-12-18 | 广州汽车集团股份有限公司 | Vehicle whole vehicle offline configuration verification method |
| CN112446635A (en) * | 2020-12-08 | 2021-03-05 | 东风柳州汽车有限公司 | Vehicle data configuration system and method |
| CN112526971A (en) * | 2020-11-30 | 2021-03-19 | 湖北亿咖通科技有限公司 | Vehicle configuration system, vehicle and production device |
| CN113094087A (en) * | 2021-04-14 | 2021-07-09 | 深圳市元征科技股份有限公司 | Software configuration method, electronic device and storage medium |
| US20210224148A1 (en) * | 2018-08-28 | 2021-07-22 | Launch Tech Co., Ltd. | Method and system of using vehicle diagnosis equipment, and vehicle diagnosis equipment |
-
2021
- 2021-09-15 CN CN202111078894.2A patent/CN113778557A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102007059524A1 (en) * | 2007-12-11 | 2009-06-25 | Continental Automotive Gmbh | Method for generating operating software on a control unit for a motor vehicle and control unit |
| CN107544461A (en) * | 2017-09-07 | 2018-01-05 | 深圳市元征科技股份有限公司 | A kind of method and apparatus for configuring vehicle diagnostics parameter |
| US20200331483A1 (en) * | 2017-12-27 | 2020-10-22 | Scania Cv Ab | Method and control unit for facilitating diagnosis for a vehicle |
| US20210224148A1 (en) * | 2018-08-28 | 2021-07-22 | Launch Tech Co., Ltd. | Method and system of using vehicle diagnosis equipment, and vehicle diagnosis equipment |
| CN109800040A (en) * | 2018-12-21 | 2019-05-24 | 深圳市元征科技股份有限公司 | A kind of diagnostic program interface display method, device and vehicle diagnostic equipment |
| CN111474921A (en) * | 2020-04-29 | 2020-07-31 | 深圳市元征科技股份有限公司 | Configuration method of automobile diagnosis software and related equipment |
| CN111708584A (en) * | 2020-05-29 | 2020-09-25 | 深圳市元征科技股份有限公司 | Vehicle diagnosis method and device, diagnosis equipment and storage medium |
| CN112055066A (en) * | 2020-08-28 | 2020-12-08 | 深圳市元征科技股份有限公司 | Communication method, apparatus, diagnostic device, and computer-readable storage medium |
| CN112102103A (en) * | 2020-11-02 | 2020-12-18 | 广州汽车集团股份有限公司 | Vehicle whole vehicle offline configuration verification method |
| CN112526971A (en) * | 2020-11-30 | 2021-03-19 | 湖北亿咖通科技有限公司 | Vehicle configuration system, vehicle and production device |
| CN112446635A (en) * | 2020-12-08 | 2021-03-05 | 东风柳州汽车有限公司 | Vehicle data configuration system and method |
| CN113094087A (en) * | 2021-04-14 | 2021-07-09 | 深圳市元征科技股份有限公司 | Software configuration method, electronic device and storage medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114936054A (en) * | 2022-04-11 | 2022-08-23 | 中车青岛四方机车车辆股份有限公司 | Method and device for generating debugging process file of vehicle and rail vehicle |
| CN114995862A (en) * | 2022-08-03 | 2022-09-02 | 深圳市星卡软件技术开发有限公司 | Method, device and system for calling diagnosis module |
| CN114995862B (en) * | 2022-08-03 | 2022-11-01 | 深圳市星卡软件技术开发有限公司 | Method, device and system for calling diagnosis module |
| CN116300780A (en) * | 2022-09-07 | 2023-06-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
| CN116300780B (en) * | 2022-09-07 | 2024-01-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
| CN116700808A (en) * | 2023-06-26 | 2023-09-05 | 中国第一汽车股份有限公司 | EOL configuration code processing method, system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113778557A (en) | Vehicle diagnosis software configuration method, device, server and storage medium | |
| CN108227675B (en) | Vehicle diagnosis method, device, terminal and computer-readable storage medium | |
| CN108563214B (en) | Vehicle diagnosis method, device and equipment | |
| CN112965871A (en) | Vehicle fault prompt information acquisition method and device and storage medium | |
| EP2031800B1 (en) | Method, system and apparatus of fault location for communicaion apparatus | |
| KR20140116492A (en) | System and method for providing diagnostic fault information | |
| CN110213258B (en) | Abnormity monitoring method and device for vehicle CAN bus and computer equipment | |
| CN112326070B (en) | Temperature sensor fault diagnosis method and device, electronic equipment and storage medium | |
| WO2020015471A1 (en) | Automotive diagnostic method and device, and storage medium | |
| CN109190776B (en) | Method and device for rechecking automobile fault, terminal equipment and storage medium | |
| CN111708584A (en) | Vehicle diagnosis method and device, diagnosis equipment and storage medium | |
| CN114490161A (en) | Fault diagnosis method and device, vehicle and storage medium | |
| CN113110994A (en) | Vehicle diagnosis method and device, electronic equipment and storage medium | |
| KR101209069B1 (en) | Debuggging Apparatus For CAN Communication Diagnosis Device | |
| CN111858354A (en) | Method and device for automatically generating test report, storage medium and electronic equipment | |
| CN117333424A (en) | Wafer defect evaluation method, device, memory chip and readable storage medium | |
| JP2007322377A (en) | On-board failure diagnosis apparatus and method for testing same | |
| CN114995792B (en) | Modularized development method, device, medium and electronic device of automobile diagnosis device | |
| CN112034820A (en) | Cloud-based hardware-in-loop system testing method and system and storage medium | |
| CN111654405A (en) | Method, device, equipment and storage medium for fault node of communication link | |
| CN111553491A (en) | Vehicle maintenance record generation method and related device | |
| CN112306038B (en) | Detection method, detection device and diagnosis equipment | |
| CN115185252A (en) | Remote diagnosis method and device based on automobile fault lamp | |
| CN114356769A (en) | Software learning method, device, equipment and storage medium | |
| CN114625106A (en) | Vehicle diagnosis method and device, electronic equipment 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 |