JP5500057B2 - Inspection system - Google Patents

Description

  The present invention relates to an inspection system for inspecting the operation of an inspection object.

  Conventionally, when inspecting the operation of an electronic device that controls the behavior of an actuator, etc., instead of performing the inspection by mounting the electronic device on a real machine, a pseudo inspection signal is output from an inspection device such as a simulator, and the inspection is performed. It is known to output operation information of an electronic device that operates in response to a signal from an inspection device. In order to appropriately inspect the inspection object by the inspection device, it is necessary to diagnose whether the inspection device is normal or abnormal.

  For example, in Patent Document 1, when diagnosing an inspection apparatus, a signal generation unit of the inspection apparatus that outputs an inspection signal to the inspection target and a signal measurement unit of the inspection apparatus that measures a signal from the inspection target are connected by a harness or the like. Then, the inspection signal output from the signal generating means is measured by the signal measuring means, and whether the inspection apparatus is normal or abnormal is diagnosed from the measurement result.

Japanese Patent Laid-Open No. 10-153628

  However, in Patent Document 1, since the inspection apparatus is diagnosed with a configuration different from the electrical connection state when the inspection object and the inspection apparatus are electrically connected to inspect the operation of the inspection object, the inspection apparatus is normal. It is difficult to accurately diagnose whether there is an abnormality or not.

  Furthermore, in order to diagnose the inspection apparatus, connection means such as a harness for electrically connecting the signal generation means and the signal measurement means of the inspection apparatus is required. This connection means is unnecessary when the inspection apparatus inspects the operation of the inspection object.

  The present invention has been made to solve the above-described problem, and provides an inspection system for diagnosing an inspection apparatus for inspecting an inspection object with high accuracy without changing the electrical connection state of the inspection system. With the goal.

  According to the first to fifth aspects of the present invention, in the inspection system for inspecting the operation of the inspection object, the inspection device outputs an inspection signal for inspecting the operation of the inspection object and operates according to the inspection signal. At least a part of the operation information of the inspection object is output, and the inspection object operation device outputs a diagnostic code generated by the self-diagnosis function of the inspection object when the inspection object operates according to the inspection signal output by the inspection apparatus Obtain from the inspection target. The inspection control device operates in response to the inspection signal when commanding the inspection device to output an inspection signal corresponding to each of the inspection of the inspection object and the diagnosis of the inspection device, and at the time of diagnosis of the inspection device. It has a diagnostic means for diagnosing whether the inspection apparatus is normal or abnormal based on a diagnostic code acquired from the inspection object by the inspection object operation apparatus.

  As described above, in both the inspection of the inspection object and the diagnosis of the inspection apparatus, the inspection apparatus outputs an inspection signal according to a command from the command means of the inspection control device, and the inspection object operates according to the inspection signal, Since the inspection target operation device acquires the diagnostic code from the inspection target, it is not necessary to change the electrical connection state of the inspection system between the inspection of the inspection target and the diagnosis of the inspection device.

  Therefore, it is possible to accurately diagnose whether the inspection apparatus is normal or abnormal based on the diagnostic code generated by the inspection object in the same electrical connection state of the inspection system as at the time of inspection of the inspection object when diagnosing the inspection apparatus. .

  For example, when diagnosing the inspection device, the inspection device outputs a diagnosis code generated by the inspection object according to the inspection signal actually output by the inspection device, and a command from the command means if the inspection device is normal. If the diagnostic code that is estimated to be generated by the inspection signal in accordance with the inspection signal to be matched matches, the inspection apparatus is diagnosed as being normal, and if not matched, the inspection apparatus is diagnosed as abnormal.

  Furthermore, since the electrical connection state of the inspection system does not change between the inspection of the inspection object and the diagnosis of the inspection apparatus, unnecessary equipment and devices are prepared at the time of inspection of the inspection object to diagnose the inspection apparatus. There is no need.

According to the second aspect of the present invention, before the diagnosis unit diagnoses the inspection device, the command unit instructs the inspection target operation device to reset the inspection target.
In this way, by resetting the inspection target and initializing the operating state before diagnosing the inspection device, the diagnostic code generated by the self-diagnostic function of the inspection target is reset. The inspection apparatus can be appropriately diagnosed on the basis of the diagnostic code generated by the inspection object.

  In addition, when diagnosing an inspection device, the inspection device that is the diagnosis target does not reset the inspection target, so that regardless of whether the inspection device is normal or abnormal, the inspection target operation device resets the inspection target normally. it can.

  By the way, normally, when the inspection object is reset, the self-diagnosis function of the inspection object diagnoses whether the inspection object is normal or abnormal in the reset initial state. Based on the diagnostic code acquired from the object, it is possible to determine whether the inspection object is normal or abnormal. If the inspection object is abnormal, the inspection apparatus cannot be properly diagnosed based on the diagnostic code generated by the inspection object when diagnosing the inspection apparatus.

  Therefore, according to the third aspect of the invention, the command means stops the diagnosis for the inspection apparatus when the diagnosis code acquired from the inspection object is an abnormal code when the inspection object operation device resets the inspection object.

Accordingly, it is possible to prevent the inspection apparatus from being diagnosed based on the diagnostic code generated by the abnormal inspection target.
According to the invention described in claim 4, the command means switches between the inspection for the inspection object and the diagnosis for the inspection apparatus at a set time interval.

Thereby, the inspection for the inspection object and the diagnosis for the inspection apparatus can be automatically switched and executed.
According to the fifth aspect of the present invention, the inspection target operating device acquires an identifier for identifying the inspection target from the inspection target, and the command means outputs an inspection signal corresponding to the identifier acquired by the inspection target operating device. To output.

Thereby, even if the inspection object is changed, the inspection apparatus can be instructed to output an inspection signal corresponding to the identifier of the inspection object acquired by the inspection object operation device.
In addition, since the inspection object identifier is not acquired using the inspection apparatus that is the diagnosis object, the inspection object operation apparatus is not changed even if the inspection object is changed regardless of whether the inspection apparatus is normal or abnormal. The inspection object can be identified based on the acquired identifier of the inspection object.

The block diagram which shows the test | inspection system of 1st Embodiment. The flowchart which shows the diagnostic process with respect to a test | inspection apparatus. (A) is a block diagram showing the switching between the inspection for the inspection object and the diagnosis for the inspection apparatus, and (B) is a schematic diagram showing the time lapse of the switching. The schematic diagram which shows the process in the case of changing a test object. The block diagram which shows the inspection system of 2nd Embodiment. The block diagram which shows the inspection system of 3rd Embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[First Embodiment]
FIG. 1 shows an inspection system 2 according to the first embodiment.

(Inspection system 2)
The inspection system 2 includes an operation PC (personal computer) 10, a simulator 20, a diagnostic tester 30, an electronic control unit (ECU) 40, and a measuring instrument 50. The inspection system 2, for example, inspects the operation of an electronic device such as an ECU mounted on a vehicle, or an actuator integrated with the ECU or the ECU and a sensor and configured as an assembly, and evaluates the operation of the electronic device. It is. In FIG. 1, ECU40 is illustrated as a test object.

  The operation PC 10 switches between an inspection program 12 for inspecting the operation of the ECU 40 and a diagnosis program 14 for diagnosing the simulator 20 as an inspection device for inspecting the ECU 40. In FIG. 1, a diagnostic program 14 indicated by a solid line is used instead of the inspection program 12 indicated by a dotted line.

  The operation PC 10 operates the diagnostic tester 30 by the diagnostic tester operation unit 16 and operates the simulator 20 by the simulator operation unit 18. The diagnostic tester operation unit 16 and the simulator operation unit 18 realize respective functions by hardware and software, and the functions are controlled by the inspection program 12 and the diagnostic program 14.

  Further, the operation PC 10 stores setting data such as a vehicle model executed by the simulator 20 and an inspection test scenario for the electronic device to be inspected.

  The operation PC 10 causes the simulator 20 to output inspection signals corresponding to the ECU 40 and the diagnosis of the simulator 20, respectively. At the time of inspection of the ECU 40, the operation PC 10 acquires the operation information of the ECU 40 that operates according to the inspection signal output from the simulator 20 from the simulator 20, and acquires the diagnosis code self-diagnosed by the ECU 40 from the diagnosis tester 30, The operation of the ECU 40 is evaluated based on the operation information of the ECU 40 and the diagnosis code.

  In addition to the simulator 20, the operation information of the ECU 40 to be inspected may be acquired by the operation PC 10 from a measuring instrument 50 such as an oscilloscope or a communication measuring device.

  Further, the operation PC 10 obtains a diagnostic code self-diagnosed by the ECU 40 that operates in accordance with an inspection signal output from the simulator 20 when diagnosing the simulator 20, and the simulator 20 is normal or abnormal based on the diagnostic code. Diagnose.

  As the simulator 20, for example, HILS (Hardware In The Loop Simulation) is used. The simulator 20 simulates a vehicle model other than the electronic device to be inspected by setting software. The simulator 20 includes a body system simulator, a power train system simulator, a chassis system simulator, a power electronics system simulator, a heat system simulator, and an ITS (Intelligent Transportation System) system simulator which are electrically connected to each other through a harness.

  The body system simulator simulates the behavior of doors, power windows, lights, etc. The powertrain system simulator simulates the behavior of injectors, transmissions, etc. The chassis system simulator simulates the behavior of brakes, handles, etc. To do. The power electronics simulator simulates the behavior of a motor or the like, the thermal simulator simulates the behavior of a heat source such as an air conditioner, and the ITS simulator simulates the behavior of a navigation device or the like.

  When a vehicle model to be simulated by the simulator 20 is set from the operation PC 10, a plant model, an ECU model, a sensor model, and an actuator are used as models of each part of the vehicle other than the ECU 40 to be inspected according to the set vehicle model. A model, a driving environment model of the vehicle, and the like are set. As each of these models, a necessary model is set according to the ECU to be inspected and the range of inspection contents.

  The plant model simulates the operation of the engine, the door, the transmission, and the like, and the ECU model simulates the operation of the ECU mounted on the vehicle other than the ECU 40 to be inspected.

  The sensor model simulates the operation of various sensors such as a crank angle sensor and an intake air amount sensor mounted on the vehicle, and the actuator model simulates the operation of an actuator such as a hydraulic pump and a throttle valve. The driving environment model simulates the driving environment around the vehicle, such as road surface conditions due to rain and snow, road gradient and curvature radius, and temperature.

  FIG. 1 shows only the sensor signal generator 22 of these models. The sensor signal generation unit 22 outputs a detection signal of a sensor to be simulated according to the vehicle model set in the simulator 20 (route A in FIG. 1). Further, the simulator 20 may simulate a vehicle model by inputting a control signal from the ECU 40. The simulator 20 and the ECU 40 are electrically connected by an analog signal, a digital signal, a PWM (Pulse Width Modulation) signal, and a network harness such as CAN.

  The simulator 20 uses, for example, time series, a predetermined crank angle synchronization, a predetermined rotation speed of a motor or a generator, a predetermined frequency, and the like, as the operation data representing the operation information of the ECU 40 that operates according to the inspection signal output from the simulator 20. Output in rotation synchronization. As described above, the operation PC 10 evaluates the operation of the ECU 40 by comparing the actual operation of the ECU 40 with the estimated operation based on the operation data of the ECU 40 output from the simulator 20.

  The diagnostic setting unit 32 of the diagnostic tester 30 resets and initializes the ECU 40 in response to a command from the operation PC 10 to reset the diagnostic code generated by the ECU 40 (route B in FIG. 1).

  The diagnostic code request unit 34 of the diagnostic tester 30 requests the ECU 40 to read the diagnostic code in response to a command from the operation PC 10 (route C in FIG. 1), and the diagnostic code acquisition unit 36 operates the diagnostic code acquired from the ECU 40. The data is output to the PC 10 (route D in FIG. 1). As described above, the operation PC 10 evaluates the ECU 40 and diagnoses the simulator 20 based on the diagnosis code acquired by the diagnosis tester 30 from the ECU 40.

The diagnostic set unit 32, diagnostic code request unit 34, and diagnostic code acquisition unit 36 realize their functions by hardware and software.
The ECU 40 is mainly composed of a microcomputer having a CPU, a RAM, a ROM, an input / output interface, and the like. The ECU 40 includes an operation unit 42 that operates in accordance with an inspection signal output from the simulator 20 and a diagnosis unit 44 as a self-diagnosis function that diagnoses the operation result of the operation unit 42. The diagnosis unit 44 generates a self-diagnosis result for the operation of the operation unit 42 as a diagnosis code.

  As described above, the measuring instrument 50 is composed of an oscilloscope, a communication measuring device, and the like, and the operation information measuring unit 52 measures information that the operation PC 10 cannot acquire from the simulator 20 as operation information of the ECU 40 that is an inspection target. For example, if the measuring instrument 50 is an oscilloscope, the ECU 40 measures a drive signal for driving a control target such as a motor, and if the measuring instrument 50 is a communication measuring device, it measures communication information of the ECU 40 that is not supported by the simulator 20. And operation PC10 acquires the operation information of ECU40 which measuring instrument 50 measured (route E of Drawing 1).

(Diagnosis processing)
FIG. 2 shows a flowchart for executing a diagnosis process when diagnosing the simulator 20. In FIG. 2, “S” represents a step.

  When diagnosing the simulator 20, the operation PC 10 first instructs the diagnostic tester 30 to reset the ECU 40, and erases the diagnostic code generated so far by the diagnostic unit 44 of the ECU 40 (S400). Then, the operation PC 10 instructs the diagnostic tester 30 to request the ECU 40 to read out the diagnostic code generated by the diagnostic unit 44 of the ECU 40 in the reset initial state (S402).

  If the diagnostic code acquired by the diagnostic code acquisition unit 36 of the diagnostic tester 30 from the ECU 40 is an abnormal code (S404: abnormal), the operation PC 10 determines that the simulator is based on the diagnostic code generated by the ECU 40 because the ECU 40 is abnormal. 20 is determined not to be properly diagnosed, and the diagnosis of the simulator 20 is stopped (S406).

  If the diagnosis code is a normal code (S404: normal), the operation PC 10 outputs a command signal to the simulator 20 (S408), and causes the ECU 40 to output an inspection signal corresponding to the command signal from the simulator 20 (S410).

  For example, the operation PC 10 changes the value of the variable that determines the electric signal value output from the accelerator sensor model to the sensor signal generation unit 22 of the simulator 20 and causes the disconnection signal of the accelerator sensor to be output as the inspection signal. As the accelerator sensor disconnection signal, a 0.2 V signal deviating from a specified value (for example, 0.5 V or more) defined in the specification is output.

The ECU 40 operates in accordance with the inspection signal output from the simulator 20, and generates a diagnosis code by self-diagnosis of the operation result.
If the simulator 20 is normal, the simulator 20 appropriately outputs the above-described accelerator sensor disconnection signal in accordance with a command from the operation PC 10, and the diagnosis unit 44 of the ECU 40 displays a diagnosis indicating that the accelerator sensor is disconnected. Generate a code (eg '01').

  If the simulator 20 is abnormal, the simulator 20 outputs a signal satisfying the specified value as the detection signal of the accelerator sensor described above in response to a command from the operation PC 10. In this case, the diagnosis unit 44 of the ECU 40 generates a diagnosis code (for example, “02”) different from the diagnosis code (01) indicating that the accelerator sensor is disconnected.

  When the operation PC 10 causes the simulator 20 to output an inspection signal corresponding to the command signal from the simulator 20 (S410), the operation PC 10 instructs the diagnosis tester 30 to generate a diagnosis generated by the diagnosis unit 44 of the ECU 40 in response to the inspection signal output by the simulator 20. The ECU 40 is requested to read the code (S412).

  In S <b> 414, the operation PC 10 displays the diagnosis code acquired by the diagnosis tester 30 from the ECU 40 and the diagnosis code that the ECU 40 is supposed to generate for the inspection signal that the simulator 20 should output when the simulator 20 is normal. Compare.

  If the diagnosis codes match (S414: Yes), the operation PC 10 determines that the simulator 20 is normal, and there is an uninspected inspection signal that is output to the ECU 40 by instructing the simulator 20 to diagnose the simulator 20. If (S416: Yes), the process returns to S408.

  If the diagnosis codes do not match (S414: No), the operation PC 10 determines that there is an abnormal part in the simulator 20. In the example described above, the fact that the location where the accelerator sensor disconnection signal is generated is abnormal is displayed on the display or recorded in the inspection report (S418). When the abnormal location is displayed, the operator analyzes the detailed cause of the abnormal location.

  After displaying the abnormal part or recording it in the inspection report, the operation PC 10 shifts the process to S416, and if there is an uninspected inspection signal to be output to the ECU 40 to instruct the simulator 20 to diagnose the simulator 20 (S416). : Yes), the process returns to S408.

  Here, when diagnosing the simulator 20, the simulator 20 outputs an inspection signal in response to a command from the operation PC 10, and the ECU 40 that operates in response to the inspection signal generates the diagnosis unit 44 in the same manner as when inspecting the ECU 40. The operation PC 10 acquires the diagnosis code via the diagnostic tester 30.

  Therefore, it is not necessary to change the electrical connection of the inspection system 2 at the time of the inspection with respect to the ECU 40 during the diagnosis with respect to the simulator 20. Therefore, as shown in FIG. 3, the inspection for the ECU 40 and the diagnosis for the simulator 20 may be performed by automatically switching the inspection program 12 and the diagnosis program 14 at predetermined time intervals in the operation PC 10. The time interval for switching between the inspection program 12 and the diagnostic program 14 can be arbitrarily set for the operation PC 10.

  Instead of automatically switching between the inspection program 12 and the diagnostic program 14 at predetermined time intervals, when the inspection for the ECU 40 is completed a predetermined number of times, the operator operates the operation PC 10 to switch the inspection program 12 to the diagnostic program 14 and Diagnosis may be performed.

  As shown in FIG. 4, when the wiring of the simulator 20 and the diagnostic tester 30 and the ECU 40 is removed and another ECU 60 is connected to the simulator 20 and the diagnostic tester 30 and the operation of the ECU 60 is inspected, the operation PC 10 An identifier (ID) for instructing the diagnostic tester 30 to identify the ECU 60 is acquired from the ECU 60. Thereby, a vehicle model corresponding to the ECU 60 specified by the identifier can be set in the simulator 20.

Furthermore, when diagnosing the simulator 20, the inspection signal according to the ECU 60 specified by the identifier can be commanded to the simulator 20.
In the first embodiment described above, when diagnosing the simulator 20, the operation PC 10 instructs the simulator 20 to output an inspection signal, and based on the diagnosis code generated by the diagnosis unit 44 of the ECU 40 in response to the inspection signal. Thus, it is diagnosed whether the simulator 20 is normal or abnormal. That is, it is not necessary to change the electrical connection of the inspection system 2 between when the operation of the ECU 40 is inspected and when the simulator 20 is diagnosed.

  As described above, since the simulator 20 can be diagnosed in the same electrical connection state of the inspection system 2 as that at the time of the inspection of the ECU 40, that is, in the same environment, whether the simulator 20 is normal or abnormal based on the diagnostic code generated by the ECU 40. Can be diagnosed with high accuracy.

Furthermore, in order to diagnose the simulator 20, it is not necessary to prepare unnecessary equipment and devices when the ECU 40 is inspected.
In the first embodiment, the inspection system 2 corresponds to the inspection system of the present invention, the ECUs 40 and 60 correspond to the inspection object of the present invention, the simulator 20 corresponds to the inspection apparatus of the present invention, and the diagnostic tester 30 corresponds to the present invention. The operation PC 10 corresponds to the inspection control device of the present invention. The operation PC 10 functions as command means and diagnosis means of the present invention.

  2 correspond to the functions executed by the inspection target operation device and the inspection control device of the present invention, and the processing of S404 to S408 and S414 to S418 is performed by the inspection control device of the present invention. This corresponds to the function to be executed, and the process of S410 corresponds to the function executed by the inspection apparatus of the present invention.

[Second Embodiment]
FIG. 5 shows an inspection system according to the second embodiment of the present invention. Components that are substantially the same as those in the first embodiment are denoted by the same reference numerals.

  In the inspection system 4 of the second embodiment, the inspection object 70 whose operation is to be inspected is not a single ECU but a plurality of ECUs 80, 90, 92. The main ECU 80 and the other ECUs 90 and 92 are connected via a network.

  For example, when the ECUs 90 and 92 control the assembly (ASSY) that drives the brakes, windows, and the like of the vehicle in cooperation with each other, the main ECU 80 arbitrates cooperative control and generates diagnostic information generated by the diagnostic unit of the ECUs 90 and 92. To generate a diagnostic code.

Since the main ECU 80 itself also includes an operation unit 82 and a diagnosis unit 84, the diagnosis unit 84 generates a diagnosis code for the operation result of the operation unit 82.
When diagnosing the simulator 20 in the inspection system 4, as in the first embodiment, the diagnosis code generated by the diagnosis unit 84 of the ECU 80 and the ECU 90, which is instructed from the operation PC 10 to output an inspection signal by the operation PC 10, and the ECU 90 , 92 diagnosing whether the simulator 20 is normal or abnormal based on the diag code generated by the ECU 80 by collecting the diag information generated by the diag part.

Also in the inspection system 4, the simulator 20 can be diagnosed in the same electrical connection state as when the inspection target 70 is inspected.
In the second embodiment, the inspection object 70 corresponds to the inspection object of the present invention.

[Third Embodiment]
An inspection system according to a third embodiment of the present invention is shown in FIG. Components that are substantially the same as those in the first embodiment are denoted by the same reference numerals.

  In the inspection system 6 of the third embodiment, the simulator 100 is configured by incorporating the functions of the diagnosis set unit 32, the diagnosis code request unit 34, and the diagnosis code acquisition unit 36 included in the diagnosis tester 30 in the first embodiment. ing.

In the third embodiment, the simulator 100 corresponds to the inspection device and the inspection target operation device of the present invention.
[Other Embodiments]
The inspection apparatus for inspecting the operation of the inspection object will be described in the above embodiment if an appropriate inspection signal can be output in response to a command from the inspection control apparatus at the time of inspection of the inspection object and at the time of diagnosis of the inspection apparatus. The inspection apparatus is not limited to the above simulator, and any inspection apparatus may be used.

  In the above embodiment, the vehicle inspection system has been described. In addition to this, if the object to be inspected has a self-diagnosis function and a means for acquiring a diagnosis code generated by the self-diagnosis function other than the inspection device, for example, an electronic device in an airplane or medical facility is inspected. The inspection system of the present invention may be applied to a target inspection system.

  Moreover, in the said embodiment, operation PC10 evaluated the test object. On the other hand, the inspection system of the present invention does not perform the evaluation of the inspection object until the inspection apparatus such as a simulator outputs an inspection signal and the inspection apparatus inspects the operation of the inspection object according to the inspection signal. It may be limited to function.

  As described above, the present invention is not limited to the above-described embodiment, and can be applied to various embodiments without departing from the gist thereof.

2, 4, 6: inspection system, 10: operation PC (inspection control device), 20: simulator (inspection device), 30: diagnostic tester (inspection target operation device), 40, 60: ECU (inspection target), 70: Inspection target, 100: simulator (inspection device, inspection target operation device)

Claims (5)

In the inspection system for inspecting the operation of the inspection object,
A test object having a self-diagnosis function;
An inspection apparatus that outputs an inspection signal for inspecting the operation of the inspection object and outputs at least a part of the operation information of the inspection object that operates according to the inspection signal;
An inspection object operating device that acquires from the inspection object a diagnostic code generated by the self-diagnosis function of the inspection object when the inspection object operates in response to the inspection signal output by the inspection apparatus;
Command means for causing the inspection apparatus to output the inspection signal according to each of the inspection of the inspection object and the diagnosis of the inspection apparatus, and the operation that operates according to the inspection signal during diagnosis of the inspection apparatus An inspection control device having diagnostic means for diagnosing whether the inspection device is normal or abnormal based on the diagnostic code acquired by the inspection target operation device from the inspection target;
An inspection system comprising:   2. The inspection system according to claim 1, wherein, before the diagnosis unit diagnoses the inspection apparatus, the instruction unit instructs the inspection target operation device to reset the inspection target.   The instruction means stops the diagnosis for the inspection apparatus when the diagnostic code acquired from the inspection object is an abnormal code when the inspection object operation device resets the inspection object. 2. The inspection system according to 2.   The inspection system according to any one of claims 1 to 3, wherein the command unit switches between an inspection on the inspection object and a diagnosis on the inspection apparatus at a set time interval. The inspection object operation device acquires an identifier for identifying the inspection object from the inspection object,
The command means causes the inspection device to output the inspection signal corresponding to the identifier acquired by the inspection target operation device.
The inspection system according to any one of claims 1 to 4, wherein:

Images