CN112558584B

CN112558584B - Diagnostic data acquisition method and device and diagnostic equipment

Info

Publication number: CN112558584B
Application number: CN202011295684.4A
Authority: CN
Inventors: 刘均; 刘国柱; 庄文龙
Original assignee: Shenzhen Launch Technology Co Ltd
Current assignee: Shenzhen Launch Technology Co Ltd
Priority date: 2020-11-18
Filing date: 2020-11-18
Publication date: 2022-05-10
Anticipated expiration: 2040-11-18
Also published as: CN112558584A

Abstract

The application is applicable to the technical field of vehicle diagnosis, and provides a diagnostic data acquisition method, a diagnostic data acquisition device and diagnostic equipment, wherein the diagnostic data acquisition method comprises the following steps: sending a diagnosis instruction to each ECU of a vehicle to be diagnosed, wherein the diagnosis instruction carries ECU group identification, the ECU group identification is used for uniquely identifying the ECU groups, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed; acquiring diagnostic data corresponding to the diagnostic instruction returned by a target ECU, wherein the target ECU is as follows: and the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction. By the method, the acquisition efficiency of the diagnostic data is improved, and resources of other ECUs are not occupied.

Description

Diagnostic data acquisition method and device and diagnostic equipment

Technical Field

The application belongs to the technical field of vehicle diagnosis, and particularly relates to a diagnostic data acquisition method, a diagnostic data acquisition device and diagnostic equipment.

Background

An Electronic Control Unit (ECU) is also called a "traveling computer" or a "vehicle-mounted computer", and has a special program inside for running. For example, when the engine ECU is in operation, the program in the engine ECU continuously compares and calculates the signals collected from the various sensors. And controlling various parameters of the engine such as ignition, air-fuel ratio, idling and/or exhaust gas recirculation according to the comparison and calculation results.

At present, a vehicle is detected by communicating a diagnostic apparatus with each ECU of the vehicle, the diagnostic apparatus obtains parameters of each ECU, and then whether the vehicle has a problem is determined according to the obtained parameters.

The communication modes of the existing diagnostic instrument and the vehicle ECU are divided into two types: one is a one-to-one communication mode, i.e., a communication mode for one ECU, in which only one ECU can communicate with one communication mode at a time, i.e., only one ECU can obtain a reply at a time; the other is a pair of all-communication modes, i.e., a communication mode for all ECUs in which communication with all ECUs is possible at a time, i.e., replies to all ECUs are acquired at a time. However, the existing 2 communication modes still cannot meet the requirements of users.

Disclosure of Invention

The embodiment of the application provides a diagnostic data acquisition method, which can improve the acquisition efficiency of diagnostic data and does not occupy the resources of other ECUs.

In a first aspect, an embodiment of the present application provides a diagnostic data obtaining method, applied to a diagnostic device, including:

sending a diagnosis instruction to each ECU of a vehicle to be diagnosed, wherein the diagnosis instruction carries ECU group identification, the ECU group identification is used for uniquely identifying the ECU groups, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed;

acquiring diagnostic data corresponding to the diagnostic instruction returned by a target ECU, wherein the target ECU is as follows: and the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction.

Optionally, before the sending of the diagnosis instruction to each ECU of the vehicle to be diagnosed, the method includes:

and sending a configuration instruction to the target ECU, wherein the configuration instruction comprises an ECU group identifier of an ECU group where the target ECU is located and characters used for indicating that the configuration instruction is an instruction related to the ECU group.

Optionally, the sending the configuration instruction to the target ECU includes:

and acquiring an inquiry identifier of the target ECU, and sending a configuration instruction to the target ECU, wherein the configuration instruction comprises an ECU group identifier where the target ECU is located, characters used for indicating that the configuration instruction is an instruction related to an ECU group, and the inquiry identifier of the target ECU used for indicating that the configuration instruction is an instruction inquired for the target ECU.

displaying ECU group identifications corresponding to the established ECU groups;

if a selection instruction of a user is detected, analyzing an ECU group identifier selected by the user from the selection instruction;

the sending of the diagnosis instruction to each ECU of the vehicle to be diagnosed comprises:

and sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the ECU group identification carried by the diagnosis instruction is the ECU group identification selected by the user.

Optionally, the acquiring the diagnostic data corresponding to the diagnostic instruction returned by the target ECU includes:

acquiring a reply identifier and a diagnosis instruction identifier of the target ECU, wherein the diagnosis instruction identifier is used for uniquely identifying the diagnosis instruction;

determining a target reply instruction identifier according to the diagnosis instruction identifier and a preset character, wherein the target reply instruction identifier is used for uniquely identifying a target reply instruction and indicating that the target reply instruction is a reply instruction corresponding to the diagnosis instruction;

searching a target reply instruction from the reply instruction of the vehicle to be diagnosed according to the target reply instruction identification;

and if the searched target reply instruction comprises the reply identifier of the target ECU, using the diagnostic data in the target reply instruction as the diagnostic data which is replied by the target ECU and corresponds to the diagnostic instruction.

