JP2016014558A - Inspection system for automobile electronic control unit - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an inspection system capable of inspecting an automobile electronic control unit efficiently with high accuracy while using a general-purpose diagnostic tool.SOLUTION: An inspection system for an automobile electronic control unit according to the present invention includes a general-purpose diagnostic tool for performing communication with the automobile electronic control unit to be inspected, a machinery device (robot arm) for manipulating the manipulation part of the diagnostic tool, an image-capturing device (camera) for image-capturing the display part of the diagnostic tool, and an HILS system. The inspection system controls the machinery device, manipulates the manipulation part of the diagnostic tool, and has prescribed information displayed on the display part of the diagnostic tool, and thereby collating the content of this display screen and the reference content of display.

Description

  The present invention relates to an inspection system for inspecting an automobile electronic control unit using a diagnostic tool.

  Patent Document 1 discloses a pseudo sensor signal that is equivalent to a sensor signal generated by receiving an actuator drive signal when an actual machine that is an original control target of an electronic control unit operates in accordance with a specified operation pattern. And an electronic control unit inspection device configured to supply the pseudo sensor signal to the electronic control unit and receive an actuator drive signal emitted from the electronic control unit.

JP 2008-261793 A

  By the way, a general-purpose diagnostic tool (portable diagnostic device) such as GST (General Scan Tool) that is manually operated is connected to the electronic control unit, and the operator confirms the operation result on the diagnostic tool screen while operating the diagnostic tool. However, when the inspection of the electronic control unit is performed, the inspection accuracy is reduced due to factors such as a failure of the diagnostic tool, a communication failure between the diagnostic tool and the electronic control unit, and an operation error of the operation unit of the diagnostic tool.

  Therefore, in order to maintain high inspection accuracy in the inspection operation for manually operating the diagnostic tool, it is necessary to proceed with the inspection process while verifying the presence or absence of the above-described defect factors. For this reason, the work procedure is complicated and the same operation is repeated, so that the skill of the worker is required and the inspection time is sometimes increased.

  Therefore, an object of the present invention is to provide an inspection system that can perform inspection of an automobile electronic control unit with high efficiency and high accuracy while using a general-purpose diagnostic tool.

  Therefore, an inspection system for an automotive electronic control unit according to the present invention includes a display unit and an operation unit, and includes a diagnostic tool that communicates with an electronic control unit for an automobile to be inspected, and an operation unit for the diagnostic tool. Photographing a mechanical device to be operated, means for storing reference operation contents of the operation unit and reference display contents of the display unit, means for controlling the machine device based on the reference operation contents, and a display unit of the diagnostic tool And a means for collating the reference display content with the display content obtained from the image of the display section taken by the imaging device.

  According to the above invention, the operation of the operation part of the diagnostic tool and the consistency judgment of the display content of the display part can be automated, and the inspection of the electronic control unit for automobile can be performed with high efficiency and high accuracy while using a general-purpose diagnostic tool. Become.

It is a block diagram showing an example of composition of an inspection system concerning one embodiment of the present invention. It is a figure which illustrates the appearance of the diagnostic tool concerning one embodiment of the present invention. It is a block diagram which illustrates the flow of information in the inspection system concerning one embodiment of the present invention. It is a flowchart which shows the operation example (1st operation example) of the test | inspection system of embodiment of this invention. It is a flowchart which illustrates the collation process in the said 1st operation example. It is a flowchart which illustrates the collation process in the said 1st operation example. It is a flowchart which illustrates the collation process in the said 1st operation example. It is a flowchart which illustrates the collation process in the said 1st operation example. It is a flowchart which shows the operation example (2nd operation example) of the test | inspection system which concerns on one Embodiment of this invention. It is a flowchart which illustrates the collation process in the said 2nd operation example. It is a flowchart which illustrates the collation process in the said 2nd operation example. It is a flowchart which illustrates the collation process in the said 2nd operation example. It is a flowchart which shows the operation example (3rd operation example) of the test | inspection system which concerns on one Embodiment of this invention. It is a flowchart which illustrates the collation process in the said 3rd operation example. It is a flowchart which illustrates the collation process in the said 3rd operation example. It is a flowchart which shows the operation example (4th operation example) of the test | inspection system which concerns on one Embodiment of this invention. It is a flowchart which illustrates the collation process in the said 4th operation example.

Embodiments of the present invention will be described below.
FIG. 1 is a configuration block diagram showing an example of an inspection system according to the present invention.
An inspection system 1 in FIG. 1 is a system for inspecting an electronic control unit (ECU) 2 that controls an engine (internal combustion engine) mounted on an automobile (vehicle) alone. The ECU 2 includes a microcomputer, a communication circuit, and the like, and is a device that calculates and outputs drive signals for various actuators for operating the engine based on various input signals when mounted on the vehicle.

The inspection system 1 includes a HILS (Hardware In the Loop Simulation) system 10, a general-purpose diagnostic tool 20, a camera (imaging device) 30 for photographing the diagnostic tool 20, and a robot arm (machine) for automatically operating the diagnostic tool 20 Device) 40.
The diagnostic tool 20, the camera 30, and the robot arm 40 are integrally attached to a frame not shown.

The HILS system 10 is a system that is connected to the ECU 2 to be diagnosed via a detachable harness 51 and performs a simulation by exchanging signals with the ECU 2 in the same manner as the engine that is the control target of the ECU 2.
The HILS system 10 includes a HILS personal computer (PC) 11.

The PC 11 includes an arithmetic device, a control device, a storage device, an input / output device, a display device, and the like. The PC 11 is equipped with HILS software and inspection software for realizing simulation by HILS, and further includes a database DB.
The HILS software includes software for instructing the HILS system 10 of operating conditions (mode travel) to be simulated, and the inspection software includes software for controlling the operation of the camera 30 and the robot arm 40. It is.
The HILS system 10 includes a driver model 12a and an engine model 12b as a model simulator 12.

The driver model 12a is a model for simulating a driving operation by a driver of an automobile, and outputs information such as an accelerator opening degree that matches a predetermined driving pattern to the engine model 12, for example.
The engine model 12b is a model for simulating the function of the engine. Based on information such as an accelerator opening degree transmitted from the driver model 12a, an actuator drive signal output from the ECU 2, and the like, The actuator motion is simulated to generate simulated sensor signals similar to the various sensor signals generated by the actual engine.
The simulated sensor signal generated by the engine model 12b is transmitted to the ECU 2 via the harness 51.

The ECU 2 performs an arithmetic process on the simulated sensor signal transmitted from the engine model 12b based on engine control software to generate an actuator control signal, and transmits the actuator drive signal to the engine model 12b.
The simulated sensor signal is, for example, an intake air flow rate measurement signal, an air-fuel ratio measurement signal, or the like. The ECU 2 calculates a fuel injection amount (fuel injection pulse width) based on these simulated sensor signals, and the fuel injection amount. An injection pulse signal corresponding to the output is output as a drive signal for the fuel injection valve (actuator).

Further, diagnostic software is installed in the ECU 2 to perform failure diagnosis of sensors and actuators, and further self-diagnosis of the engine control function.
A server computer that manages the database DB may be separately provided, and the server computer and the PC 11 may be connected via a network, and the PC 11 may access the database DB via the network.

The diagnostic tool 20 is a general-purpose diagnostic tool that is manually operated, such as GST (General Scan Tool). As illustrated in FIG. 2, the display unit 20a made of liquid crystal, ten keys, direction keys, function keys, etc. And an operation unit 20b including various push buttons.
The diagnostic tool 20 can be a device including a touch panel that serves as both the display unit 20a and the operation unit 20b, and the operation unit 20b of the diagnostic tool 20 is not limited to a push button.

The robot arm 40 is a mechanical device having a function of pressing down various push buttons constituting the operation unit 20b of the diagnostic tool 20 in the same manner as when manually operated, and is predetermined according to an operation command of the PC 11. Press down the push button.
That is, in the inspection system 1, instead of the operator manually operating the operation unit 20 b of the diagnostic tool 20, the robot arm 40 driven and controlled by the PC 11 automatically operates the operation unit 20 b of the diagnostic tool 20. The operation 20 (in other words, the inspection process of the ECU 2 using the diagnostic tool 20) is automated.

The diagnostic tool 20 and the ECU 2 are connected by a detachable harness 52, and the communication monitoring unit 13 of the HILS system 10 provided in the middle of the harness 52 acquires a communication log between the diagnostic tool 20 and the ECU 2. Then, the communication monitoring unit 13 transmits the acquired communication log to the PC 11.
Note that communication is performed between the diagnostic tool 20 and the ECU 2 based on a data transfer standard such as Controller Area Network (CAN).

