Vehicle diagnosis method and device, vehicle and diagnosis equipment

Abstract

The invention belongs to the technical field of vehicles, and particularly relates to a vehicle diagnosis method and device, a vehicle and diagnosis equipment. The method comprises the steps of receiving a data request instruction under the condition that a vehicle is in a simulation mode; the simulation mode is a working mode for interacting with diagnosis equipment based on simulation data; determining target simulation data corresponding to the data request instruction; sending the target simulation data to the diagnosis equipment; the target simulation data is used for indicating the diagnosis equipment to carry out vehicle diagnosis based on the target simulation data. According to the method, the simulation data can be utilized to interact with the diagnosis equipment, so that the ECU does not need to perform actual data acquisition, and the scene adaptability of the vehicle diagnosis method can be improved.

Description

Technical Field

[0001] This application belongs to the technical field of vehicles, and particularly relates to a vehicle diagnosis method, device, vehicle, and diagnosis equipment. Background Art

[0002] Currently, vehicle diagnosis methods mainly rely on the communication interaction between a diagnosis device and a vehicle electronic control unit (ECU) to complete. The diagnosis device sends instructions to the ECU to request vehicle-related data, and the ECU collects relevant data through sensors and feeds the collected data back to the diagnosis device. It can be seen that the existing vehicle diagnosis method is a method set under actual operating conditions. In situations such as simulation exercises or offline operations where it is not desired for operators to perform actual operations on the ECU, the existing vehicle diagnosis method will be difficult to apply. Therefore, there is an urgent need for a vehicle diagnosis method that does not require actual operation on the ECU. Summary of the Invention

[0003] In view of this, embodiments of this application provide a vehicle diagnosis method, device, vehicle, and diagnosis equipment to solve the problem in the prior art of lacking a vehicle diagnosis method that does not require actual operation on the ECU.

[0004] The first aspect of the embodiments of this application provides a vehicle diagnosis method applied to a vehicle, which may include:

[0005] Enter the simulation mode when receiving a simulation mode switching instruction; the simulation mode is a working mode of interacting with a diagnosis device based on simulation data;

[0006] Receive a data request instruction;

[0007] Determine target simulation data corresponding to the data request instruction;

[0008] Send the target simulation data to the diagnosis device; the target simulation data is used to instruct the diagnosis device to perform vehicle diagnosis based on the target simulation data.

[0009] The second aspect of the embodiments of this application provides a vehicle diagnosis method applied to a diagnosis device, which may include:

[0010] Send a simulation mode switching instruction to the vehicle; the simulation mode switching instruction is used to instruct the vehicle to enter the simulation mode;

[0011] Send a data request instruction to the vehicle; the data request instruction is used to request target simulation data from the vehicle;

[0012] Perform vehicle diagnosis on the vehicle based on the target simulation data when receiving the target simulation data.

[0013] The third aspect of the embodiments of the present application provides a vehicle diagnostic device for a vehicle, which may include:

[0014] A mode entry module, configured to enter a simulation mode when receiving a simulation mode switching instruction; the simulation mode is a working mode for interacting with a diagnostic device based on simulation data;

[0015] An instruction receiving module, configured to receive a data request instruction;

[0016] A data determination module, configured to determine target simulation data corresponding to the data request instruction;

[0017] A data sending module, configured to send the target simulation data to the diagnostic device; the target simulation data is used to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data.

[0018] The fourth aspect of the embodiments of the present application provides a vehicle diagnostic device for a diagnostic device, which may include:

[0019] An instruction sending module, configured to send a simulation mode switching instruction to the vehicle; the simulation mode switching instruction is used to instruct the vehicle to enter the simulation mode;

[0020] A request sending module, configured to send a data request instruction to the vehicle; the data request instruction is used to request target simulation data from the vehicle;

[0021] A vehicle diagnosis module, configured to perform vehicle diagnosis on the vehicle based on the target simulation data when receiving the target simulation data.

[0022] The fifth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of any of the above vehicle diagnosis methods are implemented.

[0023] The sixth aspect of the embodiments of the present application provides a diagnostic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the diagnostic device implements the steps of any of the above vehicle diagnosis methods for a diagnostic device.

[0024] The seventh aspect of the embodiments of the present application provides a vehicle, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the vehicle implements the steps of any of the above vehicle diagnosis methods for a vehicle.

[0025] The eighth aspect of the embodiments of the present application provides a computer program product, including a computer program, which when run, causes any of the above vehicle diagnostic methods to be executed.

[0026] The beneficial effects of the embodiments of the present application compared with the prior art are as follows: When the vehicle is in the simulation mode, the embodiments of the present application receive a data request instruction; the simulation mode is a working mode of interacting with a diagnostic device based on simulation data; determine target simulation data corresponding to the data request instruction; send the target simulation data to the diagnostic device; the target simulation data is used to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data. In the embodiments of the present application, interaction can be carried out with the diagnostic device using simulation data, so that the ECU does not need to perform actual data collection, which helps to improve the scenario adaptability of the vehicle diagnostic method. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0028] Figure 1 It is a schematic diagram of the application scenario for vehicle diagnosis;

[0029] Figure 2 It is a flowchart of an embodiment of a vehicle diagnostic method applied to a diagnostic device in the embodiments of the present application;

[0030] Figure 3 It is a flowchart of an embodiment of a vehicle diagnostic method applied to a vehicle in the embodiments of the present application;

[0031] Figure 4 It is a structural diagram of an embodiment of a vehicle diagnostic device applied to a vehicle in the embodiments of the present application;

[0032] Figure 5 It is a structural diagram of an embodiment of a vehicle diagnostic device applied to a diagnostic device in the embodiments of the present application;

[0033] Figure 6 It is a schematic block diagram of a vehicle in the embodiments of the present application;

[0034] Figure 7 It is a schematic block diagram of a diagnostic device in the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0035] To make the objectives, features, and advantages of the present application more apparent and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the embodiments described below are only a part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.

[0036] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0037] It should also be understood that the terms used in this specification of the present application are merely for the purpose of describing specific embodiments and are not intended to limit the present application. As used in this specification of the present application and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms.

[0038] It should be further understood that the term "and / or" used in this specification of the present application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0039] As used in this specification and the appended claims, the term "if" can be interpreted as "when", "once", "in response to determining", or "in response to detecting" according to the context. Similarly, the phrase "if determined" or "if [the described condition or event] is detected" can be interpreted as meaning "once determined", "in response to determining", "once [the described condition or event] is detected", or "in response to detecting [the described condition or event]" according to the context.

[0040] In addition, in the description of the present application, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be understood as indicating or implying relative importance.

[0041] Currently, vehicle diagnosis methods mainly rely on the communication interaction between the diagnostic device and the vehicle electronic control unit (Electronic Control Unit, ECU) to complete, such as Figure 1As shown in the figure, the diagnostic device sends an instruction to the ECU to request vehicle-related data, and the ECU collects relevant data through sensors and feeds back the collected data to the diagnostic device. It can be seen that the existing vehicle diagnostic method is a method set under actual operating conditions. In applications such as the R & D process and education and training, situations where simulation exercises or offline operations are performed and it is not desired for operators to perform actual operations on the ECU often occur. In these situations, the existing vehicle diagnostic method will be difficult to apply. Therefore, there is an urgent need for a vehicle diagnostic method that does not require actual operation on the ECU.

[0042] In view of this, the embodiments of the present application provide a vehicle diagnostic method, device, vehicle, and diagnostic device to solve the problem in the prior art of the lack of a vehicle diagnostic method that does not require actual operation on the ECU.

[0043] In actual use, the ECU in the vehicle can collect data through various sensors in the vehicle and can analyze and make decisions on the collected data. When performing vehicle diagnosis, the device for vehicle diagnosis (hereinafter referred to as the diagnostic device) can establish a communication connection with the ECU through a preset communication link. The ECU can, according to the request of the diagnostic device, reply to the diagnostic device with the collected data so that the diagnostic device can perform vehicle diagnosis on the vehicle based on the received data.

[0044] The above communication link can be a communication link established by any one of communication solutions such as a serial communication protocol, a Controller Area Network (CAN) bus communication protocol, a Local Interconnect Network (LIN) bus communication protocol, Ethernet communication, or wireless communication. The embodiments of the present application do not make any limitations in this regard.

[0045] In the embodiments of the present application, in situations such as simulation exercises or offline operations where it is not desired for operators to perform actual operations on the ECU, the ECU can interact with the diagnostic device based on simulation data. For the sake of convenience of description, the working mode in which the ECU interacts with the diagnostic device based on simulation data will be referred to as the simulation mode hereinafter, and the process of performing vehicle diagnosis in the simulation mode will be referred to as the simulation vehicle diagnosis process. In contrast, the working mode in which the ECU interacts with the diagnostic device based on the normally collected data can also be referred to as the normal mode, and the process of performing vehicle diagnosis in the normal mode will be referred to as the real vehicle diagnosis process.

[0046] When the ECU needs to perform vehicle diagnosis in the normal mode, the diagnostic device can instruct the ECU to enter the normal mode. Specifically, the diagnostic device can send a normal mode switching instruction to the vehicle's ECU. After receiving this normal mode switching instruction, the ECU can enter the normal mode and perform real vehicle diagnosis in this mode. When the ECU needs to perform vehicle diagnosis in the simulation mode, the diagnostic device can instruct the ECU to enter the simulation mode. Specifically, the diagnostic device can send a simulation mode switching instruction to the vehicle's ECU. After receiving this simulation mode switching instruction, the ECU can enter the simulation mode and simulate the interaction of vehicle diagnosis in this mode. In the simulation mode, the internal data of the ECU will not be modified, which can ensure the integrity of the ECU data.

[0047] By setting two different working modes, it can better adapt to different vehicle diagnosis scenarios, which helps to improve the usability and scenario adaptability of the vehicle diagnosis method.

[0048] In the embodiment of the present application, vehicle data in the normal mode (hereinafter referred to as historical vehicle data) can also be collected, so that in the simulation mode, the interaction between the ECU and the diagnostic device can be based on the real historical vehicle data. Accordingly, it can better imitate the real vehicle diagnosis scenario and provide a suitable solution for vehicle diagnosis in scenarios such as simulation practice and offline operation.

[0049] Specifically, when performing vehicle diagnosis in the normal mode, the ECU can store the data requests of the diagnostic device and the vehicle data replied by the ECU. After entering the simulation mode, the ECU can determine appropriate reply data from the stored historical vehicle data according to the data requests of the diagnostic device and use this vehicle data for reply.

[0050] In a specific implementation manner, the vehicle data of a real vehicle diagnosis process can be saved as a corresponding historical vehicle data file. The vehicle data of different real vehicle diagnosis processes can be saved as different historical vehicle data files respectively. Each historical vehicle data file can include various request contents and corresponding reply data in the corresponding real vehicle diagnosis process.

[0051] For example, during a real vehicle diagnosis process, the diagnostic device sends request content 1 to the vehicle to request relevant data from the vehicle ECU, and the vehicle ECU replies to the diagnostic device with reply data 1; afterwards, the diagnostic device sends request content 2 to the vehicle to request relevant data from the vehicle ECU, and the vehicle ECU replies to the diagnostic device with reply data 2; afterwards, the diagnostic device sends request content 3 to the vehicle to request relevant data from the vehicle ECU, and the vehicle ECU replies to the diagnostic device with reply data 3; based on this, it can be determined that the historical vehicle data file corresponding to this real vehicle diagnosis process includes request content 1 and the corresponding reply data 1, request content 2 and the corresponding reply data 2, and request content 3 and the corresponding reply data 3.

[0052] In the above implementation, the naming of each historical vehicle data file can include the vehicle unique identifier (such as the Vehicle Identification Number (VIN)) in the corresponding real vehicle diagnosis process, the name of the ECU, and the time of the real vehicle diagnosis process. Accordingly, the historical vehicle data used in the simulated vehicle diagnosis process can be determined based on the naming of the historical vehicle data file.

[0053] As an example, vehicle 1 with a VIN of 4127 underwent a real vehicle diagnosis process at 12:00 on January 1, 2025. The name of the ECU of vehicle 1 is ECU164. Then, the historical vehicle data file corresponding to this real vehicle diagnosis process can be named: 4127-ECU164-202501011200. Based on the name of this historical vehicle data file, the vehicle, ECU, and diagnosis time of this real vehicle diagnosis process can be determined.

[0054] Next, the vehicle diagnosis method in the embodiments of the present application will be introduced from the perspectives of the diagnostic device and the vehicle respectively.

[0055] It should be noted that the diagnostic device in the embodiments of the present application can specifically be a general diagnostic device, a special diagnostic device, or a multi-functional diagnostic device, or other common diagnostic devices; the vehicle in the embodiments of the present application can specifically be a fuel vehicle, an electric vehicle, a hybrid vehicle, etc. There is an ECU running on the vehicle, and the ECU can collect vehicle data and control the vehicle based on the vehicle data.

[0056] Specifically, please refer to Figure 2 , an embodiment of a vehicle diagnosis method applied to a diagnostic device in the embodiments of the present application may include steps S201 to S203:

[0057] Step S201: Send a simulation mode switching instruction to the vehicle.

[0058] When vehicle diagnosis is required in the simulation mode, the user can trigger a corresponding instruction on the diagnostic device (such as clicking on the corresponding control on the display interface of the diagnostic device) to trigger the diagnostic device to send a simulation mode switching instruction to the vehicle. The simulation mode switching instruction is used to instruct the vehicle to enter the simulation mode.

[0059] In the simulation mode, the vehicle will interact with the diagnostic device based on the target simulation data; where the target simulation data is the simulation data required by the diagnostic device. In the embodiments of the present application, the target simulation data may include historical vehicle data; correspondingly, the vehicle can interact with the diagnostic device based on the historical vehicle data; the target simulation data may also include algorithm-generated data, that is, vehicle data generated in real time according to a preset data generation algorithm; correspondingly, the vehicle can interact with the diagnostic device based on the algorithm-generated data.

[0060] Specifically, the simulation mode of the vehicle specifically includes a first mode and a second mode. In the first mode, the vehicle will interact with the diagnostic device based on historical vehicle data; in the second mode, the vehicle will interact with the diagnostic device based on the vehicle data obtained from real-time simulation.

[0061] When the vehicle is in the simulation mode, the diagnostic device can send a first mode switching instruction to the vehicle to instruct the vehicle to enter the first mode; in the first mode, the diagnostic device can receive a list of historical vehicle data files sent by the vehicle, and the list of historical vehicle data files may include at least one historical vehicle data file.

[0062] After that, the diagnostic device can determine the historical vehicle data file required for the simulation vehicle diagnosis process (hereinafter referred to as the target historical vehicle data file) from the list of historical vehicle data files. Based on the target historical vehicle data file, the diagnostic device can send a data determination instruction to the vehicle, and the data determination instruction can indicate the target historical vehicle data file, so that the vehicle can determine the target historical vehicle data file and interact with the diagnostic device based on the target historical vehicle data file.

[0063] For example, the list of historical vehicle data files may include historical vehicle data file 1, historical vehicle data file 2, historical vehicle data file 3, and historical vehicle data file 4, and the names of each historical vehicle data file are 4127-ECU164-202501011200, 4127-ECU164-202501020525, 4127-ECU164-202501100845, 4127-ECU164-202501131820; if the user needs to perform simulation based on the historical vehicle data on January 13, 2025, the corresponding instruction can be triggered through the diagnostic device to determine historical vehicle data file 4 as the target historical vehicle data file.

[0064] Alternatively, when the vehicle is in the simulation mode, the diagnostic device may send a second mode switching instruction to the vehicle to instruct the vehicle to enter the second mode; in the second mode, the diagnostic device may receive at least one available data generation algorithm sent from the vehicle, and the available data generation algorithm is an algorithm used to generate simulation data.

[0065] After that, the diagnostic device may determine a data generation algorithm used in the simulation vehicle diagnosis process (hereinafter referred to as the target data generation algorithm) from each available data generation algorithm. Based on the target data generation algorithm, the diagnostic device may send an algorithm determination instruction to the vehicle, and the algorithm determination instruction may indicate the target data generation algorithm corresponding to the target simulation data, so that the vehicle may generate target simulation data according to the target data generation algorithm and may interact with the diagnostic device based on the generated target simulation data.

[0066] In a specific implementation manner of the embodiment of the present application, the algorithm determination instruction may include a diagnostic identifier (Diagnostic Identifier, DID) of the target simulation data, which is used to identify the encoding of the ECU internal parameters. Through the DID of the data, each data item inside the ECU can be uniquely identified and accessed.

[0067] Here, the available data generation algorithms may include, but are not limited to, algorithms such as linear algorithms, sine algorithms, arithmetic difference algorithms, and triangular wave algorithms.

[0068] Step S202: Send a data request instruction to the vehicle.

[0069] Step S203: When the target simulation data is received, perform vehicle diagnosis on the vehicle based on the target simulation data.

[0070] In the embodiment of the present application, the diagnostic device may request data of various parts of the vehicle from the ECU of the vehicle and may perform vehicle diagnosis according to the vehicle data sent by the vehicle ECU.

[0071] Here, the data of various parts of the vehicle may include, but are not limited to, one or more data items such as vehicle speed, driving mileage, fuel consumption rate, engine speed, oil temperature, fuel pressure, coolant temperature, intake air temperature, tire pressure, and battery voltage.

[0072] Specifically, the diagnostic device may determine a target request content according to the vehicle data (hereinafter referred to as the target simulation data) required for the simulation vehicle diagnosis process and may send a data request to the vehicle based on the target request content, and the data request instruction is used to request the vehicle for the target simulation data.

[0073] In a specific implementation manner of the embodiment of the present application, the target request content may be the DID of vehicle data, and based on the DID, a unique data item (target simulation data) can be determined.

[0074] When the diagnostic device receives the target simulation data, vehicle diagnosis can be performed on the vehicle based on the target simulation data.

[0075] As an example, the diagnostic device can determine whether the vehicle is operating normally based on the target simulation data; specifically, the target simulation data can be compared with a preset normal range. If the target simulation data is within this normal range, it can be considered that the vehicle is operating normally; if the target simulation data is outside this normal range, it can be considered that the vehicle is not operating normally (i.e., operating abnormally).

[0076] In a specific implementation manner of the embodiment of the present application, if the target simulation data is not received within a preset time period after sending the data request instruction, the data request instruction can be sent to the vehicle again to request simulation data from the vehicle, or to request other simulation data from the vehicle.

[0077] In another specific implementation manner of the embodiment of the present application, if invalid data sent by the vehicle is received, it can be considered that the ECU does not have the target simulation data corresponding to the data request instruction. At this time, the request for the target simulation data can be abandoned.

[0078] When it is necessary to end the simulation vehicle diagnosis process, the diagnostic device can send a normal mode switching instruction to the vehicle to instruct the vehicle to switch to the normal mode.

[0079] Next, the vehicle diagnosis method of the embodiment of the present application will be described from the perspective of the vehicle; specifically, please refer to Figure 3 , an embodiment of a vehicle diagnosis method applied to a vehicle in the embodiment of the present application may include steps S301 to S303:

[0080] Step S301, when receiving a simulation mode switching instruction, enter the simulation mode.

[0081] After receiving the simulation mode switching instruction sent by the diagnostic device, the vehicle ECU can enter the simulation mode. In the simulation mode, the ECU can interact with the diagnostic device based on the simulation data to complete vehicle diagnosis.

[0082] Specifically, the simulation mode may include a first mode and a second mode. In the first mode, the vehicle can determine target simulation data from the target historical vehicle data file determined by the diagnostic device, and can interact with the diagnostic device based on the target simulation data. In the second mode, the vehicle can generate target simulation data in real time based on the target data generation algorithm determined by the diagnostic device, and can interact with the diagnostic device based on the target simulation data.

[0083] After the vehicle is in the simulation mode, the diagnostic device can further indicate the specific simulation mode. If the vehicle receives a first mode switching instruction from the diagnostic device, it can determine that the specific simulation mode is the first mode. If the vehicle receives a second mode switching instruction from the diagnostic device, it can determine that the specific simulation mode is the second mode.

[0084] When the vehicle is in the first mode, the vehicle can send a list of historical vehicle data files to the diagnostic device. The list of historical vehicle data files includes the names of at least one historical vehicle data file, so that the diagnostic device can determine the historical vehicle data file used in the simulation vehicle diagnosis process based on the need.

[0085] After receiving the data determination instruction sent by the diagnostic device, the data determination instruction can be parsed to obtain data determination instruction parsing information, and the target historical vehicle file data determined by the diagnostic device can be determined from the parsing information. After the subsequent simulation vehicle diagnosis process, the target simulation data can be determined according to the target historical vehicle file data.

[0086] When the vehicle is in the second mode, the vehicle can send each available data generation algorithm to the diagnostic device, so that the diagnostic device can determine the data generation algorithm used in the simulation vehicle diagnosis process.

[0087] After receiving the algorithm determination instruction sent by the diagnostic device, the algorithm determination instruction can be parsed to obtain algorithm determination instruction parsing information, and the target data generation algorithm determined by the diagnostic device can be determined from the parsing information. After the subsequent simulation vehicle diagnosis process, the target simulation data can be constructed in real time according to the target data generation algorithm.

[0088] Step S302: Receive a data request instruction.

[0089] Step S303: Determine the target simulation data corresponding to the data request instruction.

[0090] After receiving the data request instruction sent by the diagnostic device, the data request instruction can be parsed to obtain the data request instruction parsing information. Based on this data request instruction parsing information, the target simulation data required by the diagnostic device can be determined. Specifically, the data request instruction parsing information includes the target request content, and based on the target request content, the target simulation data required by the diagnostic device can be determined.

[0091] Specifically, if the vehicle is in the first mode, the target simulation data is the response data corresponding to the target request content in the target historical vehicle data file. Here, based on the target request content, a match can be made in the target historical vehicle data file. If a request content identical to the target request content is matched, the response data corresponding to this request content can be determined as the target simulation data. If no request content identical to the target request content is matched, no response can be made, or the default invalid data can be determined as the target simulation data, so that the diagnostic device can know that there is no simulation data corresponding to the data request instruction in the target historical vehicle data file.

[0092] For example, the target historical vehicle data file includes request content 1 and the corresponding response data 1, request content 2 and the corresponding response data 2, request content 3 and the corresponding response data 3. If the data request instruction parsing information includes request content 3, according to the target historical vehicle data file, it can be determined that the response data corresponding to request content 3 is response data 3, then response data 3 can be determined as the target simulation data; if the data request instruction parsing information includes request content 4, and since the target historical vehicle data file does not include request content 4 and the corresponding response data, therefore, the default invalid data can be determined as the target simulation data to indicate that there is no simulation data corresponding to the data request instruction in the target historical vehicle data file.

[0093] If the vehicle is in the second mode, the target simulation data is the vehicle data generated in real time; specifically, based on the target request content in the data request instruction parsing information, the target simulation data required by the diagnostic device can be determined; for example, DID of 0x0201 represents engine speed, DID of 0x0802 represents voltage value, and DID of 0xFFFF can represent all data items. If the DID included in the target request content is 0x0201, then the target simulation data can be determined as the engine speed.

[0094] After that, based on the target data generation algorithm, the target simulation data can be generated.

[0095] As an example, if the target data generation algorithm is a linear algorithm, the target simulation data can be calculated according to Y = X * A + B; where Y is the target simulation data, X is the number of requests for the target simulation data. When the diagnostic device requests the target simulation data for the first time, X is 1. When the diagnostic device requests the target simulation data for the second time, X is 2, and so on; A is the first algorithm parameter, B is the second algorithm parameter, and the specific values of A and B can be set according to actual needs, which are not limited in the embodiments of the present application; for example, the value of A can be set to 10, and the value of B can be set to 50. When the diagnostic device requests the target simulation data for the first time, Y = 1 * 10 + 50 = 60 can be calculated, that is, the target simulation data is 60; when the diagnostic device requests the target simulation data for the second time, Y = 2 * 10 + 50 = 70 can be calculated, that is, the target simulation data is 70.

[0096] Step S304: Send the target simulation data to the diagnostic device.

[0097] After determining the target simulation data, the vehicle can send the target simulation data to the diagnostic device to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data.

[0098] In addition, when it is necessary to end the simulation vehicle diagnosis process, the diagnostic device can also send a normal mode switching instruction to the vehicle to instruct the vehicle to switch to the normal mode and end the simulation process.

[0099] In summary, in the embodiments of the present application, when the vehicle is in the simulation mode, a data request instruction is received; the simulation mode is a working mode of interacting with the diagnostic device based on simulation data; the target simulation data corresponding to the data request instruction is determined; the target simulation data is sent to the diagnostic device; the target simulation data is used to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data. In the embodiments of the present application, interaction with the diagnostic device can be carried out using simulation data, so that the ECU does not need to perform actual data collection, which helps to improve the scenario adaptability of the vehicle diagnosis method.

[0100] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0101] Corresponding to the vehicle diagnosis method described in the above embodiments, Figure 4 FIG. shows a structural diagram of an embodiment of a vehicle diagnosis device applied to a vehicle provided by an embodiment of the present application.

[0102] In the embodiments of the present application, a vehicle diagnosis device applied to a vehicle may include:

[0103] A mode entry module 401, configured to enter a simulation mode when receiving a simulation mode switching instruction; the simulation mode is a working mode of interacting with a diagnostic device based on simulation data;

[0104] An instruction receiving module 402, configured to receive a data request instruction;

[0105] A data determination module 403, configured to determine target simulation data corresponding to the data request instruction;

[0106] A data sending module 404, configured to send the target simulation data to the diagnostic device; the target simulation data is used to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data.

[0107] In a specific implementation manner of an embodiment of the present application, the simulation data includes historical vehicle data;

[0108] The device further includes:

[0109] A determination instruction receiving module, configured to receive a data determination instruction;

[0110] A file determination module, configured to determine a target historical vehicle data file corresponding to the data determination instruction;

[0111] The data determination module includes:

[0112] A data determination sub-module, configured to determine the target simulation data corresponding to the data request instruction from the target historical vehicle data file.

[0113] In a specific implementation manner of an embodiment of the present application, the device further includes:

[0114] An algorithm instruction receiving module, configured to receive an algorithm determination instruction;

[0115] An algorithm determination module, configured to determine a target data generation algorithm corresponding to the algorithm determination instruction;

[0116] The data determination module includes:

[0117] A simulation data determination sub-module, configured to determine the target simulation data corresponding to the data request instruction based on the target data generation algorithm.

[0118] Corresponding to the vehicle diagnosis method described in the above embodiment, Figure 5 FIG. shows a structural diagram of an embodiment of a vehicle diagnosis device applied to a diagnostic device provided by an embodiment of the present application.

[0119] In an embodiment of the present application, a vehicle diagnosis device applied to a diagnostic device may include:

[0120] An instruction sending module 501 is configured to send a simulation mode switching instruction to a vehicle; the simulation mode switching instruction is used to instruct the vehicle to enter a simulation mode.

[0121] A request sending module 502 is configured to send a data request instruction to the vehicle; the data request instruction is used to request target simulation data from the vehicle.

[0122] A vehicle diagnosis module 503 is configured to perform vehicle diagnosis on the vehicle based on the target simulation data when the target simulation data is received.

[0123] In a specific implementation manner of the embodiment of the present application, the device further includes:

[0124] A list receiving module is configured to receive a historical vehicle data file list sent by the vehicle; the historical vehicle data file list includes at least one historical vehicle data file.

[0125] A file determining module is configured to determine a target historical vehicle data file from the historical vehicle data file list.

[0126] A determination instruction sending module is configured to send a data determination instruction to the vehicle; the data determination instruction is used to indicate the target historical vehicle data file.

[0127] In a specific implementation manner of the embodiment of the present application, the device further includes:

[0128] An algorithm receiving module is configured to receive at least one available data generation algorithm sent by the vehicle.

[0129] An algorithm determining module is configured to determine a target data generation algorithm corresponding to the target simulation data from each of the available data generation algorithms.

[0130] An algorithm instruction sending module is configured to send an algorithm determination instruction to the vehicle; the data determination instruction is used to indicate the target data generation algorithm corresponding to the target simulation data.

[0131] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described device, modules, and units can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0132] In the above embodiments, the descriptions of the respective embodiments have their own focuses. For parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0133] Figure 6The figure shows a schematic block diagram of a vehicle provided by an embodiment of the present application. For ease of description, only parts related to the embodiment of the present application are shown.

[0134] As Figure 6 shown, the vehicle 6 of this embodiment includes: a processor 60, a memory 61, and a computer program 62 stored in the memory 61 and executable on the processor 60. When the processor 60 executes the computer program 62, it implements the steps in each of the above embodiments of the vehicle diagnosis method, such as Figure 2 the steps S301 to S304 shown. Alternatively, when the processor 60 executes the computer program 62, it implements the functions of each module / unit in each of the above device embodiments, such as Figure 4 the functions of the modules 401 to 404 shown.

[0135] Exemplarily, the computer program 62 can be divided into one or more modules / units. The one or more modules / units are stored in the memory 61 and executed by the processor 60 to complete the present application. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, and these instruction segments are used to describe the execution process of the computer program 62 in the vehicle 6.

[0136] Those skilled in the art can understand that Figure 6 merely examples of the vehicle 6, which do not constitute a limitation on the vehicle 6. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the vehicle 6 may further include input / output devices, network access devices, buses, etc.

[0137] The processor 60 may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0138] The memory 61 may be an internal storage unit of the vehicle 6, such as a hard disk or memory of the vehicle 6. The memory 61 may also be an external storage device of the vehicle 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the vehicle 6. Further, the memory 61 may also include both the internal storage unit of the vehicle 6 and an external storage device. The memory 61 is used to store the computer program and other programs and data required by the vehicle 6. The memory 61 may also be used to temporarily store data that has been output or is to be output.

[0139] Figure 7 The schematic block diagram of a diagnostic device provided by an embodiment of the present application is shown. For ease of description, only parts related to the embodiment of the present application are shown.

[0140] As Figure 7 shown, the diagnostic device 7 of this embodiment includes: a processor 70, a memory 71, and a computer program 72 stored in the memory 71 and executable on the processor 70. When the processor 70 executes the computer program 72, the steps in the above-mentioned various embodiments of the vehicle diagnostic method are implemented, such as Figure 2 the steps S201 to S203 shown. Alternatively, when the processor 70 executes the computer program 72, the functions of each module / unit in the above-mentioned various device embodiments are implemented, such as Figure 5 the functions of the modules 501 to 503 shown.

[0141] Exemplarily, the computer program 72 may be divided into one or more modules / units. The one or more modules / units are stored in the memory 71 and executed by the processor 70 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, and this instruction segment is used to describe the execution process of the computer program 72 in the diagnostic device 7.

[0142] Those skilled in the art can understand that Figure 7 it is only an example of the diagnostic device 7 and does not constitute a limitation on the diagnostic device 7. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, the diagnostic device 7 may also include input / output devices, network access devices, buses, etc.

[0143] The processor 70 may be a Central Processing Unit (CPU), or may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0144] The memory 71 may be an internal storage unit of the diagnostic device 7, such as the hard disk or memory of the diagnostic device 7. The memory 71 may also be an external storage device of the diagnostic device 7, such as a plug-in hard disk equipped on the diagnostic device 7, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. Further, the memory 71 may also include both an internal storage unit and an external storage device of the diagnostic device 7. The memory 71 is used to store the computer program and other programs and data required by the diagnostic device 7. The memory 71 may also be used to temporarily store data that has been output or is to be output.

[0145] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional unit and module is used as an example. In practical applications, the above functions can be allocated to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiments can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working processes of the units and modules in the above system can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated here.

[0146] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0147] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0148] In the embodiments provided in this application, it should be understood that the disclosed device / diagnostic device and method can be implemented in other ways. For example, the device / diagnostic device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical, or other form.

[0149] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0150] In addition, the functional units in each embodiment of this application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0151] When the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, to implement all or part of the processes in the above-described embodiment methods of this application, it can also be completed by a computer program instructing relevant hardware. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-described various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable storage medium can include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disc, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable storage medium does not include electrical carrier signals and telecommunication signals.

[0152] The above-described embodiments are only used to illustrate the technical solutions of this application, rather than to limit them; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A vehicle diagnostic method, characterized in that: Applied to a vehicle, the method comprises: When receiving a simulation mode switching instruction, entering the simulation mode; the simulation mode is a working mode for interacting with the diagnostic device based on simulation data; receiving a data request instruction; Determining target simulation data corresponding to the data request instruction; The target simulation data is sent to the diagnostic device; the target simulation data is used to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data.

2. The vehicle diagnostic method according to claim 1, characterized in that: The simulation data includes historical vehicle data; Before determining the target simulation data corresponding to the data request instruction, the method further includes: receiving a data confirmation instruction; determining a target historical vehicle data file corresponding to the data determination instruction; The determining of the target simulation data corresponding to the data request instruction comprises: The target simulation data corresponding to the data request instruction is determined from the target historical vehicle data file.

3. The vehicle diagnostic method according to claim 1, characterized in that: The simulation data includes algorithm-generated data; Before determining the target simulation data corresponding to the data request instruction, the method further includes: receiving an algorithm-determined instruction; determining a target data generation algorithm corresponding to the algorithm determination instruction; The determining of the target simulation data corresponding to the data request instruction comprises: Based on the target data generation algorithm, the target simulation data corresponding to the data request instruction is determined.

4. A vehicle diagnostic method, characterized in that: Applied to diagnostic equipment, the method comprises: Sending a simulation mode switching instruction to the vehicle; the simulation mode switching instruction is used to instruct the vehicle to enter the simulation mode; Sending a data request instruction to the vehicle; the data request instruction is used to request target simulation data from the vehicle; When the target simulation data is received, vehicle diagnosis is performed on the vehicle based on the target simulation data.

5. The vehicle diagnostic method according to claim 4, characterized in that: Before sending the data request instruction to the vehicle, the method further includes: Receiving a historical vehicle data file list sent by the vehicle; the historical vehicle data file list includes at least one historical vehicle data file; Determine a target historical vehicle data file from the historical vehicle data file list; A data determination instruction is sent to the vehicle; the data determination instruction is used to indicate the target historical vehicle data file.

6. The vehicle diagnostic method according to claim 4, characterized in that: Before sending the data request instruction to the vehicle, the method further includes: receiving at least one available data generating algorithm sent by the vehicle; Determine a target data generation algorithm corresponding to the target simulation data from each of the available data generation algorithms; An algorithm determination instruction is sent to the vehicle; the data determination instruction is used to indicate the target data generation algorithm corresponding to the target simulation data.

7. A vehicle diagnostic device, characterized in that: Applied to a vehicle, the device comprises: A mode entry module, used to enter the simulation mode when receiving a simulation mode switching instruction; the simulation mode is a working mode for interacting with the diagnostic device based on simulation data; An instruction receiving module, used for receiving a data request instruction; A data determination module, used for determining target simulation data corresponding to the data request instruction; A data sending module is used to send the target simulation data to the diagnostic device; the target simulation data is used to instruct the diagnostic device to perform vehicle diagnosis based on the target simulation data.

8. A vehicle diagnostic device, characterized in that: Applied to diagnostic equipment, the device comprises: An instruction sending module, used for sending a simulation mode switching instruction to the vehicle; the simulation mode switching instruction is used for instructing the vehicle to enter the simulation mode; A request sending module, used for sending a data request instruction to the vehicle; the data request instruction is used for requesting target simulation data from the vehicle; The vehicle diagnosis module is used to perform vehicle diagnosis on the vehicle based on the target simulation data when the target simulation data is received.

9. A vehicle comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the vehicle implements the steps of the vehicle diagnosis method according to any one of claims 1 to 3.

10. A diagnostic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the diagnostic device implements the steps of the vehicle diagnostic method according to any one of claims 4 to 6.

Images