Optionally, the sending a diagnosis instruction to each ECU of the vehicle to be diagnosed includes:

determining a diagnosis protocol adopted for communicating with the vehicle to be diagnosed;

and sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the format of the diagnosis instruction is the same as the format of the instruction corresponding to the diagnosis protocol adopted by the communication of the vehicle to be diagnosed.

In a second aspect, an embodiment of the present application provides a diagnostic data obtaining method, applied to an ECU of a vehicle to be diagnosed, including:

receiving a diagnosis instruction sent by a diagnosis device, wherein the diagnosis instruction carries a unique identification of an ECU group, the diagnosis instruction carries an ECU group identification, the ECU group identification is used for uniquely identifying the ECU group, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed;

and if the ECU group identification is the same as the prestored ECU group identification, replying the diagnosis data corresponding to the diagnosis instruction to the diagnosis equipment.

In a third aspect, an embodiment of the present application provides a diagnostic data obtaining apparatus, which is applied to a diagnostic device, and includes:

the diagnostic instruction sending unit is used for sending diagnostic instructions to all ECUs of the vehicle to be diagnosed, the diagnostic instructions carry ECU group identifications, the ECU group identifications are used for uniquely identifying the ECU groups, and the number of the ECUs included in one ECU group is greater than 1 and smaller than the total number of the ECUs of the vehicle to be diagnosed;

a diagnostic data obtaining unit, configured to obtain diagnostic data corresponding to the diagnostic instruction returned by a target ECU, where the target ECU is: and the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction.

In a fourth aspect, the present application provides a diagnostic apparatus, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of the first aspect when executing the computer program.

In a fifth aspect, the present application provides an intelligent device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to the second aspect when executing the computer program.

In a sixth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and the computer program when executed by a processor implements the method according to any one of the first aspect, or the computer program when executed implements the method according to the second aspect.

In a seventh aspect, the present application provides a computer program product, which when run on a diagnostic device, causes the diagnostic device to execute the method of any one of the above first aspects, or when run on a smart device, causes the smart device to execute the computer program, to implement the method of the second aspect.

Compared with the prior art, the embodiment of the application has the beneficial effects that:

because the diagnosis command carries the ECU group identification, the ECU group identification is used for uniquely identifying the ECU group, and the target ECU is as follows: the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction, so that the required diagnosis data can be ensured to be acquired, and because the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed, the diagnosis equipment can simultaneously communicate with a plurality of designated ECUs in the vehicle to be diagnosed at one time, thereby improving the acquisition efficiency of the diagnosis data and not occupying the resources of other ECUs.

It is to be understood that, the beneficial effects of the second to seventh aspects may be referred to the relevant description of the first aspect, and are not repeated herein.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.

Fig. 1 is a flowchart of a diagnostic data acquisition method according to an embodiment of the present application;

FIG. 2 is a flow chart of another diagnostic data acquisition method provided in the second embodiment of the present application;

fig. 3 is a schematic diagram of a flash flow between the diagnostic apparatus and the ECU according to the second embodiment of the present application;

fig. 4 is a schematic structural diagram of a diagnostic data acquisition apparatus according to a third embodiment of the present application;

fig. 5 is a schematic structural diagram of another diagnostic data acquisition apparatus according to the fourth embodiment of the present application;

fig. 6 is a schematic structural diagram of a diagnostic apparatus provided in the fifth embodiment of the present application;

fig. 7 is a schematic structural diagram of an intelligent device according to a sixth embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

The appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like in various places in the specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

The first embodiment is as follows:

currently, when the diagnostic device communicates with the ECU of the vehicle to be diagnosed, it employs a communication mode that can be selected only from a one-to-one communication mode or from a pair of all communication modes. In practice, however, the user will typically wish to communicate with several, but not all, of the designated ECUs simultaneously, for example, with 4 door ECUs simultaneously, or with ECUs corresponding to the driver, the passenger seat, and the rear seat simultaneously. When the communication mode selected by the user is a one-to-one communication mode, the processing efficiency is low because only one of the one-to-one communication modes can be processed in sequence; when the communication mode selected by the user is a pair of all communication modes, the other ECUs are caused to respond, and the resources of the other ECUs are occupied. In order to solve the above technical problem, an embodiment of the present application provides a diagnostic data acquisition method, in which the ECUs are grouped in advance to obtain ECU groups, and the number of ECUs in each ECU group is greater than 1 and less than the total number of ECUs of a vehicle to be diagnosed. When the diagnosis equipment sends a diagnosis instruction to a vehicle to be diagnosed, filling the ECU group identification of the ECU group into the diagnosis instruction, judging whether each ECU of the vehicle to be diagnosed is in the ECU group corresponding to the ECU group identification according to the ECU group identification, and if the ECU is in the ECU group corresponding to the ECU group identification, replying the diagnosis data corresponding to the diagnosis instruction to the diagnosis equipment. Since the diagnostic device can communicate with each ECU in the same ECU group at a time, the efficiency of acquiring diagnostic data can be greatly improved, and since each ECU in the ECU group does not include all the ECUs of the vehicle to be diagnosed, the communication mode does not occupy the resources of other ECUs not in the one ECU group.

The diagnostic data acquisition method is described in detail below with reference to the drawings.

Fig. 1 shows a flowchart of a diagnostic data acquisition method provided in an embodiment of the present application, which is applied to a diagnostic device, and is detailed as follows:

step S11, sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the diagnosis instruction carries an ECU group identifier, the ECU group identifier is used for uniquely identifying the ECU group, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed.

The vehicle to be diagnosed refers to a vehicle to be diagnosed by the diagnostic device.

The ECUs (e.g., the number) included in each ECU group may be adjusted according to actual conditions, for example, the ECUs corresponding to 4 doors may be disposed in the same ECU group, for example, the ECU corresponding to the left front door and the ECU corresponding to the driver seat may be disposed in the same ECU group. Each ECU group is uniquely corresponding to one ECU group identifier, and the ECU group identifiers can be represented by designated characters or numbers, for example, "1" is used for representing the ECU group corresponding to the ECU corresponding to 4 doors.

In this embodiment, the diagnostic device establishes a communication connection with the vehicle to be diagnosed through an On Board Diagnostics (OBD) device, wherein the diagnostic device establishes a wired or wireless communication connection with the vehicle to be diagnosed through the OBD device. Specifically, the diagnostic equipment sends the diagnostic instruction to an OBD communication bus of an OBD device, and all ECUs of the vehicle to be diagnosed can receive the diagnostic instruction on the OBD communication bus, so that the diagnostic equipment can send the diagnostic instruction to all ECUs of the vehicle to be diagnosed in the above mode.

In some embodiments, since the diagnostic device may communicate with the vehicle to be diagnosed by using a plurality of diagnostic protocols, such as K protocol, CAN protocol, DOIP protocol, etc., and formats of instructions corresponding to different diagnostic protocols are different, such as byte meanings, byte order, and number of bytes of each instruction, in order to ensure that a correctly formatted diagnostic instruction is sent to the vehicle to be diagnosed, step S11 includes:

and A1, determining a diagnosis protocol used for communicating with the vehicle to be diagnosed.

A2, sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the format of the diagnosis instruction is the same as the format of the instruction corresponding to the diagnosis protocol used by the communication of the vehicle to be diagnosed.

Specifically, assuming that the diagnostic device communicates with the vehicle to be diagnosed by using the CAN protocol, and the diagnostic device sends a diagnostic instruction for reading a fault code to the ECU group identified by the ECU group "01", the diagnostic instruction may be "0 x06FF 0103190208", where "06" indicates the number of bytes of a frame in which the current diagnostic instruction is located, "FF" is used to indicate that the diagnostic instruction is an instruction related to the ECU group, and "01" following the FF indicates that the ECU group is identified by "01", and the field in which the above-mentioned "FF 01" is located is an inquiry identifier (inquiry ID) of a specific ECU that needs to acquire diagnostic data in the one-to-one mode. 03 in the diagnostic instruction indicates the number of valid data bytes, and 190208 indicates that the diagnostic instruction is to read a fault code.

Step S12, acquiring the diagnostic data corresponding to the diagnostic command returned by the target ECU, where the target ECU: and storing the ECU group identification which is the same as the ECU group identification carried by the diagnosis instruction.

In the present embodiment, the ECU that has been set in the ECU group stores in advance the ECU group identification of the ECU group in which it is located. After each ECU of the vehicle to be diagnosed receives the diagnosis instruction sent by the diagnosis equipment, whether the ECU group identification carried by the diagnosis instruction is the same as the ECU identification stored in the diagnosis instruction or not is judged, if so, the diagnosis data corresponding to the diagnosis instruction is replied to the diagnosis equipment, and if not, the diagnosis data is not replied. In this way, the diagnostic device will receive the diagnostic data returned by each ECU in the ECU group corresponding to the ECU group identifier.

In the embodiment of the application, the diagnosis equipment sends the diagnosis instruction to each ECU of the vehicle to be diagnosed, and then acquires the diagnosis data corresponding to the diagnosis instruction returned by the target ECU. Because the diagnosis instruction carries the ECU group identification, the ECU group identification is used for uniquely identifying the ECU group, and the target ECU is as follows: the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction, so that the required diagnosis data can be ensured to be acquired, and because the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed, the diagnosis equipment can simultaneously communicate with a plurality of designated ECUs in the vehicle to be diagnosed at one time, thereby improving the acquisition efficiency of the diagnosis data and not occupying the resources of other ECUs.

In some embodiments, after step S12, for easy viewing by the user, the method includes: the diagnostic equipment analyzes the acquired diagnostic data and displays the analyzed diagnostic data, wherein the analyzed diagnostic data comprises character information.

In this embodiment, it is considered that the diagnostic data is generally composed of various characters and numbers, which is inconvenient for a user to visually check, and therefore, the diagnostic data needs to be analyzed to obtain corresponding textual description and then displayed, so that the user can quickly determine whether the vehicle to be diagnosed has a fault from the textual description.

In some embodiments, in order for an ECU to be aware of its assigned ECU group, before this step S11, it includes:

and sending a configuration instruction to the target ECU, wherein the configuration instruction comprises an ECU group identifier of the ECU group in which the target ECU is positioned and characters used for indicating that the configuration instruction is an instruction related to the ECU group.

In this embodiment, the diagnostic device groups the ECUs according to the user requirement, and generates configuration information of the ECU group, where the configuration information includes an ECU group identifier, identifiers of the ECUs in the ECU group (the ECU identifiers may be represented by the ECU names), query identifiers and/or reply identifiers of the ECUs, and the like. For example, the generated configuration information is shown in table 1:

table 1:

after grouping is finished, the diagnostic equipment sends configuration instructions to each ECU in the ECU group needing to acquire the diagnostic data, the configuration instructions comprise the ECU group identification of the ECU group where the ECU is located, and after the ECU receives the ECU group identification where the ECU is located, the ECU group identification is stored.

In some embodiments, in order to accurately send the configuration instruction to the target ECU, the sending the configuration instruction to the target ECU includes:

and acquiring the inquiry mark of the target ECU, and sending a configuration instruction to the target ECU, wherein the configuration instruction comprises an ECU group mark where the target ECU is located, characters used for indicating that the configuration instruction is an instruction related to an ECU group, and the inquiry mark of the target ECU used for indicating that the configuration instruction is an instruction inquired for the target ECU.

In this embodiment, assuming that the target ECU is an ECU corresponding to a front left door, the ECU group identifier of the ECU group in which the ECU corresponding to the front left door is located is "01", and the query identifier is 0701, the configuration command may be in the form of "0 x05070102FF 01", where 05 denotes that the number of bytes of the configuration command in a whole frame is 5, 0701 denotes that the query identifier of the front left door ECU is 5, 02 denotes that the number of valid bytes is 2, FF01 denotes that the configuration command is a command related to the ECU group, and 01 denotes that the ECU group identifier is an ECU group identifier. In some embodiments, if an ECU is assigned to multiple ECU groups, it may be added in the valid bytes, such as the left front door is in both the 01ECU group and the 02ECU group, that configuration command is 0x06070103FF 0102.

In some embodiments, before step S11, the method includes:

and B1, displaying ECU group identifications corresponding to the established ECU groups.

And B2, if a selection command of the user is detected, analyzing the ECU group identification selected by the user from the selection command.

The step S11 includes:

In this embodiment, when a user desires to acquire diagnostic data of corresponding ECUs in a group mode, the diagnostic device displays an ECU group identifier corresponding to each established ECU group, and of course, in order to facilitate the user to know the ECUs included in each ECU group, each ECU identifier in each ECU group may also be displayed (the ECU identifier may be represented by the ECU name), and in addition, query identifiers, reply identifiers, and the like of each ECU may also be displayed. When the user selects one ECU group identifier from the displayed ECU group identifiers, for example, selects '01', the diagnostic equipment fills the '01' into the diagnostic instruction, and the filled diagnostic instruction is sent to the OBD communication bus.

In some embodiments, the ECU group identifiers may be displayed first, and after it is detected that one of the ECU group identifiers is selected by the user, the ECU group identifiers under the ECU group corresponding to the selected ECU group identifier are displayed in the area around the selected ECU group identifier. Or displaying each ECU group identification on a page, and popping up a new page to display each ECU identification under the ECU group corresponding to the selected ECU group identification after detecting that the user selects one ECU group identification.

In the present embodiment, the ECU group id and the ECU group id are displayed separately, so that the ECU group id can be displayed as much as possible on one page, or the ECU id can be displayed as much as possible.

In some embodiments, in order to accurately acquire the diagnostic data, the step S12 includes:

c1, acquiring the reply identifier of the target ECU and the diagnostic instruction identifier, wherein the diagnostic instruction identifier is used for uniquely identifying the diagnostic instruction.

The diagnosis instruction identification is uniquely corresponding to the diagnosis instruction, for example, in the diagnosis instruction of "0 x06FF 0103190208", the diagnosis instruction identification is "190208", and the "190208" is used to indicate that the diagnosis instruction is an instruction for reading a fault code.

And C2, determining a target reply instruction identifier according to the diagnosis instruction identifier and the preset characters, wherein the target reply instruction identifier is used for uniquely identifying a target reply instruction and indicating that the target reply instruction is a reply instruction corresponding to the diagnosis instruction.

Wherein the predetermined characters are associated with the diagnostic protocol employed. Assuming that the CAN protocol is used, the preset character is "40", and assuming that the diagnosis command is identified as "190208", since 19+40 is 59, the target reply command is identified as "590208".

And C3, searching the target reply instruction from the reply instruction of the vehicle to be diagnosed according to the target reply instruction identification.

Specifically, if there are a plurality of reply instructions of the vehicle to be diagnosed, it is determined one by one whether the reply instruction identifier in the reply instruction is the same as the target reply instruction identifier, and if the reply instruction identifier in the reply instruction is the same as the target reply instruction identifier, it is determined that the reply instruction is the target reply instruction.