The camera 30 captures the display unit 20a and the operation unit 20b (in other words, the operation unit for pressing the robot arm 40) of the diagnostic tool 20 in accordance with a command from the PC 11, and transmits a signal of the captured image to the PC 11. To do.
Then, the PC 11 analyzes the image of the operation unit 20b (robot arm 40) of the diagnostic tool 20 photographed by the camera 30, so that the operation of the operation unit 20b by the robot arm 40 is normally performed (as instructed). The software has a function to verify whether or not it exists.

Further, the PC 11 has a function of analyzing the image of the display unit 20a of the diagnostic tool 20 taken by the camera 30 and verifying whether the display content of the display unit 20a is normal as software.
Further, the PC 11 has a function of verifying whether or not the communication log information acquired by the communication monitoring unit 13 is normal as software.

Reference operation content (button operation procedure) of the diagnostic tool 20, reference display content (normal display content) of the display unit 20a, reference communication information (normal communication information) between the diagnostic tool 20 and the ECU 2, and the like Are stored in the database DB in advance.
Then, the PC 11 performs inspection processing including automatic operation control of the operation unit 20b of the diagnostic tool 20 and collation processing of display contents of the display unit 20a based on information read from the database DB, and is obtained in the inspection process. Various data (image information, communication log, etc.) are stored in the database DB.

In addition, the camera which image | photographs the display part 20a of the diagnostic tool 20, and the camera which image | photographs the operation part 20b (pressing operation part of the robot arm 40) of the diagnostic tool 20 can be provided separately. In addition, it is possible to change the angle of one camera and selectively perform one of the photographing of the display unit 20a and the photographing of the operation unit 20b.
The robot arm 40 includes, for example, a mechanical device in which a plurality of push buttons constituting the operation unit 20b of the diagnostic tool 20 are provided with a push operation mechanism, or a button that has one or a plurality of push operation mechanisms and performs a push-down operation. A mechanical device having a mechanism for moving the pressing operation mechanism to the position can be provided.

FIG. 3 is a diagram schematically showing the flow of data in the inspection system 1.
The PC 11 (operating condition instructing unit) instructs the driver model 12a about the engine operating condition (vehicle driving mode) in the simulated operation of the ECU 2.
The driver model 12a outputs information on the accelerator opening corresponding to the instructed driving condition to the engine model 12b.

The engine model 12b calculates electric signals (simulated sensor signals) output from various sensors that detect the operating state of the engine when the engine is operated at the accelerator opening output by the driver model 12a, and the electric signals are calculated. It outputs to ECU2.
The ECU 2 that receives the electrical signal output from the engine model 12b calculates the drive control signal of an actuator such as a fuel injection valve based on the electrical signal output from the engine model 12b, as in the case of actually inputting the sensor output. And trouble diagnosis.

On the other hand, the PC 11 (robot arm control unit) automatically operates the operation unit 20b of the diagnostic tool (GST) 20 according to the reference operation content (operation procedure of the diagnostic tool 20) stored in the database DB on the storage device such as a hard disk. Operation commands (control signals) for operation are sequentially output to the robot arm 40.
The robot arm 40 pushes down a push button corresponding to an operation command (press-down command) sent from the PC 11 among the plurality of push buttons constituting the operation unit 20b of the diagnostic tool 20.

When the operation unit 20b is operated by the robot arm 40, the diagnostic tool 20 performs a predetermined operation corresponding to the pressed button, for example, command transmission to the ECU 2 or switching of display contents of the display unit 20a. .
The ECU 2 transmits response information (such as a failure diagnosis result signal and an engine operating condition signal) corresponding to the command sent from the diagnostic tool 20 to the diagnostic tool 20.
The communication content between the diagnostic tool 20 and the ECU 2 is recorded by the communication monitoring unit 13 of the HILS system 10, and the communication log (communication content, transmission / reception data, CAN data) is sent to the PC 11.

The PC 11 (camera control unit) outputs a signal for instructing an imaging operation to the camera 30 at a timing determined in advance based on the inspection procedure (operation procedure of the diagnostic tool 20). The camera 30 responds to the imaging command. The diagnostic tool 20 (and the robot arm 40) is photographed, and a signal of the photographed image is transmitted to the PC 11 as photographing information.
Here, the shooting information sent from the camera 30 to the PC 11 includes an image on the display unit 20a (an image showing the display content) and an image on the operation unit 20b (an image showing a button press operation by the robot arm 40). It is.

The inspection system 1 is configured to perform the inspection process of the ECU 2 while automatically verifying the operation state of the robot arm 40, the operation state of the diagnostic tool 20, and the communication state between the diagnostic tool 20 and the ECU 2. The
Hereinafter, the verification process in the inspection system 1 will be described in detail.

The routine shown in the flowchart of FIG. 4 shows an example of the verification process of the operation state and communication state of the inspection system 1.
In step S110, the PC 11 (operation condition instructing unit) reads out the operation condition (travel pattern, mode travel) when the engine control operation by the ECU 2 to be inspected is simulated, from the database DB, and the read operation condition. Is output to the driver model 12a. As a result, an electric signal (simulated sensor signal) is output from the engine model 12b to the ECU 2, and a simulated control operation in the ECU 2 is executed.

In the next step S120, the PC 11 (robot arm control unit) reads information on the predetermined operation content (push-down operation button) of the diagnostic tool 20 from the database DB, and controls the robot arm 40 according to the read information.
In step S130, the robot arm 40 performs a push-down operation in accordance with the commanded order of the buttons for which the push-down command has been made among the buttons constituting the operation unit 20b.

When the operation unit 20b is automatically operated by the robot arm 40, the diagnostic tool 20 transmits a predetermined command that is predetermined according to the pressed button to the ECU 2 in step S140.
The communication monitoring unit 13 of the HILS system 10 monitors communication between the diagnostic tool 20 and the ECU 2, and records and acquires a command transmitted from the diagnostic tool 20 to the ECU 2 as a communication log in step S150. The communication log is transferred to the PC 11.

Next, the PC 11 (camera control unit) outputs a shooting request (shooted image transmission command) to the camera 30 in step S160.
Then, the PC 11 (camera control unit) captures and stores the image transmitted from the camera 30 in step S170. The image stored by the PC 11 is an image that allows the PC 11 to determine the button of the diagnostic tool 20 that the robot arm 40 has actually pushed down, and an image that allows the PC 11 to determine the display content of the display unit 20 a of the diagnostic tool 20. is there.
Note that the image saved by the PC 11 in step S170 represents one image data in which both the button operation state of the operation unit 20b and the display content of the display unit 20a are displayed, or the button operation state of the operation unit 20b. Two pieces of image data, that is, image data and image data representing the display content of the display unit 20a can be used.

In step S180, the PC 11 analyzes an image captured by the camera 30, detects a button that the robot arm 40 actually performs a push-down operation, and instructs a push-down operation (target button operation, reference operation content); A process of verifying with the button (actual operation content) actually pressed down by the robot arm 40, that is, a process of verifying whether or not a button operation corresponding to the instruction has been performed is performed.
Here, an example of the processing content of step S180 will be described with reference to the flowchart of FIG.

In step S181, the PC 11 collates the button instructed to be pressed down with the button actually pressed down by the robot arm 40 detected based on the captured image of the camera 30.
If the button that the PC 11 has instructed to press down matches the button that the robot arm 40 has actually pressed down (when all of the instructed button operations have been performed as instructed), the PC 11 proceeds to step S182. .

In step S182, the PC 11 controls the robot arm 40 and the data indicating that the operation of the robot arm 40 (automatic operation of the operation unit 20b of the diagnostic tool 20) is normally performed (normal determination signal for button automatic operation). ).
On the other hand, when the button that the PC 11 has instructed to press down does not match the button that the robot arm 40 has actually pressed down (when at least part of the instructed button operation is not performed as instructed), the PC 11 The process proceeds to step S183.
In step S183, the PC 11 has data indicating that at least one of the control of the robot arm 40 and the operation of the robot arm 40 is abnormal and the automatic operation of the operation unit 20b of the diagnostic tool 20 is not normally performed ( Record button automatic operation error determination signal).

As described above, it is determined whether or not the automatic operation of the button of the diagnostic tool 20 is normally performed, and by recording the determination result, the abnormality of the inspection system 1 in which the button operation different from the instruction is performed. It is possible to suppress the presence or absence of abnormality of the ECU 2 in the state, maintain the reliability of the automatic inspection process, and perform maintenance work of the inspection system 1 (such as adjustment work of the robot arm 40) based on abnormality information of button operation Can be easily performed.
Note that the result of the collation process in step S180 and the results of various collation processes described below are displayed on the display device of the PC 11, and the operator can check whether there is an abnormality in the inspection system 1. .

Next, in step S190, the PC 11 sets the target communication log (reference command, target command) corresponding to the button actually pressed down by the robot arm 40 and the communication log actually acquired by the communication monitoring unit 13 (actual diagnosis). A process for verifying whether or not the diagnostic tool 20 has output a command commensurate with the button operation is performed.
The command transmitted from the diagnostic tool 20 to the ECU 2 is, for example, data indicating the engine or vehicle operating state calculated by the ECU 2 based on an electrical signal (simulated sensor signal) from the model simulator 12 (engine rotation speed, vehicle speed, engine For example, a cooling water temperature transfer instruction.

Here, an example of the processing content of step S190 is demonstrated according to the flowchart of FIG.
In step S191, the PC 11 collates the target command recorded in the database DB corresponding to the button pressed by the robot arm 40 with the command monitored by the communication monitoring unit 13.
If the target command and the actually transmitted command match, the PC 11 proceeds to step S192, and data indicating that the diagnostic tool 20 has output a command suitable for the button operation by the robot arm 40 (diagnostic tool 20 Normality determination signal) is recorded.

On the other hand, if the target command and the actually transmitted command do not match, the PC 11 proceeds to step S193, and data indicating that the diagnostic tool 20 does not output a command corresponding to the button operation by the robot arm 40 ( The abnormality determination signal of the diagnostic tool 20) is recorded.
It is possible to suppress the presence or absence of abnormality of the ECU 2 in the abnormal state of the diagnostic tool 20 by the diagnostic processing of the command output function, and to perform inspection such as replacement of the diagnostic tool 20 based on the abnormal information of the diagnostic tool 20 Maintenance work of the system 1 can be easily performed.

As described above, the PC 11 determines whether the operation unit 20b of the diagnostic tool 20 is normally operated by the robot arm 40, and further, whether the diagnostic tool 11 outputs a command corresponding to the operation by the robot arm 40. Diagnose and record the results.
And ECU2 which received the command (transfer instruction | command) from the diagnostic tool 20 calculates the response information corresponding to a command in step S200, and transmits the calculated response information toward the diagnostic tool 20.
If the command is, for example, an instruction to transfer data indicating the engine or vehicle operating state calculated by the ECU 2, the response information transmitted by the ECU 2 is data indicating the engine or vehicle operating state.

The communication monitoring unit 13 of the HILS system 10 monitors communication between the diagnostic tool 20 and the ECU 2, and records and acquires the response information transmitted from the ECU 2 to the diagnostic tool 20 as a communication log in step S210. The communication log is transferred to the PC 11.
In step S220, the PC 11 that has received the communication log from the communication monitoring unit 13 transmits the response information (communication log) actually transmitted by the ECU 2 to the diagnostic tool 20, and the command (communication log) transmitted by the diagnostic tool 20 to the ECU 2. A process of collating target response information (reference communication information, reference response information) stored in advance in the database DB in correspondence with the simulated operation state (engine operating condition) at that time, that is, a response corresponding to the command by the ECU 2 A process for verifying whether the information is in a normal state in which information is generated and output is executed.

Here, an example of the processing content of step S220 is demonstrated according to the flowchart of FIG.
In step S <b> 221, the PC 11 collates the response information actually transmitted from the ECU 2 to the diagnostic tool 20 with target response information corresponding to the command transmitted from the diagnostic tool 20 to the ECU 2.

  If the response information actually transmitted from the ECU 2 to the diagnostic tool 20 matches the target response information corresponding to the command transmitted from the diagnostic tool 20 to the ECU 2, the PC 11 proceeds to step S222 and the ECU 2 operates normally. That is, data indicating that the ECU 2 is in a state of being ready, that is, data indicating that the ECU 2 is correctly reading the command and correctly calculating and outputting response information corresponding to the command (normal determination signal of the ECU 2) is recorded.

  On the other hand, when the response information actually transmitted from the ECU 2 to the diagnostic tool 20 and the target response information corresponding to the command transmitted from the diagnostic tool 20 to the ECU 2 do not match, the PC 11 proceeds to step S223 and the operation of the ECU 2 is abnormal. That is, data indicating that the ECU 2 corresponds to at least one of a state in which the command is not read correctly and a state in which an abnormality has occurred in the calculation processing of response information based on the command (ECU 2 (Abnormal judgment signal).

In this way, by comparing the response information expected for the command output by the diagnostic tool 20 with the response information actually output by the ECU 2, it is possible to accurately diagnose whether the operation of the ECU 2 is normal or abnormal.
The PC 11 (camera control unit) outputs a photographing request to the camera 30 in step S230 at the timing when the communication log of the response information from the ECU 2 is transferred.
In the next step S240, the PC 11 (camera control unit) takes in the image transmitted from the camera 30 and stores it in the database DB. The image stored by the PC 11 is an image that allows the PC 11 to read the display content of the display unit 20 a of the diagnostic tool 20.

On the other hand, the diagnostic tool 20 that has received the response information from the ECU 2 performs a process of updating the display content of the display unit 20a based on the response information, that is, a process of switching to a screen that displays the response information from the ECU 2 in step S250. Do.
Then, when the display content of the display unit 20a is switched in step S260, the PC 11 (camera control unit) displays an image of the display unit 20a taken by the camera 30, that is, an image showing a display screen of response information from the ECU 2. Import and save.
Note that the image stored in the PC 11 in step S240 and step S260 can be a single image in which both the button operation state and the display content of the display unit 20a are shown, and only the display unit 20a is photographed. It is also possible to obtain an image (including a trimmed image).

Next, in step S270, the PC 11 collates the content actually displayed on the display unit 20a of the diagnostic tool 20 with the target display content (reference display content) based on the response information (communication log) from the ECU 2. Process. That is, in step S270, the PC 11 determines whether the diagnostic tool 20 correctly displays the response information from the ECU 2 on the display unit 20a, in other words, whether the display function (operation) of the diagnostic tool 20 is normal. A process for verifying this is implemented.
Here, an example of the processing content of step S270 is demonstrated according to the flowchart of FIG.

In step S271, the PC 11 collates the content actually displayed on the display unit 20a of the diagnostic tool 20 with the target display content based on the response information (communication log) from the ECU 2.
For example, the PC 11 may perform a character recognition process on the image of the display unit 20a captured by the camera 30 to convert the character image into a character code, and perform a display content matching process in step S271 based on the character code. it can.

  When the content displayed on the display unit 20a of the diagnostic tool 20 matches the target display content based on the response information from the ECU 2, the PC 11 proceeds to step S272, and the display content on the display unit 20a of the diagnostic tool 20 is Data indicating correctness, that is, data indicating that the information input and display functions of the diagnostic tool 20 are normal (normal determination signal of the diagnostic tool 20) is recorded.

On the other hand, when the content displayed on the display unit 20a of the diagnostic tool 20 does not match the target display content based on the response information from the ECU 2, the PC 11 proceeds to step S273, and the display content on the display unit 20a of the diagnostic tool 20 is Data indicating that there is an error, that is, data indicating that an abnormality has occurred in the information input and / or display function of the diagnostic tool 20 (abnormality determination signal of the diagnostic tool 20) is recorded.
As described above, if the diagnostic tool 20 detects an abnormality that does not display the content corresponding to the response information transmitted from the ECU 2, the presence or absence of the abnormality of the ECU 2 in the abnormal state of the diagnostic tool 20 is specified. In addition, maintenance work of the inspection system 1 such as replacement of the diagnostic tool 20 can be easily performed based on abnormality information of the diagnostic tool 20.

Thereafter, the PC 11 discriminates the result of the collation processing performed in step S180, step S190, step S220, and step S270, that is, normal / abnormal robot arm control, normal / abnormal diagnostic tool 20, and normal / abnormal ECU2. The result is stored in the database DB in step S280.
As described above, the PC 11 determines whether or not the operation unit 20b of the diagnostic tool 20 is normally operated by the robot arm 40, and further includes a command output function of the diagnostic tool 20, a response function of the ECU 2 to the command, The screen display function in the diagnostic tool 20 is verified, and the result is stored in the database DB.

According to the above verification processing, it is verified that the automatic operation of the diagnostic tool 20 by the robot arm 40 is normally performed. Therefore, it is possible to suppress the occurrence of an inspection error due to an operation error of the diagnostic tool 20, and the inspection processing. Can be carried out efficiently.
In addition, the communication between the diagnostic tool 20 and the ECU 2 is monitored, the diagnostic tool 20 transmits a command corresponding to the operation of the operation unit 20b, and verifies whether the ECU 2 returns response information corresponding to the command. Therefore, it is possible to suppress the occurrence of an inspection error due to a communication abnormality between the diagnostic tool 20 and the ECU 2.

Furthermore, the communication between the diagnostic tool 20 and the ECU 2 is monitored, and it is diagnosed by verifying whether or not the display content of the display unit 20a of the diagnostic tool 20 matches the response information from the ECU 2. The occurrence of an inspection error due to an abnormality of the tool 20 can be suppressed.
Along with these effects, the inspection system 1 can perform the inspection of the ECU 2 with high efficiency and high accuracy while using the general-purpose diagnostic tool 20.
Furthermore, by determining whether or not there is a failure in the diagnostic tool 20 and the robot arm 40, and determining whether or not there is a communication abnormality between the diagnostic tool 20 and the ECU 2, it is possible to identify the location where the failure occurs in the inspection system 1. Appropriate maintenance work can be easily performed.

The routine shown in the flowchart of FIG. 9 shows an example of processing for verifying the presence or absence of erroneous display of the diagnostic tool 20.
In step S310, the PC 11 reads out the engine operating conditions for simulating the ECU 2 from the database DB, gives them to the model simulator 12, and starts the simulating operation of the ECM 2.

Next, in step S320, the PC 11 reads information for setting an electrical signal (simulated sensor signal) output from the model simulator 12 to the ECU 2 to an abnormal (failure) state from the database DB, and stores the data in the model simulator 12. Set. As a result, the ECU 2 performs a simulated operation in an abnormal mode in which a simulated sensor signal having a predetermined abnormal pattern is input.
In step S330, the ECU 2 calculates predetermined diagnostic parameters based on the electrical signal (simulated sensor signal) output from the model simulator 12, and based on the diagnostic parameters, various devices (various sensors, actuators) A process for diagnosing the presence or absence of an abnormality (failure diagnosis process) is performed, and a simulated operation is performed in the abnormal mode, whereby a predetermined abnormal state corresponding to the setting of the simulated operation is detected.

In step S340, the communication monitoring unit 13 of the HILS system 10 starts to acquire a communication log (record transmission / reception data) between the diagnostic tool 20 and the ECU 2.
In step S350, the PC 11 displays button operation information (reference operation content) for causing the display unit 20a of the diagnostic tool 20 to display the number of parts (devices and sensors) (the number of abnormality diagnosis) that the ECU 2 has diagnosed an abnormal condition. Is read from the database DB, and the robot arm 40 is controlled based on the read operation information.

  Under the control of the robot arm 40 by the PC 11, a predetermined button of the operation unit 20b of the diagnostic tool 20 is pushed down, and the diagnostic tool 20 transmits a command requesting the ECU 2 to notify the number of abnormality diagnosis in response to the button operation. Transmits information on the number of devices in which an abnormality is detected in the failure diagnosis processing to the diagnostic tool 20 as response information to the command. The diagnostic tool 20 that has received the information on the number of abnormality diagnosis from the ECU 2 displays the number of abnormality diagnosis on the display unit 20a (switches the display on the display unit 20a to a display screen for the number of abnormality diagnosis).

When the display of the display unit 20a of the diagnostic tool 20 is switched to the display screen of the number of abnormality diagnosis and the image of the display unit 20a captured by the camera 30 is switched, the PC 11 displays the image of the display unit 20a captured by the camera 30, that is, An image of a screen (first diagnosis result screen) that displays the number of abnormality diagnoses is stored.
Next, in step S360, the PC 11 reads the button operation (reference operation information) for displaying a list of diagnosis results (second diagnosis result screen) by the ECU 2 on the display unit 20a of the diagnosis tool 20 from the database DB and reads the button operation. The robot arm 40 is controlled based on the operation information. That is, the PC 11 causes the robot arm 40 to perform a button operation for switching the display of the display unit 20a to the diagnosis result list display screen.

By the button operation by the robot arm 40, the diagnostic tool 20 transmits a command requesting the ECU 2 to notify the diagnosis result list, and the ECU 2 performs abnormality / normality for each device that is the target of failure diagnosis as response information to the command. The information of the diagnostic result is transmitted to the diagnostic tool 20.
The diagnostic tool 20 that has acquired the diagnostic result list information from the ECU 2 switches the display content of the display unit 20a to a display showing a list of diagnostic results in the ECU 2.

When the display of the display unit 20a of the diagnostic tool 20 is switched to the display screen of the diagnosis result list and the image of the display unit 20a captured by the camera 30 is switched, the PC 11 displays the image of the display unit 20a captured by the camera 30, that is, An image of a screen (second diagnostic result screen) that displays a list of diagnostic results is saved.
The display screen of the diagnosis result list on the display unit 20a of the diagnostic tool 20 shows, for example, the name of the sensor or actuator that the ECU 2 has been subjected to diagnostic processing, and whether the diagnosis has been performed normally or abnormally in the diagnosis of the device. It is a screen which lists the display (OK / NG distinction) to show.

In step S370, the PC 11 reads the button operation content for switching the display content of the display unit 20a of the diagnostic tool 20 to the display of the diagnosis parameter (third diagnosis result screen) in the diagnostic processing of the ECU 2, from the database DB, and the read button The robot arm 40 is controlled according to the operation content.
Under the control of the robot arm 40 by the PC 11, the operation unit 20b of the diagnostic tool 20 is operated so as to switch the display content of the display unit 20a to display of diagnostic parameters. Then, the diagnostic tool 20 transmits a command for requesting notification of a diagnostic parameter in response to a button operation, acquires a diagnostic parameter as response information from the ECU 2, and diagnoses the display content of the display unit 20a based on the acquired information. Switch to parameter display.

In the diagnostic process, the ECU 2 monitors the sensor output voltage value, the state quantity such as the intake air amount and the engine rotation speed obtained from the sensor output, and diagnoses the maximum value, the minimum value, the value at the time of occurrence of an abnormality, etc. It has a function to save as parameters.
If the command transmitted from the diagnostic tool 20 is a command requesting notification of diagnostic parameters, the ECU 2 transmits the stored diagnostic parameter information to the diagnostic tool 20 as response information.

When the display content of the display unit 20a of the diagnostic tool 20 is switched to display of diagnostic parameters, the PC 11 displays an image of the display unit 20a taken by the camera 30, that is, an image of a diagnostic parameter display screen (third diagnostic result screen). save.
As described above, the diagnostic tool 20 transmits a command to the ECU 2 in accordance with the operation of the operation unit 20b, thereby reading data related to the diagnostic processing result in the ECU 2 from the ECU 2, and outlines the diagnostic contents in the ECU 2. It has a function to switch and display from step to detail step by step.

Then, the PC 11 automatically operates the operation unit 20b of the diagnostic tool 20 by controlling the robot arm 40 in order to sequentially display the diagnosis contents (diagnosis result screen) in the ECU 2 on the display unit 20a of the diagnostic tool 20.
On the other hand, the camera 30 captures the display unit 20a on which each diagnosis result screen is displayed, and the PC 11 records the display content of the display unit 20a captured by the camera 30, that is, the image of each diagnosis result screen.

In step S380, the PC 11 determines whether the display content (display content of each diagnosis result screen) analyzed from the image obtained by photographing the display unit 20a of the diagnostic tool 20 is normal.
In the next step S390, the PC 11 records the image captured by the camera 30 (image captured from the diagnosis result screen), the communication log, the determination result in step S380, and the like in the database DB.

The flowchart of FIG. 10 shows an example of the determination process in step S380 of the flowchart of FIG.
In step S410, the PC 11 determines the number of sensors and actuators set in the abnormal state in the simulated operation of the ECU 2 (the target abnormality diagnosis number, the reference abnormality diagnosis number, the electrical signal NG setting state), and the display unit 20a ( The number of abnormal diagnoses displayed on the first diagnosis result screen) is compared. Note that the PC 11 detects the number of abnormality diagnoses displayed on the display unit 20a of the diagnostic tool 20 by character recognition processing for an image signal obtained by photographing the first diagnosis result screen.

If the number of abnormality diagnoses displayed on the display unit 20a of the diagnostic tool 20 matches the number of abnormality diagnoses set in the simulation operation of the ECU 2, the PC 11 determines the number of abnormality diagnoses of the diagnostic tool 20 in step S420. Determine that the display is normal and record.
On the other hand, if the number of abnormality diagnoses displayed on the display unit 20a of the diagnostic tool 20 does not match the number of abnormalities set in the simulation operation of the ECU 2, the PC 11 displays the number of abnormality diagnoses of the diagnostic tool 20 in step S430. Determine that is abnormal and record.

Next, in step S440, the PC 11 displays normal / abnormal settings (OK / NG state of electric signal, reference diagnosis result list) of each device in the simulated operation of the ECU 2 and the display unit 20a of the diagnostic tool 20. Compare with the list of diagnostic results. The PC 11 detects a list of diagnostic results displayed on the display unit 20a of the diagnostic tool 20 by character recognition processing for an image signal obtained by photographing the second diagnostic result screen.
When the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 matches the normal / abnormal setting of each device in the simulation operation of the ECU 2, the PC 11 determines whether the diagnostic tool 20 Determine that the display of the diagnosis result list is normal and record it.

Here, the determination of whether or not the diagnosis result lists match is set, for example, for each device (sensor) such as a water temperature sensor or an oxygen sensor based on normality / abnormality displayed on the display unit 20a and simulated operation of the ECU 2. This is a process of determining whether or not the normal / abnormal state matches. For example, if the settings in the simulated operation of the ECU 2 are the water temperature sensor: abnormal, the oxygen sensor: normal, and the display on the display unit 20a is the water temperature sensor: abnormal, the oxygen sensor: normal, the diagnosis result lists match. It will be.
On the other hand, if the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 does not match the normal / abnormal setting of each device in the simulated operation of the ECU 2, the PC 11 determines whether the diagnostic tool 20 Determine that the display of the diagnostic result list is abnormal and record it.

Next, in step S470, the PC 11 compares the diagnostic parameter information (reference parameter information) set in the simulation operation of the ECU 2 with the diagnostic parameter information displayed on the display unit 20a of the diagnostic tool 20. Note that the PC 11 detects the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 by character recognition processing on the image signal obtained by photographing the third diagnostic result screen.
If the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 matches the diagnostic parameter set in the simulation operation of the ECU 2, the PC 11 displays the diagnostic parameter of the diagnostic tool 20 normally in step S480. It is determined and recorded.

On the other hand, if the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 does not match the diagnostic parameter set in the simulation operation of the ECU 2, the PC 11 displays an abnormal diagnostic parameter display on the diagnostic tool 20 in step S490. It is determined and recorded.
As described above, the PC 11 verifies whether or not a normal diagnostic result is displayed on the diagnostic tool 20 for each item of the diagnostic result in the ECU 2 and records the determination result. Therefore, for example, when a diagnostic result in the ECU 2 is erroneously displayed due to an abnormality in the display function of the diagnostic tool 20, the PC 11 can detect this as an abnormal state, and an inspection error occurs due to an abnormality in the diagnostic tool 20. Can be suppressed.

Here, the state in which the diagnostic result of the ECU 2 displayed on the display unit 20a of the diagnostic tool 20 does not correspond to the setting of the simulated operation of the ECU 2 occurs due to an abnormality of the diagnostic tool 20, and transmission data of the diagnostic result from the ECU 2 Is also caused by an abnormality in the ECU 2.
Therefore, as an example of the determination process in step S380 in the flowchart of FIG. 9, an example of a process for distinguishing between the abnormality of the diagnostic tool 20 and the abnormality of the ECU 2 will be described with reference to the flowcharts of FIGS.

  In step S510, the PC 11 determines the number of devices such as sensors and actuators (set abnormality diagnosis number, reference abnormality diagnosis number) set to an abnormal state in the simulated operation of the ECU 2, and the abnormality displayed on the display unit 20a of the diagnostic tool 20. Compare the number of diagnoses. Note that the PC 11 detects the number of abnormality diagnoses displayed on the display unit 20a of the diagnostic tool 20 by character recognition processing for an image signal obtained by photographing the first diagnosis result screen.

If the number of abnormality diagnoses displayed on the display unit 20a of the diagnostic tool 20 matches the number of abnormality diagnoses set in the simulation operation of the ECU 2, the PC 11 determines the number of abnormality diagnoses of the diagnostic tool 20 in step S520. Determine that the display is normal and record.
Note that the display of the number of abnormality diagnoses of the diagnostic tool 20 is normal because the abnormal state of various devices is correctly diagnosed by the diagnostic processing in the ECU 2, and the diagnostic tool 20 correctly displays the diagnostic results in the ECU 2. It shows that it is in a state.

  On the other hand, if the number of abnormality diagnosis displayed on the display unit 20a of the diagnostic tool 20 does not match the number of abnormality diagnosis set in the simulation operation of the ECU 2, the PC 11 determines in step S530 that the abnormality set in the simulation operation of the ECU 2 It is determined whether or not the number of diagnoses matches the data of the number of abnormality diagnoses (communication log data) transmitted from the ECU 2 to the diagnostic tool 20. The PC 11 detects the data of the number of abnormality diagnoses transmitted from the ECU 2 to the diagnostic tool 20 based on the communication log acquired by the communication monitoring unit 13.

Here, when the number of abnormality diagnoses set in the simulated operation of the ECU 2 (the number of devices set in the abnormal state) matches the data of the number of abnormal diagnoses transmitted from the ECU 2 to the diagnostic tool 20, an abnormal state is entered in the simulated operation. The ECU 2 correctly diagnoses the abnormality of the set device, and the result is transmitted to the diagnostic tool 20 as it is.
Therefore, when the number of abnormality diagnoses set in the simulated operation of the ECU 2 matches the data of the number of abnormality diagnoses transmitted from the ECU 2 to the diagnostic tool 20, the PC 11 determines the number of abnormality diagnoses of the diagnostic tool 20 in step S540. Judge that the display is abnormal and record it.

On the other hand, when the abnormality diagnosis number set in the simulated operation of the ECU 2 and the abnormality diagnosis number data transmitted from the ECU 2 to the diagnostic tool 20 do not match, the transmission data of the abnormality diagnosis number from the ECU 2 is incorrect. The number of abnormality diagnoses displayed on the display unit 20a of the diagnostic tool 20 and the number of abnormality diagnoses set in the simulation operation of the ECU 2 do not match.
Therefore, if the abnormality diagnosis number set in the simulation operation of the ECU 2 does not match the abnormality diagnosis data transmitted from the ECU 2 to the diagnostic tool 20, the PC 11 transmits the abnormality diagnosis number from the ECU 2 in step S550. Data abnormality is determined and recorded, and data of the number of abnormality diagnoses transmitted from the ECU 2 to the diagnostic tool 20, that is, data of the number of abnormality diagnoses different from the expected value is recorded.

Next, in step S560, the PC 11 compares the normal / abnormal setting (reference diagnosis result list) of each device in the simulated operation of the ECU 2 with the diagnosis result list displayed on the display unit 20a of the diagnostic tool 20. . The PC 11 detects a list of diagnostic results displayed on the display unit 20a of the diagnostic tool 20 by character recognition processing for an image signal obtained by photographing the second diagnostic result screen.
If the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 matches the normal / abnormal setting of each device in the simulated operation of the ECU 2, the PC 11 determines whether the diagnostic tool 20 Determine that the display of the diagnosis result list is normal and record it.

  On the other hand, if the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 does not match the normal / abnormal setting of each device in the simulated operation of the ECU 2, the PC 11 performs the diagnosis of the diagnostic tool 20 in step S580. Determine that the display of the result list is abnormal and record it. The processing in steps S560 to S580 is the same as the processing in steps S440 to S460 in the flowchart of FIG.

If the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 and the normal / abnormal setting of each device in the simulated operation of the ECU 2 do not match, the PC 11 transmits the diagnosis transmitted from the ECU 2 to the diagnostic tool 20. Information on the result list can be acquired from the communication log, and information on the diagnosis result list in the communication log can be compared with the normal / abnormal setting of each device in the simulated operation of the ECU 2.
The PC 11 determines the abnormality of the diagnostic tool 20 if the information of the diagnosis result list in the communication log matches the normal / abnormal setting of each device in the simulation operation of the ECU 2, and the diagnosis result list information in the communication log If the normal / abnormal setting of each device in the simulated operation of the ECU 2 does not match, the abnormality of the ECU 2 can be determined.

Next, in step S590, the PC 11 compares the diagnostic parameter information (reference diagnostic parameters, types of diagnostic parameters) set in the simulation operation of the ECU 2 with the diagnostic parameters displayed on the display unit 20a of the diagnostic tool 20. .
In the collation in step S590, for example, when the processing operation of the ECU 2 is set so as to calculate the maximum value of the engine rotation speed as the diagnosis parameter, the engine rotation speed is set as the diagnosis parameter on the display unit 20a of the diagnosis tool 20. It is determined whether or not the maximum value information is displayed.
Note that the PC 11 detects the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 by character recognition processing on the image signal obtained by photographing the third diagnostic result screen.

If the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 matches the information on the diagnostic parameter set in the simulation operation, the PC 11 is displayed on the display unit 20a of the diagnostic tool 20 in step S600. It is determined whether the diagnostic parameter value matches the expected value (target value) of the diagnostic parameter read from the database DB.
For example, in the case of setting to calculate the maximum value of the engine rotation speed as the diagnosis parameter, the PC 11 detects that the maximum value of the engine rotation speed is displayed as the diagnosis parameter on the display unit 20a of the diagnosis tool 20 in step S590. In step S600, it is determined whether or not the maximum value of the engine speed displayed on the display unit 20a of the diagnostic tool 20 matches the set value in the simulated operation of the ECU 2.

If the value of the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 matches the expected value, the PC 11 displays that the diagnostic parameter of the diagnostic tool 20 is normal and the ECU 2 calculates in step S610. It is determined that the diagnostic parameter value is normal and recorded.
On the other hand, when the value of the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 does not match the expected value, the PC 11 displays that the diagnostic parameter display of the diagnostic tool 20 is normal and the ECU 2 in step S620. The fact that the calculation result of the diagnostic parameter is abnormal is recorded, and further, the value of the diagnostic parameter that does not coincide with the expected value (target value) calculated by the ECU 2 and read from the database DB is recorded.

If the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 and the diagnostic parameter (set diagnostic parameter) set as the calculation target in the simulated operation of the ECU 2 do not match, the PC 11 determines that the ECU 2 in step S630. The diagnostic parameter set in the simulated operation is compared with the diagnostic parameter information (diagnostic parameter information in the communication log) transmitted from the ECU 2 to the diagnostic tool 20.
Here, when the diagnostic parameter set in the simulation operation of the ECU 2 matches the diagnostic parameter information in the communication log, the diagnostic parameter information is correctly output from the ECU 2, but the display content of the diagnostic tool 20 is incorrect. Will be.

  Therefore, if the diagnostic parameter set in the simulated operation of the ECU 2 matches the diagnostic parameter information in the communication log, the PC 11 confirms that the transmission of the diagnostic parameter of the ECU 2 is normal and the diagnostic tool in step S640. 20, the fact that there is an abnormality in the display of the diagnostic parameter in 20 is recorded, and information of the diagnostic parameter that is erroneously displayed in the diagnostic tool 20 is recorded.

On the other hand, if the diagnostic parameter set in the simulation operation of the ECU 2 does not match the diagnostic parameter information in the communication log, the PC 11 determines that the transmission of the diagnostic parameter of the ECU 2 is abnormal and the diagnostic tool in step S650. 20, the fact that there is an abnormality in the display of the diagnostic parameter in 20 is recorded, and information of the diagnostic parameter that is erroneously displayed in the diagnostic tool 20 is recorded.
As described above, when the display contents in the diagnostic tool 20 and the transmission data from the ECU 2 are determined for the three items of abnormality diagnosis count, diagnosis result list, and diagnosis parameter, the PC 11 performs abnormality diagnosis in step S660. It is determined whether a normal state has been detected for all items of the number, the list of diagnosis results, and the diagnosis parameters.

If the normal state is detected for all items of the number of abnormality diagnosis, the list of diagnosis results, and the diagnosis parameters, the PC 11 simulates all the contents of the diagnosis results displayed on the display unit 20a of the diagnosis tool 20 in step S670. It is recorded that there is no information (display content, communication data) that matches the operation settings but does not match the simulated operation settings.
When the normal state is detected for all of the abnormality diagnosis numbers, the diagnosis result list, and the diagnostic parameters, the PC 11 further determines that the normal operation state of the diagnostic tool 20 and the ECU 2 is confirmed in step S680 (the diagnostic tool 20 and the ECU 2). Record that a normal state was detected).

On the other hand, when the display content of the diagnostic tool 20 or an abnormality in the transmission data from the ECU 2 is detected in at least one of the number of abnormality diagnosis, the diagnosis result list, and the diagnosis parameter, the PC 11 proceeds from step S660 to step S690, Record the display contents and communication data different from the simulated operation settings.
Further, in step S700, the PC 11 detects an abnormality in the display content of the diagnostic tool 20 for at least one of the number of abnormality diagnosis, the diagnosis result list, and the diagnosis parameter, while detecting an abnormality in the transmission data from the ECU 2. It is determined whether or not the case is not detected.
If there is no abnormality in the transmission data of the diagnostic result from the ECU 2 and there is an abnormality in the display contents of the diagnostic tool 20, the PC 11 determines the abnormal state of the diagnostic tool 20 (failure of the diagnostic tool 20) in step S710. Record).

