CN114879647A

CN114879647A - ECU fault code test system, electronic controller and car

Info

Publication number: CN114879647A
Application number: CN202210645134.3A
Authority: CN
Inventors: 王文伟; 杨逢江; 魏波
Original assignee: Shenzhen Automotive Research Institute of Beijing University of Technology
Current assignee: Shenzhen Automotive Research Institute of Beijing University of Technology
Priority date: 2022-06-08
Filing date: 2022-06-08
Publication date: 2022-08-09

Abstract

The invention relates to the technical field of automobiles, in particular to an ECU fault code testing system, an electronic controller and an automobile. The test system comprises: a program-controlled power supply and an upper computer; the output end of the programmable power supply is electrically connected with the power supply end of the equipment to be tested, and the upper computer is respectively in communication connection with the equipment to be tested and the programmable power supply; the upper computer is used for controlling the program-controlled power supply to supply power to the equipment to be tested; the upper computer is pre-stored with a pre-programmed test case, and runs the test case to send a fault test instruction to the equipment to be tested; and meanwhile, the upper computer is also used for acquiring a diagnosis message returned by the equipment to be tested and analyzing and processing the diagnosis message to obtain a test result. By adopting the test system, automatic test can be completed only by starting the test system by technicians, and the test efficiency is improved.

Description

ECU fault code test system, electronic controller and car

Technical Field

The invention relates to the technical field of automobiles, in particular to an ECU fault code testing system, an electronic controller and an automobile.

Background

With the popularization of new energy vehicles, the continuous development and promotion of automobile Electronic technology have higher and higher technical requirements on Electronic Control Units (ECUs), and the maintenance difficulty and cost of new energy vehicles are also improved. Therefore, ECUs have developed DTCs (Diagnostic Trouble codes, meaning Diagnostic Trouble codes) based on UDS (universal Diagnostic Services). Nowadays, many faults of automobiles are diagnosed through fault codes, fault diagnosis in development and after-sales repair is convenient, the format and classification of the fault codes are specified in ISO-14229 and ISO-15031, and in order to enable an ECU to accurately record the fault codes when detecting the faults, testers need to simulate corresponding faults aiming at each developed DTC after the ECU is developed, and whether the ECU can accurately record the fault codes when the faults occur is detected. The node loss type fault code records the fault of the node loss through the loss of ECU to other ECU bus messages.

The prior art lacks a fault automatic detection system for an electronic controller, so that a large amount of working time is required to be spent in each detection, and the testing efficiency is low.

Disclosure of Invention

The invention mainly solves the technical problem that the efficiency of detecting the fault code of the electronic controller in the prior art is low.

The application provides an ECU fault code test system, its characterized in that includes: a program-controlled power supply and an upper computer; the output end of the programmable power supply is electrically connected with the power supply end of the equipment to be tested, and the upper computer is respectively in communication connection with the equipment to be tested and the programmable power supply; the upper computer is used for controlling the programmable power supply to supply power to the equipment to be tested;

the upper computer is pre-stored with a pre-programmed test case, and runs the test case to simulate the node loss working condition of the equipment to be tested and send a fault code reading instruction; and meanwhile, the upper computer is also used for acquiring a diagnosis message returned by the equipment to be tested and analyzing and processing the diagnosis message to obtain a test result.

In one embodiment, the upper computer comprises a data storage module and a processor module;

the storage module is used for storing the code data corresponding to the test case; the processor module is used for operating the code data corresponding to the test case to generate the fault test instruction.

In an embodiment, the upper computer includes a data processing module, and the data processing module is configured to analyze and process the diagnostic packet to obtain the test result.

In one embodiment, the storage module is further configured to store fault code information, diagnosis instruction information, diagnosis ID, and DBC information, where the fault code information includes a plurality of fault codes and a fault number corresponding to each fault code; the diagnostic instruction information includes instructions in the UDS to read current/historical DTCs; the diagnostic ID comprises a diagnostic ID of the device under test; the DBC information comprises message data of all other nodes of the network segment where the equipment to be tested is located.