And C4, if the searched target reply instruction includes the reply identifier of the target ECU, taking the diagnostic data in the target reply instruction as the diagnostic data corresponding to the diagnostic instruction and replied by the target ECU.

Specifically, assuming that the diagnostic command is "0 x06FF 0103190208", and the ECU group "01" includes the ECU corresponding to the front left door, and the corresponding reply flag is "0 x07E 1", as can be seen from table 1, the target reply command corresponding to the diagnostic command is "0 x07E 15902089001". Wherein 07 is the number of all bytes of the frame where the target return command is located, 07E1 is the return flag of the ECU at the front left, 590208 is the target return command flag, and 9001 is the number of the fault code.

In this embodiment, the diagnostic data is doubly confirmed by the reply command identifier of the target and the reply identifier of the target ECU, so that the accuracy of the obtained diagnostic data is improved.

In some embodiments, after step S12, the diagnostic apparatus determines whether diagnostic data of all ECUs in the ECU group identifier has been acquired, and if not, establishes communication with the target ECU that does not reply with the diagnostic data in a one-to-one communication mode, and sends a diagnostic instruction to the target ECU that does not reply with the diagnostic data to acquire the diagnostic data that the target ECU that does not reply with the diagnostic data replies with. Specifically, the diagnostic device determines whether the ECU has replied based on a reply flag of the ECU.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Example two:

fig. 2 shows a flowchart of a diagnostic data acquisition method provided in an embodiment of the present application, which is applied to an ECU of a vehicle to be diagnosed, the ECU being the ECU in the first embodiment, and is detailed as follows:

step S21, receiving a diagnosis instruction sent by the diagnosis device, where the diagnosis instruction carries an ECU group identifier, where the ECU group identifier is used to uniquely identify an ECU group, and the number of ECUs included in one ECU group is greater than 1 and less than the total number of ECUs of the vehicle to be diagnosed.

And step S22, if the ECU group identification is the same as the prestored ECU group identification, replying the diagnosis data corresponding to the diagnosis instruction to the diagnosis equipment.

In this embodiment, each ECU of the vehicle to be diagnosed prestores an ECU group identifier of an ECU group in which the ECU is located, and after the ECU acquires the diagnosis instruction from the OBD communication bus, the ECU group identifier carried by the diagnosis instruction is resolved, and if the ECU group identifier carried by the diagnosis instruction is the same as the ECU group identifier prestored by the ECU, the ECU replies corresponding diagnosis data to the diagnosis device.

In the embodiment of the present application, since the diagnostic command carries the ECU group identifier, the ECU group identifier is used to uniquely identify the ECU group, and the target ECU is: the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction, so that the ECU can select whether to send the diagnosis data to the diagnosis equipment according to the ECU group identification, the diagnosis equipment can obtain the required diagnosis data, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed, so that the diagnosis equipment can simultaneously communicate with a plurality of designated ECUs in the vehicle to be diagnosed at one time, the acquisition efficiency of the diagnosis data is improved, and the resources of other ECUs are not occupied.

In some embodiments, before step S21, the method includes:

the ECU allocated in the ECU group receives a configuration instruction sent by the diagnosis device, wherein the configuration instruction comprises an ECU group identifier of the ECU group in which the ECU is positioned and characters used for indicating that the configuration instruction is an instruction related to the ECU group.

In this embodiment, when the diagnostic device communicates with only one ECU, the configuration instruction sent by the diagnostic device does not need to distinguish which ECU is sent to, and at this time, the configuration instruction received by the ECU includes an ECU group identifier of an ECU group where the ECU is located and characters used for indicating that the configuration instruction is an instruction related to the ECU group.

In some embodiments, when the diagnostic device communicates with a plurality of ECUs, the configuration command sent by the diagnostic device needs to distinguish which ECU is sent to, and in this case, the configuration command further includes an inquiry identifier of the ECU. For example, assuming that the ECU group ID of the ECU corresponding to the left front door is 01, the configuration command received by the ECU corresponding to the left front door may be "0 x05070102FF 01", where 05 denotes the number of bytes of the frame where the configuration command is located, 0701 denotes the inquiry ID of the left front door ECU, 02 denotes that the number of valid bytes is 2, FF01 denotes that the configuration command is group information, and 01 denotes the ECU group ID.

In some embodiments, the step S22 includes:

and if the ECU judges that the ECU group identification carried by the diagnosis instruction is the same as the prestored ECU group identification, the diagnosis data corresponding to the diagnosis instruction in the ECU is acquired, and the acquired diagnosis data is filled into the reply instruction and is sent to the OBD communication bus.

For example, assume that the ECU group identified as "01" includes ECUs as shown in table 1. When the ECU corresponding to the left front door receives the diagnosis command 0x06FF0103190208, the group mode is judged according to FF, and then the ECU group identification is judged to be 01, because the ECU corresponding to the left front door is in the group 01, the ECU corresponding to the left front door needs to process, and the ECU corresponding to the left front door knows that the ECU needs to read the fault code in the ECU according to the diagnosis valid data of 190208. And then the ECU corresponding to the left front door fills the fault code in the ECU into a return instruction, and then the return instruction is sent to an OBD communication bus, wherein the return instruction is 0x0707E15902089001 for example. Wherein 07 is the number of bytes of the frame where the return command is located, 07E1 is the return identifier of the ECU corresponding to the left front door, 590208 is the corresponding return command identifier, and 9001 is the number of the fault code. The other three ECUs (corresponding to the right front door, left rear door, and right rear door) process the diagnostic data in return for the fault code in the same manner.