On the other hand, if there is an abnormality in the transmission data of the diagnosis result from the ECU 2, the PC 11 has no abnormality in the display content of the diagnostic tool 20 and there is an abnormality in the transmission data of the diagnosis result from the ECU 2 in step S720. It is determined whether it corresponds to.
If there is no abnormality in the display contents of the diagnostic tool 20 and there is an abnormality in the transmission data from the ECU 2, the PC 11 records the determination of the abnormal state of the ECU 2 (detection of failure of the ECU 2) in step S730.

On the other hand, when there is an abnormality in the transmission data of the diagnosis result from the ECU 2 and there is also an abnormality in the display contents of the diagnostic tool 20, the PC 11 confirms the abnormal state of the diagnostic tool 20 and the ECU 2 (step S740). The failure detection of the ECU 2 and the diagnostic tool 20) is recorded.
11 and 12, the display contents abnormality of the diagnostic tool 20 can be distinguished from those caused by the abnormality of the diagnostic tool 20 and those caused by the abnormality of the ECU 2. It is possible to suppress erroneous diagnosis of the ECU 2 based on an abnormality in display content due to the abnormality.

By the way, the ECU 2 may become unresponsive to the command transmission from the diagnostic tool 20 depending on the driving conditions, and an example of processing that can diagnose the malfunction of the ECU 2 will be described with reference to the flowchart of FIG.
In step S810, the PC 11 reads out the engine operating condition (first operating condition) for simulating the ECU 2 from the database DB, gives it to the model simulator 12 (12a, 12b), and starts the simulated operation (simulation) of the ECM2. .