The analyzing and processing of the diagnosis message to obtain the test result comprises: and analyzing the diagnosis message to obtain a corresponding fault code number.

In one embodiment, the upper computer further comprises an output module, and the output module is used for outputting the test result.

In one embodiment, the device further comprises a bus interface device, and the upper computer and the equipment to be tested are in communication connection through the bus interface device;

in one embodiment, the upper computer further comprises a simulation module, and the simulation module sends a diagnosis instruction to the device to be tested through the bus interface device to simulate various working conditions of node loss and the simulation diagnosis device. The bus interface device comprises a data analysis module, and the data analysis module is used for analyzing the fault test instruction and/or the returned diagnosis message.

In one embodiment, the test case includes: and testing whether the node message received by the equipment to be tested is lost or not and recording the node lost message by the equipment to be tested.

In one embodiment, the test case includes: a period of continuous loss and/or a plurality of periods of continuous loss of test node messages.

The present application further provides an electronic controller including an ECU fault code testing system as described above.

The application also provides an automobile which comprises the ECU fault code testing system.

The ECU fault code test system according to the above embodiment includes: a program-controlled power supply and an upper computer; the output end of the programmable power supply is electrically connected with the power supply end of the equipment to be tested, and the upper computer is respectively in communication connection with the equipment to be tested and the programmable power supply; the upper computer is used for controlling the program-controlled power supply to supply power to the equipment to be tested; the upper computer is pre-stored with a pre-programmed test case, and runs the test case to send a fault code test instruction to the equipment to be tested; and meanwhile, the upper computer is also used for acquiring a diagnosis message returned by the equipment to be tested and analyzing and processing the diagnosis message to obtain a test result. By adopting the test system, the technician only needs to start the test system and import the information of the equipment to be tested to complete automatic test, thereby improving the test efficiency.

Drawings

FIG. 1 is a block diagram of a fault code testing system according to an embodiment of the present application;

FIG. 2 is a block diagram of a fault code testing system according to another embodiment of the present application;

FIG. 3 is a block diagram of an upper computer according to an embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating the operation of a fault code testing system according to an embodiment of the present disclosure;

fig. 5 is a schematic configuration interface diagram according to an embodiment of the present application.

Detailed Description

The present invention will be described in further detail with reference to the following detailed description and accompanying drawings. Wherein like elements in different embodiments are numbered with like associated elements. In the following description, numerous details are set forth in order to provide a better understanding of the present application. However, those skilled in the art will readily recognize that some of the features may be omitted or replaced with other elements, materials, methods in different instances. In some instances, certain operations related to the present application have not been shown or described in detail in order to avoid obscuring the core of the present application from excessive description, and it is not necessary for those skilled in the art to describe these operations in detail, so that they may be fully understood from the description in the specification and the general knowledge in the art.

Furthermore, the features, operations, or characteristics described in the specification may be combined in any suitable manner to form various embodiments. Also, the various steps or actions in the method descriptions may be transposed or transposed in order, as will be apparent to one of ordinary skill in the art. Thus, the various sequences in the specification and drawings are for the purpose of describing certain embodiments only and are not intended to imply a required sequence unless otherwise indicated where such sequence must be followed.

At present, the test for the loss-like fault code is generally based on manual test. And the simulation node sends a message according to the DBC on the bus, and after the message is manually stopped to be sent, the diagnostic equipment sends a DTC reading instruction to read the DTC, and the ECU is observed whether to record the fault code lost by the node when the message is not received.