In order to more clearly describe the communication process between the diagnostic device and the ECU, the following description is made with reference to fig. 3.

1. And determining a diagnosis protocol, and assuming that the diagnosis protocol is a CAN protocol.

2. And the ECU is grouped by self-definition to obtain configuration information of the ECU group, wherein the configuration information comprises an ECU group identifier, an ECU name, an inquiry identifier and a reply identifier of the ECU.

3. And after the configuration information of the ECU group is obtained, a configuration instruction is sent to each relevant ECU, and the ECU group identification of the ECU group where the corresponding ECU is located is stored.

4. When a diagnostic command needs to be sent to the ECUs in the ECU group, the ECU group to be received, such as the ECU group identified as 01, may be selected first.

5. And filling the ECU group identification into a diagnosis instruction, and sending the diagnosis instruction to an OBD communication bus.

6. All ECUs receive data on the OBD communication bus, and each ECU judges whether the ECU needs to process according to the ECU identification in the diagnosis instruction.

7. If the ECU is determined not to be in the ECU group, no processing is required, and if the ECU is determined to be in the ECU group, processing is required.

9. And the ECUs of the ECU group acquire corresponding diagnostic data according to the content in the diagnostic instruction, and then respectively fill the diagnostic data into the reply instruction and send the diagnostic data to the OBD communication bus.

10. And the OBD device receives the reply instruction of the ECU in the ECU group on the OBD communication bus according to the reply identifier of each ECU in the ECU group.

11. And judging which ECU replies the reply command according to the reply identifier of each ECU, and simultaneously taking out the diagnostic data in the reply command.

12. And respectively and sequentially calculating the diagnosis data of each ECU through an algorithm to obtain a result.

13. And displaying the calculation results of all the ECUs in the ECU group.

Example three:

fig. 4 shows a block diagram of a diagnostic data acquisition device provided in an embodiment of the present application, which is applied to a diagnostic apparatus, corresponding to the diagnostic data acquisition method in the first embodiment.

Referring to fig. 4, the diagnostic data acquisition apparatus 4 includes:

a diagnosis instruction sending unit 41, configured to send a diagnosis instruction to each ECU of the vehicle to be diagnosed, where the diagnosis instruction carries an ECU group identifier, where the ECU group identifier is used to uniquely identify an ECU group, and the number of ECUs included in one ECU group is greater than 1 and smaller than the total number of ECUs of the vehicle to be diagnosed.

A diagnostic data obtaining unit 42, configured to obtain diagnostic data corresponding to the diagnostic instruction returned by the target ECU, where the target ECU is: and storing the ECU group identification which is the same as the ECU group identification carried by the diagnosis command.

In the embodiment of the application, the diagnosis equipment sends the diagnosis instruction to each ECU of the vehicle to be diagnosed, and then acquires the diagnosis data corresponding to the diagnosis instruction and returned by the target ECU. Because the diagnosis command carries an ECU group identifier, the ECU group identifier is used for uniquely identifying the ECU group, and the target ECU is as follows: the stored ECU group identification is the same as the ECU group identification carried by the diagnosis instruction, so that the required diagnosis data can be ensured to be acquired, and because the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed, the diagnosis equipment can simultaneously communicate with a plurality of designated ECUs in the vehicle to be diagnosed at one time, thereby improving the acquisition efficiency of the diagnosis data and not occupying the resources of other ECUs.

In some embodiments, the diagnostic data acquisition device 4 comprises:

and the configuration instruction sending unit is used for sending a configuration instruction to the target ECU, wherein the configuration instruction comprises an ECU group identifier of the ECU group where the target ECU is located and characters used for indicating that the configuration instruction is an instruction related to the ECU group.

In some embodiments, the configuration instruction sending unit is specifically configured to:

In some embodiments, the diagnostic data acquisition device 4 comprises:

and the ECU group identifier display unit is used for displaying the ECU group identifiers corresponding to the established ECU groups.

And the ECU group identifier selection unit is used for resolving the ECU group identifier selected by the user from the selection instruction if the selection instruction of the user is detected.

The diagnosis instruction sending unit 41 is specifically configured to:

In some embodiments, the diagnostic data acquisition unit 42 includes:

and the diagnosis instruction identifier acquisition module is used for acquiring the reply identifier and the diagnosis instruction identifier of the target ECU, and the diagnosis instruction identifier is used for uniquely identifying the diagnosis instruction.

And the target reply instruction identification determining module is used for determining a target reply instruction identification according to the diagnosis instruction identification and preset characters, wherein the target reply instruction identification is used for uniquely identifying a target reply instruction and is used for indicating the target reply instruction to be a reply instruction corresponding to the diagnosis instruction.