Next, in step S820, the PC 11 reads information from the database DB that is to be diagnosed by the diagnosis process in the ECU 2 and sets the information in the model simulator 12, whereby the HILS system 10 outputs an electrical signal to the ECU 2. (Simulated sensor signal) is set to a pattern that simulates the normal state (first normal state). As a result, the ECU 2 performs a simulation operation in the first normal mode.
Then, in step S830, the ECU 2 calculates a predetermined diagnostic parameter and performs a process of diagnosing the presence / absence of abnormality of the predetermined device based on the diagnostic parameter.

Next, in step S840, the PC 11 reads the operation content (reference operation information) for displaying a list of diagnosis results (second diagnosis result screen) by the ECU 2 on the display unit 20a of the diagnostic tool 20 from the database DB and reads the operation contents. By controlling the robot arm 40 based on the operation information, the robot arm 40 is caused to perform a button operation for displaying a list of diagnosis results on the display unit 20a of the diagnostic tool 20.
Then, the diagnostic tool 20 transmits a command for requesting notification of information on the diagnosis result list to the ECU 2 in response to a button operation by the robot arm 40, and acquires information on the diagnosis result list as response information from the ECU 2. Based on the information, the display content of the display unit 20a is switched to the display of the diagnosis result list.

When the display content of the display unit 20a of the diagnostic tool 20 is switched, the PC 11 captures an image of the display unit 20a captured by the camera 30, that is, an image signal obtained by capturing a list of diagnostic results (second diagnostic result screen). save.
Further, in step S850, the PC 11 reads the operation content for switching the display content of the display unit 20a of the diagnostic tool 20 to the display of the diagnostic parameter (third diagnosis result screen) in the diagnostic processing of the ECU 2 from the database DB and reads the operation content. The robot arm 40 is controlled according to the operation content.