Because the setting condition of the node loss fault codes is generally 5s or n times of the message period, the time precision reaches the millisecond level at most, the ECU needs to send the stored DTC to the bus through the diagnosis message by sending a fault reading instruction, the state change of the DTC needs to be tested according to the message recovery time, the loss and recovery time of the message and the reading time of the DTC cannot be accurately controlled by manual testing, each ECU usually has a large number of loss fault codes, the manual testing efficiency is low, the test environment construction time is long, and the test environment universality is poor. Based on the ECU fault test system provided by the application, the upper computer runs the test case to automatically simulate the node message loss and the recovery time, sends a fault reading instruction in real time, judges the fault code state, can complete automatic test and generate a test report. When different ECUs are tested, only fault code information and the like of the different ECUs need to be imported, the universality is high, and the testing efficiency is improved.

The first embodiment is as follows:

referring to fig. 1, the present embodiment provides an ECU fault code testing system, which includes: a program-controlled power supply 2 and an upper computer 1; the output end of the programmable power supply 2 is electrically connected with the power supply end of the equipment to be tested 3, and the upper computer 1 is respectively in communication connection with the equipment to be tested 3 and the programmable power supply 2; the upper computer 1 is used for controlling the programmable power supply 2 to supply power to the equipment to be tested 3. The upper computer 1 is pre-stored with a pre-programmed test case, and the upper computer 1 runs the test case to send a fault code test instruction to the equipment to be tested 3; meanwhile, the upper computer 1 is also used for obtaining a diagnosis message returned by the device to be tested 3 and analyzing and processing the diagnosis message to obtain a test result. By adopting the test system of the embodiment, the test effect can be improved.

As shown in fig. 3, the upper computer 1 of the present embodiment includes a data storage module 10, a processor module 12, and a data analysis module 11. The storage module 10 is used for storing code data corresponding to the test case; the processor module 12 is configured to run code data corresponding to the test case to generate a fault code test instruction.

The upper computer 1 comprises a data processing module 13, and the data processing module 13 is used for analyzing and processing the diagnosis message to obtain a test result.

In an embodiment, the upper computer 1 further includes a data parsing module 11, and the data parsing module 11 is configured to parse and format-convert the communication data between the upper computer 1 and the device under test 3, so that the communication data meets respective communication protocol requirements.

For example, the storage module 10 stores communication protocol data, and the data parsing module 11 is configured to invoke the communication protocol data to parse the fault test instruction and/or the returned diagnosis message. For example, the upper computer 1 and the device under test 3 adopt can bus communication, and store DBC data in the storage module 10 in advance, where the DBC data is a can signal database and is used to analyze the can signal.

The storage module 10 is further configured to store fault code information, where the fault code information includes all fault codes and a fault code number corresponding to each fault code. The data processing module 13 analyzes the diagnosis message to obtain a corresponding fault code number.

In an embodiment, as shown in fig. 2, the test system further includes a bus interface device 4, and the upper computer 1 and the device under test 3 are communicatively connected through the bus interface device 4; the bus interface device 4 includes a data analysis module for analyzing the fault test instruction and/or the returned diagnosis message.

The test case of this embodiment includes: and testing whether the equipment to be tested detects and records the node loss message when the node message received by the equipment to be tested is lost. For example, test cases include: a period of continuous loss and/or a plurality of periods of continuous loss of test node messages.

The setting condition (which can be understood as a test condition) of the node loss DTC in this embodiment includes two types, namely, a continuous lost node packet 5s and n periods of the continuous lost node packet. The DTC state comprises a current DTC and a historical DTC, when one node detects that the message loss of another node on the bus reaches a DTC setting condition, the current DTC lost by the node is immediately recorded, and if the message of the node is received on the bus, the current DTC is changed into the historical DTC. The method comprises the steps that an ECU is enabled to send DTCs and DTC states by reading a DTC command, the DTC clearing command is used for clearing DTCs stored in the ECU and resetting detection conditions, the DTC clearing command is sent when the current DTCs appear, and the current DTCs are recorded again after loss time is up; and when the history DTC appears, sending a clear DTC instruction, and clearing the history DTC.