And the target reply instruction searching module is used for searching a target reply instruction from the reply instruction of the vehicle to be diagnosed according to the target reply instruction identifier.

And the diagnostic data determining module is used for taking the diagnostic data in the target reply instruction as the diagnostic data corresponding to the diagnostic instruction replied by the target ECU if the searched target reply instruction comprises the reply identifier of the target ECU.

In some embodiments, the diagnostic instruction sending unit 41 is specifically configured to:

and determining a diagnosis protocol adopted for communicating with the vehicle to be diagnosed. And sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the format of the diagnosis instruction is the same as the format of the instruction corresponding to the determined diagnosis protocol adopted by the communication with the vehicle to be diagnosed.

In some embodiments, the diagnostic data acquisition device 4 comprises:

and the diagnostic data analysis unit is used for analyzing the acquired diagnostic data and displaying the analyzed diagnostic data, wherein the analyzed diagnostic data comprises character information.

In some embodiments, the diagnostic data acquisition device 4 comprises:

and the information integrity judging unit is used for judging whether the diagnostic data of all the ECUs in the ECU group identifier are acquired, if not, establishing communication with the target ECU which does not reply the diagnostic data in a one-to-one communication mode, and sending a diagnostic instruction to the target ECU which does not reply the diagnostic data so as to acquire the diagnostic data replied by the target ECU which does not reply the diagnostic data. Specifically, the diagnostic device determines whether the ECU has replied based on a reply flag of the ECU.

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

Example four:

fig. 5 shows a block diagram of a diagnostic data acquisition device provided in an embodiment of the present application, which is applied to an ECU, corresponding to the diagnostic data acquisition method of the second embodiment described above, and only the parts related to the embodiment of the present application are shown for convenience of explanation.

The diagnostic data acquisition device 5 includes: a diagnostic instruction receiving unit 51 and a diagnostic data replying unit 52, wherein:

the diagnostic instruction receiving unit 51 is configured to receive a diagnostic instruction sent by the diagnostic device, where the diagnostic instruction carries an ECU group identifier, the ECU group identifier is used to uniquely identify an ECU group, and the number of ECUs included in one ECU group is greater than 1 and smaller than the total number of ECUs of the vehicle to be diagnosed.

And a diagnostic data replying unit 52, configured to, if the ECU group identifier is the same as a pre-stored ECU group identifier, reply the diagnostic data corresponding to the diagnostic instruction to the diagnostic device.

In some embodiments, the diagnostic data acquisition device 5 comprises:

and the configuration instruction receiving unit is used for receiving a configuration instruction sent by the diagnosis equipment, and the configuration instruction comprises an ECU group identifier of the ECU group in which the ECU is positioned and characters used for indicating that the configuration instruction is an instruction related to the ECU group.

In this embodiment, when the diagnostic device communicates with only one ECU, the configuration instruction sent by the diagnostic device does not need to be distinguished from which ECU is sent, and at this time, the configuration instruction received by the ECU includes an ECU group identifier of an ECU group where the ECU is located and a character for indicating that the configuration instruction is an instruction related to the ECU group.

In some embodiments, the diagnostic data recovery unit 52 is specifically configured to:

Example five:

fig. 6 is a schematic structural diagram of a diagnostic apparatus provided in the fifth embodiment of the present application. As shown in fig. 6, the diagnostic apparatus 6 of this embodiment includes: at least one processor 60 (only one processor is shown in fig. 6), a memory 61 and a computer program 62 stored in the memory 61 and executable on the at least one processor 60, the processor 60 implementing the steps of the first embodiment described above when executing the computer program 62:

and sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the diagnosis instruction carries an ECU group identifier, the ECU group identifier is used for uniquely identifying the ECU group, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed.

Acquiring diagnostic data corresponding to the diagnostic instruction returned by a target ECU, wherein the target ECU is as follows: and storing the ECU group identification which is the same as the ECU group identification carried by the diagnosis instruction.

and displaying the ECU group identification corresponding to each established ECU group.

And if the selection instruction of the user is detected, the ECU group identification selected by the user is analyzed from the selection instruction.

The sending of the diagnosis instruction to each ECU of the vehicle to be diagnosed includes:

Optionally, the obtaining of the diagnostic data corresponding to the diagnostic instruction returned by the target ECU includes:

and acquiring a reply identifier and a diagnosis instruction identifier of the target ECU, wherein the diagnosis instruction identifier is used for uniquely identifying the diagnosis instruction.

And determining a target reply instruction identifier according to the diagnosis instruction identifier and a preset character, wherein the target reply instruction identifier is used for uniquely identifying a target reply instruction and indicating that the target reply instruction is a reply instruction corresponding to the diagnosis instruction.

And searching a target reply instruction from the reply instruction of the vehicle to be diagnosed according to the target reply instruction identification.

Optionally, the sending of the diagnosis instruction to each ECU of the vehicle to be diagnosed includes:

and determining a diagnosis protocol adopted for communicating with the vehicle to be diagnosed.