Then, the diagnostic tool 20 transmits a command requesting notification of a diagnostic parameter to the ECU 2 in response to a button operation by the robot arm 40, acquires diagnostic parameter information as response information from the ECU 2, and based on the acquired information The display content of the display unit 20a is switched to display of diagnostic parameters.
When the display content of the display unit 20a of the diagnostic tool 20 is switched to display of diagnostic parameters, the PC 11 captures an image of the display unit 20a captured by the camera 30, that is, a diagnostic parameter display screen (third diagnostic result screen). Save the image signal.

Next, in step S860, the PC 11 reads out from the database DB a second operating condition that is different from the operating condition (first operating condition) set in step S810 as the engine operating condition for causing the ECU 2 to perform a simulated operation. Furthermore, the electrical signal (simulated sensor signal) output from the HILS system 10 to the ECU 2 is set to a normal pattern (second normal pattern) under the second operating condition.
In step S870, similarly to step S840, the PC 11 performs an automatic operation for displaying a list of diagnosis results on the display unit 20a of the diagnostic tool 20, and displays the diagnosis result list screen displayed on the display unit 20a. Record the captured image signal.

Next, in step S880, the PC 11 performs an automatic operation for displaying the diagnostic parameters on the display unit 20a of the diagnostic tool 20, and photographs the diagnostic parameter information screen displayed on the display unit 20a, as in step S850. Record the image signal.
The PC 11 collates the display contents of the diagnostic tool 20 in step S890, and then stores the collation result in the database DB in step S900.

The flowcharts of FIGS. 14 and 15 show an example of the display content collation process of the diagnostic tool 20 in step S890.
In step S1010, the PC 11 indicates that the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 when the first operating condition (first time) is in a normal state in the simulated operation of the ECU 2 under the first operating condition. It is determined whether it matches the device set to.

If the list of diagnostic results displayed on the display unit 20a of the diagnostic tool 20 when the first operating condition is satisfied matches the simulation operation setting (reference display content), the PC 11 performs the first operation in step S1020. It is determined that the display of the diagnostic result list of the diagnostic tool 20 under conditions is normal, and the determination result is recorded.
On the other hand, if the list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 when the first operating condition is satisfied does not match the setting of the simulated operation, the PC 11 determines in step S1030 the diagnostic tool under the first operating condition. It is determined that the display of the list of 20 diagnostic results is abnormal, and the determination result is recorded.

Further, in step S1040, the PC 11 determines that the diagnostic parameter information displayed on the display unit 20a of the diagnostic tool 20 when the first operating condition is set is the diagnostic parameter set in the simulation operation of the ECU 2 under the first operating condition. It is determined whether or not the information matches.
If the diagnostic parameter information displayed on the display unit 20a of the diagnostic tool 20 matches the simulated operation setting (reference display content) when the first operating condition is satisfied, the PC 11 performs the first operation in step S1050. It is determined and recorded that the display of diagnostic parameters of the diagnostic tool 20 is normal under conditions.

On the other hand, if the information on the diagnostic parameter displayed on the display unit 20a of the diagnostic tool 20 does not match the setting of the simulated operation when the first operating condition is satisfied, the PC 11 determines in step S1060 that the diagnostic tool 20 satisfies the first operating condition. It is determined that the display of the diagnostic parameter is abnormal and recorded.
Further, in step S1070, the PC 11 is a list of diagnosis results displayed on the display unit 20a of the diagnostic tool 20 when the first operation condition (first time) is satisfied, and the second operation condition (second time). Sometimes, the diagnosis result list displayed on the display unit 20a of the diagnostic tool 20 is collated.

A diagnosis result list displayed on the display unit 20a of the diagnostic tool 20 when the first operating condition is satisfied, and a diagnosis result list displayed on the display unit 20a of the diagnostic tool 20 when the second operating condition is satisfied. If they match, in step S1080, the PC 11 determines and records a normal state in which the display of the list of diagnosis results under two different operating conditions matches.
On the other hand, a list of diagnostic results displayed on the display unit 20a of the diagnostic tool 20 when the first operating condition is satisfied, and a list of diagnostic results displayed on the display unit 20a of the diagnostic tool 20 when the second operating condition is satisfied. If they do not match, the PC 11 determines and records an abnormal state in which the display of the diagnostic result list under two different operating conditions does not match in step S1090.

In step S1100, the PC 11 displays the diagnostic parameters in the diagnostic tool 20 under the first operating condition (first time) and the diagnostic parameters in the diagnostic tool 20 under the second operating condition (second time). And match.
If the display of the diagnostic parameter in the diagnostic tool 20 under the first operating condition matches the display of the diagnostic parameter in the diagnostic tool 20 under the second operating condition, the PC 11 determines in step S1110 that two different operating conditions. The normal state in which the display of the diagnostic parameter matches in is determined and recorded.

On the other hand, if the display of the diagnostic parameter in the diagnostic tool 20 under the first operating condition does not match the display of the diagnostic parameter in the diagnostic tool 20 under the second operating condition, the PC 11 determines in step S1120 that two different operating conditions. An abnormal state in which the display of the diagnostic parameter in the display does not match is determined and recorded.
In step S1130, the PC 11 determines whether the normal state is determined in all of the matching processes in steps S1010 to S1120, and whether the abnormal state is determined for all items.

When the normal state is determined in all of the collation processes in steps S1010 to S1120, the PC 11 records that the normality is determined in all of the collation processes in step S1140.
On the other hand, when an abnormal state is determined in at least one of the collation processes in steps S1010 to S1120, the PC 11 transmits a diagnostic result list and diagnostic parameter information from the ECU 2 to the diagnostic tool 20 in step S1150. The contents of the current communication log are collated with the reference diagnosis result list and reference diagnosis parameter information read from the database DB.

  Then, the diagnostic parameter list information (communication log) transmitted from the ECU 2 to the diagnostic tool 20 matches the reference diagnostic result list information read from the database DB, and the diagnostic parameter transmitted from the ECU 2 to the diagnostic tool 20 If the information (communication log) and the reference diagnostic parameter information read from the database DB match, the ECU 2 sends the diagnostic result list and correct information about the diagnostic parameters to the diagnostic tool 20, but the diagnostic tool 20 Thus, incorrect information different from the correct information transmitted by the ECU 2 is displayed.

Therefore, if the transmission data of the diagnosis result list acquired from the communication log matches the reference diagnosis result list, and the transmission data of the diagnosis parameter acquired from the communication log matches the reference diagnosis parameter, the PC 11 in step S1160. The abnormality of the diagnostic tool 20 is determined and recorded.
On the other hand, when the transmission data of the diagnosis result list acquired from the communication log does not match the reference diagnosis result list and / or when the transmission data of the diagnosis parameter acquired from the communication log does not match the reference diagnosis parameter, that is, the ECU 2 When sending erroneous information to at least one of the diagnostic result list information and the diagnostic parameter information to the diagnostic tool 20, the PC 11 determines and records an abnormality in the ECU 2 in step S1170.

As described above, the ECU 2 is operated so as to simulate two different driving conditions, and it is determined whether or not the diagnosis result list and the diagnostic parameters under the respective driving conditions are correctly displayed on the diagnostic tool 20. When the ECU 2 becomes unresponsive depending on conditions, it is possible to detect the occurrence of malfunction of the ECU 2.
Further, as a pattern of malfunction of the ECU 2, the ECU 2 may transmit information different from the result of the diagnostic process to the diagnostic tool 20, and an example of a process that can diagnose such malfunction of the ECU 2 is shown in FIG. It demonstrates according to a flowchart.

In step S1210, the PC 11 reads out the engine operating conditions for simulating the ECU 2 from the database DB, gives them to the model simulator 12 (12a, 12b), and starts the simulating operation (simulation) of the ECM2.
Next, in step S1220, the PC 11 reads information from the database DB that is to be diagnosed by the diagnosis process in the ECU 2 and sets the information in the model simulator 12, so that the HILS system 10 outputs an electrical signal to the ECU 2. (Simulated sensor signal) is set to a pattern that simulates a normal state. As a result, the ECU 2 performs a simulation operation in the normal mode.

In step S1230, the ECU 2 performs a process of calculating a predetermined diagnosis parameter and diagnosing the presence / absence of an abnormality based on the diagnosis parameter, and performing a simulated operation in the normal mode to set normal states for various devices. Come to detect.
In step S1240, the PC 11 outputs a command for requesting transmission of diagnostic support information to the ECU 2, and displays the operation contents of the diagnostic tool 20 for displaying the diagnostic support information transmitted from the ECU 2 on the display unit 20a. The robot arm 40 is controlled in accordance with the operation content.

Further, in step S1240, the PC 11 causes the camera 30 to capture the diagnostic support information displayed on the display unit 20a of the diagnostic tool 20, and records an image signal obtained by capturing the diagnostic support information display screen by the camera 30.
The diagnosis support information is information on the presence / absence of a diagnosis target component in the engine controlled by the ECU 2, for example, the presence / absence of an oxygen sensor (air-fuel ratio sensor) for detecting the oxygen concentration in exhaust gas, the oxygen This is information such as the presence or absence of a heater in the sensor.