Wherein, the bus interface Device 4 of this embodiment adopts a Vector bus interface card supporting CAN and CANFD, the DUT (Device Under Test, i.e. the Device Under Test) of this embodiment is connected with the programmable power supply and the Vector bus interface card supporting CAN and CANFD (e.g. VN1640A, etc.), and is accessed to the analog virtual bus CAN1, the test script is written by CAPL (network access programming language) of the CANoe to generate a testCaseSE module, the CANoe is CAN open environment, which is a bus development environment developed by Vector company in Germany for the development of automobile bus, the power supply of the programmable power supply is controlled by the script, the imported DBC simulation node message is acquired, the IG virtual node message sending module is controlled to send the simulation node message to the bus CAN1, and meanwhile, sending a diagnosis instruction to the DUT, acquiring a diagnosis message returned by the DUT, analyzing and judging, generating a test result and recording a log (test log) in the test process.

For example, the failure setting condition according to the node missing DTC of the present embodiment includes: starting recording DTC at the specified time of continuous loss; the fault recovery conditions are as follows: receiving a lost message; the DTC status change extracts the test cases, as shown in table 1 below.

Table 1 test case extraction

According to the test case, a CAPL program is designed, and as shown in FIG. 4, the flow chart of the CAPL program includes the following steps:

step 1: the method comprises the steps that when a program is started, a CAPL program can read DUT configuration information such as DUT names, diagnosis requests, response IDs (identification) and fault code reading commands, and meanwhile power is called to the DUTs through a power interface to supply power to the DUTs; simulating all node messages to be sent periodically through the imported DBC file, and sending a DTC (digital time series control) clearing instruction to clear DTC information stored in a DUT (device under test); and after the system is stable, sending a DTC reading instruction, analyzing the response message of the DUT whether to record a communication loss DTC, if the node loss DTC is recorded, recording a test problem and ending the DTC test, and if no node loss DTC exists, starting the test aiming at the first node loss DTC.

Step 2: and after a DTC clearing instruction is sent and the system is stable, stopping sending a message 5s specified by the first DTC, recovering for 2s or recovering for 2 times of n times of the cycle, sending a DTC reading instruction, analyzing the response message of the DUT whether to record the node losing DTC, marking the test problem if the node losing DTC is recorded, successfully testing if the node losing DTC is recorded, and sending a DTC clearing instruction by recovering the node message.

And step 3: and after the system is stable, stopping sending the message 3s specified by the first DTC, recovering for 2s or recovering for 2 times of n-2 times of period, sending a DTC reading instruction, analyzing whether to record the node loss history DTC for the DUT response message, marking the test problem if the DTC is recorded, and if the DTC is not recorded, successfully testing, and sending a DTC clearing instruction by the recovery node message.

And 4, step 4: and after the system is stable, stopping sending the message 5s specified by the first DTC and not recovering or not recovering in n times of period, sending a DTC reading instruction, analyzing whether to record the node loss history DTC or not for the DUT response message, if not recording the current DTC, marking a test problem, if recording, successfully testing, and sending a DTC clearing instruction by the recovery node message.

And 5: the first DTC test complete will determine if all the imported DTCs have been tested. If not, the test is continued until all DTC tests are completed, and a test report is generated.

In order to improve the universality of the test device, information of different DUTs needs to be input, and program parameter settings need to be changed through CAPL acquisition, and the DUT information needs to be configured in the embodiment as follows: the method comprises the following steps of DUT name (convenient to record in a test report), DUT diagnosis request and response ID (different DUT diagnosis IDs), DUT fault code instructions, DUT fault setting conditions, CAN and CANFD switching, a parameter import interface and the like. Drawing the parameter import interface on demand is shown in fig. 5.

The CAPL program changes program parameters by calling different values on a parameter import interface to realize the DTC test of loss types of different ECUs, information such as specific fault codes, lost message IDs, message periods and the like of the ECUs are imported through a DTC parameter import key to open an imported ini format template, and the information is imported through software such as a system notepad and the like, and then the information is saved, so that the DTC information can be called through a CAPL language.