And sending a diagnosis instruction to each ECU of the vehicle to be diagnosed, wherein the format of the diagnosis instruction is the same as the format of the instruction corresponding to the determined diagnosis protocol adopted by the communication with the vehicle to be diagnosed.

Alternatively, the following steps are implemented:

and receiving a diagnosis instruction sent by the diagnosis equipment, wherein the diagnosis instruction carries a unique identifier of the ECU group, the diagnosis instruction carries an ECU group identifier, the ECU group identifier is used for uniquely identifying the ECU group, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed.

The diagnostic device 6 may be a desktop computer, a notebook, a palm computer, a diagnostic device, an ECU, or other computing device. The diagnostic device may include, but is not limited to, a processor 60, a memory 61. It will be understood by those skilled in the art that fig. 6 is merely an example of the diagnostic device 6, and does not constitute a limitation of the diagnostic device 6, and may include more or less components than those shown, or some components in combination, or different components, such as input and output devices, network access devices, etc.

The Processor 60 may be a Central Processing Unit (CPU), and the Processor 60 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 61 may in some embodiments be an internal storage unit of the diagnostic device 6, such as a hard disk or a memory of the diagnostic device 6. The memory 61 may also be an external storage device of the diagnostic device 6 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the diagnostic device 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the diagnostic device 6. The memory 61 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 61 may also be used to temporarily store data that has been output or is to be output.

Example six:

fig. 7 is a schematic structural diagram of an intelligent device according to a sixth embodiment of the present application. As shown in fig. 7, the smart device 7 of this embodiment includes: at least one processor 70 (only one processor is shown in fig. 7), a memory 71, and a computer program 72 stored in the memory 71 and operable on the at least one processor 70, wherein the processor 70 implements the steps of the second embodiment when executing the computer program 72:

The smart device 7 may be a computing device such as an ECU in the vehicle to be diagnosed. The smart device may include, but is not limited to, a processor 70, a memory 71. Those skilled in the art will appreciate that fig. 7 is merely an example of the smart device 7, and does not constitute a limitation of the smart device 7, and may include more or less components than those shown, or combine some of the components, or different components, such as input output devices, network access devices, etc.

The Processor 70 may be a Central Processing Unit (CPU), and the Processor 70 may be other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 71 may in some embodiments be an internal storage unit of the smart device 7, such as a hard disk or a memory of the smart device 7. In other embodiments, the memory 71 may also be an external storage device of the Smart device 7, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the Smart device 7. Further, the memory 71 may also include both an internal storage unit and an external storage device of the smart device 7. The memory 71 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 71 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

An embodiment of the present application further provides a network device, where the network device includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, the processor implementing the steps of any of the various method embodiments described above when executing the computer program.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.

The embodiments of the present application provide a computer program product, which when running on a mobile terminal, enables the mobile terminal to implement the steps in the above method embodiments when executed.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A diagnostic data acquisition method, applied to a diagnostic apparatus, comprising:

sending a diagnosis instruction to each Electronic Control Unit (ECU) of a vehicle to be diagnosed through a vehicle-mounted self-diagnosis communication bus, wherein the diagnosis instruction carries an ECU group identifier, the ECU group identifier is used for uniquely identifying the ECU group, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed;

2. The diagnostic data acquisition method according to claim 1, prior to said sending of the diagnostic instruction to each ECU of the vehicle to be diagnosed, comprising:

3. The diagnostic data acquisition method as set forth in claim 2, wherein said sending a configuration instruction to the target ECU comprises:

4. The diagnostic data acquisition method according to claim 1, prior to said sending of the diagnostic instruction to each ECU of the vehicle to be diagnosed, comprising:

5. The diagnostic data acquisition method according to claim 1, wherein the acquiring of the diagnostic data corresponding to the diagnostic instruction returned by the target ECU includes:

6. The diagnostic data acquisition method according to any one of claims 1 to 5, wherein the sending of the diagnostic instruction to each ECU of the vehicle to be diagnosed includes:

7. A diagnostic data acquisition method, applied to an ECU of a vehicle to be diagnosed, comprising:

receiving a diagnosis instruction sent by a diagnosis device through a vehicle-mounted self-diagnosis communication bus, wherein the diagnosis instruction carries a unique identification of an ECU group, the diagnosis instruction carries an ECU group identification, the ECU group identification is used for uniquely identifying the ECU group, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed;

8. A diagnostic data acquisition device, applied to a diagnostic apparatus, comprising:

the vehicle-mounted self-diagnosis system comprises a diagnosis instruction sending unit, a diagnosis instruction receiving unit and a diagnosis instruction processing unit, wherein the diagnosis instruction sending unit is used for sending a diagnosis instruction to each ECU of a vehicle to be diagnosed through a vehicle-mounted self-diagnosis communication bus, the diagnosis instruction carries ECU group identification, the ECU group identification is used for uniquely identifying ECU groups, and the number of the ECUs included in one ECU group is more than 1 and less than the total number of the ECUs of the vehicle to be diagnosed;

9. A diagnostic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any one of claims 1 to 6 when executing the computer program.

10. A smart device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of claim 7 when executing the computer program.