In step S1250, the PC 11 reads button operations for displaying a list of diagnosis results by the ECU 2 on the display unit 20a of the diagnostic tool 20 from the database DB, and controls the robot arm 40 based on the read operation information. Then, the robot arm 40 is caused to execute a button operation for displaying the diagnosis result list on the display unit 20a.
Then, the diagnostic tool 20 transmits a command requesting the ECU 2 to notify the diagnosis result list in response to a button operation by the robot arm 40, acquires information on the diagnosis result list as response information from the ECU 2, and acquires the acquired information. Based on the above, the display content of the display unit 20a is switched to the display of the diagnosis result list of the ECU 2.

Here, when the display content on the display unit 20a of the diagnostic tool 20 is switched to the diagnostic result list, the PC 11 causes the camera 30 to capture the screen of the diagnostic result list and records the image signal captured by the camera 30.
Then, in step S1260, the PC 11 performs collation processing of the display content of the display unit 20a of the diagnostic tool 20, and records the collation result in the next step S1270.

An example of the collation process in step S1260 will be described with reference to the flowchart of FIG.
In step S1310, the PC 11 analyzes the image signal obtained by capturing the screen of the diagnosis result list displayed on the display unit 20a to obtain the display content of the diagnostic support information. The display content and the electric signal in the simulation operation of the ECU 2 are obtained. Compare the setting information.

If the diagnostic support information displayed on the display unit 20a of the diagnostic tool 20 matches the setting of the simulation operation of the ECU 2, the PC 11 stores the diagnostic support information on the display unit 20a of the diagnostic tool 20 in step S1320. Judge that it was displayed normally and record it.
On the other hand, if the diagnostic support information displayed on the display unit 20a of the diagnostic tool 20 does not match the setting of the simulated operation of the ECU 2, the PC 11 displays the diagnostic support information on the display unit 20a of the diagnostic tool 20 in step S1330. Judge that it is abnormal and record it.

  For example, a device to be diagnosed whose normal state is simulated in the simulated operation of the ECU 2 (a sensor in which the output of the simulated sensor signal to the ECU 2 is set) is not mounted on the engine in the diagnostic support information displayed on the diagnostic tool 20 If it is determined, the PC 11 proceeds to step S1330 and determines that the display of the diagnostic support information on the diagnostic tool 20 is abnormal.

Further, in step S1340, the PC 11 sets the electric signal setting information (abnormal / normal setting information) in the simulated operation of the ECU 2 and the display contents of the diagnosis result list obtained by analyzing the image signal obtained by photographing the display unit 20a. Is matched.
If the display content of the diagnostic result list obtained by analyzing the image signal obtained by photographing the display unit 20a matches the set state of the electrical signal in the simulation operation of the ECU 2, the PC 11 displays the diagnostic tool 20 in step S1350. It is determined and recorded that information of the diagnosis result list is normally displayed on the unit 20a.

On the other hand, if the display content of the diagnostic result list obtained by analyzing the image signal obtained by photographing the display unit 20a does not match the setting state of the electrical signal in the simulation operation of the ECU 2, the PC 11 displays the diagnostic tool 20 in step S1360. It is determined and recorded that the information of the diagnosis result list in the unit 20a is abnormal.
For example, when a failure occurs in which the ECU 2 does not output information on a device that has been determined to be normal according to the setting of the simulated operation, the PC 11 has abnormal information in the diagnostic result list on the display unit 20a of the diagnostic tool 20 in step S1360. It will be determined.

As described above, the PC 11 collates the display content on the display unit 20a of the diagnostic tool 20 with the reference display content according to the setting of the simulated operation of the ECU 2, thereby causing an abnormality in the diagnostic tool 20 and / or the ECU 2. Can diagnose the condition.
The PC 11 controls the robot arm 40 to display the fault code information, the process information supported by the diagnostic tool 20, the vehicle identification information, and the like on the display unit 20 a of the diagnostic tool 20. The operation unit 20b is automatically operated, and the content displayed on the display unit 20a of the diagnostic tool 20 by such operation is captured by the camera 30, and the display content detected by analyzing the captured image and the setting of the simulation operation of the ECU 2 are set. The presence or absence of abnormality of the diagnostic tool 20 and the ECU 2 can be diagnosed by comparing the display contents of the corresponding reference.

According to the above inspection system, the operation unit 20b of the diagnostic tool 20 is automatically operated in a predetermined order, and the camera 30 determines whether or not the actual operation content of the operation unit 20b matches the target operation content. Since the verification is performed based on the imaging result, the inspection procedure error due to an operation error can be suppressed.
Further, a communication log between the diagnostic tool 20 and the ECU 2 is acquired, the display content on the display unit 20a of the diagnostic tool 20 and the content of the communication log are collated, and the operation content of the operation unit 20b and the communication log Since the presence or absence of abnormality of the diagnostic tool 20 is verified by collating the contents, it is possible to suppress a decrease in the inspection accuracy of the ECU 2 due to the abnormality of the diagnostic tool 20.

Further, by comparing the setting of the simulated operation of the ECU 2 with the display content of the diagnostic tool 20, and by comparing the setting of the simulated operation of the ECU 2 with the content of the communication log, the abnormality of the diagnostic tool 20 and the abnormality of the ECU 2 are detected. Can be distinguished.
Further, by switching the operation conditions for simulating the ECU 2 to a plurality of types, it is possible to verify whether or not an operation failure of the ECU 2 occurs due to a difference in the operation conditions.
When the ECU 2 is inspected using the above-described inspection system, inspection mistakes can be reduced and the inspection can be stably performed in a short time compared to the case where the operator manually operates the diagnostic tool 20.

Although the contents of the present invention have been specifically described above with reference to the preferred embodiments, it is obvious that those skilled in the art can take various modifications based on the basic technical idea and teachings of the present invention. is there.
The electronic control unit for automobiles to be inspected by the inspection system according to the present invention is not limited to the ECU 2 for controlling the engine. For example, the electronic control unit for controlling the automatic transmission for automobiles and the electronic for controlling the air conditioner for automobiles. It can be applied to various on-vehicle electronic control units such as control units.

Further, when an inspection is performed on one of a plurality of electronic control units configured to be able to communicate with each other via a CAN in a vehicle-mounted state, another electronic control unit outputs as an electric signal to be given to the electronic control unit to be inspected. A signal can be included.
Moreover, when abnormality of ECU2 and / or the diagnostic tool 20 is detected, it can be set as the structure which displays a warning on the screen of PC11, or lights the lamp | ramp which notifies an operator of abnormality detection.

  DESCRIPTION OF SYMBOLS 1 ... Inspection system, 2 ... Electronic control unit (ECU), 10 ... HILS system, 11 ... Personal computer (PC) for HILS, 13 ... Communication monitoring part, 20 ... Diagnostic tool, 20a ... Display part, 20b ... Operation part, 30 ... Camera (photographing device), 40 ... Robot arm (mechanical device)

Claims (5)

A diagnostic tool that includes a display unit and an operation unit, and communicates with an electronic control unit for an automobile to be inspected;
A mechanical device for operating the operation part of the diagnostic tool;
Means for storing the standard operation content of the operation unit and the standard display content of the display unit;
Means for controlling the mechanical device based on the reference operation content;
An imaging device for imaging the display unit of the diagnostic tool;
Means for collating the reference display content with the display content obtained from the image of the display unit photographed by the photographing device;
An inspection system for an electronic control unit for automobiles The photographing apparatus photographs the display unit and the operation unit of the diagnostic tool,
The inspection system for an automobile electronic control unit according to claim 1, further comprising means for collating the reference operation content with the operation content obtained from the image of the operation unit photographed by the photographing apparatus. Means for storing reference communication information between the diagnostic tool and the automotive electronic control unit;
Means for acquiring a communication log between the diagnostic tool and the automotive electronic control unit;
Means for collating the communication log with the reference communication information;
The inspection system for an electronic control unit for automobiles according to claim 1 or 2, further comprising:   The inspection system for an electronic control unit for an automobile according to any one of claims 1 to 3, further comprising means for storing data indicating a result of the collation and an image photographed by the photographing apparatus. The vehicle electronic control unit is an engine control unit that controls an engine mounted on the vehicle,
The inspection system for an automobile electronic control unit according to any one of claims 1 to 4, comprising a HILS system in which an engine model is mounted.