CN113778557B - 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
- CN113778557B CN113778557B CN202111078894.2A CN202111078894A CN113778557B CN 113778557 B CN113778557 B CN 113778557B CN 202111078894 A CN202111078894 A CN 202111078894A CN 113778557 B CN113778557 B CN 113778557B
- Authority
- CN
- China
- Prior art keywords
- target
- software
- function data
- data
- diagnosis
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000003745 diagnosis Methods 0.000 claims abstract description 65
- 230000006870 function Effects 0.000 claims description 185
- 238000004590 computer program Methods 0.000 claims description 23
- 230000009471 action Effects 0.000 claims description 18
- 238000012360 testing method Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 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
- 230000008439 repair process Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 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
- 238000006467 substitution reaction Methods 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
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 acquired for the first time; if yes, universal data, appointed function data and configuration parameters corresponding to target vehicle type information for configuring target diagnosis software are sent to a user; if not, the general data for configuring the target diagnosis software, the first function data corresponding to the historical diagnosis result related to the target vehicle type information and the configuration parameters corresponding to the target vehicle type information are sent to the user. Different data for configuring the target diagnostic software can be automatically sent to the user during primary acquisition and non-primary acquisition, and all data for configuring the diagnostic software are not required to be sent to the user each time, so that the storage requirement on diagnostic equipment is reduced.
Description
Technical Field
The application belongs to the technical field of vehicles, and particularly relates to a vehicle diagnosis software configuration method, a device, diagnosis equipment and a storage medium.
Background
With the continuous and rapid development of society, automobiles become important transportation means for people to travel, and when the automobiles fail, vehicle diagnosis can be performed through diagnostic software.
Different diagnostic software can be used for diagnosing different types of vehicles, and as the functions of the vehicles are increased, configuration data related to the diagnostic software are increased, and requirements on hardware storage resources in diagnostic equipment for installing the diagnostic software are also increased.
Disclosure of Invention
The embodiment of the application provides a vehicle diagnosis software configuration method, a device, diagnosis equipment and a storage medium, which aim to solve the problem that the hardware storage resource requirement in the existing diagnosis equipment for installing diagnosis 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 acquired for the first time;
if yes, universal data, appointed function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software are sent to the user;
if not, the general data for configuring the target diagnosis software, the first function data corresponding to the historical diagnosis result related to the target vehicle type information and the configuration parameters corresponding to the target vehicle type information are sent 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 faults or not;
if yes, the first functional data are functional data corresponding to the fault type;
if not, the first function data is the appointed function data.
In one embodiment, the method further comprises:
acquiring an execution result of the specified functional data or the first functional data of the target diagnostic software in the using process;
And according to the execution result, sending second function data which needs to be configured for the next execution of the target diagnosis software to the user.
In one embodiment, the specified function data or the first function data comprises read trouble code function data;
The execution result comprises the step of reading a fault code;
Correspondingly, the sending, according to the execution result, second function data that needs to be configured for the next execution of the target diagnostic software to the user includes:
And according to the fault code, sending second function data which need to be configured for the next execution of the target diagnosis software associated with the fault code to a user.
In one embodiment, the fault code comprises a software class fault code;
correspondingly, according to the fault code, sending second function data which needs to be configured for the next execution of the target diagnosis software associated with the fault code to a user, 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 types.
In one embodiment, the fault code comprises a hardware class fault code;
correspondingly, according to the fault code, sending second function data which needs to be configured for the next execution of the target diagnosis software associated with the fault code to a user, wherein the second function data comprises:
And sending the read data stream function data and the action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware class.
In one embodiment, the fault code comprises 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 for the next execution of the target diagnosis software associated with the fault code to a user, wherein the second function data comprises:
And sending the read data stream function data, the online programming function data and the 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 control module, wherein the acquisition instruction receiving module is used for receiving a diagnosis software acquisition instruction sent by a user, and 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 acquired for the first time;
the first sending module is used for 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 when the target diagnosis software is acquired for the first time;
And the second sending module is used for sending general data for configuring the target diagnosis software, first function data corresponding to the historical diagnosis result related to 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 acquired for the first time.
In one embodiment, the second sending module specifically includes:
a judging unit for judging whether the history diagnosis result has a fault;
A first sending unit, configured to determine that the historical diagnosis result has a fault, and send, to the user, first function data corresponding to the historical diagnosis result associated with the target vehicle type information to be 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 first function data corresponding to the historical diagnosis result related to the target vehicle type information to the user as the appointed function data.
In one embodiment, the vehicle diagnostic software configuration apparatus further includes:
The execution result acquisition module is used for acquiring the execution result of the specified function data or the first function data in the using process of the target diagnosis software;
and the third sending module is used for sending second function data which needs to be configured for the next execution of the target diagnosis software to the user according to the execution result.
In one embodiment, the specified function data or the first function data comprises read trouble code function data; the execution result comprises the step of reading a fault code;
Correspondingly, the third sending module is specifically configured to: and according to the fault code, sending second function data which need to be configured for the next execution of the target diagnosis software associated with the fault code to a user.
In one embodiment, the fault code comprises a software class fault code; 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 types.
In one embodiment, the fault code comprises a hardware class fault code; the third sending module is specifically configured to: and sending the read data stream function data and the action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware class.
In one embodiment, the fault code comprises an ECU fault code belonging to a preset severity level; the third sending module is specifically configured to: and sending the read data stream function data, the online programming function data and the 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, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the vehicle diagnostic software configuration method described above when the processor executes the computer program.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the vehicle diagnostic software configuration method described above.
In a fifth aspect, embodiments of the present application provide a computer program product for causing a diagnostic device to perform the steps of the above-described vehicle diagnostic software configuration method when the computer program product is run on the diagnostic device.
Compared with the prior art, the embodiment of the application has the beneficial effects that: according to the embodiment of the application, whether the target diagnostic software corresponding to the target vehicle type information is acquired for the first time can be judged according to the diagnostic software acquisition instruction sent by the user, and different data for configuring the target diagnostic software are respectively sent to the user during the first acquisition and the non-first acquisition. On the one hand, the server automatically transmits the data corresponding to the configuration diagnosis software, and the corresponding data is not required 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 first acquisition and the non-first acquisition are performed, different data for configuring the target diagnostic software are automatically sent to the user, so that flexible configuration of the diagnostic software can be realized, all the data for configuring the diagnostic software are not required to be sent to the user every time, and the storage requirement of the diagnostic equipment can be further reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced 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 these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a vehicle diagnostic software configuration method according to an embodiment of the present application;
FIG. 2 is a flowchart of a vehicle diagnostic software configuration method step S104 according to an embodiment of the present application;
FIG. 3 is a flowchart of 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 device according to 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 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 diagnosis equipment, the diagnosis equipment can be used for loading diagnosis software for diagnosing a vehicle, the diagnosis equipment can be vehicle-mounted equipment, a diagnosis instrument, fault detection equipment, a mobile phone, a tablet computer, a notebook computer, a netbook, a Personal Digital Assistant (PDA) and other electronic equipment, and the embodiment of the application does not limit the specific type of the diagnosis equipment.
In order to illustrate the technical scheme of the application, the following description is made by specific examples.
Example 1
Referring to fig. 1, a schematic flowchart of a vehicle diagnostic software configuration method provided by an embodiment of the present application is shown, where the method includes:
Step S101, 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.
Specifically, when a user at the diagnosis equipment end needs diagnosis software to perform diagnosis, a diagnosis software acquisition instruction can be sent, and corresponding target diagnosis software is acquired according to the diagnosis software acquisition instruction; the diagnosis software acquisition instruction comprises target vehicle type information of the vehicle to be diagnosed, and the target diagnosis software is diagnosis software corresponding to the target vehicle type information.
Step S102, judging whether the target diagnosis software is acquired for the first time.
Specifically, whether the target diagnostic software is first acquired is determined according to the historical acquisition information of the target diagnostic software, so that different data for configuring the target diagnostic software is transmitted to the diagnostic device where the user is located at the time of the first acquisition and the time of the non-first acquisition. 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 and the functional data and the configuration parameters corresponding to different vehicle types are stored in a server. The generic data may be some configuration files that are generic. The function data may be a configuration file required by the diagnostic software to execute the corresponding function, and the function data may enable the diagnostic software to perform the diagnosis normally for the corresponding function. Different general data and functional data for configuring target diagnostic software and configuration parameters corresponding to different vehicle types can be sent to a user during primary acquisition and non-primary acquisition.
And step S103, if yes, transmitting 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 the vehicle type configuration parameters and the vehicle type information is pre-established and stored in a server, and general data and function data associated with the vehicle type configuration parameters are stored in the server. If the target diagnosis software is judged to be acquired for the first time, vehicle type configuration parameters corresponding to the vehicle type can be acquired from a server according to the mapping relation, and general data and appointed function data which are stored corresponding to the vehicle type configuration parameters are acquired from the server, wherein the appointed function data can be fault code reading function data included in the function data. The user of the diagnosis equipment can configure the diagnosis software according to the general data, the designated function data and the configuration parameters corresponding to the target vehicle type information. Under the condition that the diagnosis software is acquired for the first time, a user needs to check whether the diagnosis of each function of the vehicle is faulty through a fault code reading function when diagnosing the vehicle by using the diagnosis software, and needs to combine general data and configuration parameters corresponding to the target vehicle type information to generate the target diagnosis software, so that the target diagnosis software runs normally. Further, when the user is the target diagnosis software corresponding to the target vehicle type information, the vehicle to be diagnosed does not have a fault and does not need to be further detected and repaired, so that in the scene, the method only transmits the general data, the fault code reading function data and the configuration parameters corresponding to the target vehicle type information of the pre-associated target diagnosis software through the server, and the method is used for rapidly configuring the target diagnosis software.
Step S104, if not, the general data for configuring the target diagnosis software, the first function data corresponding to the historical diagnosis result related to the target vehicle type information and the configuration parameters corresponding to the target vehicle type information are sent to the user.
Specifically, since the user does not first acquire the diagnostic software of the target vehicle model, and the vehicle of the vehicle model is diagnosed by using the diagnostic software in the past, the vehicle may be used for a period of time, and the possibility of a fault existing in the past is high, and the possibility of a fault existing in the past in the current vehicle is also high, when the user does not first acquire the target diagnostic software, the past historical diagnostic result can be adjusted to correspondingly configure the target diagnostic software.
According to the embodiment of the application, whether the target diagnostic software corresponding to the target vehicle type information is acquired for the first time can be judged according to the diagnostic software acquisition instruction sent by the user, and different data for configuring the target diagnostic software are respectively sent to the user during the first acquisition and the non-first acquisition. On the one hand, the server automatically transmits the data corresponding to the configuration diagnosis software, and the corresponding data is not required 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 first acquisition and the non-first acquisition are performed, different data for configuring the target diagnostic software are automatically sent to the user, so that flexible configuration of the diagnostic software can be realized, all the data for configuring the diagnostic software are not required to be sent to the user every time, and the storage requirement of the diagnostic equipment can be further reduced.
In one embodiment, as shown in fig. 2, the step S104 of transmitting the first function data corresponding to the history diagnosis result associated with the target vehicle type information to the user includes steps S1041 to S1043:
Step S1041, determining whether the history diagnosis result has a fault.
Specifically, it may be determined whether the historical diagnosis result in the preset time period has a fault, for example, the preset time period may be set to be one week recently or one month recently, and may be set according to practical applications, which is not limited to this, and the historical diagnosis result may be a diagnosis result obtained by the server before obtaining the diagnosis software for diagnosing the vehicle corresponding to the target vehicle type.
In step S1042, if yes, the first function data is the function data corresponding to the fault type.
Specifically, if the historical diagnosis result has a fault, the possibility that the current vehicle has a fault which has occurred in the past is high, 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 categories 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 acquired according to the categories of the faults. The function data may be one or more of read fault code function data, clear fault code function data, read data stream function data, on-line programming function data, and action test function data, etc.
Step S1043, if not, the first function data is the specified function data.
Specifically, if the historical diagnosis result does not have a fault, the possibility that the current vehicle does not have a fault is high, and even if the current vehicle has a fault, the fault is unknown, so that in order to rapidly configure the target diagnosis software, the application issues fault code reading function data for detecting whether the vehicle has a fault, general data necessary for configuring the diagnosis software and configuration parameters corresponding to the target vehicle type information to a user. Thus, when the diagnostic software is not acquired for the first time, the diagnostic software can be configured according to the historical diagnostic information of the diagnostic software. Therefore, the general data of the target diagnosis software, the first function data corresponding to the historical diagnosis result related to the target vehicle type information and the configuration parameters corresponding to the target vehicle type information can be related in advance to the condition of non-initial acquisition. 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 function 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 faults, acquiring the first function data corresponding to the historical diagnosis result of the target diagnosis software can be the function data corresponding to the type of the faults; when the historical diagnosis result does not have a fault, acquiring the first function data corresponding to the historical diagnosis result of the target diagnosis software may be reading fault code function data.
In this embodiment, the sending of the first function data corresponding to the history diagnosis result associated with the target vehicle type information to the user may be determining the first function data according to whether there is a fault in the history diagnosis result, where the fault exists in the history diagnosis result, and the first function data is the function data corresponding to the fault type; the first functional data are designated functional data when the historical diagnosis result does not have faults, so that different data can be intelligently transmitted according to different historical diagnosis results, flexible configuration of diagnosis software is realized, and only data corresponding to the historical diagnosis result are transmitted without excessive data, so that the storage requirement in diagnosis equipment can be further reduced.
Example two
The present embodiment is further described in the first embodiment, and the same or similar parts as those of the first embodiment can be referred to in the description of the first embodiment, which is not repeated here. As shown in fig. 3, the vehicle diagnostic software configuration method includes:
Step S101, 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.
Step S102, judging whether the target diagnosis software is acquired for the first time.
And step S103, if yes, transmitting general data, appointed function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software to the user.
Step S104, if not, the general data for configuring the target diagnosis software, the first function data corresponding to the historical diagnosis result related to the target vehicle type information and the configuration parameters corresponding to the target vehicle type information are sent to the user.
Specifically, the descriptions of steps S101 to S104 can be referred to the descriptions of the first embodiment, and are not repeated here.
Step S105, acquiring an execution result of the specified function data or the first function data in the use process of the target diagnostic software.
Specifically, the user automatically sends the data of the next associated module according to the function execution result of the current function module of the diagnostic software in the process of using the diagnostic software. And therefore, in the using process of the target diagnosis software, acquiring the execution result of the specified function data or the first function data. 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 an 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-vehicle electronic control system such as an engine or a gearbox.
And step S106, according to the execution result, sending second function data which needs to be configured for the next execution of the target diagnosis software to the user.
For example, when the execution result is that a fault code of a certain system is read, then the fault code needs to be repaired for the vehicle, and when the repair is completed, the corresponding fault code is cleared. Then, the second function data that needs to be configured for the next execution of the target diagnostic software and sent to the user according to the execution result may be function data related to performing fault repair and fault clearing code function data. Here, the functional data related to the fault repair is functional data related to the fault code. For example: when the first function data is the read data flow function data, the execution result of the read data flow comprises the execution result of reading the abnormal engine data flow, and the execution result of the abnormal engine data flow is next pre-related to the engine revolution table action test function data, so when the execution result is the abnormal engine data flow, the second function data which is required to be configured for next execution of the target diagnosis software is sent to the user and can be the engine revolution table action test function data.
In one embodiment, the fault code comprises a software class fault code; correspondingly, according to the fault code, sending second function data which needs to be configured for the next execution of the target diagnosis software associated with the fault code to a user, 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 types.
Specifically, since the fault code clearing function of the software class can be executed in the next step to clear the fault code of the software class, the second function data required to be configured in the next step of executing the fault code of the software class can be associated in advance to be the fault code clearing function data, and if the fault code reading function reads the fault code of the software class in the executing process, the fault code clearing function data of the target diagnosis software is sent to the user, so that the fault code clearing function data is further configured for the user.
In one embodiment, the fault code comprises a hardware class fault code; correspondingly, according to the fault code, sending second function data which needs to be configured for the next execution of the target diagnosis software associated with the fault code to a user, wherein the second function data comprises: and sending the read data stream function data and the action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware class.
Specifically, since the fault code of the hardware type can further detect the data state of the vehicle component in the next step, the second function data required to be configured in the next step of executing the fault code of the hardware type can be associated with the read data stream function data and the action test function data in advance, and can be used for further detecting and analyzing the data of the vehicle, and if the fault code of the hardware type is read in the executing process of the read fault code function, the read data stream function data and the action test function data of the target diagnostic software are sent to the user, so that the read data stream function data and the action test function data are further configured for the target diagnostic software.
In one embodiment, the fault code comprises 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 for the next execution of the target diagnosis software associated with the fault code to a user, wherein the second function data comprises: and sending the read data stream function data, the online programming function data and the 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 serious-level ECU fault codes need to detect specific data conditions of the vehicle ECU, the second functional data to be configured, which is associated with the second functional data to be configured, can be pre-executed in advance by the ECU fault codes with preset severity levels, and can be used for further detecting and analyzing ECU faults of the vehicle, and if the ECU fault codes with preset severity levels are read in the execution process of the ECU fault code reading function, the read data stream functional data, the online programming functional data and the action test functional data of the target diagnostic software are sent to a user, so that the read data stream functional data, the online programming functional data and the action test functional data are further configured for the target diagnostic software.
According to the embodiment of the application, the execution result of the specified functional data or the first functional data of the target diagnosis software in the using process can be obtained; and according to the execution result, sending second function data which needs to be configured for the next execution of the target diagnosis software to the user. In the use process of the diagnostic software, the second functional data which needs to be configured for the next execution is sent according to the execution result of the currently executed functional module, so that the corresponding configuration data is not required to be completely arranged inside the diagnostic equipment, and the corresponding data is sent according to the use process of the diagnostic software, thereby reducing the occupation of the storage space of the diagnostic equipment and reducing the hardware storage requirement in the diagnostic equipment.
Example III
Corresponding to the vehicle diagnostic software configuration method described in the above embodiments, fig. 4 shows a block diagram of the vehicle diagnostic software configuration device provided in the embodiment of the present application, and for convenience of explanation, only the portions related to the embodiment of the present application are shown. The vehicle diagnostic software configuration apparatus 400 includes:
The acquisition instruction receiving module 401 is 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 configured to acquire target diagnostic software corresponding to the target vehicle type information;
a judging module 402, configured to judge whether the target diagnostic software is acquired for the first time;
A first sending module 403, configured to send, to the user, general data for configuring the target diagnostic software, specified function data, and configuration parameters corresponding to the target vehicle type information when the target diagnostic software is acquired for the first time;
And the second sending module 404 is configured to send, to the user, general data for configuring the target diagnostic software, first function data corresponding to a historical diagnostic result associated with the target vehicle type information, and configuration parameters corresponding to the target vehicle type information, when the target diagnostic software is acquired for a non-primary time.
In one embodiment, the second sending module specifically includes:
a judging unit for judging whether the history diagnosis result has a fault;
A first sending unit, configured to determine that the historical diagnosis result has a fault, and send, to the user, first function data corresponding to the historical diagnosis result associated with the target vehicle type information to be 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 first function data corresponding to the historical diagnosis result related to the target vehicle type information to the user as the appointed function data.
In one embodiment, the vehicle diagnostic software configuration apparatus further includes:
The execution result acquisition module is used for acquiring the execution result of the specified function data or the first function data in the using process of the target diagnosis software;
and the third sending module is used for sending second function data which needs to be configured for the next execution of the target diagnosis software to the user according to the execution result.
In one embodiment, the specified function data or the first function data comprises read trouble code function data; the execution result comprises the step of reading a fault code;
Correspondingly, the third sending module is specifically configured to: and according to the fault code, sending second function data which need to be configured for the next execution of the target diagnosis software associated with the fault code to a user.
In one embodiment, the fault code comprises a software class fault code; 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 types.
In one embodiment, the fault code comprises a hardware class fault code; the third sending module is specifically configured to: and sending the read data stream function data and the action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware class.
In one embodiment, the fault code comprises an ECU fault code belonging to a preset severity level; the third sending module is specifically configured to: and sending the read data stream function data, the online programming function data and the 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 embodiment of the application, whether the target diagnostic software corresponding to the target vehicle type information is acquired for the first time can be judged according to the diagnostic software acquisition instruction sent by the user, and different data for configuring the target diagnostic software are respectively sent to the user during the first acquisition and the non-first acquisition. On the one hand, the server automatically transmits the data corresponding to the configuration diagnosis software, and the corresponding data is not required 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 first acquisition and the non-first acquisition are performed, different data for configuring the target diagnostic software are automatically sent to the user, so that flexible configuration of the diagnostic software can be realized, all the data for configuring the diagnostic software are not required to be sent to the user every time, and the storage requirement of the diagnostic equipment can be further reduced.
Example IV
Fig. 5 is a schematic structural diagram of a diagnostic device according to 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 processor 501, when executing the computer program 503, implements the steps of the vehicle diagnostic software configuration method embodiment described above.
Illustratively, the computer program 503 may be split 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 a specific function, which instruction segments describe the execution of the computer program 503 in the server 500. For example, the computer program 503 may be divided into an acquisition instruction receiving module, a judging module, a first sending module, a second sending module, and the like, where specific functions of each module are described in the above embodiments, and are not described herein.
The server 500 may include, but is not limited to, a processor 501, a memory 502. It will be appreciated by those skilled in the art that fig. 5 is merely an example of server 500 and is not meant to be limiting of server 500, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., server 500 may also include input and output devices, network access devices, buses, etc.
The Processor 501 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), off-the-shelf Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 502 may be an internal storage unit of the server 500, for example, a hard disk or a memory of the server 500. The memory 502 may also include both internal storage units and external storage devices of the server 500. The memory 502 is used to store the computer program and other programs and data required by the server 500. The memory 502 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-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the maintenance case generating device may refer to the corresponding process in the foregoing method embodiment, which is not described herein.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
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 solution. 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 manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the above-described division of modules or units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or may be integrated into another system module, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present application.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the steps of each method embodiment may be implemented. The computer program comprises computer program code, and the computer program code can be in a source code form, an object code form, an executable file or some intermediate form and the like. The computer readable medium may include: any entity or device capable of carrying the computer program code described above, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium described above can be appropriately increased or decreased according to the requirements of the jurisdiction's legislation and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the legislation and the patent practice. The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (9)
1. A vehicle diagnostic software configuration method, applied to a server, comprising:
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 diagnostic software is acquired for the first time according to the historical acquisition information of the target diagnostic software;
if yes, universal data, appointed function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnosis software are sent to the user, wherein the appointed function data is fault code reading function data;
If not, sending general data for configuring the target diagnosis software, first function data corresponding to a historical diagnosis result related to the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user;
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 in a preset time period has faults or not;
if yes, the first functional data are functional data corresponding to the fault type of the historical fault;
if not, the first function data is the fault code reading function data.
2. The vehicle diagnostic software configuration method of claim 1, wherein the method further comprises:
acquiring an execution result of the specified functional data or the first functional data of the target diagnostic software in the using process;
And according to the execution result, sending second function data which needs to be configured for the next execution of the target diagnosis software to the user.
3. The configuration method according to claim 2, characterized in that the first function data includes a read trouble code function data;
The execution result comprises the step of reading a fault code;
Correspondingly, the sending, according to the execution result, second function data that needs to be configured for the next execution of the target diagnostic software to the user includes:
And according to the fault code, sending second function data which need to be configured for the next execution of the target diagnosis software associated with the fault code to a user.
4. A configuration method according to claim 3, characterized in that the fault code comprises a fault code of the software class;
correspondingly, according to the fault code, sending second function data which needs to be configured for the next execution of the target diagnosis software associated with the fault code to a user, 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 types.
5. A configuration method according to claim 3, characterized in that the fault code comprises a fault code of the hardware category;
correspondingly, according to the fault code, sending second function data which needs to be configured for the next execution of the target diagnosis software associated with the fault code to a user, wherein the second function data comprises:
And sending the read data stream function data and the action test function data for configuring the target diagnosis software to the user according to the fault code of the hardware class.
6. A configuration method according to claim 3, characterized in that the fault code comprises 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 for the next execution of the target diagnosis software associated with the fault code to a user, wherein the second function data comprises:
And sending the read data stream function data, the online programming function data and the 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.
7. A vehicle diagnostic software configuration apparatus, comprising:
the system comprises an acquisition instruction receiving module, a diagnosis software acquisition module and a control module, wherein the acquisition instruction receiving module is used for receiving a diagnosis software acquisition instruction sent by a user, and 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 acquired for the first time according to the history acquisition information of the target diagnosis software;
The first sending module is used for sending general data, appointed function data and configuration parameters corresponding to the target vehicle type information for configuring the target diagnostic software to the user when the target diagnostic software is acquired for the first time, wherein the appointed function data is fault code reading function data;
The second sending module is used for sending general data for configuring the target diagnosis software, first function data corresponding to a historical diagnosis result related to the target vehicle type information and configuration parameters corresponding to the target vehicle type information to the user when the target diagnosis software is acquired for non-primary time;
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 in a preset time period has faults or not;
if yes, the first functional data are functional data corresponding to the fault type of the historical fault;
if not, the first function data is the fault code reading function data.
8. 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 6 when executing the computer program.
9. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111078894.2A CN113778557B (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 CN113778557B (en) | 2021-09-15 | 2021-09-15 | Vehicle diagnosis software configuration method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113778557A CN113778557A (en) | 2021-12-10 |
| CN113778557B true CN113778557B (en) | 2024-04-26 |
Family
ID=78843922
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111078894.2A Active CN113778557B (en) | 2021-09-15 | 2021-09-15 | Vehicle diagnosis software configuration method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778557B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114936054B (en) * | 2022-04-11 | 2024-07-12 | 中车青岛四方机车车辆股份有限公司 | Method and device for generating debugging process file of vehicle and railway vehicle |
| CN115050232A (en) * | 2022-05-19 | 2022-09-13 | 深圳市元征科技股份有限公司 | Simulation diagnosis method of vehicle data, terminal device and medium |
| CN114995862B (en) * | 2022-08-03 | 2022-11-01 | 深圳市星卡软件技术开发有限公司 | Method, device and system for calling diagnosis module |
| CN116300780B (en) * | 2022-09-07 | 2024-01-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
| CN116700808B (en) * | 2023-06-26 | 2024-05-14 | 中国第一汽车股份有限公司 | EOL configuration code processing method, system, electronic equipment and storage medium |
Citations (10)
| 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 |
| 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 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| SE541395C2 (en) * | 2017-12-27 | 2019-09-10 | Scania Cv Ab | Method and control unit for facilitating diagnosis for a vehicle |
| CN109196477A (en) * | 2018-08-28 | 2019-01-11 | 深圳市元征科技股份有限公司 | A kind of application method of vehicle diagnostic equipment, system and vehicle diagnostic equipment |
-
2021
- 2021-09-15 CN CN202111078894.2A patent/CN113778557B/en active Active
Patent Citations (10)
| 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 |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113778557A (en) | 2021-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113778557B (en) | Vehicle diagnosis software configuration method, device, server and storage medium | |
| CN108563214B (en) | Vehicle diagnosis method, device and equipment | |
| CN110908888B (en) | Server testing method and device | |
| CN109190776B (en) | Method and device for rechecking automobile fault, terminal equipment and storage medium | |
| CN109857085B (en) | Method and system for generating driving data in simulation mode, simulation terminal and test system | |
| CN111708584A (en) | Vehicle diagnosis method and device, diagnosis equipment and storage medium | |
| KR20140116492A (en) | System and method for providing diagnostic fault information | |
| CN113114659B (en) | Diagnostic equipment detection method and device, terminal equipment and storage medium | |
| CN109085811B (en) | Equipment point inspection method and device | |
| CN113608518A (en) | Data generation method, device, terminal equipment and medium | |
| CN111553491A (en) | Vehicle maintenance record generation method and related device | |
| CN115223273A (en) | TCU data monitoring method and device, terminal equipment and storage medium | |
| CN112034820A (en) | Cloud-based hardware-in-loop system testing method and system and storage medium | |
| CN116257437A (en) | ADAS system defect verification method and device based on real vehicle data reinjection | |
| CN112306038B (en) | Detection method, detection device and diagnosis equipment | |
| CN114995792B (en) | Modularized development method, device, medium and electronic device of automobile diagnosis device | |
| CN115480944A (en) | Black screen fault analysis method and device of vehicle-mounted entertainment terminal, vehicle and medium | |
| CN115587041A (en) | Mobile application delivery task processing method and device, electronic equipment and storage medium | |
| CN114625106A (en) | Vehicle diagnosis method and device, electronic equipment and storage medium | |
| KR101626581B1 (en) | Test method for error applition of portable communication terminal | |
| CN112327800A (en) | Vehicle detection method and device and diagnosis equipment | |
| CN111145386A (en) | Method, equipment and medium for managing vehicle computer data based on block chain | |
| CN114753911B (en) | SCR system mixer working condition detection method and device, electronic equipment and storage medium | |
| CN114220190A (en) | Integration method of vehicle maintenance diagnosis report, related device and storage medium | |
| CN118464459A (en) | Engine fault diagnosis method and device, cloud server 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |