CN114415631A - Diagnostic tool based ECU (electronic control Unit) diagnostic method and diagnostic tool - Google Patents

Abstract

The invention discloses an ECU diagnosis method and a diagnosis tool based on a diagnosis tool, comprising: a request message generation module submits a target diagnosis request list to a user equipment through an interaction module, receives a designated diagnosis request identifier through the interaction module, and obtains a target diagnosis from a diagnosis management module Request message parameters and target request message structure, provide target request message parameters to the user equipment through the interaction module, receive request message parameter values fed back by the user equipment through the interaction module, according to the target request message structure and request message parameter values Generate a diagnosis request message, and send the diagnosis request message to the ECU to be diagnosed; the response message parsing module receives the diagnosis response message corresponding to the diagnosis request message sent by the ECU to be diagnosed, and sends the diagnosis response message to the diagnosis management module. Receive the target response message structure sent by the diagnosis management module, parse the diagnosis response message according to the target response message structure, and provide the analysis result to the user equipment through the interaction module.

Description

ECU Diagnosis Method and Diagnosis Tool Based on Diagnosis Tool

technical field

The invention relates to the technical field of automobiles, and in particular, to an ECU diagnosis method and a diagnosis tool based on a diagnosis tool.

Background technique

ECU (Electronic Control Unit, Electronic Control Unit) is a controller used to control a certain part of the system of the vehicle. Like an ordinary computer, it consists of a microcontroller, memory, input/output interface, analog-to-digital converter and It is composed of large-scale integrated circuits such as drivers. To describe it in a simple sentence is "ECU is the brain of the vehicle".

The diagnostic software of the ECU is an important part of its built-in program. Its task is to monitor its own hardware and software in real time, and to properly handle the various faults found, so as to ensure the safety of people and vehicles and speed up maintenance. The current ECU diagnostic solution relies on the diagnostic data of a specific ECU. Once it needs to adapt to different types of ECUs, the diagnostic data changes, resulting in the need to modify the code of the diagnostic instrument, and it needs to be rewritten and compiled to adapt to the modification, so that whether it is the first development or the second Each modification takes a long time.

SUMMARY OF THE INVENTION

The invention provides an ECU diagnosis method and a diagnosis tool based on a diagnosis tool, which can realize a decoupled ECU diagnosis software framework based on an ODX (OpenDiagnostic data exchange) file, so that when the ECU type changes, only the It only needs to load different ODX files, which improves the development efficiency, and because each module relatively independently decomposes the diagnostic requirements, the cost of the development cycle and maintenance cycle has been greatly reduced.

The specific technical solutions are as follows:

In a first aspect, an embodiment of the present invention provides an ECU diagnosis method based on a diagnosis tool. The diagnosis tool includes a database module, a diagnosis management module, a request message generation module, a response message analysis module, and an interaction module. The method include:

The request message generation module provides the user equipment with a target diagnosis request list supported by the database module through the interaction module, wherein the target diagnosis request list is based on the database module parsing the ODX file of the open diagnostic data exchange Generated from the obtained diagnosis data, the target diagnosis request list includes a diagnosis request list corresponding to the specified diagnosis service;

The request message generation module receives, through the interaction module, a designated diagnosis request identifier fed back by the user equipment, wherein the designated diagnosis request identifier is a diagnosis request identifier in a diagnosis request list corresponding to the designated diagnosis service;

The request message generation module obtains the target request message parameters and the target request message structure from the diagnosis management module, and provides the user equipment with the target request message parameters through the interaction module. The module receives the request message parameter value corresponding to the target request message parameter fed back by the user equipment, wherein the target request message parameter is the request message parameter corresponding to the specified diagnosis request identifier, and the target request message parameter The request message structure is a request message structure corresponding to the specified diagnosis request identifier, and the target request message parameters and the target request message structure stored in the diagnosis management module are stored in the database module. obtained from the diagnostic data of ;

The request message generation module generates a diagnosis request message according to the target request message structure and the request message parameter value, and sends the diagnosis request message to the ECU to be diagnosed;

The response message parsing module receives a diagnosis response message corresponding to the diagnosis request message sent by the to-be-diagnosed ECU, and sends the diagnosis response message to the diagnosis management module;

The response message parsing module receives the target response message structure sent by the diagnosis management module, parses the diagnosis response message according to the target response message structure, and sends the message to the user equipment through the interaction module. Provide a parsing result for the diagnosis response message, wherein the target response message structure is a response message structure corresponding to the diagnosis response message, and the target response message stored in the diagnosis management module The structure is obtained from the diagnostic data stored in the database module.

In an implementation manner, the request message generation module provides the user equipment with a list of target diagnosis requests supported by the database module through the interaction module, including:

The request message generation module provides the diagnosis service list obtained from the diagnosis management module to the user equipment through the interaction module, wherein the diagnosis management module obtains the diagnosis data from the database module, and generating the list of diagnostic services and a list of diagnostic requests corresponding to each diagnostic service in the list of diagnostic services according to the diagnostic data;

The request message generation module receives the specified diagnostic service fed back by the user equipment through the interaction module;

The request message generation module obtains a diagnosis request list corresponding to the specified diagnosis service from the diagnosis management module as the target diagnosis request list;

The request message generating module provides the user equipment with the target diagnosis request list through the interaction module.

In one embodiment, the diagnostic data includes at least one diagnostic service, at least one diagnostic request identifier, at least one request message parameter, at least one request message structure, at least one response message structure, diagnostic service and diagnostic request identifier The first mapping relationship, and the second mapping relationship between the diagnosis request identifier, the request message parameter and the request message structure, the diagnosis management module includes a diagnosis service management submodule and a diagnosis request management submodule;

The request message generating module provides the diagnostic service list obtained from the diagnostic management module to the user equipment through the interaction module, including: the request message generating module will generate a list of diagnostic services from the diagnostic service management sub-module. The list of diagnostic services obtained in is provided to the user equipment through the interaction module;

The request message generation module obtains a diagnosis request list corresponding to the specified diagnosis service from the diagnosis management module as the target diagnosis request list, including: the request message generation module obtains from the diagnosis request management sub-module. The diagnosis request list corresponding to the specified diagnosis service is obtained in the module as the target diagnosis request list, wherein the diagnosis request management sub-module obtains the specified diagnosis service from the diagnosis management service sub-module, and the specified diagnosis service is obtained according to the specified diagnosis service sub-module. The diagnosis service, the first mapping relationship determines the target diagnosis request list;

The request message generation module obtains the target request message parameters and the target request message structure from the diagnosis management module, including: the request message generation module obtains the target request message from the diagnosis request management sub-module parameters and the target request message structure, wherein the diagnosis request management sub-module determines the target request message parameters and the target request message structure according to the second mapping relationship and the specified diagnosis request identifier.

In one embodiment, the diagnosis data further includes a third mapping relationship between the diagnosis request identifier and the response message structure, and the diagnosis management module further includes a diagnosis response management sub-module;

The response message parsing module sending the diagnostic response message to the diagnostic management module includes: the response message parsing module sending the diagnostic response message to the diagnostic response management sub-module;

The response message parsing module receiving the target response message structure sent by the diagnosis management module includes: the response message parsing module receiving the target response message structure sent by the diagnostic response management sub-module, wherein the The diagnosis response management sub-module acquires the specified diagnosis diagnosis request identifier from the diagnosis request management sub-module, and determines a target response message structure according to the specified diagnosis request identifier and the third mapping relationship.

In one embodiment, the diagnostic response message is parsed according to the target response message structure, and the user equipment is provided with a parsing result for the diagnostic response message through the interaction module, including:

The response message parsing module parses the diagnostic response message according to the target response message structure, obtains a parsing result based on the json format, and sends the parsing result based on the json format to the interaction module;

The interaction module parses the parsing result based on the json format into an parsing result satisfying a preset parsing requirement, and feeds back the parsing result satisfying the preset parsing requirement to the user equipment.

In one embodiment, the interaction module includes a service interaction submodule and a request interaction submodule, and the request message generation module provides the diagnostic service list obtained from the diagnosis management module to the user through the interaction module. The user equipment includes: the request message generation module provides the diagnosis service list obtained from the diagnosis management module to the user equipment through the service interaction sub-module;

The request message generation module receives the specified diagnostic service fed back by the user equipment through the interaction module, including: the request message generation module receives the specified diagnostic service fed back by the user equipment through the service interaction sub-module;

The request message generation module provides the user equipment with the target diagnosis request list through the interaction module, including: the request message generation module provides the user equipment with the target through the request interaction sub-module list of diagnostic requests;

The request message generation module receives the specified diagnosis request identifier fed back by the user equipment through the interaction module, including: the request message generation module receives the specified diagnosis request fed back by the user equipment through the request interaction sub-module identification;

The request message generation module provides the user equipment with the target request message parameters through the interaction module, and receives, through the interaction module, a request message corresponding to the target request message parameters fed back by the user equipment parameter value, including: the request message generation module provides the target request message parameter to the user equipment through the request interaction sub-module, and receives the target feedback from the user equipment through the request interaction sub-module The request message parameter value corresponding to the request message parameter.

In an embodiment, the interaction module further includes a response interaction sub-module, and the response message parsing module sends the parsing result based on json format to the interaction module, including: the response message parsing module sending the json format-based parsing result to the response interaction submodule;

The interaction module parses the parsing result based on the json format into an parsing result that meets the preset parsing requirement, and sends the parsing result that meets the preset parsing requirement to the user equipment, including: the response interaction sub-module The parsing result based on the json format is parsed into a parsing result that meets the preset parsing requirement, and the parsing result that meets the preset parsing requirement is sent to the user equipment.

In an embodiment, the diagnostic tool further includes a diagnostic message recording module, where the diagnostic message recording module is configured to record the diagnostic request message and/or the diagnostic response message.

In a second aspect, an embodiment of the present invention provides a diagnosis tool, where the diagnosis tool includes a database module, a diagnosis management module, a request message generation module, a response message analysis module, and an interaction module;

The database module is used to parse the open diagnostic data exchange ODX file to obtain diagnostic data;

the diagnosis management module, configured to obtain the diagnosis data from the database module, and generate a diagnosis request list corresponding to each diagnosis service according to the diagnosis data;

The request generating message module is used to obtain a target diagnosis request list from the diagnosis management module, and send the target diagnosis request list to the interaction module, wherein the target diagnosis request list includes the corresponding diagnosis service. list of diagnostic requests;

The interaction module is configured to receive the target diagnosis request list sent by the request message generation module, and feed back the target diagnosis request list to the user equipment, receive the specified diagnosis request identifier fed back by the user equipment, and sending the specified diagnosis request identifier to the request generating message module, wherein the specified diagnosis request identifier is the diagnosis request identifier in the diagnosis request list corresponding to the specified diagnosis service;

The request generating message module is further configured to receive the designated diagnosis request identifier sent by the interaction module, and send the designated diagnosis request identifier to the diagnosis management module;

The diagnosis management module is further configured to receive the specified diagnosis request identifier sent by the request generation message module, search for the target request message parameter and target request message structure corresponding to the specified diagnosis request identifier, and store the specified diagnosis request message. The target request message parameter and the target request message structure are sent to the request message generation module, wherein the target request message parameter is a request message parameter corresponding to the specified diagnosis request identifier, and the target request message parameter is The request message structure is a request message structure corresponding to the specified diagnosis request identifier, and the target request message parameter and the target request message structure are obtained from the diagnosis data;

The request message generation module is further configured to receive the target request message parameters and the target request message structure sent by the diagnosis management module, and send the target request message parameters to the interaction module, ;

The interaction module is further configured to receive the target request message parameters sent by the request message generation module, feed back the target request message parameters to the user equipment, and receive all the feedback from the user equipment. the request message parameter value corresponding to the target request message parameter, and send the request message parameter value to the request message generation module;

The request message generation module is further configured to receive the request message parameter value sent by the interaction module, generate a diagnosis request message according to the target request message structure and the request message parameter value, and send the request message to the request message. The diagnosis request message is sent to the ECU to be diagnosed;

The response message parsing module is configured to receive a diagnosis response message corresponding to the diagnosis request message sent by the ECU to be diagnosed, and send the diagnosis response message to the diagnosis management module;

The diagnostic management module is further configured to receive the diagnostic response message sent by the response message parsing module, search for a target response message structure, and send the target response message structure to the response message parsing module, wherein the target response message structure is a response message structure corresponding to the diagnostic response message, and the target response message structure is obtained from the diagnostic data;

The response message parsing module is further configured to receive the target response message structure sent by the diagnosis management module, parse the diagnostic response message according to the target response message structure, and use the interactive The module provides the user equipment with a parsing result for the diagnostic response message.

In an embodiment, the diagnostic tool further includes a diagnostic message recording module, the diagnostic message recording module is configured to record the diagnostic request message and/or the diagnostic response message.

In an embodiment, the diagnosis management module is further configured to generate a diagnosis service list according to the diagnosis data, and send the diagnosis service list to the request message generation module;

The request message generation module is configured to receive the diagnosis service list sent by the diagnosis management module, and send the diagnosis service list to the interaction module;

The interaction module is configured to receive the diagnosis service list sent by the request message generation module, provide the diagnosis service list to the user equipment, receive the specified diagnosis service fed back by the user equipment, and convert the diagnosis service list to the user equipment. The specified diagnostic service is sent to the request message generation module;

The request message generation module is configured to receive the designated diagnosis service sent by the interaction module, and send the designated diagnosis service to the diagnosis management module;

The diagnosis management module is configured to receive the specified diagnosis service sent by the request message generation module, and use the diagnosis request list corresponding to the specified diagnosis service as the target diagnosis request list, and use the target diagnosis request list The list is sent to the request message generation module.

In one embodiment, the diagnostic data includes at least one diagnostic service, at least one diagnostic request identifier, at least one request message parameter, at least one request message structure, at least one response message structure, diagnostic service and diagnostic request identifier The first mapping relationship, and the second mapping relationship between the diagnosis request identifier, the request message parameter and the request message structure, the diagnosis management module includes a diagnosis service management submodule and a diagnosis request management submodule;

The diagnostic service management submodule is configured to generate a diagnostic service list according to the diagnostic data, and send the diagnostic service list to the request message generation module;

The diagnosis request management submodule is used to store the first mapping relationship, and generate a diagnosis request list corresponding to each diagnosis service according to the diagnosis data;

The diagnosis service management sub-module is further configured to receive the designated diagnosis service sent by the request message generation module, and send the designated diagnosis service to the diagnosis request management sub-module;

The diagnosis request management sub-module is further configured to look up the diagnosis request list corresponding to the designated diagnosis service as the target diagnosis request list according to the first mapping relationship, and send the target diagnosis request list to the request report. text generation module;

The diagnosis request management sub-module is further configured to receive the specified diagnosis request identifier sent by the request generation message module, and find the target request message parameter and target request message structure corresponding to the specified diagnosis request identifier, and The target request message parameters and the target request message structure are sent to the request message generation module.

In one embodiment, the diagnosis data further includes a third mapping relationship between the diagnosis request identifier and the response message structure, and the diagnosis management module further includes a diagnosis response management sub-module;

The diagnostic response management sub-module is configured to receive the diagnostic response message sent by the response message parsing module, obtain a designated diagnostic request identifier from the diagnostic request management sub-module, and obtain a designated diagnostic request identifier according to the designated diagnostic request identifier Find a target response message structure with the third mapping relationship, and send the target response message structure to the response message parsing module.

In one embodiment, the response packet parsing module is configured to parse the diagnostic response packet according to the target response packet structure, obtain a parsing result based on json format, and parse the response packet based on json format The analysis result is sent to the interaction module;

The interaction module is configured to parse the json format-based parsing result into an parsing result that meets a preset parsing requirement, and feed back the parsing result that meets the preset parsing requirement to the user equipment.

In one embodiment, the interaction module includes a service interaction submodule and a request interaction submodule;

The service interaction sub-module is configured to receive the diagnosis service list sent by the request message generation module, provide the diagnosis service list to the user equipment, and receive the designated diagnosis service fed back by the user equipment, sending the designated diagnostic service to the request message generation module;

The request interaction sub-module is further configured to receive the target diagnosis request list sent by the request message generation module, feed back the target diagnosis request list to the user equipment, and receive the specified diagnosis request identifier fed back by the user equipment , and send the specified diagnosis request identifier to the request generation message module;

The request interaction sub-module is further configured to receive the target request message parameters sent by the request message generation module, and feed back the target request message parameters to the user equipment, and receive feedback from the user equipment The request message parameter value corresponding to the target request message parameter is sent to the request message generation module.

In one embodiment, the interaction module further includes a response interaction sub-module;

The response interaction sub-module is configured to parse the json format-based parsing result into parsing results that meet preset parsing requirements, and feed back the parsing results that meet preset parsing requirements to the user equipment.

In a third aspect, an embodiment of the present invention provides a storage medium on which executable instructions are stored, and when the instructions are executed by a processor, the processor implements the method described in any one of the implementation manners of the first aspect.

In a fourth aspect, an embodiment of the present invention provides a vehicle, including:

one or more processors;

storage means for storing one or more programs,

Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method described in any one of the embodiments of the first aspect.

It can be seen from the above that the ECU diagnosis method and the diagnosis tool based on the diagnosis tool provided by the embodiment of the present invention can set mutually independent database module, diagnosis management module, request message generation module, response message analysis module, The interactive module, after the database module parses the ODX file to obtain diagnostic data, the request message generation module can provide the user equipment with a list of target diagnostic requests supported by the database module through the interactive module, and receive user-specified diagnostic services fed back by the user equipment through the interactive module The specified diagnostic request identifier in the diagnostic request list of the specified diagnostic request list, the request message generation module obtains the target request message parameters and target request message structure corresponding to the specified diagnostic request identifier from the diagnostic management module, and provides the target request message to the user equipment through the interaction module. Packet parameters, the request packet parameter value corresponding to the target request packet parameter fed back by the user equipment is received by the interaction module, and the request packet generation module generates a diagnosis request packet according to the target request packet structure and the request packet parameter value, and generates a diagnosis request packet. The diagnostic request message is sent to the ECU to be diagnosed, and the response message parsing module receives the diagnostic response message corresponding to the diagnostic request message sent by the ECU to be diagnosed, and sends the diagnostic response message to the diagnostic management module, and the response message parsing module The target response message structure corresponding to the diagnosis response message sent by the diagnosis management module is received, the diagnosis response message is parsed according to the target response message structure, and the analysis result for the diagnosis response message is provided to the user equipment through the interaction module. It can be seen from this that the embodiment of the present invention can realize the ECU diagnosis function through the interaction between various mutually decoupled modules, so that the cost of the development cycle and the maintenance cycle is greatly reduced, and because the embodiment of the present invention is based on the The diagnostic data interactive and open diagnostic data format ODX file obtains diagnostic data in the vehicle life cycle, so when the ECU type changes, it is only necessary to load a different ODX file without modifying the code, thus improving the ECU diagnostics. software development efficiency.

The embodiments of the present invention can also achieve at least the following technical effects:

1. By dividing the diagnosis management module into multiple sub-modules, including, for example, a diagnosis service management sub-module, a diagnosis request management sub-module, and a diagnosis response management sub-module, the management of the diagnosis service, diagnosis request and diagnosis response in the diagnosis management module can be obtained. Decoupling, thereby further reducing the cost of the development cycle and maintenance cycle, and improving the efficiency of diagnostic management. In addition, compared with directly feeding back all the diagnosis request lists to the user equipment, the embodiment of the present invention first feeds back the diagnosis service list to the user equipment, and then obtains the target corresponding to the designated diagnosis service according to the designated diagnosis service fed back by the user based on the diagnosis service list. The list of diagnostic requests can reduce the number of data calls, data transfers, and data storage, thereby improving data transfer efficiency and saving resources.

2. By dividing the interaction module into multiple sub-modules, such as service interaction sub-module, request interaction sub-module and response interaction sub-module, the interaction between diagnosis service, diagnosis request and diagnosis response and the outside world can be decoupled, thereby further Reduce the cost of development and maintenance cycles and improve the efficiency of diagnostic interactions.

3. By setting the diagnostic message recording module in the diagnostic tool for recording the diagnostic request message and/or diagnostic response message involved in the diagnostic process, when an abnormality occurs during the diagnostic process, the technician can pass the diagnostic message. The record module quickly locates the cause of the abnormality.

Of course, it is not necessary for any product or method of the present invention to achieve all of the advantages described above at the same time.

Description of drawings

In order to illustrate the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that are required in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1 is a schematic flowchart of an ECU diagnostic method based on a diagnostic tool provided by an embodiment of the present invention;

FIG. 2 is a schematic flowchart of another ECU diagnostic method based on a diagnostic tool provided by an embodiment of the present invention;

3 is a schematic flowchart of another ECU diagnosis method based on a diagnosis tool provided by an embodiment of the present invention;

4 is a block diagram of a diagnostic tool provided by an embodiment of the present invention;

FIG. 5 is a block diagram of an ECU based on a diagnostic tool provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It should be noted that the terms "comprising" and "having" and any modifications thereof in the embodiments of the present invention and the accompanying drawings are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the steps or units listed, but optionally also includes steps or units not listed, or optionally also includes For other steps or units inherent to these processes, methods, products or devices.

The embodiments of the present invention provide an ECU diagnostic method and a diagnostic tool based on a diagnostic tool, which can implement a decoupled ECU diagnostic software framework based on an ODX file, so that when the ECU type changes, it is only necessary to load different ODX files, The development efficiency has been improved, and the cost of the development cycle and maintenance cycle has been greatly reduced due to the relatively independent functional decomposition of the diagnostic requirements of each module.

The embodiments of the present invention will be described in detail below.

1 is a schematic flowchart of an ECU diagnosis method based on a diagnosis tool provided by an embodiment of the present invention. The method is applied to a diagnosis tool. The diagnosis tool can be deployed in an ECU, and the ECU can be an ECU to be diagnosed, or it can be For other ECUs, that is, the diagnostic tool can diagnose the ECU to which it belongs, and can also diagnose other ECUs. The diagnostic tool includes a database module, a diagnostic management module, a request message generation module, a response message parsing module, and an interaction module. The method may include Follow the steps below:

S110: The request message generation module provides the user equipment with a target diagnosis request list supported by the database module through the interaction module.

Wherein, the target diagnosis request list is generated according to the diagnosis data obtained by parsing the open diagnosis data exchange ODX file by the database module, and the target diagnosis request list includes a diagnosis request list corresponding to a specified diagnosis service. The designated diagnostic service in this document may be understood as a designated or user-selected diagnostic service.

Since the ODX file saves the diagnostic data in xml format, and the ISO22901 protocol standardizes some data structures for the description of the diagnostic data and the internal reference to the description of the diagnostic data, such as Parameter, Structure, MUX (Multiplexer, data selector), EndOfPdu and so on. Therefore, the database module can parse the ODX file based on the ISO22901 protocol specification and the DOM (Document Object Model, document object model) method to obtain diagnostic data. The diagnostic data includes at least one diagnostic service, at least one diagnostic request, the first mapping relationship between the diagnostic service and the diagnostic request, the request message parameters corresponding to each diagnostic request, the request message structure, the response message structure, and may also include DID (Data Identifier, Data Identifier) data, DTC (Diagnostic Trouble Code, Diagnostic Trouble Code) data and the data structures Parameter, Structure, MUX, EndOfPdu and so on that the internal reference of the ODX protocol depends on. The database module defines and stores the instantiated objects of these data structures, and provides access to the diagnostic management module. ODX is a file describing diagnostic data, and each data element has a unique DID for identification. DTCs are used to describe the cause of a car failure and are available through diagnostic services.

The request message generation module may include a PDU request message generation sub-module for generating a request message supporting a PDU (Protocol Data Unit, protocol data unit), and a sub-module implementation and interaction module based on the PDU request message generation sub-module , Communication between diagnostic management modules. The following execution process of the request message generation module can be implemented by using the PDU request message generation sub-module, which will not be repeated here.

The diagnostic data includes at least one diagnostic service, at least one diagnostic request identifier, at least one request message parameter, at least one request message structure, at least one response message structure, the first mapping relationship between the diagnostic service and the diagnostic request identifier, and Diagnose the second mapping relationship between the request identifier, the request message parameter, the request message structure and the response message structure. The diagnosis management module can obtain the diagnosis data from the database module, and generate a diagnosis service list and a diagnosis request list corresponding to each diagnosis service in the diagnosis service list according to the diagnosis data. The diagnostic service list includes a diagnostic service identifier, and the diagnostic service identifier may be a diagnostic service DID, or may be a diagnostic service name + a diagnostic service DID. The diagnosis request list includes a diagnosis request identifier, and may also include a positive response DID corresponding to the diagnosis request identifier, and a negative response DID corresponding to the diagnosis request. The diagnostic request identifier may be the diagnostic request DID, or may be the diagnostic request name + the diagnostic request DID. The mapping relationship between each diagnostic request list and the diagnostic service can be a separate mapping relationship table, or the list name of the diagnostic request list can be directly named as the corresponding diagnostic service name, and the corresponding diagnostic request can also be added to the diagnostic service list The list name of the list.

When the diagnosis is local diagnosis, the user equipment may be a diagnostic instrument or a host computer, and when the diagnosis is remote diagnosis, the user equipment may be a remote server. In projects that need to support remote diagnosis, this data transmission can be completed through HTTP (Hyper Text Transfer Protocol, hypertext transfer protocol). At this time, the interaction module needs to interact with the client module. The remote server provides the function of interacting with the user, that is, the client module is required as a relay module to forward the data that needs to be interacted between the interaction module and the remote server.

When providing the target diagnosis request list to the user equipment, all the diagnosis request lists or part of the diagnosis request list (such as several diagnosis request lists that the user has recently accessed frequently) can be directly provided to the user equipment for selection by the user, or the The user equipment provides a list of diagnostic services, and after the user specifies the diagnostic service, it provides the user equipment with a list of diagnostic requests corresponding to the specified diagnostic service. Among them, the last solution, compared with the first two solutions, firstly feeds back the diagnosis service list to the user equipment, and then obtains the diagnosis request list corresponding to the designated diagnosis service according to the designated diagnosis service fed back by the user based on the diagnosis service list. Reduce the number of data calls, data transfers, and data storage, which can improve data transfer efficiency and save resources.

Taking the last solution as an example below, the specific implementation process of this step will be described. As shown in Figure 2, the process includes:

S111. The request message generation module provides the diagnostic service list obtained from the diagnostic management module to the user equipment through the interaction module.

The diagnosis management module sends the diagnosis service list to the request message generation module, the request message generation module sends the received diagnosis service list to the interaction module, and the interaction module sends the diagnosis service list to the user equipment.

In order to improve the efficiency of diagnosis service and diagnosis request management and reduce the cost of the development cycle and maintenance cycle of the diagnosis management module, a diagnosis service sub-module for managing diagnosis services and a diagnosis request management module for managing diagnosis requests can be set in the diagnosis management module. submodule. When the diagnosis management module includes a diagnosis service management submodule and a diagnosis request management submodule, the diagnosis service management submodule acquires the at least one diagnosis service from the database module, and generates a diagnosis according to the at least one diagnosis service Service list, the diagnostic request management sub-module obtains from the database module at least one diagnostic request identifier, at least one request message parameter, at least one request message structure, the first mapping relationship between the diagnostic service and the diagnostic request identifier, and the diagnostic A second mapping relationship between the request identifier, the request message parameter and the request message structure, and a diagnostic request list of each diagnostic service is generated according to the first mapping relationship. That is to say, the diagnostic service management sub-module interacts with the database module upward to obtain the diagnostic service supported by the ODX file, and interacts with the request message generation module downward to provide the related data of these diagnostic services supported by the database module, and manage the diagnostic data supported by the diagnostic data. List of services. The diagnostic request management sub-module interacts with the database module upward, obtains the first mapping relationship and the second mapping relationship, interacts with the diagnostic service management sub-module, obtains the specified diagnostic service, and interacts downward with the request message generation module to provide request-related information.

In order to improve the efficiency of interaction with the user equipment and reduce the cost of the development cycle and maintenance cycle of the interaction module, the interaction module may include a service interaction sub-module for interactive diagnosis services and a request interaction sub-module for interactive diagnosis requests, and the service interaction Submodules and request interaction submodules are independent of each other. When the interaction module includes a service interaction submodule, the request message generation module provides the diagnostic service list obtained from the diagnosis management module to the user equipment through the service interaction submodule.

To sum up, when the request message generation module includes a PDU request message generation sub-module, the diagnostic management module includes a diagnostic service management sub-module, and the interaction module includes a service interaction sub-module, the PDU request message generation sub-module will convert the diagnostic service The list of diagnostic services obtained in the management sub-module is provided to the user equipment through the service interaction sub-module.

S112. The request message generation module receives the specified diagnostic service fed back by the user equipment through the interaction module.

The specified diagnosis service fed back by the user equipment is the diagnosis service selected by the user in the diagnosis service list displayed on the user equipment, rather than the diagnosis service automatically selected by the user equipment. After acquiring the specified diagnostic service selected by the user, the user equipment may send the specified diagnostic service to the interaction module, and the interaction module then forwards the specified diagnostic service to the request message generation module.

When the interaction module includes a service interaction sub-module, the request message generation module receives the specified diagnosis service fed back by the user equipment through the service interaction sub-module, that is, after the user equipment obtains the specified diagnosis service selected by the user, it can The designated diagnosis service is sent to the service interaction sub-module, and the service interaction sub-module then forwards the designated diagnosis service to the request message generation module.

S113. The request message generation module acquires a diagnosis request list corresponding to the specified diagnosis service from the diagnosis management module as a target diagnosis request list.

The request message generation module sends the specified diagnosis service to the diagnosis management module, and the diagnosis management module can search for the diagnosis request list corresponding to the specified diagnosis service according to the first mapping relationship, and send the found diagnosis request list to the request message generation module, So that the request message generation module takes the found list of diagnostic requests as the list of target diagnostic requests.

When the diagnosis management module includes a diagnosis request management sub-module, the request message generation module may acquire a diagnosis request list corresponding to the specified diagnosis service from the diagnosis request management sub-module as the target diagnosis request list, wherein , the diagnosis request management sub-module acquires the specified diagnosis service from the diagnosis management service sub-module, and determines the target diagnosis request list according to the specified diagnosis service and the first mapping relationship.

S114. The request message generation module provides the user equipment with a target diagnosis request list through the interaction module.

The request message generation module sends the target diagnosis request list to the interaction module, and the interaction module forwards the target diagnosis request list to the user equipment, so that the user equipment can display the target diagnosis request list to the user, so that the user is in the target diagnosis request list. Select Specify Diagnostic Request ID.

When the interaction module includes a request interaction submodule, the request message generation module provides the user equipment with the target diagnosis request list through the request interaction submodule, that is, the request message generation module generates the target diagnosis request list It is sent to the request interaction sub-module, and the request interaction sub-module forwards the target diagnosis request list to the user equipment, so that the user equipment can display the target diagnosis request list to the user.

S120: The request message generation module receives the specified diagnosis request identifier fed back by the user equipment through the interaction module.

The user equipment acquires the designated diagnosis request identifier selected by the user, and sends the designated diagnosis request identifier to the interaction module, and the interaction module then forwards the designated diagnosis request identifier to the request message generation module. The specified diagnosis request identifier is the diagnosis request identifier in the diagnosis request list corresponding to the user-specified diagnosis service.

When the interaction module includes a request interaction sub-module, the request message generation module receives the specified diagnosis request identifier fed back by the user equipment through the request interaction sub-module, that is, the user equipment obtains the specified diagnosis request identifier selected by the user, and sends The designated diagnosis request identifier is sent to the request interaction sub-module, and the request interaction sub-module then forwards the designated diagnosis request identifier to the request message generation module.

S130: The request message generation module obtains the target request message parameters and the target request message structure from the diagnosis management module, provides the target request message parameters to the user equipment through the interaction module, and receives the target request message fed back by the user equipment through the interaction module The parameter value of the request message corresponding to the parameter.

The target request message parameter is a request message parameter corresponding to the specified diagnosis request identifier, the target request message structure is a request message structure corresponding to the specified diagnosis request identifier, and the diagnosis management The target request message parameters and the target request message structure stored in the module are acquired from the diagnostic data stored in the database module.

When the diagnosis management module includes a diagnosis request management submodule, the request message generation module acquires the target request message parameters and the target request message structure from the diagnosis request management submodule, wherein the diagnosis request The management submodule determines the target request message parameter and the target request message structure according to the second mapping relationship and the specified diagnosis request identifier.

When the interaction module includes a request interaction submodule, the request message generation module provides the target request message parameters to the user equipment through the request interaction submodule, and receives the user equipment through the request interaction submodule The feedback parameter value of the request message corresponding to the target request message parameter.

To sum up, when the request message generation module includes a PDU request message generation sub-module, the diagnosis management module includes a diagnosis request management sub-module, and the interaction module includes a request interaction sub-module, the PDU request message generation sub-module is managed from the diagnosis request. The sub-module obtains the target request message parameters and the target request message structure, provides the target request message parameters to the user equipment through the request interaction sub-module, and receives the target feedback from the user equipment through the request interaction sub-module The request message parameter value corresponding to the request message parameter.

S140: The request message generation module generates a diagnosis request message according to the target request message structure and the request message parameter value, and sends the diagnosis request message to the ECU to be diagnosed.

When the request message generation module includes a PDU request message generation sub-module, the PDU request message generation sub-module can generate a diagnosis that conforms to the UDS (Unified diagnostic services, unified diagnostic services) protocol based on the request message structure and the request message parameter values. request message, and send the diagnosis request message to the ECU to be diagnosed.

When the diagnostic tool is deployed in the to-be-diagnosed ECU, the request message generation module in the to-be-diagnosed ECU sends the request message to the ECU module deployed in the to-be-diagnosed ECU for data forwarding, and the ECU module sends the diagnostic request message to the to-be-diagnosed ECU ECU's operating system.

When the diagnostic tool is deployed in other ECUs other than the ECU to be diagnosed, the request message generation module in the other ECU can first send the diagnostic request message to the ECU module in the ECU to be diagnosed, and the ECU module in the ECU to be diagnosed will diagnose The request message is sent to the operating system of the ECU to be diagnosed.

S150: The response message parsing module receives a diagnosis response message corresponding to the diagnosis request message sent by the ECU to be diagnosed, and sends the diagnosis response message to the diagnosis management module.

When the diagnosis management module includes a diagnosis response management submodule, the response message parsing module sends the diagnosis response message to the diagnosis response management submodule. The response message parsing module may include a PDU response message parsing sub-module for generating a response message supporting a PDU (Protocol Data Unit, protocol data unit), and the PDU response message parsing sub-module receives the message sent by the to-be-diagnosed ECU. The diagnostic response message corresponding to the diagnostic request message is sent to the diagnostic response management sub-module. The execution process of the response message parsing module can be implemented by using the PDU response message parsing sub-module.

S160: The response message parsing module receives the target response message structure sent by the diagnosis management module, parses the diagnostic response message according to the target response message structure, and provides the user equipment with a parsing result of the diagnostic response message through the interaction module.

Wherein, the target response message structure is a response message structure corresponding to the diagnosis response message, and since the diagnosis response message corresponds to the diagnosis request message, the diagnosis request message corresponds to the specified diagnosis request identifier, Therefore, the target response message structure is the response message structure corresponding to the specified diagnostic request identifier. The target response message structure stored in the diagnosis management module is obtained from the diagnosis data stored in the database module. It can be understood that, when the diagnostic response message is divided into a positive response and a negative response, the structure of the target response message needs to be determined in combination with the corresponding type of the diagnostic response message.

When the diagnosis management module includes a diagnosis response management submodule and the interaction module includes a response interaction submodule, the response message parsing module receives the target response message structure sent by the diagnosis response management submodule, and responds according to the target response. The message structure parses the diagnostic response message, and provides the user equipment with a parsing result for the diagnostic response message through the response interaction sub-module, wherein the diagnostic response management sub-module The specified diagnosis request identifier is obtained in the diagnosis request management sub-module, and the target response message structure is determined according to the specified diagnosis request identifier and the third mapping relationship, and the third mapping relationship is between the diagnosis request identifier and the response message structure. The diagnostic response management sub-module obtains the third mapping relationship from the diagnostic data of the database module. When the response message parsing module includes a PDU response message parsing sub-module, the PDU response message parsing sub-module receives the target response message structure corresponding to the diagnostic response message sent by the diagnostic response management sub-module, and according to the target The response message structure parses the diagnostic response message, and provides the user equipment with a parsing result for the diagnostic response message through the response interaction sub-module.

During the diagnosis process, the ECU to be diagnosed will respond to the diagnosis request message. A positive response is a positive response, and a negative response is a negative response. The diagnosis response management sub-module can maintain the positive/negative response message structure of the current diagnosis request message. . When the diagnostic response message is a positive response, the diagnostic response management sub-module sends the positive response message structure to the response message parsing module; when the diagnostic response message is a negative response, the diagnostic response management sub-module sends the negative response message structure Sent to the response packet parsing module.

The response message parsing module parses the diagnostic response message according to the target response message structure, and provides the user equipment with the analysis result for the diagnostic response message through the interaction module. The specific implementation process may be: As shown in Figure 3.

S151. The response message parsing module parses the diagnostic response message according to the target response message structure, obtains the parsing result based on the json format, and sends the parsing result based on the json format to the interaction module.

When the interaction module further includes a response interaction submodule, the response message parsing module sends the json format-based parsing result to the response interaction submodule.

S152. The interaction module parses the parsing result based on the json format into an parsing result that meets the preset parsing requirement, and feeds back the parsing result that meets the preset parsing requirement to the user device.

When the interaction module includes a response interaction sub-module, the response interaction sub-module parses the parsing result based on json format into parsing results that meet preset parsing requirements, and converts the parsing results that meet preset parsing requirements feedback to the user equipment. The parsing result satisfying the preset parsing requirement is also the parsing result of the diagnostic response message. The preset parsing requirements include preset parsing format requirements, for example, the preset parsing format requires a natural language in Chinese format or English format. When the analysis results include diagnosis results for multiple diagnosis objects, the preset analysis requirements may also include requirements for output items of diagnosis results. For example, when the multiple diagnosis results include both fault results and no-fault results, only faults are required to be output As a result, when all of the multiple diagnosis results are non-faulty results, it is required to output only one result representing no faults.

In an embodiment, the ECU further includes a diagnostic message recording module, and the diagnostic message recording module is configured to record the diagnostic request message and/or the diagnostic response message. If the program is abnormal, for example, there is no response after the diagnostic command is issued or the user interface diagnostic result is garbled, the diagnostic message recording module records all the diagnostic request messages and diagnostic response messages during the diagnostic process, which can be handed over to professional engineers. positioning problem. The diagnostic message recording module can realize the diagnostic request message and/or the diagnostic response message received by the interactive module by communicating with the interactive module, or obtain the diagnostic request message by communicating with the request message generating module, and communicate with the response message. The message parsing module communicates to obtain a diagnostic response message.

The ECU diagnosis method based on the diagnosis tool provided by the embodiment of the present invention can set up mutually independent database module, diagnosis management module, request message generation module, response message analysis module, and interaction module in the diagnosis tool. After the file parsing obtains the diagnostic data, the request message generation module can provide the user equipment with the target diagnosis request list supported by the database module through the interaction module, and receive the specified diagnosis in the diagnosis request list of the user-specified diagnosis service fed back by the user equipment through the interaction module. request identifier, the request message generation module obtains the target request message parameters and target request message structure corresponding to the specified diagnosis request identifier from the diagnosis management module, and provides the target request message parameters to the user equipment through the interaction module, and receives through the interaction module The request message parameter value corresponding to the target request message parameter returned by the user equipment, the request message generation module generates a diagnosis request message according to the target request message structure and the request message parameter value, and sends the diagnosis request message to the to-be-diagnosed ECU, the response message parsing module receives the diagnostic response message corresponding to the diagnostic request message sent by the ECU to be diagnosed, and sends the diagnostic response message to the diagnostic management module, and the response message parsing module receives and diagnoses sent by the diagnostic management module. The target response message structure corresponding to the response message, the diagnostic response message is parsed according to the target response message structure, and the analysis result for the diagnostic response message is provided to the user equipment through the interaction module. It can be seen from this that the embodiment of the present invention can realize the ECU diagnosis function through the interaction between various mutually decoupled modules, so that the cost of the development cycle and the maintenance cycle is greatly reduced, and because the embodiment of the present invention is based on the The diagnostic data interactive and open diagnostic data format ODX file obtains diagnostic data in the vehicle life cycle, so when the ECU type changes, it is only necessary to load a different ODX file without modifying the code, thus improving the ECU diagnostics. software development efficiency. By dividing the diagnosis management module into multiple sub-modules, for example, including a diagnosis service management sub-module, a diagnosis request management sub-module, and a diagnosis response management sub-module, the management of diagnosis services, diagnosis requests and diagnosis responses in the diagnosis management module can be decoupled , so as to further reduce the cost of development cycle and maintenance cycle, and improve the efficiency of diagnosis management. In addition, compared with directly feeding back all the diagnosis request lists to the user equipment, the embodiment of the present invention first feeds back the diagnosis service list to the user equipment, and then obtains the target corresponding to the designated diagnosis service according to the designated diagnosis service fed back by the user based on the diagnosis service list. The list of diagnostic requests can reduce the number of data calls, data transfers, and data storage, thereby improving data transfer efficiency and saving resources. By dividing the interaction module into multiple sub-modules, for example, including a service interaction sub-module, a request interaction sub-module and a response interaction sub-module, the interaction between the diagnosis service, diagnosis request and diagnosis response and the outside world can be decoupled, thereby further reducing development costs. Cycle and maintenance cycle costs, improve the efficiency of diagnostic interactions. By setting the diagnostic message recording module in the diagnostic tool for recording the diagnostic request message and/or the diagnostic response message involved in the diagnostic process, when an abnormality occurs during the diagnostic process, the technician can record the module through the diagnostic message. Quickly locate the cause of the abnormality.

Corresponding to the above method embodiments, the embodiments of the present invention provide a diagnostic tool. The diagnostic tool can be deployed in an ECU, and the ECU to be diagnosed can be an ECU in which the diagnostic tool is deployed, or other ECUs in the vehicle. As shown in FIG. 4 , the diagnosis tool includes a database module 21, a diagnosis management module 22, a request message generation module 23, a response message analysis module 24 and an interaction module 25;

The database module 21 is used to parse the open diagnostic data exchange ODX file to obtain diagnostic data;

The diagnosis management module 22 is configured to obtain the diagnosis data from the database module 21, and generate a diagnosis request list corresponding to each diagnosis service according to the diagnosis data;

The request generating message module is used to obtain the target diagnosis request list from the diagnosis management module 22, and send the target diagnosis request list to the interaction module 25, wherein the target diagnosis request list includes the specified diagnosis A list of diagnostic requests corresponding to the service;

The interaction module 25 is configured to receive the target diagnosis request list sent by the request message generation module 23, and feed back the target diagnosis request list to the user equipment, and receive the specified diagnosis request identifier fed back by the user equipment , and send the designated diagnosis request identifier to the request generating message module, wherein the designated diagnosis request identifier is the diagnosis request identifier in the diagnosis request list corresponding to the designated diagnosis service;

The request generating message module is further configured to receive the designated diagnosis request identifier sent by the interaction module 25, and send the designated diagnosis request identifier to the diagnosis management module 22;

The diagnosis management module 22 is further configured to receive the specified diagnosis request identifier sent by the request generation message module, search for the target request message parameter and target request message structure corresponding to the specified diagnosis request identifier, and store the specified diagnosis request message. The target request message parameter and the target request message structure are sent to the request message generation module 23, wherein the target request message parameter is the request message parameter corresponding to the specified diagnosis request identifier, so The target request message structure is a request message structure corresponding to the specified diagnosis request identifier, and the target request message parameter and the target request message structure are obtained from the diagnostic data;

The request message generation module 23 is further configured to receive the target request message parameters and the target request message structure sent by the diagnosis management module 22, and send the target request message to the interaction module 25. text parameter,

The interaction module 25 is further configured to receive the target request message parameters sent by the request message generation module 23, and feed back the target request message parameters to the user equipment, and receive feedback from the user equipment the request message parameter value corresponding to the target request message parameter, and send the request message parameter value to the request message generation module 23;

The request message generation module 23 is further configured to receive the request message parameter value sent by the interaction module 25, and generate a diagnosis request message according to the target request message structure and the request message parameter value, and send the diagnosis request message to the ECU to be diagnosed;

The response message parsing module 24 is configured to receive a diagnosis response message corresponding to the diagnosis request message sent by the to-be-diagnosed ECU, and send the diagnosis response message to the diagnosis management module 22;

The diagnostic management module 22 is further configured to receive the diagnostic response message sent by the response message parsing module 24, search for the target response message structure, and send the target response message structure to the response message. The text parsing module 24, wherein the target response message structure is the response message structure corresponding to the diagnostic response message, and the target response message structure is obtained from the diagnostic data;

The response message parsing module 24 is further configured to receive the target response message structure sent by the diagnosis management module 22, parse the diagnostic response message according to the target response message structure, and pass the target response message structure. The interaction module 25 provides the user equipment with a parsing result for the diagnosis response message.

In one embodiment, as shown in FIG. 5 , the diagnostic tool further includes a diagnostic message recording module 26, which is configured to record the diagnostic request message and/or the diagnostic message response message.

In an embodiment, the diagnosis management module 22 is further configured to generate a diagnosis service list according to the diagnosis data, and send the diagnosis service list to the request message generation module 23;

The request message generation module 23 is configured to receive the diagnosis service list sent by the diagnosis management module 22, and send the diagnosis service list to the interaction module 25;

The interaction module 25 is configured to receive the diagnosis service list sent by the request message generation module 23, provide the diagnosis service list to the user equipment, and receive the specified diagnosis service fed back by the user equipment, sending the designated diagnostic service to the request message generation module 23;

The request message generation module 23 is configured to receive the designated diagnosis service sent by the interaction module 25, and send the designated diagnosis service to the diagnosis management module 22;

The diagnosis management module 22 is configured to receive the specified diagnosis service sent by the request message generation module 23, and use the diagnosis request list corresponding to the specified diagnosis service as the target diagnosis request list, and use the target diagnosis request list. The diagnosis request list is sent to the request message generation module 23 .

In one embodiment, as shown in FIG. 5 , the diagnostic data includes at least one diagnostic service, at least one diagnostic request identifier, at least one request message parameter, at least one request message structure, at least one response message structure, The first mapping relationship between the diagnostic service and the diagnostic request identifier, and the second mapping relationship between the diagnostic request identifier, the request message parameter and the request message structure, the diagnostic management module 22 includes a diagnostic service management sub-module 221 and a diagnostic request management sub-module. module 222;

The diagnostic service management sub-module 221 is configured to generate a diagnostic service list according to the diagnostic data, and send the diagnostic service list to the request message generation module 23;

The diagnosis request management sub-module 222 is configured to store the first mapping relationship, and generate a diagnosis request list corresponding to each diagnosis service according to the diagnosis data;

The diagnosis service management sub-module 221 is further configured to receive the designated diagnosis service sent by the request message generation module 23, and send the designated diagnosis service to the diagnosis request management sub-module 222;

The diagnosis request management sub-module 222 is further configured to look up the diagnosis request list corresponding to the specified diagnosis service as the target diagnosis request list according to the first mapping relationship, and send the target diagnosis request list to the requester message generation module 23;

The diagnosis request management sub-module 222 is further configured to receive the specified diagnosis request identifier sent by the request generation message module, and find the target request message parameter and target request message structure corresponding to the specified diagnosis request identifier, and set the The target request message parameters and the target request message structure are sent to the request message generation module 23 .

In an embodiment, as shown in FIG. 5 , the diagnosis data further includes a third mapping relationship between the diagnosis request identifier and the response message structure, and the diagnosis management module 22 further includes a diagnosis response management sub-module 223;

The diagnostic response management sub-module 223 is configured to receive the diagnostic response message sent by the response message parsing module 24, obtain the specified diagnostic request identifier from the diagnostic request management sub-module 222, and according to the specified diagnostic request The diagnosis request identifier and the third mapping relationship look up the target response message structure, and send the target response message structure to the response message parsing module 24 .

In one embodiment, the response message parsing module 24 is configured to parse the diagnostic response message according to the target response message structure, obtain a parsing result based on json format, and analyze the json-based The parsing result of the format is sent to the interaction module 25;

The interaction module 25 is configured to parse the parsing result based on the json format into an parsing result satisfying a preset parsing requirement, and feed back the parsing result satisfying the preset parsing requirement to the user equipment.

In one embodiment, as shown in FIG. 5 , the interaction module 25 includes a service interaction sub-module 251 and a request interaction sub-module 252;

The service interaction sub-module 251 is configured to receive the diagnosis service list sent by the request message generation module 23, provide the diagnosis service list to the user equipment, and receive the specified diagnosis fed back by the user equipment service, sending the specified diagnostic service to the request message generation module 23;

The request interaction sub-module 252 is further configured to receive the target diagnosis request list sent by the request message generation module 23, feed back the target diagnosis request list to the user equipment, and receive the specified diagnosis fed back by the user equipment. request identification, and send the specified diagnosis request identification to the request generation message module;

The request interaction sub-module 252 is further configured to receive the target request message parameters sent by the request message generation module 23, and feed back the target request message parameters to the user equipment, and receive the user The request message parameter value corresponding to the target request message parameter fed back by the device is sent to the request message generation module 23 .

In one embodiment, as shown in FIG. 5 , the interaction module 25 further includes a response interaction sub-module 253;

The response interaction sub-module 253 is configured to parse the json format-based parsing result into parsing results that meet preset parsing requirements, and feed back the parsing results that meet preset parsing requirements to the user equipment.

In one embodiment, as shown in FIG. 5 , the request message generation module 23 includes a PDU request message generation sub-module 231, and the PDU request message generation sub-module 231 is configured to perform the steps performed by the request message generation module 23 above. ;

The response message parsing module 24 includes a PDU response message parsing sub-module 241, and the PDU response message parsing sub-module 241 is configured to perform the steps performed by the response message parsing module 24 above.

Based on the above method embodiments, another embodiment of the present invention provides a storage medium on which executable instructions are stored, and when the instructions are executed by a processor, the processor implements the above method.

Based on the above method embodiment, another embodiment of the present invention provides a vehicle, including:

one or more processors;

storage means for storing one or more programs,

Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described above.

The foregoing system and device embodiments correspond to the method embodiments, and have the same technical effects as the method embodiments. For specific descriptions, refer to the method embodiments. The apparatus embodiment is obtained based on the method embodiment, and the specific description can refer to the method embodiment section, which will not be repeated here. Those of ordinary skill in the art can understand that the accompanying drawing is only a schematic diagram of an embodiment, and the modules or processes in the accompanying drawing are not necessarily necessary to implement the present invention.

Those skilled in the art may understand that: the modules in the apparatus in the embodiment may be distributed in the apparatus in the embodiment according to the description of the embodiment, and may also be located in one or more apparatuses different from this embodiment with corresponding changes. The modules in the foregoing embodiments may be combined into one module, or may be further split into multiple sub-modules.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that it can still be The technical solutions described in the foregoing embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present invention.

Claims (10)

1. an ECU diagnosis method based on a diagnosis tool, is characterized in that, described diagnosis tool comprises database module, diagnosis management module, request message generation module, response message analysis module and interaction module, and described method comprises: The request message generation module provides the user equipment with a target diagnosis request list supported by the database module through the interaction module, wherein the target diagnosis request list is based on the database module parsing the ODX file of the open diagnostic data exchange Generated from the obtained diagnosis data, the target diagnosis request list includes a diagnosis request list corresponding to the specified diagnosis service; The request message generation module receives, through the interaction module, a designated diagnosis request identifier fed back by the user equipment, wherein the designated diagnosis request identifier is a diagnosis request identifier in a diagnosis request list corresponding to the designated diagnosis service; The request message generation module obtains the target request message parameters and the target request message structure from the diagnosis management module, and provides the user equipment with the target request message parameters through the interaction module. The module receives the request message parameter value corresponding to the target request message parameter fed back by the user equipment, wherein the target request message parameter is the request message parameter corresponding to the specified diagnosis request identifier, and the target request message parameter The request message structure is a request message structure corresponding to the specified diagnosis request identifier, and the target request message parameters and the target request message structure stored in the diagnosis management module are stored in the database module. obtained from the diagnostic data of ; The request message generation module generates a diagnosis request message according to the target request message structure and the request message parameter value, and sends the diagnosis request message to the ECU to be diagnosed; The response message parsing module receives a diagnosis response message corresponding to the diagnosis request message sent by the to-be-diagnosed ECU, and sends the diagnosis response message to the diagnosis management module; The response message parsing module receives the target response message structure sent by the diagnosis management module, parses the diagnosis response message according to the target response message structure, and sends the message to the user equipment through the interaction module. Provide a parsing result for the diagnosis response message, wherein the target response message structure is a response message structure corresponding to the diagnosis response message, and the target response message stored in the diagnosis management module The structure is obtained from the diagnostic data stored in the database module. 2. The method according to claim 1, wherein the request message generation module provides the user equipment with a target diagnosis request list supported by the database module through the interaction module, comprising: The request message generation module provides the diagnosis service list obtained from the diagnosis management module to the user equipment through the interaction module, wherein the diagnosis management module obtains the diagnosis data from the database module, and generating the list of diagnostic services and a list of diagnostic requests corresponding to each diagnostic service in the list of diagnostic services according to the diagnostic data; The request message generation module receives the specified diagnostic service fed back by the user equipment through the interaction module; The request message generation module obtains a diagnosis request list corresponding to the specified diagnosis service from the diagnosis management module as the target diagnosis request list; The request message generating module provides the user equipment with the target diagnosis request list through the interaction module. 3. The method according to claim 2, wherein the diagnostic data comprises at least one diagnostic service, at least one diagnostic request identifier, at least one request message parameter, at least one request message structure, at least one response message structure, the first mapping relationship between the diagnostic service and the diagnostic request identifier, and the second mapping relationship between the diagnostic request identifier, the request message parameter and the request message structure, and the diagnostic management module includes a diagnostic service management sub-module and a diagnostic request management sub-module. module; The request message generating module provides the diagnostic service list obtained from the diagnostic management module to the user equipment through the interaction module, including: the request message generating module will generate a list of diagnostic services from the diagnostic service management sub-module. The list of diagnostic services obtained in is provided to the user equipment through the interaction module; The request message generation module obtains a diagnosis request list corresponding to the specified diagnosis service from the diagnosis management module as the target diagnosis request list, including: the request message generation module obtains from the diagnosis request management sub-module. The diagnosis request list corresponding to the specified diagnosis service is obtained in the module as the target diagnosis request list, wherein the diagnosis request management sub-module obtains the specified diagnosis service from the diagnosis management service sub-module, and the specified diagnosis service is obtained according to the specified diagnosis service sub-module. The diagnosis service, the first mapping relationship determines the target diagnosis request list; The request message generation module obtains the target request message parameters and the target request message structure from the diagnosis management module, including: the request message generation module obtains the target request message from the diagnosis request management sub-module parameters and the target request message structure, wherein the diagnosis request management sub-module determines the target request message parameters and the target request message structure according to the second mapping relationship and the specified diagnosis request identifier. 4. The method according to claim 3, wherein the diagnosis data further comprises a third mapping relationship between a diagnosis request identifier and a response message structure, and the diagnosis management module further comprises a diagnosis response management submodule; The response message parsing module sending the diagnostic response message to the diagnostic management module includes: the response message parsing module sending the diagnostic response message to the diagnostic response management sub-module; The response message parsing module receiving the target response message structure sent by the diagnosis management module includes: the response message parsing module receiving the target response message structure sent by the diagnostic response management sub-module, wherein the The diagnostic response management sub-module acquires the designated diagnostic request identifier from the diagnostic request management sub-module, and determines a target response message structure according to the designated diagnostic request identifier and the third mapping relationship. 5 . The method according to claim 2 , wherein the diagnostic response message is parsed according to the target response message structure, and the diagnostic response is provided to the user equipment through the interaction module. 6 . Packet parsing results, including: The response message parsing module parses the diagnostic response message according to the target response message structure, obtains a parsing result based on the json format, and sends the parsing result based on the json format to the interaction module; The interaction module parses the parsing result based on the json format into an parsing result satisfying a preset parsing requirement, and feeds back the parsing result satisfying the preset parsing requirement to the user equipment. 6. The method according to claim 5, wherein the interaction module comprises a service interaction submodule and a request interaction submodule, and the request message generation module obtains a list of diagnostic services from the diagnosis management module Providing to the user equipment through the interaction module includes: the request message generation module provides the diagnosis service list obtained from the diagnosis management module to the user equipment through the service interaction sub-module; The request message generation module receives the specified diagnostic service fed back by the user equipment through the interaction module, including: the request message generation module receives the specified diagnostic service fed back by the user equipment through the service interaction sub-module; The request message generation module provides the user equipment with the target diagnosis request list through the interaction module, including: the request message generation module provides the user equipment with the target through the request interaction sub-module list of diagnostic requests; The request message generation module receives the specified diagnosis request identifier fed back by the user equipment through the interaction module, including: the request message generation module receives the specified diagnosis request fed back by the user equipment through the request interaction sub-module identification; The request message generation module provides the user equipment with the target request message parameters through the interaction module, and receives, through the interaction module, a request message corresponding to the target request message parameters fed back by the user equipment parameter value, including: the request message generation module provides the target request message parameter to the user equipment through the request interaction sub-module, and receives the target feedback from the user equipment through the request interaction sub-module The request message parameter value corresponding to the request message parameter. 7. The method according to claim 6, wherein the interaction module further comprises a response interaction sub-module, and the response message parsing module sends the parsing result based on the json format to the interaction module, comprising: : the response message parsing module sends the parsing result based on the json format to the response interaction sub-module; The interaction module parses the parsing result based on the json format into an parsing result that meets the preset parsing requirement, and sends the parsing result that meets the preset parsing requirement to the user equipment. The module parses the parsing result based on the json format into an parsing result that meets the preset parsing requirement, and sends the parsing result that meets the preset parsing requirement to the user equipment. 8. The method according to any one of claims 1-7, wherein the diagnostic tool further comprises a diagnostic message recording module, and the diagnostic message recording module is configured to record the diagnostic request message and /or the diagnostic response message. 9. A diagnostic tool, characterized in that the diagnostic tool comprises a database module, a diagnostic management module, a request message generation module, a response message analysis module and an interaction module; The database module is used to parse the open diagnostic data exchange ODX file to obtain diagnostic data; the diagnosis management module, configured to obtain the diagnosis data from the database module, and generate a diagnosis request list corresponding to each diagnosis service according to the diagnosis data; The request generating message module is used to obtain a target diagnosis request list from the diagnosis management module, and send the target diagnosis request list to the interaction module, wherein the target diagnosis request list includes the corresponding diagnosis service. list of diagnostic requests; The interaction module is configured to receive the target diagnosis request list sent by the request message generation module, and feed back the target diagnosis request list to the user equipment, receive the specified diagnosis request identifier fed back by the user equipment, and sending the specified diagnosis request identifier to the request generating message module, wherein the specified diagnosis request identifier is the diagnosis request identifier in the diagnosis request list corresponding to the specified diagnosis service; The request generating message module is further configured to receive the designated diagnosis request identifier sent by the interaction module, and send the designated diagnosis request identifier to the diagnosis management module; The diagnosis management module is further configured to receive the specified diagnosis request identifier sent by the request generation message module, search for target request message parameters and target request message structure corresponding to the specified diagnosis request identifier, and The target request message parameter and the target request message structure are sent to the request message generation module, wherein the target request message parameter is the request message parameter corresponding to the specified diagnosis request identifier, so The target request message structure is a request message structure corresponding to the specified diagnosis request identifier, and the target request message parameter and the target request message structure are obtained from the diagnostic data; The request message generation module is further configured to receive the target request message parameters and the target request message structure sent by the diagnosis management module, and send the target request message parameters to the interaction module, ; The interaction module is further configured to receive the target request message parameters sent by the request message generation module, feed back the target request message parameters to the user equipment, and receive all the feedback from the user equipment. the request message parameter value corresponding to the target request message parameter, and send the request message parameter value to the request message generation module; The request message generation module is further configured to receive the request message parameter value sent by the interaction module, generate a diagnosis request message according to the target request message structure and the request message parameter value, and send the request message to the request message. The diagnosis request message is sent to the ECU to be diagnosed; The response message parsing module is configured to receive a diagnosis response message corresponding to the diagnosis request message sent by the ECU to be diagnosed, and send the diagnosis response message to the diagnosis management module; The diagnostic management module is further configured to receive the diagnostic response message sent by the response message parsing module, search for a target response message structure, and send the target response message structure to the response message parsing module, wherein the target response message structure is a response message structure corresponding to the diagnostic response message, and the target response message structure is obtained from the diagnostic data; The response message parsing module is further configured to receive the target response message structure sent by the diagnosis management module, parse the diagnostic response message according to the target response message structure, and use the interactive The module provides the user equipment with a parsing result for the diagnostic response message. 10. The diagnostic tool according to claim 9, wherein the diagnostic tool further comprises a diagnostic message recording module, and the diagnostic message recording module is used to record the diagnostic request message and/or the diagnostic message response message.

Images