CN113787977A - Vehicle maintenance method, communication device, and storage medium - Google Patents
Vehicle maintenance method, communication device, and storage medium Download PDFInfo
- Publication number
- CN113787977A CN113787977A CN202111117628.6A CN202111117628A CN113787977A CN 113787977 A CN113787977 A CN 113787977A CN 202111117628 A CN202111117628 A CN 202111117628A CN 113787977 A CN113787977 A CN 113787977A
- Authority
- CN
- China
- Prior art keywords
- target
- maintenance
- file
- vehicle
- fault code
- 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
- 238000012423 maintenance Methods 0.000 title claims abstract description 377
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000004891 communication Methods 0.000 title claims abstract description 33
- 238000003745 diagnosis Methods 0.000 claims description 23
- 230000008439 repair process Effects 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 18
- 230000006870 function Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000002405 diagnostic procedure Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000004378 air conditioning Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
- B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
- B60R16/0232—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions
- B60R16/0234—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions related to maintenance or repairing of vehicles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Mechanical Engineering (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application is applicable to the technical field of computers, and provides a vehicle maintenance method, communication equipment and a storage medium, wherein the vehicle maintenance method comprises the following steps: diagnosing a target vehicle and acquiring a target fault code of the target vehicle; uploading the target fault code to a server; receiving file information of each target maintenance guide file aiming at the target fault code, which is returned by the server, wherein the file information comprises the maintenance success rate of the target maintenance guide file; wherein each target fault code corresponds to at least one target maintenance instruction file; and displaying the file information of the target maintenance guide file. According to the method and the device, the user can intuitively select the corresponding target maintenance instruction file as the maintenance reference according to the displayed file information containing the maintenance success rate, so that the user is accurately guided to solve the vehicle fault, and the vehicle maintenance efficiency is improved.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a vehicle maintenance method, communication equipment and a storage medium.
Background
With the continuous development of vehicle electronics, Electronic Control Units (ECUs) of vehicles are becoming more and more, and corresponding vehicle failures are also increasing. The fault code of the vehicle is an important means for detecting the fault of the vehicle, and a maintenance person checks the fault code through a diagnosis tool and then checks a maintenance vehicle. At present, maintenance personnel usually determine a method capable of solving the current vehicle fault to perform vehicle maintenance according to own experience or ways of actively seeking help and the like. This approach does not facilitate efficient resolution of vehicle faults.
Disclosure of Invention
In view of this, embodiments of the present application provide a vehicle maintenance method, a communication device, and a storage medium, so as to solve the problem in the prior art how to facilitate a user to accurately solve a vehicle fault.
A first aspect of an embodiment of the present application provides a first vehicle maintenance method, which is applied to a diagnostic device, and includes:
diagnosing a target vehicle and acquiring a target fault code of the target vehicle;
uploading the target fault code to a server;
receiving file information of each target maintenance guide file aiming at the target fault code, which is returned by the server, wherein the file information comprises the maintenance success rate of the target maintenance guide file; wherein each target fault code corresponds to at least one target maintenance instruction file;
and displaying the file information of the target maintenance guide file.
Optionally, the diagnosing the target vehicle and obtaining the target fault code of the target vehicle includes:
scanning and diagnosing a target ECU system of the target vehicle to determine an ECU system topology map of the target vehicle;
and acquiring a target fault code selected by a user according to the topological graph of the ECU system.
Optionally, after the displaying the file information of the target repair guidance file, the method further includes:
and downloading the target maintenance guide file when a reference instruction of a user for the target maintenance guide file is received.
Optionally, after the displaying the file information of the target repair guidance file, the method further includes:
and receiving maintenance result information fed back by a user and aiming at the target maintenance guide file, and uploading the maintenance result information to the server so as to indicate the maintenance success rate of the server for updating the target maintenance guide file.
Optionally, the displaying file information of the target repair guidance file includes:
and when at least two target maintenance guide files exist correspondingly in the target fault code, sequentially displaying file information of the at least two target maintenance guide files according to a mode that the maintenance success rate is from high to low.
Optionally, before the uploading the target fault code to the server, the method further includes:
acquiring identification information of the target vehicle;
correspondingly, the uploading the target fault code to a server includes:
and uploading the target fault code and the identification information of the target vehicle to a server.
A second aspect of the embodiments of the present application provides a second vehicle repair method, applied to a server, including:
acquiring a target fault code uploaded by a diagnostic device;
determining information of each target maintenance guide file corresponding to the target fault code according to the target fault code; each target fault code corresponds to at least one target maintenance instruction file;
and sending file information of each target maintenance guide file to the diagnosis equipment, wherein the file information comprises the maintenance success rate of the target maintenance guide file.
Optionally, the vehicle repair method further includes:
obtaining maintenance result information corresponding to the target maintenance guide file uploaded by the diagnosis equipment;
and updating the maintenance success rate of the target maintenance guide file according to the maintenance result information corresponding to the target maintenance guide file.
A third aspect of embodiments of the present application provides a communication device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, which when executed by the processor causes the communication device to carry out the steps of the vehicle repair method as described.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes a communication device to carry out the steps of the vehicle repair method as described.
A fifth aspect of embodiments of the present application provides a computer program product, which, when run on a communication device, causes the communication device to perform the vehicle servicing method of any one of the first or second aspects described above.
Compared with the prior art, the embodiment of the application has the advantages that: in the embodiment of the application, the diagnosis equipment can diagnose the target vehicle, acquire the target fault code of the current target vehicle and upload the target fault code to the server, so that the diagnosis equipment can receive the file information of each target maintenance instruction file returned by the server according to the target fault code, wherein the information of the target maintenance instruction file at least comprises the maintenance success rate of the target maintenance instruction file, and each target fault code at least corresponds to one target maintenance instruction file; and then, displaying file information of the target maintenance guide file. The file information of each corresponding target maintenance guide file can be acquired from the server, so that maintenance reference can be accurately and effectively provided for a user; in addition, the file information of the target maintenance guide file comprises the maintenance success rate of the target maintenance guide file, so that a user can accurately select the corresponding target maintenance guide file as a maintenance reference according to the maintenance success rate by displaying the file information of the target maintenance guide file, thereby accurately guiding the user to solve the vehicle fault and improving the vehicle maintenance efficiency.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.
FIG. 1 is a schematic flow chart illustrating a first method for vehicle maintenance provided by an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating an implementation of a second vehicle repair method provided by an embodiment of the present application;
FIG. 3 is a schematic diagram of an ECU system topology provided by an embodiment of the present application;
FIG. 4 is a schematic flow chart illustrating an implementation of a third vehicle repair method provided by the embodiment of the present application;
FIG. 5 is a schematic flow chart illustrating a fourth implementation of a vehicle repair method according to an embodiment of the present disclosure;
FIG. 6 is a schematic illustration of a first vehicle service device provided by an embodiment of the present application;
FIG. 7 is a schematic view of a second vehicle service device provided in an embodiment of the present application;
fig. 8 is a schematic diagram of a communication device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
With the continuous development of vehicle electronics, Electronic Control Units (ECUs) of vehicles are becoming more and more, and corresponding vehicle failures are also increasing. The fault code of the vehicle is an important means for detecting the fault of the vehicle, and a maintenance person checks the fault code through a diagnosis tool and then checks a maintenance vehicle. At present, maintenance personnel usually determine a method capable of solving the current vehicle fault to perform vehicle maintenance according to own experience or ways of actively seeking help and the like. Or some diagnostic equipment local directories store fault code help files, and maintenance personnel can acquire maintenance guide information according to the fault code help files. However, the manner depending on the experience of the user is more subjective and limited, and it is inconvenient to actively seek help, and if the local fault code help file is queried, there may be a problem that the local fault code is not updated or the current fault cannot be solved by the single guidance information stored in the local fault code help file. Therefore, the current vehicle maintenance method is inconvenient for effectively solving the vehicle fault.
In order to solve the technical problem, an embodiment of the present application provides a vehicle maintenance method, including: diagnosing a target vehicle and acquiring a target fault code of the target vehicle; uploading the target fault code to a server; receiving file information of each target maintenance guide file aiming at the target fault code, which is returned by the server, wherein the file information comprises the maintenance success rate of the target maintenance guide file; wherein each target fault code corresponds to at least one target maintenance instruction file; and displaying the file information of the target maintenance guide file.
The file information of each corresponding target maintenance guide file can be acquired from the server, so that maintenance reference can be accurately and effectively provided for a user; in addition, the file information of the target maintenance guide file comprises the maintenance success rate of the target maintenance guide file, so that a user can select an effective target maintenance guide file according to the maintenance success rate by displaying the file information of the target maintenance guide file, the vehicle fault is further conveniently and accurately solved by the user, and the vehicle maintenance efficiency is improved.
The first embodiment is as follows:
fig. 1 shows a schematic flow chart of a first vehicle maintenance method provided in an embodiment of the present application, where an execution subject of the vehicle maintenance method is a diagnostic device, which is detailed as follows:
in S101, the target vehicle is diagnosed, and a target fault code of the target vehicle is acquired.
In the embodiment of the application, the target vehicle is a vehicle which is currently in communication connection with the diagnosis equipment and needs to be diagnosed and maintained. The target fault code is the fault code of the target vehicle which needs to be repaired and solved currently. The number of the target fault codes can be one or more than one.
Specifically, the diagnostic device may be connected to an On Board Diagnostics (OBD) interface of the target vehicle, so that data interaction may be performed with an ECU system of the target vehicle, diagnosis of the target vehicle may be achieved, and a current target fault code of the target vehicle may be obtained.
In S102, the target fault code is uploaded to a server.
And after the current target fault code is determined, uploading the target fault code to a server. In one embodiment, if the number of the target fault codes is more than one, the target fault codes can be uploaded to the server together in a list manner.
In S103, receiving file information of each target maintenance guidance file for the target fault code, where the file information includes a maintenance success rate of the target maintenance guidance file, where the file information is returned by the server; wherein each target fault code corresponds to at least one target maintenance instruction file.
After the server acquires the target fault code, the server inquires the information of a maintenance guide file prestored in the server according to the target fault code, determines the maintenance guide file stored corresponding to the target fault code as the target maintenance guide file, and acquires the file information of the target maintenance guide file. And for each target fault code, the server stores one or more target maintenance guide files corresponding to the target fault code.
In the embodiment of the application, the file information of the target maintenance instruction file at least comprises the maintenance success rate of the target maintenance instruction file, and also comprises other information which can represent the target maintenance instruction file. The other information may be a file name or unique identification information of the target maintenance guide file, and may also be specific text content of the target maintenance file directly. In one embodiment, the other information may also be content summary information of the target maintenance guidance file, so that after the user views the information of the target maintenance guidance file, the user can select one or more target maintenance guidance files from the information to view specific text content, and guidance is provided for vehicle maintenance of the user.
In S104, the file information of the target repair guidance file is displayed.
In the embodiment of the application, after the file information of the target maintenance guide file returned by the server is received, the file information of the target maintenance guide file containing the maintenance success rate is displayed, so that a user can select one target maintenance guide file to check the specific text content according to the displayed maintenance success rate of the target maintenance file, and maintain the target vehicle according to the guidance of the target maintenance guide file.
In one embodiment, when the number of the target fault codes of the target vehicle acquired in step S101 is more than one, step S104 specifically includes: and correspondingly displaying the target fault codes and the file information of the target maintenance guide file. For example, if the current target fault code includes two fault codes, namely, the number "C11016" and the number "U100016", the fault code "C11016" and the file information of the target maintenance guidance file corresponding to the fault code may be displayed in the first area of the display interface; and displaying the fault code 'U100016' and file information of the corresponding target maintenance guide file in a second area of the display interface. Illustratively, the file information of the target repair guide file includes a file name and a repair success rate of the target repair guide file. In some embodiments, the target fault code is displayed, and at the same time, fault description text information corresponding to the target fault code is also displayed, for example, fault description text information "ignition line fault" of the fault code is displayed while the fault code "C11016" is displayed in the first area.
In the embodiment of the application, the diagnosis equipment can diagnose the target vehicle, acquire the target fault code of the current target vehicle and upload the target fault code to the server, so that the diagnosis equipment can receive the file information of each target maintenance instruction file returned by the server according to the target fault code, wherein the information of the target maintenance instruction file at least comprises the maintenance success rate of the target maintenance instruction file, and each target fault code at least corresponds to one target maintenance instruction file; and then, displaying file information of the target maintenance guide file. The file information of the effective target maintenance guide file can be obtained from the server according to the current detected fault, so that maintenance reference can be accurately and effectively provided for a user; in addition, the file information of the target maintenance guide file comprises the maintenance success rate of the target maintenance guide file, so that a user can select an effective target maintenance guide file according to the maintenance success rate by displaying the file information of the target maintenance guide file, the vehicle fault is further conveniently and accurately solved by the user, and the vehicle maintenance efficiency is improved.
Example two:
fig. 2 is a schematic flow chart of a second vehicle maintenance method provided in an embodiment of the present application, in which an execution subject of the vehicle diagnostic method is a diagnostic apparatus. The vehicle maintenance method in the embodiment of the application is further improved on the basis of the method in the first embodiment, and the same parts as the first embodiment are not repeated. The vehicle service method as shown in fig. 2 is detailed as follows:
in S201, a target ECU system of the target vehicle is scanned and diagnosed to determine an ECU system topology of the target vehicle.
In this embodiment of the application, the diagnostic device may send a scan instruction to the target vehicle to scan the target ECU system of the target vehicle, diagnose the target vehicle, and obtain information of the target ECU system returned by the target vehicle. The information of the target ECU system at least includes fault condition information of the target ECU system, and may further include connection information of the target ECU system, and the like. And then, determining and displaying the ECU system topological graph of the target vehicle according to the acquired information of the target ECU system.
Illustratively, the ECU system topology of the target vehicle is shown in FIG. 3. The gateway System of the target vehicle is connected to each target ECU System such as a Battery Management System (BMS), a DC-to-DC converter (DCDC), a Transmission Control Unit (TCU), an Engine Management System (EMS), an electronic Parking System (EPB), and an Air conditioning System (AC). If the ECU system has fault codes, the system name is followed by numbers which are used for indicating how many fault codes exist in the ECU system at present. For example, as shown in fig. 3, there are 1 fault code for each of the battery management system and the dc converter, 5 fault codes for the engine management system, and 3 fault codes for each of the electronic parking system and the air conditioning system.
In S202, a target fault code selected by a user according to the ECU system topological graph is obtained.
After the ECU system topological graph of the target vehicle is determined, a fault code selection instruction is obtained according to the fault codes displayed on the ECU system topological graph by a user, and the target fault code selected by the current user is determined according to the fault code selection instruction.
For example, a user may click on a location indicated by the engine management system in the topology of the ECU system shown in fig. 3, and select two fault codes from 5 fault codes as target fault codes, wherein the two fault codes may be divided into a primary fault code and a secondary fault code according to their urgency or importance.
In S203, the target fault code is uploaded to a server.
In S204, receiving file information of each target maintenance guidance file for the target fault code, where the file information includes a maintenance success rate of the target maintenance guidance file, and the file information is returned by the server; wherein each target fault code corresponds to at least one target maintenance instruction file.
In S205, the file information of the target repair guidance file is displayed.
In the embodiment of the application, each ECU system of the target vehicle can be scanned, and the ECU system topological graph of the target vehicle is determined, so that a user can conveniently know the structure of the target vehicle and conveniently select the target fault code according to the ECU system topological graph, and the convenience of vehicle maintenance can be further improved.
Optionally, after step S104 or S205, the method further includes:
and downloading the target maintenance guide file when a reference instruction of a user for the target maintenance guide file is received.
In the embodiment of the present application, in step S103 or step S204, the information of the target maintenance guidance file acquired by the diagnostic device from the server is only the file name and the maintenance success rate of the target maintenance guidance file, and the actual content of the target maintenance guidance file is not downloaded.
In the embodiment of the application, after information of a target maintenance guide file is displayed, a reference instruction of a user for the target maintenance guide file is received. And then, downloading a corresponding complete target maintenance guide file from the server for the user to check according to the checking instruction aiming at the target maintenance guide file. For example, when the touch button corresponding to the target maintenance guidance file of the "ignition circuit fault maintenance manual" is clicked, it is determined that the viewing instruction of the target maintenance guidance file is currently acquired, and the "ignition circuit fault maintenance manual" is downloaded for viewing.
In the embodiment of the application, the target maintenance guide file is downloaded when a reference instruction of a user for the target maintenance guide file is received, and the files can be downloaded as required compared with a mode of downloading all the target maintenance guide files at the beginning, so that system operation resources and storage resources can be saved.
Optionally, after step S103 or S205, the method further includes:
and receiving maintenance result information fed back by a user and aiming at the target maintenance guide file, and uploading the maintenance result information to the server so as to indicate the maintenance success rate of the server for updating the target maintenance guide file.
In the embodiment of the application, after a user checks a target maintenance instruction file and carries out vehicle maintenance according to the target maintenance instruction file, maintenance result information corresponding to the target maintenance instruction file is input into the diagnosis equipment. The maintenance result information is information indicating that the target maintenance guidance file cannot successfully guide the user to complete the vehicle maintenance (may be indicated by text information such as "unresolved" or "failed"), or information indicating that the target maintenance guidance file successfully guides the user to complete the vehicle maintenance (may be indicated by text information such as "resolved" or "successful").
After the maintenance result information corresponding to the target maintenance guide file is obtained, the identification information (such as name) of the target maintenance guide file and the maintenance result information are uploaded to the server together, so that the server is instructed to update the maintenance success rate of the target maintenance guide file according to the maintenance result information of the target maintenance guide file.
In the embodiment of the application, after the target maintenance guide files are displayed in sequence according to the maintenance success rate, the maintenance result information fed back by the user and aiming at the target maintenance guide files can be further received and uploaded to the server, so that the maintenance success rate of the target maintenance guide files can be updated timely, the accuracy of file information display of the follow-up target maintenance guide files is improved, the user can accurately select the target maintenance guide files with higher maintenance success rate to maintain the vehicle, and the accuracy and the efficiency of vehicle maintenance are improved.
Optionally, before the receiving the repair result information for the target repair guidance file fed back by the user, further comprising:
and sending prompt information to prompt a user to enter maintenance result information corresponding to the target maintenance guide file.
In the embodiment of the application, the user can be prompted to enter the maintenance result information corresponding to the currently displayed target maintenance instruction file by sending the prompt information. In one embodiment, the corresponding maintenance result information of each target maintenance instruction file at the beginning is defaulted to 'not executed'. And then, if a viewing instruction is checked, namely after the user downloads the corresponding target maintenance guide file for viewing, sending a prompt message to instruct the user to select character information of 'unresolved' (also can be 'failed') or 'resolved' (also can be 'successful') as maintenance result information according to a maintenance result of vehicle maintenance carried out by the viewed target maintenance guide file.
In an embodiment, the prompt message may be specifically sent within a preset time period after the viewing instruction is detected. Specifically, the user may be prompted to enter the maintenance result information of the currently viewed target maintenance guidance file by popping up a prompt box or sending a voice prompt.
In the embodiment of the application, the prompt information is sent, so that the user can be prompted to enter the maintenance result information corresponding to the target maintenance guide file in time, the server can update the maintenance success rate of the target maintenance guide file in time according to the maintenance result information, the accuracy of file information display of the subsequent target maintenance guide file is improved, and the accuracy and the efficiency of vehicle maintenance are improved.
Optionally, the step S104 or the step S205 includes:
and when at least two target maintenance guide files exist correspondingly in the target fault code, sequentially displaying file information of the at least two target maintenance guide files according to a mode that the maintenance success rate is from high to low.
In the embodiment of the application, for each target fault code, when at least two target maintenance guide files exist in the target fault code, the file information of each target maintenance guide file is displayed in sequence according to the mode that the maintenance success rate of each target maintenance guide file is from high to low.
Illustratively, for the fault code "C110116" indicating "ignition circuit fault", the respective target maintenance instruction files acquired from the server are sorted according to the size of the maintenance success rate, and the display contents may be as shown in table 1.
Table 1:
in the embodiment of the application, the target maintenance instruction files can be sequentially displayed according to the mode that the maintenance success rate is from high to low, so that a user can conveniently and preferentially select the target maintenance instruction file which is sequenced in the front and has a high maintenance success rate as the maintenance instruction, the success rate of vehicle maintenance can be improved, and the vehicle maintenance efficiency can be improved.
Optionally, before the uploading the target fault code to the server, the method further includes:
acquiring identification information of the target vehicle;
correspondingly, the uploading the target fault code to a server includes:
and uploading the target fault code and the identification information of the target vehicle to a server.
In the embodiment of the present application, the Identification information of the target Vehicle may be Vehicle type information or Vehicle Identification Number (VIN) of the target Vehicle. In one embodiment, the identification information of the target vehicle may be acquired by receiving an input instruction of a user. In another embodiment, the VIN code of the target vehicle may be read as the identification information of the target vehicle by sending a VIN code reading instruction to the ECU system of the target vehicle.
Correspondingly, after the target fault code is obtained, the target fault code and the identification information of the target vehicle are uploaded to the server together, so that the server returns the file information of the maintenance guidance file matched with the target fault code and the identification information of the target vehicle as the file information of the target maintenance guidance file. In one embodiment, the identification information of the target vehicle is the VIN code of the vehicle, and the VIN code of the vehicle is uploaded to the server, so that the server can determine the vehicle type annuity information of the target vehicle according to the VIN code, and the corresponding maintenance guidance file can be found more accurately by combining the vehicle type annuity information and the target fault code.
In the embodiment of the application, the identification information of the target vehicle can be obtained in advance, and the target fault code and the identification information of the target vehicle are uploaded to the server together, so that the file information of the target maintenance guide file returned by the server is more accurate, and the success rate and the efficiency of vehicle maintenance are further improved.
Example three:
fig. 4 is a schematic flow chart of a third vehicle repair method provided in the embodiment of the present application, where an execution subject of the vehicle diagnostic method is a server, and the details are as follows:
in S401, a target fault code uploaded by the diagnostic device is acquired.
Step S401 in the embodiment of the present application corresponds to step S102 in the first embodiment, and the server can obtain the target fault code uploaded by the diagnostic device. In one embodiment, the server specifically obtains identification information and a target fault code of a target vehicle that is currently being diagnosed by the diagnostic device. The number of the target fault codes can be one or more than one.
In S402, according to the target fault code, determining each target maintenance guide file corresponding to the target fault code; each target fault code corresponds to at least one target maintenance instruction file.
Step S402 in the embodiment of the present application corresponds to step S103 in the first embodiment. After the server obtains the target fault code uploaded by the diagnosis device, the server can query a pre-stored maintenance guide file library according to the target fault code, and find a maintenance guide file matched with the target fault code as a target maintenance guide file. And for each target fault code, at least one target maintenance guide file corresponding to the target fault code exists in the maintenance guide file library.
In one embodiment, specifically, according to the target fault code and the identification information of the target vehicle, a maintenance guidance file which is matched with the identification information of the target vehicle and corresponds to the target fault code is found as a target maintenance guidance file. In one embodiment, for each target fault code, the target maintenance guidance file is specifically a preset number (e.g., 5) of maintenance guidance files that match the model of the target vehicle and have the highest maintenance success rate corresponding to the target fault code.
In S403, file information of each target maintenance guidance file is sent to the diagnostic device, where the file information includes a maintenance success rate of the target maintenance guidance file.
In the embodiment of the application, the information of the target maintenance instruction file at least comprises the maintenance success rate of the target maintenance instruction file, and also comprises other information which can represent the target maintenance instruction file and the like. The other information may be a file name or unique identification information of the target maintenance guide file, specific text content of the target maintenance guide file, or content summary information of the target maintenance guide file.
After determining each target maintenance guide file corresponding to the target fault code, acquiring file information of each target maintenance guide file, and sending the file information to the diagnosis equipment. In an embodiment, if the number of the target fault codes is more than one, the target fault codes and the file information of the target maintenance guidance files corresponding to the target fault codes can be bound and then sent to the diagnosis equipment together, so that the diagnosis equipment can distinguish the target maintenance guidance files corresponding to the target fault codes respectively.
In the embodiment of the application, the server can acquire the target fault code uploaded by the diagnosis equipment, determine each target maintenance instruction file corresponding to the target fault code according to the target fault code, and return the file information of the target maintenance instruction file to the diagnosis equipment, so that the diagnosis equipment can accurately and effectively provide maintenance reference for a user according to the file information of the target maintenance instruction file; in addition, the file information of the target maintenance guide file at least comprises the maintenance success rate of the target maintenance guide file, so that when the diagnosis equipment displays the information of the target maintenance guide file, a user can conveniently and effectively select the target maintenance guide file with higher maintenance success rate, the user can further conveniently and accurately solve the vehicle fault, and the vehicle maintenance efficiency is improved.
Example four:
fig. 5 is a schematic flow chart of a fourth vehicle repair method provided in the embodiment of the present application, in which an execution subject of the vehicle diagnostic method is a server device. The vehicle maintenance method of the embodiment of the application is further improved on the basis of the method of the third embodiment, and the parts same as the third embodiment are not repeated. The vehicle service method as shown in fig. 5 is detailed as follows:
in S501, a target fault code uploaded by the diagnostic device is acquired.
In S502, according to the target fault code, determining each target maintenance guide file corresponding to the target fault code; each target fault code corresponds to at least one target maintenance instruction file.
In S503, file information of each target maintenance guidance file is sent to the diagnostic device, where the file information includes a maintenance success rate of the target maintenance guidance file.
In S504, maintenance result information corresponding to the target maintenance instruction file uploaded by the diagnostic device is acquired.
In the embodiment of the application, after sending the information of the target maintenance instruction file to the diagnostic device, the server obtains the maintenance result information corresponding to the target maintenance instruction file uploaded by the diagnostic device, and the maintenance result information may be specifically uploaded together with the identification information (for example, name) of the target maintenance instruction file. The maintenance result information is information indicating that the target maintenance guidance file cannot successfully guide the user to complete the vehicle maintenance (may be indicated by text information such as "unresolved" or "failed"), or information indicating that the target maintenance guidance file successfully guides the user to complete the vehicle maintenance (may be indicated by text information such as "resolved" or "successful").
In S505, the maintenance success rate of the target maintenance guidance file is updated according to the maintenance result information corresponding to the target maintenance guidance file.
In the embodiment of the application, if the maintenance result information corresponding to the obtained target maintenance instruction file is information indicating that the target maintenance instruction file successfully instructs the user to complete vehicle maintenance, the maintenance success rate of the target maintenance instruction file is increased, otherwise, the maintenance success rate of the target maintenance instruction file is reduced, and the maintenance success rate of the target maintenance instruction file is updated.
Optionally, before step S501, the method further includes:
acquiring fault codes corresponding to vehicle types created by technicians, and uploading at least two fault maintenance guide files for each fault code;
setting an initial maintenance success rate for each fault maintenance guide file;
and storing the file information of each fault maintenance guide file in sequence according to the maintenance success rate.
In the embodiment of the application, the server can acquire the maintenance result information of the target maintenance instruction file and update the maintenance success rate of the target maintenance instruction file, so that the maintenance success rate can be updated timely according to the actual maintenance result, the latest target maintenance instruction file and the corresponding maintenance success rate can be returned to the diagnosis equipment in the subsequent process, a user can select a proper target maintenance instruction file to carry out vehicle maintenance according to the latest maintenance success rate, and the accuracy and the efficiency of vehicle maintenance are further improved.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example five:
fig. 6 shows a schematic structural diagram of a first vehicle maintenance device provided in an embodiment of the present application, where the first vehicle maintenance device is applied to a diagnostic apparatus, and for convenience of explanation, only a part related to the embodiment of the present application is shown:
the first vehicle service device includes: a target fault code acquisition unit 61, a target fault code uploading unit 62, a file information acquisition unit 63, and a display unit 64. Wherein:
and a target fault code obtaining unit 61, configured to diagnose the target vehicle and obtain a target fault code of the target vehicle.
And the target fault code uploading unit 62 is used for uploading the target fault code to the server.
A file information obtaining unit 63, configured to receive file information of each target maintenance guidance file for the target fault code, where the file information includes a maintenance success rate of the target maintenance guidance file, and the file information is returned by the server; wherein each target fault code corresponds to at least one target maintenance instruction file.
And the display unit 64 is used for displaying the file information of the target maintenance guide file.
Optionally, the target fault code obtaining unit 61 is specifically configured to scan and diagnose a target ECU system of the target vehicle to determine an ECU system topology of the target vehicle; and acquiring a target fault code selected by a user according to the topological graph of the ECU system.
Optionally, the first vehicle service device further comprises:
and the downloading unit is used for downloading the target maintenance guide file when a reference instruction of a user for the target maintenance guide file is received.
Optionally, the first vehicle service device further comprises:
and the maintenance result information acquisition unit is used for receiving maintenance result information which is fed back by a user and aims at the target maintenance guide file, and uploading the maintenance result information to the server so as to indicate the maintenance success rate of the server for updating the target maintenance guide file.
Optionally, the display unit 64 is specifically configured to, when at least two target maintenance guidance documents exist corresponding to the target fault code, sequentially display document information of the at least two target maintenance guidance documents according to a mode that a maintenance success rate is from high to low.
Optionally, the first vehicle service device further comprises:
an identification information acquisition unit configured to acquire identification information of the target vehicle;
correspondingly, the target fault code uploading unit 62 is specifically configured to upload the target fault code and the identification information of the target vehicle to a server.
Fig. 7 is a schematic structural diagram of a second vehicle maintenance device provided in an embodiment of the present application, where the second vehicle maintenance device is applied to a server, and for convenience of description, only a part related to the embodiment of the present application is shown:
the second vehicle maintenance device includes: a target fault code receiving unit 71, a target maintenance instruction file determining unit 72 and a transmitting unit 73. Wherein:
and the target fault code receiving unit 71 is used for acquiring the target fault code uploaded by the diagnostic equipment.
A target maintenance instruction file determining unit 72, configured to determine, according to the target fault code, each target maintenance instruction file corresponding to the target fault code; each target fault code corresponds to at least one target maintenance instruction file.
A sending unit 73, configured to send file information of each target maintenance guidance file to the diagnostic device, where the file information includes a maintenance success rate of the target maintenance guidance file.
Optionally, the second vehicle service device further comprises:
the updating unit is used for acquiring maintenance result information corresponding to the target maintenance guide file uploaded by the diagnosis equipment; and updating the maintenance success rate of the target maintenance guide file according to the maintenance result information corresponding to the target maintenance guide file.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
Example six:
fig. 8 is a schematic diagram of a communication device according to an embodiment of the present application. As shown in fig. 8, the communication device 8 of this embodiment includes: a processor 80, a memory 81, and a computer program 82, such as a vehicle service program, stored in the memory 81 and operable on the processor 80. The processor 80, when executing the computer program 82, implements the steps in the various vehicle service method embodiments described above, such as steps S101 to S104 shown in fig. 1 or steps S401 to S403 shown in fig. 4, for example. Alternatively, the processor 80 executes the computer program 82 to implement the functions of the modules/units in the device embodiments, such as the functions of the target fault code acquiring unit 61 to the display unit 64 shown in fig. 6, or the functions of the target fault code receiving unit 71 to the transmitting unit 73 shown in fig. 7.
Illustratively, the computer program 82 may be partitioned into one or more modules/units that are stored in the memory 81 and executed by the processor 80 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 82 in the communication device 8.
The communication device 8 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The communication device may include, but is not limited to, a processor 80, a memory 81. Those skilled in the art will appreciate that fig. 8 is merely an example of a communication device 8 and does not constitute a limitation of communication device 8 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the communication device may also include input-output devices, network access devices, buses, etc.
The Processor 80 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field 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 memory 81 may be an internal storage unit of the communication device 8, such as a hard disk or a memory of the communication device 8. The memory 81 may also be an external storage device of the communication device 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the communication device 8. Further, the memory 81 may also include both an internal storage unit of the communication device 8 and an external storage device. The memory 81 is used for storing the computer programs and other programs and data required by the communication device. The memory 81 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 function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform 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 system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art 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/communication device and method may be implemented in other ways. For example, the above-described apparatus/communication device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
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 modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the 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 signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by 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 maintenance method, characterized in that the method is applied to a diagnostic apparatus, comprising:
diagnosing a target vehicle and acquiring a target fault code of the target vehicle;
uploading the target fault code to a server;
receiving file information of each target maintenance guide file aiming at the target fault code, which is returned by the server, wherein the file information comprises the maintenance success rate of the target maintenance guide file; wherein each target fault code corresponds to at least one target maintenance instruction file;
and displaying the file information of the target maintenance guide file.
2. The vehicle service method of claim 1, wherein said diagnosing the target vehicle and obtaining the target fault code of the target vehicle comprises:
scanning and diagnosing a target ECU system of the target vehicle to determine an ECU system topology map of the target vehicle;
and acquiring a target fault code selected by a user according to the topological graph of the ECU system.
3. The vehicle repair method as set forth in claim 1, further comprising, after said displaying the documentation information of the target repair guidance documentation:
and downloading the target maintenance guide file when a reference instruction of a user for the target maintenance guide file is received.
4. The vehicle repair method according to any one of claims 1 to 3, further comprising, after said displaying the document information of the target repair guidance document:
and receiving maintenance result information fed back by a user and aiming at the target maintenance guide file, and uploading the maintenance result information to the server so as to indicate the maintenance success rate of the server for updating the target maintenance guide file.
5. The vehicle service method of claim 1, wherein said displaying documentation information for said target service guideline file comprises:
and when at least two target maintenance guide files exist correspondingly in the target fault code, sequentially displaying file information of the at least two target maintenance guide files according to a mode that the maintenance success rate is from high to low.
6. The vehicle service method of claim 1, further comprising, prior to said uploading said target fault code to a server:
acquiring identification information of the target vehicle;
correspondingly, the uploading the target fault code to a server includes:
and uploading the target fault code and the identification information of the target vehicle to a server.
7. A vehicle maintenance method is applied to a server and comprises the following steps:
acquiring a target fault code uploaded by a diagnostic device;
determining each target maintenance guide file corresponding to the target fault code according to the target fault code; each target fault code corresponds to at least one target maintenance instruction file;
and sending file information of each target maintenance guide file to the diagnosis equipment, wherein the file information comprises the maintenance success rate of the target maintenance guide file.
8. The vehicle service method of claim 7, further comprising:
obtaining maintenance result information corresponding to the target maintenance guide file uploaded by the diagnosis equipment;
and updating the maintenance success rate of the target maintenance guide file according to the maintenance result information corresponding to the target maintenance guide file.
9. A communication device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the computer program, when executed by the processor, causes the communication device to carry out the steps of the method according to any one of claims 1 to 6 or 7 to 8.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes a communication device to carry out the steps of the method according to any one of claims 1 to 6 or claims 7 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111117628.6A CN113787977A (en) | 2021-09-23 | 2021-09-23 | Vehicle maintenance method, communication device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111117628.6A CN113787977A (en) | 2021-09-23 | 2021-09-23 | Vehicle maintenance method, communication device, and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113787977A true CN113787977A (en) | 2021-12-14 |
Family
ID=79184225
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111117628.6A Pending CN113787977A (en) | 2021-09-23 | 2021-09-23 | Vehicle maintenance method, communication device, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113787977A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114407812A (en) * | 2022-01-12 | 2022-04-29 | 中国第一汽车股份有限公司 | Diagnostic database determination method, diagnostic database determination device, electronic equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002228554A (en) * | 2001-01-31 | 2002-08-14 | Mazda Motor Corp | On-vehicle remote failure diagnostic device, on-vehicle remote failure diagnostic program, remote failure diagnostic method of vehicle, failure diagnostic device of vehicle, and failure diagnostic program of vehicle |
| JP2016060406A (en) * | 2014-09-19 | 2016-04-25 | 日産自動車株式会社 | Vehicle diagnosis apparatus, terminal device, and vehicle diagnosis method |
| CN109189050A (en) * | 2018-10-22 | 2019-01-11 | 爱驰汽车（上海）有限公司 | Troubleshooting methodology, calculates equipment and computer storage medium at device |
| CN109214706A (en) * | 2018-09-28 | 2019-01-15 | 深圳市轱辘汽车维修技术有限公司 | Maintenance tool management method, device, system, server and storage medium |
| CN109885038A (en) * | 2019-03-28 | 2019-06-14 | 深圳市元征科技股份有限公司 | A kind of vehicle trouble code maintenance guidance method and relevant device |
| CN109976314A (en) * | 2019-04-22 | 2019-07-05 | 深圳市元征科技股份有限公司 | A kind of querying method and system of error code Maintenance Cases |
| CN110032169A (en) * | 2019-03-22 | 2019-07-19 | 深圳市朗仁科技有限公司 | Breakdown maintenance bootstrap technique and device |
| CN113263993A (en) * | 2021-05-17 | 2021-08-17 | 深圳市元征科技股份有限公司 | Fault early warning method and device, communication equipment and storage medium |
-
2021
- 2021-09-23 CN CN202111117628.6A patent/CN113787977A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002228554A (en) * | 2001-01-31 | 2002-08-14 | Mazda Motor Corp | On-vehicle remote failure diagnostic device, on-vehicle remote failure diagnostic program, remote failure diagnostic method of vehicle, failure diagnostic device of vehicle, and failure diagnostic program of vehicle |
| JP2016060406A (en) * | 2014-09-19 | 2016-04-25 | 日産自動車株式会社 | Vehicle diagnosis apparatus, terminal device, and vehicle diagnosis method |
| CN109214706A (en) * | 2018-09-28 | 2019-01-15 | 深圳市轱辘汽车维修技术有限公司 | Maintenance tool management method, device, system, server and storage medium |
| CN109189050A (en) * | 2018-10-22 | 2019-01-11 | 爱驰汽车（上海）有限公司 | Troubleshooting methodology, calculates equipment and computer storage medium at device |
| CN110032169A (en) * | 2019-03-22 | 2019-07-19 | 深圳市朗仁科技有限公司 | Breakdown maintenance bootstrap technique and device |
| CN109885038A (en) * | 2019-03-28 | 2019-06-14 | 深圳市元征科技股份有限公司 | A kind of vehicle trouble code maintenance guidance method and relevant device |
| CN109976314A (en) * | 2019-04-22 | 2019-07-05 | 深圳市元征科技股份有限公司 | A kind of querying method and system of error code Maintenance Cases |
| CN113263993A (en) * | 2021-05-17 | 2021-08-17 | 深圳市元征科技股份有限公司 | Fault early warning method and device, communication equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114407812A (en) * | 2022-01-12 | 2022-04-29 | 中国第一汽车股份有限公司 | Diagnostic database determination method, diagnostic database determination device, electronic equipment and storage medium |
| CN114407812B (en) * | 2022-01-12 | 2024-05-03 | 中国第一汽车股份有限公司 | Diagnostic database determination method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108563214B (en) | Vehicle diagnosis method, device and equipment | |
| EP3722901B1 (en) | Vehicle trouble diagnosis method and vehicle trouble diagnosis apparatus | |
| CN109976314B (en) | Method and system for inquiring fault code maintenance case | |
| US11238676B2 (en) | Automated vehicle scan tool initialization | |
| CN104937557A (en) | Methods and systems for utilizing repair orders in determining diagnostic repairs | |
| US20220277599A1 (en) | Supplementing Vehicle Service Content with Scan Tool Initialization Links | |
| CN111708353A (en) | Data display method and system for vehicle diagnosis equipment and related equipment | |
| CN113608518A (en) | Data generation method, device, terminal equipment and medium | |
| CN114407812B (en) | Diagnostic database determination method, device, electronic equipment and storage medium | |
| CN111693294A (en) | Vehicle detection method and device, terminal equipment and storage medium | |
| CN113787977A (en) | Vehicle maintenance method, communication device, and storage medium | |
| US20200184744A1 (en) | Vehicle Scan Tool Configured to Receive Automated Initialization Requests | |
| KR101980112B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980116B1 (en) | Apparatus and method for uploading a wiring design request | |
| CN112306040A (en) | Vehicle detection method, device, equipment and server | |
| KR101956902B1 (en) | Apparatus and method for uploading a wiring design request | |
| WO2020123608A1 (en) | Automated vehicle scan tool initialization | |
| CN112099471B (en) | Vehicle power type judgment method and device, terminal device and storage medium | |
| KR101980122B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980117B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980119B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980118B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980114B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980121B1 (en) | Apparatus and method for uploading a wiring design request | |
| KR101980115B1 (en) | Apparatus and method for uploading a wiring design request |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211214 |
|
| RJ01 | Rejection of invention patent application after publication |