Along with the development of automobile electronics, more and more ECUs are arranged on an automobile, the test and verification work aiming at the ECUs is more and more important, and the conventional ECU test has high cost, long time consumption and poor test precision by means of manual test; the main engine plant mostly adopts an automatic test cabinet, the purchasing and debugging cost is high, the functions are multiple, the operation is complex, and the large utilization rate of the floor area of the cabinet is low. The invention provides an ECU node loss fault code test system based on CANOE by analyzing a test principle and a test specification and combining the repeatability of test work. The use is simple, the efficiency of the test repeatability work is greatly improved, bus test tool chains such as vectors and the like commonly used in the industry are used, the cost is low, the carrying is convenient, the CAPL logic can be changed according to special requirements, and the use is flexible.

Example two:

the present embodiment provides an electronic controller including the ECU fault code testing system provided in the first embodiment described above.

Example three:

the embodiment provides an automobile which comprises the ECU fault code testing system provided by the first embodiment.

Those skilled in the art will appreciate that all or part of the functions of the various methods in the above embodiments may be implemented by hardware, or may be implemented by computer programs. When all or part of the functions of the above embodiments are implemented by a computer program, the program may be stored in a computer-readable storage medium, and the storage medium may include: a read only memory, a random access memory, a magnetic disk, an optical disk, a hard disk, etc., and the program is executed by a computer to realize the above functions. For example, the program may be stored in a memory of the device, and when the program in the memory is executed by the processor, all or part of the functions described above may be implemented. In addition, when all or part of the functions in the above embodiments are implemented by a computer program, the program may be stored in a storage medium such as a server, another computer, a magnetic disk, an optical disk, a flash disk, or a removable hard disk, and may be downloaded or copied to a memory of a local device, or may be version-updated in a system of the local device, and when the program in the memory is executed by a processor, all or part of the functions in the above embodiments may be implemented.

The present invention has been described in terms of specific examples, which are provided to aid understanding of the invention and are not intended to be limiting. For a person skilled in the art to which the invention pertains, several simple deductions, modifications or substitutions may be made according to the idea of the invention.

Claims

1. An ECU fault code testing system, comprising: a program-controlled power supply and an upper computer; the output end of the programmable power supply is electrically connected with the power supply end of the equipment to be tested, and the upper computer is respectively in communication connection with the equipment to be tested and the programmable power supply; the upper computer is used for controlling the programmable power supply to supply power to the equipment to be tested;

the upper computer is pre-stored with a pre-programmed test case, and runs the test case to send a fault test instruction to the equipment to be tested; and meanwhile, the upper computer is also used for acquiring a diagnosis message returned by the equipment to be tested and analyzing and processing the diagnosis message to obtain a test result.

2. The ECU fault code testing system of claim 1, wherein the upper computer comprises a data storage module and a processor module;

3. The ECU fault code testing system according to claim 1, wherein the upper computer comprises a data processing module, and the data processing module is used for analyzing and processing the diagnosis message to obtain the testing result.

4. The ECU fault code testing system of claim 3, wherein the storage module is further configured to store fault code information, the fault code information including a plurality of fault codes and a fault number corresponding to each fault code;

5. The ECU fault code testing system of claim 2, wherein the upper computer further comprises an output module for outputting the test result.

6. The ECU fault code testing system according to claim 1, further comprising a bus interface device, wherein the upper computer and the device under test are in communication connection through the bus interface device;

the bus interface device comprises a data analysis module, and the data analysis module is used for analyzing the fault test instruction and/or the returned diagnosis message.

7. The ECU fault code testing system of claim 1, wherein the test case comprises: and testing whether the node message received by the equipment to be tested is lost or not and recording the node lost message by the equipment to be tested.

8. The ECU fault code testing system of claim 1, wherein the test case comprises: a period of continuous loss and/or a plurality of periods of continuous loss of test node messages.

9. An electronic controller comprising the ECU fault code testing system of any one of claims 1-8.

10. An automobile comprising the ECU fault code testing system according to any one of claims 1 to 8.